RecheckableHelium
helium.com · Infra · Solana · data checked 2026-10-20 13:01 (Stockholm)
Contact route: on-chain security.txt (program) ↗
Not claimed Automated from public data
Produced automatically from public data on 2026-10-20 (method v0.2.6). It shows how much of this project’s control structure, code and contact information could be checked from public sources. No person selected or adjusted it, and nothing a project does or pays changes it. It is not a security audit.
Beta: the method is still being calibrated, so this automated score may contain errors. Send a correction.
Transparency score, not a security audit. Scores are generated automatically from public data (Solana RPC, OtterSec build registry, GitHub, project websites). Projects are not involved unless a page is marked “Claimed”, and claiming never changes a score. Nothing here says a project is safe. How scores are made → · Corrections, right of reply & opt-out →
- Onchain: strongest Code openness; weakest Contract control; missing data in Contract control, Audits, Team & contact.
Something wrong on this page? Dispute a check or send a correction · opt-out. We re-run the check and correct the page.
What was checked: addresses & sources
hdaoVTCqhfHHo75XdAMxBKdUqvq1i5bF23sisBqVgGR(program) — source: https://github.com/helium/helium-program-library/blob/master/Anchor.tomlhntyVP6YFm1Hg25TN9WGLqM12b8TQmcknKrdu1oxWux(token mint) — source: https://docs.helium.com/tokens/hnt-token- audits page: not found on an official page → not checked
Website helium.com · GitHub helium/helium-program-library. Addresses are used only if they appear verbatim on an official project page.
Onchain track
Contract control weight 30 · 1 unknown15/30
- ◐ Partial
Upgrade authority hdaoVT…
Upgrade authority is pULUgsYtKvT7qhsL8QJ2oJXYQUeCCdjtfawPnBqEr3U: Squads v4 multisig FXyzyVsm… with threshold 3 of 5 voting member(s) (6 total), time lock 0 s (established by re-deriving the vault address from the multisig; found in upgrade history tx 56c7HzND…). Member independence not established. Address taken from official source: https://github.com/helium/helium-program-library/blob/master/Anchor.tomlWhat would show up as met
- If the program is final, revoke the upgrade authority. It then reads as immutable.
- Otherwise move the authority to a multisig or a DAO. For a multisig, use a threshold of at least 2, add a time lock, and do not keep a separate config authority that can change members without a vote.
- Publish the multisig or DAO address on your own website so the page and the on-chain account can be tied together.
How we check: We read the program’s upgrade authority on Solana (public RPC) and recognise Squads, Serum-style multisigs and SPL Governance accounts. This is what the check looks for. It makes no promise about a score or grade, and claiming or paying never changes a score.
- ✕ Not met
Build matches source (OtterSec registry) hdaoVT…
OtterSec registry: 3 build submission(s) exist (https://github.com/helium/helium-program-library), but none matches the current on-chain program hash (3dcaa95c082c…) — one possible reason is an upgrade after the submission. We found no registry record that the deployed code was built from the public source.OtterSec registry ↗OtterSec registry ↗GitHub ↗ checked 2026-10-20sha256 ce7bf3799473…sha256 7babef1e80f9…What would show up as met
- Build the program reproducibly from your public source with the Solana verifiable-build tooling (
solana-verify). - Submit the build to the registry so that it appears in the OtterSec registry (verify.osec.io). The check reads that registry; it does not rebuild anything itself.
How we check: We ask the OtterSec build registry (verify.osec.io, a third party) whether the deployed program matches a build from the public source. We report what the registry says; we do not rebuild or vouch for anything ourselves. Any registry entry that matches the program’s current on-chain hash counts, not only the registry’s default entry (method 0.2.5). This is what the check looks for. It makes no promise about a score or grade, and claiming or paying never changes a score.
- Build the program reproducibly from your public source with the Solana verifiable-build tooling (
- ? Unknown
Mint authority hntyVP…
3QqEkX1juz4bW8mCQBMJLWjEpHqYawvbEUvpc6iwYom3: a program-derived address whose controller could not be established. The account is owned by circAbx64bbsscPbQzZAUvuXpHqrCe6fLMzc2uKXz9g. Scanned 12 transactions and 67 candidate accounts: no multisig, vault or governance account re-derives to this address.. Address taken from official source: https://docs.helium.com/tokens/hnt-tokendocs.helium.com ↗Explorer ↗Explorer ↗RPC call (getAccountInfo) checked 2026-10-20sha256 692d5c2306d2…sha256 8b47368ca4ba…What would show up as met
- If no more tokens will ever be minted, revoke the mint authority. It then reads as met.
- If minting must stay possible, move the authority to a multisig (threshold 2 or more, time lock) or a DAO and publish that address on your site.
How we check: We read the mint account on Solana (public RPC). This is what the check looks for. It makes no promise about a score or grade, and claiming or paying never changes a score.
- ✓ Met
Freeze authority hntyVP…
Revoked. Address taken from official source: https://docs.helium.com/tokens/hnt-tokendocs.helium.com ↗Explorer ↗RPC call (getAccountInfo)RPC call (getSignaturesForAddress) checked 2026-10-20sha256 692d5c2306d2…sha256 8b47368ca4ba…
Audits weight 15 · 1 not readnot built
- ⊘ Not read
Audits found at official sources
Not read: our checker could not read this source (automatic audit search incomplete: only the 60 most recently updated of 136 repositories were searched). This is not a finding about the project. Pointing us to the right URL? info@recheckable.com Searched: GitHub helium: 60 of 136 non-fork repositories file-listed via GitHub API | helium.com: 25 audit/security page address(es) fetched (docs sub-domains and homepage audit links included). (reason: search_incomplete)api.github.com ↗api.github.com ↗api.github.com ↗GitHub ↗ checked 2026-10-20sha256 b87444fe1a20…sha256 5edaaf99f633…What would show up as met
Nothing for the project to do. Our checker could not read the source this time, so the check is “Not read”: no points are lost. It is tried again at the next run. If you think the data behind it is wrong, send a correction.
Code openness weight 1515/15
- ✓ Met
Public repository
helium/helium-program-library public, created 2022-08-24, 18 contributor(s) (count only).GitHub ↗api.github.com ↗api.github.com ↗ checked 2026-10-20sha256 728ec0a7dfc0…sha256 960440cb6059… - ✓ Met
Licence
SPDX: Apache-2.0.GitHub ↗api.github.com ↗api.github.com ↗ checked 2026-10-20sha256 728ec0a7dfc0…sha256 960440cb6059… - ✓ Met
Activity last 90 days
Last push 2026-10-19 (0 d ago).GitHub ↗api.github.com ↗api.github.com ↗ checked 2026-10-20sha256 728ec0a7dfc0…sha256 960440cb6059… - ✓ Met
On-chain program source public
1/1 own program ID(s) found in public source: hdaoVT… in https://github.com/helium/helium-program-library. Repos searched (shallow clone, text search for the program ID): https://github.com/helium/helium-program-library. Does not prove the deployed binary matches (see the build check).
Onchain history weight 105/10
- ◐ Partial
Last deploy hdaoVT…
Last deploy 2026-09-25 (25 d ago). Upgraded within the last 30 days.Explorer ↗RPC call (getAccountInfo)RPC call (getSignaturesForAddress)RPC call (getTransaction) checked 2026-10-20sha256 f1640045e12a…sha256 4012f0eabeb2…What would show up as met
- Nothing to configure: a deploy more than 30 days ago reads as met, a more recent deploy as partial because the code changed recently.
How we check: We read the last deploy time on Solana. This is what the check looks for. It makes no promise about a score or grade, and claiming or paying never changes a score.
- ○ Not built
Program age / upgrade count hdaoVT…
Full history scan (first deploy, upgrades in 30 d, authority changes) needs an indexer (e.g. Helius); not available on public RPC.Explorer ↗RPC call (getAccountInfo)RPC call (getSignaturesForAddress)RPC call (getTransaction) checked 2026-10-20sha256 f1640045e12a…sha256 4012f0eabeb2…
Team & contact weight 15 · 1 unknown7.5/15
- ✕ Not met
Security contact (security.txt)
No valid security.txt at /.well-known/security.txt or /security.txt (404).What would show up as met
- Publish a text file at https://your-domain/.well-known/security.txt (or /security.txt) with a
Contact:line, for exampleContact: mailto:security@your-domain. - RFC 9116 also asks for an
Expires:line. We look only forContact:, but addExpires:too so the file stays correct.
How we check: We fetch the two standard locations over HTTPS. This is what the check looks for. It makes no promise about a score or grade, and claiming or paying never changes a score.
- Publish a text file at https://your-domain/.well-known/security.txt (or /security.txt) with a
- ? Unknown
Bug bounty programme linked
No bug-bounty link found on homepage (raw + rendered), sitemap or security.txt. Not checked deeper (docs sites, Immunefi search) — counted as unknown, not as missing. Also checked: Immunefi public list: no active programme matched; hdaoVT… security.txt policy https://github.com/helium/helium-program-library/tree/master/SECURITY.md mentions no bounty, contacts: email:hello@helium.foundation.helium.com ↗helium.com ↗helium.com ↗helium.com ↗ checked 2026-10-20sha256 fa9e868dcfae…sha256 493fda531200…What would show up as met
- Link your bug bounty (for example an Immunefi, HackerOne or Cantina page, or a /bug-bounty page of your own) from the homepage, the sitemap or your security.txt.
- “Unknown” here means we found no link. It does not mean you have no programme.
How we check: We look at the homepage links (also as rendered in a browser), sitemap.xml and security.txt, and at Immunefi’s public list for on-chain security.txt names. This is what the check looks for. It makes no promise about a score or grade, and claiming or paying never changes a score.
- ℹ Status only
Claimed / not claimed
Status only, not scored: claiming proves control of an authority, domain or GitHub organisation and never changes a score. The status is shown in the page header.source: calculated from the other checks checked 2026-10-20 - ○ Not built
Team declared (voluntary, with consent)
Team declaration + consent flow not built — excluded.source: calculated from the other checks checked 2026-10-20 - ℹ Status only
Components declared complete by the project
Status only, not scored (it used to be scored, which made pages that are not claimed systematically lower; removed 2026-10-15). Other programs/packages may exist that were not submitted.source: calculated from the other checks checked 2026-10-20 - ✓ Met
Program embeds security.txt
1/1 own program(s) embed a solana-security-txt block with contacts (hdaoVT…). - ◐ Partial
Official program address list
hdaoVT… published on project GitHub only (https://github.com/helium/helium-program-library/blob/master/Anchor.toml).What would show up as met
- List your official program addresses on a page of your own domain (for example a docs page called “Addresses”). A list only on GitHub reads as partial, and one only on a third-party page as not met.
How we check: We use the pages the project itself publishes. This is what the check looks for. It makes no promise about a score or grade, and claiming or paying never changes a score.
Legal documents weight 1010/10
- ✓ Met
Terms & privacy policy present
Terms: https://helium.com/legal; privacy: https://helium.com/privacy (homepage links, sitemap.xml, common paths). Content not assessed. - ○ Not built
Registered legal entity
Not stated.source: calculated from the other checks checked 2026-10-20 - ✓ Met
Legal entity named in terms
Terms/privacy text names “Nova Labs, Inc” (https://helium.com/legal). Not checked against a company registry.
Domain weight 55/5
- ✓ Met
HTTPS
https://helium.com answered HTTP 200 over TLS.helium.com ↗helium.com ↗helium.com ↗helium.com ↗ checked 2026-10-20sha256 fa9e868dcfae…sha256 493fda531200… - ✓ Met
Security headers
Present: HSTS, CSP, X-Content-Type-Options, X-Frame-Options. Missing: none.helium.com ↗helium.com ↗helium.com ↗helium.com ↗ checked 2026-10-20sha256 fa9e868dcfae…sha256 493fda531200… - ✓ Met
Domain age
Registered 1997-05-22 (~10743 d), source: RDAP (rdap.org). Registrant data ignored. - ✓ Met
Domain ↔ components consistency
Linked: address hntyVP… published on helium.com (https://docs.helium.com/tokens/hnt-token); homepage links to github.com/helium; GitHub org name matches domain (weak)source: calculated from the other checks checked 2026-10-20
Snapshot hash of monitored fields: 6a8871d5425b179a
AI summaries
Generated with Grok 4.7 (xAI), Claude sonnet-5-5 (Anthropic) and GPT-6.1-sol (OpenAI) via their APIs. xAI, Anthropic and OpenAI have not reviewed, approved or sponsored Recheckable. AI-generated text; models see only extracted check results, never project-supplied text or personal names. They do not affect the score. Some text on this site (summaries and reports) is AI-generated and labelled where it appears. Scores and check results come from fixed code, not from AI. Scores are produced automatically from public data and are not reviewed by hand before they are shown; cases that the automatic checks flag are held for a person.
Template summary (deterministic)
Onchain track: band C (65/100, coverage 85 %, onchain v0.2.6). Strongest: Code openness, Legal documents, Domain. Weakest: —. 2 check(s) unknown (each costs 1.5 points); 1 not read (no points lost, lowers coverage); 3 not built yet (excluded).
Grok (xAI)
Placeholder — no API key configured for this model in the PoC.
Claude (Anthropic)
Placeholder — no API key configured for this model in the PoC.
GPT (OpenAI)
Placeholder — no API key configured for this model in the PoC.
Regulatory information
The project has not declared any regulated-activity types, so no rules are listed.
Law firms (free listing, alphabetical, no ranking)
- Delphi — Stockholm, Blockchain law (self-described)
- Gernandt & Danielsson — Stockholm, Fintech (self-described)
- Magnusson — Stockholm, Fintech (self-described)
- Mannheimer Swartling — Stockholm, Fintech (own practice page to be confirmed) (self-described)
- Setterwalls — Stockholm, Fintech (self-described)
- Vinge — Stockholm, MiCA (own practice page to be confirmed) (self-described)
Recheckable has no financial relationship with the listed firms and receives no fee per contact. Paid placements, if ever introduced, are marked “Ad” and never shown next to low scores.
Score history
Automated score at each published review, newest on the right. The line steps at the date of a review; between reviews the score is unchanged.
◆ 2026-10-17: the scoring method changed from v0.2.1 to v0.2.5. A score change at that point can come from the method and not from the project.
◆ 2026-10-19: the scoring method changed from v0.2.5 to v0.2.6. A score change at that point can come from the method and not from the project.
Data table
| Review | Track | Score | Grade | Coverage | Method |
|---|---|---|---|---|---|
| 2026-10-15 | onchain | 53/100 | C | 85 % | v0.2.1 |
| 2026-10-17 | onchain | 53/100 | C | 85 % | v0.2.5 |
| 2026-10-19 | onchain | 65/100 | C | 85 % | v0.2.6 |
| 2026-10-20 | onchain | 65/100 | C | 85 % | v0.2.6 |
Check changes between reviews
- 2026-10-19 · onchain Audits found at official sources: Unknown → Not read method changed
History
- 2026-10-20 13:01Forced fresh run (same result; fresh evidence snapshots): onchain C (65, coverage 85 %)
- 2026-10-19 12:42Nightly re-run: onchain C (65, coverage 85 %)
- 2026-10-17 06:08Nightly re-run: onchain C (53, coverage 85 %)
- 2026-10-15 10:16Method 0.2.1: the scope declaration and claim status are status-only (never scored). Re-scored from the stored checks, no new fetch. Before: C 52 (cov 81 %); after: C 53 (cov 85 %).
- 2026-10-15 07:43Initial review (operator-run): onchain C (52, coverage 81 %)
Project's own statements and reply
Does your team control the upgrade authority, official domain or GitHub organisation of this project? Claim this page (free, about a minute; it never changes a score).
For project owners: badge
Status: Active. The badge says “no changes since review”, never “safe”.
Badges are for claimed projects. The embed code is available after the page has been claimed (free, about a minute; claiming never changes the score). Claim this page
Re-checks are rate-limited (once per 10 minutes). Restoring a grey badge requires a full review.