Zane retweeted
I keep returning to an oddly deliberate choice in @UnseenOrdo artwork: the figures show us their backs.
A portrait normally invites strangers to study a face. Here, we can recognize the silhouette, identify the work, and verify its place in the collection, but the figure still gets to turn away. Its other side is reserved for the UDA holder.
That simple decision raises a question I find much more interesting than the usual discussion around NFT rarity: how much of something do we actually need to see to know it's real?
Bitcoin RGB gives that question a technical foundation. Through client-side validation, asset state can be verified by the parties involved without exposing every detail to the entire network. UNSEEN builds on RGBMap's Private Collection standard, pairing publicly identifiable artwork with a private attachment intended for its holder.
What caught my attention is how closely that design fits the world they've created.
Take the Archivist, one of UNSEEN's five orders. An archive survives because knowledge can pass from one custodian to another without losing its integrity. A private digital artwork faces a similar challenge. When ownership changes, the next holder needs a reliable way to verify the piece and access its private side without turning that exchange into a public exhibition.
That's also where I think UNSEEN will face its most meaningful test. The private-content experience still needs to mature across wallets. And no encryption can make a previous owner forget an image they've already seen or saved. The real achievement would be making current ownership, verifiable provenance, and controlled access work together naturally.
There's something about this idea that reminds me of music. A score can preserve every note of a composition, yet it can never fully capture what those notes meant to the person playing them. I've always found that distinction beautiful. Something can be shared faithfully while part of its meaning remains personal.
I see the same possibility in UNSEEN.
If the technical experience delivers on what the artwork already suggests, those figures facing away might become the collection's most important design decision.
A stranger can verify that the portrait is genuine.
That doesn't mean the portrait owes them its face.
Zane retweeted
I watched @PlayRunevorn latest gameplay previews, and the crafting system caught my attention.
There's something interesting about a dungeon loop where the materials you collect from boss fights can shape how you prepare for the next encounter. I'm curious to see how Runevorn develops that experience.
In collaboration with @PlayRunevorn , I'm giving away 10 GUARANTEED WL SPOTS to my community ⚔️
🎮 3,333 Pixel Art MMORPG NFTs
🎟️ 10 GTD WL spots
💎 Free Mint | Date TBA
⏳ 24-Hour Giveaway
How to enter:
• Follow @PlayRunevorn & @AhoteSpirit
• Like & repost this post
• Reply with your favorite RPG class
I'll randomly select 10 eligible winners after 24 hours and contact them privately to collect their EVM wallet addresses.
One entry per person. No alt accounts.
Please don't share your wallet address publicly.
Good luck 🫡
Zane retweeted
THE SIGNATURE SCHEME CHANGES WHO CAN SEE.
Miden's private multisig can keep signer information out of publicly visible account state. Someone inspecting a treasury account onchain cannot simply retrieve its list of authorized signers.
But keeping a public key out of account storage doesn't necessarily keep it out of the transaction verification process.
OpenZeppelin documented this distinction in its audit of Miden's authentication components.
With ECDSA/secp256k1, signature verification uses a precompile that requires native re-verification. The transaction proof carries calldata containing the compressed public key, the signed message digest and the signature.
That information is needed by the verifier, which means the public key and signature become visible to the node operator and parties with access to the transaction submission or gossip path.
The account still stores a commitment to the public key. The disclosure happens through verification data, not because the account publishes its signer list onchain.
Falcon-512 with Poseidon2 follows a different path.
Its signature verification happens inside the proving circuit, avoiding the same public-key and signature calldata disclosure.
Both schemes can authenticate transactions, but they create different privacy boundaries.
For a private treasury, that distinction matters. Concealing reserves and signer commitments from public account inspection is one requirement. Limiting which infrastructure participants can observe the keys used to authorize transactions is another.
And Falcon alone doesn't guarantee anonymity. Operational disclosures, wallet interactions and other metadata can still reveal relationships.
OpenZeppelin explicitly documented the ECDSA disclosure path and recommended Falcon for integrations requiring signer-key privacy. The finding was marked resolved through documentation, rather than a change that eliminated ECDSA's disclosure behavior.
This is a useful reminder that privacy guarantees depend on more than the information an account stores.
The verification architecture determines what information must leave the user's environment, and who can observe it along the way.
Zane retweeted
The helmet hides the face. It also puts every other artistic decision under a microscope.
That's what interests me about @zkunnamed
.@heyitsnady is working with hundreds of helmets, pauldrons, chestplates, expressions and colors that all have to feel like they belong to the same medieval world.
In pixel art, even a few misplaced colors can change the weight of the armor or weaken a silhouette. Getting those combinations right takes serious discipline.
And there's something compelling about characters whose identities remain concealed, yet whose presence comes through in the smallest details.
My card is at the gates for the Second Wave.
Awaiting Judgement ⚔️
Zane retweeted
The part of a stock-paired NFT that interests me most begins when someone decides to sell it.
.@NFTX_ is introducing stock-denominated holder rewards and creator royalties alongside its NFT liquidity infrastructure. With @ThinkersClub_ preparing to bring stock-paired NFTs to Ink, there's one particular scenario I keep coming back to.
Imagine holding a Thinkers NFT while holder rewards accumulate, then selling it into a liquidity vault before the next distribution.
Who receives the rewards earned before that sale? Does the previous holder retain the claim? Does it follow the NFT into the vault? Or does eligibility depend on a snapshot taken at a specific moment?
Creator royalties and holder rewards are separate economic mechanisms. Understanding exactly how each works becomes especially important when an NFT can move between wallets, liquidity vaults and collectors.
There's a product idea I'd love to see explored here: a Pairing Passport.
A verifiable record showing what each NFT is paired with, where its rewards originate, how entitlements are calculated, and what happens to pending claims when ownership changes.
Ideally, a collector could inspect those rules before buying, swapping or selling, with the underlying logic verifiable onchain.
The mechanics of Thinkers haven't been fully revealed yet, so these are questions rather than assumptions about how the collection will operate.
But that's the part of this experiment I'm most interested in.
Because once financial rewards become part of an NFT's identity, understanding what happens between one owner and the next becomes essential to understanding what you're actually buying.
thinking_thinking_thinking_
Zane retweeted
I fed one hungry dog that morning.
By sunset, three of us were coming home.
I had woken up with no real plan, only the desire to walk into the forest.
Before I left, a hungry dog appeared outside. I brought him bread.
When I came back, a second dog was standing beside him, a beautiful spotted one, as if the first had somehow invited a friend.
I fed them both and thought that was the whole story.
It wasn't.
I put on my shoes and started walking.
They came with me.
Not for a few minutes. Not for the easy part of the path.
For twelve hours.
They moved ahead, stopped, looked back, and waited.
Sometimes one ran farther forward while the other stayed close, as if they had silently divided the work between them.
At one fork, I hesitated.
One way made sense to my mind. The other pulled at something quieter.
I followed that quieter pull.
They followed too.
Deeper in, when the trees closed around us and the forest grew still, I sat on a tree trunk and closed my eyes.
I meditated there for a long time.
The two of them stayed at the base of the tree.
Every rustle in the undergrowth sent them outward to investigate. Then they returned, settling near me again.
I have spent a lot of time alone in wild places.
But that day, something about being there felt different.
I never asked them to come. They simply stayed.
Yet every time I looked around, there they were.
On the way back, I lost sight of them for a while.
I stopped.
Somehow, I was certain they would find me before I found them.
They did.
When we finally returned home, I fed them again.
And I kept feeding them, morning and evening, until the day I left.
When I saw @IThinkItsArt asking people to share their stories, I thought of two hungry dogs and a piece of bread.
I left home alone.
Three of us came back.
Zane retweeted
i once asked a forest to remember me.
i sat on a thick branch against the trunk of an ancient tree and read something i'd written aloud. one line asked the forest to tell its trees that i would return.
i'd walked barefoot that day, watched sunlight break through the canopy and listened to leaves landing on the ground. there was nobody around to hear those words, yet that afternoon has stayed with me in a way photographs could never fully explain.
then i came across @nullsxyz and its invitation to "press start to remember."
the experience begins by asking players to recover five memories. those answers shape an original player card. from there, puzzles, games, challenges and community interactions offer opportunities to collect Memory Cards.
there's something interesting about the direction of that journey. you arrive carrying memories from your own life, then begin collecting new ones through experiences shared with other players.
but it also raises a question i'd love to see NULLS explore.
what happens to the story behind a Memory Card?
two players might earn the same reward from the same puzzle. one solves it in minutes. the other spends an entire evening exchanging clues with strangers, finally discovers the answer and remembers the people who helped long after the puzzle is forgotten.
the reward may be identical. the memory isn't.
NULLS hasn't confirmed a system that preserves those individual histories. but if the project eventually finds a way to connect collectible memories with the experiences and relationships behind them, "your story, saved" could become much more meaningful.
because years later, the number of cards someone collected might matter far less than the moments they still want to revisit.
i already know what it feels like to promise a place i'll return.
i'd love to discover a digital world that earns that same promise.
Zane retweeted
THE POWER TO PAUSE IS NOT THE POWER TO RESTART.
Imagine a bridge detects suspicious activity. Funds may be at risk, and every minute spent collecting approvals could increase the damage.
Now imagine the same bridge is ready to resume operations.
Should the person who can stop it immediately also have the authority to restart it alone?
Miden's approach to managing its own bridge infrastructure offers an interesting answer.
The team uses its private multisig to administer high-impact contracts, including those associated with Circle's CCTP bridge for USDCx.
And its approval requirements depend on the action being performed.
Pausing the bridge requires just one signer, allowing an immediate response to an emergency. Changing a USDCx attester key requires more signatures than adjusting the minimum withdrawal amount. Unpausing can require broader agreement.
That distinction matters because these actions carry different risks.
A pause is a containment measure. It can interrupt legitimate activity, but its immediate purpose is to prevent further exposure.
Restarting means accepting that the conditions for normal operation have been restored. If the original problem remains unresolved, reopening the bridge could expose users to the same danger.
Changing an attester key involves another kind of authority: deciding which credentials the system trusts.
A uniform signature threshold might appear simpler, but it ignores these differences.
There is a trade-off here. Giving one signer the ability to pause creates an availability risk if that signer is compromised or acts maliciously. Requiring broader approval for sensitive actions can make legitimate recovery slower.
Neither risk disappears simply because the system uses a multisig.
What matters is how authority is distributed across operations, and whether the approval policy reflects the consequences of each decision.
Miden's implementation illustrates why multisig security cannot be reduced to the number of people holding keys.
The deeper question is what each key is allowed to do, how quickly it can act, and what it takes to reverse the decision.
Zane retweeted
POLYMARKET'S NEW ENGINE TESTED 412X FASTER. THE BIGGER TEST IS WHETHER TRADERS CAN TRUST IT.
On November 13, Polymarket opened sandbox access to Nex, a trading engine rebuilt from scratch in Rust.
The headline numbers are striking.
In internal tests, p99 order placement latency fell from 1.55 seconds on the existing CLOB to 3.76 milliseconds on Nex, roughly a 412x improvement.
Order cancellation dropped from 627.92 milliseconds to 3.20 milliseconds. Sustained processing capacity is expected to rise from 10,000 to 100,000 commands per second.
But there's a detail in the announcement that deserves more attention than the speed benchmarks.
What does a successful cancellation response actually guarantee?
Under the existing system, a cancel-all request can return a response while the exchange is still cancelling orders in the background. According to Polymarket's engineering team, completing that process typically takes another 600 milliseconds to two seconds.
Nex changes the contract. Its response arrives only after the cancellations have actually completed.
For a market maker managing exposure across multiple outcomes, that distinction matters. An acknowledgement that a request was received is different from confirmation that the resting orders have actually been cancelled.
The WebSocket rewrite addresses another part of the same problem.
Polymarket reports that p99 WebSocket write latency fell from 44.5–88.1 milliseconds to 0.099 milliseconds in internal testing.
Faster market data could help participants update quotes before prices move against them. More predictable cancellations could help them manage exposure during sudden repricing.
Together, those improvements create the conditions for a healthier order book.
But they don't guarantee one.
A faster matching engine doesn't automatically produce tighter spreads, deeper liquidity or better execution for ordinary traders. Those outcomes depend on market-maker participation, competition, network conditions and how the entire system behaves under real trading pressure.
And there's an important boundary around the numbers published so far: these are internal exchange timings, not end-to-end trading latency measurements.
Nex is currently operating in shadow mode alongside production traffic, with a sandbox open for testing. Polymarket is targeting a conditional rollout in mid-December after four weeks of validation.
That makes the next phase more interesting than the benchmark itself.
Can the exchange maintain matching correctness and predictable cancellation behavior under sustained load? Will faster market-data delivery reduce stale quotes? And once Nex is live, will traders actually see improvements in spreads, available depth and execution quality?
Those are the measurements that will determine whether this rebuild changes the trading experience.
Polymarket has demonstrated a much faster engine in internal testing.
Now comes the harder task: proving that speed translates into a better market.
Zane retweeted
I just applied for a free Land Plot on @PlayPixelora, the pixel farm game on Robinhood Chain.
2,222 wallets get a free mint, picked at random. Connect X, finish 5 quick tasks and you're in the draw.
Apply with my link: pixelora.fun/whitelist?ref=9…
Zane retweeted
GERMANY ARE HEAVY FAVORITES. BUT HOW CONVINCING WILL A WIN BE?
Germany face Serbia tonight with roughly a 78% chance of winning on Polymarket.
Serbia have lost all four of their Nations League matches, while Germany have managed just one win from four.
The difference in squad quality helps explain why Germany are favored, but their results so far make the expected margin worth examining.
Look at how the market separates the outcomes:
Germany to win: 78%
Germany -1.5: roughly 58%
Over 3.5 total goals: roughly 46%
A 78% moneyline price makes Germany a strong favorite.
But the 58% price on Germany -1.5 means a victory by at least two goals is considerably less certain.
The gap between those prices also implies roughly 20 percentage points for a Germany victory by exactly one goal, using the displayed market prices.
That's a meaningful distinction.
Germany could win 1-0 and satisfy the moneyline without covering the spread.
They could win 2-0 and cover the spread while the match stays under 3.5 goals.
Or they could win 3-1 and satisfy all three outcomes.
Germany's modest scoring record in this Nations League campaign adds another reason to examine the margin rather than focus exclusively on the favorite.
But none of these prices tells us which exact scoreline will occur.
The market is pricing a range of possible outcomes, and the moneyline captures only one part of that picture.
Tonight, I'm watching whether Germany turn their advantage into a comfortable win, or whether the gap between being favored and winning convincingly proves just as important as the headline probability.
Zane retweeted
FRANCE ARE STILL FAVORITES. MBAPPÉ IS OUT. WHAT IS POLYMARKET PRICING?
France face Italy at San Siro tonight without Kylian Mbappé.
Zinedine Zidane has confirmed that the French captain isn't fully fit and won't be risked in this Nations League clash.
Yet Polymarket still favors France.
In the latest market snapshot:
France: 49%
Draw: 26%
Italy: 27%
France remain the most likely individual winner, but their price is now below 50%.
And that distinction matters.
Mbappé has already missed France's previous three matches, so his absence tonight doesn't necessarily represent completely new information for traders.
There's also a movement worth watching.
An earlier snapshot showed France at 52% and Italy at 24%. The latest prices put France at 49% and Italy at 27%.
That's a three-point shift in opposite directions.
But it would be premature to attribute that movement to Mbappé's absence without knowing exactly when the relevant information became available and how the market reacted.
The deeper question is how traders value France's remaining squad against Italy's home advantage.
France can be the favorite while the combined probability of a draw or an Italian victory remains greater than their chance of winning.
And even if France win tonight, that alone won't prove the market priced their missing captain correctly.
One match produces one result. A probability describes uncertainty across possible results.
What I'm watching before kickoff is whether France's price holds as the final lineups arrive, or whether traders continue reassessing the favorite.
Zane retweeted
.@RetiumChain October 29 release (node 3.0.31) quietly changed the lifetime of every transaction signing key.
The wallet still has one seed. The address still stays the same. But the key that signs one transaction is never trusted to sign another.
For transaction nonce i, the wallet uses key i from the same seed. Later keys are derived deterministically with BLAKE3, so there is no second backup or separate collection of secrets to manage.
The transaction also carries the hash of the key that will sign next.
The network checks that the current public key matches the hash it was already expecting. Once the signature is accepted, it stores the next hash and moves forward.
The public key that just appeared on-chain has already finished its job.
That changes the long-term security value of historical transaction data.
A blockchain keeps public data around indefinitely. If a signature scheme were weakened years later, historical public keys would still be available to analyze.
Retium’s design limits what recovering one of those old keys would achieve.
The chain is already waiting for a different key.
The key capable of authorizing the next transaction has not been exposed. Only its hash has.
This is a separate security layer from ML-DSA-44.
ML-DSA-44 defines the signature scheme. The one-key-per-transaction sequence limits how long any transaction signing key remains useful after becoming public.
It is also separate from Retium’s native 2FA and multisig design.
Those systems change who must participate in authorizing a transaction. This mechanism changes the lifecycle of the signing key used for that transaction.
There are limits, and they matter.
If someone gets the wallet seed, they can derive future transaction keys too. A compromised device can still sign something the owner never intended. Rotating transaction keys does not make endpoint security irrelevant.
What it does is reduce the value of a signing key recovered from old public chain data.
There is also operational complexity behind that protection.
A wallet has to know which nonce and which key hash the network expects next. A restored wallet must query the chain and continue from the correct point in the sequence. The SDK refuses to sign if the supplied seed cannot produce the key the network currently expects.
The October release was significant enough that Retium restarted the public testnet from a fresh genesis, moved transactions to payload version 6, and made the previous SDK incompatible with the new network.
That makes this more than a wallet-side security preference.
It changes what the network itself accepts as a valid next signature.
The next useful test is therefore not simply whether fresh keys are generated.
It is how reliably that state stays synchronized through wallet restores, failed submissions, multisig flows, 2FA and other conditions where transaction state can become messy.
Retium already chose post-quantum signatures.
With release 3.0.31, it added another assumption to the design: once a transaction signing key becomes public, its authority should already be over.
Zane retweeted
A token can gain 20% against its quote asset and still lose 16% in dollars.
With @MontraXYZ expanding into stock-linked pairs, that distinction matters more than ever.
I dug into what it means for token valuations, holder rewards and protocol fees.
Zane retweeted
spacerz has already revealed something interesting before its world fully opens.
look at the loop:
choose an identity.
complete missions.
climb the leaderboard.
come back tomorrow.
that's already a structured onboarding experience built around identity, contribution, competition and repetition.
but there's another detail worth watching.
official character reveals introduce names, classes and planets. that hints at a world with its own internal identity system, beyond simply choosing one of four classes on an application page.
here's the question i find most interesting:
will the identity people choose and the effort they invest today have a meaningful place inside the actual Spacerz universe tomorrow?
because points can attract a crowd.
a world where participation has meaning can give that crowd a reason to stay.
that's the evolution i'm watching from @SpacerzNFT 👾
Zane retweeted
THE WALLET IS PRIVATE. THE JOURNEY ISN'T.
Bread Wallet introduces an interesting question about financial privacy that becomes much more important once users start doing something with their assets.
Keeping a balance private is one thing.
Putting that balance to work in a public lending market is another.
A recent Xangle report examines how Bread brings Miden's private account architecture into everyday wallet functions, including transfers, swaps, cross-chain movement, and Earn.
The Earn feature is where one of the most important boundaries becomes visible.
Bread allows users to deposit USDCx from Miden into external lending markets.
According to the report, users can access six lending markets: Aave V3 and Compound III across Ethereum, Base, and Arbitrum.
The process is relatively straightforward from the user's perspective.
They hold USDCx in Bread.
They choose an external lending market.
The assets move out of Miden, and USDC is supplied to the selected protocol on the destination chain.
Their position and returns can then be monitored from the same wallet.
But something changes during that journey.
The location of the assets changes. And so does the privacy model protecting them.
Inside a Miden private account, detailed balances and account state are not published to the public ledger.
Instead, the network records commitments and verifies the validity of account updates.
That protects information which would ordinarily be visible in a conventional public blockchain account.
But Aave and Compound operate on public networks.
When funds enter those lending markets, the relevant deposits, position changes, and returns may become observable through public onchain records.
The wallet interface may remain the same.
The privacy guarantees do not.
Consider a hypothetical user holding 50,000 USDCx in a private Bread account.
An outside observer cannot simply inspect the account's public state and read that balance.
Now suppose the user moves 20,000 USDCx into a lending market on Base.
The external transaction may publicly reveal a deposit of approximately 20,000 USDC, alongside the address interacting with the lending protocol.
The transfer into the public network can also expose information at the bridge boundary, including amounts and destination-side activity, depending on the route and its implementation.
That is a real disclosure of financial activity.
But it does not necessarily mean an observer can identify the original private Miden account, establish its complete balance, or attribute every other transaction belonging to the same user.
Those are separate questions.
Visibility of an external deposit is not the same as visibility of the private account behind it.
The distinction matters because privacy is often described as though it were a permanent property of an asset.
Once private, always private.
But financial activity doesn't stay inside a single execution environment.
Assets move through bridges.
They enter lending protocols.
They interact with liquidity markets.
They return to wallets.
And each environment has its own disclosure rules.
A private account cannot automatically impose its confidentiality model on a public lending protocol that was never designed to preserve it.
Nor does returning funds to Miden erase the public records created while those funds were outside it.
When withdrawn assets arrive back in a Bread private account, the account's detailed state is again protected.
The earlier external deposits, withdrawals, and other publicly recorded activity remain visible on the destination chain.
That creates an important difference between protecting a balance and protecting an entire financial journey.
A wallet can conceal what someone currently holds without concealing every action they previously took elsewhere.
And the reverse can also be true.
Public activity on an external chain does not necessarily reveal everything about the private account from which the assets originated.
The actual privacy outcome depends on what the bridge reveals, how external addresses are used, which records can be correlated, and what additional information observers already possess.
This is not merely a theoretical distinction.
For an individual using Earn occasionally, a visible deposit may reveal relatively little beyond the size, timing, and destination of one lending position.
For an institution repeatedly deploying treasury funds into the same external markets, the consequences can be different.
Recurring deposit amounts, timing patterns, withdrawals, and reused addresses may expose aspects of its liquidity management or investment strategy.
Even if its full Miden account state remains private.
That is why evaluating financial privacy requires following the workflow rather than examining the wallet in isolation.
What can observers see before the transfer?
What becomes visible during the bridge operation?
What does the destination protocol publish?
Can separate activities be linked?
And what information remains protected when the assets return?
These questions do not invalidate Bread's privacy architecture.
They define the conditions under which its protections apply.
They also reveal a practical tradeoff.
Bread is making external financial services accessible from a private wallet without requiring every connected protocol to adopt Miden's architecture.
That expands what users can do with their assets.
But interoperability with public finance also means accepting the disclosure characteristics of the systems being used.
Miden is working toward confidential swaps and more private cross-chain transfers, which could reduce some of the information exposed along the way.
Those developments should not be confused with privacy guarantees already available across every external service.
Even a more private transfer mechanism would not, by itself, make an ordinary public lending market confidential.
The larger challenge is not simply moving assets between private and public environments.
It is understanding what information crosses with them.
A private wallet can protect where your money is held.
Protecting what your money does requires looking beyond the wallet.
A new @Xangle_official's report by @jundeu00 examines how Bread makes Miden’s privacy infrastructure accessible to everyday users.
Read below👇
Zane retweeted
My favorite part of Ascend is what happens after the initial launch.
The progression from Ascended Status to HyperCore Spot and eventually HIP-3 perps gives projects a potential path into deeper market infrastructure.
That matters because launching a token is only the first step. Building sustained market activity is the harder challenge.
I’m particularly interested in seeing how Ascend executes this pipeline on Elysium.
The Ascend Token Catalyst Pipeline. ↗️
At Ascend we have built an entire pipeline of catalysts designed to help projects grow and reach their full potential by leveraging Hyperliquid’s infrastructure.
Launch → Ascended Status → HyperCore Spot → HIP-3 Perps → Ascend Strategic Partner
And because we have no separate Ascend token, our priority remains the projects launching with us. We want these tokens to grow freely without unnecessary ceilings holding them back.
Ascend is becoming the growth engine of the entire Elysium ecosystem, and we’re actively looking for promising teams to support.
To celebrate our upcoming launch, we’re giving away 5 whitelist spots to our community.
To enter:
* Follow @AscendLaunch
* Like and repost this tweet
* Quote tweet describing your favorite feature of Ascend.
We’ll be selecting whitelist winners in 24 hours.
Ascend to Elysium
Zane retweeted
BASE MADE BLOCKS 10X FASTER. THE HARDER PROBLEM IS WHAT GETS INTO THEM.
On November 5, Base activated Denim, replacing its two-second canonical blocks and intermediate Flashblocks with a new canonical block every 200 milliseconds.
Five canonical blocks per second. No separate preconfirmation stream to reconcile. A meaningful architectural upgrade.
But the rollout exposed a different problem.
Base acknowledged periodic transaction inclusion delays and a higher-than-expected rate of empty blocks after activation.
That distinction matters.
A blockchain can keep producing blocks on schedule while users still wait for their transactions to land.
And the engineering work happening inside Base's transaction pool reveals why reducing block time is only part of the challenge.
Validity Transactions allow execution to depend on specific conditions. Some can remain in the pool until those conditions become true.
The problem is what happens when a block builder repeatedly examines thousands of transactions that aren't ready to execute.
In a local benchmark involving 75,000 dormant transactions, an experimental optimization reduced median per-block processing time from 96.4 milliseconds to 0.48 milliseconds.
Nearly 200 times faster in that specific test.
But this is not a measured mainnet improvement. The proposal remains a draft, and the optimization is off by default in the proposed implementation.
Nor does the benchmark establish that dormant transactions caused the inclusion delays reported after Denim.
What it does reveal is how expensive transaction selection can become when the block-building window shrinks.
At 200 milliseconds per block, wasted processing time matters.
A faster clock creates more opportunities to include transactions. It also makes inefficient work inside each opportunity harder to ignore.
This is where Base's next scaling challenge becomes interesting.
Denim changed how frequently the network produces canonical state. Now the infrastructure responsible for selecting and including transactions has to make those opportunities consistently useful.
For trading, payments, liquidations and autonomous agents, predictable inclusion matters alongside nominal block time.
Denim is a real step forward.
But the next measure of progress won't be how quickly Base produces another block.
It will be how reliably transactions make it into one.
Zane retweeted
Real Madrid are overwhelming favorites against Valencia tonight.
But Polymarket is telling three different stories about what that advantage might look like.
Madrid are priced at roughly 79% to win.
Their chance of covering -1.5 (winning by at least two goals) sits around 55%.
And the probability of the match producing more than 3.5 goals is only around 44%.
These aren't contradictory signals.
They're different questions.
The moneyline asks who finishes ahead.
The spread asks how large the winning margin might be.
The total asks how many goals both teams produce together.
Madrid can dominate the game without turning it into a goal festival.
They can also win comfortably while the match stays under four total goals.
And a high probability of winning doesn't eliminate the possibility of a narrow result.
That's why a favorite's moneyline alone tells an incomplete story.
The interesting part of tonight's market isn't simply that Madrid are expected to beat Valencia.
It's how much confidence traders have in the manner of that victory.
A strong favorite is one thing.
A guaranteed comfortable win is something else entirely.
Zane retweeted
Institutions don't necessarily need another private blockchain.
They need a way to operate without exposing everything about their business.
That distinction is at the center of something Miden co-founder Dominik Schmid said during his recent Devcon interview.
"We need to understand way better what institutions need and want on a blockchain, and then build something for them. I also think that it must be on a public permissionless network."
There are two important ideas in that statement.
The first is that institutional requirements cannot simply be inferred from what blockchain technology already makes possible.
The second is that meeting those requirements should not automatically mean moving financial activity onto a closed network.
For years, institutional blockchain discussions have often treated privacy and permissionlessness as competing priorities.
Public networks offer shared infrastructure, open participation, and independently verifiable rules.
But they can also expose financial information that institutions have strong reasons to protect, including balances, counterparties, payment amounts, trading strategies, and commercial relationships.
For an institution, revealing that information isn't necessarily a matter of personal preference.
It can create competitive disadvantages, expose clients, or conflict with confidentiality obligations.
A permissioned network can restrict who participates and who sees certain information.
But that introduces a different set of questions.
Who controls access?
Who decides which institutions are allowed to participate?
What happens when organizations need to transact across networks operated by different groups?
And how much of the original promise of shared, open financial infrastructure survives those restrictions?
Miden is approaching that tension from a different architectural direction.
Instead of requiring every transaction to expose its full underlying state to the public network, Miden is designed around local execution and client-side proof generation.
The user's device performs the computation.
The network verifies a cryptographic proof and records the relevant commitments.
For private account transactions, this means the public network can verify that the required rules were followed without publishing the account's underlying private state.
The network doesn't need to publish every balance or payment detail to establish that an account update is valid.
That matters because public verification and public disclosure are not the same thing.
A financial system can make its rules independently verifiable without requiring every participant to reveal every piece of business information.
But there is a second distinction that is just as important.
Privacy is not compliance.
An institution may need to keep its positions confidential from competitors while still proving specific facts to auditors, regulators, or authorized counterparties.
Those are different requirements.
A system that hides everything from everyone may protect confidentiality but still be difficult to integrate into regulated financial workflows.
And a system that supports selective disclosure does not automatically satisfy the legal, operational, and reporting obligations of every institution.
The real challenge is deciding what must remain private, what must be provable, who is entitled to receive particular information, and under what conditions.
That requires more than cryptography.
It requires policies defining disclosure rights.
Identity and access controls that can be administered and audited.
Recovery procedures that work when employees leave, devices fail, or authorized signers change.
Reporting mechanisms that produce the records institutions are legally required to maintain.
And integrations that continue functioning when assets move between networks, custodians, and financial services.
A private transaction is only one step inside a much larger institutional workflow.
This is why Dominik's admission about understanding institutional needs is significant.
Building a technically sophisticated private execution environment is one problem.
Turning it into infrastructure that institutions can actually adopt is another.
And the second problem cannot be solved entirely inside a proving system.
There is also an important distinction between Miden's architectural destination and its current rollout.
During Partner Mainnet, validators still re-execute transactions as an additional security measure and therefore receive private transaction inputs.
The network is also initially operating with restricted participation and a gradual decentralization plan.
Those safeguards are deliberate, but they mean the present deployment does not yet provide every property of the intended permissionless, proof-verification-only model.
Similarly, the ability to protect private account state should not be mistaken for universal confidentiality across every financial activity.
Public swaps can expose assets and amounts.
Interactions with external networks can reveal transfer information outside Miden's private account environment.
And an institution may have to disclose information to counterparties or service providers to complete an otherwise legitimate financial operation.
For institutions, these boundaries matter.
A privacy claim is only useful when an organization understands exactly where it applies, where it stops, and which parties must still be trusted.
Dominik also described the need to learn from actual usage rather than treating architecture alone as proof of readiness.
That is the right test.
Not whether a blockchain can demonstrate privacy in isolation.
But whether institutions can perform real financial operations, meet their disclosure obligations, recover from failures, interact with external services, and rely on the system over time.
The interesting possibility Miden is pursuing is not simply bringing institutions onto a private blockchain.
It is making public financial infrastructure compatible with information that should never have been public in the first place.
Whether that becomes a viable institutional model will depend on what gets built around the cryptography, and how well those capabilities survive real operational demands.
The remaining question is no longer simply whether private transactions are possible on a public network.
It's whether institutions can actually operate there, with all the controls, disclosures, recovery mechanisms, and external dependencies that real finance requires.
“Client-side proving is the holy grail for privacy because what leaves your device is only the proof." - @schmiddominik1
Dominic says Miden's partner mainnet has around 1,000 users one week in, and he expects to open it up in January.
I asked the @0xMiden co-founder how Miden balances privacy with what institutions need.
> How do you balance strong privacy with the compliance and selective disclosure institutions need?
> What advantages does client-side proving give users and institutions, and what are the tradeoffs?
> What have you learned from real usage on partner mainnet so far?
> How is Miden different from other privacy-focused chains?
> What insight made you spin out of Polygon and double down on Miden?
> What does successful institutional adoption look like over the next one to two years?
Full Q&A👇

























