Custom RPC URIs

Add your own RPC endpoint per network so a project’s transaction construction and reads try it first.

yield.xyz ships with its own RPC endpoints for every supported network. A project can add one custom RPC URI per network instead: your own node, or a third-party provider such as Alchemy, Infura, or QuickNode.

What it overrides

A custom RPC URI is tried first for on-chain reads and transaction construction on that network, for that project. If it fails or times out, the request falls back to yield.xyz’s default endpoints for the network rather than erroring out, so a misconfigured or rate-limited custom RPC degrades to the default rather than breaking the project.

Custom RPC URIs are scoped per project and per network: one URI per network per project, and they only affect that project’s requests.

Who can manage it

Adding, editing, or removing a custom RPC URI requires the owner or admin role; members can view the configured list but not change it. See Roles & permissions.

Next steps

Payout wallets

Register the wallets that receive your collected fees.

Geo-blocking

Restrict yield actions by country or region.