Content
@
https://warpcast.com/~/channel/six
0 reply
0 recast
0 reaction
Chris Carlson
@chrislarsc.eth
One of the things I like about ERC-721/1155 is tokenURI. I own a specific token and it directly references the stuff it represents. All interfaces (wallets, dApps) support this relationship so when I look at what I own it shows the “stuff” Erc-20 is “just a token” though. These assets show up in my wallet under “Crypto” while the other stuff is organized under the NFT tab. @zora has co-opted Erc-20 and simply added “content”:{} to the contractURI. This isn't part of the standard though: https://eips.ethereum.org/EIPS/eip-7572 Where’s the EIP to propose this change? It feels cabal-like if @jacob @jessepollak @mikedemarais.eth @dwr.eth just “decide” that UIs will support this change (assuming Coinbase wallet, rainbow, and warplet make this update, which it seems like they will). Does this weaken Ethereum if the defacto application "leaders" are making changes now without consulting the wider community and proposing new standards? https://warpcast.com/jessepollak/0x6b8d4cb7
4 replies
1 recast
9 reactions
𝙗𝙡𝙖𝙣𝙠
@blankspace
> additional metadata addition permissionless and experimental systems but for composability reasons ofc there should be a standard for it > frontends clearly there are relationships there and things were likely discussed - frontends are not decentralized to put it simply > weaken Ethereum they are coordinating within their means imo, if we wait for everything to become a standard before experimenting with it, i think many things wouldn't come to fruition in the end, the market will decide whether they like it or not and there will be backlash if they don't (those frontends/people take on this risk)
1 reply
0 recast
4 reactions
Chris Carlson
@chrislarsc.eth
good take, thx
1 reply
0 recast
1 reaction
