kitty-kad

Thanks fo the response! > suggest an interface functioning at the level of policies Having this interface be implemented on policies make sense for marmalade based NFTs. However since there...

@Gh0stts0hg thanks for jumping into the discussion, good to see other people get involved :) > don't see why ledger can't inherently support it One thing with having it at...

@sirlensalot agree with most of what you said One question > each row has a list of the tokens managed in that collection, e.g. (defschema collection tokens:[string]) Since each row...

@nzpopa thanks for sharing your thoughts and good to get more data-points on whether this is an issue or not :) > If the computational effort is too big I...

@Gh0stts0hg in your scenario - adding (writing) is O(1), which will be very gas efficient. Reading will be O(N) since it can be a _SELECT keys -> filter where key...

> then stored account.index -> token id in a separate table In this case, if someone sells an NFT and index 0, it'll require putting a different NFT they own...

Happy to keep `get-all-tokens-for-owner` optional - it makes sense based on the conversation above. Also another marmalade related concern came up while implementing a marketplace - How to handle capabilities...

Continued discussion about royalties here https://github.com/kadena-io/KIPs/issues/27

This may be fixed by follow on work from https://github.com/kadena-community/kadena.js/pull/59 Leaving discussion for the community to decide if we should still add it to the standard or rely on code...