Knowledge built for everyday crypto users — and for the people behind the protocols.
Three streams of content, one editorial standard: every claim links to data or admits its limit. Pick the one that matches what you're trying to do right now.
- 20articles published
- 3content streams
- 1active authors
Pick the stream that matches your intent
Editor's picks
Is cross-chain swapping safe? An honest breakdown
Cross-chain swapping is reasonably safe when routing is non-custodial, contracts are audited on every chain used, and bridges in the path have a clean operational record. The biggest risk vector historically is not the swap layer itself — it's bridge contracts holding pooled liquidity, which have lost over $2.5B since 2021. Aggregators reduce (but don't eliminate) this by spreading volume across many bridges and using audited venues; you reduce it further by checking the destination chain, address, and starting with a small test for new routes.
Cross-chain swap vs bridge: when to use which
A bridge gives you the same asset on a different chain (ETH → ETH-on-Arbitrum). A cross-chain swap changes both the asset and the chain (ETH → USDC-on-Base). For single-asset chain switches, a direct bridge is simpler; for changing tokens, a cross-chain swap saves you a separate DEX trade and one round of gas. Aggregated routing usually beats a single bridge on price.
What is a cross-chain swap?
A cross-chain swap exchanges Token A on Chain X for Token B on Chain Y in a single, non-custodial flow. Under the hood, a routing engine combines a bridge transfer with one or more DEX trades, picks the cheapest path across many bridges and market makers, and settles the destination token to your address — usually within minutes, with funds in your control the entire time.
Latest articles
Multi-Pool Sandwich Risk: How DeFi Routes Detect Transient Wrong Prices
Multi-pool sandwich risk is not only local AMM slippage. Price impact, TWAP lag, oracle caches, liquidation thresholds, and cross-chain delay can combine into a transient wrong-price state. This article models defensive slippage VaR and route-level price-quality gates.
Under-Constrained ZK-Rollup Circuits: How Missing Constraints Break State Proofs
A valid ZK proof does not automatically mean a valid Rollup state transition. This article analyzes under-constrained circuits, Circom and Halo2 constraint semantics, SMT-based formal verification, static analysis, and why proof semantics matter for cross-chain routing.
Cross-Chain Bridge Signature Forgery and Merkle Proof Fraud: Where Verification Semantics Fail
Bridge failures often come from verifier semantics, not broken cryptography. This article analyzes signature-domain mistakes, Merkle empty witnesses, signer deduplication, validator-set timing, replay domains, and route-risk implications.
Solana Write-Lock Exhaustion: Account Contention, Local Fee Markets, and SVM DoS Defense
Solana parallel execution depends on declared account access. Hot writable accounts can serialize Sealevel execution and create local DoS pressure. This article analyzes conflict graphs, local fee markets, early drop, and routing defenses.
Yul and EIP-1153 Reentrancy: Transient Storage, Slot Overlap, and State Poisoning
EIP-1153 makes transaction-scoped locks cheaper, but it also creates new audit surfaces. This article analyzes Yul slot overlap, transient state poisoning, CFG reentrancy windows, delegatecall namespaces, and defensive static-analysis rules for EVM contracts.
Ethereum PoS Double-Signing Forensics: Validator Slashing and Reorg Boundaries
Ethereum PoS double-signing is compact consensus evidence, not just signing twice. This article explains BLS-backed proposer and attester slashing, LMD-GHOST reorg boundaries, balancing attacks, and how finality risk affects cross-chain route policy.
Decentralized ZK Prover Networks: Proof Markets, Front-Running, and Rollup Settlement Risk
Decentralized ZK prover networks are not just outsourced compute. This article analyzes proof task sharding, Proof-of-Useful-Work, proof-result front-running, tree aggregation, and hardware centralization as settlement risks for rollups and cross-chain routing.
Nested ZK Proofs for Layer 3 Settlement and Cross-L3 Refund Safety
Nested ZK proofs can compress L3-to-L2-to-L1 verification, but they do not remove preconfirmation risk, data availability constraints, proof lag, or refund ambiguity.
Validium DAC Risk: Data Availability and Cross-Chain Exit Safety
Validium cost savings come from moving data availability offchain. This article analyzes DAC certificates, data withholding, witness recovery, Rollup fallback, and AllSwap routing risk.
Modular Liquidity Layers: Virtual Balances and Cross-Rollup Settlement Risk
A modular liquidity layer does not create free liquidity. It uses solver inventory, virtual balances, and net settlement to reduce rebalancing frequency while making settlement risk explicit.
ZK-Rollup Escape Hatches: Forced Withdrawals and Cross-Chain Refund Safety
A ZK-Rollup escape hatch is not a fast-withdrawal feature. It is the final asset-safety boundary when sequencers censor users, proofs stall, or the Rollup enters frozen mode.
Cross-Rollup Atomicity: Shared Sequencers, State Locks, and 2PC
Shared sequencers can align input ordering across rollups, but they do not automatically guarantee atomic execution. This article analyzes state locks, 2PC, receipts, rollback, and route scoring.
Who writes this
Real names, real expertise, public contact channels. New contributors are vetted on technical accuracy and conflict-of-interest disclosure before joining.