Glossary
Changelog
Pre-launch
Section
Glossary
Documentation category
Type
Guide
Technical reference
Summary
Documentation changelog, a record of significant updates, additions, and corrections to the SwssChain developer documentation.
SDK Update Notice

SWSS SDK v2.1 is deploying across the ecosystem. API signatures may change during this period. Ensure your integration uses the latest schema from SWSS DevHub.

Article Content

Documentation Changelog

This page records significant updates to the SwssChain developer documentation. Protocol changes, SDK releases, and new documentation sections are listed in reverse chronological order. For the SDK release changelog specifically, refer to the SDK Reference section.

2026: Q2

May 2026

  • New: Complete developer documentation published across all 12 categories: Start Here, Settlement Layer, Consensus Protocol SCP v3.2.2, Deed Transaction Standard, SWSS Coin, Developer Reference, API Reference, SDK Reference, Products, Testnet, Security, and Glossary.
  • New: API Reference section covering all SwssChain JSON-RPC endpoints with curl examples and JSON response schemas.
  • New: SDK Reference section covering JavaScript/TypeScript, Python, and Go SDKs with full code examples.
  • New: Security section covering smart contract security guidelines, key management best practices, vulnerability reporting, and audit programme.
  • New: Glossary covering all SwssChain terminology, acronyms, Deed type quick reference, and documentation changelog.

April 2026

  • New: Deed Transaction Standard documentation: five Deed types, settlement lifecycle, Finality Certificate structure, and on-chain verification.
  • New: SWSS Coin section: fixed supply model, Settlement Combustion Model mechanics (TSL, ERRP, SGP), staking guide, and compliance framework.
  • New: Developer Reference section: Hardhat setup, Foundry integration, ethers.js v6, viem v2, wagmi v2, OpenZeppelin contracts, and event log querying.

March 2026

  • New: Settlement Layer documentation: SwssChain architecture, settlement flow diagrams, the Deed Transaction Standard introduction, and Settlement Combustion Model overview.
  • New: SCP v3.2.2 documentation: four pillar architecture (SAPE, DSA, PCA, BFTFA), Byzantine fault tolerance guarantee, Finality Certificate production, and why SCP cannot be replicated without the full pillar set.
  • New: Testnet documentation: testnet overview, connecting guide, faucet instructions, explorer guide, and issue reporting process.

Upcoming Documentation

The following documentation additions are planned for Q3 2026, aligned with the scheduled activation of new protocol features:

  • Compute Deed integration guide: activated Q3 2026.
  • AI Agent Deed integration guide: activated Q4 2026.
  • ERRP distribution mechanics and staking reward calculation: activated Q3 2026.
  • SWSS Bridge integration guide for BNB Chain and Polygon: activated Q3 2026.
  • SWSS Governance on-chain voting guide: following governance framework activation.
  • Audit report publications: as audit rounds complete throughout 2026.

Documentation Contribution

The SwssChain developer documentation is maintained by the SwssChain core team. Corrections, clarifications, and suggestions from the developer community are welcomed via the SWSS DevHub issue tracker, categorised under "Documentation".

To report a documentation error:

  1. Navigate to the specific page containing the error.
  2. Click "Report an issue with this page" in the page footer.
  3. Describe the error and, where applicable, the correct information.

Contributors whose corrections are accepted will be credited in the documentation changelog. Corrections that affect protocol behaviour descriptions are reviewed by the SwssChain engineering team before publication.

Version Tracking

Each documentation page displays a "Last Updated" timestamp in the page footer. Major documentation sections are versioned in alignment with the protocol version they describe. When a protocol upgrade changes behaviour documented on an existing page, the page is updated and a changelog entry is added here.

Historical versions of the documentation are not publicly hosted, the documentation always reflects the current protocol version. Where protocol changes are backward-incompatible, migration notes are published alongside the updated documentation.