NFT Token Standard Working Group We at DFINITY are dedicated to providing better developer experiences and driving adoption. Along with members of our great community, we created the first Fungible Token Standard ICRC-1. The standard is seeing increasing adoption and is paving the path for easier in…

Personally, I would consider it to be a high priority if we want to grow the ecosystem. Right now, as you know, most NFT projects are bound to their FE marketplace provider (Toniq, Yumi, etc). This is because the marketplace address is baked into the canister code at deployment. Independent NFT mar…

It doesn’t sound demanding at all. Those concerns were what was behind the origyn_nft standard to begin with. We put the marketplace inside the NFT collection with standardized market functions to create a balance between marketplaces that tend to accrue too much power in the classic paradigm and …

Full Batch API semantics In last week’s NFT standards WG meeting the group discussed the batch interface again, because this is the current work item of the Ledger and Tokenization WG ( ICRC-4 Batch transfers for fungible tokens ). The outcome of the discussions was that we should align the NFT batch …

The above post lists the reasonable API options for batch APIs so we can move forward with full batch semantics, compared to the more constrained bulk semantics we have now. My personal preference is one of the variations of Option 2 for the following reasons. The discussions on ICRC-4 also have …

I also think that Option 2 works best. As far as needing to include the request with the result in the response, it puts a constraint on the possible implementation space that you will not be able to optimize the processing of transactions in a scenario where parallelization might improve the perfo…

@pramitgaha has a valid question implementing the standard in rust. does anyone have any ideas? [image] Assigned: BNT-5 - ICRC-7 NFT Implementation (Rust or Motoko) Bounties Hello, I’m facing an issue while implementing the transaction log for icrc30_revoke_token_approvals…

I responded. We need more input from him in order to be able to discuss in the WG. See my comment on this in the other topic.

The Option 2.3 you give, quoted below, is quite neat. [image] skilesare: type TransferBatchResult = vec opt record { transfer_result : variant { Ok : nat; // Transaction index for successful transfer Err : TransferError }; }; My understanding is that with this option …

hello, I’ve replied in the another thread, can you check?

ICRC-30 is now ICRC-37. The reason is that it did not stick to a naming convention initially.

Call for Participation: NFT Token Standard Working Group [Status Updated]

Developers

cryptoschindler January 23, 2024, 10:59am 170

@pramitgaha has a valid question implementing the standard in rust. does anyone have any ideas?

Topic		Replies	Views
Assigned: BNT-5 - ICRC-7 NFT Implementation (Rust or Motoko) Bounties & RFPs NFT	72	4294	June 25, 2024
Announcing "Token Standard" as topic of the first meeting of the Ledger & Tokenization Working Group Developers	319	15338	November 26, 2024
ICRC-1 Token Standard final draft Developers	40	3775	February 28, 2023
Thoughts on the token standard Developers	199	21394	December 26, 2022
ICRC-1 Token Standard Ledger Developers	128	7106	September 22, 2022

Call for Participation: NFT Token Standard Working Group [Status Updated]

Related topics