Agave 4.2 off-chain compatibility#

Seesaw's maintained transaction and block readers opt into transaction version 1. Run the source and dependency contract before release:

pnpm audit:agave-42

The contract requires the Solana Kit dependency cohort to remain at 8.x or newer and rejects maxSupportedTransactionVersion: 0. Raw transaction consumers must retain canonical fixtures for legacy, v0, and v1 (0x81, message first, signatures last).

For v1 RPC responses, message.transactionConfig.priorityFee is the total fee in lamports. It is not a micro-lamport-per-compute-unit price and must not be multiplied by computeUnitLimit. Null configuration fields mean the sender did not set them. Legacy and v0 transaction construction continues to use Compute Budget instructions.

Slots establish ordering but are not a clock. User-facing age calculations use measured block/head timestamps, wall-clock response age, or an explicit operational estimate. They must not embed a fixed slot duration.

The repository currently has no reward-array parser, account-update completion latch, Token-2022 jsonParsed instruction/extension parser, Yellowstone client, or LaserStream client. Adding any such surface requires extending scripts/agave-42-readiness.mjs with the corresponding compatibility policy.

Release signoff#

Local checks prove source and fixture compatibility, not provider rollout. Before release, run a read-only staging capture against the target Agave 4.2 RPC provider containing a real version-1 transaction and record:

• provider and cluster genesis hash;
• transaction signature and observed slot;
• successful getTransaction/getBlock reads with maximum version 1;
• decoded version/configuration and fee-unit assertion;
• release commit.

Do not fall back to maximum version 0 when a provider returns JSON-RPC -32015; treat it as a provider compatibility failure.