Web3 Pi ( @_Web3Pi_ ), a Golem Ecosystem project, has made a node small enough to sit on a shelf. Arkiv's testnet now runs on a Raspberry Pi 5. Here’s what it all means and how you can run your own node.
Building on a testnet starts with an application. Running a node brings you closer to the infrastructure behind it. Web3 Pi offers a way to explore both: connect to its hosted RPC demonstration, or run an Arkiv node on a Raspberry Pi 5 at home.
What is [ ARKIV ]
Arkiv is an Ethereum-aligned Web3 database, currently in testnet stage (Tiramisu, the current testnet is here).
-
You write data as entities with typed, indexed attributes.
-
You own the data with your own wallet.
-
You query it the way you’d query a Web2 database, and you decide when it expires.
-
Every write is a signed transaction.
Under the hood are DB-Chains: blockchains that run their state through a database engine, not the EVM. They’re coordinated by the Arkiv chain, which is linked to Ethereum.
The database engine is deterministic, so every node computes the same state, including one running on a Pi on your desk.
Want to take part? Here’s how:
-
Run one node at home. You need a Raspberry Pi 5 with at least 8 GB of RAM and a 2 TB NVMe SSD. It runs Arkiv’s execution and consensus clients and gives your apps a local RPC endpoint. You can watch it sync and see exactly how your app talks to the network. Power draw is around 6 W, as an indicative figure for a single node: actual use depends on configuration and workload. That makes it suitable to leave running all the time. A Pi-specific setup guide is in preparation.
-
Pool your own fleet. Web3 Pi Arkiv Proxy puts several nodes behind one endpoint. Before it routes a request, it checks each node’s chain, sync status, block freshness and distance from the chain head. It then chooses between eligible nodes on active load, configured weight and observed latency. You can add, pause or remove nodes while it keeps serving. The Web3 Pi Control Center shows the whole fleet in one view: topology, node readiness, chain progress, and hardware and client status.
-
Try the hosted fleet first. Web3 Pi runs Raspberry Pi 5 and x86 nodes behind its proxy. Ask the team on Discord for a personal API key and connect your app. The public dashboard is open without a key.
Where it stands today
This is an early proof of concept, and it already works on the Tiramisu testnet. Local nodes, fleet routing, API-key access and the Control Centre run together today. The project is built and operated by Web3 Pi, working with the Arkiv team. Arkiv is in active, pre-mainnet development, and this project will develop alongside it.
Explore the project and the live dashboard at arkiv-proxy.web 3 pi.io.
Find us at Devcon 8
Mumbai, 3 to 6 November. Come to the Arkiv booth for demo, discussion and collaboration opportunities.
▶ Watch the original video on X
Start building on [ ARKIV ]
npm i @arkiv-network/sdk
Docs: docs.arkiv.network · Hub: hub.arkiv.network · Community: discord.gg/arkiv