vitalik.eth
0xd8dA…6045- transactions
- 1,284
- chains
- 6
- top token
- ETH
- onchain since
- Mar 2022
That isn't a valid address or ENS name.
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.
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 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.
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…
Ticket details are catching up
Ticket titles, status, size and pull requests are missing below for a few minutes. Round activity from the Vinaya log, where available, still shows. This refreshes on its own every few seconds.
Timing data is temporarily unavailable
Every ticket, round and finding below is complete. Only the time per round and the guardrail totals are missing for now. This refreshes on its own every few seconds.
Timing data is temporarily unavailable
Every ticket, round and finding below is complete. Only the time per round and the guardrail totals are missing for now. This refreshes on its own every few seconds.
Milestone
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.
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.
Milestone
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.
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.
The GitHub record of every task becomes a development record
Pull request #49Started Code review: approveSecurity: approve
Developer 22 minReviewers 9 min5 files · +300 −10
Problems raised: 1 blocker · 1 major · 1 minor
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.
The development record reads the Vinaya log correctly
Pull request #45Code review: approveSecurity: approve
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.
The Vinaya log's review-loop events become a round-by-round record
Pull request #43Code review: approveSecurity: pass
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.
The share panel handles a wallet with no balance history
Pull request #51Code review: approve
Developer 18 minReviewers —2 files · +60 −4
Problems raised: 1 minor
1 round · 18 min of developer and reviewer time.
A twelfth demo wallet replaces one that stopped producing a good story
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.
GitHub is unavailable, so ticket titles and status aren't shown here — only what the round-by-round log itself recorded.
Developer 21 minReviewers 8 min3 files · +140 −8
Problems raised: 1 major · 1 minor · 1 high · 1 medium · 1 low
Developer 18 minReviewers —2 files · +60 −4
Problems raised: 1 minor