PLI
@ZecPli
network requests since load: 0
CA0x28627e1c96ccb7cd77c66832660976730d644496

Community token. Pli itself is free — you never need the token to seal or open a request.

Ask for ZEC.
Leak nothing.

A shielded transaction hides the payment. The request you text, email or DM still shows your address, the amount and the reason. Pli seals all three in your browser — only the person with your passphrase can read what to pay.

Seal a request See what leaks
← what you wrotewhat everyone else sees →

The bench

An example is already sealed so you can see the output. Replace the fields with your own — nothing you type leaves this page.

Send it through a different channel than the pli — in person, Signal, a call.

Z
Sealed—

        

          
          
          
        

        

          
Visible from outside
—

          
Cipher
AES-256-GCM

          
Key derivation
PBKDF2-SHA-256 · 600,000 rounds

          
Inside
ZIP-321 URI + expiry

          
Link
pli lives after the # — browsers never send that part

        

      

    


    
  


  

    
Who reads what

    
Your messenger, your mail provider, a screenshot, a backup — every hop that carries a payment request can read it. Flip the switch.

    

      

        
        
      

      

        

          What the carrier stores
          

          
        

        
    
          
  • Your addressu1l9f0exampleq7m3x8d2k5vns4…EXPOSED
    • 
          
  • Amount0.42 ZECEXPOSED
    • 
          
  • MemoSite mockup — 50% depositEXPOSED
    • 
          
  • Payload sizeexact, to the byteEXPOSED
    • 
          
  • Lifetimevalid foreverFOREVER
    • 
        

      

    

  


  

    
Three moves

    
From form to shielded transaction, with nobody in the middle.

    
    
      
  1. You seal
    The request becomes a ZIP-321 zcash: URI, gets padded with random noise to a multiple of 512 bytes, then encrypted with AES-GCM.
    2. 
      
  2. You send two things
    The pli over any channel — email, Telegram, whatever. The passphrase over another. Neither is enough alone.
    3. 
      
  3. They open and pay
    Their browser decrypts, checks expiry, draws the QR. Their wallet sends a shielded transaction; the memo travels encrypted on-chain.
    4. 
    

  


  

    
What Pli won't do

    
A privacy tool that doesn't tell you where it stops isn't one.