Adding deploymentBlocknumber property for BaseContract

[tornadocontrib]

Ethers Version

latest

Search Terms

No response

Describe the Problem

Would be great to have this as an alternative approach for deploymentTransaction . deploymentTransaction would be useful to fetch deployment block number required to fetch historic contract events until Geth starts to prune old transactions ( transactions more than a year ). Since almost every public nodes now have a pruned transaction state it would make sense if we could add the deploymentBlock or deploymentBlockNumber property that could be used for fetching historic events.

Code Snippet

No response

Contract ABI

No response

Errors

No response

Environment

No response

Environment (Other)

No response

[ricmoo]

This unfortunately is not data that is indexed. There is no way (outside of adding additional data; such as how Etherscan does) to determine the block at which a contract was deployed.

The deploymentTransaction is only available on Contract deployed directly using the ContractFactory, in which case this information is available only because it was deployed by the current VM instance.

Moving to discussion. :)

[tornadocontrib]

@ricmoo Yes, what I meant is to add an optional properties that could be added manually, like baseContract.deploymentBlock = block. Wrapping the BaseContract would be very painful and wouldn't work with typechain instances. So I thought adding it for type compatibility would be great.