Architecture Overview¶
AnimeChain is a Layer 3 blockchain built on Arbitrum Orbital technology.
Layer Stack¶
L1 (Ethereum) → L2 (Arbitrum) → L3 (AnimeChain)
| Layer | Purpose | Security | Currency |
|---|---|---|---|
| L1 | Settlement & data availability | Ethereum PoS | ETH |
| L2 | Optimistic rollup scaling | Ethereum | ETH |
| L3 | Anime & gaming apps | Arbitrum One | ANIME |
Rollup of a Rollup¶
Rollup-of-a-rollup (visual)¶
- Batching on L3: AnimeChain’s sequencer orders transactions and produces L3 blocks on a ~2s cadence.
- Compression: Recent L3 blocks are periodically compressed into a single L2 transaction (a “package”).
- Submission to L2: The package is posted to Arbitrum’s inbox. When Arbitrum is ready to accept the message, it ingests the package and replays/updates L2 state accordingly.
- Result: L3 state commitments and any cross-chain messages become available on L2 once the batch is accepted.
- Batching on L2: Arbitrum batches L2 data and posts commitments/calldata to Ethereum for data availability.
- Optimistic finality: L2 outputs are considered correct unless challenged. After the challenge window closes (typ. ~7 days), the posted state roots are finalized on L1.
- Result: Once finalized on L1, withdrawals and cross-chain messages from L2 to L1 can be proven and executed trustlessly on Ethereum.
Cross-Layer Message Timing (Examples)¶
These real examples illustrate why L3 → L2 (and onward to L1) can take time.
In a cross-chain flow, your transaction first executes and finalizes on the source chain (e.g., L3). Then, its effect is conveyed to the next layer via a batched message: L3 compresses recent blocks into a rollup “package” and posts it to L2’s inbox; L2 only reflects the change after it reads and processes that inbox. Each hop has its own cadence and finality rules (e.g., L3→L2 inbox reads can be on a multi‑hour schedule; L2→L1 also includes an optimistic challenge period). Therefore, “confirmed on L3” does not immediately imply visibility or effect on L2/L1 until the message is ingested and processed at each hop.
The transaction is confirmed on L3 but has not yet been sent to L2. It will be included in a future L3 → L2 rollup batch.
The rollup has been posted to L2, but Arbitrum has not yet opened and processed its cross-chain inbox. This can be on a multi‑hour schedule (up to ~12h).
The message has been read and processed; the transaction is reflected on L2 and downstream state is updated.
Note: Inbound funding/messages L1 → L2 → L3 are typically much faster than outbound L3 → L2 → L1.
⚙️ Components¶
- Sequencer: Orders transactions (~2s confirmations)
- Bridges: Token/data movement between layers
- Fraud Proofs: 7-day challenge window for security
- Data Availability: Compressed calldata posted to L2
🚅 Performance¶
- Block Time: ~2s (responsive gaming UX)
- TPS: 1,000+ (NFT mints, in-game transactions)
- Gas: 0.1-1 gwei (affordable micro-transactions)
🗺️ Data Flow¶
Transactions → AnimeChain → Arbitrum One → Ethereum (for censorship resistance)
Links: Use AnimeChain • Animecoin • Start Building