Compute Contracts
Defines what data is used, how computation runs, who can see the results, and how participants get paid. If you are building on Palliora, this is the best place to start.
Accountable Privacy
How data and identities stay sealed by default, and the due process that can reveal a specific record. No master key, no silent access.
Guardian
A neutral node that coordinates data access and computation across the network. Guardians work as a group, so no single node can access data or change a contract on its own.
Compute Artifacts
The packaged, executable unit a Compute Contract actually runs: a model, function, or workload, published once and referenced by any number of contracts.
Actors and Roles
Who takes part in a Compute Contract: Publisher, Retriever, Guardian, compute node, Verifier, and Validator, and what each one is paid for.
Validator
Validators maintain the coordination ledger, confirm transactions, and agree on the order of blocks. They keep the public record that everything else in Palliora depends on.
Confidential Compute
Runs computation on sensitive data without exposing it to the machine or anyone operating it, using secure processor enclaves called TEEs. Only the outputs allowed by the contract are ever revealed.
Data Availability
Makes sure that data stored on the network can always be retrieved and has not been changed. Uses erasure coding and compact proofs so nodes can verify data exists without downloading all of it.
Threshold Encryption
Splits the ability to decrypt data across multiple Guardian nodes so no single party can unlock it alone. A minimum number of Guardians must cooperate before any protected data can be accessed.
Fees and Incentives
How a Compute Contract is priced, who gets paid when, and what keeps every actor honest.
PALI Token
What the PALI token is used for: fees, staking and rewards.
Glossary
Short definitions for every Palliora-specific term used across these docs.