Tamper-Evident Work Records for Industrial Equipment

A machine that can prove what it did is worth more than one that can't. Work attestation is the audit trail for autonomous action — a verifiable record of what a machine produced, when, and on whose authority.

The problem: machine work is unprovable

JPMorgan tokenizes deposits. Goldman tokenizes real estate. But the work a machine does — the parts it cut, the hours it ran, the alarms it cleared — lives in a log file that anyone with write access can edit. When an autonomous agent throttles a line at 3am, the question "who authorized that, and what actually happened?" has to have an answer that survives a regulator, an insurer, or a lender. A mutable log is not that answer.

This matters most where money meets machines. Equipment finance without verified work history is underwriting blind. Equipment-as-a-service billing without verifiable usage is a trust exercise. Machine credit scoring needs a track record that can't be doctored.

How FoundryNet solves it

Every billable event — a trigger fire, a normalize result, a settlement candidate — is hashed and appended to a tamper-evident buffer on the edge. On a schedule the buffer is Merkle-rooted and only the root plus per-event SHA-256 hashes are anchored to an immutable public ledger (Solana). Raw telemetry never leaves the host — the chain holds proofs, not data.

Tamper-evident — any change to a record breaks its hash; the anchored root is the witness.
Hash-only — a network trace shows SHA-256 digests, never machine data or part geometry.
Durable — the buffer survives power loss and air-gapped operation; unsettled work anchors on the next online window.
Opt-in — attestation is off by default (MINT_SETTLE=false); a customer turns it on deliberately, so a security review sees zero outbound chain traffic until they do.

Tamper-evident work records aren't crypto. They're audit infrastructure — the same role a notarized logbook played, made verifiable and machine-readable.

Connect an agent in 60 seconds

FoundryNet Forge is a Model Context Protocol (MCP) server — 14 tools over SSE, bearer-key auth. Add it to any MCP client (Claude Desktop, Cursor, an agent framework):

claude mcp add --transport sse foundrynet \
  https://foundrynet-mcp-production.up.railway.app/mcp \
  --header "Authorization: Bearer fnet_YOUR_KEY"

Or as JSON config:

{
  "mcpServers": {
    "foundrynet": {
      "url": "https://foundrynet-mcp-production.up.railway.app/mcp",
      "headers": { "Authorization": "Bearer fnet_YOUR_KEY" }
    }
  }
}

Attested work is the foundation for the next layer: machine credit. A machine with a verifiable history of work done is a financeable asset.

Start attesting work — 50 calls, no card Read the Agent Card Explore the ecosystem ↗

The path to machine credit

Verified work history → usage-based billing → machine credit scoring → equipment finance priced on real output. Each step needs the one before it, and all of them need a record that can't be faked. For the ecosystem of projects building attestation and settlement for physical assets, see the curated guide on PhysicalMCP.

Frequently asked

What is machine work attestation?

Work attestation is a tamper-evident record of what a machine actually did — parts produced, hours run, actions fired — anchored to an immutable public ledger so it can be independently verified and can't be quietly edited after the fact.

Does attestation send my machine data to a blockchain?

No. Only SHA-256 hashes (a Merkle root plus per-event leaf hashes) are anchored. Raw telemetry, part geometry, and process data never leave the host. The chain holds proofs, not data.

Is attestation required to use FoundryNet?

No — it is opt-in and off by default (MINT_SETTLE=false). Normalization and automation work fully without it. You enable attestation deliberately when you need a verifiable record, for example for equipment finance, EaaS billing, or audit.