Update from Toasty Peeps

What we worked on

Completed the Zcash shielded settlement test integration for Toasty Peeps. The confidential paid engagement (Jam) path now includes shielded recipient validation, settlement quoting and status handling, FullPrivacy enforcement, private compliance receipts, and public audit trails (Breadcrumbs) that deliberately exclude private counterparties, transaction IDs and settlement amounts. A live regtest end-to-end test path was added for settlement through the payments and earnings layer (Dough).

We also merged the broader Toasty Peeps product foundation and tracked the Colosseum resources skill directly in the project so hackathon ecosystem tooling is part of the build environment.

What went well

The privacy work moved from an architectural direction into testable product infrastructure. Confidential paid engagements (Jams) can be compliance-approved, routed through the Zcash shielded rail, and represented publicly without leaking the sensitive settlement data. The code also explicitly blocks the Zcash adapter from mainnet for now, keeping experimentation constrained to testnet/regtest.

What didn’t

There is not yet evidence in today’s repository activity that the live regtest settlement was executed against a funded wallet. The end-to-end test exists, but it remains environment-gated and requires Zallet RPC credentials, a funded source account and a shielded recipient.

Challenges

Keeping useful proof and reputation signals public while confidential engagement and payment data stay private. The settlement architecture also has to preserve compliance evidence without turning the public audit trail (Breadcrumb layer) into a privacy leak.

Accomplishments

• Completed Zcash shielded settlement test integration.

• Added live regtest end-to-end coverage through the payments and earnings layer (Dough).

• Added shielded recipient validation and settlement status handling.

• Added private compliance receipts tied to settlement state.

• Added privacy-safe confidential paid engagement audit trails (Jam Breadcrumbs).

• Merged the Toasty Peeps product foundation.

• Tracked the Colosseum resources skill in the repository.

Learnings

Privacy has to be enforced at the data-model boundary, not treated as a presentation choice. A useful public proof can say that a verified institutional engagement happened without exposing who participated, how much was paid or the private transaction identifier. Keeping mainnet disabled until the test path is proven is the right constraint for the hackathon stage.

Next focus

Run and verify the live funded Zcash regtest path end to end. Continue turning the confidential paid engagement (Jam) flow into a demonstrable institutional use case. Keep the public proof layer useful while testing that private settlement and compliance data cannot leak into audit trails (Breadcrumbs).