01 ·
replicate the content
you replicate content addressed by cid and limit by total size, region of origin, or creator/ministry. nothing is imposed — what you choose to replicate is your curation.
infra · provider nodes
provider nodes
the protocol does not distribute without persistence nodes. if you operate infrastructure — at home, in a regional data center, or on a trusted provider — you can render that service to the protocol.
a provider node is a go process that replicates content addressed by cid and proves that replication on-chain at regular intervals. the node receives fee-for-service compensation in cusdc proportional to verified uptime, volume of replicated objects, and region weight.
you do not need to be large. we expect most of the network to be composed of small operators — ministries, creator collectives, home operators with a proxmox and a decent connection. redundancy comes from number, not from size.
02 ·
prove replication
the node regularly answers proof-of-replication challenges. the validity of the proof determines compensation for the period. no valid proof, no compensation — simple and auditable.
03 ·
receive service compensation
the persistence pool contract on base pays cusdc per hour of audited replication. this is fee-for-service compensation for what you execute — not a yield on invested capital, not a profit share, not a securities offering.
legal nature of the relationship
the relationship between provider node and aevia llc is an infrastructure service provision. you operate your own hardware, network, and operations; you define your own replication policies within the protocol rules; and you are compensated for the service effectively delivered. participation does not constitute an offer or acquisition of securities, collective investment vehicle, or investment contract under the howey test (sec v. w.j. howey co., 328 u.s. 293). operators are responsible for local tax and regulatory compliance (applicable money transmitter licenses, revenue declaration, etc.).
aevia does not distribute without provider nodes. render that service.
the waitlist is run by email. send me your hardware spec, bandwidth range, region, and operational jurisdiction. i reply in days — one-by-one, no newsletter.
“redundancy comes from number, not from size.”