Sriram Krishnan pfp
Sriram Krishnan
@sriramk.eth
What do folks here think of the NFT mandatory vs optional royalty discussion currently going on? Feels like FC is a much better place to have a conversation than on the blue app.
35 replies
0 recast
0 reaction

nyx.eth pfp
nyx.eth
@nyx
i've implemented EIP-2981, the royalties standard in contract, set manually in opensea, and used the manifold registry. even for coded in contract, marketplaces still have to be willing to write the corresponding code to respect the standard and most don't.
4 replies
0 recast
0 reaction

JG pfp
JG
@bigcymbal
But that’s just a limitation of EIP-2981 as long term full solution though right? If gas costs were negligible to the consumer, the royalty requirement and distribution could be baked right into the transfer functions themselves rather than the fee being metadata as in EIP-2981
1 reply
0 recast
0 reaction

nyx.eth pfp
nyx.eth
@nyx
i thiiink you wouldn't want to bake it directly in transfer since royalties only apply to sales vs moving between your own wallets price is also set by the marketplace, its an eth <> nft swap kinda. if you left it up to them to pass price as an arg, they can also get around it.
1 reply
0 recast
0 reaction

JG pfp
JG
@bigcymbal
Maybe dumb Q: why wouldn’t the royalties just be 0 in that case (and hypothetically marketplace clients could just make the assumption that a transfer with 0 erc20 value attached in this hypothetical would be a transfer and >0 as sale for display purposes eg last sale price)
1 reply
0 recast
0 reaction

nyx.eth pfp
nyx.eth
@nyx
its not dumb!! the main problem is that magic eden is choosing intentionally not to implement the logic, so letting them pass 0 or non 0, it's still not enforced. prices are set at the marketplace level, so its a tricky thing to enforce in your contract unless the price is fixed
0 reply
0 recast
0 reaction