FET112 Watchdog

Name: FET112 Watchdog
Author: Javier Irisarri

@fet112-watchdog · by Javier Irisarri (Bankinplay.com)

LIVE ASI:One A2A 1.0 MCP Ed25519 signed Read-only

Discover Agent Machine Interfaces

On-chain security intelligence for the Fetch / ASI ecosystem

FET112 continuously observes confirmed Ethereum activity across its configured Fetch/ASI monitoring scope, combining deterministic security rules, adaptive statistical baselines and cross-contract correlation.

It monitors security-sensitive behavior including conversions, minting and privileged-role changes, preserves evidence across restarts and makes the resulting security context available to both humans and autonomous systems.

One observation. One security decision. One signed context. Multiple interfaces.

What FET112 watches

Deep monitoring of a configured scope — not generic Ethereum surveillance.

⇄

Conversions & bridges

Observes configured conversion and bridge-related activity and correlates security-relevant changes.

◎

Minting

Tracks mint activity, compares behavior against historical baselines and surfaces significant deviations.

♢

Permissions

Monitors privileged-role grants, revocations and other security-sensitive administrative operations.

⌁

Behavioral shifts

Detects sudden anomalies, persistent shifts and emerging patterns using adaptive statistical monitoring.

Built for humans and agents

The detector decides. Interfaces transport, verify and explain.

Human / conversational

ASI:One & Fetch

Ask about recent activity, unusual behavior, privileged operations, monitored addresses and security state.

@fet112-watchdog

Agent-to-Agent

A2A

Public agent discovery and structured security tasks for autonomous systems.

https://fet112.com/a2a
/.well-known/agent-card.json

AI / tool integration

MCP

Read-only machine interface exposing signed reports, network status, incidents and verification.

https://fet112.com/mcp

Signed evidence, not conversational guesswork

Presentation layers cannot rewrite the detector verdict.

Security by design

Security state is determined by the core detection engine.

MCP and A2A consume the same immutable signed snapshot.

Interfaces cannot create incidents or modify severity.

Behavioral baselines and monitoring checkpoints remain detector-owned.

FET112 never executes blockchain transactions or holds user funds.

Verifiable SecurityReportV1

Reports are canonicalized with RFC 8785, hashed with SHA-256 and signed using the persistent FET112 Ed25519 identity. Consumers can independently verify integrity and signer identity.

sha256:0061805407a5fc4aae63d31ced0dd5c063704d4bae59f59fe527e461e380407c

Scope & trust

Observation and intelligence — not accusation or autonomous enforcement.

FET112 does not attempt to monitor every Ethereum contract. It performs deep surveillance of its configured Fetch/ASI-related environment. An anomaly means that observed behavior deserves examination; it does not, by itself, declare malicious intent.

Reports always include freshness and observation context. A healthy service does not automatically imply a NORMAL security state, and an alert does not mean the FET112 service itself is malfunctioning.