Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[enhancement]: show what was checked in the browser verifier

Open
  • Is something wrong?
#24 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@khoap1220-hue is already working on this.

Since Oct 27, 2026.

  • #28 by @sparkysolutions10-pixel — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
1/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript, rust
Domain
cryptography, frontend

Research direction

Read CONTRIBUTING.md for the repository checks, then inspect site/app.js and the browser verifier's verdict rendering. Time the verify call and use the report and bundle text for the displayed counts and size; done means the localized muted line appears for the stored sample and proven transactions, not rejections, with a screenshot in the PR.

Written by the indexing model from the issue text.

Description

area/site complexity:trivial enhancement good first issue Stellar Wave
Context

A verified result in the browser lists the ledger, the orgs and the claims, but not how much work was done. "30 signatures checked in 7 ms, 77 KB bundle" makes it concrete that the check really ran in the visitor's browser.

Scope
  • Time the verify call in site/app.js (performance.now()), and take the bundle's size from its text.
  • Add one muted line under the verdict, such as "Checked 30 Ed25519 signatures and 2 hash chains in 7 ms, here in your browser. Bundle: 77 KB."
  • Count the signatures from report.ledger.signers.length. Hash chains are one for the ledger plus one per claim.
Done when
  • The line appears for the stored sample and for a proven transaction, and not for rejections.
  • Numbers use the visitor's locale formatting. A screenshot in the PR.

Comment to be assigned before starting. Read CONTRIBUTING.md for the checks this repository runs.

Dominant language
Rust
Stars
1
Forks
1
Avg merge
3d 13h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Externalize-Labs/externalize

All issues in Externalize-Labs/externalize

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.