Coming soon on Aleo·Zero-knowledge by default
spectre_
AleoComing Soon
> initializing spectre_invoices.leo...
> connecting to aleo...
> privacy: ON
> compliance: ON
> launching...
Zero-Knowledge Invoices on Aleo

Invoices that

can’t be seen

Mint invoices as encrypted Leo records.
Compliance verified on-chain with ZK proofs.
Minimal trust surface. No TEE. No custodian.

Coming Soon

Everything. Exposed.

Public blockchains broadcast every transaction. Sender, recipient, amount — all visible to anyone.

Traditional invoicing. Zero privacy.

PDFs with names, bank details, amounts. Forwarded, intercepted, leaked.

Compliance. Bolted on. After the fact.

Regulatory checks happen after exposure. The damage is already done.

There’s a better way.

Create an
encrypted invoice

No wallet address exposed. No personal data. Just an Aleo ID and an encrypted Leo record.

Spectre App

Recipient ID

aleo1qnr3...spectre

Amount

500ALEO
Create Invoice

Leo Program

transition create_invoice(
    recipient_id: field,
    amount: u64,
) -> InvoiceRecord {
    return InvoiceRecord {
        owner: self.caller,
        recipient: recipient_id,
        amount: amount,
        status: 0u8,
    };
}

Invoice minted as a private Leo record.
On-chain. Encrypted. Only visible to parties involved.

Compliance proved.
Identity hidden.

Compliance verified on-chain with ZK proofs. Minimal trust surface.

ZK Compliance

> running compliance check...
> generating zk_exclusion_proof...
> proving: sender NOT in sanctions list
> proving: recipient NOT in sanctions list
> proof generated ✓
> revealing: NOTHING

Exclusion Proof

Thousands of sanctioned addresses as Merkle leaves.

ZK circuit proves exclusion without revealing position or touching any node.

Proof attaches to invoice record like a cryptographic seal.

Funds move.
Nothing leaks.

Payment

PENDING
→VERIFIED
→SETTLED
transition pay_invoice(
    invoice: InvoiceRecord,
    compliance_proof: Proof,
    payment: credits.aleo
) -> Receipt {
    // verify proof, transfer, seal
}

Encrypted capsule through the Aleo network. Every node it passes — untouched, unreadable.

Recipient

> new record received
> invoice_id: [encrypted]
> amount: [encrypted]
> compliance: VERIFIED ✓
> status: CLAIMABLE

Recipient sees what they need. Nobody else sees anything.

> batch_withdraw: 4 invoices → 1 proof → 1 tx

Batch. Private. One proof covers everything.

Built on
zero-knowledge

Aleo
RuntimeAleo
LanguageLeo
ProofsZK-SNARKs
ComplianceMerkle Exclusion
PrivacyEncrypted Records
SettlementOn-chain