omarhamdan

Hey beautiful discussion, to your answer > Thus, the simplest collection implementation records all tokens added (captured via enforce-init). It could then support operations to list token IDs, etc. (Note...

Also policy could benefit from having enforce-withdraw incase it wants to track open sales per user

To track open sales for buyers/nfts : Currently, the SALE escrow handles "timeout" through capabilities, by checking if we're within timeout, but does not pass to policy. Having it at...

Could we lower computation by indexing differently, data is cheaper than computation here i would assume given we're on kadena > Since each row is a collection, I'm wondering if...

Thanks for your answer, and loved the enumeration logic explanation! > One question would be if get-account-token* should take a collection ID or span collections ... here if you mean...

very good points & thank you very much for discussion! i will create policy based on both (directly in implementation, nothing on interface level for now) and share here if...

@kitty-kad yep that is correct, it falls under > Requires managing this new state like you said shift from last, this is probably the easiest way to deal with it,...

Hey @sirlensalot , not fully sure i followed this > > Mutability makes this index degrade to O(n) on write. This means lists are asymptotically equivalent ... it seems like...

just saw earlier reply, will look over in detail but for now will assume token list approach is the way to go, thanks again! > letting them have dynamic NFTs:...