docs: add permit functionality to allow single transactions registers

This commit is contained in:
jm-clius 2025-09-26 11:43:06 +01:00
parent 6887a986cd
commit 54ff957623
No known key found for this signature in database
GPG Key ID: 5FCD9D5211B952DA
2 changed files with 3 additions and 1 deletions

View File

@ -13,6 +13,7 @@
2. User does not need to wait for merkle tree synchronization and building to start relaying 2. User does not need to wait for merkle tree synchronization and building to start relaying
or sending messages. or sending messages.
3. Application does not need to do a Web3 RPC call for every tree change to generate or validate messages. 3. Application does not need to do a Web3 RPC call for every tree change to generate or validate messages.
4. Application can transfer tokens and register membership with a single transaction.
## Reliability ## Reliability

View File

@ -132,7 +132,7 @@ See deliverables.
- [ ] Dogfood: link to dogfooding session/artefact - [ ] Dogfood: link to dogfooding session/artefact
- [ ] Docs: links to README.md or docs.waku.org (TBD) - [ ] Docs: links to README.md or docs.waku.org (TBD)
### Improve RLN UX by reducing Web3 RPC calls ### [Improve RLN UX by reducing contract interactions](https://github.com/waku-org/pm/issues/344)
**Owner**: core research **Owner**: core research
@ -140,6 +140,7 @@ See deliverables.
**FURPS**: **FURPS**:
- U3. Application does not need to do a Web3 RPC call for every tree change to generate or validate messages. - U3. Application does not need to do a Web3 RPC call for every tree change to generate or validate messages.
- U4. Application can transfer tokens and register membership with a single transaction.
**Checklist**: **Checklist**:
- [ ] Specs: link to specs and/or API definition - [ ] Specs: link to specs and/or API definition