lists.eth (@EthereumLists) profile picture

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

Joined June 2021
Photo by lists.eth (@EthereumLists)Photo by lists.eth (@EthereumLists)Photo by lists.eth (@EthereumLists)Photo by lists.eth (@EthereumLists)Photo by lists.eth (@EthereumLists)Photo by lists.eth (@EthereumLists)Photo by lists.eth (@EthereumLists)Photo by lists.eth (@EthereumLists)Photo by lists.eth (@EthereumLists)Photo by lists.eth (@EthereumLists)
Just merged the ACiD (@pHbalanceweb3) chain to @EthereumLists - did not dig deep - so not an endorsement of this chain - but the pitch made me smile ;-)
1
1
5
243
You can just list things
you can just compile things
3
511
lists.eth retweeted
The chainId is 232.
44
63
13
564
54,713
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/etherface/iโ€ฆ
1
1
8
849
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 .. ๐Ÿคฆโ€โ™‚๏ธ
1
1
4
705
We will likely stop using 4byte.directory by @pipermerriam as a source of 4bytes. The spam is just too much now. E.g. see this ERC20 4byte: 4byte.directory/signatures/?โ€ฆ and managing the ignore.lst is a time-consuming game of whack-a-mole. Guess we will only use @SourcifyEth ..
1
1
1
427
.. as source in the future. It is harder to spam there as you actually need to deploy contracts and not just do a API call. See the current ignore.lst for a reference on how bad the situation is: github.com/ethereum-lists/4bโ€ฆ
1
162
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/chโ€ฆ
1
3
319
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/chโ€ฆ
2
4
322
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 teapawt.net/thegrifft/status/16173โ€ฆ
Replying to @mr_ligi @web3beach
Also @gitcoin I find it a bit strange you invited chainlist.org to the round but not the underlying data @EthereumLists where chainlist.org is just one view on the data that fell in the hand of @DefiLlama in some weird action. See: github.com/antonnell/networkโ€ฆ
2
1
11
1,111