Add an extension to set contract address

[Kalina-Todorova]

We have the following case: we are aiming to have contract deployment is 100% compatible with the Ethereum workflow, but in our case the contract address is not based on sender address and nonce but rather it's the next available id (Hedera).

From which arises the need for us to set the contract address on contract deployment. Is there an option to add an extension which would allow us to do so?

https://docs.ethers.io/v5/api/utils/address/#utils--contract-addresses

ethers.utils.getContractAddress( transaction )
from + nonce

For context: https://github.com/hashgraph/hedera-json-rpc-relay/issues/193

Code Example

No response

[ricmoo]

This isn’t probably going to happen in the near future, but I will move it to “ideas”, as it could be something added for sub-classes to override.

In hedera, are contract addresses synchronous? As in, they can be computed from the transaction? Or does it require fetching chain data?

[Kalina-Todorova]

Thanks Richard,

It requires fetching chain data - in Hedera addresses are allocated sequentially by the network itself and it's not dependent on the transaction args / account properties.

We would appreciate it if we can try adding the option for sub-classes to override, this will work for us.

[natanasow]

@ricmoo
Improvement proposal: Add a precomputeAddress flag on contract deployment

• add the flag on ContractFactory.deploy({ precomputeAddress: true }) - default true
• if the flag has been set to true - do nothing in BaseContract constructor, all should work as it is now
• if the flag has been set to false - do not precompute the address in BaseContract constructor and define the address from receipt.contractAddress as BaseContract.address in Contract._deployed method

Implementing this flag, we are making ethersjs 100% compatible with the Hedera EVM, also unintentionally ethersjs will support one more ecosystem out-of-the-box and a new flow of users will come.

Big note here, the current users will not be affected by these changes, and their workflow will be the same as it has always been.