Support eth typed-tx via TX_CONTAINER encoding

[CoderZhi]

Summary

Mirrors the Go SDK PR iotex-antenna-go#113. Lets callers send Ethereum typed transactions — Legacy / AccessList (EIP-2930) / DynamicFee (EIP-1559) / Blob (EIP-4844) / SetCode (EIP-7702) — through the JS SDK using the TX_CONTAINER encoding. The signing path builds a go-ethereum-style Transaction via ethers v6, signs the hash with the existing elliptic secp256k1 keypair, serializes to raw bytes, and wraps them verbatim in iotextypes.TxContainer. The node decodes the raw tx with go-ethereum directly — no proto-field reconstruction.

Two commits:

1. 086b0af toolchain bump — typescript 3.6.2 → ~5.5, @types/node 11 → 20, and the four latent type errors the bump surfaces (Proxy handler name typing, crypto.Binary rename, catch-clause unknown). Isolated from the feature so the diff is easy to read.
2. 1ecb365 typed-tx feature — proto additions, signing path, caller wiring, and 32 unit tests.

What changed

Proto (additive only, no field-number conflicts with v0.7.1):

• New messages: TxContainer, AccessTuple, BlobTxSidecar, BlobTxData, SetCodeAuthorization
• New ActionCore fields: chainID, gasTipCap, gasFeeCap, blobTxData, accessList, txContainer (in oneof), txType, setCodeAuthList
• New top-level Encoding enum; new Action.encoding
• protogen/proto/types/action_pb.{js,d.ts} regenerated with the same protoc-gen-grpc-web toolchain

New code:

• src/action/typed-tx.ts — typed-tx builder, secp256k1 signer (via elliptic), extractEthTxSig, txContainerHash, ioAddressToEth
• src/action/envelop.ts — Envelop carries typed-tx fields; SealedEnvelop.sign dispatches to signTxContainer when txType > 0. For TX_CONTAINER actions, .hash() returns keccak256(raw)
• src/rpc-method/types.ts — IActionCore + IAction extended; toAction writes the new proto fields and short-circuits the oneof body setters when txContainer is set (otherwise they'd clear the slot)
• Public API: TransferRequest, ContractRequest, ExecuteContractRequest, MethodExecuteParameter, Contract.deploy all accept typed-tx options via a shared TypedTxOptions interface
• Iotx.sendTransfer / deployContract / executeContract forward the new options through to TransferMethod / ExecutionMethod

Dependencies:

• Adds ethers ^6.16.0 as a runtime dep — the underlying Transaction class is the canonical reference for typed-tx wire format. Signing still goes through the existing elliptic-based secp256k1; ethers is used for serialization and parsing only.

Tests

32 ava cases in src/action/__test__/typed-tx.test.ts:

• Signature recovery (5) — signed tx parses back to TEST_ADDR for all five tx types. This is the load-bearing crypto check: any sign-key/digest/V-byte bug fails here.
• V-byte normalization (2) — legacy and typed both produce 27/28 (covers both branches of extractEthTxSig)
• toAction proto plumbing (4) — access-list, dynamic-fee, blob, setcode all confirm encoding == 128 + hasTxcontainer() + non-empty raw bytes (blob asserts size > 1000 to confirm sidecar made it in)
• End-to-end caller routing (3) — TransferMethod.execute with txType=2 and ExecutionMethod.execute with txType=1 both produce TX_CONTAINER actions on the wire; without txType, the iotex protobuf path is preserved
• Edge cases (4) — legacy contract creation (to==null) recovers signer; sidecar length mismatch throws; bad bech32 throws; non-iotex prefix throws
• Determinism (1) — signing the same envelop twice yields byte-identical rawEthTx, ethTxHash, and signature
• Baseline (13) — per-type round-trips + validation tests

Note on test runner: the repo's pinned ava 2.2.0 is broken on modern Node (esm package fails to load). All 32 cases were verified passing via a standalone ts-node runner during development. Bumping ava is out of scope for this PR — see the test plan checklist below.

Test plan

• tsc --noEmit clean across 308 files
• 32 typed-tx test cases pass via standalone ts-node runner during development
• Follow-up: bump ava to a version that runs on modern Node so npm test works end-to-end
• Live integration test against a testnet node that accepts TX_CONTAINER actions (cross-verifies the wire format matches iotex-core's expectations)
• Bundle size / webpack-cli compat check after dep bump

Known gaps

• The pinned ava 2.2.0 doesn't run on modern Node; new tests can't be exercised by npm test without an ava bump. Separate PR worth doing.
• No fixture-based cross-verification against iotex-core's wire format. If iotex-core changes the V-byte or access-list-hex convention, the JS tests still pass; only a live node catches that.
• Bundled fix typo commit (0854fb7, 2021) was already on local master and is included here — it's a real fix (checkingPending → checkPending in IGetActionsByHashRequest); flagging since it's older history riding along with this PR.

🤖 Generated with Claude Code