Skip to content
Satnam SatoshiIn service of humanityFind your place ↗
Menu
Lesson 17 / 21 · Expert

Arc, Base and cross-chain dependencies

Name the settlement rules behind the interface.

14 MIN WITH PRACTICEREAD → TRY → REFLECTNO WALLET NEEDED

By the end, you’ll be able to…

  • Explain why EVM compatibility does not imply Bitcoin security.
  • Map a cross-chain workflow into distinct finality and exit steps.
Your learning map

Three questions to carry into this lesson.

01Explain why EVM compatibility does not imply Bitcoin security.
02Map a cross-chain workflow into distinct finality and exit steps.
Use these goals to guide your reading. Try the paper exercise, then explain the result in your own words.

Compatible software can sit on different foundations

EVM compatibility helps applications use familiar contract tooling, but it does not define a chain’s consensus, validator access or withdrawal process. Arc’s documentation describes a permissioned validator set using Malachite, a Tendermint BFT implementation. Base documentation describes deriving its L2 chain from data published to its L1. Neither should be presented as Bitcoin proof-of-work settlement.

A bridge adds a separate transition

A cross-chain action can involve custody, locking, burning, minting, proofs or external messages depending on the design. The exact bridge and asset determine the assumptions. Submission on the starting chain is not automatically usable value at the destination. Identify each state and the evidence that advances the workflow; a single spinner conceals too much for an accountable financial interface.

Evaluate the whole exit route

In a fictional architecture review, list the source chain, destination chain, asset contracts, bridge mechanism, administrative powers, fees and expected waiting conditions. Then remove the usual front end and ask what the authorized human can still verify or recover. A decentralization goal should be expressed as dependencies to reduce, not a claim that a particular deployment has no third parties. This course does not certify a bridge or imply that Arc and Base inherit Bitcoin’s consensus guarantees.

Your turn / A paper experiment

Practice on paper

A product runs the same Solidity interface on two chains. Which conclusions cannot be inferred from that fact alone?

I’ve tried it — show the worked answer

You cannot infer identical consensus, validator openness, finality assumptions, gas behavior, bridge safety or exit availability. Inspect each chain and deployment with its current official specification.

Want to explore with buttons and instant feedback? Try the practice lab ↗

Think it through

Make a choice. Discover why.

Choose an answer and check the explanation. You can retry as often as you like. These are practice questions, not a test of mastery; answers are not saved or sent.

1. Does EVM compatibility mean Bitcoin proof of work?
  • Yes
  • No
Read the explanation

No. Execution compatibility and consensus are different properties.

2. Is a source-chain transaction alone proof of destination availability?
  • Yes
  • No
Read the explanation

No. The complete transition must be verified.

One idea to take with you

Describe every trust boundary in a cross-chain flow.

Your learning, at your pace

Read every lesson freely. Optional progress tracking needs JavaScript and browser storage; it does not require an account or wallet.