From 2440bb5507c8f38a4dfa77eee322fc4fd7ed9ad8 Mon Sep 17 00:00:00 2001 From: Sneh1999 Date: Thu, 27 Jul 2023 14:35:36 -0400 Subject: [PATCH 1/2] Update NFT example in solana caip-19 --- solana/caip19.md | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/solana/caip19.md b/solana/caip19.md index 10ce77a0..87a4a320 100644 --- a/solana/caip19.md +++ b/solana/caip19.md @@ -2,7 +2,7 @@ namespace-identifier: solana-caip19 title: Solana Namespace - Asset author: Qiao Liang (@qbig) -discussions-to: +discussions-to: status: Draft type: Standard created: 2022-06-01 @@ -12,7 +12,7 @@ requires: ["CAIP-2", "CAIP-10", "CAIP-19", "CAIP-30"] # CAIP-19 -*For context, see the [CAIP-19][] specification.* +_For context, see the [CAIP-19][] specification._ ## Rationale @@ -21,24 +21,22 @@ On Solana, all contracts are stateless and state is instead represented using "a - 1 single global "mint" account instance is used for the global data like "total supply". - each token account represents an account balance belonging to a given address. -The only difference between fungible tokens and non-fungible tokens is that non-fungible token mints have a total supply of 1 and zero decimal place. Both asset type can be identified by their "mint" account. - +The only difference between fungible tokens and non-fungible tokens is that non-fungible token mints have a total supply of 1 and zero decimal place. Both asset type can be identified by their "mint" account. ## Syntax After the [CAIP-2][] (namespace+chainID), a slash defines an `asset_namespace` and an `asset_reference`. Since both fungible and non-fungible tokens can be identified using the mint account, we use `token` (fungible) and `nft` (non-fungible) as the asset namespaces and the address of the `mint` account as the reference in both. -| Reference | Equivalent to | See also | -| :--- | :---- | :--- | -| token | ERC20 Token | [Metaplex](https://docs.metaplex.com/programs/token-metadata/token-standard) Fungible | -| nft | ERC721 | [Metaplex](https://docs.metaplex.com/programs/token-metadata/token-standard) NonFungible| - +| Reference | Equivalent to | See also | +| :-------- | :------------ | :--------------------------------------------------------------------------------------- | +| token | ERC20 Token | [Metaplex](https://docs.metaplex.com/programs/token-metadata/token-standard) Fungible | +| nft | ERC721 | [Metaplex](https://docs.metaplex.com/programs/token-metadata/token-standard) NonFungible | ## Examples ``` # One Solana Mainnet NFT：Pesky Penguins #398 -solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp/token:Fz6LxeUg5qjesYX3BdmtTwyyzBtMxk644XiTqU5W3w9w +solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp/nft:Fz6LxeUg5qjesYX3BdmtTwyyzBtMxk644XiTqU5W3w9w # Solana Mainnet USDC solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp/token:EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v @@ -55,7 +53,6 @@ solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp/token:EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEG [CAIP-19]: https://github.com/ChainAgnostic/CAIPs/blob/master/CAIPs/caip-19.md [CAIP-30]: https://github.com/ChainAgnostic/CAIPs/blob/master/CAIPs/caip-30.md - ## Copyright Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). From f5a37f69d26d994bd8f1473507ca7e4c24cc6bf2 Mon Sep 17 00:00:00 2001 From: Sneh1999 Date: Thu, 27 Jul 2023 14:37:21 -0400 Subject: [PATCH 2/2] fix formatting --- solana/caip19.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/solana/caip19.md b/solana/caip19.md index 87a4a320..8c5f5538 100644 --- a/solana/caip19.md +++ b/solana/caip19.md @@ -2,7 +2,7 @@ namespace-identifier: solana-caip19 title: Solana Namespace - Asset author: Qiao Liang (@qbig) -discussions-to: +discussions-to: status: Draft type: Standard created: 2022-06-01 @@ -12,7 +12,7 @@ requires: ["CAIP-2", "CAIP-10", "CAIP-19", "CAIP-30"] # CAIP-19 -_For context, see the [CAIP-19][] specification._ +*For context, see the [CAIP-19][] specification.* ## Rationale @@ -21,16 +21,18 @@ On Solana, all contracts are stateless and state is instead represented using "a - 1 single global "mint" account instance is used for the global data like "total supply". - each token account represents an account balance belonging to a given address. -The only difference between fungible tokens and non-fungible tokens is that non-fungible token mints have a total supply of 1 and zero decimal place. Both asset type can be identified by their "mint" account. +The only difference between fungible tokens and non-fungible tokens is that non-fungible token mints have a total supply of 1 and zero decimal place. Both asset type can be identified by their "mint" account. + ## Syntax After the [CAIP-2][] (namespace+chainID), a slash defines an `asset_namespace` and an `asset_reference`. Since both fungible and non-fungible tokens can be identified using the mint account, we use `token` (fungible) and `nft` (non-fungible) as the asset namespaces and the address of the `mint` account as the reference in both. -| Reference | Equivalent to | See also | -| :-------- | :------------ | :--------------------------------------------------------------------------------------- | -| token | ERC20 Token | [Metaplex](https://docs.metaplex.com/programs/token-metadata/token-standard) Fungible | -| nft | ERC721 | [Metaplex](https://docs.metaplex.com/programs/token-metadata/token-standard) NonFungible | +| Reference | Equivalent to | See also | +| :--- | :---- | :--- | +| token | ERC20 Token | [Metaplex](https://docs.metaplex.com/programs/token-metadata/token-standard) Fungible | +| nft | ERC721 | [Metaplex](https://docs.metaplex.com/programs/token-metadata/token-standard) NonFungible| + ## Examples @@ -53,6 +55,7 @@ solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp/token:EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEG [CAIP-19]: https://github.com/ChainAgnostic/CAIPs/blob/master/CAIPs/caip-19.md [CAIP-30]: https://github.com/ChainAgnostic/CAIPs/blob/master/CAIPs/caip-30.md + ## Copyright Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).