BLVCK MINDZDOCS
Try demo ↗GitHub ↗

BLVCK MINDZ × NEAR / Verify the payment

A visible result with a path back to the network.

Start with the receipt from your own test. The example below is a previously verified run, preserved for inspection.

A recorded execution

Open the saved receipt →

Inspect its NEAR testnet transaction ↗

ENAa7vja5ruQ5kR7B9WfhXnYYcFGtupKkapvjMFuxYYu

This example distributed 2.00 test tokens as 0.80 / 0.84 / 0.36. It was executed after the hosting migration on 15 November, with the payment logic and deployed WASMs unchanged.

What the verifier checks

  • The configured rights contract, batch and receipt.
  • The configured test token and successful transfer outcomes.
  • Each recipient, its amount and the full payment total.

Open the evidence report →

Run the checks yourself

From a clone of the public repository, use the prerequisites and installation steps in the README. The following verification command reads network evidence; it does not send a payment.

cd app
npm run verify:live -- ../evidence/live-runs/b19d4dcf-c5fb-4f06-8a6d-52820cd78cd7.json

Prerequisites and complete verification instructions ↗

Source and deployed code

Build comparison report ↗ compares local WASM artifacts with deployed bytecode. That is distinct from independently rebuilding the contracts from a clean environment. The candidate’s full clean Rust build and integration reproduction remain pending.

Application tests and recorded stress checks cover specific cases. Their count is not a security certification or proof of commercial operation.

Documentation maintenance · 16 November 2026 · Source and scope