Releases and compatibility
How this documentation, the open-source Bloxchain Protocol, the npm packages and the Bloxchain Platform line up, which versions the pages on this site describe, and what changed and when.
Versions and compatibility
Bloxchain Platform
The Platform at bloxchain.app ships continuously. There is no numbered public release; features may appear behind the Alpha · Testnet · Local-first badge before they are documented here, and this documentation is updated to match the shipped app.
What the Platform looks like today: Platform guide
What is planned: Roadmap
Documentation changes: Changelog on this page
Protocol and SDK (open source)
The Protocol repository is the source of truth for versions. Releases are tagged on GitHub and the npm packages are published from the same tree.
Release notes and tags
Package version
sdk/typescript/package.json at the pinned commit
Solidity version and build settings
foundry.toml in the repository
License
MPL-2.0. See License and terms
Audit status
npm packages and version alignment
@bloxchain/sdk
TypeScript clients, meta-transaction helpers, engine mirrors
1.0.0 (tag sdk-v1.0.0)
@bloxchain/contracts
ABIs and artifacts for the Protocol contracts
1.0.0 (tag contracts-v1.0.0)
Install both packages at the same release as the contracts you deploy or import. A mismatch between ABI and deployed bytecode is the most common cause of decode errors in custom integrations. See SDK setup and Production readiness.
Official deployments
The Platform's Deploy account dialog uses the official factory, BasicFactory, which mints a BasicAccount. The official addresses ship in @bloxchain/contracts (1.2.0) as official-deployed-addresses.json, the published address catalog. Read them from that file rather than copying them into code or environment variables. They are listed once, with every other number and default, on Limits and defaults. Verify them on a block explorer before using them from your own code.
The Sepolia developer toolkit (the CopyBlox factory and the AccountBlox template) is listed in the same file. It is Sepolia only and is not the default Platform path. The Platform runs on Sepolia, chain 11155111. Ethereum mainnet is coming soon. See Supported networks.
Documentation site
Source: bloxchain-docs on GitHub.
Platform, Guides, Developers, Security and Resources pages are written here.
Protocol pages under Protocol are vendored from the Protocol repository at a pinned commit and are not edited on this site.
Protocol documentation pin
Upstream
https://github.com/PracticalParticle/Bloxchain-Protocol.git
Pinned commit
Tag at pin
contracts-v1.0.0
Published as
protocol/*.md on this site
Every GitHub link on this site that points into the Protocol repository uses this commit, so the code you read matches the pages you read. When the pin advances, the Protocol section and this table are updated together and the change is recorded in the Changelog below.
Changelog
Documentation and product notes, newest first.
2026-10-10: Official mint is BasicFactory
The Platform's Deploy account dialog and the SDK mint through the official factory, BasicFactory, which clones a BasicAccount. CopyBlox and AccountBlox are the Sepolia developer toolkit, not the default path.
Official addresses now come from the published address catalog in
@bloxchain/contracts(official-deployed-addresses.json). Limits and defaults and Deploy the Protocol list them, and Supported networks lists the catalog networks.The owner is the wallet that sends the deploy. Deploy from a regular wallet (EOA). BasicAccount accepts a time lock of 1 day to 90 days.
2026-09-14: Consistency pass and a limits reference
Added Limits and defaults: every cap, default and official address in one place.
Sign-in now reads the same everywhere: sign in if you have early access, otherwise join the waitlist from the same dialog. The Free path needs no account and is open to everyone.
Plans are named, never priced. Pricing is shown at checkout or on request; Enterprise is contact us.
Maturity and audit wording standardised: the Platform runs on Sepolia today, Ethereum mainnet is coming soon, and the audit covers the Protocol core framework only.
The site home names the four audiences (individual users, organizations, builders and developers, AI agents) and points each at its entry page.
2026-09-13: Documentation remade for the current Platform
New navigation: Introduction, Getting started, Platform guide, Guides, Developers, Protocol, Security, Resources.
All Platform pages rewritten for Discover, Accounts and the in-account rail (Overview, Assets, Approvals, History, On-chain access, Policies).
Screenshots added for every Platform page and major dialog.
Terminology aligned with the app: Bloxchain Platform, smart account, execution paths, gates, allowlists, signed files.
Stale pages removed, including the previous per-tab workspace, transaction and settings pages and the separate Resources overview and Community pages (community links now live on Support and community).
Resources refreshed: FAQ, Glossary, Troubleshooting, Roadmap, License and terms.
2026-07-02: Protocol link normalization
SDK and Protocol reading links point to the Protocol section on this site rather than to files in the GitHub repository.
GitHub links for deploy, audits, LICENSE and SECURITY use the pinned commit (
contracts-v1.0.0).The Protocol section adds a source repository hub; the link sanitizer fixes upstream-only links in vendored pages.
2026-07-02: Pre-publish hardening
Removed private package references from public developer guides.
Stripped legacy redirects from the unpublished site.
Linked the Nethermind NM_0828 audit report on Audit status.
Added a Protocol navigation entry for state abstraction versus account abstraction.
2026-06: Production readiness and GitBook structure
Added Production readiness, a mainnet checklist for the Protocol, the Platform and the SDK.
Established the top-level sections and vendored the Protocol pages from the Protocol repository with a sync script and pin.
Submit documentation corrections through bloxchain-docs issues.
Related
Last updated
Was this helpful?