Closed daithi-coombes closed 4 years ago
Am wondering if it might be related to this issue: https://github.com/celo-org/celo-blockchain/pull/298
found it in @celo/contractkit
: https://www.npmjs.com/package/@celo/contractkit#sending-custom-transactions
Celo transaction object is not the same as Ethereum's. There are three new fields present:
feeCurrency (address of the ERC20 contract to use to pay for gas and the gateway fee)
gatewayFeeRecipient (coinbase address of the full serving the light client's trasactions)
gatewayFee (value paid to the gateway fee recipient, denominated in the fee currency)
This means that using web3.eth.sendTransaction or myContract.methods.transfer().send() should be avoided.
golang solution is to use celo's implementation in this package here: https://github.com/celo-org/celo-blockchain/blob/master/accounts/abi/bind/base.go
closing.
Expected Behavior
Singed transaction would be processed successfully. Log in
geth --verbosity 3
would show transaction.Current Behavior
Receiving the error:
First I tried using the
go-ethereum bindings
created runningtruffle compile
against themono-repo/packages/protocol
repo. I then usedabigen
to create the go bindings. Calling anything on a contract returned the above error. (more info on implementation used commented here https://github.com/ethereum/go-ethereum/issues/16290#issuecomment-579622015)Next I tried singing the transactions in vanilla go without the bindings created from
abigen
.Steps to Reproduce Behavior
Call the above function
Logs
No logs on node
System information
Run
geth version