/system

Onchain Rewind

theme

Button

primary
ghost
icon

Tooltip

label / value

ProgressSegments

idle
filling / paused
done

StatNumber

1,284transactions
+38.4%price change
−42.7%negative

ChainBar · ChainIcon · TokenIcon

BaseBase
Base: 46%
EthereumEthereum
Ethereum: 27%
ArbitrumArbitrum
Arbitrum: 14%
OptimismOptimism
Optimism: 8%
PolygonPolygon
Polygon: 5%
icons: loaded / initial / broken / blockedETHETHPEPEBaseOptimismPolygon

LineChart

under 2 pointsRenders nothing:

ShareCard

with ENS name

vitalik.eth

0xd8dA…6045
transactions
1,284
chains
6
top token
ETH
onchain since
Mar 2022
Onchain Rewind
address only

0x5a0B…9c4c

0x5a0B…9c4c
transactions
97
chain
1
top token
PEPE
onchain since
Nov 2024
Onchain Rewind

WalletCombobox

idle
resolving
valid
0xd8dA…6045 ✓
invalid

That isn't a valid address or ENS name.

disabled

SettingsDialog

open

StoryChrome

wallet + progress
Onchain Rewind
vitalik.eth
recorded snapshot
Onchain Rewind
vitalik.eth

Showing a recorded snapshot

no wallet (first visit)
Onchain Rewind

SiteFooter

Shown only on the start screen of / (overlay, bottom of that screen) and at the end of /dev-stats (inline) — never during the reveal or the story.

inline (/dev-stats)
overlay (start screen)

ParticleReveal

fixture
run

Full screen. The callbacks are logged over the reveal. Press Esc to come back. Under reduced motion there is no canvas: a static count, then a crossfade.

Full screens

fixture
open

Full screen. Press Esc or the gear to come back. ← → move the story, a hold or Space pauses it, and the last card holds instead of advancing. The empty fixture has no transactions to page, so it opens on the empty state.

Development log

The four read states, then the record on fixtures — a ticket with two rounds (a re-review after a human ruling), and a ticket the log currently marks running.

Reading the project record…

empty milestone

Milestone

Onchain Rewind v1: demo-ready

0 of 0 tickets merged

Time per ticket

—

Median developer plus reviewer time per ticket, from the Vinaya round log. Waiting for a human is not counted.

Second rounds

0 of 0

Reviewed tickets where the reviewers asked for changes and the developer went round again.

Problems caught

0

Raised by the two reviewers before merge:Code review: noneSecurity: none

Typical size

—

Model tokens

0 out

0 read in total, developer and reviewers together.

Ticket by ticket

Rounds is how many times the developer and reviewers went back and forth. Problems are what each reviewer, code review and security, raised, by severity — not every problem stops a merge; some are recorded and fixed later.

  • TicketTimeRoundsSizeProblemsTokens

Milestone

Onchain Rewind v1: demo-ready

3 of 5 tickets merged

Reviewers are working on ticket #25 — The share panel handles a wallet with no balance history — right now.

The developer is working on ticket #28 — A retired demo wallet is replaced with one that still tells a story — right now.

Time per ticket

42 min

Median developer plus reviewer time per ticket, from the Vinaya round log. Waiting for a human is not counted.

Second rounds

1 of 4

Reviewed tickets where the reviewers asked for changes and the developer went round again.

Problems caught

12

Raised by the two reviewers before merge:Code review: 1 blocker · 3 major · 5 minorSecurity: 1 high · 1 medium · 1 low

Typical size

4 files

Median change: 180 lines added or removed.

Model tokens

410k out

3.2M read in total, developer and reviewers together.

Where the time goes

Developer writes the code: 2 h 45 min (74%)Reviewers check it: 58 min (26%)

Across every round the log has seen. Humans stepped in 1 time. The loop recovered from a platform failure on its own on 1 ticket.

Guardrails

6 automated checks ran across 214 runs before code could be committed, pushed or merged. 9 runs stopped a bad change.

The rules are enforced by code, not by asking the AI politely. Live from the Vinaya log, refreshed every few seconds.

Ticket by ticket

Rounds is how many times the developer and reviewers went back and forth. Problems are what each reviewer, code review and security, raised, by severity — not every problem stops a merge; some are recorded and fixed later.

  • TicketTimeRoundsSizeProblemsTokens
  • #21Merged1 human ruling

    The GitHub record of every task becomes a development record

    Pull request #49Started Code review: approveSecurity: approve

    Time58 min
    Rounds2 rounds
    Size6 files+410 −22
    ProblemsCode review:1 blocker1 major2 minorSecurity:none
    Tokens120k out980k read
    1. Round 1Changes requestedConfidence 74%

      Developer 22 minReviewers 9 min5 files · +300 −10

      Problems raised: 1 blocker · 1 major · 1 minor

    2. Round 1 · re-review after a human rulingApprovedConfidence 91%

      Developer 14 minReviewers 6 min6 files · +410 −22

      Problems raised: 1 minor

    2 rounds · 51 min of developer and reviewer time. A human paused the loop at least once.

  • #24Merged

    The development record reads the Vinaya log correctly

    Pull request #45Code review: approveSecurity: approve

    Time31 min
    Rounds1 round
    Size4 files+180 −14
    ProblemsCode review:1 major1 minorSecurity:none
    Tokens95k out720k read
    1. Round 1ApprovedConfidence 88%

      Developer 24 minReviewers 7 min4 files · +180 −14

      Problems raised: 1 major · 1 minor

    1 round · 31 min of developer and reviewer time. The loop recovered from a platform failure on its own.

  • #20Merged

    The Vinaya log's review-loop events become a round-by-round record

    Pull request #43Code review: approveSecurity: pass

    Time27 min
    Rounds1 round
    Size3 files+140 −8
    ProblemsCode review:1 major1 minorSecurity:1 high1 medium1 low
    Tokens88k out610k read
    1. Round 1ApprovedConfidence 82%

      Developer 21 minReviewers 8 min3 files · +140 −8

      Problems raised: 1 major · 1 minor · 1 high · 1 medium · 1 low

    1 round · 29 min of developer and reviewer time.

  • #25In review

    The share panel handles a wallet with no balance history

    Pull request #51Code review: approve

    Time—
    Rounds1 round
    Size2 files+60 −4
    ProblemsCode review:1 minorSecurity:none
    Tokens41k out340k read
    1. Round 1In progress

      Developer 18 minReviewers —2 files · +60 −4

      Problems raised: 1 minor

    1 round · 18 min of developer and reviewer time.

  • #27Planned

    A twelfth demo wallet replaces one that stopped producing a good story

    Time—
    Rounds—
    Size—
    Problems—
    Tokens—

When GitHub fails but the Vinaya log hasn't: no ticket titles or status, just the round activity, time and guardrails the log alone can give.

Ticket #25 is being worked on right now.

Where the time goes

Developer writes the code: 2 h 45 min (74%)Reviewers check it: 58 min (26%)

From the Vinaya log alone, while GitHub is unavailable.

Guardrails

6 automated checks ran across 214 runs before code could be committed, pushed or merged. 9 runs stopped a bad change.

The rules are enforced by code, not by asking the AI politely. Live from the Vinaya log, refreshed every few seconds.

Round activity, from the Vinaya log

GitHub is unavailable, so ticket titles and status aren't shown here — only what the round-by-round log itself recorded.

  • Ticket #20
    1. Round 1ApprovedConfidence 82%

      Developer 21 minReviewers 8 min3 files · +140 −8

      Problems raised: 1 major · 1 minor · 1 high · 1 medium · 1 low

  • Ticket #25
    1. Round 1In progress

      Developer 18 minReviewers —2 files · +60 −4

      Problems raised: 1 minor