Everything you need to know about running a CargoX relayer.
⚙️
How relaying works
1
How are signatures (documents) distributed to relayers?
Every active relayer is placed in a queue. Signatures are evenly distributed to every relayer
and reserved for 3 minutes. If the relayer fails to relay the document in that period,
the signature becomes "free for all" — any relayer can then claim it.
2
Which relayer gets a "free for all" signature?
It depends on several factors: relayer performance, network latency,
and how much gas fee the relayer is willing to pay per transaction.
Faster, higher-gas relayers have a competitive advantage.
3
Can I spam the CargoX API every second to grab free-for-all signatures?
No. The API result is cached for 1 minute, so hitting it every second makes no difference.
However, if a new signature is reserved for your relayer, the cache is bypassed and you receive it immediately.
Most likely the Polygon network is congested and gas fees are too high for your current limit.
You need to edit the relayer code to increase the gas fee ceiling you're willing to pay per transaction.
7
How do I set a higher gas fee in the official relayer?
Open src/utils/process-signatures.ts — find SafeGasPrice, replace with FastGasPrice.
Open src/api.ts — do the same replacement.
In extreme conditions, replace FastGasPrice with a custom numeric value (e.g. 200).
8
My transactions are stuck — how do I fix them?
Two options:
Send a replacement transaction with a higher gas fee manually via MetaMask (same nonce, higher gas).