pinely @pinely_protocol - Twitter Kullanıcısı

Sabitlenmiş Tweet

yaklaşık 18 saat önce

PINELY is live on Robinhood Chain Mainnet Money for Physical AI. CA: 0x415fa0f3480e7c1115ef052f9a7238827dc288cf PINELY’s Stage 1 contracts are now deployed on Robinhood Chain Mainnet (Chain ID 4663), owned by a 2-of-3 Safe multisig, and anyone can verify them onchain. Robots, drones, EV chargers and sensors can now have their own onchain identity and ERC-4337 smart accounts. They get scoped session keys, sponsored gas and USDG settlement, and the operator always keeps control. Why this matters Machines are starting to earn and spend on their own. A delivery rover pays for its charging. A solar charger collects revenue. A sensor sells its data. But a machine in a public place can’t safely hold a private key. If someone steals the device, they steal the wallet too. Embedded hardware also shouldn’t have to manage ETH balances or estimate gas. PINELY gives machines a payment rail with identity, limits, and a stable unit of account, without ever handing them the owner key. How it works The operator owns the account. The machine only holds a scoped session key with allowlisted targets and an expiry of 30 days max. Machines don’t need ETH. The Paymaster sponsors native gas and bills the account in USDG. One-transaction kill switch. Freeze a single machine or the whole fleet. Revenue flows home. Balances above a reserve threshold get swept to the operator treasury. Deployed on mainnet Deployed across blocks 113,448,196 – 113,448,242: 8 transactions, about 0.000196 ETH in total gas. 🔹 MachineRegistry Machine identity, attestation hash, session key, policy and freeze state. The 2 USDG anti-Sybil registration fee goes to the Safe treasury. 0x75Eb65C532207617B7b0CdC34348De376B16920B 🔹 PinelyAccountFactory Deterministic ERC-4337 machine accounts via CREATE2. 0x1d312F5264202350F006789d18Ae3f21b2d00712 🔹 PinelyPaymaster Sponsors ETH gas and bills in USDG. A price circuit breaker uses owner-set bounds and a staleness check, so sponsorship stops if the price is out of range or too old. 0x70C63C0Fb54028F6F2b30c38d9f11f9696ACB1BC 🔹 SurplusSweeper Moves revenue above the reserve threshold to the operator treasury. 0x49a09d2558C4497913eAda66DB0e3ce1e7c0B579 🔐 Safe (owner and treasury), 2-of-3 0x340B621D1BB4Be8b25D75fbBD9a628eD491030dD External dependencies Paxos USDG (6 decimals): 0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168 ERC-4337 EntryPoint v0.7: 0x0000000071727De22E5E9d8BAf0edAc6f37da032 Governance and security The Safe owns everything that matters. Ownership of the Registry and Paymaster was transferred to a 2-of-3 Safe with three distinct signers. The deployer is not one of them, and we read the ownership back onchain after the transfer. The deployed bytecode matches the local build. We compared all four contracts, with immutable values masked. No private keys in files. We deployed with an encrypted keystore. Mainnet guards. Deploy scripts reject mock tokens, zero addresses, test keys, a non-Safe owner and the wrong chain id. Domain separation. EIP-712 uses the PINELY domain plus the chain id. The machine verifies before it signs. The TypeScript, Python and ROS2 SDKs check the exact UserOperation against 13 attack classes. We rehearsed first. The full Stage 1 deployment ran on Robinhood Testnet (46630) before mainnet. Where we honestly are A deployment is not a finished product, so here’s the plain status: The contracts are not externally audited. No UserOperation has gone through mainnet yet. The first end-to-end test is next. The app, API and indexer are not deployed yet. The Paymaster price is set manually by the Safe. There’s no oracle feed yet. Spend caps are not yet enforced onchain in Stage 1, and hardware-backed key storage is still on the roadmap. Stage 2 (private Uniswap v4 pool, hook, staking, burn) and the $PINELY token are testnet only. This is guarded pre-beta. Please don’t route real value through it yet. Verify it yourself You don’t need a private key: bash RPC=https://t.co/x5j03GWtGt cast call 0x75Eb65C532207617B7b0CdC34348De376B16920B "owner()(address)" --rpc-url $RPC cast call 0x70C63C0Fb54028F6F2b30c38d9f11f9696ACB1BC "owner()(address)" --rpc-url $RPC cast call 0x340B621D1BB4Be8b25D75fbBD9a628eD491030dD "getThreshold()(uint256)" --rpc-url $RPC Both owner calls should return the Safe, and the threshold should be 2. 🔍 https://t.co/CTxnVoNseC What’s next The first sponsored UserOperation on mainnet through the bundler Launching the app, API and indexer An external security audit Onchain spend caps and hardware-backed keys Stage 2 and the token launch Build with us Running a fleet of robots, drones, chargers or sensors? Building on ERC-4337 or DePIN? Let’s talk. 🌐 https://t.co/iBbNPOx5Kh

40

49

4

2

3K

pinely

@pinely_protocol

Sotwe'de En Son Ziyaret Edilenler

Senin İçin Trendler

En Popüler Kullanıcılar