Upgrade to 1.0

crypto-aio 1.0 settles the last parts of the API that 0.1.0 left open. Most applications change nothing; read the sections that match what you use. Every change is also in the changelog, and from 1.0 on, semver applies.

Operations that 0.1.0 stored are read as they are: no data migration is needed, and an idempotency key repeated after the upgrade finds its Operation.

Everyone

• Node.js 22.12 or later. Earlier 22.x releases are no longer supported (Solana already needed 22.12).
• TX_UNEVIDENCED. A transfer whose transaction executed but shows no transfer to the recipient now fails with TX_UNEVIDENCED, not TX_REVERTED: an EVM or Tron token that logged no Transfer to the recipient, or TON jettons sent to a wallet the master does not name. Value may have moved, so treat it like an unknown outcome: check the chain before paying again. If your code handles TX_REVERTED as "safe to pay again", it no longer sees these cases there, which is the point; add a branch for TX_UNEVIDENCED that routes to a person (Errors).
• Proofs wait for every configured endpoint's share. A proof needs proofQuorum endpoints (2) capped by the endpoints you configured, even while some are down: with two endpoints and one down, final waits for it. Configure three or more endpoints, from independent providers, so one outage leaves enough. To keep 0.1.0's behavior, where the one endpoint left proves alone, set transport: { degradedProofs: true }.
• Endpoint health reads unknown until its height is known. getNetworkStatus() and bc.ready() no longer count an endpoint as healthy from its identity alone: ready() now fails with PROVIDER_UNAVAILABLE when no endpoint has answered its height probe.

If you send EVM or Tron tokens

• Deprecated Tether-style tokens are refused. A token whose contract answers deprecated() with true fails before signing with ASSET_RESOLUTION: send to the upgraded contract instead, by its address or a registered asset.
• A gas-limit bound. EVM transfers, replacements and cancels refuse a gas limit above maxGasLimit (2^24 by default) with INVALID_INTENT. Raise it in the chain's or the handle's options if you send to contracts that need more.
• library: 'web3' is deprecated and warns once per process; switch to ethers before 2.0.

If you scan Bitcoin

The scanner reads each block's raw bytes (GET /block/:hash/raw) and the previous transactions of its inputs (GET /tx/:txid/hex), so your Esplora service must serve both (Blockstream's and mempool.space's do). Scan with filter.addresses: an unfiltered scan reads one previous transaction per distinct parent outside the block, thousands for a full mainnet block. details.vout[].type is named from the script, as Blockstream electrs names it.

If you sign Bitcoin p2tr with a custody signer

A wallet whose signer does not declare the scheme its address type signs with is refused with CONFIG_INVALID when it resolves, not at signing: a p2tr wallet needs a signer that declares secp256k1-schnorr, and the other address types secp256k1-ecdsa.

If you read RecoveryReport

aio.operations.recover() reports unresent: Operations whose wallet no longer resolves are now checked on chain, and counted there rather than in failed. Restore the wallet and recover again to resend them.

If your idempotency keys are unusual text

An idempotency key or a scanner's cursorKey with U+0000 or a lone surrogate (half of a UTF-16 pair) is now refused. Keys made of ordinary text are unaffected.

If you write a durable store

Run the contract suites from crypto-aio/testing again: they now check two more fields.

• Operation records carry format (OPERATION_FORMAT, 1). Store it like every other field. A record without one, as 0.1.0 wrote them, reads as format 1, so existing rows need no migration.
• Observations carry failure ('reverted' or 'unevidenced') on a failed Attempt. Store it, and clear it when an observation is replaced without it, as you do reason.

During a rolling upgrade, a process never reads a record of a newer format: it throws RECORD_FORMAT_UNSUPPORTED, and its workers leave such records to newer processes (upgrades).

If you construct handles or containers yourself

• Blockchain's constructor is private, and its internal protected methods are gone from the type declarations: create handles with aio.blockchain() or Blockchain.create(). Subclassing a handle was never supported.
• CryptoAio's constructor has one signature, new CryptoAio(options?).

If you write a chain family plugin

The driver port is final for 1.0 (Write a chain family plugin):

• observe and includedFinal report what failed with failure: set 'unevidenced' when a transaction executed but shows no transfer to the recipient.
• BuildContext.decimals gives the decimals the core scaled the amounts with. A driver whose transaction signs decimals must refuse a mismatch with what the chain says.
• ReplacementPolicy.comparePrice (optional) ranks two transactions of one slot by price, for repeat cancels.