Skip to main content

Sponsorship Models

VelumX supports two sponsorship policies. Choose based on your business model.

DEVELOPER_SPONSORS

The developer’s relayer pays STX gas. Users pay nothing at all.

How it works

  1. Developer builds any Stacks contract call with sponsored: true
  2. User signs the transaction (no STX needed)
  3. velumx.sponsor(signedTxHex) — relayer co-signs and broadcasts
  4. On-chain: the contract call executes, relayer pays STX gas

No paymaster contract needed

The developer calls any protocol contract directly — Bitflow, ALEX, Velar, StackingDAO, custom contracts. VelumX doesn’t need to know what contract is being called.

Best for

  • Zero-friction onboarding (day-0 users with empty wallets)
  • Subsidized DeFi experiences
  • Any protocol action — unlimited coverage

USER_PAYS

The user pays a SIP-010 token fee. The developer deploys a paymaster contract that atomically collects the fee and executes the action.

How it works

  1. Developer deploys their own paymaster contract (copy velumx-defi-paymaster-v1 as template)
  2. User signs a transaction calling the paymaster
  3. velumx.sponsor(signedTxHex) — relayer co-signs and broadcasts
  4. On-chain: paymaster collects fee → executes action (atomic rollback if action fails)

Developer owns the paymaster

VelumX does not deploy a shared paymaster. Each developer deploys their own, customized for their protocol. This means:
  • Full control over what actions are supported
  • No dependency on VelumX contract upgrades
  • Immutable once deployed — no admin key risk

Best for

  • Sustainable fee models where users pay in the token they hold
  • Protocols where users already have stablecoins (aeUSDC, USDCx)
  • Revenue generation — developer earns markup on every transaction

Comparison


High-Impact Use Cases