Skip to main content
The versioned engineering evidence matrix links implementations, tests and public proof for all five entered categories. The table below summarizes what a reviewer can actually inspect.

Device verification procedure

  1. Record browser, OS and passkey provider on two devices. Start from a campaign/referral URL, cancel sign-in once, then complete it with the original passkey and confirm the return context.
  2. Perform a testnet link or purchase action, record its transaction and verify its indexed result. Do not use real funds for this commerce test.
  3. Write non-sensitive test text in a campaign notebook, Encrypt & sync, download an encrypted backup, reload and reopen with the same passkey.
  4. On the second device, use that same provider-synced passkey and verify PRF support by actually decrypting the synced note. Record unsupported combinations as failures or limitations, not successes.
  5. Test conflicting edits on disposable notes, restoring a backup and retrying after an interrupted sync. Keep the original working copy until restoration is verified.

Merchant usability test

Ask a consenting merchant to compare two distributors, inspect a receipt, send an invitation, then have the recipient accept and create a link. Record where they hesitate, which states are unclear and whether they can find the final reward allocation. Collect observed feedback; do not substitute scripted tests for user adoption. All proof must retain its network and data origin: demo fixtures, scripted testnet assets, external cached history and real mainnet funds are different things. Contract source verification and passing tests are not an independent security audit.