Shieldport

Shieldport · harbour notes, vol. 1

Move between chains the way light moves through glass.

Shieldport is a set of instruments for people who keep their coins shielded on Zcash and trade on Solana. Read any unified address, watch the three markets that matter, and see exactly which leg of a crossing leaves footprints — before you take it.

Instruments
Six, all working
Venues read
Hyperliquid · Jupiter · mempool.space
Custody
None. Nothing to sign.
Begin

The tide table

Three assets, three public venues, one honest clock. ZEC from Hyperliquid's perpetual book, SOL and Solana-side ZEC from Jupiter, bitcoin from mempool.space. Cross rates and the wrapped-ZEC premium are computed here, in your browser.

Live prices
AssetPrice24 hContextSource
ZECZcash · perp midHyperliquid
ZECsolZcash on SolanaJupiter
SOLSolanaJupiter
BTCBitcoinmempool.space

Cross rates computed

1 ZEC in SOL
—
1 ZEC in sats
—
Wrapped premium
—
ZEC funding, hourly
—

The premium compares ZEC on Solana (Jupiter) with the Hyperliquid mid. A few basis points either side is normal friction; a wide gap means the bridge or pool is thin.

Waiting for first reading…

ZEC, last 24 hoursHourly closes from Hyperliquid
Loading candles…

Two ledgers

Zcash keeps two kinds of record side by side. Choose a payment direction and watch what the public record keeps, what it seals, and what an observer can still infer.

Diagram of a payment from a sender wallet to a recipient wallet passing through the public chain record. Sendert1 address Recipientt1 address Public chain record

An observer learns

    Leaves a footprint when

    Round-trip check heuristic

    Shielding an amount and deshielding nearly the same amount soon after is the most common way shielded privacy is undone. Enter both legs to see how alike they look.

    Interlude · scroll to decode

    Anatomy of one address

    1. One string. A ZIP 316 test-vector unified address: 213 characters of bech32m, with a checksum in its tail.
    2. Checked, then bytes. The checksum holds and the characters become 128 bytes — still scrambled by F4Jumble, so no part of it can be read on its own.
    3. Unjumbled. Four rounds of BLAKE2b mixing run in reverse. Typecodes and lengths surface, and the last sixteen bytes spell the prefix.
    4. Three receivers. Transparent, Sapling and Orchard, stacked like panes. The sender’s wallet pays the most private one it supports.

    The address reader

    A unified address is several addresses folded into one string. This reader verifies the bech32m checksum, reverses the F4Jumble mixing step with BLAKE2b, and lays every receiver out on the table. It runs entirely in your browser; nothing is sent anywhere.

    Samples from the ZIP 316 test vectors:

    Paste an address, or pick a sample. The reader decodes as you type.

    The crossing

    Plot a route from where your coins are to where you want them. Each leg shows what it costs today and what it reveals. The final swap on Solana is a live Jupiter quote; the bridge leg is a model with a fee you set.

      The fee ledger

      Zcash prices a transaction by its logical actions, not its size (ZIP 317). Set the shape of a transaction and the ledger computes the conventional fee, then sets it beside what bitcoin and Solana charge right now.

      Shapes:

      Conventional fee

      10,000 zatoshis

      0.0001 ZEC

      Bitcoin, 1 in 2 out, next block
      —
      Solana, one signature + median priority
      —

      The sealed note

      Every shielded output carries a 512-byte encrypted memo that only the recipient can read. Compose one, see its exact bytes, and wrap it in a ZIP 321 payment request any Zcash wallet can open.

      A memo can only travel to a shielded receiver.

      Attach a routing note for a Solana destination

      Checked locally: must decode to exactly 32 bytes.

      0of 512 bytes

      Memo bytes (first 64 of 512)

      
            

      ZIP 321 payment request

      —

      Harbour rules

      What Shieldport is for, what it is still drawing, and the lines it will not cross.

      01

      Shielded is the default, not the upgrade

      Every instrument here assumes your coins start in a shielded pool. When a route must touch a transparent address, the map says so in plain words and shows you the leg where it happens.

      02

      Read before you sign

      The address reader exists because a unified address hides its receivers inside one string. Know whether a transparent fallback is in there before a wallet decides for you.

      03

      Nothing held, nothing signed

      No wallet connect, no keys, no deposits. Shieldport only reads public prices and does arithmetic on your screen. Closing the tab ends every session.

      04

      Every number shows its source

      Prices name their venue. Anything we cannot observe — a bridge fee, a heuristic — carries a model or heuristic label and an input you control.

      Working today

      • Live ZEC, wrapped ZEC, SOL and BTC with cross rates
      • Unified address decoder with receiver re-encoding
      • Route and exposure map with live Jupiter quote
      • ZIP 317 fee ledger with live comparisons
      • Memo composer and ZIP 321 request builder
      • Round-trip linkability check

      On the drawing board

      • Launch a Solana coin paid for from a shielded wallet
      • Memo-addressed swaps settled on Solana
      • Viewing-key reports for your own records

      These are designs, not products. There is no Shieldport token and no launch pad live today.

      Questions

      Short answers to the things people ask first.

      Does Shieldport ever see my address or keys?

      No. The address reader, fee ledger and memo composer run as JavaScript in your tab. The only network calls are price and quote requests to Hyperliquid, Jupiter and mempool.space, and none of them include anything you type into the reader or memo.

      What is a unified address, in one sentence?

      A single string, starting with u1, that bundles one or more receivers — Orchard, Sapling and optionally transparent — so the sender's wallet can choose the most private one it supports.

      Why does the reader warn about transparent receivers?

      If a sender's wallet cannot use the shielded receivers, it may pay the transparent one, and that payment is fully public. An address with only Orchard and Sapling receivers removes that fallback.

      Is the bridge fee real?

      No, it is a model. Bridges and venues price differently and change often, so the crossing map lets you set the percentage. The Jupiter swap leg and the network fees are live.

      Where does ZEC on Solana come from?

      The price row reads a Solana-side ZEC token that Jupiter lists as verified. It is a bridged representation, not native Zcash; holding it carries the bridge's risk, and Solana transfers of it are public.

      How is the Zcash fee calculated?

      By ZIP 317: 5,000 zatoshis per logical action, with a floor of two actions. Logical actions are the larger of transparent inputs or outputs, plus the larger of Sapling spends or outputs, plus Orchard actions. Wallets pad shielded bundles, which the ledger includes.

      Can I pay or launch anything here?

      Not today. Shieldport has no custody, no swaps and no launch flow. The payment request in Chapter VI is a link your own wallet opens; Shieldport never sees whether it was paid.

      Is there a Shieldport coin?

      Not at the time of writing. If one is published, its contract address will appear in the header and footer of this page, and nowhere else should be trusted.