Blockchains cannot read each other. A user holding Bitcoin cannot spend it in an application built on Ethereum, because the two networks share no ledger. Cross-chain bridges close that gap. The asset is locked, burned or pooled on one chain and the equivalent is issued on another, as two separate entries connected by a protocol. Our new blockchain basics article explains how bridges work, how they differ from decentralized exchanges and coin swap services, and where the compliance risk sits.

Blockchains are getting busier and cheaper at once. Ethereum: 68% more transactions year over year, cost down from $1.08 to $0.31. Solana: 9.8 bln transactions at half a cent. What cheap blockspace opens up for builders, from perps to agent-driven apps:

“Blockchains Are Cities” from @hosseeb and @jmonegro “Fat Protocols” are two pieces I’ve returned to repeatedly over the yrs But things changed in the last 10 years This piece looks at the trade-offs between ETH, SOL, and HYPE and why all 3 can win imo

blockchains are the everything exchange assets, information, ownership changing hands and settling every slot. the prize is being where information gets discovered. every new thing built there makes discovery faster for everything already there. it only compounds in one place.

Blockchains delivered self-custody for asset holders. LayerZero extends it to asset issuers: the infrastructure to issue, move, and secure any asset across any chain with the issuer itself able to attest every transfer. Read our latest article about Self Custodied Applications below:

Blockchains (like @solana) keep launching accelerators, incubators and holding contests to drive development in web3 ... will it help? Solana adds incubator to spur growth and woo founders away from rival chains

Public blockchains face a difficult design question as institutional participation grows: How can validators gain the controls they require without turning one compliance policy into a network-wide rule? Bringing configurable screening into Solana’s block-building process offers an interesting middle ground. Instead of enforcing a single standard across the network, each validator can determine which policies it wants to apply. That preserves validator autonomy and may make public infrastructure more usable for institutions operating under different requirements. But it also introduces a new kind of complexity. If validators begin applying different screening rules, transaction inclusion may no longer depend only on fees, network conditions or technical validity. It could also depend on which validator is producing the block and which policy that validator follows. Over time, users may need to understand not only how a network operates, but also which invisible rules influence the path their transactions take. Without sufficient transparency, one public blockchain could gradually begin to resemble several partially separated execution environments. In my view, programmable compliance could help public networks support a wider range of participants without forcing every validator to follow the same standard. But flexibility alone is not enough. Clear disclosure, measurable behavior and visibility into transaction filtering will be essential if users are expected to trust the system. The goal should be to expand access without weakening the neutrality that makes public blockchains valuable in the first place. Can validator-level policies bring more institutions onchain without creating different versions of the same public network?

These blockchains have more development than you might think... @chainspect_app's developer dashboard shows data on how many developers are currently active on each chain, featuring expected names like @Ethereum $ETH and @Solana $SOL. However, it also details some chains with impressive developer numbers, but that are less widely known than the aforementioned chains... @Polkadot $DOT [9,066] @Cardano $ADA [3,726] @0xPolygon $POL [1,811] @hedera $HBAR [1,325] @NEARProtocol $NEAR [1,216]

Public blockchains broadcast every transaction. For a company running payroll, that would mean publishing every salary and who receives it. Tempo Zones enable private transactions. The relevant parties see the details, the public doesn't. Learn more in our docs: