What will break in next release

[vikiival]

I am currently polishing last bits for minimal RMRKv2
And there would be a ton of changes:

1. Some actions were renamed

MINTNFT -> MINT
CONSUME -> BURN

[yangwao]

Can we not merge this update till we push out this one to main & hyper-jpeg

• redesign: Offers - add accepting and canceling offers #4437

[vikiival]

Yes will update also snek with suitable data

[vikiival]

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!"
}

• fix: fallback to mp4 thumbnail #6080
• fix: 3D NFT Thumbnail Preview #6956
• unify nft item metadata workers#95

[vikiival]

@kodadot/internal-dev: we plan to release a squid versions with unified addresses (no more different addresses per chain).

Question is which address format is more friendly for you:

1. Polkadot (prefix 0) Vote ❤️
2. General substrate (prefix 42) vote 🚀

@kodadot/design-squad, @kodadot/internal-dev, @kodadot/internal please vote (for 1. ❤️, for 2. 🚀 )

[JustLuuuu]

What is easier for users to understand? Also for newcomers (peeps outside of ecosystem)? In Nova Wallet, I tried to find my generic one and I was not able to find it. So I would say Polkadot

[vikiival]

What is easier for users to understand?

That is a very good and valid question:

1. React fork of KodaDot is using (42)
2. I honestly think many newcomers come via polkadot so they see (prefix 0)

That is the reason I started the discussion to collectively decide.

[jsidorenko]

Developers usually use 42, since this is what set locally + on westend and rococo

[damskyftw]

If something it should be Polkadot :)

[vikiival]

Since #10354 is up I am in favour of use Substrate generic addresses.

[vikiival]

Dev update 09/23

1. SubSquid pricing

As you may know, subsquid is going for a paid model when we are billed for indexing, data storage, and API availability.
This pricing is very friendly; however, we can still save money on the infrastructure.
Therefore, we decided to do a few optimizations:

1. Deprecation of old squids

since SubSquid cannot bill old squids, they will have end-of-life on 1st October 2023.
Namely: click, antick, rubick@008
There is a WIP to bring the moonbeam indexer again

• 🌕 Deprecating Moon(River/Beam) for now #7369
• 🔧 rubickV9 #7373

Edit:
There is an unknown bug in rubick/marck #7373 that they index less nfts as they should because of this reason I removed rubickV9, forked 008 and released v8 which will be supported for the longer period of time.

2. Removing snek chain

Sadly, 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.
Is there going to be a testnet? There is an issue with creating AHW or AHR (Westend or rococo) for devs to try all the features.
Contact me if you are familiar with deploying docker images to some pricing/dev-friendly infra. We can pay a bounty for the setup.
EOL is also on 1st October 2023

Edit:
I managed to configure snek into very minimal squid so I would move Its life for at least 1st Nov 2023

As I mentioned I am still in favour of running AHR (rococo) for the test purposes.

3. Combining RMRK + KSM

According to pricing, the part of “indexing” is the highest on the bill.
Since rmrk and KSM index the same chain, they could be merged under “the one” indexer. For this change to happen, there is currently no date to make it happen. See parts 2.1 and 2.2

Edit: Most probably this won't happen as addressed in edit of 1.1

2. Breaking changes

1. Unified addresses

As 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.
As agreed per the discussion above, we will show the address in the Polkadot prefix on the subsquid side; however, we plan to use the original ss58 address as it is more common in the ecosystems, and both wallets prefer them by default.

2. Prefixed legacy nfts

To 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 / Workers

Apart 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

[preschian]

aahh I see, thank you so much, I will turn it off now

[vikiival]

sad, I like snek. Because testing on mainnet is quite expensive

I will try to optimize the squid pricing so we can keep it running for testing.
I am still in favour of switching to ahw/ahr.

[preschian]

I am still in favour of switching to ahw/ahr

this one is also better 👍

[exezbcz]

1. Unified addresses

this is good!

[vikiival]

Updated ^-^ with edits