Inbox

Inbox · notify chain

Reading Nobody is signed in
Notify chain reading
How a notification is written
What this tab can and cannot do

Reading and pings work here. Every record addressed to the open key is re-hashed, and its Ed25519 signature is checked with WebCrypto before it is drawn. Marking read and sending a ping are signed with your FXN ID after you review the exact bytes.

Sealed notifications stay sealed here. Opening one needs X25519 with XSalsa20-Poly1305 (NaCl box). WebCrypto has no XSalsa20, this stack runs no WebAssembly, and pure-JS crypto is not used on a real path. Open them in a client that holds your key. Today that is the command-line reader, for a key it made with flux-notify keygen:


            
Writing a sealed body works the same way: flux-notify send --key <file> --to <key> --topic <text> --title <title>.

            
The node returns the whole chain to every reader. Recipient keys and topics are public, and so is each record's time. Only a sealed body is private.

          

        

      

    

    

  


  
    

      

        
Send a ping

        
      

      
A ping carries no body. Recipient, topic and reference are public on the chain.

      

      

        
        
      

      

        
        
        
      

      

        
        
      

      
A sealed body is written in a client that holds your key (flux-notify send … --title). See “What this tab can and cannot do”.

      

        
        
      

    

  


  
    

      

        

          
Sign in
Sign in to Inbox

          
        

        
Checking…

        
        
or open your FXN ID file

        

        
Your file opens in this browser only. Nothing is uploaded, and reloading the page signs you out.