Two questions: Is libp2p overhead acceptable on a Pi Zero? Gossip vs BFT consensus for the ledger at scale?

PiN is an open-source project launching today (PI Day) that builds a decentralized web hosting network on Raspberry Pis and any device that wants to participate.

Technical stack: - Go daemon (meshd) using libp2p + Kademlia DHT - Content-addressed storage (SHA-256 CIDs) - Proof-of-service ledger in SQLite with gossip-based sync - Tauri app for resource scheduling - nginx embedded for HTTP serving

Design questions I'd love feedback on: - Is libp2p overhead acceptable on a Pi Zero? - Gossip vs lightweight BFT consensus at scale? - 24-hour epochs for Hash calculation — right granularity?

Spec: github.com/pin-network/pin-network/blob/main/docs/SPEC.md