Authenticated Verifiable Open Web Protocol
A protocol design that aims to make consent, unsubscribe, and rate-limit compliance verifiable.
Unsubscribe links often don't work. No proof consent was given.
$200M+ market
Fake profiles, astroturfing, election interference. Current solutions don't scale.
$1.2B+ market
Companies spend $100M+/year fighting spam and bots. Still losing.
Bots remain a persistent problem
Use dependent types (Idris2) to make message properties verifiable at compile-time.
Cryptographically provable consent chains. Can't fake timestamps or skip verification.
proof : confirmation > initial_request
Unsubscribe links validated before sending to avoid broken links.
proof : response.code = OK ∧ response.time < 200ms
Protocol-level rate limits based on account age. Cannot be bypassed.
proof : messages_today < daily_limit
struct UnsubscribeLink {
url: String,
tested: bool, // Can lie
}
No guarantees. Developers can lie about testing.
record UnsubscribeLink where
url : URL
tested_at : Timestamp
response : HTTPResponse
{auto proof : response.code = OK}
{auto proof : response.time < 200ms}
Designed to be verifiable. The protocol aims to reject invalid links before send.
Test AVOW verification right in your browser (build-time proofs + demo rules):
Verify that confirmation happened AFTER initial request (time-ordering proof)
👆 Click a button above to see verification in action
Note: URL checks use build-time proofs from proven. Consent checks are demo rules.
See AVOW in action with our live Telegram bot:
/start to subscribe/verify to see full verification/unsubscribe to test the demo flowDesign for compliance with CAN-SPAM, GDPR. Verified unsubscribe links.
Reduce fake profiles with verified identity chains.
Combat astroturfing and election interference with verified accounts.
RCS, SMS marketing with verifiable compliance.