Repository navigation
v1.0.0
v1.0.0 is the first release of the FORA reference implementation that is not a release candidate. It moves onto FORA protocol v1.2.0, lets an Exchange sell a licensing term only to subscribers who prove it with a verified delegation chain, and leaves a publisher's discovery file where the publisher keeps it: on their own site. The publisher console now takes a new publisher through four steps and saves their work as they go.
Upgrading from v1.0.0-rc.5
- Protocol v1.2.0. Request signing does not change, so clients built on the v1.1.0 SDKs keep working. What changes is the delegation chain in
Requester.delegation: it must follow the v1.2.0 delegation profile, andDelegation.tokenis at most 32768 bytes. Move agents and other clients to the v1.2.0 SDKs. - The edge no longer answers
/.well-known/fora.jsonor/rsl.txt. It passes both addresses through to the publisher's origin, for every client. Before you deploy this release's edge, serve the discovery file from the origin (thefora.jsonthe publisher console gives you), and the RSL file if you have one. The edge no longer readsPROVIDER,EXCHANGES_JSON,CATALOG_CONTRIBUTORS_JSONorRSL_BODY: a deployment that still sets them starts and ignores them. The domain-verification route/.well-known/fora-verify/<token>and its settingACME_TOKENS_JSONare removed. - Terraform. The
cloudflare-edgemodule no longer takesprovider_domain,exchanges_json,rsl_body,acme_tokens_jsonorcatalog_contributors_json: remove them from the module block. Theedgestack drops the last four; itsprovider_domainstays and names the hostname the Worker fronts.build-lambda-edge.shtakes the publisher's hostname as a second argument. - Exchange. It applies one migration when it starts,
000052, which adds the tablefora.subscription_records. No setting is removed and none becomes required.EXCHANGE_BOOT_FIXTURE_FILEis new and optional.EXCHANGE_BILLING_TB_ID_NAMESPACEis read only by the end-to-end build; a production build refuses to start when it is set. - Console. The edge package the console hands out no longer carries the discovery file. A publisher downloads
fora.jsonand serves it from their own site.
Highlights
- Subscription-gated terms. A licensing term that carries one concrete
subscription:scope is sold only to an agent that proves the subscription with the holder-bound delegation chain inRequester.delegation. The chain must verify under the root keys of the subscription record that owns the scope, be bound to the key that signed the request, and cover the term. Any failure denies that item withDENIAL_REASON_DELEGATION_INVALID, with no transaction and no charge, and stating the scope inRequester.scopesgrants nothing. At discovery, only a query the agent sends to the Exchange itself can see a gated term; a query a Broker sends for the agent does not show it. The Broker forwardsRequester.delegationto every Exchange it asks, and a catalog push is refused for a term with two subscription scopes or a wildcard one. The records live in the new tablefora.subscription_records. This release creates them only through the end-to-end build's control service and has no administrative route for them yet. The scope rule is in ADR-014. - The discovery file lives on the publisher's site. The edge passes
/.well-known/fora.jsonand/rsl.txtthrough to the origin, so the file the publisher serves is the one every agent and Exchange reads. Editing it is how a publisher changes which Exchanges sell their pages and who may add pages to the catalogue. The console's check on Connect your site asks for the file the way an AI agent does: a site that refuses agents at that address is not verified, and the console says why. The demo and staging stacks serve each demo publisher's documents from its origin as well. - Publisher console onboarding. A new account goes through four steps: Your business, Your domain, Your terms and Connect your site. The business name is asked once, before the first domain, and cannot be left for later; every later domain takes only the three domain steps. The domain is saved on the first step's Next and the terms on the second step's Next. Finish later returns to My domains, and Finish setup reopens a domain on Your terms when no terms were chosen, and on Connect your site otherwise. Connect your site has two tasks, done in either order: serve your discovery file, and install the package on your CDN. The console checks both every 15 seconds and verifies the domain once both pass. An account with no domain sees an empty My domains with one Add domain button. The Cloudflare steps run
npx wrangler loginbeforenpx wrangler deployand say they need Node.js 22 or newer, and every price reads "per fetch". Design: ADR-026, amendments of 2026-10-28 and 2026-10-29. - Exchange boot fixture.
EXCHANGE_BOOT_FIXTURE_FILEnames a YAML file that declares the seats, publishers, sites and listings a deployment starts with. At every start the Exchange creates the declared rows that are not stored yet and changes nothing that is; a file it cannot read or apply stops the start. Design: ADR-029. - A lighter, stricter end-to-end suite. One TigerBeetle cluster serves every test Exchange, each with its own ledger-id namespace, one nginx serves every test key directory, and health checks poll quickly only while a service starts. The stack needs less than half the memory it did. Every test signs as an agent of its own, each Exchange starts from a boot fixture instead of database writes, and the harness builds its requests from the protocol's generated models and sends them through the SDKs in strict mode. ADR-028 is accepted. The real-AWS acceptance suite, which checked a CloudFront RSA path that no stack deploys, is retired.
- Terraform. The CloudFront edge module's Lambda@Edge role allows
logs:CreateLogGroupon the log-group ARN and the log-stream actions on the log-stream ARN, in two statements, as CloudWatch Logs requires.
Container images
Built from this tag for linux/amd64.
docker pull ghcr.io/fora-protocol/exchange:1.0.0
docker pull ghcr.io/fora-protocol/broker:1.0.0
docker pull ghcr.io/fora-protocol/identity:1.0.0
docker pull ghcr.io/fora-protocol/console:1.0.0
| Image | Digest |
|---|---|
exchange |
sha256:ed8984992c4cc85269a34349f1235e488774d394eede0ea1df77b307eebb09f1 |
broker |
sha256:bd6a3cf96b8092267bac98229116a1b27f18f00de2714e6b648bdb9117306471 |
identity |
sha256:ee10ee1f5317485f34e0005a04bd965b68690f3a510b8faafbf515aa095b6580 |
console |
sha256:9fcd9a142fd43eb6ad797f0caa7d58cfa3a41ccfc64377856b10c50d3b0a2e76 |
Each service's DEPLOYMENT.md and CONFIGURATION.md say how to run it: exchange, broker, identity, console.
Protocol
Pinned to FORA protocol v1.2.0 everywhere: the Go module github.com/FORA-Protocol/protocol v1.2.0 for the services, @fora-protocol/sdk 1.2.0 for the edge, and fora-protocol-sdk 1.2.0 with the fora-protocol 1.2.0 models for the end-to-end tests.
Full Changelog: v1.0.0-rc.5...v1.0.0