Support alternative transaction signing methods

[CDDelta]

This PR adds support for signing transactions with the secp256k1 ECDSA and ed25519 EdDSA schemes. This change is entirely backwards compatible with the existing signing method, the process for signing transactions with RSA remains the same.

Transactions can now include an optional signature_type field which can be PS256_65537, ES256K or Ed25519 to specify their signing scheme. Transactions using the new schemes should include the signature_type field as the last leaf used to generate the Merkle root used as the transaction signature message. This should not be done for the pre-existing scheme PS256_65537.

Transactions signed with secp256k1 ECDSA must specify a compressed owner (public key). Uncompressed owners are rejected to avoid confusion with a single EC wallet having two possible addresses.

signature_type field values correspond to those defined in the IANA Jose assignment database and IETF RFC8410 with an extension for PS256 to also define the RSA public exponent.

[CDDelta]

Have some questions here.

[CDDelta]

@ldmberman are there any tests that test out tx inclusion e2e ie. tx creation, /tx endpoint posting, block inclusion? Could you point me to them if there are? I think it would be good to have them updated with the new signature types as well.

[ldmberman]

@CDDelta there are lots of e2e tests in the codebase, one thing I would do is make ar_wallet:new/0 return an ECDSA or EDDSA wallet and see if the tests pass, but not necessarily commit the change. To name a few places, there are complex e2e tests in ar_multiple_txs_per_wallet_tests.erl and ar_data_sync_tests.erl. It might make sense to update these to use a mix of wallets. Also, perhaps, check ar_node_tests, e.g., wallet_transaction_test_.

[CDDelta]

@CDDelta there are lots of e2e tests in the codebase, one thing I would do is make ar_wallet:new/0 return an ECDSA or EDDSA wallet and see if the tests pass, but not necessarily commit the change. To name a few places, there are complex e2e tests in ar_multiple_txs_per_wallet_tests.erl and ar_data_sync_tests.erl. It might make sense to update these to use a mix of wallets. Also, perhaps, check ar_node_tests, e.g., wallet_transaction_test_.

ar_node_tests was just what I was looking for. I believe everything is in line now. Could you have a look again? :)

Unfortunately, the tests don't all pass here since master itself is broken but it looks like the areas I touched didn't break anything.

[DougAnderson444]

Hello Team, wondering what the status of this PR is? Would love to see ed25519 keys used to sign Arweave transactions.