Hi, We are a crypto business and we use your product in a couple of internal processes.
We are having some problems with a recent version of Trezor Connect, specifically with a message regarding an ethereum transaction nonce being to big (more than 64 bits). This used to work, but now we are getting the following message: ‘nonce cannot exceed MAX_UINT64’.
Because of the way we use ethereum transactions for this process, we usually use much bigger nonces than that (20 bytes or more). Since the ethereum protocol allows up to 32 bytes for nonces in transactions not to be over 32 bytes, and it works correctly in other libraries we use, is there a reason connect limits this value to 64 bits?
Not being able to sign these transactions means we will need to derive the keys from the mnemonics and expose them to use them directly, thus breaking this process and the keys security, we would like to avoid that.
Thanks!