Skip to main content

Overview

The StarkZap accepts configuration through a single options object. You can use network presets for simplicity, or provide explicit RPC URLs and chain IDs for custom setups.
New to blockchain? An RPC (Remote Procedure Call) is like an API endpoint for the blockchain—it’s how your app communicates with the network. A network is like an environment (production, staging, development). See the Glossary for more web2-friendly explanations.
The simplest way to configure the SDK is using network presets. Think of networks like environments:
  • mainnet = Production (real money, real transactions)
  • sepolia = Staging/Testnet (fake money for testing)
  • devnet = Local development (your own test blockchain)

Available Presets

Using Network Objects

You can also pass a custom NetworkPreset object:
If you run your own blockchain node or use a different RPC provider (like using a different API endpoint):
An RPC provider is like choosing which API server to use. Just like you might use AWS, Google Cloud, or your own servers, you can use different RPC providers to connect to the blockchain.
rpcUrl and chainId override values from network if both are provided.
Enable staking functionality to let users earn passive income by staking their tokens. When configured, users can:
  • 💰 Stake tokens in validator pools and earn rewards over time (like earning interest on a savings account)
  • 📈 Grow their holdings as rewards accumulate automatically
  • 🔄 Manage their positions by adding more tokens, claiming rewards, or exiting pools
  • 🏦 Support network security while earning passive income
Staking works out of the box using chain-aware staking contract presets:
If needed, you can override the default preset:
Ready to implement staking? See the Staking & Delegation Guide for complete instructions on how users can stake tokens, claim rewards, and manage their positions.
Configure optional cross-chain bridge settings when depositing assets from Ethereum or Solana into Starknet.
  • ethereumRpcUrl: Custom Ethereum RPC for bridge fee/balance operations
  • solanaRpcUrl: Custom Solana RPC (falls back to cluster URL if omitted)
  • layerZeroApiKey: Required for OFT/OFT-migrated routes
OFT routes require bridging.layerZeroApiKey and are supported on mainnet bridge routes only.
For the full deposit flow (getBridgingTokens, external wallet adapters, fee estimate, deposit), see the Bridging Guide.

Complete Configuration Example

Here’s an example with all optional features configured:

Using Network Preset

Using Custom RPC

For paymaster configuration, see the Paymasters Guide for detailed setup instructions for AVNU Paymaster or Cartridge’s built-in paymaster.

Configuration Type Reference

For paymaster configuration details, see the Paymasters Guide.

Next Steps