ZcashENCRYPTION PATH01 / LOCAL
VIEW: ENCRYPTED
VISUALIZATION / ANIMATED CIPHER SCHEMATICNO ONCHAIN ACTIVITY
/ PRIVATE CHANNEL
Your message. Your key.
ACCESS CONTROL02 / YOU
PUBLIC INPUT: NONE
Keep the content
between people.
Write a message. Encrypt it on your device.
Keep the key separate from the ciphertext.
zkript@local:~LOCAL SHELL
SESSION 01 ●UTF-8
WebCrypto module loaded.
Notes remain in this page’s memory.
Type /help for available commands.
UP 00:00:00HISTORY 0↑↓ HISTORY Tab COMPLETE
PAIR CONTEXT04 / PLANNED
- Pair provider
- NEAR Omni Bridge
- Our token
- Not launched
- Pair status
- Planned
Planned launch venue
pump.fun ↗
pump.fun ↗A7bdiYdS5GjqGFtxf17ppRHtDKPkkRqbKtR27dxvQXaSDATA BOUNDARY05 / LOCAL
MESSAGE↓YOUR BROWSER↓
CIPHERTEXTKEY
- Server uploadNONE
- Browser storageNONE
- Wallet accessNONE
You copy or download the pieces yourself. Anyone holding both can read the message.
WHY ZEC?06 / CONTEXT
PRIVACY AS A CHOICE
Zcash makes selective disclosure part of its native protocol. That idea is the starting point for this community.
Our message tool uses browser encryption. A ZEC pair does not turn it into a Zcash shielded transaction.
READ THE ZCASH PROTOCOL ↗COMMUNITY CONCEPTNO AFFILIATION
/ ENCRYPTION WORKSPACE
Plaintext → ciphertext.
Your message is encrypted on this device.
The packet and its key are separate.
INCOMING / YOUR NOTE01
OUTGOING / TWO SEPARATE PIECES
ENCRYPTION COMPLETE.
Anyone with both pieces can read the note. Keep a copy of the key before clearing or leaving this page.
/ DECRYPTION WORKSPACE
Only the matching key.
A sealed packet. Its matching key.
Only then does the note open.
OPEN / A SEALED NOTE02
OPENED / ON THIS DEVICE
DECRYPTION COMPLETE.
/ IMPLEMENTATION RECORD
Check the working parts.
REPRODUCIBLE FUNCTION CHECK01 / LOCAL
The test creates a sample message and fresh keys on this device. Your own message workspace is left untouched.
- 01WebCrypto runtimeSecure context and AES-GCM availabilityNOT RUN
- 02Encrypt → decryptApp round-trip and independent WebCrypto decryptionNOT RUN
- 03Wrong-key rejectionA different key must not open the packetNOT RUN
- 04Altered-packet rejectionChanged ciphertext must fail authenticationNOT RUN
Ready. No notes are uploaded and no wallet is needed.
This is a functional self-check of the listed operations. It is not an independent security audit or a token assessment.
WHAT EXISTS TODAY02 / SCOPE
- Message encryptionBrowser-local AES-256-GCM
- IMPLEMENTED
- Native Zcash shieldingThis tool does not send shielded Zcash transactions
- NOT IMPLEMENTED
- Community tokenContract address is pending launch
- NOT LAUNCHED
- ZEC trading pairSolana asset is the planned pair target
- NOT CREATED
INSPECT THE IMPLEMENTATIONEncryption module JS ↗Self-check implementation JS ↗Format, limits and data flow TXT ↗File checksums JSON ↗
After launch, the token record can link to its exact contract and actual pool. This preview does not present the pair-asset mint as our token contract.