You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no single reference for traits defined by the Stacks Improvement Process.
A document maintained in this repo which lists recommended trait contracts already deployed will be helpful to new and existing developers.
SIPs 009 and 010 reference a deployed mainnet trait contract but not testnet versions. Versions for testnet are included below along with the new SIP-013 standard which is deployed on testnet but not yet ratified.
+1, was looking for a testnet version of SIP-009/SIP-010 and saw that many projects deploy their own.
I could see it done two ways:
a separate document outlining deployed contracts
a specific section in the SIP for deployed contracts
I'm leaning toward the latter because then it would be each SIP author's job to provide/update the deployment information, and it keeps all the information for a particular SIP together in one place.
Maybe right after the Activation section add something for Deployed Contracts so it's more explicit?
Also, should the trait name be listed in the link? Imagining two flows: one where the trait reference is copied directly from the SIP, and the other where the link is to the explorer/contract and you have to get the trait reference from the contract source. I prefer the latter, but it's definitely some extra steps.
For example, with SIP-010:
Activation
This trait will be considered activated when this trait is deployed to mainnet, and 3 different implementations of the trait have been deployed to mainnet, no later than Bitcoin block 700000.
There is currently no single reference for traits defined by the Stacks Improvement Process.
A document maintained in this repo which lists recommended trait contracts already deployed will be helpful to new and existing developers.
SIPs 009 and 010 reference a deployed mainnet trait contract but not testnet versions. Versions for testnet are included below along with the new SIP-013 standard which is deployed on testnet but not yet ratified.
Mainnet
SIP-009
SP2PABAF9FTAJYNFZH93XENAJ8FVY99RRM50D2JG9.nft-trait.nft-trait
SIP-010
SP3FBR2AGK5H9QBDH3EEN6DF8EK8JY7RX8QJ5SVTE.sip-010-trait-ft-standard.sip-010-trait
SIP-013 not yet ratified / deployed
Testnet
SIP-009
ST1NXBK3K5YYMD6FD41MVNP3JS1GABZ8TRVX023PT.nft-trait.nft-trait
SIP-010
ST1NXBK3K5YYMD6FD41MVNP3JS1GABZ8TRVX023PT.sip-010-trait-ft-standard.sip-010-trait
SIP-013
ST1NXBK3K5YYMD6FD41MVNP3JS1GABZ8TRVX023PT.sip013-semi-fungible-token-trait.sip013-semi-fungible-token-trait
References
The text was updated successfully, but these errors were encountered: