Skip to content

docs: align final Afterlight release claims #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
dolepee wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs: align final Afterlight release claims #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 4 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,18 +8,13 @@ An owner privately funds a fixed reserve through STRK20 and remains in control t

[![CI](https://github.com/dolepee/afterlight/actions/workflows/ci.yml/badge.svg)](https://github.com/dolepee/afterlight/actions/workflows/ci.yml)

| Rubric | Present evidence |
|---|---|
| STRK20 integration depth | Private funding, cancellation/refund, and exact-note recovery through the canonical pool and custom Afterlight helper |
| Working Mainnet product | Public Ready X app, deployed contract, five qualifying receipts, and a founder-operated E3 lifecycle |
| Innovation | Authenticated inactivity, heartbeat, veto, designated-successor authorization, and one exact private destination |
| Open source | Reproducible artifacts, CI, read-only Mainnet verifier, threat model, operations guide, and MIT license |

## Current status

**Evidence level: E3 public completion.** The complete recovery mechanism has run through the deployed public app on Starknet Mainnet. Five successful transactions touch both the canonical STRK20 pool and Afterlight. The fresh public Recovery Drill completed private funding, heartbeat, request, veto, a second request, and [exact-note recovery](https://voyager.online/tx/0x722033f7fd0397ff4d3845428c98cad885b6a63824f7c78a2b7e1d7d6f5c1b6); Ready X then showed the successor's shielded balance increase from `7 STRK` to `8 STRK` while the neutral sponsor paid the pool and network fees.
**Evidence level: E3 public completion.** The complete recovery mechanism has run through the deployed public app on Starknet Mainnet. Five successful transactions touch both the canonical STRK20 pool and Afterlight. The fresh public Recovery Drill completed private funding, heartbeat, request, veto, a second request, and [exact-note recovery](https://starkscan.co/tx/0x722033f7fd0397ff4d3845428c98cad885b6a63824f7c78a2b7e1d7d6f5c1b6); Ready X then showed the successor's shielded balance increase from `7 STRK` to `8 STRK` while the neutral sponsor paid the pool and network fees.

**Release status: deployed public Mainnet Recovery Drill.** Afterlight is [deployed on Mainnet](https://starkscan.co/contract/0x06e8b6e49b4366e0dc6a35eee722b417c718988eca3f4a0c298bdf8785261c25). The bounded neutral relayer executed the public control and recovery path without using either Ready role as the outer sender. The public app supports real Ready X connection, local per-vault keys, private funding, live state, relayed controls, exact-note recovery, contextual receipts, and post-claim balance reconciliation.

**Release status: deployed public Mainnet product.** Afterlight is [deployed on Mainnet](https://starkscan.co/contract/0x06e8b6e49b4366e0dc6a35eee722b417c718988eca3f4a0c298bdf8785261c25). The bounded neutral relayer executed the public control and recovery path without using either Ready role as the outer sender. The public app supports real Ready X connection, local per-vault keys, private funding, live state, relayed controls, exact-note recovery, contextual receipts, and post-claim balance reconciliation.
The public drill is founder-operated E3 evidence; an unrelated owner-successor E4 completion is not claimed. Its neutral sponsorship is deliberately capacity-limited: the supported route admits one fully backed vault and one private exit at a time, and closes funding whenever allowance, balance, liability, reservation, lease, or UTC-day exit capacity is unavailable. The relayer is correctness-untrusted but liveness-critical—it cannot forge or redirect a valid recovery, but it can delay sponsored controls or settlement by refusing or failing to relay them.

## Recovery flow

Expand Down
24 changes: 17 additions & 7 deletions docs/MAINNET.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,9 @@

## Current evidence level

Afterlight has a complete deployed Mainnet product and five validator-qualified
STRK20 receipts. It is classified **E3 public completion**. A fresh Recovery
Afterlight has a deployed public Mainnet Recovery Drill and five
validator-qualified STRK20 receipts. It is classified **E3 public completion**.
A fresh Recovery
Drill completed through the canonical app, and an approved Ready X
`wallet_strk20Balances` read showed the successor increase from `7 STRK` to
`8 STRK` after its exact-note claim. Prepared, simulated, reverted, and
Expand Down Expand Up @@ -52,19 +53,28 @@ contract. Plain Shield transactions and failed attempts do not fill these slots.
| `CANCEL_REFUND` Vault A | [`0x69e234…c0fb`](https://starkscan.co/tx/0x69e2345ae8816986a709de84f0dcb571b5d092400d6c53bf90197480102c0fb) | PASS |
| `FUND` Vault B | [`0x036e00…0682a`](https://starkscan.co/tx/0x036e003396fe360ae7fe4766646f493c0eb579d82509652559d40e460770682a) | PASS |
| `CLAIM` Vault B | [`0x11c990…c8098`](https://starkscan.co/tx/0x11c990aea864e755630d41fd1292620c313b3f64407fc0b3a902544c67c8098) | PASS |
| Public E3 `CLAIM` | [`0x722033…f5c1b6`](https://voyager.online/tx/0x722033f7fd0397ff4d3845428c98cad885b6a63824f7c78a2b7e1d7d6f5c1b6) | PASS |
| Public E3 `CLAIM` | [`0x722033…f5c1b6`](https://starkscan.co/tx/0x722033f7fd0397ff4d3845428c98cad885b6a63824f7c78a2b7e1d7d6f5c1b6) | PASS |

The official hub validator's exact success, pool-touch, and declared-contract
ownership checks pass for all five. Vault A is `CANCELLED`, Vault B is
`CLAIMED`, total locked liability is zero, and the neutral pool allowance is
zero. Exact-note settlement is proven onchain. The wallet's post-finality
ownership checks pass for all five. At the terminal E2 checkpoint, Vault A was
`CANCELLED`, Vault B was `CLAIMED`, total locked liability was zero, and the
neutral pool allowance was zero. Exact-note settlement is proven onchain. The
wallet's post-finality
reconciliation is `6 STRK -> 7 STRK`: the exact `+1 STRK` recovery output was
added to the beneficiary while the neutral sponsor paid the separate `6 STRK`
pool fee. The public E3 vault is also `CLAIMED`; its immediate Ready X
reconciliation is `7 STRK -> 8 STRK`. Final video production remains pending.

The public E3 lifecycle was founder-operated. An unrelated owner-successor E4
completion is not claimed.
completion is not claimed. After that lifecycle, the neutral sponsor allowance
was deliberately restored to exactly `12 STRK`: enough for one bounded private
exit under the supported UI policy. A successful claim or cancellation consumes
`6 STRK` of that allowance and exhausts the route until a later, reviewed
replenishment. Funding also fails closed whenever a liability, reservation,
funding lease, daily-exit limit, sponsor-balance floor, or exact allowance check
is not ready. This is a capacity-limited public drill, not an unattended or
permissionless liveness guarantee; the relayer cannot forge or redirect a valid
settlement, but it can delay one by censoring or going offline.

Historical identifiers such as the `spike-inline-56` compiler profile and the
relayer's `phase-a` hostname are pinned release identifiers. They do not mean
Expand Down