Richard Moore

This change would require a major version change, so I don't think it's really feasible. It isn't really even a word, so the rule for how it should be suffixed...

The properties need to be all marked as `?`, since other chains won't have them. There is definitely a need to allow some way to allow more expressive and network-specific...

Can you include a demo of how you are using the decrypt functions that generated the invalid key? I use the following code and get the correct (non-prefixed) values: ```javascript...

I don’t think these changes make sense for the repo. Looks somewhat like spam.

Thanks! I'll get these into the next minor bump.

Thanks! I'll get these chains tested and added asap. :)

For signing though (see [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559)) (which is why unsignedSerialized returns): > The signature_y_parity, signature_r, signature_s elements of this transaction represent a secp256k1 signature over keccak256(0x02 || rlp([chain_id, nonce, max_priority_fee_per_gas, max_fee_per_gas,...

Do you have a link to the project repo? Should be easy to modify it to accept either a standard unsigned tx or the non-standard serialized form they use now;...

I have a fix coming out for this soon. In the mean time, if you `npm install @types/node` it should resolve this.

If someone has resolved the v6 issues, please contact me too, so I can include instructions. I’m considering a dedicated rn package too, if people are interested.