PACTAby Fractal Neurons
Pacta / Protocols / Across Protocol (HubPool)
Intent-Based Cross-Chain Settlement

Across Protocol (HubPool): control-plane safety record

1 indexed control-plane surface for Across Protocol (HubPool), with its controller and timelock state pinned to a canonical Ethereum block over archive JSON-RPC (not EAS-attested; documentation parameters are linked, not compared). Contract: 0xc186fA914353c44b2E33eBE05f21846F1048bEda.

Check it live (free)

The pre-flight API re-reads the controller, proxy and capabilities of a contract at the latest block. No key, no wallet.

Live pre-flight check
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0xc186fA914353c44b2E33eBE05f21846F1048bEda"

MCP: https://pacta-x402.pacta.workers.dev/mcp · tool pacta_check_preflight.

Provenance

RPC-pinned record: read over public JSON-RPC at the Ethereum block shown below and independently re-read at the same block by a second Pacta seat. It is not EAS-attested: no sprint number, no summary document and no Base EAS UID. Status RPC-observed baseline: the on-chain control plane is pinned at block height; whether it matches the protocol's documented parameters is not assessed here (the documentation is linked for reference). Machine-readable: /api/v1/rpc-pinned.json. The Base-EAS-attested Sprint records are in /api/v1/index.json.

AcrossHubPool · 3-of-5 Safe Control Plane

Status
RPC-observed baseline
Target
AcrossHubPool 0xc186…bEda
Pinned block
Ethereum #26,414,499 · RPC-pinned, not EAS-attested
Block hash
0xb83fee0a…9c0978
Controller
3-of-5 Safe 0xB524…3715

Observed on-chain. AcrossHubPool (0xc186fA914353c44b2E33eBE05f21846F1048bEda) verified on Ethereum Mainnet at canonical block #26,414,499 (19,572 bytes runtime code). EIP-1967 implementation and admin storage slots are both zero (non-EIP-1967 contract). Direct owner() returns 0xB524735356985D2f267FA010D681f061DfF03715, verified via getThreshold() and getOwners() as a 3-of-5 Safe multisig.

Documentation (linked, not compared). Across Protocol (HubPool) documentation is linked for reference (https://docs.across.to/reference/contract-addresses/mainnet-chain-id-1; governance: https://forum.across.to/). This RPC-pinned record does not compare documentation parameters with the on-chain state.

Reproduce on any archive node
cast call 0xc186fA914353c44b2E33eBE05f21846F1048bEda \
  "owner()" \
  --block 26414499 --rpc-url "$ETH_RPC_URL"
cast call 0xB524735356985D2f267FA010D681f061DfF03715 "getThreshold()(uint256)" --block 26414499 --rpc-url "$ETH_RPC_URL"
cast call 0xB524735356985D2f267FA010D681f061DfF03715 "getOwners()(address[])" --block 26414499 --rpc-url "$ETH_RPC_URL"
cast block 26414499 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0xb83fee0a1d10d5fb8510d87ee9e33b180acac3208a7d00162a6a6f97789c0978
For issuers

Issuing Across Protocol (HubPool)? Reconcile & Anchor 24h Institutional Clearance

Reconcile documentation drift, verify multisig and timelock control planes across archive RPCs, prepare an upstream docs reconciliation PR, and anchor a Base EAS Aligned Attestation + Curator Diligence Dossier within 24 hours.

Read-only on-chain analysis. Not investment advice. Exploit-sensitive vulnerabilities are never published here; they go through Immunefi or Cantina bounty programmes.Clear findings in 24h · $5,000 USDC →