Active development: 100+ commits in the last 90 days across 2 contributors
Code ActivitySource linked
7 active day(s) in yonkoo11/quorum.
StockFi · Utility
Verified BuilderA 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.
Code ActivitySource linked
7 active day(s) in yonkoo11/quorum.
Code ActivitySource linked
1 active day(s) in yonkoo11/hey-redesign.
View evidenceCode ActivitySource linked
7 active day(s) in Yonkoo11/quorum.
View evidenceCode ActivitySource linked
1 active day(s) in Yonkoo11/hey-redesign.
View evidenceGithub ReleaseSource verified
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 false
View evidenceGithub ReleaseSource verified
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 evidenceCode ActivitySource linked
4 active day(s) in Yonkoo11/quorum.
View evidenceGithub ReleaseSource verified
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/[email protected]) 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 member
View evidenceGithub ReleaseSource verified
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/0xa648821d91093df770b72c60be56834d069c9355c785e6195183e911f00bf713
View evidenceCode ActivitySource linked
3 active day(s) in Yonkoo11/erc8056-evidence.
View evidenceCode ActivitySource linked
1 active day(s) in Yonkoo11/rhc-verify.
View evidenceWritten by Dawnscan researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.
No published notes on Quorum yet.
Know something about Quorum? Sign in with wallet to submit a research note. Notes are reviewed before they appear here.