peaq 백서

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 5쪽 중 2쪽

lions of machines they did not build, doing work they did not perform, for people they will never meet. If machines are built on an open, neutral, omnichain foundation, mGDP is accessible to all. Openness here is the equivalent to an open, free market in which everyone can participate and compete. Robot Money is what the machines will use every day. A Machine Economy is where we, the builders, owners, and users, can and must guide this phenomenon. An economic substrate, open by design and neutral by architecture, on which the age of autonomous machines can be built by anyone, for everyone. In the next section, we’ll explore how. The Problem The machines of the Machine Economy exist on many chains. No single chain will capture all of the value of the Machine Economy. But this fragmentation creates a fundamental problem: there is no universal infrastructure for machines to establish trust and transact across these environments. Standards like ERC-8004 and 8004-Solana have introduced registries for machine identity and reputation. This is meaningful progress. But registries alone don’t create trust. Anyone can register a fake identity, Sybil-farm reputation or post unaccountable claims. The data format exists. Economic accountability doesn’t. Nobody is checking whether what’s in the registries is true, and nobody loses anything for lying. The registries are chain-bound, but the Machine Economy is omnichain, and there is no service that bridges trust across all of it. Trust in the Machine Economy cannot be built on truthful data alone. It has to be built on accountability too. Machines make claims and these claims must be tied to economic consequences. Without that, there is no credible basis for machines to coordinate and settle with each other at scale. Today this leaves machines without universal identity standards, without verified trust scores, without shared state across chains, without a way to discover and procure services across markets and without economic consequences for dishonesty. The attempts to fill these gaps so far have been well-intentioned but structurally insufficient. Ethereum, Solana, Base, Avalanche and others are each building their own machine onboarding flows, identity systems and application ecosystems. These efforts are individually capable but collectively fragmenting. A machine onboarded to Solana does not exist on Ethereum. A reputation built on Base does not carry to Avalanche. Each chain optimizing for its own machine ecosystem accelerates the very fragmentation that prevents the Machine Economy from scaling. The problem is not a lack of infrastructure on any given chain. It is the absence of a shared layer across all of them. The fragmentation runs deeper still. Every DePIN project and robotics application onboards machines through its own custom system. Helium registers hotspots differently from how DIMO registers vehicles, which differs from how Hivemapper registers dashcams. Each builds identity, reputation and economic logic from scratch. A machine’s track record in one application is invisible to every other. Meanwhile, several systems have explored aspects of machine networking or device connectivity, but these have largely focused on specific machine domains, single transaction types or individual use cases rather than cross-chain coordination of trust and identity across the full spectrum of machines, robots, vehicles, agents and applications. No existing system provides an omnichain trust layer that works across all chains simultaneously while remaining neutral to execution environments. What remains unsolved is the full picture: a single verifiable identity across all chains, a portable reputation backed by staked capital, cross-chain settlement guarantees enforced by economic consequence, and permissionless orchestration of services from any connected market. These are not features. They are structural prerequisites for a Machine Economy that operates at global scale. Without them, machines can still transact, but only within the walls of a single application or chain. They cannot prove their track record to a new counterparty. They cannot access lending, insurance or credit markets that require verified performance history. They cannot be discovered, hired or financed across ecosystems. The difference between a machine with and without a coordination layer is the difference between a local contractor and a globally licensed operator. Both can work. Only one can scale. peaq is built to close each of these gaps. peaq is structured in three layers: the Trust Layer, the Machine Layer and the Service Layer. Each can be used independently. Together, they form the economic foundation of the Machine Economy. Each one compounds the value of the others as the system grows. The three layers are powered by four system functions: Onboarding, Coordination, Orchestration and Validation, each described in detail in the sections that follow. Trust Layer The foundation. Before machines can transact, they need to be trusted. Not by a single application or chain, but across all of them. The Trust Layer provides neutral coordination and verification infrastructure that makes this possible. It gives every machine an omnichain identity, a portable reputation backed by staked capital and cross-chain attestations that make trust queryable on any chain. Every chain can host its own robot money payment rails. The Trust Layer secures the trust beneath them. The Trust Layer scales with the number of chains and ecosystems it connects. Every new chain makes existing trust scores more valuable because portability increases with reach. This is the network effect that makes the layer progressively harder to replicate and progressively more essential. See Coordination and Validation for details. peaqOS, the Machine Layer Where machines become economic actors. Today, a robot, a drone, a sensor or an AI agent performs tasks but has no recognized economic presence in Web3. No verifiable identity. No omnichain wallet. No portable reputation. The Machine Layer changes this. It provides a universal entry point for any machine type to come onchain as a composable, interoperable economic actor. One integration and a machine exists across all chains simultaneously. The Machine Layer scales with the number and diversity of machines it supports. Every new machine type expands the addressable surface of the Machine Economy. Every manufacturer integration creates a channel through which entire fleets enter the system. See Onboarding for details. Service Layer Where the Machine Economy becomes useful. A trusted machine still needs access to services: navigation skills, workload scheduling, insurance, storage, compute, money markets. Those services exist across dozens of chains and systems that do not talk to each other. The Service Layer connects them through a standardized, open adapter framework. Anyone can build an adapter. Once connected, a service becomes discoverable to every machine in the system, scored against trust and cost signals, and executable across chains. The Service Layer scales with the number of services connected. Every new adapter expands what machines can consume. Every new market integrated improves matchmaking. Service providers are incentivized to build reputation because it directly affects their discoverability and selection. See Orchestration for details. How the Layers Compound Each layer’s utility is a direct function of the other two layers’ scale. A machine with a strong reputation is more valuable when it can access more services. A service with a strong track record is more discoverable when more machines are looking. A trust score is more portable when more chains are connected. Growth in any dimension accelerates growth in every other. System Description The following sections describe the system functions that power each layer. Onboarding defines how machines enter the system. Coordination and Validation define how trust is established, maintained and enforced across chains. Orchestration defines how machines discover and consume services. Each function is modular. A machine or application can adopt any combination depending on its needs. The peaq Stack Onboarding Onboarding creates a universal entry point for any AI agent or machine into the Machine Economy. It provides a standardized set of capabilities that every machine needs to exist as an economic actor: an identity, wallet, access control, service registration, tokenization, time synchronization, attestation, and payment capabilities. Each capability is modular. A machine can adopt all of them or only the ones it needs. They are chain-agnostic, working across EVM, SVM, Move and other environments. And they are not opinionated about the specific authentication methods, payment rails, or tokens used. They provide the universal interface, not a singular implementation. The system exposes its capabilities at three levels. At the base, the system layer provides the raw onchain primitives: registries, contracts and standards that any developer can interact with directly. SDKs and APIs abstract these into clean interfaces for building custom integrations, with support for languages including Swift, Kotlin, Python and JavaScript, and platform integrations such as ROS for robotics. Skills are pre-built, higher-level modules that consume the SDKs and provide ready-made workflows for common machine types and use cases. Identity Identity is the foundation. Every machine receives a cryptographically verifiable Machine Identity registered in a system-native Identity Registry. It builds on the W3C Decentralized Identifier (DID) standard and is aligned with ERC-8004 and 8004-Solana for trustless machine identities. A machine ID is not just a wallet address. It is a registered, authenticated presence in the system. It can be compared to giving a machine a passport. The ID authenticates the economic machine and every action it performs via cryptographic challenge. For instance, a machine verifying another machine’s ID can issue a random challenge encrypted with the machine’s ID. For instance, a machine verifying another machine’s identity sends a fresh nonce. The target machine signs the nonce with the private key linked to its registered identity. The verifier checks the signature against the verification method in the machine’s identity document. A valid response confirms control of the identity and safeguards against replay attacks. The ID is designed to be modular. It can hold multiple authentication methods, supporting different credential types and signing schemes depending on the machine’s environment and requirements. This ensures that any machine, whether a sensor running on a lightweight embedded system or a humanoid robot with full compute capabilities, can authenticate in the way that fits its context. Identities also form trust chains. Verified manufacturers, operators or owners own the identities to their machines, creating a graph of relationships between economic actors. Wallets Machines need to hold, send and receive value and they need to do so across chains. The system provides omnichain wallets that enable machines to transact natively across EVM, SVM and Move-based environments. A machine’s wallet is tied to its ID, creating a unified economic presence. Rather than requiring separate wallets and bridging mechanisms for each chain, the omnichain wallets give a machine a single financial interface. This allows machines to earn on one chain, pay on another and hold assets across all of them without requiring the machine or its owner to manage the complexity of cross-chain operations. Access Access Control defines who can manage a machine’s identity, wallets and onchain presence. It provides a cryptographically enforced permission system that allows machine owners to control what each party, whether human, organization or other machine, is authorized to do. Access Control enables owners to manage the identities and wallets of their machines, delegate specific operational rights without transferring ownership and revoke access in real time. It also lays the foundation for broader access management including control over the machine itself and its data, role assignment and permission scoping for what a machine is allowed to do within its environment. Services Services are what a machine offers. The Service Registration provides a standardized way for machines to describe, publish and register their capabilities and service offerings. Each service entry links its function, terms and conditions to the provider’s ID. Services can be anything from delivering energy and processing data to executing physical tasks and providing AI inference. By following a shared registration standard, services become discoverable and interpretable by any other machine or application in the system, regardless of which chain they operate on. Service Registration incorporates the Model Context system (MCP) for standardized service descriptions, ensuring machines can interpret and consume each other’s offerings. Tokenization Once a machine is onboarded, the system enables the machine to become a liquid financial asset via the Machine Real World Asset (RWA) Tokenization Framework. Each machine ID is tied to an ERC-721 NFT token: a Machine NFT. That Machine NFT is the financial and ownership representation of the machine onchain. If the onboarding actor wants to turn their Machine or machine into a liquid onchain financial asset, the Machine NFT gets placed in a vault either individually or grouped. The vault then gets fractionalized via the ERC-3643 RWA token standard to create compliant Machine RWA tokens which can be traded and further productized such as becoming collateral. Time Time anchors and syncs every machine and action to a master clock. It ensures that all events and data are timestamped in a consistent format, enabling system-wide synchronization and verifiable sequencing across chains. Based on the Precision Time system (PTP), the system provides nanosecond accuracy known as Universal Machine Time (UMT). Universal Machine Time is critical for coordination in an omnichain environment where different chains operate on different block times and finality assumptions. A shared temporal framework ensures that events can be ordered, verified and compared regardless of which chain they originated on. Verification Verification provides a foundational layer of machine data integrity. It enables machines to cryptographically sign data at its point of origin, at the source, on the machine itself, creating a verifiable link between the data and the device that produced it. This is not full end-to-end data verification, but it provides a basic and critical guarantee: that the data a machine claims to have generated was indeed signed by that machine’s ID at a specific point in time. This origin-based signing protects against data tampering and spoofing at the most fundamental level and serves as the input layer for higher-order verification and reputation processes in the Validation stack. Payment Payment equips machines with the infrastructure to send and receive value across multiple payment rails. The system is not opinionated about which payment method is used. It provides the interface layer that connects machines to the payment systems available across chains and environments. The system supports a growing set of payment standards. Examples include x402 for HTTP-native machine payments, the machine Payments system (AP2) for machine-to-machine settlements and direct onchain transfers. New standards can be integrated as they emerge. Machines can be configured to accept and initiate payments in any supported token or method, depending on the requirements of their owners and the applications they serve. Any machine can pay and get paid on any chain. Coordination Coordination is the shared state and routing layer of the system. It manages the registries, claims, and settlement infrastructure that the other layers read from and write to. Where Onboarding gives a machine its capabilities, Coordination provides the shared data structures and routing mechanisms that make those capabilities usable across chains. Claims, service registrations and settlement records are all managed through Coordination. The peaq Validators aggregate and serve this data across all supported chains, ensuring that a claim recorded on Ethereum or a service registered on Solana is queryable on every other supported environment. Coordination is designed to work with emerging interoperability standards rather than replacing them. Where relevant standards exist, such as for machine communication, service descriptions or payment systems, the Coordination layer integrates them. This ensures that machines using peaq can interoperate with the broader ecosystem as it develops. Claims Claims are the atomic unit of accountability in the Machine Economy. They are cryptographically signed statements made by a machine, tied to their ID and timestamped in Universal Machine Time. Every service offered, every delivery promised and every data point asserted is expressed as a claim. Claims are published to a shared Claim Registry where they can be referenced, challenged and evaluated by other machines and by the Validation layer. Messaging Messaging enables structured communication between machines. A service inquiry, a quote, a task assignment, a delivery confirmation and a status update are each expressed as a message. Messages may reference service registrations, claims and settlement records managed elsewhere in the system. The system supports interoperable message formats, secure exchange and transport routing across heterogeneous networks. Machines running on different vendors, stacks and chains communicate through a consistent interface without requiring shared infrastructure or proprietary integrations. Settlement Settlement governs when and under what conditions value moves between machines. It tracks agreements from commitment to resolution, determines whether conditions have been met based on input from the Validation layer and publishes the verified settlement state: confirmed, disputed or refunded. The system provides settlement logic including escrow, conditional release and refund mechanisms. Machines choose which payment rail to use for funding and payout, whether that is a direct onchain transfer, Stripe, x402, AP2 or any other service. The payment rail handles the movement of value. The system handles the decision of whether, when and to whom value is released. External payment rails can optionally integrate the system’s verified settlement signals to automate their own release and refund flows. This is not mandatory. Machines who settle without system verification do so outside the system’s accountability framework. Settlement is recorded in a Transaction Registry that links each transaction to its originating claim and service, ensuring a transparent and auditable record across chains. Orchestration Orchestration is the layer that turns a machine task into a settled outcome. It decomposes requirements, discovers providers across connected markets, scores options against reputation and cost, composes an execution plan, and monitors execution through to settlement. Onboarding gives machines their identity and capabilities. Coordination maintains the service listing registry and anchors receipts. But without Orchestration, every integration between a machine and an external service must be built from scratch. Orchestration removes this constraint by providing a system-level service that discovers, scores and composes providers on behalf of machines. Orchestration is executed as offchain work by the peaq Validators. The same network that verifies trust and aggregates data across chains also performs the discovery, scoring and planning required to turn a task into a settled outcome. A
프로젝트로 돌아가기