docs(id): 2026-10-28 program investigations — TigerBeetle + Cloudflare Workers fit by dezren39 · Pull Request #2067 · developing-today/code

dezren39 · 2026-10-29T01:06:22Z

Adds the first two investigation reports of the 2026-10-28 ID platform expansion program (epic #2056), filed in doc/ following the repo's timestamped design-doc convention (pkgs/id/doc symlinks there):

TigerBeetle currency backend (for id: investigate: TigerBeetle — multi-currency ledgers, conversions, per-coin vs balance model, 3-node cluster topology #2040): dynamic ledgers yes; native conversions NO (cross-ledger transfers are forbidden — conversions are application-composed linked pairs, design id: design: conversion engine — linked transfer pairs, rate authorisation, liquidity accounts #2063); balance-only (no per-coin identity); cluster = all-replicas-running VSR, not 1-active+backups (topology decision id: investigate: TigerBeetle cluster topology decision — 3 vs 6 replicas, site placement, commit latency #2064); refund/revocation gap with a pending-transfer mitigation (id: design: refundable grants via pending transfers — Steam premium tokens voidable through the refund window #2065).
Cloudflare Workers fit map (for id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044): the hosted edition is an HTTP/WebSocket-shaped subset (no UDP in isolates, so no Iroh); per-user Durable Object + SQLite is the winning shape; D1-per-user capped at 50k databases; Google sub as the SSO key; custodial keys rejected.

These feed the currencies v1 synthesis (#2043) and the serverless edition v1 synthesis (#2046). Docs only; no code changes.

^{Need help on this PR? Tag @codesmith-bot with what you need.}

…e Workers fit First two investigation reports of the ID platform expansion program (epic #2056): TigerBeetle capability report for the currencies design (#2040) and the Cloudflare Workers/DO/SQLite fit map for the serverless edition (#2044). Filed under doc/ (the pkgs/id/doc symlink target).

coderabbitai · 2026-10-29T01:06:31Z

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 40 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: c216784a-6972-4e95-aa3e-8e9d246f2ca6

Commits

Reviewing files that changed from the base of the PR and between 0fda29d and 9995a56.

Files selected for processing: 2

doc/2026-10-28T23-34-14Z_investigation_cloudflare_workers_fit/2026-10-28T23-34-14Z_investigation_cloudflare_workers_fit.md
doc/2026-10-28T23-34-15Z_investigation_tigerbeetle_currency_backend/2026-10-28T23-34-15Z_investigation_tigerbeetle_currency_backend.md

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

chatgpt-codex-connector · 2026-10-29T01:06:33Z

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-29T04:00:43.675455Z	`9995a56`	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8bbefcab68

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-10-29T01:13:04Z

+- **UDP: there is no UDP socket API.** Iroh's transport is QUIC, and QUIC runs
+  over UDP; hole punching and Iroh relay (DERP-style) flows are likewise
+  UDP/QUIC-shaped. None of that can execute inside a Worker or Durable Object.


Evaluate relay-only Iroh before ruling out protocol compatibility

The lack of UDP rules out direct connections and hole punching, but not Iroh's relay transport. Iroh's official Wasm documentation describes browser peers that cannot send UDP and nevertheless communicate through relays, including an echo-server example. The repository also documents the WebSocket relay protocol in doc/2026-10-11T11-08-42Z_design_remaining_work/research-round2/cloudflare-workers/RESULTS.md. Workers compatibility and connection-lifetime costs still need investigation, but the UDP-only premise does not establish that an application-level HTTPS bridge is mandatory. Qualify the conclusion and assess the relay-only Wasm path separately.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-10-29T01:13:04Z

+   model issuance; a `credits_must_not_exceed_debits`-style constraint would
+   cap it. TigerBeetle does not pick for you.


Correct the constraint recommended for limiting issuance

For the issuer → recipient minting model defined here, issuance increases the issuer's debits. credits_must_not_exceed_debits therefore does not cap issuance; it constrains incoming credits instead, so arbitrarily large mint transfers would still pass that constraint. The Account reference specifies this direction explicitly. Describe a prefunded issuance account with debits_must_not_exceed_credits, or a separate supply-limit construction, rather than recommending the opposite flag as a supply cap.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-10-29T01:13:04Z

+- **Account closure exists but is narrow.** An account can be closed (via
+  `flags.closing_debit`/`closing_credit` pending transfers) once its net
+  balance is zeroed; a closed account "will reject further transfers, except


Separate account freezing from zero-balance closing entries

The zero-balance prerequisite incorrectly excludes a database-enforced freeze for funded accounts. The Transfer reference defines the closing flags as setting Account.flags.closed when a pending transfer succeeds, without requiring the existing balance to be zero; balancing the account is a separate operation in the closing-entry recipe. A zero-amount closing pending transfer can therefore freeze an account with funds and be voided to reopen it. Correct this distinction and the earlier claim that no freeze primitive exists, so the design does not unnecessarily rely exclusively on gateway-side freezes.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-10-29T01:13:04Z

+- Execution is single-threaded per object and requests to one object are
+  serialized, which is what makes the strong consistency cheap: no locks or
+  consensus are needed inside one user's store. For ID this matches the existing


Qualify the request-serialization guarantee across async calls

When a handler awaits an external operation such as fetch(), another request can execute on the same Durable Object and change its state; single-threaded execution does not serialize complete asynchronous handlers. Cloudflare's concurrency documentation explicitly distinguishes synchronous SQLite operations and storage input gates from external async calls that permit interleaving. The unconditional guarantee here could lead the proposed graph/journal or shared-world handlers to read state, await external work, and then commit updates against stale state. State that invariant-sensitive check/update sequences must remain synchronous or use explicit concurrency protection when spanning external awaits.

Useful? React with 👍 / 👎.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9995a56b2e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-10-29T04:00:41Z

+would be two records of the same event, linked by storing the ID-graph object
+ID in a transfer's `user_data_128` (128-bit, indexed) — the docs explicitly


Preserve the full graph ID in the reconciliation link

For the signed ID-graph events described here, the proposed direct link does not fit: pkgs/id/src/event_store/range.rs:36–37 defines event IDs as 32-byte BLAKE3 hashes, whereas TigerBeetle's user_data_128 holds only 16 bytes. Storing the full event ID in this field is therefore impossible, and truncating it would lose the reference needed to retrieve and verify the signed source. Specify a control-plane mapping from a 128-bit surrogate to the full hash, or another lossless representation, as part of the reconciliation design.

Useful? React with 👍 / 👎.

dezren39 requested a review from a team as a code owner October 29, 2026 01:06

dezren39 mentioned this pull request Oct 29, 2026

epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056

Open

3 tasks

chatgpt-codex-connector Bot reviewed Oct 29, 2026

View reviewed changes

github-actions Bot assigned dezren39 Oct 29, 2026

style: treefmt the two investigation reports (CI format-check)

9995a56

chatgpt-codex-connector Bot reviewed Oct 29, 2026

View reviewed changes

dezren39 merged commit 8124cc0 into main Oct 29, 2026
4 checks passed

dezren39 deleted the docs/id-program-investigations-2026-10-28 branch October 29, 2026 05:56

Navigation Menu

Repository navigation

docs(id): 2026-10-28 program investigations — TigerBeetle + Cloudflare Workers fit - #2067

docs(id): 2026-10-28 program investigations — TigerBeetle + Cloudflare Workers fit#2067
dezren39 merged 2 commits into
mainfrom
docs/id-program-investigations-2026-10-28

dezren39 commented Oct 29, 2026 •

edited by blacksmith-sh Bot

Loading

Uh oh!

coderabbitai Bot commented Oct 29, 2026 •

edited

Loading

Review limit reached

Uh oh!

chatgpt-codex-connector Bot commented Oct 29, 2026 •

edited

Loading

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Oct 29, 2026

Uh oh!

chatgpt-codex-connector Bot Oct 29, 2026

Uh oh!

chatgpt-codex-connector Bot Oct 29, 2026

Uh oh!

chatgpt-codex-connector Bot Oct 29, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Oct 29, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

		model issuance; a `credits_must_not_exceed_debits`-style constraint would
		cap it. TigerBeetle does not pick for you.

		would be two records of the same event, linked by storing the ID-graph object
		ID in a transfer's `user_data_128` (128-bit, indexed) — the docs explicitly

Conversation

dezren39 commented Oct 29, 2026 • edited by blacksmith-sh Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot commented Oct 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review limit reached

Uh oh!

chatgpt-codex-connector Bot commented Oct 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codex Review Summary

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Oct 29, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Oct 29, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Oct 29, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Oct 29, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Oct 29, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

dezren39 commented Oct 29, 2026 •

edited by blacksmith-sh Bot

Loading

coderabbitai Bot commented Oct 29, 2026 •

edited

Loading

chatgpt-codex-connector Bot commented Oct 29, 2026 •

edited

Loading