PACTAby Fractal Neurons
Request a dossier
Creator shares priced on a bonding curve for social trading and chat access (Base)

friend.tech V1: control-plane safety record

1 indexed control-plane surface for friend.tech V1, with its controller and timelock state pinned to a canonical Base block over archive JSON-RPC (not EAS-attested; documentation parameters are linked, not compared). Contract: 0x0bD4…6670

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: Not determinedSigner quorum: Not determinedEmergency / freeze scope: Not determinedDocs-vs-chain parity: Uncompared

Observed Chain pinned; docs not assessed

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
Not determined · No signer quorum in the published records
Emergency / freeze scope
Not determined · No pause / freeze authority in the published records
Docs-vs-chain parity
Uncompared · Uncompared: documentation not assessed (RPC-observed)

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=base&address=0x0bD4887f7D41B35CD75DFF9FfeE2856106f86670"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "base", "address": "0x0bD4887f7D41B35CD75DFF9FfeE2856106f86670"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "base", "address": "0x0bD4887f7D41B35CD75DFF9FfeE2856106f86670"})

Provenance

RPC-pinned record: read over public JSON-RPC at the Base 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 Observed (RPC-observed baseline): the onchain 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.

FRIEND (Points) · Non-Proxy Bytecode & Controller

Status
Observed
Target
FRIEND (Points) 0x0bD4…6670 · Basescan
Pinned block
Base #59,450,023 · Basescan · RPC-pinned, not EAS-attested
Block hash
0xf0732368…24466d
Controller
No single-key owner or admin getter (immutable or role-scoped modules)

Observed onchain. FRIEND (Points) (0x0bD4887f7D41B35CD75DFF9FfeE2856106f86670) verified on Base Mainnet at canonical block #59,450,023 (6,037 bytes runtime code). EIP-1967 implementation and admin storage slots are both zero (non-EIP-1967 contract). No owner(), admin(), authority(), curator() or AccessControl admin was readable on the contract.

Documentation (linked, not compared). friend.tech V1 documentation is linked for reference (https://www.friend.tech/keys). This RPC-pinned record does not compare documentation parameters with the on-chain state.

Reproduce on any archive node
cast call 0x0bD4887f7D41B35CD75DFF9FfeE2856106f86670 \
  "owner()" \
  --block 59450023 --rpc-url "$BASE_RPC_URL"
cast block 59450023 --field hash --rpc-url "$BASE_RPC_URL"
# expect 0xf0732368cb614a82f09f6c0e1c33011269cb9da90e64995249a218a3d724466d

Control-plane badge: RPC-Observed

Pacta Control Plane: RPC-Observed

The slate badge states only what Pacta pinned on-chain; it makes no documentation claim until friend.tech V1 is compared with its documentation and attested on Base.

Markdown
[![Pacta Control Plane](https://pacta.wtf/badges/friend-tech-v1.svg)](https://pacta.wtf/protocols/friend-tech-v1/)
HTML
<a href="https://pacta.wtf/protocols/friend-tech-v1/"><img src="https://pacta.wtf/badges/friend-tech-v1.svg" alt="Pacta Control Plane: RPC-Observed" height="20"></a>

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

For maintainers and issuers

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

A maintainer and an independent verifier re-check friend.tech V1 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 friend.tech V1? 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)