Loading interactive scene…

Explore the infrastructure
UserFARELESSSolana

01 THE FRICTION

A balance to spend. A reason to stop.

Your user has USDC. They want to send it. Asking them to buy another token shouldn't be the next step.

WITHOUT FEE SPONSORSHIP01 / 02 · EXAMPLE
Available balance100.00 USDC
You send$20.00 USDC
Insufficient SOL for transaction fees.
Transaction blocked

02 UNDER THE HOOD

One transaction. Every check in place.

FARELESS's planned sponsorship service applies your app's rules, while the user keeps control of what they sign.

01User
02App
03Fareless SDK
04App fee payer
05Solana
Proposed flow: policy checked. Fees sponsored in SOL. Confirmation tracked.
Identify the user01
Identify the requesting app02
Validate programs and instructions03
Estimate fees and account costs04
Check policy limits05
User approves and signs06
App fee payer co-signs07
Submit to Solana08
Track confirmation and spending09

03 BUILT FOR DEVELOPERS

Your app. Your fee policy.

Build on Solana. Decide which fees your app covers, without making users manage SOL just to complete an eligible action.

A better flow starts in your stack.

FARELESS is being built for Solana app developers. The proposed integration connects your app to a controlled sponsorship service.

  1. 1Register your app (planned)
  2. 2Set a sponsorship budget
  3. 3Validate eligible transactions
  4. 4Request user approval
Try the transaction flow
send-transaction.ts
import { Fareless } from "@fareless/sdk";

const fareless = new Fareless({
  network: "solana"
});

await fareless.send({
  transaction,
  fees: "sponsored"
});
Proposed SDK · Illustrative integration
Integration notes Read the example ↗

From app intent to sponsored transaction

The snippet shows the proposed FARELESS 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

Connect. Check. Explore.

Connect your Solana wallet to view your address and live mainnet SOL balance.

FARELESS ON SOLANA
No wallet connected
NetworkSolana Mainnet
SOL balance—

05 COMPLETE VISIBILITY

Less friction. More signal.

See what your app sponsors, how much it spends, and where your users are transacting.

FARELESS / OverviewIllustrative data
Transactions18,493 Example · all-time
Fees sponsored1.82 SOL Example · all-time
Success rate99.4% Example · all-time
Active wallets4,291 Example · all-time

Fee spending

Sponsored fees in SOL · sample data
0.080.040.00
30 days agoToday
A clear view of every sponsored interaction.

06 SPONSORSHIP WITH BOUNDARIES

Generous by design. Controlled by you.

Solana fees still exist. The app pays them for eligible transactions, within the sponsorship rules you define. These controls illustrate the planned service.

Set spending limits

Define a daily sponsorship budget in SOL per user. Keep spending within a predictable allowance.

perUser.dailyFeeLimitLamports

Choose allowed programs

Check program IDs and instructions before sponsoring a transaction. Keep unrelated actions outside your policy.

programs.allowlist

Cap each transaction

Limit sponsored fees, priority fees and any approved account funding to protect your app's SOL balance.

transaction.maxSponsoredLamports