-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arc 41 - NFT's vault of NFT, Algo & Fungible Token #213
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not commenting on substance of arc atm, but have some minor feedback
ARCs/arc-0041.md
Outdated
The `arc41_transferFrom` method MUST error when `from` is not the owner of `asaId` or `tokenId`. | ||
|
||
## Rationale | ||
ASAs NFT ([ARC-3](./arc-0003.md), [ARC-69](./arc-0069.md)) and Application NFT ([ARC-72](./arc-0072.md)) are compatible with This standard. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although ARC-3, ARC-19, ARC-69 are all just ASAs and nothing about this spec cares about their initial config or metatadata variations (and just tracks an ASA ID), I'd add ARC-19 to this list for completeness - otherwise some might think it doesn't apply.
Wording + naming
This standard is inspired by EIP-6551
The goal is to allow an ASA to detain & manage ASAs or Algo through a ”vault”.