Quorum now takes findings from any tool, not just its own scanner.
You commit a fingerprint of your proof on chain and burn the fee, then reveal it after the fix.
First claim is live on the registry: contents hidden, time and fingerprint are public.
Anyone can hit Check and verify it against the chain themselves.
Quick update.
We aimed Quorum at a fresh batch of Robinhood Chain contracts.
Swap routers and token contracts that move money, not the large audited set we had already checked.
The engine flagged a few suspicious spots and tried to break them.
Copy the live chain. Run the attack. Show the money leave.
It could not make a single one pay out.
All three were dropped.
No "possible bug, be careful."
Either we hand you proof the attack ran, or we tell you there is nothing.
This week there is nothing.
We post that as plainly as a win.
Prove it. Or drop it.
my private hunting tool (soon to be open-source and @runQuorum played a huge role in helping me trace these
SHIELDS UP
i really hope the attitude of the average crypto users and industry leaders changes after this
i still remember telling my close friends their cryptos are SAFU with binance because the risk of hacks were relatively low and their funds were backed the insurance fund
yet binance got hacked
i really hope this is serves as the final wake-up call for more investments into the neglected security space
hacks such as this damage the already underwhelming reputation of crypto among the masses generally
we need to put and end to them by preventing as much hacks as possible and creating emergency response security teams and alerts to support the current alert systems such as @blockaid_ @ShieldifySec etc
i traced the @binance hack on-chain
~$6.3B left hot wallets used on a daily basis, about $3B is frozen.
binance say they will cover all of it from their insurance fund (SAFU) and company money, withdrawals are currently paused
binance initially pointed at a DevOps engineer’s work PC being the source of the hack, not a stolen private key
it’s now suspected that the hack comes from more than one factor, and that computer may be the entry point.
the full report isn’t out yet
on ETH, i recovered 50 spending permissions signed by binance’s own wallet. only 1 went through.
the other 49 were already out of date.
that same wallet kept sending normal txs during the theft, the attacker didn’t lock them out.
around 00:10 UTC extra spending permission was turned off
a little ETH is still sitting in that hot wallet, the stolen ETH is in the five wallets further down.
the attacker’s wallet that pushed the permissions got funded through a mixer
note that a mixer doesn’t tell you who funded it.
five ETH wallets still hold what left. none of them has sent a tx.
197,460 ETH
0x8532FA14ACAf483729C449b8458aedDb900543D4
137,602 ETH
0xc887aF690E0301CD4edBbCe8F8d31b4EC65B286A
78,415 ETH
0x897C80d1a9729E94460e2Bd93178bD5215158DF3
32,954 ETH
0x54401f80Da97893a15D43566184635B6674BC942
19,740 ETH
0x79e70d139fC05AA75F75611fDF2680E9952B544A
QUORUM retweeted
We pointed Quorum at the 20 largest money-holding contracts on Robinhood Chain.
Together they represented more than $400M.
The result: no exploitable bugs we could confirm.
Most of the code was standard and well built.
That is a result from that run.
It is not a certificate for the next block.
We are working down the list and will publish what we can prove.
Keep up with our updates:
t.me/runQuorumchat
We pointed Quorum at the 20 largest money-holding contracts on Robinhood Chain.
Together they represented more than $400M.
The result: no exploitable bugs we could confirm.
Most of the code was standard and well built.
That is a result from that run.
It is not a certificate for the next block.
We are working down the list and will publish what we can prove.
Keep up with our updates:
t.me/runQuorumchat
QUORUM retweeted
An upcoming design would let independent operators run checkers and stake to show they are separate.
That design is not in the current tool.
There is no release date year as of now.
Four constraints remain open:
-Checker versions have to be pinned, or results are not reproducible. The required strictness is not settled.
-A weak checker is not a dishonest one. Penalties do not fix low coverage.
-Checkers that are too similar can pass validation and still fail the independence test.
-Below a sufficient number of participants, independence is not meaningful. That threshold is not set.
The current product does not depend on this design. For now, prove it or drop it
runquorum.site/
An upcoming design would let independent operators run checkers and stake to show they are separate.
That design is not in the current tool.
There is no release date year as of now.
Four constraints remain open:
-Checker versions have to be pinned, or results are not reproducible. The required strictness is not settled.
-A weak checker is not a dishonest one. Penalties do not fix low coverage.
-Checkers that are too similar can pass validation and still fail the independence test.
-Below a sufficient number of participants, independence is not meaningful. That threshold is not set.
The current product does not depend on this design. For now, prove it or drop it
runquorum.site/
Dev stays shipping
🧵 Yesterday an hacker drained wallets i believe belong to @TheGodMurdoch
The hacker’s address was flagged by @GhostcatJoypad in the comments of the quoted tweet
Hacker: 0x0a3c30a8b184d828ae808035e06f02a21b9bc08c
I traced about 5.3 ETH (~$13K) through it so far
2
5
469
Have a contract you don't fully trust?
Send us a hypothesis.
Chain. Address. Block.
One line describing what you think can go wrong.
Quorum takes that hypothesis to a fork and tries to make it happen.
If the exploit succeeds, the result is PROVEN. If it doesn't, you get UNPROVEN, with a reason.
A suspicion is easy to post.
A claim you're willing to test is more useful.
QUORUM retweeted
Another day to remind you.
The goal is not a scanner that always has something to say.
The goal is a scanner that knows when it has enough reason to speak.
That is Quorum.
Six independent lenses read the contract.
No single lens can publish a finding.
Two have to reach the same conclusion, for different reasons.
Sometimes they do not.
The report stays quiet.
We are trying to make every line on the results mean something.
Still building. Still testing.
runquorum.site
Another day to remind you.
The goal is not a scanner that always has something to say.
The goal is a scanner that knows when it has enough reason to speak.
That is Quorum.
Six independent lenses read the contract.
No single lens can publish a finding.
Two have to reach the same conclusion, for different reasons.
Sometimes they do not.
The report stays quiet.
We are trying to make every line on the results mean something.
Still building. Still testing.
runquorum.site
One of the hacks was run blind.
We replayed four real 2026 incidents to the amount stolen:
Unistreet, Sandbox, Squid, and GaslessReservoir.
The last one was a hack the operator had never read.
No walkthrough. No head start. The tool had to get there on its own.
We also publish the number most security writeups leave out.
Quorum catches roughly 2 in 3 known bugs.
The misses stay next to the hits.
We keep improving and adding updates
Prove it or drop it
runquorum.site/
QUORUM retweeted
Last week updates.
We rebuilt Quorum because a flag was too easy to believe.
A bug is not real NOW until the tool writes the attack, runs it on a fork of live state, and watches the money move.
If the money does not move, it stays off the report.
You give it a chain, an address, a block, and a one-line hypothesis.
PROVEN if it pays. UNPROVEN if it does not, with a reason.
It still does not watch the room.
A compromised laptop or a hot wallet drained by a third-party tool stays outside the report.
Bitget was that case. Quorum would not have caught it.
An empty report is not a certificate of safety.
It is the tool refusing to guess.
Prove it or drop it.
runquorum.site
Last week updates.
We rebuilt Quorum because a flag was too easy to believe.
A bug is not real NOW until the tool writes the attack, runs it on a fork of live state, and watches the money move.
If the money does not move, it stays off the report.
You give it a chain, an address, a block, and a one-line hypothesis.
PROVEN if it pays. UNPROVEN if it does not, with a reason.
It still does not watch the room.
A compromised laptop or a hot wallet drained by a third-party tool stays outside the report.
Bitget was that case. Quorum would not have caught it.
An empty report is not a certificate of safety.
It is the tool refusing to guess.
Prove it or drop it.
runquorum.site
QUORUM retweeted
Your scanner found 20 issues.
How many would you actually trust?
That's something we've been thinking about while building Quorum.
A scanner can flag something suspicious, but that doesn't automatically make it a bug.
So we built Quorum to be stricter.
It has 6 independent lenses. one can't report a bug on its own. two have to agree, for different reasons.
Sometimes, nothing makes it into the report.
We'd rather have a finding earn its place than give you another thing to investigate for no good reason.
still building. still testing. more to share as we go.
runquorum.site
Your scanner found 20 issues.
How many would you actually trust?
That's something we've been thinking about while building Quorum.
A scanner can flag something suspicious, but that doesn't automatically make it a bug.
So we built Quorum to be stricter.
It has 6 independent lenses. one can't report a bug on its own. two have to agree, for different reasons.
Sometimes, nothing makes it into the report.
We'd rather have a finding earn its place than give you another thing to investigate for no good reason.
still building. still testing. more to share as we go.
runquorum.site
QUORUM retweeted
Another day to inform you that Quorum does not start with a verdict.
It starts with a guess you have to write down.
Give it a chain, an address, a block, and a one-line hypothesis.
It will try to make that hypothesis pay on a fork of live state.
If the money moves, the result is PROVEN.
If it does not, the result is UNPROVEN, with a reason.
A checker having a feeling is no longer the report.
The report is what survived the attempt.
Another day to inform you that Quorum does not start with a verdict.
It starts with a guess you have to write down.
Give it a chain, an address, a block, and a one-line hypothesis.
It will try to make that hypothesis pay on a fork of live state.
If the money moves, the result is PROVEN.
If it does not, the result is UNPROVEN, with a reason.
A checker having a feeling is no longer the report.
The report is what survived the attempt.
What Quorum does not do: it does not watch the room. It reads the contract.
It will not see a compromised laptop.
It will not catch a hot wallet drained by a third-party tool.
The recent Bitget incident is a good example. The loss was not in the contract our scanner reads, so Quorum would not have caught it. An empty report there would have been the honest one.
You may still open a report and find nothing in it.
That does not mean the checkers sat still.
Some of them may have noticed something but none of them are allowed to publish it alone.
Two have to agree, from different evidence, before a finding exists.
If they do not, the page stays empty.
If the loss never lived in the contract, it stays empty for a second reason.
An empty report is not a certificate of safety.
It is a scanner with a strict rule.
The rebuild made that rule harder.
A bug is not called real until the tool writes the attack, runs it on a fork of live state, and watches the money move.







