Deployed contract does not match the predicted address about thor

Yeah,
I know that the nonces supposed to be random but if we at least get any controls over this issue, we can handle our nonces locally to finally support vechain.

[libotony]

For CREATE you can calculate the contract address before sending the tx, take a look at

thor/thor/address.go

Lines 107 to 112 in bee753f

	func CreateContractAddress(txID Bytes32, clauseIndex uint32, creationCount uint32) Address {
	var b4_1, b4_2 [4]byte
	binary.BigEndian.PutUint32(b4_1[:], clauseIndex)
	binary.BigEndian.PutUint32(b4_2[:], creationCount)
	return BytesToAddress(crypto.Keccak256(txID[:], b4_1[:], b4_2[:]))
	}

you need txID, clauseIndex and creationCount. Regarding the creationCount, it's the overall contract creation count for one clause, so if you send a tx with one clause {to: null, data: <creation code>} then it should be 0. Please forgive me, it starts from 0 not 1
To generate the address you wanted, you need to change nonce in the tx then txID is generated and you will get the contract address. Regarding nonce it is a random number in tx which is different from ethereum's account nocne.

[libotony]

thor/vm/patch.go

Lines 19 to 20 in bee753f

	func CreateAddress2(b common.Address, salt [32]byte, inithash []byte) common.Address {
	return common.BytesToAddress(crypto.Keccak256([]byte{0xff}, b.Bytes(), salt[:], inithash)[12:])

CREATE2 is also available.

[aghamir]

Dear @libotony,

Thanks kindly for your response.

Regarding the creationCount, it's the overall contract creation count for one clause, so if you send a tx with one clause {to: null, data: <creation code>} then it should be 1.

We need to reach the exact same contract address in CREATE due to the fact that we provide exchanges contract wallets for their users(unless the same user address will not accessible in Vechain network and causes fund loss in recovery plans). However, the minimum amount of creationCount is 1 in your solution and our generated mother contract address has nonce on 0.

CREATE2 is OK, however, we must first deploy the same address mother with CREATE in Vechain.

Do you have any solution for nonce 0?

Regards,

[libotony]

We have a different tx-model than Ethereum. Take a look at the function signature:

// Ethereum
func CreateAddress(caller common.Address, nonce uint64) Address
// VeChain
func CreateContractAddress(txID Bytes32, clauseIndex uint32, creationCount uint32) Address

Regardless of the creationCount, you might not be able to create the same contract address using the same method of Ethereum. Luckily CREATE2 works.

And I took another look into the source code, creationCount starts from 0.

[aghamir]

Thanks a lot. I see the differences now. I'm not familiar with evm code and their effect on all nodes. Is it possible you add some other function like CREATELEGECY in your evm which act like ethereum one?

[libotony]

@aghamir I am afraid this can not be done, sorry for the inconvenience. Closing this issue, feel free to reopen or append comments.