PACTAby Fractal Neurons
Request a dossier
Crypto-native hedging instruments: impermanent-loss and interest-rate derivatives (iGain) (Ethereum)

Hakka Finance: control-plane safety record

1 indexed control-plane surface for Hakka Finance, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xF2B8…500A

What differs

Changed / discrepant

  • Multi-sig: docs name 3 keyholders; the Safe is 2-of-4 with 1 unnamed owner: Hakka multi-sig 0xF2B8f214Dc81b849ed3BDCAEdA6c8c39625c500A (Ethereum Safe, the address the page gives): getThreshold() = 2 of getOwners() = 4; guard slot empty; observed vs 'The keyholders are as follows.' documented
    Show the full onchain evidence

    Hakka multi-sig 0xF2B8f214Dc81b849ed3BDCAEdA6c8c39625c500A (Ethereum Safe, the address the page gives): getThreshold() = 2 of getOwners() = 4; guard slot empty; getModulesPaginated() lists no module. Owners: 0x9033c3677E6C63FC252E9546AD5b5E7d66Fc0926, 0x1D075f1F543bB09Df4530F44ed21CA50303A65B2, 0xF9aCeFD1A4e4360eE3A534Cb3485Bce36F5F05A4, 0x784e010430a923Ce2a3Ff9846C4010694Bb7BEfb, all accounts with no code; the three documented keyholders are owners, and 0x9033c3677E6C63FC252E9546AD5b5E7d66Fc0926 is an owner the page does not name. With a threshold of 2, that key and any one documented keyholder can execute. HAKKA token 0x0E29e5AbbB5FD88e28b2d355774e73BD47dE3bcd owner() = this Safe.

    Show the full documented text

    'The keyholders are as follows.' (hakkafinance.gitbook.io/hakka-wiki/governance/multi-sig.md)

Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: Not determinedSigner quorum: ModerateEmergency / freeze scope: Not determinedDocs-vs-chain parity: Weak

Delta Docs and chain differ

Aligned means the docs are accurate, not that the protocol is low-risk. The rosette rates the controls themselves.
Upgradeability
Not determined · Upgrade path not in the published records
Timelock floor
Not determined · No enforced admin delay in the published records
Signer quorum
Moderate · Lowest controlling quorum: 2-of-4Evidence: controller fact: Safe getThreshold()
Emergency / freeze scope
Not determined · No pause / freeze authority in the published records
Docs-vs-chain parity
Weak · Documentation differs from the chain (parameter delta)

Each slice is derived only from the pinned records on this page and their controller facts (/api/v1/scorecards.json). A hollow slice is not determined by the published evidence (never a guess); docs-vs-chain parity is uncompared for RPC-observed protocols. How to read it.

Check it live (free)

The pre-flight API re-reads the controller, proxy and capabilities of one contract at the latest block. No key, no wallet. The score rates that single contract, not the whole protocol.

cURL
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0xF2B8f214Dc81b849ed3BDCAEdA6c8c39625c500A"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0xF2B8f214Dc81b849ed3BDCAEdA6c8c39625c500A"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0xF2B8f214Dc81b849ed3BDCAEdA6c8c39625c500A"})

Multi-sig: docs name 3 keyholders; the Safe is 2-of-4 with 1 unnamed owner

Status
Delta
Target
Hakka Finance multi-sig (Safe) 0xF2B8…500A · Etherscan
Pinned block
Ethereum #26,453,551 · Etherscan · sprint 34
Block hash
0x51e9967f…767129
Attestation
Base EAS attestation 0xc281…d992

Observed onchain. Hakka multi-sig 0xF2B8f214Dc81b849ed3BDCAEdA6c8c39625c500A (Ethereum Safe, the address the page gives): getThreshold() = 2 of getOwners() = 4; guard slot empty; getModulesPaginated() lists no module. Owners: 0x9033c3677E6C63FC252E9546AD5b5E7d66Fc0926, 0x1D075f1F543bB09Df4530F44ed21CA50303A65B2, 0xF9aCeFD1A4e4360eE3A534Cb3485Bce36F5F05A4, 0x784e010430a923Ce2a3Ff9846C4010694Bb7BEfb, all accounts with no code; the three documented keyholders are owners, and 0x9033c3677E6C63FC252E9546AD5b5E7d66Fc0926 is an owner the page does not name. With a threshold of 2, that key and any one documented keyholder can execute. HAKKA token 0x0E29e5AbbB5FD88e28b2d355774e73BD47dE3bcd owner() = this Safe.

Documented. 'The keyholders are as follows.' (hakkafinance.gitbook.io/hakka-wiki/governance/multi-sig.md)

Reproduce on any archive node
cast call 0xF2B8f214Dc81b849ed3BDCAEdA6c8c39625c500A \
  "getOwners()" \
  --block 26453551 --rpc-url "$ETH_RPC_URL"
cast block 26453551 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0x51e9967ffd6a84012d0dad44204d523b8ac43928e69de2801d2e72dbf8767129

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

This badge is amber because at least one Base-EAS-attested surface of Hakka Finance differs from what the protocol documents. It turns to the neutral Aligned · Base EAS shield only when the on-chain state or the documentation changes and the two match at a new finalized block, whoever requests the re-check.

Submit updated docs

Embed this badge (it updates when the status changes):

Markdown
[![Pacta Control Plane](https://pacta.wtf/badges/hakka-finance.svg)](https://pacta.wtf/protocols/hakka-finance/)
HTML
<a href="https://pacta.wtf/protocols/hakka-finance/"><img src="https://pacta.wtf/badges/hakka-finance.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>

Badge: https://pacta.wtf/badges/hakka-finance.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/hakka-finance.svg.

For maintainers and issuers

Fixed this gap? 24h mainnet re-verification ($99 intro)

A maintainer and an independent verifier re-check Hakka Finance on mainnet within 24h and attest the result on Base. The fee pays for the 24-hour mainnet re-verification work, never the grade: your attestation reads Aligned when on-chain controls match the published documentation, and Delta when they do not.

Maintaining Hakka Finance? Verify and reconcile the record

Two paths, both public. A free doc-update notice asks the maintainers to correct the documentation or the onchain parameter; anyone can send it. A Full Control-Plane Dossier ($2,500–$5,000 USDC, 24h SLA) re-reads the multisig and timelock control planes on archive RPCs and prepares an upstream docs reconciliation PR. Either way the classification changes only when the onchain state or the documentation aligns at a new finalized block.

Need procurement paperwork? Request a commercial invoice (PDF).

Read-only onchain analysis. Not investment advice. Exploit-sensitive vulnerabilities are never published here; they go through Immunefi or Cantina bounty programmes.Request a dossier (24h SLA)