Deployment on Arc
RUFF is live on Arc mainnet, chain ID 5042 (0x13b2). Use the hub proxy for requests, reads, and verification.
Contracts
Section titled “Contracts”| Contract | Address |
|---|---|
| Hub proxy | 0x398F839B85DA2945D26EBBD1B3a4784A2F1389AB |
Implementation, version 1.0.0 |
0xABC1A507Ae9117A5065A01Fd1fD86f6f5019A24D |
| ProxyAdmin | 0x3D83B1C976C8A27D5673cED8569f77216ABa082d |
| TimelockController, 600-second delay | 0xbEd892A7015eF084094af82de425e44d3e7Ef4A3 |
| Hub owner, 2-of-3 Safe | 0x5B1Ef0E6b331D82E59D421ddC24B2a2759ABD51A |
| ExampleConsumer | 0x4A57d8B3648Dbe7C6a6Ce16Ca58E9f16E8dCDdbD |
The Safe owns the hub and is the timelock’s sole proposer, executor, and canceller. The timelock owns ProxyAdmin. The trust model explains the scope of those powers.
The hub proxy, implementation, ProxyAdmin, timelock, and example consumer have verified source on Arc’s explorer and Sourcify. Source verification has Sourcify status match.
Hub proxy source · Implementation source
Integration coordinates
Section titled “Integration coordinates”| Setting | Value |
|---|---|
| Network | Arc mainnet |
| Chain ID | 5042 |
| Native fee asset | USDC, 18 EVM decimals |
| History start block | 23355234 |
| Proxy creation block | 23355248 |
| Initial lane | 1, with 1,000,000 links |
| Lane 1 publication block | 23356677 |
| SDK and CLI | ruff-hub 0.2.0 |
| Result explorer | explorer.jerdog.xyz |
| Explorer API | https://explorer.jerdog.xyz/api/v1 |
Use 23355234 as fromBlock for strict historical verification. Remaining links, fees, and request capacity are live configuration; read the current values before submitting transactions.
Public RPC
Section titled “Public RPC”These endpoints support public reads and browser CORS:
https://rpc.blockdaemon.mainnet.arc.iohttps://rpc.drpc.mainnet.arc.ioCheck that the selected endpoint returns chain ID 0x13b2. The quickstart uses the Blockdaemon endpoint. Applications can configure another Arc mainnet provider with the required history access.
Versioning an integration
Section titled “Versioning an integration”Pin the SDK and Solidity interfaces used by the application. Record the proxy, chain, implementation version, and history start block together. Review upgrades and configuration changes against callback, fee, and timeout handling.