Construct unsigned ETH or USDC transfer transactions on Base for client-side signing.
npx skills add https://github.com/nirholas/agenti --skill pinion-send
Please help me install this Agent Skill. Skill: pinion-send Source: https://github.com/nirholas/agenti/tree/main/packages/protocols/x402-pinion-os/skills/send Command: npx skills add https://github.com/nirholas/agenti --skill pinion-send
This skill enables developers and wallets to create an unsigned ETH or USDC transfer on Base so the end user can securely sign and broadcast the transaction, enabling seamless on-chain payments without exposing private keys.
Post a JSON payload to the skill endpoint with to, amount, and token to obtain an unsigned transaction ready for signing.
High-intent search queries and answers about installing and using this skill.
To construct an unsigned ETH or USDC transfer on Base, post a JSON payload containing the recipient address, amount, and token type to the endpoint. The system returns a raw transaction object with fields like to, value, data, and chainId ready for client-side signing.
Client-side signing for Base payment workflows works by having a server build the raw transaction object and return it to the client. The end user then securely signs the transaction in their wallet and broadcasts it to the Base network without exposing private keys.
Yes, you can build USDC transactions on the Base network by specifying USDC as the token in your JSON payload. The system constructs the unsigned transaction data field required for the ERC-20 transfer, returning it for user signing.
The best way to secure private keys in Web3 transaction building is to construct unsigned transactions server-side and delegate signing to the client. This ensures the server never handles private keys while still preparing the necessary transaction fields for broadcasting.
The payload structure needed to build a raw transaction object requires a JSON POST request containing the to address, amount, and token fields. This input generates an unsigned transaction with the correct value, data, and chainId fields for the Base network.
A limitation of building unsigned transactions for ERC-20 tokens like USDC is that the server must correctly encode the transfer function call into the transaction data field. The client wallet must also support signing and broadcasting raw transactions on the Base chain.
chu2bardConstruct unsigned ETH or USDC transfer transactions on Base for client-side signing.
nirholasSign unsigned Base transactions with a private key and broadcast them to the Base network.
trustwalletGenerate HD wallets, derive addresses, and sign transactions across 140+ blockchains.
zkp2pTransfer USDC directly between agent wallets on Base without escrow.
