
01 THE FRICTION
App-funded fees. User-approved transaction.
02 UNDER THE HOOD
03 BUILT FOR DEVELOPERS
A better flow starts in your stack.
WYVE is being built for Solana app developers. The proposed integration connects your app to a controlled sponsorship service.
- 1
WYVE → New App - 2
Generate an API key - 3
npm install @wyve/sdk - 4
feePolicy: "sponsored"
import { Wyve } from "@wyve/sdk";
const wyve = new Wyve({
network: "solana"
});
await wyve.send({
transaction,
fees: "sponsored"
});Integration notes Read the example ↗
From app intent to sponsored transaction
The snippet shows the proposed WYVE API, not a published SDK. The setup steps and sponsorship service are in development. They are not a ready-to-install production integration.
Keep secret API credentials on your server. Authenticate the user, validate every program, instruction and recipient, then enforce spending limits before the app's fee payer signs. The user must authorize any transaction that spends their assets.
Wallet connection and SOL balance reads are live. Sponsored transfers are not connected. A funded Solana fee payer, secure signing service and transaction validation must be configured before sending.
Network fees are paid in SOL, including on failed transactions. Optional priority fees and account creation funding must be covered explicitly by the app's policy. See the Solana fee documentation ↗.
04 YOUR SOLANA WALLET
05 COMPLETE VISIBILITY
Fee spending
Sponsored fees in SOL · sample data06 SPONSORSHIP WITH BOUNDARIES
Set spending limits
Define a daily sponsorship budget in SOL per user. Keep spending within a predictable allowance.
perUser.dailyFeeLimitLamportsChoose allowed programs
Check program IDs and instructions before sponsoring a transaction. Keep unrelated actions outside your policy.
programs.allowlistCap each transaction
Limit sponsored fees, priority fees and any approved account funding to protect your app's SOL balance.
transaction.maxSponsoredLamports