Redacted Receipts

Every Silo transaction generates a redacted receipt for both the sender and the receiver. These receipts confirm that a payment occurred and provide each party with enough information to verify the transaction, without exposing the other party’s wallet address, transaction hash, or routing details.

​

What the Sender Sees

The sender’s receipt shows: the amount they sent, the receiver’s username, their own outbound transaction hash (proof that funds left their wallet), and the timestamp of the transaction. The sender does not see the receiver’s wallet address, the receiver’s withdrawal transaction hash, or any details about how the payment was routed or delivered on the receiver’s side.

​

What the Receiver Sees

The receiver’s receipt shows: the amount they received, the sender’s username, their own inbound transaction hash (proof that funds arrived at their wallet), and the timestamp of the transaction. The receiver does not see the sender’s wallet address, the sender’s deposit transaction hash, or any details about which asset or chain the sender paid from.

​

What Neither Party Sees

Neither the sender nor the receiver sees the other’s wallet address or the other’s on-chain transaction hash. The only shared information is the username, the amount, and the timestamp. This means a receipt can be used to confirm that a payment took place, for record-keeping, expense tracking, or dispute purposes, without doxxing either party’s on-chain identity.

​

Why This Matters

Most crypto transactions today offer no receipt at all. A user can look up a transaction hash on a block explorer, but that reveals the full on-chain details to anyone who has the hash, including wallet addresses and balances. There is no built-in way to prove a payment occurred without exposing private information. Privacy protocols have the opposite problem. Proving a transaction happened typically requires revealing the secret note, which compromises the privacy of the transaction entirely. Silo’s redacted receipts sit between these two extremes. They provide verifiable proof that a payment occurred, with enough detail to be useful for real-world purposes, while redacting the information that would expose either party’s on-chain identity. This makes receipts practical for use cases like expense reporting, payroll records, tax documentation, and dispute resolution: scenarios where proof of payment is needed but full on-chain transparency is not.

​

Relationship to Payment Instructions

Redacted receipts and Payment Instructions draw from the same underlying transaction data captured in Silo’s database throughout the payment lifecycle. Receipts are generated and delivered to both parties as soon as the relevant transaction data is available. They do not depend on the Payment Instruction being finalized or uploaded to Walrus. The redacted receipt is a filtered view of the transaction record, tailored to show each party only the information relevant to them. The full Payment Instruction, once finalized and stored on Walrus, contains the complete unredacted record and remains encrypted and access-controlled on Silo’s backend.