> ## Documentation Index
> Fetch the complete documentation index at: https://corridor.udokaam.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Shielded supplier batch

> Three suppliers paid privately in one Zcash Ironwood transaction: priced by NEAR Intents, funded from the Tempo hub, held for FROST approval, co-signed by two of three signers, reconciled through a viewing key.

An importer (`acme-imports`) pays three suppliers \$5 each and does not want competitors reading the amounts. The console action **Pay 3 suppliers privately** ran this on testnet on 29 September 2026.

<Frame caption="Fig. 06 · The shielded lane: funded from the hub, held for 2-of-3 FROST approval, one Ironwood transaction, read by the auditor with a viewing key.">
  <img className="block dark:hidden" src="https://mintcdn.com/corridorapp/YeOtjsXcStLLcZ_W/images/diagrams/shielded-lane-light.svg?fit=max&auto=format&n=YeOtjsXcStLLcZ_W&q=85&s=4df37dd666aefb6690645486601c2f4d" alt="Shielded lane through NEAR Intents into a FROST vault and out to suppliers" width="1200" height="600" data-path="images/diagrams/shielded-lane-light.svg" />

  <img className="hidden dark:block" src="https://mintcdn.com/corridorapp/YeOtjsXcStLLcZ_W/images/diagrams/shielded-lane-dark.svg?fit=max&auto=format&n=YeOtjsXcStLLcZ_W&q=85&s=49b22d8ebd0347718a81428f73323f9a" alt="Shielded lane through NEAR Intents into a FROST vault and out to suppliers" width="1200" height="600" data-path="images/diagrams/shielded-lane-dark.svg" />
</Frame>

## The plan

```text theme={"dark"}
ledger.reserve → near.swap → zcash.shieldedBatch          (testnet)
ledger.reserve → across.bridge → near.swap → zcash.shieldedBatch   (mainnet)
```

`privacy: "shielded"` is the only difference from a public payout: the planner requires the route to end in the `zcash_ironwood` venue and appends the batch leg.

## Step by step

<Steps>
  <Step title="Reserve $15">
    15 pathUSD moves to the customer's hold.
  </Step>

  <Step title="Price with NEAR Intents">
    A live mainnet 1Click quote: \*\*$15 → 0.01022830 ZEC** (about $1,466.52 per ZEC). The quote is stored in `leg_artifacts`.
  </Step>

  <Step title="Leave the hub">
    15 pathUSD leaves the treasury toward the swap venue with the batch reference as memo ([0xbafdbde3…](https://explore.testnet.tempo.xyz/tx/0xbafdbde30386b736fb7151df338ebacc395843575704303fe5e438c17bb760a5)).
  </Step>

  <Step title="Deliver ZEC into the vault">
    0.01022830 testnet ZEC arrives at the FROST vault's unified address ([1f05d641…](https://testnet.zcashexplorer.app/transactions/1f05d6415ad694bdc3ecffc06ef57eb9b859b2fbc1c5724601faf5bf806ee720)). The hold converts into a ZEC liability through the `usd-zec` clearing pair.
  </Step>

  <Step title="Build and prove the batch">
    30,000 zatoshi are kept back for the ZIP-317 fee and the remaining **0.00992830 ZEC** is split by USD share into three outputs, each with an encrypted memo: `INV-2026-09-S01`, `S02`, `S03`.
  </Step>

  <Step title="Hold for approval">
    The saga opens an approval request (threshold 2 of 3) and waits. In the console it showed **1 of 2 required** after signer 1 approved.
  </Step>

  <Step title="Co-sign and broadcast">
    Signer 3 approved; `corridor-frost` co-signed with exactly signers 1 and 3; the batch was broadcast and mined ([ba4e845b…](https://testnet.zcashexplorer.app/transactions/ba4e845b81b7d6faf350fd01cf967d9d35d717d5bc3eb455eb48ee945b3c38c7)).
  </Step>

  <Step title="Book and reconcile">
    One entry per recipient output plus the actual 20,000-zatoshi fee to `expense:zcash-fees`. The vault's viewing-key scan produces observations that match every entry.
  </Step>
</Steps>

## What the world sees

| Party | View |
| - | - |
| The public | A Tempo transfer to the swap venue and one shielded Zcash transaction. No recipients, no amounts. |
| Each supplier | Their payment and invoice memo, in their own wallet |
| The auditor | With the exported viewing key: exactly these three payouts, nothing else from the treasury |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.