Changelog
What moved
Releases, findings and ecosystem shifts, dated as they happened. Follow along by RSS — new entries land whenever something actually moves, not on a content schedule.
-
Live data now refreshes every 4 hours
The data sweep behind this site — repository stats and tags from the GitHub API, all watched standards proposals, and the chain numbers from both independent indexers — now runs every 4 hours instead of daily. A merged proposal flips its badge within hours; a new release shows the same shift it ships. The heavyweight verification stays on its daily cadence: build-page commands re-proven in fresh containers and community contracts recompiled against the current toolchain, once a day as before. Every "refreshed daily" claim on the site has been updated to match reality, in all 12 languages where it appears.
-
KCC-20 is in Last Call — the token standard is one review window from Final
The day arrived: the pull request advancing KCC-20 merged on 2026-10-07, and the standard's own file now reads Status: Last Call — the final review window (typically 14 days, per KCC-0) before Final. KCC-1 and KCC-2 are in Last Call alongside it. The same day, the first official Argent KCC-20 reference implementation merged in argent-lang/kcc20-reference — a token actor and an admin-keyless public mint, the kind of independent implementation KCC-0 asks for on the road to Final. This site's KCC-20 badge moves from draft to last-call across every page and all 12 languages; per the house rule, production still waits for a tagged release. If this window completes without normative changes, the next changelog entry here is the big one.
-
KCC-1 and KCC-2 reach Last Call; the Studio hand-off goes one-click
Verified at source: KCC-1 (the covenant definition and ABI) and KCC-2 (authority schemes) both advanced to Last Call on 2026-10-01 — the final review stage before Final. KCC-20's own Last Call PR remains open with an approving review. Newly watched: a draft mobile wallet session-and-pairing API, companion territory to KCC-12. And a site milestone: SilverScript Studio shipped its import endpoint, so the covenant designer's 'Open in Studio' button now delivers your contract straight into their editor — pre-loaded, credited, with their reminder to review keys before deploying. Design to IDE in one click, nothing installed.
-
KCC-20's Last Call approved; the metadata question is answered; rusty-kaspa v2.1.0
Three moves, all verified at source. (1) The pull request advancing KCC-20 to Last Call received an approving review on 2026-09-28 — merge looks imminent, and this site's status badge flips the day it lands. (2) The covenant-metadata question is settled: KCC-21 was closed as superseded on 2026-09-25, making KCC-23 (Metadata JSON) the track — with a follow-up planned to define name, ticker, decimals and image fields. (3) rusty-kaspa v2.1.0 (released 2026-09-22, already on the repo board): network and P2P hardening, an arithmetic-safety audit, and the ZK proof-script tooling extracted into a standalone kaspa-txscript-zk-sdk crate — a building block for proof-verified covenants. Also now watched daily: the first Argent KCC-20 reference implementation, opened in the official argent-lang/kcc20-reference repo.
-
SilverScript Studio: a browser IDE for covenants
Off the under-review list and onto the board: silverscriptstudio.com is a zero-install Silverscript IDE with annotated snippets, eight covenant wizards, an AI assistant, and one-key compilation with a hex inspector — we exercised the compiler in-browser and watched the welcome contract compile to 56 bytes. Its deploy, deposit and withdraw flows are the site's own claims (not yet independently tested), and no public source repository is named — the card says so. It was unreachable when first suggested on 2026-09-24 and has been back up since.
-
KCC-0 is Final — the first finalized Kaspa convention — and KCC-20 moves toward Last Call
Verified at source: KCC-0, the meta-document defining how Kaspa conventions are proposed and finalized, reached Status: Final on 2026-09-21 — the first KCC to complete the process. A new pull request proposes advancing KCC-20 itself to Last Call alongside KCC-0 compliance; this site's daily proposals watcher now tracks it, together with a new proposal domain: reputation, bond and identity registry covenants. Also new: the footer now links the Kas Smiths forum (where these standards are debated — its public content is mirrored daily in Manyfestation's kas-smiths-public-archive on GitHub) and the public Kaspa Core R&D Telegram. One suggestion is parked honestly: silverscriptstudio.com was unreachable on every check today and joins the under-review list until it answers.
-
Official docs restructured: a programmability decision guide, and "Based Apps" named
docs.kaspa.org shipped a new Toccata Programmability section — a pick-your-layer guide organised around one question: do you need concurrent state mutation? It names four tracks: Covenants (buildable today, Silverscript as the main reference, with a documented ~300 KB script budget shared between contract code and state), "Based Apps" (new name: one Rust app in a managed environment with built-in accounts and shared-state concurrency — explicitly in construction), Full vProgs (reframed as the future direction for composition between apps, not a current option), and Inline ZK (the specialist per-action-proof path). This site's component links, decision guide and glossary now reflect the new structure. The section is brand new and still settling — one page currently carries an unfinished inline editor's note — so expect it to evolve.
-
KasStacker speaks 12 languages
The homepage and the full 6-stop tour — including the interactive break-a-covenant lesson and every checkpoint quiz — are now available in Spanish, German, French, Portuguese, Turkish, Dutch, Chinese, Indonesian, Russian, Japanese and Korean, via the new language menu in the header. The language set covers every locale kaspa.org itself supports, plus Turkish and Dutch. Technical pages (build, status, compare, ecosystem) remain English-first for now, and the menu is honest about that: on an untranslated page it takes you to your language's home.
-
Corrections from the first independent review (STP-KAS)
STP-KAS published an independent claim-and-product review of this site, and it was right about a lot. Shipped the same day: (1) the homepage counter now says what it counts — covenants created all time (mostly completed KasWare vault lifecycles), with 'alive now' (created minus burned, ~700) and a template breakdown alongside; (2) vProgs was wrongly listed as having no public repo — kaspanet/vprogs is public and in early development, and is now on the status board with live GitHub data; (3) KCC-20's maturity badge dropped from production to draft — the standard has no tagged release, and the legend now states the rule: production requires one (mainnet adoption is shown separately, from the feed); (4) the try-it lesson no longer implies a network broadcast — it runs in your browser against the contract's logic, and now says so (live testnet-10 broadcast: coming); (5) ecosystem cards replaced the bare 'reviewed' stamp with typed, dated checks — compiled in CI, on-chain proof, source public, homepage visited — and a card with only a homepage visit says 'listed, not verified', per the now-public LISTING_CHECKLIST.md; (6) the status page gained an indexer-agreement table comparing kcc20.info against kascov.io daily, with units labelled where they differ. Review: github.com/STP-KAS/three-x-reviews.
-
Five new ways in: design a covenant, spot the rug, and more
The learn section gained a covenant design wizard — answer three plain questions and real Silverscript assembles itself, with all eight possible contracts compiled against silverc v1.0.0 and re-proven daily in CI. Alongside it: a spot-the-rug game about what covenants actually prevent, a five-years-in-one-slider timeline, a live covenant counter on the homepage, and a downloadable tour certificate you can timestamp on Kaspa itself via KasProof.
-
KCC-12 proposed: one wallet API for every Kaspa dApp
A new draft KCC proposes a common browser-wallet provider API — deliberately close to Ethereum's EIP-1193/6963 model (announce/request provider events, request({method}), familiar error codes) — so one dApp can talk to any Kaspa wallet without per-wallet integrations. This week's revision added PSKB support: partially-signed transaction bundles for multisig and covenant flows where a wallet signs only the inputs it controls. Caveats that matter: it is a draft under active review (16 review comments in its first two days), no wallet has adopted it yet, and it overlaps a separate KIP-12 wallet-discovery effort — which standard wallets converge on is the open question. This site now tracks the proposal daily on the status page.
-
State of the stack: live adoption numbers
The status page now leads with chain data refreshed daily from the keyless kcc20.info indexer — covenants created, state transitions, live KCC-20 tokens, and a 30-day activity chart. Plus: every trading venue, explorer and indexer now has its own ecosystem card.
-
kcc20-live: the first verified third-party Argent contract
A KCC-20 token written in Argent (.ag) by a third party builds cleanly with argentc in this site's CI — the first community Argent contract we have been able to verify. Argent itself still has no tagged release.
-
Silverscript v1.0.0 quietly broke most pre-1.0 community contracts
Compile-checking every known community contract library against v1.0.0 in fresh containers: OpenSilver (21 of 25 contracts), kosign, K100bet and kasmelt-snapshot — all written pre-release — no longer parse. Stateless contract styles survived; stateful ones did not. These repos are on the under-review list until they update, and the weekly re-check will notice the moment one does.
-
KCC-20's draft specification has a home: kccs.dev
Kaspa Calls for Conventions (kaspanet/kccs) hosts the draft fungible-token covenant specification, the covenant ABI and authority schemes. The KCC-20 component page now links it, and the spec repo is watched by the daily status data.
-
Silverscript v1.0.0 released — no external audit named
The covenant language hit its first tagged release, adding Groth16 and RISC Zero proof verifiers that lower to the KIP-16 opcode live on mainnet. Its own security policy still calls the project experimental, and no external audit has been named — maturity on this site remains pre-audit.
-
Toccata's inline ZK verification live on mainnet
KIP-16's OpZkPrecompile went live: Kaspa script can verify zero-knowledge proofs directly, meaning a covenant can require a valid proof before coins move.