Replies: 4 comments 19 replies
-
Can we not merge this update till we push out this one to |
Beta Was this translation helpful? Give feedback.
-
We need to find a way how to unify metadata for chains How Kodadot works? We use OpenSea metadata standard so everything which was minted through us will is following this. What others have you seen? Example of metadata {
"name": "Kodachain - Bled Mini-conference 2023",
"image": "ipfs://ipfs/bafybeiasrjssdtaqegmsx4nuhcxnjoy6iw6pyeou3l7qf7gp7fvgst6l3y",
"animation_url": "ipfs://ipfs/bafybeievjhx7fxkgrkgyktbmominjy7u2f5qhcl6decspyhnxhq7hnumhe",
"description": "Congratulations! You are the owner of this commemorative Kodachain. You received it for attending the event on the 6th of May 2023. This event took place in SubWork Bled (Slovenia) and it was full of interesting speakers mostly from the Polkadot ecosystem. Created by [Sebicified](https://twitter.com/sebicified)./n Participate and join our future events so you can collect more Kodachains!"
} |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Dev update 09/231. SubSquid pricingAs you may know, subsquid is going for a paid model when we are billed for indexing, data storage, and API availability. 1. Deprecation of old squidssince SubSquid cannot bill old squids, they will have end-of-life on 1st October 2023. Edit: 2. Removing snek chainSadly, as it was our only test indexer, we no longer plan to support Snek, as the bill for that is much more than developers usually pay for testing on AHK. Edit: As I mentioned I am still in favour of running AHR (rococo) for the test purposes. 3. Combining RMRK + KSMAccording to pricing, the part of “indexing” is the highest on the bill. Edit: Most probably this won't happen as addressed in edit of 1.1 2. Breaking changes1. Unified addressesAs you have seen on kodadot.xyz, the address of a logged-in user changes based on the chain in which they are logged in. This is, however, sad for UX as the user always has to “learn” his/her address. 2. Prefixed legacy nftsTo support two protocols per squid, we decided to prefix nfts and collection with the prefix u- as it stands for (uniques old pallet on asset hub ). As mentioned in 1.3, a similar thing will come to the rmrk1.0, where nfts will get the same prefix. This is just an aware note to construct the correct extrinsic. 3. Data availability / WorkersApart from my assigned tasks, my current focus will be Squids and workers. If you find some parts of the app slow, please open an issue in Kodadot/loligo, ideally accompanied by another issue from nft-marketplace |
Beta Was this translation helpful? Give feedback.
-
I am currently polishing last bits for minimal RMRKv2
And there would be a ton of changes:
MINTNFT
->MINT
CONSUME
->BURN
Beta Was this translation helpful? Give feedback.
All reactions