A developer starter template demonstrating the full Polkadot technology stack through a Proof of Existence system — the same concept implemented as a Substrate pallet, a Solidity EVM contract, and a Solidity PVM contract. Drop a file, claim its hash on-chain, and optionally upload it to IPFS via the Bulletin Chain.

Students do not need to use every part of this repo. The runtime, pallet, contracts, frontend, CLI, Bulletin integration, Spektr integration, and deployment workflows are intentionally separated so teams can keep only the slices they want.

• Polkadot SDK Blockchain (blockchain/) — A Cumulus-based parachain compatible with polkadot-omni-node
  • Substrate Pallet (blockchain/pallets/template/) — FRAME pallet for creating and revoking Proof of Existence claims on-chain
  • Parachain Runtime (blockchain/runtime/) — Runtime wiring the pallet with smart contract support via pallet-revive
• Smart Contracts (contracts/) — The same PoE example as Solidity, compiled to both EVM bytecode (solc) and PVM/RISC-V bytecode (resolc)
• Frontend (web/) — React + TypeScript app using PAPI for pallet interactions and viem for contract calls
• CLI (cli/) — Rust CLI for chain queries, pallet operations, and contract calls via subxt and alloy
• Dev Scripts (scripts/) — One-command scripts to build, start, and test the full stack locally

# Start the parachain node + Ethereum RPC adapter (first build compiles the runtime ~10-20 min)
docker compose up -d
# Deploy contracts and start the frontend on the host
(cd contracts/evm && npm install && npm run deploy:local)
(cd contracts/pvm && npm install && npm run deploy:local)
(cd web && npm install && npm run dev)
# Frontend: http://127.0.0.1:5173

Only Node.js is needed on the host. The Docker build compiles the Rust runtime and generates the chain spec automatically. See contracts/README.md and web/README.md for the component-specific follow-up steps.

• OpenSSL development headers (libssl-dev on Ubuntu, openssl on macOS)

• protoc Protocol Buffers compiler (protobuf-compiler on Ubuntu, protobuf on macOS)

• Rust (stable, installed via rustup)

• Node.js 22.x LTS (22.5+ recommended) and npm v10.9.0+

• Polkadot SDK binaries (stable2512-3): polkadot, polkadot-prepare-worker, polkadot-execute-worker (relay), polkadot-omni-node, and eth-rpc. Fetch them into ./bin/ (gitignored) with:

  ./scripts/download-sdk-binaries.sh

  The stack scripts (start-all.sh, start-local.sh, etc.) run the same step automatically unless you set STACK_DOWNLOAD_SDK_BINARIES=0. Versions match the Key Versions table below.

• zombienet v1.3.x (npm install -g @zombienet/cli) for the local relay-chain + collator topology

• chain-spec-builder v17.0.0 (cargo install staging-chain-spec-builder)

Manual installs or other platforms: docs/INSTALL.md (release links and build-from-source).

The repo includes .nvmrc and engines fields in the JavaScript projects to keep everyone on the same Node major version.

# Start everything: node, contracts, and frontend in one command
./scripts/start-all.sh
# Substrate RPC: ws://127.0.0.1:9944
# Ethereum RPC: http://127.0.0.1:8545
# Frontend: http://127.0.0.1:5173

start-all.sh is the recommended full-feature local path. It uses Zombienet under the hood so the Statement Store example works on polkadot-sdk stable2512-3.

For the solo-node loop, relay-backed network, frontend-only startup, port overrides, or a second local stack, see scripts/README.md.

For component-specific next steps, see:

• contracts/README.md
• web/README.md
• cli/README.md

# Rust (requires nightly for rustfmt config options)
cargo +nightly fmt # format
cargo +nightly fmt --check # check only
cargo clippy --workspace # lint
# Frontend (web/)
cd web && npm run fmt # format
cd web && npm run fmt:check # check only
cd web && npm run lint # eslint
# Contracts (contracts/evm/ and contracts/pvm/)
cd contracts/evm && npm run fmt
cd contracts/pvm && npm run fmt

# Pallet unit tests
cargo test -p pallet-template
# All tests including benchmarks
SKIP_PALLET_REVIVE_FIXTURES=1 cargo test --workspace --features runtime-benchmarks
# Statement Store runtime + CLI coverage
cargo test -p stack-template-runtime
cargo test -p stack-cli
# Relay-backed Statement Store smoke test
./scripts/test-statement-store-smoke.sh
# Solidity tests (local Hardhat network)
cd contracts/evm && npx hardhat test
cd contracts/pvm && npx hardhat test

• docs/TOOLS.md - All Polkadot stack components used in this template
• docs/DEPLOYMENT.md - Deployment guide (GitHub Pages, DotNS, contracts, runtime)
• docs/INSTALL.md - Detailed setup instructions

• Pallet only: Keep blockchain/pallets/template/, blockchain/runtime/, and optionally cli/. You can ignore contracts/, web/src/components/ContractProofOfExistencePage.tsx, and eth-rpc.
• Contracts only: Keep contracts/ plus the Revive runtime wiring in blockchain/runtime/. The pallet and Bulletin integration are optional.
• Frontend only: The core PoE UI lives in web/src/pages/PalletPage.tsx, web/src/pages/EvmContractPage.tsx, and web/src/pages/PvmContractPage.tsx. The Accounts page, Spektr support, and Bulletin upload hook can be removed without affecting the basic claim flows.
• Optional integrations: Bulletin Chain, Spektr, and DotNS are isolated extras. They are documented locally in docs/TOOLS.md and can be skipped entirely for workshops or hackathons.

• Polkadot Smart Contract Docs
• Polkadot SDK Documentation
• PAPI Documentation
• Polkadot Faucet (TestNet tokens)
• Blockscout Explorer (Polkadot TestNet)
• Bulletin Chain Authorization - On Bulletin Paseo, use Faucet -> Authorize Account to request a temporary upload allowance for the Substrate account that will sign the upload.

MIT