Skip to content

Commit

Permalink
Updated readme propposal.
Browse files Browse the repository at this point in the history
  • Loading branch information
pa-long committed Oct 30, 2024
1 parent 4388645 commit 1ea043b
Showing 1 changed file with 2 additions and 4 deletions.
6 changes: 2 additions & 4 deletions arc722/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ The Aleo NFT Registry extends ARC721 standard, defining a registry for NFTs thro

Moreover, ARC722 can be implemented with any `Data` struct type, allowing abitrary on-chain NFT data.

[An example implementation is available here](./src/main.leo), with `Data` defined as:
[Such an implementation can be found here](./src/main.leo), with `Data` defined as:

```rust
struct Data {
Expand All @@ -23,11 +23,9 @@ struct Data {

## Enforcing Registry list

Here are two possible ways of registry program enforcement.
Since multiple registry, will co-exist, we should decide on how we keep track of registry program list. Here are two propositions, but feel free to make any additional suggestions.

1. Explorers could maintain a list of valid ARC722 implementations.
2. Wallets could allow to add custom registry programs, similar to how MetaMask allows adding custom token contracts.

Feel free to make any suggestions.

NFT collections are then identified by the unique pair: `(registry_program_id, collection_id)`.

0 comments on commit 1ea043b

Please sign in to comment.