ALGOFLOW Docs

Architecture

Understand how frontend assets, smart contracts, RPC providers, and indexing services fit together.

Last updated: 2026-03-22

Frontend Storage Layer

ALGOFLOW deploys static HTML/CSS/JS assets to IPFS using content addressing (CID).

For production durability, keep content pinned on at least one reliable pinning provider.

  • IPFS is decentralized content distribution.
  • CID changes whenever file content changes.
  • Gateway URLs are easy to share but not ownership by themselves.

Smart Contract Layer

Business logic lives on-chain in deployed contracts. Frontend clients interact through ABI + address.

Contract state is persisted in blockchain storage and transaction writes require gas.

  • Bytecode is immutable at a contract address.
  • Upgradeable systems use proxy patterns.
  • ABI definitions are required for typed contract calls.

API Layer

Your frontend interacts with blockchain nodes through JSON-RPC providers such as MetaMask, Alchemy, or Infura.

Indexing APIs are optional but useful for fast history queries and analytics views.

High-level request flowtext
Browser -> Static Site (IPFS)
Browser -> RPC Provider -> Blockchain
Browser -> Optional Indexer API