2026-10-18 20:14 UTC
release
The project takes its name: Infrabond
Infrabond; its token will be $IBOND. Contracts, addresses and the API are unchanged. The SDK claim message now reads "Infrabond claim" (older signatures are still accepted); the new SDK sha256 is on this page.
/sdk/bond.mjs2026-10-18 20:12 UTC
compensation
Epoch 3 of bond 3: 0 customers compensated
0.000000 USDG to customers, 0.007397 USDG to the reserve.
0x9adc...66f12026-10-18 20:12 UTC
settle
Epoch 3 of bond 3 settled with a slash
118 failed probes of 340, 11.7% slashed, 0.007397 USDG to compensation.
0xb33a...39412026-10-18 20:12 UTC
compensation
Epoch 3 of bond 2: 0 customers compensated
0.000000 USDG to customers, 0.010547 USDG to the reserve.
0x1f93...58142026-10-18 20:11 UTC
settle
Epoch 3 of bond 2 settled with a slash
340 failed probes of 340, 25% slashed, 0.010547 USDG to compensation.
0xf9f0...2f262026-10-18 20:00 UTC
release
A privacy layer
Compensation can now be paid to a one-time payout address. The payer binds it to the payment through the EIP-3009 nonce it signs, the publisher keeps the link to itself, and the leaves, the published documents and the claims name the payout address only. The relayer submits the claim, so the payout address needs no gas. Operators can bond a sealed service: its URL is encrypted to the prober in the browser, ProbeLog records a commitment, and the board shows the commitment with the measurements. Probe records now carry a hash of each response; the response itself is never stored. No contract changed: Compensation.claim already paid the leaf's account whoever submitted it.
docs/privacy2026-10-18 19:00 UTC
design
Infrabond
The product is now called Infrabond and its ticker is $IBOND. The site, the contracts, the prober and the records are the same. The API still accepts the earlier leg names.
og.png2026-10-07 13:00 UTC
design
Infrabond's new look
The indigo and mint night is gone. The site now runs on warm black with cobalt blocks and amber light, and the light sections sit on cool grey trays. The name is set in a pixel face. The city in the hero is built from unit cubes: one tower per bonded service, charcoal layers for the operator's junior capital, cobalt for the backers above, and an amber window for every probe that passed. Same data, same binding, nothing changed in the contracts or the prober.
og.png2026-10-06 21:00 UTC
compensation
Epoch 0 of bond 1: 1 customer compensated
0.015000 USDG to customers, 0.000000 USDG to the reserve.
0x590f...1a632026-10-06 21:00 UTC
settle
Epoch 0 of bond 1 settled with a slash
30 failed probes of 60, 3% slashed, 0.015000 USDG to compensation.
0xc85e...c81d2026-10-06 18:10 UTC
release
Canary switched off for 30 minutes
A planned outage inside epoch 0 (18:00 to 19:00 UTC) to exercise a real slash: 30 failed probes against a 99% promise. The backer asked to exit during the same epoch; the exit waits for its settlement.
0xcd1a...c3662026-10-06 17:50 UTC
release
Prober live: first window posted
25 services probed once a minute. Window 17:40 UTC posted with 175 probe records, each anchored to the hash of the block seen before its probe; the root recomputes from /probes/<root>.json.
0xa1dc...01612026-10-06 17:42 UTC
release
House bonds issued
Four house services bonded with real USDG: canary (1 h epochs, availability 99%), quotes feed, filings feed and the Infrabond API (daily epochs). A second house key backs the canary with 0.40 USDG senior.
0xec56...f0f5at deploy
release
Contracts deployed and verified
BondBook, ProbeLog, Compensation, the passkey account factory and a 48 h TimelockController that owns them.
0xe43B...5292at deploy
release
SDK 1.1.0 served from the site
/sdk/bond.mjs: isBonded, record, issue, back, exit, claimCompensation, the bonded() middleware, and the privacy layer: freshPayout, payX402 with a payout address, sealEndpoint and claimSealed. sha256 4942aef077ce3401baf9c7eb04bfd9ce2c74fcdb2500f621372d3cad37de6068
sha256 4942aef077ce