Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

Paul Berg pfp
Paul Berg
@prberg
We need an EIP to expose the blockNumber at which a contract was deployed via a JSON-RPC method. Any EVM dev who's built a multichain indexer knows how painful it is to manually track down start blocks for contracts.
13 replies
31 recasts
205 reactions

eth_chainId pfp
eth_chainId
@4miin3
Thirdweb insight offer a REST API to get that data. https://playground.thirdweb.com/insight/transactions?path=/v1/transactions/%7BcontractAddress%7D Why serve it through RPC?
1 reply
0 recast
1 reaction

Haardik pfp
Haardik
@haardikkk
Do it!
0 reply
0 recast
3 reactions

Joaquim Verges pfp
Joaquim Verges
@joaquim
YES PLEASE
0 reply
0 recast
2 reactions

Darryl Yeo 🛠️ pfp
Darryl Yeo 🛠️
@darrylyeo
This would be soooo useful.
0 reply
0 recast
1 reaction

Erik⚡️ pfp
Erik⚡️
@ryk
It's not too bad-- but would definitely make it way easier if we had a standard for it. Love the idea!
0 reply
0 recast
1 reaction

Mo pfp
Mo
@meb
Yes please
0 reply
0 recast
1 reaction

0xqeew  pfp
0xqeew
@0xqeew
No lies can be a lot frustrating
0 reply
0 recast
1 reaction

Martinni pfp
Martinni
@martinni
This is a huge pain point. I’ve been thinking about doing similar for a long time. Chain observability is very tedious.
0 reply
0 recast
1 reaction

Lefteris Karapetsas pfp
Lefteris Karapetsas
@lefteris.eth
yes!!!!!
0 reply
0 recast
0 reaction

DegenFans 🔐 pfp
DegenFans 🔐
@degenfans
Also while reading locks it would be a great info the max current block… currently I query the latest block and then fetch from last time +1 to this.. unfortunately if the rpc is on a load balanced endpoint
0 reply
0 recast
1 reaction

Ape/rture pfp
Ape/rture
@aperture
@runninyeti.eth anything we can expose here? I know we run these queries all the time
1 reply
0 recast
0 reaction

Dung Nguyen pfp
Dung Nguyen
@dunghbc
Lfg
0 reply
0 recast
0 reaction

Cao Thiên Vũ pfp
Cao Thiên Vũ
@vucao9293
.
0 reply
0 recast
0 reaction