Upstream Compatibility

Upstream Compatibility#

• Latest supported @solana/kit version: 8.3.0
• This Dart port tracks upstream APIs and behavior through v8.3.0.

Version parity#

Each row pairs a published solana_kit release with the upstream @solana/kit version it tracks. Use the row that matches your Dart dependency to know which upstream release its APIs and behavior correspond to. The solana_kit version is the workspace compatibility marker; the other packages release independently.

Upstream client pins#

The upstream clients and IDLs the current release was generated and verified against. Tag pins are fixed; branch and commit pins are moving or unversioned upstream refs (clone:repos materializes them under .repos/, and the short revision records the last checked commit).

Upstream refs by release#

Which upstream ref each solana_kit release was generated and verified against. Cell values are the ref recorded in config/reference-repos.json at that release; — means the repository was not tracked yet. Branch pins include the short revision that was last checked, so they can be compared across releases even though the branch itself moves.

Solana program clients

Solana Foundation programs

Metaplex programs

Wallet and SDK references

Parity status

Executable parity currently covers stable, CI-cheap surfaces: address/signature validation, derivation, transaction message compilation, wire serialization, and selected invalid-input error codes.

Live RPC timing, subscription transport behavior, mobile platform adapters, and other intentionally documented divergences remain tracked separately rather than being implied by the current harness.

Validation Workflow#

• Keep .repos/kit updated (clone:repos).
• Run upstream:check to verify tracked compatibility metadata remains internally consistent.
• Run upstream:parity to install the tracked @solana/kit release in a local cache, generate runtime fixtures, and compare selected Dart behaviors against upstream.
• Record intentional deviations and migration notes.
• Re-run benchmarks after major upstream alignment changes.

Current Executable Parity Scope#

The first harness focuses on stable, high-signal surfaces that are cheap to run in CI:

• address validation and coercion semantics
• address encoding and derivation helpers
• signature validation/coercion semantics
• signer deduplication and assertion context parity
• transaction message v1 compilation and wire serialization
• transaction message v0 compilation and wire serialization
• transaction size limits (legacy, v0, v1)
• transaction message size limit version-aware helpers
• error-code parity for selected invalid inputs
• JSON-RPC error BigInt code support
• sendTransaction preflight context defaults
• simulateTransaction metadata defaults
• compute-unit helpers (set/limit estimation)
• SOL/Lamports type helpers
• reactive store and slot-tracking subscription helpers
• abortable websocket subscription helpers
• key-pair writing and grinding helpers
• fixed-point binary/decimal arithmetic
• vote-account Agave v3 parsed types
• client/plugin composition helpers
• instruction-plan version-aware size compatibility

The harness intentionally does not yet cover live RPC behavior, subscription transport timing, mobile-wallet platform adapters, Helius-specific extensions, or stricter Dart-only transaction-construction invariants such as requiring an explicit lifetime before compilation. Those remain tracked separately in the roadmap and issue set.

Versioning Guidance#

When upstream introduces breaking API behavior, prefer explicit compatibility notes and migration docs over silent behavior changes.