Skip to content

v1.0.0-rc.5

Pre-release
Pre-release

Choose a tag to compare

@legendko legendko released this 20 Oct 13:00
· 3 commits to main since this release

v1.0.0-rc.5 moves the reference implementation onto FORA protocol v1.1.0, so every request it signs or verifies is a Web Bot Auth signature. It adds the publisher console, where publishers register their business and their sites, and the Exchange can now bill in more than one currency.

Upgrading from v1.0.0-rc.4

rc.5 does not interoperate with rc.4, and some rc.4 data does not carry over.

  • Protocol v1.1.0 (hard cut). rc.4 was built against an untagged protocol revision. v1.1.0 changes request signing in both directions, so the Exchange, the Broker, the Identity Service, every publisher edge and every agent upgrade together. Agent software built on the FORA SDKs needs v1.1.0.
  • Signed key directories. A v1.1.0 verifier takes a key only from a directory signed by that key. An edge that serves the publisher's own keys (WBA_KEYS_JSON) must also serve the pre-signed directory (WBA_SIGNED_DIRECTORY_JSON). Without it, the directory goes out unsigned.
  • Publisher sites are registered. The Exchange applies 18 database migrations when it starts (000034 to 000051). Migration 000036 removes signing_scheme and cloudfront_key_pair_id from the seat (fora.tenants) and does not copy them anywhere, because which publisher owns a site is decided at registration. Register each site again through the console after upgrading. The seat's domain now names the Exchange's own hostname.
  • Billing settings. EXCHANGE_BILLING_LEDGER takes a comma-separated list of ISO 4217 numeric codes, one ledger each (978 for EUR, 840 for USD). EXCHANGE_DEFAULT_AGENT_CREDIT takes CODE=AMOUNT pairs, such as EUR=100. The old single number stops the Exchange at boot.
  • Ledger balances do not carry over. Every TigerBeetle account id now includes its currency, so rc.5 does not find the accounts rc.4 created. Fund agents again after upgrading.
  • The console needs a PostgreSQL database of its own (CONSOLE_DSN) and two Exchange settings: EXCHANGE_CONSOLE_WELLKNOWN_URL and EXCHANGE_CATALOG_CONTRIBUTOR_HOST. Every other setting new to the existing services is optional, and none of their documented settings was removed.

Highlights

  • Web Bot Auth signing. The Identity Service, the Broker and the Exchange sign and verify every FORA request as Web Bot Auth. fora-sign-directory pre-signs a key directory for a host that serves it as a static file.
  • Publisher console (new service and image). Publishers sign in through a login provider separate from the one developers use. They register their business and sites, download the files to deploy, and confirm that each site is theirs. A dashboard shows an overview, transactions with in-browser verification, the catalog and income. Design: ADR-026.
  • Automatic catalog import. fora-import builds and refreshes each listing's catalog from the sitemap recorded at registration.
  • One signed offer per licensing term. Discovery returns one offer for each term the publisher offers, in the publisher's order, each with its own price and offer_id. Before, only the first term could be bought.
  • Several currencies. The Exchange keeps one TigerBeetle ledger per currency, and money never moves between them. Balances are reported per currency.
  • Refused purchases are recorded. The Exchange writes each refused purchase to an append-only journal. Design: ADR-027.
  • MCP tools. fora_discover accepts search_filters. fora_execute returns only the URLs when called with embed_content: false. fora_status reports one balance per currency.
  • Sign-in. Every authorization response carries the iss parameter (RFC 9207).
  • Operations. Each service takes its own log level: EXCHANGE_LOG_LEVEL, BROKER_LOG_LEVEL, IDENTITY_LOG_LEVEL and CONSOLE_LOG_LEVEL. A publisher edge can limit the paths it licenses with LICENSED_PATHS_JSON.
  • Testing. An obligation registry drives the end-to-end suite, and every protocol request in it goes through the protocol SDKs. Design: ADR-028. Each e2e run brings up its own stack on its own network, with no host ports, so runs never collide.
  • Demo content. Playable music tracks offered under alternative licences (the fora-music-v1 profile), plus new essays and articles.

Container images

Built from this tag for linux/amd64. The console image is new in this release.

docker pull ghcr.io/fora-protocol/exchange:1.0.0-rc.5
docker pull ghcr.io/fora-protocol/broker:1.0.0-rc.5
docker pull ghcr.io/fora-protocol/identity:1.0.0-rc.5
docker pull ghcr.io/fora-protocol/console:1.0.0-rc.5
Image Digest
exchange sha256:362b9c1b1b7392687bb6eb94ea0a4e398e203c4bdc14cf677536ac3e9838e78d
broker sha256:2cb6a282b37eee1faa077a67a319d0fb1514de4d9723806af9bd3203c170ded2
identity sha256:de5f5fdc70a0d5dc254440337c660f159bbc3d47eda1bc92606854bb157dbc58
console sha256:55fcba0fb8efbcb80727cde444323eb66a369cae9392723dc5d0a8622bb1cec6

Each service's DEPLOYMENT.md and CONFIGURATION.md say how to run it: exchange, broker, identity, console.

Protocol

Pinned to FORA protocol v1.1.0 everywhere: the Go module github.com/FORA-Protocol/protocol v1.1.0 for the services, @fora-protocol/sdk 1.1.0 for the edge, and fora-protocol-sdk 1.1.0 for the end-to-end tests.

Full Changelog: v1.0.0-rc.4...v1.0.0-rc.5