Deployment Configuration
Get the current Sepolia Pool, contract addresses and network parameters.
Get configuration#
GET /api/queue/config takes no parameters. It returns the contracts and routes used by the public Sepolia service. Fetch it when your application starts instead of copying addresses into source code.
Live read requests run through the docs server. Copied examples call api.fuyu.xyz directly. No API key required.
Response fields#
| Field | Meaning |
|---|---|
| chainId | 11155111 for Sepolia |
| poolAddress / domain | Pool address and the domain used by its proofs |
| deploymentBlock / deploymentBlockHash | Block where this Pool was deployed |
| poolRuntimeCodeHash | Hash of the deployed Pool bytecode |
| accountRegistry / receiveDirectory | Account and receiving contracts, including addresses and ABIs |
| assets | Asset addresses, decimals and token definitions |
| routes | Action routes offered by this deployment |
| relayFees | Current relay fee schedule |
| queue | Endpoint paths and proof-artifact locations |
Read wallet connection parameters#
GET /api/queue/networks returns supportedChains. The public service supports Sepolia only. Its entry includes chainId, chainIdHex, nativeCurrency, explorerUrl and walletRpcUrl.
Use walletRpcUrl when connecting an Ethereum wallet. The separate rpcUrl is used for chain reads. Check that the wallet is on Sepolia before asking the user to sign a transaction.
Live read requests run through the docs server. Copied examples call api.fuyu.xyz directly. No API key required.
Keep a payment on one deployment#
Store the chain ID and Pool address alongside an operation's status identifier. If configuration changes while a payment is pending, check that original operation before preparing another one.
Contract addresses, proof files and action routes belong to the same deployment. Do not combine values from an older response with the current configuration.