trn-seed
trn-seed copied to clipboard
Add collection info - RPC call
PR checklist
- [ ] Describe the added/changed/fixed/removed behaviour
- [ ] Tag related issue(s)
- [ ] Add appropriate unit tests and/or integration tests to the integration test repository
Looking good, some fields I don't think are needed in this RPC call. I also think we should have a think about whether it would make sense to have one RPC for all information, or multiple RPC calls for each individual part. What do you think?
Thanks for your review.. I think the reason for this rpc call is, storage collection_info would fail, ownedTokens list if it is too huge, then the storage retrieval fails.. so an alternative to that without ownedTokens info