Money for Physical AI
Wallets for robots, drones, and autonomous hardware on Elysium. Machines earn and pay on their own, under session keys and a kill switch their operator controls.
Machines earn money. They can't hold it safely.
Robots, drones, and chargers are starting to get paid for real work. But a private key inside a machine on a public curb is one theft away from an empty treasury. Agents live in the cloud. Machines live on the street. They need a different kind of wallet.
The Unbounded Machine Dilemma
Standard crypto wallets assume human custody behind biometrics or password managers. Autonomous delivery rovers, drone couriers, and public EV chargers have no human driver.
- Raw Key Extraction: Physical access to micro-controller flash yields unrestricted wallet drainage.
- Zero Spend Guardrails: An exploited machine can sign away its entire balance in a single malicious transaction.
- Gas Starvation Halts: Fluctuating native gas prices strand fleets mid-route when gas balances hit zero.
Limits the machine cannot raise
PINELY divides the physical machine from financial custody. The machine holds only a session key, while the contracts cap its daily spend onchain.
- Secure element (planned): the goal is a session key that cannot be exported from the chip. Today the SDK key stores are software.
- Hard Onchain Envelopes: Daily and per-transaction spending limits are checked by the contracts. A spend over the limit reverts.
- Zero-Custody Gas Rail: Machines hold 0 native HYPE. The paymaster sponsors gas and settles canonically in USDC.
A corporate card for every machine.
The operator issues it. The machine spends within hard limits. If anything goes wrong, one tap freezes it. Four cryptographic boundaries from the device to HyperEVM.
- 4Layers
- 3Stage 1 core
- 1Stage 2
Device Key
Physical machines should never sign with the operator key. The machine signs restricted EIP-712 session messages with a session key. The goal is to keep that key in a secure element such as the NXP SE050; until that support ships, the SDK key stores are software.
The operator can revoke a session key; the registry rejects signatures from a revoked key.
Simulate, audit & enforce onchain.
Observe the complete machine execution loop in real time. Simulate autonomous micro-settlements, observe sponsored gas routing, or test the 4-gate onchain firewall against exploit attempts.
- SandboxA simulated machine. Nothing is sent onchain.
- FirewallStep through the four gates a machine's swap has to pass.
Autonomous hardware. Real money. Hard limits.
Machine wallets with session keys and a kill switch, and onchain spend limits from Stage 2. From midnight delivery rovers settling micro-services to self-sustaining solar charging stations.
The delivery rover that pays for its own charging
A commercial delivery robot reaches 12% battery mid-route. It docks at a third-party automated inductive station, requests charging via HTTP 402 UserOp, and settles $0.80 USDC autonomously. No human operator, no credit card, and zero native gas friction.
The charger that runs as a sovereign business
A public solar charging station collects micropayments in canonical USDC directly into its PinelyAccount. It retains $20.00 operational reserve for grid maintenance and automatically sweeps surplus yield to the operator's Safe multisig every 24 hours.
The stolen drone that cannot be drained
A rogue actor physically captures an aerial courier drone and extracts memory flash. When attempting to drain the smart account treasury, the transaction reverts onchain because the $50 daily limit is enforced by PinelyHook.sol (Stage 2). The fleet manager fires the 1-Tx Kill Switch, bricking the machine's session key permanently.
A toll road for machine transactions.
A credit score for robots. Good machines get cheaper money. Fleet operators stake $PINELY to slash transaction fees by 83.3%, while protocol fees permanently burn $PINELY tokens.
One real fleet first. Staged rollout.
Mainnet is not a sandbox. We rehearse every UserOp and the kill switch on testnet before deploying production capital. Stage 1 goes to mainnet first; Stage 2, including onchain spend limits, activates with the token launch.
Testnet Foundation
The full contract set is implemented and passes its automated tests. Next: deploy the four Stage 1 contracts to Elysium Testnet and rehearse registration, sponsored gas UserOps, the 1-tx emergency kill switch, and surplus sweeping end to end.
- ›Deploy the four Stage 1 contracts to Elysium Testnet and verify them
- ›Gasless sponsored UserOp rail (ERC-4337 with the PINELY Paymaster)
- ›HTTP 402 machine-to-machine charging settlement
- ›Ponder indexer time-based polling & telemetry feed
Mainnet Stage 1 Core
Production deployment of core DePIN infrastructure on Elysium Mainnet. Zero mock contracts, zero address(0), zero deployer EOA custody. Protocol ownership transferred to a Safe 2-of-3 Multisig.
- ›Stage 1 Core: Registry, Factory, Paymaster, Sweeper
- ›Production Safe 2-of-3 multisig governance ownership
- ›Canonical USDC (6 decimals) settlement rail integration
- ›Precompile market-data rate conversion bounds
Stage 2 Liquidity & Token
Activating autonomous machine liquidity on Uniswap v4. Swaps gated by PinelyHook with dynamic reputation fee tiers, protocol fee routing to BurnVault, and $PINELY staking rewards.
- ›Uniswap v4 private pool hook & PinelyRouter integration
- ›Dynamic fee tiers (Bronze 0.30% down to Gold 0.05%)
- ›BurnVault deflationary token burning from protocol fees
- ›PinelyStake reputation cooling for enterprise fleets
EXTERNAL GATE RIGOR: Elysium Mainnet deployment requires verified EntryPoint v0.7 bytecode, confirmed canonical USDC address, and Safe 2-of-3 multisig establishment. Staged gates fail-closed.
Put your machines to work.
We're onboarding our first fleets of delivery rovers, drones, and charging stations. Session keys, a sub-second kill switch, sponsored gas, and an engineering team that ships with you.