Technical paper v1.0
A Layered P2P File Storage Architecture for Blockchain-Anchored IPFS Deployments
The paper describes the seven-layer architecture and four core algorithms of the PaliMesh storage layer, and validates its storage guarantee with a controlled experiment: a 50 MB file is uploaded to 5 geographically dispersed nodes, those 5 nodes are then destroyed, and the file is still retrieved intact from 3 production validators that never took part in the upload and were not adjacent to the source — showing that the storage guarantee is a property of the network topology, not of any single node.
⚠ The experiment ran on a separate validation network with chainId 18780; the production Canary is Palium 88780. The two must not be confused.
Experimental setup
Five uploading nodes across five GCP regions; three retrieving nodes are existing production validators that never received the original upload and are not in the source nodes' DHT neighbourhood. After pushToK and one repairTick cycle completed, all five uploading nodes were destroyed at once.
Finding
All three validators retrieved the file by CID and passed verification. The retrieval path relied on provider records and passively pushed replicas, not on any “source” node — the storage guarantee is a topological property.
Disaster-recovery guarantees
The paper states four guarantees: a single uploading node disappears, all uploading nodes disappear, replicas stay missing, the source node is replaced. Each maps to an algorithmic path: fetchRemote, pushToK / pushStripe, repairTick, and the CidRegistry anchor.
Issues found and fixed during evaluation
The experiment exposed two defects that never trigger on the happy path (PR #74, #75): provider records were not re-announced promptly after expiry, and repairTick pushed duplicates under concurrent retrieval. Both are merged to main and covered by regression tests.
The full specification, protocol parameters, and release plan live in the complete document and the linked pages.