Project: Ledger API v2 Rollout · Date: Jun 2, 2026 · Attendees: Alex Chen, Priya Natarajan, Marcus Webb, Yuki Tanaka, Sam Okafor
Goals
Replace the legacy v1 ledger service with a horizontally-scalable double-entry implementation that supports multi-currency settlement, exposes a versioned REST + gRPC surface, and unblocks the new Treasury and Payouts workstreams. Target GA is June 19, 2026.
Discussion topics
- Cutover plan for the 14 internal services currently on v1
- SLA contract: 99.99% on writes, p99 < 80ms
- Data backfill strategy for in-flight transactions during cutover
- On-call rotation handoff between Platform and Payments
Milestones
| Milestone | Owner | Target | Status |
|---|---|---|---|
| Schema freeze | Marcus Webb | May 22 | Done |
| Load testing complete | Priya Natarajan | Jun 1 | In progress |
| Cutover dry-run | Yuki Tanaka | Jun 10 | Not started |
| GA Launch | Alex Chen | Jun 19 | At risk |
| Decommission v1 | Sam Okafor | Jul 31 | Not started |
PN
Priya NatarajanNow
Flagging a potential blocker for GA: last night's load test (8k RPS sustained) hit an intermittent race condition in the double-entry write path — two concurrent transfers occasionally commit against the same ledger row before the second read sees the first write, leaving balances off by the smaller amount. Only repros above ~6k RPS so canary missed it. Patch in flight but needs a schema-level lock change + re-run of the conformance suite. Realistically puts the Jun 19 GA at risk by 5–8 days. Can we get this triaged?
Action items
- Priya: share full load-test report by EOD
- Marcus: spike on row-level lock alternative
- Alex: log the GA risk and notify steering committee