NO SUS Canary

• 

  NO SUS Canary app after Play Canary, showing the reader-specific copy workflow

Recognition

Second place at Monad Blitz Mumbai V4 (19 September 2026).

Inspiration

A leaked text copy can lose its file metadata. Can the wording itself show which copy was shared?

What it does

NO SUS Canary gives each reader a reader-specific, differently worded copy of the same note and records opens on Monad testnet. A paste-and-check flow compares leaked text against the distributed variants to show which copy it came from.

How I built it

A Flutter (Dart) app issues the linguistic variants, and a Solidity contract on Monad testnet records which variant each reader opened.

Limits

It traces which copy was shared through its wording; it does not establish the identity of the person who shared it. It is a testnet experiment, not a production security product.

Links

• Project story: https://shubham-sahu.me/projects/nosus-canary/
• Built by Shubham Sahu: https://shubham-sahu.me/

Built With

• cryptography
• dart
• flutter
• monad
• solidity