Skip to main content
Built for workloads that can’t tolerate a wrong answer: DeFi, AI agents, accounting. A stale, buggy, or manipulated upstream is outvoted rather than served, and a genuine disagreement is returned as an error instead of a guess. The Fanout tier is available on request. Contact us or email sales@goldsky.com and we’ll get you set up.

​
Checks & coverage

The methods below are fanned out to multiple independent upstreams (the standard tier tries one at a time). How the answer is settled depends on the method; expand any one to see it per network.

​
Consensus

The request goes to several independent upstreams; the answer is returned only when enough come back identical, so a lone wrong or stale node is outvoted.

​
Highest value

We query several upstreams and keep the highest, freshest value. A node that has fallen behind reports a number that is too low, which is enough to leave your transaction unmined or rejected.

​
Broadcast

We push it to every upstream in parallel for the widest, fastest propagation, and return the fastest response.

​
Under the hood

The tier layers two independent protections: cross-source consensus and per-response data-integrity checks. For reads with one canonical answer (state, blocks, logs, receipts), consensus sends the request to several independent upstreams in parallel via eRPC’s consensus failsafe and only returns a value once a quorum agrees. Fields that legitimately differ between client implementations (block timestamps, L1 metadata) are ignored, so only meaningful disagreements count. When sources genuinely disagree it returns an error rather than guessing, routing around any upstream that returned wrong data. The quorum isn’t hand-tuned: it’s sized per network from how many independent upstreams it actually has. Not everything has a single right answer to vote on. Gas price and priority-fee estimates are computed locally by each node, and eth_sendRawTransaction is a write, not a read. So the tier still fans these out to multiple upstreams, but applies the rule that fits: it keeps the highest value for eth_gasPrice / eth_maxPriorityFeePerGas / eth_getTransactionCount (so a stale, too-low estimate can’t stick you), and broadcasts eth_sendRawTransaction to every upstream in parallel for the widest, fastest propagation. Independently of agreement, every response runs through eRPC’s data-integrity checks: Can’t find what you’re looking for? Reach out to us at support@goldsky.com for help.