It’s down more than 50% from the top. Gold is eating its lunch. Stablecoins quietly stole its original job. But the story everyone’s arguing about is the wrong one.

Naked Market breaks down macro finance, blockchain infrastructure, AI systems, and automated trading to help you understand the future of global finance before the mainstream catches up.

Picture a screen glowing in the dark. Doesnt matter where a phone in Lagos, a laptop in Jakarta, a bedroom in Manila. Same numbers everywhere.

Bitcoin, July 2026: around $60,000.

A year ago it was near $109,000. Last October it touched $126,000 and half the internet was shouting that six figures was the new floor that it could only go up from here.

Its not the floor anymore. It hasnt been for months.

And heres the strange part. The price falling isnt even the interesting bit. Prices fall. Prices rise. Thats literally the one thing prices do.

The interesting bit is that Bitcoin is quietly losing something worth far more than dollars.

Its losing the narrative.

First — what does “losing the narrative” even mean?

Let me back up, because this word gets thrown around constantly and almost nobody stops to define it.

Every asset on earth is really two things at once. Theres the thing itself — the coin, the share, the bar of metal. And theres the story people tell about the thing. The story is what makes you hold it through a bad week, buy more when its down, or try to explain it to your uncle at a family dinner.

Gold’s story: “it has held its value for 5,000 years.” The dollar’s story: “the whole planet accepts it.” A hot tech stock’s story: “this company owns the future.”

Clean. One line each.

Bitcoin never had one story. It had four. And in 2026, three of them cracked right down the middle.

Let me show you the autopsy. (Sorry thats dark. But it fits.)

Story 1: the “digital gold” that didn’t act like gold

For years the pitch was beautifully simple. Bitcoin is “digital gold.” When the world gets scary and money runs for safety, it runs to gold and it would run to Bitcoin too. Same job as gold, just younger and faster.

2026 ran that experiment live, in public, for everyone to watch.

Late January. President Trump starts firing tariff threats at NATO allies and floating the idea of taking Greenland. Textbook fear moment exactly when a safe haven is supposed to shine.

So what did Bitcoin do?

It fell 6.6%. Gold rose 8.6%. They ran in opposite directions during the precise kind of chaos Bitcoin was built to survive.

And it gets worse. That same month, the 30-day correlation between Bitcoin and the Nasdaq 100, the index stuffed with risky tech stocks hit 0.80. The tightest in almost four years.

Quick translation, because “0.80 correlation” means nothing until someone explains it. It basically means: when tech stocks sneeze, Bitcoin catches the cold. They move together — up together, down together, nearly in lockstep.

That is the exact opposite of a safe haven. A safe haven is supposed to zig when everything else zags. Bitcoin zigged when tech zigged, then crashed when tech crashed.

Meanwhile the boring old rock it was supposed to replace? Gold ripped past $5,600 an ounce, up 23% in a matter of weeks. And the biggest buyers werent nervous day traders. They were central banks. A record 45% of them, the highest reading in the history of the survey said they plan to buy more gold this year.

Sit with that for a second. The most powerful money managers on the planet had a straight choice between digital gold and actual gold.

They chose the rock.

Story one: cracked.

Story 2: the cash job that got stolen

Rewind to the very beginning. In 2008, a person or group nobody actually knows calling themselves Satoshi Nakamoto published a short paper. Its title described Bitcoin as a peer-to-peer electronic cash system.

Cash. Money you spend. That was the founding dream, send value to anyone, anywhere on earth, with no bank in the middle taking a cut and taking its time.

Now heres the brutal irony of 2026. That dream came true. Bitcoin just isnt the thing that made it happen.

Something else did. Stablecoins.

And this is the single most important idea in this whole piece, so let me make sure it lands even if youve never touched crypto in your life.

A stablecoin is a digital token pegged to a normal currency almost always the US dollar. One token is meant to always equal one dollar. It lives on a blockchain, so it moves like crypto: instantly, globally, around the clock, no weekends, no “please allow 3–5 business days.” But because its tied to the dollar, it doesnt lurch up and down like Bitcoin does. Its basically a dollar that learned how to teleport.

And people are using them. Not a little. A staggering amount.

In February 2026, stablecoins did something that honestly should have been front-page news everywhere and somehow wasnt. In a single month they moved $7.2 trillion beating ACH, the decades-old plumbing behind American bank transfers, for the first time ever. Across all of 2025 they settled roughly $33 trillion. Thats more than Visa and Mastercard combined.

Heres the cleanest way I can put it. The dollar is the cargo. The blockchain is just a faster truck.

The world never actually wanted a brand new kind of money to spend. It wanted its existing money — dollars, the thing it already trusts to move at the speed of a text message. Stablecoins delivered exactly that. Bitcoin, swinging 5% on a random Tuesday, was never going to be the thing you buy groceries with in Buenos Aires or send home to family in Manila.

Story two: stolen, right out from under it.

Story 3: the frontier that moved on

For about a decade, if you were an investor who wanted a slice of “the future” the wild frontier, the thing your friends didnt understand yet and kind of mocked you for you bought Bitcoin. It was the frontier-technology trade. The rebel bet.

Then, in 2023, three letters walked into the room and took the entire table.

A.I.

By 2026, the frontier isnt crypto anymore. Its artificial intelligence. The money that used to chase “the next big technology” now chases chips and models and AI startups. Bitcoin went from being the daring outsider to being, lets be honest a ten-year-old asset your bank now sells you in a neat little ETF wrapper.

Nothing ages a frontier story faster than becoming mainstream. And nothing makes yesterday’s frontier look dull faster than a shiny new one moving in next door.

Story three: replaced.

The twist: the one story Bitcoin is quietly winning

Okay. Three stories cracked. So Bitcoin is finished, right? Pack it up, nothing to see?

No. And this is exactly where almost everyone bulls and bears both gets it wrong.

While those three narratives were falling apart, a fourth one quietly got stronger. Not “money you spend.” Not “safe haven for a scary Tuesday.” Something slower, heavier, and far less exciting to post about:

A reserve asset for governments.

In March 2025, the United States created a Strategic Bitcoin Reserve. Today the US government sits on somewhere around 325,000 Bitcoin. El Salvador holds it as official national policy. Bhutan quietly mines it with hydro power off its mountains. Pakistan announced a reserve of its own.

Look at what all these buyers have in common. Theyre not trying to buy coffee. Theyre not trading in and out on a Tuesday afternoon. Theyre parking value for the long haul — the US reserve literally comes with a 20-year holding rule.

And that is a completely different story from the other three. Better yet, its the one job Bitcoin is genuinely good at: a scarce, hard-to-seize, borderless thing a country can hold when it doesnt fully trust the dollar or cant fully get access to it.

So the honest scoreboard for Bitcoin in 2026 looks like this:

Three losses. One win.

And yet the crowd keeps reacting to the price of the whole bundle screaming either “its dead” or “its going to a million” when the truthful answer is: it completely depends on which story youre talking about.

Zoom out: it was never one coin

Now step all the way back. Because this is where Naked Market actually lives not in the price, but in the structure humming underneath it.

For years, one tribe of Bitcoin believers held a very specific dream. One coin. One deflationary money. Bitcoin would swallow the dollar, the euro, the yen, and become the single money of the internet. One coin to rule them all.

2026 quietly put that dream to bed. But and this is the part that matters most it proved something far bigger true.

If youve been reading this newsletter for a while, you know the thread running through all of it: One Earth, One Currency. The idea that the world is slowly, structurally rebuilding money on shared, neutral, borderless rails. (New here? Start with this its the whole thesis in one place.)

Heres what people keep misreading. “One Earth, One Currency” was never going to be one coin winning a cage match. Its shared rails winning. A common settlement layer that dollars can ride, that tokenized bonds can ride, that in time many national currencies can ride, all at once, all on the same open network.

Now look at what actually won in 2026. Not a single coin. The rails. Stablecoins moving $33 trillion isnt proof that “crypto beat the dollar.” Its proof that money itself is climbing onto blockchain infrastructure and the dollar simply got there first by hitching a ride.

So Bitcoin losing three of its four narratives isnt evidence against the future of digital money. Its the strongest evidence yet for what that future actually is. It was never one coin. It was always the rails.

Bitcoin is one passenger on those rails. An important one, with a real, permanent seat the “hard reserve” seat by the window. But it was never the whole train. The people in real pain right now are the ones who bet it was. (Thats the misconception that keeps costing people money.)

Your tool: The Narrative Ledger

So how do you avoid becoming one of those people? How do you look at any hyped asset or any dumped, left-for-dead one and actually see clearly, while everyone around you is either euphoric or terrified?

Heres the tool. Im calling it the Narrative Ledger. Take it with you. Its yours now.

A ledger, in plain accounting terms, is just two columns: what you own (assets) and what you owe (liabilities). The Narrative Ledger does the exact same thing but for stories instead of money.

When you look at any asset, company, coin, or trend, dont ask the crowd’s lazy question (“is it going up or down?”). Ask a sharper one:

“Which of its stories is winning, and which is losing?”

KEEP THIS · THE NARRATIVE LEDGER

1. List every story. Not the loudest one. All of them. (Bitcoin had four.)
2. Write the evidence next to each. Real numbers, real behavior, real money flows. Not vibes, not headlines, not what a guy screamed on YouTube.
3. Mark each one. Asset (evidence backs it up) or liability (evidence kills it).
4. Read the net — never the loudest line.

Run Bitcoin through it and the fog burns off in about thirty seconds. Three liabilities, one asset. Not “dead.” Not “to the moon.” Just a specific thing thats quietly excellent at one job and has clearly lost three others.

And heres why this little tool is worth more than any price prediction youll ever read: it works on everything. Run it on an AI stock everyone swears is infinite. Run it on gold. Run it on the next coin your cousin promises is a 100x at the next family dinner. The crowd will always react to the whole. Youll read the lines.

Thats the entire game.

Rich reacts. Wealthy reads the rails.

Theres a difference between being rich and being wealthy, and it shows up right here, in exactly this kind of moment.

The rich person sees Bitcoin at $60,000, sees a screen full of red, feels the fear thick in the room and reacts. Sells at the bottom, or panic-buys the top, yanked around by whichever story is loudest that particular week.

The wealthy person doesnt look at the price first. They read the ledger. They notice that one quiet narrative got stronger while three noisy ones fell apart. And they understand that “Bitcoin” and “the future of money” were never the same sentence. They were watching the rails the entire time.

Bitcoin didnt lose the narrative. It lost three narratives, kept one, and in the process accidentally revealed what the real story was all along.

The rails are being laid. Right now, under all the noise. The only question that actually matters is whether youre reading them or reacting to them.

If you want to understand where money is heading before it gets obvious before the headlines, before the crowd, before your bank sends you that polite little email about its exciting new digital-asset product this is the place.

Subscribe to Naked Market

Well keep reading the rails together.

Keep going

Stablecoins: How a Casino Chip Became the Most Important Money on Earth

The New Rails: Blockchain as Infrastructure

Crypto Was Supposed to Escape the System

- More soon

Has Bitcoin Lost the Narrative? was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.

What gas fees are, why they exist, how Ethereum calculates them, and how to pay less.

Before Ethereum’s Dencun upgrade in March 2024, a single token swap on a busy day could cost more in gas than many people were moving. Within days of the upgrade, Layer 2 fees fell by as much as 98 percent, and a basic transfer today often costs a fraction of a cent.

Crypto gas fees are the payment you make to a blockchain network to process your transaction. Here is crypto gas fees explained in full: what they are, why you pay them, how Ethereum calculates them, and how to pay less. You pay them because block space is limited and the validators who process and secure transactions need to be compensated.

The biggest lever on what you pay is which network you transact on, and that is where most of the savings live.

A gas fee is the charge to run a transaction, paid to the validators who process and secure it, priced in gwei.

What are gas fees?

Gas fees are the fee you pay to run a transaction on a blockchain, similar to postage on a letter. The fee compensates the validators who process and secure your transaction. On Ethereum it is quoted in gwei, a small unit of ether equal to one billionth of one ETH.

Every action consumes a measurable amount of gas, from a plain transfer to a multi-step contract interaction. The heavier the computation, the more gas it uses.

You pay gas to compensate validators, ration limited block space, and deter spam.

Why do you pay gas fees?

You pay gas fees for three reasons: to compensate validators for the computing work and security they provide, to ration limited block space so fees decide whose transaction is processed first, and to deter spam that would otherwise flood the network.

Without a fee attached to every action, nothing would stop endless junk transactions from filling each block. The fee makes block space a resource people spend deliberately.

Crypto gas fees explained: how they are calculated

An Ethereum gas fee is the gas your transaction uses multiplied by the gas price. Since the EIP-1559 upgrade, that price is a base fee the network sets and burns, plus an optional priority fee that tips a validator to include you sooner, as the Ethereum documentation describes.

Transaction fee = gas used × gas price

More complex transactions use more gas, and higher demand pushes the price up. The base fee adjusts automatically with how full recent blocks are, and because it is burned rather than paid to anyone, every transaction permanently removes a little ether from circulation.

Transaction fee equals gas used times gas price; since EIP-1559 the price is a burned base fee plus an optional priority tip.

What makes gas fees high or low?

Gas fees rise and fall with four things: network congestion, transaction complexity, timing, and which network you use. Congestion is the largest short-term driver, because the base fee climbs when blocks fill during busy periods such as a major token launch or a sharp market move.

The scale of that swing is real. Average Ethereum gas ran near 72 gwei before Dencun and fell to roughly 3 gwei after, and through 2026 mainnet gas has often sat near 1 gwei on the Etherscan tracker, which puts a basic transfer well under a cent.

Average Ethereum gas fell from about 72 gwei before Dencun to roughly 1 gwei in 2026.

How to reduce gas fees

The most effective way to reduce gas fees is to use a Layer 2 network, then to time transactions for quiet periods and combine actions. In rough order of impact:

1. Use a Layer 2 network such as Base, Arbitrum, or Optimism, where fees are routinely a fraction of a cent.
2. Transact at off-peak times, since the base fee drops when the network is quiet.
3. Batch or consolidate actions so fewer transactions use less total gas.
4. Set an appropriate priority fee instead of overpaying a large tip during calm periods.
5. Choose the right network for the task, since baseline fees differ widely between chains.

Five ways to reduce gas fees, biggest lever first: Layer 2, off-peak timing, batching, the right priority fee, and a cheaper network.

Why Layer 2 is the biggest lever

A Layer 2 is a faster, cheaper network that processes transactions off the Ethereum mainnet and settles them back to it for security. After Dencun let rollups post their data in low-cost blobs, Layer 2 fees dropped sharply and now often sit below one cent.

Do stablecoin transfers cost gas?

Yes. Moving or using stablecoins consumes gas like any other transaction, so it can be pricey on Ethereum mainnet during congestion and is usually cheap on a Layer 2. The token holding its value at a dollar does not change the network cost of moving it.

When you use an onchain app, including supplying or redeeming stablecoins through Sky.money, you pay network gas, which is separate from any app fee. If you move stablecoins often, doing it on a low-fee network keeps the cost close to trivial.

For what to do with stablecoins once they are in your wallet, see how to earn yield on stablecoins.

Moving stablecoins costs network gas like any transaction; it is cheap on a Layer 2 and separate from any app fee.

Frequently asked questions

What are gas fees? The fee you pay a blockchain network to process a transaction. It goes to the validators who process and secure it, and on Ethereum it is quoted in gwei.

Why do I pay gas fees? To compensate validators for their work and security, to ration limited block space, and to deter spam that would clog the network.

How are Ethereum gas fees calculated? Gas used multiplied by the gas price, which since EIP-1559 is a base fee that is burned plus an optional priority fee, all quoted in gwei.

How can I reduce gas fees? Use a Layer 2 network, transact at off-peak times, batch your actions, and pick a cheaper network for the task.

What is a Layer 2? A faster, cheaper network that processes transactions off the Ethereum mainnet and settles them back to it for security.

Do stablecoin transfers cost gas? Yes. They are usually cheap on Layer 2 networks and can be costly on Ethereum mainnet during congestion.

What is gwei? A small unit of ether used to price gas, equal to one billionth of one ETH.

Final thoughts

If I had to reduce crypto gas fees explained to one habit, it would be to match the network to the transaction. Keep large, occasional moves on Ethereum mainnet when you value its settlement security, and run everyday stablecoin activity on a Layer 2 where the fee is a rounding error.

Check a live gas tracker before you confirm anything costly, and treat the fee as payment to a public network doing real work for you, not a charge from a middleman. Once you pick the right network, gas stops being something you worry about.

Crypto Gas Fees Explained: Why You Pay Them and How to Save (2026) was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.

The biggest takeaway was not what everyone was talking about.

Reading Ethereum improvement proposals is not most traders’ idea of market research. They are dense, technical, and frequently contain jargon that requires significant background to parse correctly. The process of reading them is slow. Most of what they contain is not directly tradeable information in any near-term sense.

And yet, over the course of several weeks, I made my way through every significant EIP and upgrade proposal from the past four years. Not because I expected to find a hidden trading edge buried in the technical documentation, but because I had grown frustrated with my understanding of Ethereum being almost entirely derived from secondary sources: Twitter summaries, YouTube explanations, newsletter digests.

Secondary sources have a specific problem. They are produced by people who have read the primary documents and then filtered, simplified, and interpreted them for an audience. That filtering process necessarily involves choices about what matters and what does not. The trading community’s version of Ethereum’s development story reflects those choices, and those choices are shaped by what generates engagement, which is not always the same as what is most important for understanding where the asset is headed.

What stood out most to me was not a specific technical proposal. It was a consistent pattern in how upgrades are developed, debated, and eventually implemented that has direct implications for how protocol development timelines should be weighted as a factor in Ethereum’s valuation narrative.

The Gap Between Proposal and Implementation

The first thing that becomes clear from reading the proposals directly is how long the path from an idea to a shipped upgrade actually takes.

The most significant upgrades to Ethereum over the past several years have had gestation periods that would be surprising to anyone whose understanding comes from community announcements and price-movement coverage. By the time a major upgrade receives significant media attention and is reflected in market discussions as a near-term catalyst, it is often already deep into an implementation cycle that began years earlier.

The Merge, which received enormous market attention as an upcoming catalyst in 2021 and 2022, was the subject of active EIP discussion from 2018 onward. The staking mechanism that preceded the actual Merge was deployed in late 2020. When the market was treating the Merge as a future event with uncertain timing in 2021, significant portions of the technical infrastructure had been live and tested for over a year.

This pattern, where the visible market narrative about an upgrade’s timing is substantially later than the actual development timeline, has a specific implication. By the time an Ethereum upgrade becomes widely discussed as a market catalyst in retail crypto communities, most of the technical risk associated with the upgrade has already been addressed in earlier testnet and mainnet deployments that occurred without the same market attention.

What This Means for “Buy the Upgrade” Narratives

The crypto community has developed a general heuristic for upgrades: buy the anticipation, sell the news. This heuristic has some validity. Markets do tend to price in anticipated positive events, and the actual delivery of an event sometimes removes the uncertainty premium that had been sustaining elevated prices.

But reading the actual upgrade proposals reveals a nuance that the simple heuristic misses.

Because significant Ethereum upgrades are developed over years rather than months, the anticipation phase in the retail market narrative often begins when the technical risk is already largely resolved. The uncertainty that would justify a genuine anticipation premium, the uncertainty about whether the upgrade will actually work, has already been substantially reduced through the extended development and testing process that predated the retail market’s attention.

What this means practically is that the “buy the anticipation” narrative in crypto often begins at a point where the real anticipation was already priced by more technically sophisticated participants who had been following the EIP process. The retail community is not buying anticipation of a genuinely uncertain outcome. It is buying anticipation of an outcome that is already reasonably well-established technically.

This does not mean the upgrade has no price impact. It means the price impact is front-loaded toward the portion of the development cycle that predates retail attention, not the portion that generates the most discussion.

The Technical Detail That Most Analysts Glossed Over

Reading the EIPs directly also surfaced a specific technical dynamic that almost every secondary source I encountered either glossed over or described inaccurately.

The relationship between Ethereum’s supply dynamics and its fee burning mechanism is substantially more nuanced than the simplified description that circulates in most trading communities. The common narrative is something like: EIP-1559 introduced fee burning, which makes Ethereum deflationary, which is bullish. This is technically accurate as a skeleton and misleading as a trading thesis.

The actual relationship between fee burning, new issuance, and the net supply change is dynamic and depends entirely on network activity levels. At low network activity levels, new issuance exceeds the amount burned, which produces net supply increase. At moderate activity levels, burning roughly offsets issuance. At high activity levels, burning exceeds issuance, which produces net supply decrease.

The critical point that most community discussions miss is that the supply dynamics are a consequence of network usage, not a guaranteed feature of the protocol. Ethereum becomes deflationary when the network is heavily used. It is not inherently deflationary in the way a fixed supply asset is.

This creates a circularity that the simple bullish supply narrative does not acknowledge: for the supply dynamics to be bullish, the network needs to be extensively used, but extensive network usage requires Ethereum to be the preferred platform for significant activity, which is a competitive outcome that is not guaranteed regardless of the protocol’s technical properties.

What the Upgrade History Says About Execution Risk

One more pattern that stood out from reading the full upgrade history was the frequency and nature of delays.

Nearly every significant Ethereum upgrade has experienced timeline extension from its original estimates. Not because the development process is poorly managed, but because shipping consensus-critical code to a live network where errors have irreversible consequences requires caution that is not compatible with aggressive timelines.

The community’s response to delays is usually impatient. Delays generate negative sentiment, are cited as evidence of mismanagement, and sometimes produce price weakness in Ethereum relative to competitors who claim to move faster.

What the EIP history reveals is that these delays have consistently been the result of genuine technical prudence rather than organizational dysfunction. Upgrades that were delayed were delayed because testing revealed issues that needed to be addressed before deployment. In every case in the record I reviewed, the delayed upgrade was eventually delivered successfully.

The pattern of delays followed by successful delivery has a specific implication for how execution risk in Ethereum upgrades should be assessed. The fact that an upgrade is taking longer than originally announced is not, by itself, evidence that the upgrade is in trouble. It is evidence that the development process is maintaining the caution appropriate to consensus-critical code.

How to Use Technical Upgrade Research in an Investment Framework

None of the above produces a specific near-term trading signal. Ethereum’s upgrade trajectory is a long-horizon framework for thinking about the asset’s development, not a source of weekly or monthly actionable calls.

The practical use of understanding the upgrade process is in calibrating how to weight technical development as a factor against other factors in the overall investment thesis.

When the retail market narrative is excited about an upcoming upgrade and treating it as a near-term price catalyst, the technical reality is usually that the upgrade has already been de-risked through an extended development process and that much of the potential value associated with it has already been recognized by more technically informed participants.

When the retail market narrative is pessimistic about delays, the technical reality is usually that the delays reflect appropriate caution in an environment where errors are irreversible, and that the track record of successful delivery after delay is stronger than the pessimistic framing suggests.

Reading the primary technical documentation does not give you certainty about outcomes. Markets are uncertain and even technically excellent protocol development does not guarantee a specific price trajectory. But it does give you a more grounded perspective on the relationship between technical development and market narrative, which helps identify when the narrative has gotten ahead of the technical reality and when it has fallen behind.

I Read Every Major Ethereum Upgrade Proposal and This Stood Out the Most was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.

First in a series: “Things I learned while building with DAML.”

I came to Canton the way a lot of blockchain engineers do: sideways.

I’d spent a lot of time thinking in Solidity storage slots, msg.sender, reentrancy, ERC-20 approvals, the occasional ZK circuit when privacy mattered. Then I built a prototype of something institutions actually care about: tokenized gold custody, dual-signature vault attestations, compliance-gated escrow, and fund subscription/redemption on the Canton Network, using DAML and the CIP-56 token standard.

I expected another smart contract language with different syntax.

What I got was a different question.

Ethereum asks: *What does everyone agree on?*

Canton asks: *Who actually needs to agree?*

That shift completely changes how you model financial systems. This piece is about that shift and about being/ fair to both stacks when people reach for “Ethereum + ZK” versus “DAML on Canton” for real-world assets.

What I actually built (so this isn’t vapor)

Before the philosophy, the artifact.

The prototype covers a full custody-to-fund loop roughly like this:

- Vault layer: gold bars with serials, purity checks against system config, a serial registry (no contract keys Canton multi-domain reality), vault receipts for regulators.

- Operators & attestations: weighmaster + weigh device for dual-confirmed weight, assayers, transporters, auditors; permissions mapped exhaustively to attestation kinds.

- Token layer: GoldHolding implementing CIP-56 Holding / transfer-factory interfaces an issuance ledger so over-mint against a bar is structurally hard a small prototype CashHolding for settlement legs.

- Escrow propose → accept-and-fund → settle, with a list of compliance checks as data (KYC, limits, presence freshness, open movements, open discrepancies…).

- Fund ops share classes, NAV points, redemption gates, fees with banker’s rounding, in-kind redemption above a threshold.

- Off-ledger TypeScript connectors for NAV publishing, vault tablet attestations, and a thin ISO 20022 (setr.010/012) adapter.

The interesting part for an EVM person isn’t the feature list. It’s that almost every design decision was about parties, visibility, and workflows not about packing more logic into a globally visible bytecode blob.

Smart contracts are templates, not programs

One thing that surprised me about DAML: you don’t think in terms of “contracts” the way Solidity trains you to.

In Solidity, a contract is often a long-lived program with mutable storage. You deploy it once. Callers poke functions. State variables update in place.

In DAML, you define templates schemas for agreements between parties. Creating a contract instantiates an agreement. Exercising a choice advances it. Many choices archive the old contract and create a new one. The ledger isn’t a bag of storage slots; it’s a set of active agreements with lifecycles.

It feels closer to modeling a business process or even, oddly, closer to HTML than to writing EVM bytecode. You describe who must sign, who may see, who may act. The runtime enforces that description.

Here’s a tiny slice from the vault layer:

template GoldBar
with
custodian : Party
regulator : Party
serialNumber : Text
weightGrams : Decimal
purity : Decimal
vaultLocation : Text
custodianRef : Text
where
signatory custodian
observer regulator
ensure weightGrams > 0.0

The custodian must authorize creation. The regulator can see the bar without being able to invent one. Purity thresholds against system config live in the registering choice because ensure can’t fetch other contracts but the authorization shape is already visible in the template.

Contrast the EVM reflex:

// Everyone who can call sees the same storage.
// Visibility is not part of the type; access control is bolted on.
mapping(bytes32 => GoldBar) public bars;
function registerBar(…) external onlyCustodian {
bars[serial] = GoldBar(…);
}

Both can be correct. They encode different defaults about who the system is for.

Solidity teaches you to think like a VM.

DAML teaches you to think like a lawyer drafting an agreement that happens to execute.

That was the biggest mindset shift for me.

Explicit parties beat ambient msg.sender

In Solidity, authorization often collapses to:

require(msg.sender == custodian);

In DAML, the language gives you three distinct roles in the model itself:

- signatory: must authorize creation (and typically archival consequences)

- observer: can see the contract without controlling it

- controller: may exercise a particular choice

Escrow settlement isn’t “anyone who knows the address.” It’s this buyer, under these checks, before this expiry, with cash-issuer authority threaded explicitly when holdings are archived because DAML authority doesn’t magically transit through nested fetches the way a careless Solidity onlyOwner might pretend to.

That verbosity is a feature when you’re modeling custody, dual control, and regulated observers. It’s overhead when you want a two-line meme coin.

Different optimization targets.

Shared execution vs shared agreements

Ethereum asks: what does everyone agree on?

DAML asks: who actually needs to agree?

That one-line swap is the whole article, if you’re in a hurry.

Ethereum optimizes for shared execution.

One canonical state. One global truth. Anyone can re-execute the same transaction history (in principle) and land on the same balances. That’s why DeFi composability feels magical: your vault can trust Uniswap’s pool the way it trusts math because both live in the same transparent machine.

DAML / Canton optimizes for shared agreements.

There isn’t a single global RPC that returns the world state. Each participant node sees the contracts it’s entitled to see. Settlement is about getting the right parties to the same conclusion on the slice of state they share not about broadcasting every position to every stranger on the network.

When we wrote end-to-end privacy scripts for the gold prototype, the assertions weren’t “the chain shows X.” They were:

- Investor B sees none of investor A’s holdings, subscriptions, or KYC contracts.

- The regulator sees vault-layer facts without seeing investor cash books.

- The custodian doesn’t get NAV methodology internals beyond what’s disclosed.

Banks rarely want global transparency. They want shared truth between the parties involved and a clean story for supervisors who are observers.

That doesn’t make Ethereum wrong. It makes “public by default” a product choice with consequences.

Privacy by default vs privacy as an add-on

On Ethereum, privacy is something you add.

- Private mempools and encrypted orderflow for MEV.

- ZK proofs so you can convince a public verifier of a private statement.

- FHE so you can compute on ciphertext when even intermediate plaintext is too hot.

Those are serious technologies. They’re also expensive in engineering surface area: circuits, provers, trusted setups or transparent alternatives, key management, auditability of the crypto, gas, latency.

In DAML, visibility is part of the data model from day one. If you’re not a stakeholder on a contract, you don’t get the payload. Privacy isn’t a bolt-on proving system; it’s how the ledger partitions knowledge.

Neither approach is free.

A fairer unpack of the add-ons:

ZK on EVM is not “DAML but worse.” It’s a different primitive. You keep a public settlement substrate and attach a proof that a private computation or private data satisfies a public predicate. That’s incredibly powerful when strangers must coordinate: LPs in a pool, holders of a tokenized fund share trading on an open venue, journalists checking a reserve claim. The cost is real circuits, prover ops, audit surface but the social payoff is “the market can verify without being invited into the room.”

FHE on EVM (or adjacent confidential compute) attacks a harder problem: let multiple parties compute on encrypted inputs without decrypting mid-flight. Think sealed-bid auctions, confidential risk scoring, or shared analytics over positions nobody wants to reveal. It’s earlier than ZK for production RWA stacks, and the performance/ops tax is steep. When it matures, it will matter most where even the operators shouldn’t see plaintext something DAML’s stakeholder model doesn’t automatically give you if a party is itself a curious intermediary.

DAML’s privacy is closer to “need-to-know messaging with enforceable rights” than to “ciphertext on a public bulletin board.” That’s usually what a custodian, fund admin, and auditor want for operating the book. It is not automatically what a secondary market wants when price discovery depends on many anonymous participants trusting the same rules.

The question I hear too often is:

Should institutions use Ethereum + ZK?

Sometimes yes. A better question is often:

When does proving something publicly make more sense than simply sharing it privately?

If the audience that must be convinced is the open market holders, LPs, journalists, on-chain analysts ZK on a public substrate is a natural fit. Proof of reserves. Solvency. Correctness of a dark-pool matching rule without revealing orders.

If the audience that must be convinced is the counterparties and the regulator and everyone else should see nothing DAML’s need-to-know model is often the shorter path. You’re not proving a statement to the world; you’re sharing the agreement with the people in the agreement.

Both are “privacy.” They answer different social questions.

Finality, not TPS

Crypto Twitter obsesses over throughput.

Institutions obsess over deterministic settlement.

Did the DvP complete? Are both legs final? Can operations book it? Can legal point to a single outcome if something blows up at 4:01pm?

Canton is excellent at institution-to-institution settlement workflows for exactly that reason: the unit of design is the multi-party transaction over shared contracts, not “how many Uniswap swaps fit in a block.”

That doesn’t mean EVM chains can’t settle RWAs — they do, increasingly. It means if your KPI is TPS theater, you’re measuring the wrong thing for custody and fund ops. If your KPI is *irreversible agreement among the right parties*, you’re closer to how banks already think.

When each stack is interesting for RWAs

Fairness means naming wins on both sides.

Prefer DAML / Canton when…

- The workflow is multi-party and regulated: custodian, investor, fund manager, auditor, transporter.

- Disclosure is asymmetric by law or policy (regulator sees vault; peer investor must not see your book).

- You need lifecycle fidelity proposals, acceptances, expiries, dual control, consuming choices that map to “this agreement is done.”

- Privacy is a requirement, not a roadmap item.

- Counterparties are known legal entities, not anonymous addresses competing in a public mempool.

Our gold prototype lived here: presence freshness that can “self-freeze” settlement if attestations go stale; movement checks that block escrow while a bar is in transit; discrepancy reports that halt site settlement until write-down or resolve. Those are *process* controls. They want to be first-class in the model.

Prefer public EVM (and EVM + ZK) when…

- You need permissionless secondary markets and DeFi collateral composability.

- Success depends on anyone integrating wallets, aggregators, lending markets without bilateral onboarding.

- You must prove a fact to the world (reserves, NAV integrity, compliance predicates) while keeping underlying data hidden ZK shines.

- Retail distribution and liquidity bootstrapping matter more than bilateral confidentiality.

Prefer hybrid when…

- Primary issuance and institutional ops need private shared state, but public representation or a ZK attestation of that state feeds open markets.

- You want Canton (or similar) for the agreement layer and an EVM venue for the liquidity layer with a deliberately designed bridge and disclosure policy.

Hybrid is where a lot of serious RWA architecture is heading. Tribal “EVM vs DAML” posts miss that.

Concrete lessons from the gold build

A few engineering notes that stuck.

1. Compliance as data, not as a rewrite

Escrow took a list of compliance check contract IDs. The same escrow template settled with [KYC, Limit] and failed with [KYC, Limit, Presence] when presence was stale without changing Escrow.daml.

On EVM you’d reach for a strategy pattern or a modular hook. it’s doable. In DAML it felt native: the agreement says “run these checks,” and checks are themselves agreements with providers and subjects.

2. Dual-signature weight

A weight attestation wasn’t “confirmed” until a human weighmaster and a weigh device agreed within tolerance and the same attestor twice was rejected. Dual control isn’t a comment in a PR; it’s a template choice with negative tests.

3. Tokens that can freeze themselves

Pass time beyond attestationMaxAge with no fresh presence attestation and settlement paths that require PresenceFreshnessCheck fail. Fresh attestation unlocks them again. That’s operational reality for physical gold, encoded as workflow not as an admin pause() god-key (though god-keys exist in many EVM systems for worse reasons).

4. CIP-56 as the ERC-20 mindset bridge

Coming from ERC-20, CIP-56’s Holding / TransferInstruction interfaces were the familiar part: standardize how wallets and apps talk to holdings without caring which registry implemented them. The unfamiliar part was everything around who sees the holding.

Consuming choices (a favorite concept)

Exercising a choice can archive a contract and create its successor.

That’s closer to how legal agreements evolve “this SOW is superseded by amendment #3” than to

balances[alice] -= x; 
balances[bob] += x; 

in place. Escrow that settles doesn’t flip a status = Settled enum in eternal storage (though you can model that). It consumes the escrow agreement and produces the resulting holdings under new owners. Failed settle leaves both legs intact partial state is a bug you test for.

Once you see consuming choices, a lot of DAML design clicks. Once you miss them, you write DAML like Solidity and fight the language.

What DAML is not (yet) great at

Honesty matters if you want engineers to trust the comparison.

- Ecosystem gravity. Most crypto talent, tooling, auditors, and memes are EVM-native. Hiring and open-source velocity still favor Solidity.

- Permissionless composability. Uniswap-style “plug any token into any pool” is not Canton’s home game. If your RWA product’s moat is DeFi money legos, start on EVM (with ZK where needed) and be honest about disclosure.

- Retail UX myths. Canton is excellent at institution-to-institution settlement. The interesting question isn’t whether that works it does for the workflows it’s built for. It’s whether the same principles can eventually simplify payments for everyone else. That’s a product and policy problem, not a language flex.

- Public verifiability without disclosure. If your stakeholder is “the internet,” ZK on a public L1/L2 is often clearer than explaining participant-local ledgers.

- Tooling familiarity. Foundry, Hardhat, Tenderly, open auditors — EVM engineers drown in options. DAML’s loop (SDK, Script, LocalNet, JSON Ledger API) is coherent, but smaller. Expect a learning tax; budget for it.

None of that makes DAML “worse.” It makes it specialized. Specialization is how serious infrastructure usually wins.

And the reverse honesty: public EVM is not “institutions can’t use this.” They can and do especially when liquidity, distribution, or public attestation dominate. Pretending banks only want Canton is as unserious as pretending every gold custody workflow belongs on a public mempool.

Mental models, not tribal banners

Instead of Ethereum vs DAML, compare the lenses:

Ethereum optimizes for shared execution.

DAML optimizes for shared agreements.

They sound similar. They’re solving different problems.

I’m not done with either. The more I work on RWAs, the more I believe the interesting systems will be bilingual: public where the market must see or verify, private where the counterparties must settle.

If you write Solidity and you’ve never modeled a multi-party workflow in DAML, try one thin vertical escrow with two compliance checks, or a dual-control attestation and notice what becomes easy and what becomes annoying. That annoyance is usually a clue about which problem you were actually solving.

What’s next in this series

Topics I want to dig into next, still from an Ethereum engineer’s notebook:

1. Consuming choices as a first-class design tool (with escrow war stories).

2. Parties vs accounts and why allocateParty` feels alien until it doesn’t.

3. Finality and deterministic settlement what institutions measure that TPS dashboards ignore.

4. CIP-56 for ERC-20 natives mappings, traps, and where the analogy breaks.

If this was useful, model one RWA workflow both ways and tell me which lies you had to tell each stack.

That’s usually where the real architecture starts.

Things I Learned Building with DAML: Notes on Privacy, RWAs, and Mental Models was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.

Robinhood Chain crossed $311M in TVL in under three weeks. Growth like that is exactly when security gets skipped.

A rollup carrying tokenized stocks, stablecoins, and open lending markets is not just another L2 to review. The token itself is the giveaway: a Stock Token can have flawless code and still be wrong if the price feed lags, the issuer’s reserve does not match onchain supply, or the legal agreement behind the token does not say what the marketing says it does. Our RWA Handbook breaks this wider surface into five categories: asset-token mismatch, mint and burn exploits, privilege and admin risk, oracle failures, and custody and legal risk. Robinhood Chain touches all five within its first month live.

Some of the risk is just standard Arbitrum Orbit territory. Sequencer centralization, since a single sequencer orders every transaction. A seven-day fraud-proof withdrawal delay. Address aliasing on L1-to-L2 calls. Data availability gaps if blob posting is delayed. Upgrade keys controlling the rollup contract. None of this is unique to Robinhood, and all of it still applies.

Other risk is specific to this chain. Stock Tokens use ERC-8056, scaling value through a uiMultiplier() function instead of rebasing balances, so any protocol that reapplies the Chainlink feed’s built-in multiplier will double count it. An oraclePaused flag signals an unreliable price around dividends and splits, but it is advisory, not enforced onchain. A single Authorised Participant controls the entire mint and redeem pathway for every tokenized stock, sitting outside the smart contract layer entirely.

Then there is agentic trading, live now for equities and options through Robinhood’s brokerage stack, not the chain itself. Robinhood CEO Vlad Tenev has said every capability a human can do will be available to an AI agent. Crypto support is coming next, and that is when this risk surface starts sharing a trust boundary with Robinhood Chain: prompt injection through the research tools an agent reads, session and credential compromise through the MCP connection, autonomous mode removing human review by default, and correlated trading behavior across thousands of agents running similar strategies at once.

None of this makes the chain unsafe today. It makes Robinhood Chain a rollup already carrying real securities and real stablecoin liquidity, with a closely adjacent AI agent risk surface about to merge with it, exactly the kind of shift that rewards independent review before it happens.

We put together a full breakdown of every attack vector here, plus a six-step checklist for what a founder should decide before writing a single line of code: Robinhood Chain Security Risks and Attack Vectors Explained.

If you are building on Robinhood Chain, or auditing something that touches it, that piece is worth ten minutes before your next commit.

Robinhood Chain Security Risks and Attack Vectors Explained was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.

From the start of the year, Bitcoin and Ethereum prices collapsed. A big shake in the crypto industry, which resulted in prices dropping. But the greed and fear index is red. Showing it at 35, which means the percent chance of fear is more than 50%. But much better than last week, which was around 26. The monthly greed and fear index is 25.

Today, 16 June, the overall crypto market performed better than on previous days. The coins listed below by their market cap performed very well today.

Bitcoin, the number one cryptocurrency by its market cap, has a value of $64,876.08, a weekly surge in the price of around 4.2%. The market cap of bitcoin is $1.3 trillion, increased by 0.05%. The 24-hour trading volume is $27.31 billion, a decline of 8.36%.

Ethereum, the second-largest cryptocurrency, is trading at the price of $1,922.43, a surge in the price of around 2.41% in the last 24 hours. Similarly, it increased its value weekly by 11.04%. The market cap increased by $232 billion, a 2.43% jump. Whereas the volume in the last 24 hours is $13.19 billion, it rose by 1.04%.

Zcash is also referred to as ZEC. The 11th number is marked by its market cap on CoinMarketCap. ZEC is trading at the price of $576.83, a surge in the last seven days, which is 24.34%. Its market cap is $9.67 billion, a rise of 2.88%. Also, the volume recorded in the last 24 hours is $668.51 million, surging by 11.29%.

Chainlink, as LINK, is the number 14 cryptocurrency in the market, according to CoinMarketCap. Chainlink’s trading price is marked as $8.55. An increase of 12.11% since last week. When the market cap is $6.4 billion, it also increased by 6.09%. The 24-hour trading volume is $291.33 million, which is surging by 11.77%

Ondo is also known by its blockchain, ONDO. The 38th-ranked altcoin. ONDO is trading at $0.3653, a huge surge in prices weekly by 15.73%. Its market cap is $1.77 billion, increased by 15.93%. Although the 24-hour trading volume is $168.59 million, a huge surge in the last 24 hours is around 183.13%.

Market Update as Crypto Fear Index Shows Improvement was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.