PIER
More possibility.
Keep the moment.
Cover the fee.
A new user shouldn’t have to leave your app to find SOL for a network fee.
PIER is building the layer that lets your application sponsor eligible transactions, with the budget and boundaries you choose.
One action.
Three parts.
The user acts.
A transfer, a payment, a next step inside your app.
The policy checks.
The action, the allowance and the available budget.
The app covers.
A funded sponsor pays eligible network fees in SOL.
Proposed sponsorship flow. Both user and sponsor provide the signatures their roles require.
Generous to users.
Precise by design.
Sponsoring an experience should feel deliberate. Set the boundaries that make sense for your application.
Your budget.
Start with a daily allowance you can measure.
Your actions.
Choose which programs and interactions qualify.
Your limits.
Define a ceiling for each user and transaction.
Estimates only. The lowest fee assumes two signatures and no priority fee. No funds move. Account creation and other transaction costs are excluded.
Your wallet.
A clear starting point.
Connect a Solana wallet and see your live mainnet balance. No signature. No funds moved.
Your balance appears after you connect.
A small layer.
A better experience.
PIER’s intended integration keeps sponsorship rules behind your app, where every request can be checked before a sponsor signs.
This architecture example describes the planned flow. A production SDK and sponsored transactions are not available yet.
// PIER sponsorship flow · architecture example
const policy = {
network: "solana:mainnet",
dailyBudget: "0.10 SOL",
maxFeePerAction: "0.00001 SOL",
allowedActions: ["token_transfer"]
};
// Validate the complete transaction.
// Set a funded sponsor as fee payer.
// Collect the required signatures.
// Submit and track confirmation.