1.98.4 (2025-07-31)

Bug Fixes

• Add Cost Units (Transaction Cost) (#3750) (c26c13b)

1.98.3 (2025-07-31)

Reverts

• Revert "chore: Add costUnits to transaction classes (#3748)" (#3749) (3d0e82a)

1.98.2 (2025-04-24)

Bug Fixes

• update base-x to 3.0.11 in lockfile (#3731) (6f265af)

1.98.1 (2025-04-22)

Bug Fixes

• patch bigint-buffer (#3727) (d3dc5d5)

1.98.0 (2024-12-16)

Features

• Agave v2 RPC: replace getRecentBlockhash with getLatestBlockhash (#3419) (8ea27fc)

1.97.0 (2024-12-16)

Features

• agave v2 rpc: replace getConfirmedTransaction with getTransaction (#3418) (a805cb9)

1.96.0 (2024-12-16)

Features

• Agave v2 RPC: replace getConfirmedBlock with getBlock (#3417) (60e39a6)

1.95.8 (2024-12-03)

Earlier today, a publish-access account was compromised for @solana/web3.js, a JavaScript library that is commonly used by Solana dapps. This allowed an attacker to publish unauthorized and malicious packages that were modified, allowing them to steal private key material and drain funds from dapps, like bots, that handle private keys directly. This issue should not affect non-custodial wallets, as they generally do not expose private keys during transactions. This is not an issue with the Solana protocol itself, but with a specific JavaScript client library and only appears to affect projects that directly handle private keys and that updated within the window of 3:20pm UTC and 8:25pm UTC on Tuesday, December 2, 2024.

These two unauthorized versions (1.95.6 and 1.95.7) were caught within hours and have since been unpublished.

We are asking all Solana app developers to upgrade to version 1.95.8. Developers pinned to latest should also upgrade to 1.95.8.

Developers that suspect they might be compromised should rotate any suspect authority keys, including multisigs, program authorities, server keypairs, and so on.

1.95.5 (2024-11-20)

Bug Fixes

• added programId field in TokenBalance type (#3592) (526ce5f)

v2.0.0 (2024-11-07)

Today we have dropped the Release Candidate label from @solana/web3.js v2.0.0. We now recommend it for general use.

Read more in this blog post.