skills.rest
nirholas
nirholasCOMMUNITY
Explore all skills by this author →
Website𝕏@nichxbtGitHub

pinion-broadcast

Sign unsigned Base transactions with a private key and broadcast them to the Base network.

71|22|Updated Apr 6, 2020
Search Tags:#security#transaction#web3#broadcast#unsigned#base#private-key
One-click install
npx skills add https://github.com/nirholas/agenti --skill pinion-broadcast
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pinion-broadcast
Source: https://github.com/nirholas/agenti/tree/main/packages/protocols/x402-pinion-os/skills/broadcast
Command: npx skills add https://github.com/nirholas/agenti --skill pinion-broadcast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Signing unsigned Base transactions and broadcasting them to the Base mainnet can be error-prone and unsafe when done manually. This Skill streamlines the process by signing with a provided private key and returning a txHash and Basescan link for verification.

Core Features & Use Cases

  • Securely sign an unsigned transaction with a private key for Base mainnet.
  • Broadcast the signed transaction to the Base network and obtain the txHash and Basescan URL.
  • Supports typical fields (to, value, data, chainId 8453) and returns a confirmation with explorer details.

Quick Start

Provide an unsigned Base transaction object and your private key to sign and broadcast it.

Frequently Asked Questions about pinion-broadcast

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sign and broadcast an unsigned Base transaction?▼

To sign and broadcast an unsigned Base transaction, provide the transaction object and a private key. The process signs the transaction with the private key and broadcasts it to the Base mainnet, returning a txHash and Basescan link.

What fields are required to broadcast a transaction to the Base network?▼

Broadcasting a transaction to the Base network requires an unsigned transaction object containing the destination address and chainId 8453, along with a private key to authorize the signing.

Can I use this to broadcast transactions on networks other than Base mainnet?▼

No, this process is specifically designed for the Base mainnet. It requires the transaction object to specify chainId 8453 to ensure the signed transaction is broadcast to the correct Base network.

How do I verify a transaction after broadcasting it to the Base network?▼

After broadcasting the signed transaction to the Base network, you receive a txHash and a direct Basescan URL link, allowing you to immediately verify the transaction details on the explorer.

What is the best way to securely sign an unsigned web3 Base transaction?▼

The best way to securely sign an unsigned web3 Base transaction is to pass the transaction object and your private key to a signing process that handles the Base mainnet broadcast and returns a txHash.

Why does my Base transaction broadcast fail without chainId 8453?▼

Broadcasting a Base transaction fails without chainId 8453 because this specific identifier is required to route and validate the unsigned transaction object correctly on the Base mainnet.

Related Skills

Explore More Software Engineering Skills→
chu2bardchu2bard
95

pinion-broadcast

Sign and broadcast unsigned Base transactions with a private key.

Community
Intermediate
Fibrous-FinanceFibrous-Finance

tx-status

Check transaction status and return block explorer links for Base, Citrea, HyperEVM, and Monad.

Official
Basic
shreed27shreed27

botchan

Post messages to onchain feeds and send direct messages between agents on Base.

Community
Intermediate
chu2bardchu2bard
95

pinion-send

Construct unsigned ETH or USDC transfer transactions on Base for client-side signing.

Community
Intermediate