lists.eth retweeted
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 ;-)
lists.eth retweeted
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/chโฆ
There is a very nice new open-source interface to the chain-list by @SimplrSh
chainlist.simplr.sh
More L3s popping up:
github.com/ethereum-lists/chโฆ
when the first L4 ?-)
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โฆ
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 ..
๐คฆโโ๏ธ
lists.eth retweeted
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/chโฆ
lists.eth retweeted
Not a fan of CEXes and hence also CoinBase - but having a CEO creating PRs is a cool thing to see.
github.com/ethereum-lists/chโฆ
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
..
.. 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โฆ
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โฆ
Fighting spam in the 4byte directory:
github.com/ethereum-lists/4bโฆ
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โฆ
lists.eth retweeted
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โฆ












