Even when a layer-2 network controls its own proof system and account model, it may still inherit cryptographic assumptions from the layer that settles its proofs and stores its data.
Data availability is often provided by blobs and the bridge messaging layer may rely on specific elliptic-curve precompiles.
Those components will become post-quantum only when the settlement layer itself completes its migration.
Until then, a rollup’s end-to-end security cannot exceed the security of its settlement layer for the properties that depend on that layer.
@Starknet published roadmap explicitly separates work that is under its own control such as hash replacements, account-level signature upgrades, and migration tooling from work that depends on the settlement layer.
The recent non-binding governance discussion about researching an independent layer-1 path is one way of examining whether removing that dependency is desirable.
An independent chain could set its own timeline for consensus signatures, data availability, and bridge design, but it would also forgo the existing security and liquidity relationships that come with settlement on another chain.
The trade-off is therefore not purely technical; it involves assumptions about relative migration speeds, bridge risk, and ecosystem effects.
Documenting the dependency clearly, rather than claiming full independence prematurely, is itself a form of cryptographic transparency.
Users and builders can then evaluate how much residual exposure remains and whether additional measures are warranted while external components catch up.
Flare passed its value-accrual rule in April with 98 percent support. The pool that rule created has collected $50,003 since May. The emission it is meant to replace runs to about $22 million a year. I hold FLR, so read on with that in mind.
FIP.16 did everything a holder could ask for on paper. Inflation cut from five to three percent, hard cap three billion FLR a year. Base gas fee up twentyfold and burned in full. A revenue pool named FIRE collecting ninety percent of data-connector fees, FAsset minting fees, a tenth of redemption fees, confidential-compute fees and, once block building changes ship, protocol-level MEV. Stated purpose: replace inflation with organic yield for stakers, buy and burn the rest. Staked FLR rose from sixteen to twenty-one and a half billion after the vote.
Then the dashboard. $24,700 from FAsset minting. $22,800 from the data connector. About $2,000 from redemptions. A few hundred from tag registrations. September's pace is fifteen to twenty thousand dollars a month against an emission worth roughly $22 million at current prices. Cumulative coverage: about 0.2 percent. On run-rate: under one percent.
None of that is a failure of the design. The largest intended revenue sources have not launched. It means the yield I receive as a staker is financed by inflation, and inflation-financed yield is rented. Flare will own its depth when FIRE pays for it.
Ethereum ran the same sequence in the other order. EIP-1559 landed in 2021 on a network that already had blockspace scarcity, so the burn was material from the first week. Flare installed the rule before the customers. That may be the only way a smaller network can make the rule credible. A rule is still priced as a promise, and a promise is priced differently from a cash flow.
The gap between XDP and FLR is that Flare wrote the rule into protocol and made the number public. The gap between FLR and HYPE is that Hyperliquid's number is large.
I will publish the ratio every quarter: FIRE inflow in dollars over FLR emitted times the quarter's average price. Two conditions before I call Flare an accrual network: above ten percent for two consecutive quarters, and the dollar inflow itself higher than the quarter before, because a price crash alone can clear the first bar. Ten percent is a judgement, stated now so it cannot move later.
What is the number at which you would call a promise a cash flow?
Morning all. The garden's a mess after the storms, carpeted in dead flowers, fallen leaves & sycamore keys, & badly needs a sweep up. Meanwhile here are some of the tricolor dahlias from a few weeks ago. The dahlias are all finished now & will soon go into winter storage. 👏👏👏
If someone verifies a spatial capture, what makes them accountable for getting it wrong?
@vangrid_io’s planned verification system puts collateral behind that judgement. Its token documentation describes independent operators staking $VAN before reviewing assigned captures. In simple terms, they would commit tokens that could be partly lost if their attestation disagreed with the resolved outcome.
The assignment process matters too. Captures would be allocated pseudorandomly, so contributors couldn’t choose their reviewer and reviewers couldn’t simply select the submissions they preferred.
An important status check: VanGrid currently marks both $VAN and independent verification under collateral as not live. This is a proposed mechanism, separate from the checks already operating today.
Imagine a capture that passes basic technical checks but contains a misleading claim about the scene. The harder question is whether someone can evaluate that claim reliably—and face consequences for a false attestation.
That is the role collateral is intended to play. It creates something at stake behind the reviewer’s decision. It doesn’t make every decision automatically correct.
For me, the most interesting part to watch is how disagreements would be resolved. Who establishes the final outcome? What evidence supports it? How are honest mistakes distinguished from deliberate misconduct?
Those details would determine how useful the incentive becomes. I’d judge the design by the quality and accountability of the review process, rather than treating the presence of a token as proof that verification works.
Pretty pink flowers!🩷🌸
These bright pink Madagascar periwinkles (also called pink vinca) look so happy in their pots. Glossy green leaves and cheerful blooms — perfect for any garden! 🌸
Chamath Palihapitiya just warned about a quantum or AI attack on Satoshi-era Bitcoin wallets. 🚨
The concern: a quantum machine running Shor's algorithm could break ECDSA signatures and expose private keys from public ones.
But in real, no such machine exists yet.
Crypto's counter: a decade of battle-tested security culture is a real edge over traditional finance.
And builders are already moving:
• Quip Network is working on post-quantum wallets for Ethereum and Bitcoin
• Ethereum has upgrades planned for 2029
• Industry alliances are forming around standards
It's not a panic signal. A preparation signal.
🔥 $BMNR MASTERMIND TOM LEE
THINK BANKS SHOULD ADAPT CRYPTO!👇
Tom Lee, chairman of the largest $ETH treasury Bitmine says 99% of finance still runs on pretty old rails, and that's exactly why banks are underestimating how extremely fast crypto could take over.
Banks without a real crypto plan could get left behind completely!
I think as a bank you have to transform from TradFi to DeFi.
Tokenized RWA’s, stablecoins and AI agents with huge amount of transactions need crypto rails.
Do you agree with Tom Lee?🤔
I recently took a look at the REA service from @termix_ai , and what I find particularly interesting is that it doesn’t just offer to "read" and interpret complex, hard-to-decipher content it also leaves a trail of evidence, allowing you to verify the findings yourself.
A common, practical question arises when encountering an unverified smart contract: what can actually be gleaned from the bytecode running on the chain? REA addresses this by extracting interfaces directly from the bytecode even for contracts where the source code is unavailable.
Beyond that, it handles ELF/PE binaries (generating pseudocode, disassemblies, call graphs, etc.), JS/Electron applications (mapping modules, imports, URLs, or embedded keys), and even .NET assembly. What stands out to me isn't just the final output; it’s that every discovery is linked to an "evidence ID" and the SHA-256 hash of the original artifact.
This allows the recipient of the report to cross-reference the exact data that was analyzed, rather than having to take the agent’s word for it. Of course, reconstructing an interface remains an inferential process; a matching hash only confirms the source material used it doesn't automatically render the conclusions absolute truth, nor does it guarantee that the software is secure.
The transaction process follows the "agent commerce" model that TermiX is building: quotes start at around $10, with a turnaround time of about a day. Terms are negotiable, and funds are held in an escrow account on the BNB Chain until the requester accepts the report. It’s a concrete example of an agent taking on a specific task, delivering verifiable results, and only then triggering the release of payment.
Ultimately, the true value of such a report lies in whether the provided evidence enables the user to independently verify the findings and gauge the level of certainty or uncertainty surrounding them.
If a service simply provides an answer and stops there, its utility is largely fleeting. But if the evidence is clear enough to allow others to build upon it or conduct further investigation, then it becomes genuinely useful.
Scribely is getting some solid daily traffic lately 📈
thinking of adding a few sponsor spots for fellow indie hackers & SaaS founders to get some extra visibility.
worth a shot? 👀