CHANGELOG.md

Changelog

All notable changes to this repository are documented here.

The format is based on Keep a Changelog.

[2026-07-23] - Metadata examples on Quasar 0.1.0 (vendored quasar-metadata)

Added

• tokens/quasar-metadata: a vendored copy of the quasar-metadata crate from blueshift-gg/quasar rev 623bb70f (the last revision that shipped it), adapted to compile against the 0.1.0 quasar-lang API (RentAccess type parameter on AccountInit::init, try_find_program_address rename, Seed import from quasar_lang::cpi, unsafe set_data_len). Upstream removed the crate before 0.1.0 with no replacement; vendoring it lets the Metaplex-metadata examples ride the same release pin as everything else. Provenance and local changes are documented in the crate's README and CHANGELOG.

Changed

• tokens/token-minter, tokens/nft-minter, and tokens/nft-operations now migrate to the 0.1.0-release pin (be60fca) like every other example, depending on the vendored crate via quasar-metadata = { path = "../quasar-metadata" }. This supersedes the previous day's "not migrated" limitation: all 53 Quasar examples are now on 0.1.0.
• quasar.yml drops the legacy-metadata-examples job and .github/.ghaignore is empty again — the whole matrix builds with the one 0.1.0 CLI.

[2026-07-22] - Quasar 0.1.0

Changed

• Migrated 50 of the 53 Quasar examples to the Quasar 0.1.0-release line, pinned by rev (be60fca) because crates.io still hosts 0.0.0 placeholders for quasar-lang/quasar-cli. Per project: quasar-lang/quasar-spl repinned (the four previously floating examples — basics/pyth and the three compression examples — are now pinned too); Quasar.toml rewritten to the 0.1.0 schema ([testing] command, [clients] targets; the old [toolchain]/testing.language/testing.rust/clients.languages keys are hard errors in 0.1.0); the idl-build feature and "lib" crate-type added for the new IDL build; and tests fully rewritten from the direct QuasarSVM harness (QuasarSvm::new().with_program(...), include_bytes!, assert_success) to the new quasar-test fixture harness (#[quasar_test], Wallet/Mint/TokenAccount fixtures, crate::cpi instruction builders, Outcome assertions). The standalone quasar-svm git dev-dependency is gone — quasar-test pulls the published quasar-svm 0.1.0 from crates.io — and generated-client path dev-dependencies were dropped in favor of crate::cpi (a path dev-dependency to a not-yet-generated crate now breaks the required cargo generate-lockfile).
• quasar.yml CI installs the 0.1.0 CLI (--rev be60fca), runs cargo generate-lockfile before quasar build (the 0.1.0 IDL step runs cargo metadata --locked), and builds the three unmigrated examples in a separate legacy-metadata-examples job with the pre-0.1.0 CLI.
• Compute-unit assertions were dropped from the migrated tests pending recalibration under 0.1.0 (correct values are unknowable until the suite first runs on the new line).

Known limitations

• tokens/token-minter, tokens/nft-minter, and tokens/nft-operations stay on the pre-0.1.0 pins (quasar 623bb70 / quasar-svm cb7565d): they depend on quasar-metadata, which was removed upstream before 0.1.0 with no replacement. They are listed in .github/.ghaignore and built by the legacy CI job.

[2026-07-11] - Discoverability and FAQ pass

Fixed

• Quasar CI broke repo-wide when quasar-svm's HEAD (c63afd2, "sbpf v3") moved to solana-program-runtime 4.1 / solana-address 2.6, which cannot co-resolve with the pinned quasar-lang rev 623bb70 (needs solana-address <2.6). Pinned quasar-svm to cb7565d (the last rev before the bump) in every Quasar example that pins quasar-lang, matching the pin prop-amm already carried. basics/pyth and the three compression Quasar examples float both dependencies and are left as-is.

Added

• FAQ sections, written as the questions people actually ask, in the root README and every finance example's anchor/ README.
• llms.txt at the repository root: a summary and link manifest for LLM crawlers and answer engines.
• docs/example-readme-template.md, the example-README template that CONTRIBUTING.md referenced but which did not exist. It documents the H1 convention and the definition-first opener.

Changed

• Every finance example README now titles itself # Solana <Example> (<Framework>) (e.g. # Solana Escrow (Anchor)) and opens with a self-contained definition that names Solana, so each example page stands alone in search results.
• The root README states its toolchain currency explicitly (Anchor 1.1, LiteSVM, July 2026) with a pointer to this changelog.
• CONTRIBUTING.md style rules now include the README H1 naming convention and the no-em-dash rule.

[2026-07-10] - Failed fundraisers can be retired

Added

• token-fundraiser (Anchor): a close_fundraiser instruction handler. The Fundraiser PDA is derived from the maker's key alone, so a failed raise used to lock its maker out of ever raising again. The maker can now retire a failed fundraiser (after the deadline, target missed, all contributions refunded), sweeping any direct vault donations to themselves and recovering both rent deposits, then initialize a fresh fundraiser. New error variant RefundsOutstanding.
• token-fundraiser (Anchor): tests for both contribution caps (test_contribute_above_cap_fails, test_cumulative_contributions_above_cap_fail) and for every branch of the close path (before deadline, target met, refunds outstanding, donation sweep, and close-then-raise-again).

[2026-06-30] - Anchor 1.1.2

Changed

• Upgraded every Anchor program from anchor-lang/anchor-spl 1.0.0 to the latest stable 1.1.2, and bumped the Anchor CLI used by anchor.yml CI to match (anchor-version: 1.1.2).

Fixed

• anchor.yml built no projects when .ghaignore was empty: find … | grep -vE "$ignore_pattern" treated the empty pattern as "match everything" and dropped the whole list, so the workflow passed without building anything. Guarded the filter (as native.yml, pinocchio.yml and solana-asm.yml already do).
• vault-strategy and perpetual-futures LiteSVM tests loaded their sibling mock program's .so with include_bytes!, which is evaluated at compile time. Anchor's IDL build compiles the tests before that sibling .so is built, so the build failed. They now read the sibling .so at runtime with std::fs::read, matching the existing cross-program-invocation/hand test.

[2026-06-12] - Rust + LiteSVM tests everywhere

Changed

• All native, Pinocchio, and ASM examples are now tested exclusively with Rust + LiteSVM. The web3.js v1 / solana-bankrun / ts-mocha TypeScript test suites (which duplicated existing Rust tests) were removed, along with their package.json, pnpm-lock.yaml, and tsconfig.json files and the ts/ client directories.
• Rust tests now load the program binary from the workspace target/deploy/ (built with cargo build-sbf --manifest-path=./program/Cargo.toml) instead of per-project tests/fixtures directories. Committed foreign-program fixtures (e.g. mpl_token_metadata.so) stay where they were.
• ASM examples standardized on sbpf build's default deploy/ output directory; their inline LiteSVM tests load from there.
• tools/shank-and-codama now generates a Rust client (@codama/renderers-rust) instead of a TypeScript one, wrapped in the car-rental-service-client crate, and its tests are Rust + LiteSVM under program/tests/.
• transfer-hook/block-list gained a Rust + LiteSVM lifecycle test (program/tests/) driving the program through its Codama-generated Rust SDK; the mocha/web3.js test was removed. Its package.json now only covers SDK generation.
• CI (native.yml, pinocchio.yml, solana-asm.yml) no longer installs Node/pnpm; it builds with cargo build-sbf (or sbpf build) and tests with cargo test.

Added

• basics/hello-solana/pinocchio Rust + LiteSVM test (it previously had only a TypeScript test).

[2026-04-08] - Quicknode fork modernization (Mike MacCana)

Mike MacCana led the Quicknode fork of the Solana Foundation program examples from late 2025. The first commits on this repository lineage are dated 8 April 2026; the summary below covers that work through the initial merge.

What changed (high level)

Toolchain and frameworks. The tree had accumulated examples from several years of Solana development (including Anchor releases going back to the ~0.26 era in 2022 and many intermediate versions). The fork brought the Anchor examples up to Anchor 1.0.0 stable (from 1.0.0-rc.5), refreshed Agave/Solana CLI pins, standardized on pnpm, and added parallel implementations in Quasar, Pinocchio, Native Rust, and ASM where applicable. Token-2022 examples were renamed to token-extensions.

Testing. Replaced the old pattern of local validators, Bankrun, and scattered TypeScript anchor test flows with LiteSVM in-process tests for most Anchor programs - matching current Anchor defaults (cargo test wired through Anchor.toml / pnpm test). Fixed broken or flaky tests across Native, Pinocchio, and Anchor; added missing harnesses (e.g. block-list Pinocchio). CI was reworked for a repo this size: path filtering, caching, matrix sharding, and reliable detection of framework roots.

Programs and layout. Broke large monolithic lib.rs files into instruction handler modules; adopted InitSpace and explicit PDA bumps instead of magic account sizes; corrected several logic bugs (escrow, token swap invariant, counter authority checks, compression Bubblegum program id, and more). Expanded finance and token-extension coverage; reorganized transfer-hook examples (including block-list under Pinocchio).

Documentation. Rewrote the root README (framework badges, clearer example blurbs, ASM links), ran a style and truth audit on READMEs, and linked canonical Solana terminology on first mention. Added this changelog, CONTRIBUTING.md (aligned with LiteSVM testing), README templates, per-example Anchor and Quasar READMEs, fixed Husky for GUI git clients, removed unused maintainer scripts (sync-package-json, cicd.sh, local-validator helpers for the allow/block-list UI), dropped the orphan tokens/spl-token-minter/ tree, and removed legacy root package.json dependencies (web3.js, Bankrun, chai).

Removed / deferred. Dropped duplicate or WIP trees (duplicate block-list Pinocchio copy, Quasar metadata example blocked on sol_realloc, root yarn.lock). Some examples remain excluded from CI via .ghaignore until they build cleanly again (compression, escrow, pyth, and others - see that file for the live list).

Before June 2026

There was no changelog before June 2026. Older history lives in git only.