Files

defiQUG dae04d51f7 Initial commit: Fireblocks Web3 integration for Chain 138

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-02-21 15:21:16 -08:00

4.2 KiB

Raw Permalink Blame History

Fireblocks Web3 Integration — Chain 138

Last Updated: 2026-02-21
Status: Active ✅ (DNS + SSL + NPMplus complete)
RPC Node: VMID 2301 (192.168.11.232) — dedicated for Fireblocks

Overview

One RPC node is dedicated for Fireblocks Web3 integrations: VMID 2301 (besu-rpc-private-1, IP 192.168.11.232). Use it for Fireblocks Console custom network, API, and SDK so Fireblocks traffic is isolated from public and other tenant RPCs.

Canonical URLs (parent repo: proxmox docs/04-configuration/RPC_ENDPOINTS_MASTER.md):

Use	URL
HTTP RPC (public)	`https://rpc-fireblocks.d-bis.org`
WebSocket RPC (public)	`wss://ws.rpc-fireblocks.d-bis.org`
HTTP RPC (LAN)	`http://192.168.11.232:8545`
WebSocket RPC (LAN)	`ws://192.168.11.232:8546`

Env vars (see .env.example):

RPC_URL_138_FIREBLOCKS = http://192.168.11.232:8545
WS_URL_138_FIREBLOCKS = ws://192.168.11.232:8546

1. Fireblocks Console — Add Chain 138 (Custom Network)

In Fireblocks Console go to Settings → Network Connections → Web3 (or API → custom networks).
Add custom network (or “Add chain” / “Custom RPC” depending on UI).
Use:
- Network name: e.g. Chain 138 or D-BIS 138
- RPC URL: https://rpc-fireblocks.d-bis.org
- Chain ID: 138
- WebSocket URL (optional): wss://ws.rpc-fireblocks.d-bis.org
Save. Fireblocks will use this RPC for Chain 138 for API and (where supported) Web3 provider.

2. Fireblocks Web3 Provider (SDK) — Custom RPC

Use the dedicated RPC URL when instantiating the Fireblocks Web3 provider so all Chain 138 traffic goes to the Fireblocks-dedicated node.

Example (Node.js / ethers):

import { FireblocksWeb3Provider } from "@fireblocks/fireblocks-web3-provider";

const eip1193Provider = new FireblocksWeb3Provider({
  privateKey: process.env.FIREBLOCKS_API_PRIVATE_KEY_PATH,
  apiKey: process.env.FIREBLOCKS_API_KEY,
  vaultAccountIds: process.env.FIREBLOCKS_VAULT_ACCOUNT_IDS,
  rpcUrl: process.env.RPC_URL_138_FIREBLOCKS || "https://rpc-fireblocks.d-bis.org",
});
// Chain ID is inferred from RPC (138). Use with ethers.js / web3.js.

Environment variable (recommended): see .env.example.

3. Fireblocks REST API — Custom Chain

For Create Transaction and other REST calls that require a chain/network, use Chain ID 138 and ensure the Fireblocks backend is configured to use the custom RPC for 138 (via Console custom network above). No extra code change is needed once the custom network is set in the Console.

4. Hosting (Operator)

The Fireblocks-dedicated RPC is exposed via NPMplus (VMID 10233) with WebSocket support. DNS and SSL are managed in the proxmox repo.

NPMplus Proxy Host	Forward To	WebSocket
`rpc-fireblocks.d-bis.org`	`http://192.168.11.232:8545`	Yes
`ws.rpc-fireblocks.d-bis.org`	`http://192.168.11.232:8546`	Yes

Operator steps (run from proxmox repo): NPMplus proxy update, SSL request (CERT_DOMAINS_FILTER=rpc-fireblocks), Cloudflare A records. See parent docs/04-configuration/FIREBLOCKS_WEB3_INTEGRATION.md for full operator steps.

5. Verify RPC and Chain ID

curl -s -X POST https://rpc-fireblocks.d-bis.org \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
# Expected: {"jsonrpc":"2.0","id":1,"result":"0x8a"}

6. Optional: IP Allowlisting

If you use Fireblocks Network Link / Provider Connectivity and need to allowlist Fireblocks egress IPs, restrict access to the Fireblocks-dedicated node (2301) only. See Fireblocks Network Link Integration.

Parent (proxmox): docs/04-configuration/RPC_ENDPOINTS_MASTER.md, docs/05-network/RPC_NODE_TYPES_ARCHITECTURE.md
Fireblocks Web3 Provider — npm
Fireblocks Create Web3 Connection — API

4.2 KiB Raw Permalink Blame History