You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ots: inject isOtsCommit on esplora-mode /api/tx/:txid via proxy
In production (BACKEND=esplora), bitcoin.routes.ts gates off
getTransaction, so /api/tx/<txid> is served by the electrs proxy and
attachIsOtsCommit never runs. Frontend's lazy probe in OtsKnowledgeService
rescues UX, but the wire-strip-fill was dead code on prod.
Buffer the small (~1-3 KB) tx-detail JSON inside the proxy, mutate via
attachIsOtsCommit, re-emit with corrected content-length. Other paths
(/tx/:txid/hex, /tx/:txid/status, non-200s, non-JSON bodies, POST,
/api/v1/*) stream through untouched. 6 new regression tests pin the
behaviour.
Also tighten Cache-Control on /resources/config.js + customize.js via a
Cloudflare Pages _headers file -- max-age=0, must-revalidate -- so the
window.__env GIT_COMMIT_HASH refreshes on revalidation instead of
lingering for 4 hours.
Updates ORDPOOL-FLAGS-ARCHITECTURE.md \xc2\xa74 to reflect the actual
strip-fill site on prod.
"note": "Floor for .github/workflows/test-count-floor-backend.yml. Count of passing tests from the single jest config (node). Only an ordpool core maintainer is authorised to lower this number; every other change that reduces test count is treated as an accident and rejected. To raise the floor after legitimately adding tests, bump this value and commit. See also workspace CLAUDE.md, HARD RULE 'Never delete a passing test without explicit permission'."
0 commit comments