Loading…
Coinsider Host called it:
“The long-term target is around 10,000 transactions per second directly on Ethereum”
On the record 24 days and counting. Nobody can edit it, including Coinsider.
No machine-checkable test was locked with this record, so it is preserved rather than scored. Thonest never invents a threshold or deadline the speaker did not give.
This is kept for what it is: something said, on a date, from a source anyone can check. No test was locked, so nothing settles it and it is never counted for or against anyone. Thonest will not invent a threshold or a date that was never said — a claim scored against criteria written afterwards would prove nothing.
Submitter-attested — no machine-readable source
Added by @sam. The contributor is credited for finding the source, never trusted for the wording — that is verified against the source itself.
Watch what they said — from 12:27 ↗
Reactions are about the record being worth keeping — never about whether the person was right. They are never counted for or against anyone, and never used to rank anything.
Discussion
Loading…
The goal is to make Ethereum's base layer dramatically faster, more efficient, and capable of handling far more activity on its own. The long-term target is around 10,000 transactions per second directly on Ethereum, which is way more than what they can do today. The long-term target is around 10,000 transactions per second directly on Ethereum
Transcribed from the audio and confirmed by the submitter, who listened to this passage. YouTube confirms the video and the channel, not the words — those are checkable in one click by anyone. Watch the full moment →
From the video "I Haven’t Been THIS Bullish on Ethereum in 3 Years".
History — append-only
Proof
Disputes
No disputes have been filed. If something here is wrong — a misquote, a wrong date, a misattributed source — say so and it gets answered on the record. How disputes work.
✓ The anchored proof cannot be rewritten, and the published record is append-only by default. Everything that happened afterward is in the history above — corrections are appended, never silently edited in.
The check runs in your browser and reads the anchored root straight from a public Base node — not from Thonest. How this works.