DO NOT BELIEVE ME. RUN THE TEST.

Public Original

Asset ID

profile:bjklock:624e3ecf-2e6b-46c0-8e94-a5c20ab82fb1

Native asset ID

624e3ecf-2e6b-46c0-8e94-a5c20ab82fb1

Owner

@bjklock

Original Kai pulse

13310952

Sealed at

2026-07-25T23:03:16.450223+00:00

Observed USD value

12170.6

Original digest

49f3653775919a99c91bba65b5d851abc19e6b56c3d9d39f781fac94d39c05c3

DO NOT BELIEVE ME. RUN THE TEST.

DO NOT BELIEVE ME. RUN THE TEST.

Create it offline.

Seal it offline.

Verify the sealed file offline.

Test the screenshot offline.

This is not an argument.

It is a test.

Follow the steps exactly.

1. INSTALL THE RECORD SEAL

While connected to the internet, open:

https://receiz.com/offline-record-seal.html

Install the Record Seal as a PWA on your device.

The internet is required only once to load and install the app.

After installation, close it.

2. TURN THE INTERNET OFF

Turn on Airplane Mode.

Turn off Wi-Fi.

Turn off cellular data.

Confirm that the device has no internet connection.

Now open the installed Record Seal app.

Do not reconnect until the entire test is complete.

3. CREATE AND SEAL A RECORD

Choose Record.

Record any moment you want.

Seal the record.

Save or export the sealed file to your device.

Then take a screenshot of the recorded moment or sealed result.

You now have two separate files:

The sealed record.

A screenshot of the sealed record.

Both were created while your device was offline.

4. VERIFY THE SEALED FILE

Stay inside the same Record Seal app.

Choose Verify.

Upload the sealed file you just created.

Verify it.

The sealed file passes verification.

Remain offline.

5. TEST THE SCREENSHOT

Stay inside Verify.

Upload the screenshot of the recorded moment or sealed result.

Attempt to verify it.

The screenshot fails verification.

Remain offline.

THAT IS THE TEST

The same installed page has now:

Recorded the moment.

Sealed the record.

Exported the sealed file.

Verified the authentic sealed file.

Rejected the screenshot.

All while the device was disconnected from the internet.

You created the record offline.

You sealed it offline.

You saved the proof object offline.

You took a screenshot of the sealed record.

The sealed proof object passed verification.

The screenshot failed verification.

The verifier distinguished the authentic proof object from a picture of the proof object.

The entire test happened inside one installed page without contacting the internet after installation.

Do not believe me.

Run it.

The sealed file passes.

The screenshot fails.

No trust required.

OPTIONAL: REPEAT THE TEST WITH A STANDALONE VERIFIER

For an additional independent test, use:

https://receiz.com/offline-verifier.html

Before disconnecting from the internet, save the standalone Offline Verifier HTML file to your device.

The verifier can also be opened through any PDF viewer.

While still offline, open the verifier file locally.

Upload the sealed file.

Verify it.

The sealed file passes.

Then upload the screenshot.

Attempt to verify it.

The screenshot fails.

The standalone verifier does not need to contact Receiz.

It does not need an API.

It does not need a database.

It does not need a blockchain query.

It does not need a server.

It does not need the internet.

The verifier is the file.

The proof is in the object.

The screenshot is not the proof object.

A picture of the proof is not the proof.

Nothing contacted the internet.

Nothing asked a server.

Nothing asked a blockchain.

Nothing asked you to trust me.

You ran the test yourself.



NOW TRY TO BREAK IT

If you believe this is fake, stop saying it.

Demonstrate it.

Produce one of the following:





A file that successfully passes the Receiz Offline Verifier that was never sealed by Receiz.



A forged Receiz proof object that the verifier accepts as authentic.



A screenshot, image, PDF, edited file, or fabricated object that the verifier incorrectly validates.

Run the test.

Record it.

Show the entire process.

Publish every step.

If you can create a fake proof object that passes the verifier, then you have found a failure.

Produce it.

If you cannot, then stop pretending your opinion outweighs a reproducible experiment.

The verifier either accepts the object or it does not.

There is no debate.

There is no appeal to authority.

There is no “I think.”

There is only the result.

Do not tell people it can be faked.

Fake it.

Do not tell people the verifier is meaningless.

Make it verify something it shouldn’t.

Do not speculate.

Demonstrate.

If you cannot produce a single object that passes verification without having been legitimately sealed, then your claim remains unsupported.

The challenge is public.

The verifier is public.

The test is reproducible.

The burden is no longer on me.

It is on anyone claiming the verifier accepts objects that were never sealed.

Produce the proof object.

Make it pass.

If you can’t—

Shut the fuck up and run the test.

Carried text evidence

Text SHA-256

f0fe25d6ecf21ff0d0663b43fddc63823c7b2b4f42c3fed71ffc09dd8e06f6d0

Public proof manifest

Coordinate

0030BB9A/13310952

Pulse

13310952

Verify Path

/v/20260725_1903/0030BB9A/13310952?a=97fa5dc6&ms=1785020596225

Circuit

Groth16

Groth16

BB28E4B6645BED95

Poseidon

190a4ef4b6a9947b2ff8e1f13b27084659f1f2991003e842e165ce03b566dfd6

Claim SHA-256

A3694E027F47256A85215873476E232BB576CDDDFBD2DEAE3A2B28C6601975A9

Media SHA-256

7B82E2475BF0A450C019796497ED7EE940450517D312D30163BE95CE5024911F

PBI Signature

FAD847D5625F1B4FB6223E12F8C4BB04BA77145CCBC115C741E00596D9963331

Offline Verifier

/offline-verifier.html

Verification Key

/zk/verification_key.json

Carried public pricing

{
  "quoteUsdPerPhi": 328.626957138,
  "priceUsd": 12170.6,
  "pricePhi": 37.034707,
  "intrinsicPhi": 37.034707,
  "changePct": 3.35,
  "volumeUsd": 41795.92,
  "liquidityUsd": 18957.9,
  "holders": 5,
  "premiumX": 1.034,
  "momentX": 1.129
}

Carried valuation inputs

{
  "kind": "sigil",
  "claimPulse": 13310952,
  "beat": 0,
  "stepIndex": 8,
  "creatorVerified": true,
  "frequencyHz": 2831.4,
  "chakraDay": "Crown",
  "kaiSignature": "bjklock",
  "userPhiKey": "eecb99a0-9c6a-4e89-813b-f76331ea9c41:624e3ecf-2e6b-46c0-8e94-a5c20ab82fb1"
}

Carried material details

{
  "kind": "image",
  "name": "23D90330-5813-4095-8FAB-F7BF1362CA8B.png",
  "mime": "image/png",
  "size": 1753259,
  "sha256Hex": "7b82e2475bf0a450c019796497ed7ee940450517d312d30163be95ce5024911f",
  "originalDownloadMime": "image/png",
  "originalDownloadName": "23D90330-5813-4095-8FAB-F7BF1362CA8B.receized.png",
  "originalDownloadSize": 1755614,
  "originalDownloadSha256Hex": "49f3653775919a99c91bba65b5d851abc19e6b56c3d9d39f781fac94d39c05c3",
  "allowOriginalDownload": true,
  "derivativeDownloadMime": "image/png",
  "derivativeDownloadName": "receiz_20260725_1903_0030BB9A_derivative.png",
  "allowDerivativeDownload": false,
  "allowMomentRecordDownload": false,
  "receiptTzMinutesEast": -240,
  "receiptMs": "1785020596225"
}

Public materials and source

• Original public source
• Verification reference
• Public artwork
• Public reading source
• Original download endpoint (existing access rules apply)