Support FAQs
With our user-friendly platform and thorough documentation, our customer
Last updated
Was this helpful?
With our user-friendly platform and thorough documentation, our customer
Last updated
Was this helpful?
Q. How do I get started with my RPC subscription?
A. You can fill-out the that creates an entry in our client onboarding pipeline or if you have other questions mail us at or get in touch with us over or via .
Q. Do you require a long-term contract?
A. No, we bill month-to-month by default.
Q. What payment methods do you accept?
A. We accept the following:
USDC (SPL)
USDC-ERC20 on Ethereum
USDC on Tron
USDC on Polygon
Payments through hel.io (USDC)
Credit cards (through Coinflow)
Wire instructions in GBP and USD
Q. Should the need arise, can I upgrade/downgrade my plan at a later time?
A. Yes, if your usage changes, you can upgrade or downgrade your plan as needed. For dedicated nodes we uphold a one calendar month notice period.
Q. Can I cancel my RPC subscription anytime?
A. We require calendar months notice to cancel your subscription to align with our vendors' cancellation notice period.
Q. What happens when we hit the rate limits? Can you bump our current rate limits?
A. You would likely get 429 or 413 errors and yes we can bump your current rate limits but you may also want to slow down or decrease traffic.
Q. How do we know our ratelimits?
A. The limit per RPC method depend if traffic comes from a frontend or backend (with token authentication), for backend the current limits are:
snapshot: 2
genesis: 2
sendTX: 100
getProgramAccounts: 200
getTokenAccountsByOwner: 200
getLargestAccounts: 500
getTokenLargestAccounts: 500
getLeaderSchedule: 200
getVoteAccounts: 200
getClusterNodes: 200
getMultipleAccounts: 5000
getAccountInfo: 5000
sendTX: 100
Q. Where are Triton One servers located?
A. Our servers are geographically located in the Americas, Europe and Asia Pacific
Q. Can we run scripts in the shared/liquid endpoints?
A. Shared service is for frontend only. Running scripts is only allowed in backend and you would need a dedicated server.
Q. What happens if we suspect our token got leaked?
A. For existing customers, we will generate a new token and the old one/s will be disabled.
Q. How to use websocket option:
A. To use websocket option, just replace https:// with wss:// on your endpoint URL
Q. How can I use the Geyser plugins?
Q, We want geyser plugin installed in our node, does this require additional fee?
A. Installation of geyser plugin does not incur any additional fee. Our Geyser plugins are included as part of the dedicated server package and gradually will be deployed on shared servers.
Q. Can geyser also be used by people not running validator?
A. Yes. Geyser is RPC 2.0. Real time streaming of account updates. With Geyser, you can also see the account state changes within a slot. With RPC 1.0, you only see the final state at the end of the slot.
Q. What is the advantage of sending transactions through a validator?
A. There is a max of 2,500 QUIC connections per validator. 2,000 are reserved for other staked validators. Only 500 are available to anonymous & unstaked RPC nodes. During big market events all of the bots are fighting for the same 500 connections. By sending through a validator, you get access to the other 2,000.
Q. Is it possible for a transaction to be dropped even after it has reached the Commitment Status of "Processed" during periods of network congestion or temporary/minority network forks?
A. Yes, processed slots can still be dropped. Confirmed slots are reliable.
You can check more about .
A. We can install any geyser plugin to your node. You can refer to this list of available geyser plugins