The trench line · edition index

The day in three signals.

Read the full edition
01Rules0 storiesPolicy, regulation, courts and enforcement.
02Rails5 storiesProtocols, products and infrastructure.
03Risk0 storiesSecurity, solvency and market integrity.

Lead story · Rails

Samsung Partners with Solana for USDC Cross-Border Transfers in Samsung Wallet

Beginning late October 2026, Samsung Wallet will support USDC cross-border transfers on Solana across 82 million U.S. Galaxy devices.

  • Samsung Wallet will enable USDC cross-border transfers on Solana across 82 million U.S. Galaxy devices starting in late October 2026.

Read original source · solana-foundation

Read the 90-second brief

What happened

Beginning late October 2026, Samsung Wallet will support USDC cross-border transfers on Solana across 82 million U.S. Galaxy devices.

Why it matters

Samsung Wallet will enable USDC cross-border transfers on Solana across 82 million U.S. Galaxy devices starting in late October 2026.

What to watch

24h breadthMixed · 44/100
Latest available market pulse.A compact snapshot of whether BTC, ETH, SOL moved higher or lower over the prior 24 hours.
Lower50 = flatHigher

Tracked assets were broadly lower.

Breadth starts at 50, adds three points for each 1% of average 24-hour movement across the tracked assets, and is capped between 0 and 100.
BTC$82,597.00−1.81%
BTC was 1.81% lower than the provider quote 24 hours earlier. Snapshot: 04:58 UTC.
ETH$2,560.26−1.94%
ETH was 1.94% lower than the provider quote 24 hours earlier. Snapshot: 04:58 UTC.
SOL$114.88−2.73%
SOL was 2.73% lower than the provider quote 24 hours earlier. Snapshot: 04:58 UTC.

CoinGecko snapshot at 04:58 UTC. Prices and 24-hour moves refresh automatically without rerunning the newsroom.

The complete daily file

Across the crypto map.

5 distinct stories, grouped by subject and ranked by the Editor-in-Chief.

01

Ethereum & L2

Ethereum, rollups, staking, governance and application infrastructure.

01

Solana

Network, validators, applications, payments and ecosystem activity.

Story featured above.

01

DeFi & Stablecoins

Trading, lending, stablecoins, tokenized assets and onchain finance.

Story featured above.

01

Markets & Macro

Flows, derivatives, market structure, institutions and macro drivers.

01

Industry & Other

Cross-chain infrastructure and consequential industry developments.

The social evidence desk

Voices from the Trenches

Source-preserved posts worth knowing today.

Source-preserved X posts — original wording, author, timestamp and link. A post proves what the account said, not whether its external claims are true.

@brian_armstrongBrian Armstrong

We’re working with Samsung to bring USDC to Samsung Wallet, powered by Coinbase.

RailsdevelopingOriginal ↗
@laurashinLaura Shin

ScopeLift CEO Ben DiFrancesco says a big chunk of DAO dysfunction traces back to fear of the SEC "Well, yeah. Maybe zoom out further from the specifics of the Safe situation and just talk about DAOs in general." "I think for people outside of the industry, not working with projects day to day on this stuff, it's really easy to underestimate the degree to which our entire industry, and DAOs especially as a category, has been warped over the last 4 to 10 years by regulatory fears." "So much of what was done or not done, behaviors that seemed weird, was done because people didn't wanna go to jail or get a nastygram from the SEC." "You don't see that from the outside, because they don't talk about the fact that the reason they're setting it up this way is to hack around some kind of regulatory concern. Obviously, because the lawyers will jump down your throat if you do that. That's the reality of what has been happening in the industry for a long time." "So a big chunk of the dysfunction does come from this sort of like approximate cause of obfuscation of what's actually happening."

RailsdevelopingOriginal ↗
@VitalikButerinvitalik.eth

I don't recommend anyone scramble to move their funds to new wallets today. But we should take the risks to cryptography from AI-accelerated math seriously, and minimize our exposure to not just quantum-vulnerable cryptography, but also potentially AI-vulnerable cryptography. The core new area of risk from this viewpoint is, unfortunately, ML-DSA / FHE / lattices. (and it's also another reason, along with quantum, why ECDSA might fall even faster than expected, hence the "fresh address" recommendation) So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe". But there is a good chance that the concrete security of lattices will take serious hits from the next two years of AI math. The basic threat model is: factoring is something that naively takes 2^(n/2) time, but over decades smart people have found and optimized number field sieves, and degraded that to 2^O(n^(1/3)), which is why RSA keys and signatures need to be ~400 bytes (and not 64 bytes). What if there are skeletons in the closet like that, both for elliptic curves and lattices, that we are simply not smart enough to discover - but bots soon will be? This is a major part of the reason why for the past year ethereum's lean roadmap has been going in the "hash-only" direction: no lattices, no ML-DSA, no Falcon, no lattice-based commitments inside ZK proofs, etc. Signatures in lean ethereum are all hash-based, either WOTS or SPHINCS-. For signatures and proofs, we already know how to go hash-only. The bigger challenge is for *public-key encryption* - and this goes far beyond blockchains. Secure communication, anonymizing protocols, lots of things need public-key encryption. And unfortunately there are long-standing mathematical theorems showing why public-key encryption cannot be done with hashes alone. You have to have some kind of trapdoor object that has at least one form of usable "structure" - either group theory (incl. isogenies) or lattices or code-based or potentially in the future even more newfangled and spooky things (local mixing?). But for anything that has structure, you should assume that AI will make at least some progress in breaking that structure. Here, one reasonable inference is that if you want to make something plausibly long-term secure, multiply the key sizes by 10. To me that's a very plausible world and something not at all extreme to predict. If AI will bring us 50 years of math in 2 years, then that 50 years of math may very plausibly include a "naive factoring -> GNFS" level of improvement to our ability to break lattices. In that world, lattices will still exist, but they will have to be significantly bigger to guarantee the same level of safety. And at those new larger sizes, hash-based constructions will beat lattice-based constructions on concrete efficiency in every use case where hash-based constructions are possible at all. Theoretically, of course it's possible that hashes are broken too (eg. P = NP would imply that). But I think P = NP is very unlikely. And intuitively, it's much more likely that a mathematical object has exactly no exploitable structure (like hashes are intended to), than that a mathematical object has exactly ~3 forms of exploitable structure (for elliptic curves: associativity, Schoof, pairings) and not some secret fourth form of structure we have not yet discovered that greatly degrades its security (for elliptic curves, ECDLP and pairing security). Similar for LWE, SVP, RLWE and the zoo of lattice problems. For this reason, we do not yet see any reason to worry and start padding the byte size of hashes (if we start to worry more, we would pad the round count first before doing anything to the byte size). Concrete TLDR, my own personal views: * Hash-based > lattice-based, in those situations where hash-based is possible at all * For anything lattice-based, be much more paranoid on param sizes. Remember that blockchains are only a small portion of the cryptography story; this point goes far beyond blockchains and applies to eg. access to websites, secure messaging, Tor / VPNs ... * For privacy protocols, strongly favor NOT putting encrypted notes onchain. Instead, send them offchain through some third-party mechanism. * If it's not difficult for you, keeping your funds in addresses which have not yet been used to make a transaction is a good idea. If it's easy for you, do it. **But be careful about migrations; I personally have lost more money in botched migrations than I have lost in all hacks combined**. * For multisig wallets, doing confirmations offchain is better than onchain, because this way the signatures of signer wallets do not get exposed to the public, so if ECDSA falls to AI much faster than expected, at least the multisig "gracefully degrades" to a 1-of-1 where the 1 is whoever was gathering the signatures - a much better place to be than "anyone can take the money" https://t.co/oVjwZog2lL

RailsdevelopingOriginal ↗

Reviewed through 04:58 UTC · editorial order, not engagement rank

Markets

The tape, without the theatre.

Latest market data · 24h snapshot

What moved, and by how much.

This panel compares each provider quote with the quote 24 hours earlier. Editorial stories remain in the Editor-in-Chief’s priority order instead of being repeated or pulled into this fixed data region.

Mixed · breadth 44/100. A score of 50 means the tracked assets were flat on average.

24-hour price changeLatest · 04:58 UTC
Each row compares the current provider quote with its quote 24 hours earlier. Bar length is scaled to the largest move shown.
BTC$82,597.00
−1.81%BTC was 1.81% lower than the provider quote 24 hours earlier. Snapshot: 04:58 UTC.
ETH$2,560.26
−1.94%ETH was 1.94% lower than the provider quote 24 hours earlier. Snapshot: 04:58 UTC.
SOL$114.88
−2.73%SOL was 2.73% lower than the provider quote 24 hours earlier. Snapshot: 04:58 UTC.

Exact percentages are printed beside every row; color is supplemental.

Founding membership

Finish crypto before breakfast.

Get the complete Daily Trenches: a five-minute brief, cited source trail, audio edition, and every past front page.

Planned founding rate $8 / month · cancel anytime

No checkout yet. Submit to request an invite by email; nothing is stored silently.