DEV Community

Daniel Ioni
Daniel Ioni

Posted on

From a Synthetic AHP Event to a Real Base Sepolia Anchor

#sepolia #anchor #synthetic #ahp

From a Synthetic AHP Event to a Real Base Sepolia Anchor

Today we completed the first end-to-end blockchain anchoring test for MyZubster’s AHP traceability layer.

The goal is to prove the integrity and timestamp of a circular-economy pilot event without placing personal or health data on-chain.

What we implemented

The MyZubster traceability service now supports:

  • signed append-only events;
  • pseudonymous pilot and lot identifiers;
  • MongoDB persistence;
  • SHA-256 event hashing;
  • Merkle tree generation;
  • Ed25519 signature verification;
  • EVM anchoring through a calldata transaction;
  • Base Sepolia receipt verification.

The first test event was:

Event type: LOT_CREATED
Pilot: MZ-AHP-PILOT-001
Lot: MZ-AHP-LOT-20260909-001
Mass: 100 kg
Enter fullscreen mode Exit fullscreen mode

No names, emails, addresses, medical data or household-level information were included.

The real testnet anchor

The event was persisted in MongoDB and anchored on Base Sepolia.

Network: Base Sepolia
Chain ID: 84532
Status: CONFIRMED
Block: 46577137
Enter fullscreen mode Exit fullscreen mode

Transaction:

https://sepolia.basescan.org/tx/0x6dcf39faac6d1eabbaf0e6857ae329d41a1de74cf8320f8f9f048a2dca7ce649

Merkle root:

5e02cd7fdf95a484942d4cd88666b043b24b5018e73491c48cdd078eafed27d3
Enter fullscreen mode Exit fullscreen mode

The transaction uses a zero-value self-transfer containing the MyZubster anchor payload. The blockchain stores the integrity reference, while operational evidence remains off-chain under controlled access.

What this proves

This test demonstrates that MyZubster can:

  1. create a signed traceability event;
  2. validate the event against the AHP schema;
  3. persist it in MongoDB;
  4. generate a Merkle root;
  5. anchor the root on a public EVM testnet;
  6. verify the resulting transaction receipt.

Blockchain anchoring supports integrity, ordering and timestamp verification. It does not independently prove that a physical measurement is accurate or that recycling actually occurred. Those claims still require operational evidence and independent verification.

Next steps

The next phase will extend the pilot with:

  • supply and custody-transfer events;
  • collection and transport records;
  • treatment and recovered-fraction measurements;
  • QR/NFC lot linkage;
  • Merkle inclusion-proof verification;
  • correction and dispute workflows;
  • public reporting that separates measured, verified, estimated and unknown values.

This is the first real blockchain anchor for the MyZubster AHP traceability workflow. The next objective is to connect the technical ledger to a controlled physical pilot for absorbent products and circular-material recovery.

Top comments (0)