Open allenday opened 1 year ago
I'll see if I can find some time this week to work on this, should in theory be fairly simple as they're 1:1 clones of Etherscan with only a different stylesheet. Anyways, on top of my head I can think of two approaches to implement this:
polygonscan_contract
and bscscan_contract
table with the same structure as etherscan_contract
ornetwork
enum field into etherscan_contract
which can either by ethereum
, polygon
or binance
; also make the address
and network
fields into an unique tuple to avoid collisions. Any thoughts?
Edit: Also does #9 apply here?
it's also a different API key
RE #9 we have Polygon in BQ but not yet BNBChain
identical API to etherscan