Skip to content

Feat/200ms demo - #145

Open
soheimam wants to merge 10 commits into
mainfrom
feat/200ms-demo
Open

Feat/200ms demo#145
soheimam wants to merge 10 commits into
mainfrom
feat/200ms-demo

Conversation

@soheimam

@soheimam soheimam commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • added 200ms demo game and also added 200m copy to transactions

Screenshots

Test plan

@cb-heimdall

Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

@vercel

vercel Bot commented Sep 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
omni-ui Ready Ready Preview Sep 3, 2026 7:50pm UTC

Request Review

Vibenet runs Denim (one block every 200 ms, with a millisecond
timestampMs on each block). Every sent transaction in the Accounts and
Tokens demos now carries an inclusion badge on the success view and its
Activity row: "Landed in 359 ms · block 148,646 · .200". Latency is the
block's own timestamp minus the send time, so it reports chain latency
rather than client polling; the trailing slot is the 200 ms position
inside the second.

The account engine records the send time before broadcast, polls
receipts at the block cadence, and reads timestampMs from the landed
block. A short direct receipt pre-poll runs ahead of the vendored waiter,
which otherwise spent a second round trip per loop and turned a 300 ms
inclusion into ~1.4 s of spinner. Validity's receipt poll drops from 1 s
to 150 ms for the same reason.
Every swallow adds exactly one; heavy walls keep their reward by
filling the belly twice as fast. Comments and tests updated to match.
Measure the span between oldest and newest head in a 3 s window instead
of counting heads per fixed bucket, which made a steady 200 ms cadence
flicker between 5.0 and 5.5.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants