Integrate in minutes, debug without leaving your IDE. Docs, SDKs, and auth optimized for agentic development.
Answers to common questions and 24/7 support regardless of subscription.
Solana is a high-throughput L1 blockchain that uses a Proof-of-History–assisted PoS design to deliver low-latency, low-fee transactions and rich on-chain data via JSON-RPC (HTTP + WebSocket). It’s attractive for market-intensive apps (swaps, MEV-aware tooling), games, and real-time UX because of throughput, subsecond confirmations (at low commitments), and mature RPC surfaces.
gRPC (Google Remote Procedure Call) is a high-performance, open-source framework, unique to Solana, that uses HTTP/2 and Protocol Buffers for fast, efficient data exchange. It enables real-time streaming and strongly-typed APIs, making it ideal for Web3 and large-scale applications.
Yes. To avoid rate limits, you can:
Use 1inch Business plan configurator to configure and customize the RPS and Web3 calls based on your needs, rather than using public and shared endpoints.
Optimize the calls using WebSockets or gRPC.
Use the 1inch Balance API.
Batching:
JSON-RPC allows sending an array of requests; for account data, prefer getMultipleAccounts over many singles (keep batches modest to avoid timeouts).
Pagination:
For transaction history, use getSignaturesForAddress with the before/until, and limit parameters.
getProgramAccounts has no native pagination; restrict results using filters (memcmp, dataSize) and dataSlice.
Use gRPC, supported by 1inch.
Use filters aggressively (getProgramAccounts with filters + dataSlice) to shrink payloads.
Prefer WebSockets for streams (accountSubscribe, programSubscribe, logsSubscribe) instead of tight polling.
Paginate history with getSignaturesForAddress (limit, before and until).
Choose commitment wisely: use processed or confirmed for speed, finalized for consistency.
Respect rate limits (HTTP 429 + Retry-After) and apply backoff and retries; consider dedicated RPC for sustained throughput.