CIP112: Receivers should be able to pre-approve incoming transfers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue describes registry support for transfer pre-approvals and links to the draft standard in canton-network/splice#2085 and an Amulet example in Splice/AmuletRules.daml. Read those references first; the issue says this feature may be added once the standard is public. Done would mean supporting the standard so compatible wallets can pre-approve incoming transfers, but the implementation scope is not yet specified.
Written by the indexing model from the issue text.
Description
A transfer completes in one step only when the receiver's account parties are among actors. Otherwise the sender's funds lock until the receiver accepts. Amulet solves this with TransferPreapproval, and standard wallets get the one-step transfer without any preapproval-specific code.
Our registry should support the same, but because this isn't a standard operation, wallet's don't support it out of the box, and OZ's CIP112 registry would require custom UI to create transfer pre-approvals on wallets supporting CIP103.
There's a draft standard for pre-approval support for registries https://github.com/canton-network/splice/issues/2085, so we could add this feature once the standard is public.
- Dominant language
- Haskell
- Stars
- 5
- Forks
- 0
- Avg merge
- 1d 36m
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenZeppelin/canton-contracts
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenZeppelin/canton-contracts#92 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
OpenZeppelin/canton-contracts#88 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenZeppelin/canton-contracts#86 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
OpenZeppelin/canton-contracts#96 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
OpenZeppelin/canton-contracts#95 ·
Maintainers usually reply within 1 day
All issues in OpenZeppelin/canton-contracts
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
IntersectMBO/cardano-ledger#6276 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
hasura/graphql-engine#10954 ·
Maintainers usually reply within 1 day