kodadot / stick Goto Github PK

Describe the bug

Magically I do not know where the code is for that

To Reproduce

1. Run squid
2. No royalty is extracted

Expected behavior

extend NFTEntity

Describe the bug

@jsidorenko if I understand that correctly, you can totallly give up rights of your collection?

This is useful for cases when the collection is created, all the items are minted and now we want to be 100% sure no one will mint any more items, or change the metadata, or disable some item's transfer.

To Reproduce
Steps to reproduce the behavior:

• Submit extrinsic when you set empty issuer
• issuer will stay the same

Expected behavior
A clear and concise description of what you expected to happen.

• mark collection as standalone?
• set max to current supply

Resolver that would fetch all swaps available for the NFT

An event handler for indexing the the cancelation of a atomic swap event from a chain will be developed.

Steps:

• into typegen.json add: REF

[
 "Assets.Created",
 "Assets.MetadataSet"
]

• typegen
• in src/mappings/assets make files create.ts and setMetadata.ts
• the functions should early return when they are not in 'Our' allowList

Formulation and creation of a GraphQL schema entity representing Non-fungible tokens.

Develop a handler that marks particular collection as tombstone for Offers.

Process

• 1) create a public collection “Koda offers” with unlimited supply

• 2) if user wants to place an order, batch 2 calls: mint + create_swap

• 3) list all the offers via indexer

• 4) when user accepts, batch the claim + burn calls

that’s how you get the offers onchain + some incentive for the bidders to remove their offer later

• there is an option to set the expiration date for each offer

Ensuring backward compatibility with current Uniques v1.

An event handler for indexing the claiming of a atomic swap event from a chain will be developed.

Describe the bug

NFTs pallet is coming to statemine and we want to support both pallets at once
Therefore we should prefix Uniques Collections and nfts with u- prefix

An event handler for indexing the creation of a atomic swap event from a chain will be developed.

Design and include royalty support within the GraphQL schema.

Development of a GraphQL schema entity that represents the Atomic Swap.

Push version to 4 in squid.yml
Do a pr against main
After merge pr to release-squid

Cc @daiagi

Ref

• kodadot/nft-gallery#5322
• https://github.com/kodadot/ops-internal/issues/318

          Doesn't load because they are all videos (https://image-beta.w.kodadot.xyz/ipfs/QmT2yg18YvYdECQcy5VJ4NYUd1dvVUjxJEhqiKBcMgS5UF) maybe missing `thumbnailUri` or `mediaUri` from indexer side?

Originally posted by @roiLeo in kodadot/nft-gallery#5974 (comment)

• kodadot/loligo#10

A handler that tracks surcharge on Atomic Swap will be developed.

Development of a GraphQL schema entity that represents the collection.

If you open Statemine, there are collections missing. You cannot see Decoded 2023 collections there. https://kodadot.xyz/stmn/explore/collectibles

There are currently only 19 collections!

Same on Canary. Where are they?

_Originally posted by @JustLuuuu in kodadot/nft-gallery#6477

• #47
• #48
• #49
• #50
• #51
• #52
• #53
• #54
• #55
• #56
• #57
• #58
• #59
• #60
• #61
• #62
• #63
• #64
• #65
• #66
• #67
• #68
• #69
• #70
• #71
• #72
• #73
• #74
• #75
• #76
• #77
• #78
• #79
• #80
• #81
• #82
• #83
• #84
• #85
• #86
• #87
• #88
• #89
• #90
• #91
• #92

Same as Manifold royalty registry we can select an account that will serve as royalty registry and use RR namespace for royalty percent and receiver

Implement a handler to add royalty into NFT

What

It would be nice to have an on-chain multi royalty system.

How

receivers => [ [address, royalty] ] where the sum of all the royalties here should be equal to 100
the main field royalty will represent the cut from the sale price (e.g. 5%), where the receivers will tell how to split that 5% (e.g. 30% to address1, 70% to address2)

let's introduce receivers that is Tuple(string, number) Array.

Describe the bug

When someone makes on-chain attributes they are not processed by indexr

To Reproduce

• post attribute via polkadot-js

Expected behavior

Screenshots

// TODO

• copy/paste code from other indexers