Skip to content

feat: add Commonware Alto Reference Blockchain Node and Benchmark Studio - #200

Open
yappermoar-boop wants to merge 1 commit into
commonwarexyz:mainfrom
yappermoar-boop:feature-alto-node-studio
Open

feat: add Commonware Alto Reference Blockchain Node and Benchmark Studio#200
yappermoar-boop wants to merge 1 commit into
commonwarexyz:mainfrom
yappermoar-boop:feature-alto-node-studio

Conversation

@yappermoar-boop

Copy link
Copy Markdown

Added interactive Web Studio for running the Alto reference Rust blockchain node, simulating sub-second block production (~250ms target) across a P2P node mesh, inspecting Alto crates architecture, and CLI testing utilities.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 3 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 18226ac. Configure here.

const data = await res.json();
if (data.success) {
appendBlockRow(data.block);
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale dashboard chain height

Medium Severity

The header height is set once from static networkMetrics.currentHeight and never updated when produceBlock succeeds, and /api/config always returns the frozen config value instead of the runner’s live height. The dashboard keeps showing the initial height while produced blocks advance past it.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 18226ac. Configure here.

</div>
`;
container.insertBefore(row, container.firstChild);
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unbounded ledger DOM growth

Medium Severity

appendBlockRow always inserts a new ledger row and never trims older entries. During auto-production the #blocks-container grows without bound, increasing DOM size and browser memory over time.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 18226ac. Configure here.

initTabs();
loadConfig();
initListeners();
});

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ledger not restored on load

Medium Severity

Startup only calls loadConfig and never fetches /api/node/blocks, so a refresh or new tab shows an empty ledger even though the server still holds produced blocks. The available blocks API is unused by the UI.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 18226ac. Configure here.

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.

1 participant