EthereumLists's profile picture. Born to list data in the ethereum context (chains, tokens, 4bytes, contracts)

lists.eth

@EthereumLists

Born to list data in the ethereum context (chains, tokens, 4bytes, contracts)

Repost di lists.eth

I think emails or PRs should contain a warning if the content or code is AI generated. Really sad I was reading all this text. github.com/ethereum-lists…


You can just list things

you can just compile things



Repost di lists.eth

The chainId is 232.

The chainId is 232.

StaniKulechov's tweet image. The chainId is 232.


There is a very nice new open-source interface to the chain-list by @SimplrSh chainlist.simplr.sh


Don't use the 4byte db with the most signatures - select the one with the best data. Amount of signatures is not a metric you should use to determine the quality of the database! github.com/volsa/etherfac…


Another reason why you should not use/promote chainlist.org but use e.g. chainlist.wtf As the people that took over the site decided to have a separate source for RPCs you can get inconsistencies. This RPC does not belong to the chain .. 🤦‍♂️

EthereumLists's tweet image. Another reason why you should not use/promote chainlist.org but use e.g. chainlist.wtf
As the people that took over the site decided to have a separate source for RPCs you can get inconsistencies. This RPC does not belong to the chain ..
🤦‍♂️

Repost di lists.eth

the alpha leak was already on github 9 hours ago. funny to see @mr_ligi blocking and requesting proper json formatting from coinbase’s CEO @brian_armstrong PR, not something you see everyday 😅 github.com/ethereum-lists…


If you start a chain - make sure your chainID is not taken! We do not care at all if you did KYC, have good partners or are listed in some CEXes - listing 2 chains with the same chainID opens the risk for replay attacks! github.com/ethereum-lists…


More and more chains collide with their chainID This is not good as it opens the doors for replay attacks and also the reason we will only list one chain for one chainID. But we are changing the rules for collision management now: github.com/ethereum-lists…


Repost di lists.eth

Please use and recommend chainid.network or chainlist.wtf by @FrederikBolding instead of chainlist.org It has much more recent data, supports @WalletConnect and dark mode. Also none of the drama uncovered by this tweet

Also @gitcoin I find it a bit strange you invited chainlist.org to the round but not the underlying data @EthereumLists where is just one view on the data that fell in the hand of @DefiLlama in some weird action. See: github.com/antonnell/netw…



We *might* change our current collision policy from "Oldest Genesis" to - "First registered on ethereum-lists/chains" We currently have a bit of a messy situation with 2 colliding chains - and the oldest genesis can be problematic (also can be faked) Comments/Ideas welcome!


Loading...

Something went wrong.


Something went wrong.