👋
Hyperstrate provides private transaction infrastructure for Polygon. Sign transactions with your existing wallet infrastructure, submit the serialized payload to Hyperstrate, and monitor delivery and execution through one API.

Build private Polygon transaction flows

Hyperstrate helps applications submit signed Polygon transactions through configured private delivery routes.

Your private keys never leave your infrastructure. Hyperstrate receives only the signed transaction, validates it against the configured Polygon chain, stores it securely for durable processing, and forwards it to qualified block-producer infrastructure.

Private transactions

Understand private delivery and its guarantees.

Send a transaction

Submit your first signed Polygon transaction.

How it works

Create a workspace
Your workspace owns its API keys, prepaid balance, transaction history, and usage.
Create a submit-scoped API key
API keys used for transaction submission require the submit scope. The secret is displayed once, so store it securely.
Discover the active Polygon configuration
Use GET /v2/networks to verify the chain ID, submission format, capabilities, and current availability.
Sign the transaction locally
Build and sign the transaction with your existing wallet or signing infrastructure.
Submit the signed payload
Send the serialized transaction to POST /polygon/v2/transactions.
Monitor its lifecycle
Use the Hyperstrate transaction id to check delivery, execution, and billing state.

🔐
Hyperstrate never needs your private key or seed phrase. Sign transactions locally and submit only the serialized, signed transaction.

Why Hyperstrate?

Private delivery

Transactions are delivered only to configured, qualified private targets. Private mode does not fall back to public transaction broadcasting.

Durable intake

A successful 202 Accepted response means Hyperstrate has durably accepted the transaction for processing. Temporary worker or infrastructure interruptions do not require you to rebuild the transaction.

Observable lifecycle

Every submission exposes separate delivery, execution, and billing states. You can distinguish between a transaction waiting for delivery, accepted by a target, included on-chain, reverted, expired, or requiring review.

Non-custodial integration

You retain control of transaction construction, nonce management, fees, signing policies, and private keys.

Before you begin

You will need:

A Hyperstrate workspace
A submit-scoped API key
Sufficient prepaid credit when billing is enabled
A signed transaction for the chain ID returned by network discovery
An HTTPS client capable of sending JSON requests

Send your first transaction

Follow the complete submission workflow.

Polygon private transactions

Learn what private delivery does and does not guarantee.