Skip to content
HEY Research Lab
Menu

Quorum

$QUORUM

StockFi · Utility

Contract 0xa6452fd7134218f62056a304eaf501f8714a26b9

HEY holds 93 other Robinhood Chain tokens that use $QUORUM. This page is only the contract above. See them

A swarm of security lenses that never talk to each other. Sibyl Memory is the only channel between them, and it is the only reason the swarm can agree on anything, recognise anything, or forget anything.

What HEY knows

Development

Last shipped 28 days agoActive: 1 counted ship in 30 days; latest ship 28 days ago. Evidence Source

Build Momentum 25How it is measured

Latest: Code changes, week of 2026-09-28 – 2026-10-04 · 27 commits

Token market · context

Active market$26K fully diluted valuation

Same name, different contract: 1 other published project uses the name Quorum. This page: the deployer of 0xa645…26b9 signed for it on chain. quorum: no official source HEY read names 0xeb42…aaf0. HEY does not say which is the real one — only what each project’s own sources name.

Token check

Project names this contract
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Quorum on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow Quorum

No account? Email me Quorum’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

View latest ship
Share
Attention
Building ranks ahead, and the market already notices it, among comparable projects: its building is ahead of 94.1% of them, its market attention ahead of 77.3% (a gap of 16.8). What the Discovery Gap is

It compares building with market attention; it is not a prediction and not a reason to trade.

More detail
Product usage
Fact1 of 1 watched contract active · 12,404 calls in 7 days — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches.

Counted from the chain. Usage says the contracts are used, not that anyone is building.

Contracts
Fact1 contract on record for code changes, 1 with published source code; no implementation or interface change recorded.
Not yet known
Unknown3 gaps: Official docs (no source), API description (not tied to the project yet), Official site changes (not tied to the project yet). HEY read its website and found no link to docs.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 1 counted ship in the last 30 days, the newest 2026-10-03.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 27 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 38 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 53 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found counted building from the project's own sources.
Source9 registered sources, 3 of them context only.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 27 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 38 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 53 commits+7 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Project names this contract.
Project names this contract: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedProject names this contract: the owner signed for it on-chain.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Active market.
Active market: the pool holds liquidity and the token traded in the last day.
Source9 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Research coverage: HEY can answer 16 of the 19 research questions that apply.
16 of 19 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 3h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 41d ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNot tied to the project yetIts website is not yet confirmed as the project’s own.
  • Official site changesNot tied to the project yetIts website is not yet confirmed as the project’s own.

Code and packages

  • Repository detailsMeasuredRead 9h ago.
  • Published packagesMeasuredRead 9h ago.

Contracts

  • Contract creationMeasuredRead 8h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 2d ago.
  • Contract interfaceMeasuredRead 2d ago.

Market

  • Current marketMeasuredRead 56m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead 2d ago.
  • LocksMeasuredRead 3h ago.
  • Market checksMeasured

Not applicable here: Package advisories, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology
LinksWebsite (context only) (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)DEX Screener (opens in a new tab)RHTools (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-09-28 – 2026-10-04 · 27 commits yonkoo11/quorum

Code activitySource-backed

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

What changed, in the repository’s own words:

5 active days in yonkoo11/quorum.

This week HEY looked inside 3 of 27 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

Record ship:f54f0724… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗ (opens in a new tab)

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 3 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-09-21 – 2026-09-27 · 38 commits yonkoo11/quorum

    Code activitySource-backed

    What changed, in the repository’s own words:

    4 active days in yonkoo11/quorum.

    How HEY read this week

    This week HEY looked inside 4 of 38 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 38 commits (opens in a new tab)

  2. Code changes, week of 2026-09-14 – 2026-09-20 · at least 53 commits yonkoo11/quorum

    Code activitySource-backed

    What changed, in the repository’s own words:

    6 active days in yonkoo11/quorum.

    How HEY read this week

    This week HEY looked inside 4 of 53 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 53 commits (opens in a new tab)

  3. v0.7.1: the same code gives the same answer yonkoo11/quorum

    GitHub releaseSource-backed

    This is a defect fix, and the defect was reproducibility. Three runs of the same benchmark corpus, on the same commit, reported 523, 518 and 517 sightings. The findings the two-witness rule publishes did not move, but the count underneath them did, and on one file an accounting… Show all

    This is a defect fix, and the defect was reproducibility. Three runs of the same benchmark corpus, on the same commit, reported 523, 518 and 517 sightings. The findings the two-witness rule publishes did not move, but the count underneath them did, and on one file an accounting finding appeared in one run and not in the next. The cause is in _reads, which reports the variables a line mentions without writing. It reported only the first one, chosen by iterating a set, and Python randomises set iteration order per process. So require(balances[msg.sender] >= MinDeposit) reported balances…

    View evidence: v0.7.1: the same code gives the same answer (opens in a new tab)

  4. 3 releases in yonkoo11/quorum on 19 Sep

    GitHub release

    Show all 3 releases

    1. v0.7.0: a third reading of the access risk yonkoo11/quorum

      GitHub releaseSource-backed

      Quorum had two readings of unguarded-state-write, and both judge a function by how it is written: whether it carries a modifier, and whether the variable it writes carries a privileged-looking name. Recent Solidity writes last_gauge and _validatorsMap, not feeRate, so on… Show all

      Quorum had two readings of unguarded-state-write, and both judge a function by how it is written: whether it carries a modifier, and whether the variable it writes carries a privileged-looking name. Recent Solidity writes last_gauge and _validatorsMap, not feeRate, so on bench/MODERN.md that pair corroborated nothing and recall there was 0%. The last release ended by saying a genuinely different second reading was needed and was not designed yet. This is it. consistency-lens asks the contract instead of the spelling. If every other externally callable function that writes a variable agrees…

      View evidence: v0.7.0: a third reading of the access risk (opens in a new tab)

    2. v0.6.0: lenses read across files yonkoo11/quorum

      GitHub releaseSource-backed

      A lens used to read one file. Modern protocols declare their state in a base contract and put a function's work in an internal helper one file up, which is why four of the seven targets in bench/MODERN.md were invisible to every lens. That file ended by naming this as the only… Show all

      A lens used to read one file. Modern protocols declare their state in a base contract and put a function's work in an internal helper one file up, which is why four of the seven targets in bench/MODERN.md were invisible to every lens. That file ended by naming this as the only change that would move the number, so this release makes it. A run now builds the inheritance graph of its own files, and a function is read with the state and the internal helpers its contract actually has. Nothing wider: an unrelated contract's names stay out of scope, or every same-named local variable would look…

      View evidence: v0.6.0: lenses read across files (opens in a new tab)

    3. v0.5.1: measured against modern audits yonkoo11/quorum

      GitHub releaseSource-backed

      The measurement this project was missing: what the lenses do against recent audits, not against corpora built from the bugs they were written for. bench/MODERN.md takes 16 recent public audit contests, each repository at the exact commit its published report links. Every High… Show all
      • The measurement this project was missing: what the lenses do against recent audits, not against corpora built from the bugs they were written for. bench/MODERN.md takes 16 recent public audit contests, each repository at the exact commit its published report links. Every High and Medium finding was read and classified first, before any lens ran. Two numbers came out of it:
      • The four risks Quorum covers are 5% of what those audits reported at High and Medium. 131 findings; 7 in those shapes; the rest were business logic, denial of service, validation, signatures, slippage, rounding and the…
      View evidence: v0.5.1: measured against modern audits (opens in a new tab)

  5. 3 releases in yonkoo11/quorum on 18 Sep

    GitHub release

    Show all 3 releases

    1. v0.5.0: the claim registry, live yonkoo11/quorum

      GitHub releaseSource-backed

      The claim now goes through a contract. The ClaimRegistry at 0xDeA0…3Ea3 on Robinhood Chain (deployed 18 September 2026, block 66593107) pulls the 100,000 QUORUM fee, burns it through the token's own burn, and only then records the claim, all in one transaction. A record cannot… Show all

      The claim now goes through a contract. The ClaimRegistry at 0xDeA0…3Ea3 on Robinhood Chain (deployed 18 September 2026, block 66593107) pulls the 100,000 QUORUM fee, burns it through the token's own burn, and only then records the claim, all in one transaction. A record cannot exist without its own fee and one fee cannot back two records. No owner, no pause, no upgrade, no ether, nothing to sweep. The fee and the token are immutable. Proven on chain the same day: one claim made from the tool (block 66594959), read back with quorum verify, revealed, and…

      View evidence: v0.5.0: the claim registry, live (opens in a new tab)

    2. v0.4.2: the run as a page on the pull request yonkoo11/quorum

      GitHub releaseSource-backed

      The action now writes the run as a page: every confirmed finding with the two lenses that agreed and the line each read, plus the count of candidates held back. It lands in the job summary (no write token needed) and, with the comment job shown in .github/workflows/quorum.yml… Show all

      The action now writes the run as a page: every confirmed finding with the two lenses that agreed and the line each read, plus the count of candidates held back. It lands in the job summary (no write token needed) and, with the comment job shown in .github/workflows/quorum.yml, as one comment on the pull request that is updated in place on every push. The comment job runs no repository code. Tested on a pull request against this repository: one comment, updated on the second push, then closed.

      View evidence: v0.4.2: the run as a page on the pull request (opens in a new tab)

    3. v0.4.1: the lenses after the Robinhood Chain run yonkoo11/quorum

      GitHub releaseSource-backed

      We ran the eight lenses over every public Solidity repo HEY Research lists for Robinhood Chain: 631 repos, 11,506 files, 281 findings confirmed by two lenses. Then we read all 281 by hand. Three were true. The record, every verdict with its reason, is bench/ROBINHOOD.md. The… Show all
      • We ran the eight lenses over every public Solidity repo HEY Research lists for Robinhood Chain: 631 repos, 11,506 files, 281 findings confirmed by two lenses. Then we read all 281 by hand. Three were true. The record, every verdict with its reason, is bench/ROBINHOOD.md. The false ones taught five changes, all in this release:
      • a function only the owner can call is not a reentrancy target;
      • the reentrancy pair reads one level into the private helpers a function calls (the bug that mattered most in the run sat in a private _claim reached from three public functions);
      • a write anywhere on…
      View evidence: v0.4.1: the lenses after the Robinhood Chain run (opens in a new tab)

  6. v0.4.0: the accounting pair yonkoo11/quorum

    GitHub releaseSource-backed

    A fourth pair of lenses, for the shape announced on 15 Sep: a contract that adds to a balance in one function and never takes it back in another. ledger-lens reads the whole contract (does this balance have any way down?), payout-lens reads one function (does value leave against… Show all

    A fourth pair of lenses, for the shape announced on 15 Sep: a contract that adds to a balance in one function and never takes it back in another. ledger-lens reads the whole contract (does this balance have any way down?), payout-lens reads one function (does value leave against a balance it never reduces?); a finding needs both. Eight lenses, four risks. Measured before it was posted (bench/ACCOUNTING.md): 1,164 files from twelve audited codebases, 0 confirmed; SmartBugs-curated, 4 confirmed, each read by hand and each paying against a balance the contract never lowers, all four counted…

    View evidence: v0.4.0: the accounting pair (opens in a new tab)

  7. 2 releases in yonkoo11/quorum on 13 Sep

    GitHub release

    Show all 2 releases

    1. v0.3.0: verified source from five chains, no key yonkoo11/quorum

      GitHub releaseSource-backed

      quorum fetch --chain ethereum | base | arbitrum | optimism | polygon reads each chain's Blockscout API with no key, joins multi-file contracts into one file with a marker per part, saves under targets/ /, and refuses anything that is not verified JSON under 5 MB. Findings are… Show all

      quorum fetch --chain ethereum | base | arbitrum | optimism | polygon reads each chain's Blockscout API with no key, joins multi-file contracts into one file with a marker per part, saves under targets/ /, and refuses anything that is not verified JSON under 5 MB. Findings are keyed by the path under targets/, so one contract name on two chains stays two targets. The run on the wrapped token from each chain is in bench/MULTICHAIN.md. 49 tests. README and the registry page now say when, and only when, the token would go to a second chain.

      View evidence: v0.3.0: verified source from five chains, no key (opens in a new tab)

    2. Quorum 0.2.0 yonkoo11/quorum

      GitHub releaseSource-backed

      Three days after the hackathon submission. Everything below is measured, and the files that measured it are in bench/. Findings where code review happens. quorum run --sarif writes SARIF 2.1.0 and the composite action (uses: Yonkoo11/quorum@v0.2.0) uploads it to the GitHub… Show all

      Three days after the hackathon submission. Everything below is measured, and the files that measured it are in bench/. Findings where code review happens. quorum run --sarif writes SARIF 2.1.0 and the composite action (uses: Yonkoo11/quorum@v0.2.0) uploads it to the GitHub Security tab. Every alert names the two lenses that agreed and what each one read. A candidate seen by one lens is never written. The registry can no longer be poisoned for one fee. An imported pattern is a hint until two local lenses agree; one fee burn admits one import per memory; the idiom signature keeps the…

      View evidence: Quorum 0.2.0 (opens in a new tab)

  8. Code changes, week of 2026-09-07 – 2026-09-13 · at least 25 commits yonkoo11/quorum

    Code activitySource-backed

    4 active days in Yonkoo11/quorum.

    How HEY read this week

    This week HEY looked inside 4 of 25 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 25 commits (opens in a new tab)
Earlier ships (3)

  1. Quorum v0.1.0 — Sibyl Labs Hackathon yonkoo11/quorum

    GitHub releaseSource-backed

    Demo video for the Sibyl Labs Hackathon submission. A swarm of six security lenses that coordinate only through Sibyl Memory. The video is one continuous unedited session: the swarm reaches quorum on fixtures, three agent processes partition work through the HOT tier, a pattern… Show all

    Demo video for the Sibyl Labs Hackathon submission. A swarm of six security lenses that coordinate only through Sibyl Memory. The video is one continuous unedited session: the swarm reaches quorum on fixtures, three agent processes partition work through the HOT tier, a pattern learned on a fixture is recognised in Friend.tech's live Base contract, the ablation collapses it, and a published claim on Base is verified back against memory. Base claim: https://basescan.org/tx/0xa648…f713

    View evidence: Quorum v0.1.0 — Sibyl Labs Hackathon (opens in a new tab)

  2. Code changes, week of 2026-08-31 – 2026-09-06 · at least 13 commits yonkoo11/erc8056-evidence

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in Yonkoo11/erc8056-evidence.

    How HEY read this week

    This week HEY looked inside 2 of 13 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 13 commits (opens in a new tab)

  3. Code changes, week of 2026-08-31 – 2026-09-06 · at least 7 commits yonkoo11/rhc-verify

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in Yonkoo11/rhc-verify.

    How HEY read this week

    This week HEY looked inside 1 of 7 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 7 commits (opens in a new tab)

Other changes on HEY’s record

34 changes on HEY’s record for Quorum: 11 releases · 2 new Verified Builders or owner proofs · 1 market check · 2 build pace changes · 18 other changes in 2 more kinds.

All 34 changes for Quorum →

The full change record holds 9 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

The token’s market, checks, locks and stamps below are context only: none of it changes activity status or Build Momentum.

Contract 0xa6452Fd7134218f62056a304eaf501F8714A26b9 on Robinhood Chain

0xa645…26b90xa6452fd7134218f62056a304eaf501f8714a26b9

Project names this contract: The owner proved control of the contract with an on-chain signature.

Market context

Active market · FDV (fully diluted) $26K · current liquidity $14.1K · reading under an hour old (DEX Screener).

Token

Launch stage
Trading in a DEX pool
Pair age
50d ago

Market

24h volume
$40K
Trades 24h
235 buys · 207 sells
Price 24h
up 62.4 percent over 24 hours· 6hdown 35.8 percent over 6 hours

The tracked token has liquidity and traded in the last 24 hours.

Market history, trading and checks →

Market integrity

Liquidity is 5% below the level it held two days running ($15.8K, 2026-09-21).

Market
Active market
Last day with trading
2026-10-30
  1. seen 2026-09-24Trading fell from 4,303 trades a day (the seven days to 2026-09-13) to 45 a day in the seven days to 2026-09-26, in HEY's decoded on-chain trades.

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-10-31 06:51 UTC · How HEY checks this

Locks

Token supply locked
1%
Opens
2027-09-15
Pair locked
Not applicable

Locked by HoodLock, read from the locker contract HEY watches. No locked pair holds this token; most pools on this chain have no pair token to lock. Locked supply says what cannot move today, not that the price will do anything.

Questions HEY can answer about Quorum — as of 31 Oct

Show the answers
Is Quorum still being built?
DerivedActive: 1 counted ship in 30 days; latest ship 28 days ago. Evidence
What did Quorum ship last?
FactCode changes, week of 2026-09-28 – 2026-10-04 · 27 commits — Code activity, 28 days ago. Evidence
Is 0xa6452Fd7134218f62056a304eaf501F8714A26b9 Quorum’s own contract?
FactProject names this contract: The owner proved control of the contract with an on-chain signature. Details
What does HEY not know about Quorum?
Unknown3 gaps: Official docs (no source), API description (not tied to the project yet), Official site changes (not tied to the project yet). HEY read its website and found no link to docs.

Sources

9 places HEY reads for Quorum