Sources and verification

These docs describe implemented behavior from the app and SDK revisions below. Network capabilities are checked separately against Midnight’s official documentation, because an application README can lag a network upgrade.

Reviewed implementation

Source	Revision	Review scope
Shielded Pools app (local checkout)	329a03b56ea802b8e7ea28b61288dcff3853b15b	Transfer forms, amount and recipient validation, wallet discovery and network checks, transaction tracking, public history, security notes, and disabled bridge interface.
Shielded Pool SDK	6f6a573ab6d2e011efede0010a70549bb812332a	Contract calls, wrapped-token identity, backing queries, immutability guards, argument validation, and transaction outcomes.

The SDK’s pool implementation defines shield and unshield: wrapping locks an amount and issues the same amount of the wrapped token; unwrapping retires wrapped tokens and releases the same amount of the underlying token. It also defines the immutability guard and public backing query. Its transaction handling distinguishes known failure from an unknown outcome, including partial application.

The app calls these operations with NIGHT. Transfer.tsx, amount.ts, and pool.ts establish the guide steps, six decimal places, and recipient types. wallets.ts establishes connector discovery and network validation; transaction.ts establishes progress and unresolved-request handling. history.ts and the transfer notices establish the public addresses and amounts described on the Privacy page.

The app README records the proof-server trust warning and fake-connector testing limit. Its wording does not establish that no compatible wallet exists. config.ts offers Mainnet and Preprod; Bridge.tsx is a disabled interface. These observations do not independently verify any live contract or deployment.

Official network check

Checked 10 November 2026, against Midnight’s Environments and endpoints page (updated 10 November 2026): Preview, Preprod, and Mainnet run ledger 9. The page reports a Preview reset on 6 November 2026, removing that prior chain’s contracts and balances, and an in-place Preprod upgrade on 9 November 2026.

This supersedes the app README’s outdated ledger-8 Preview statement. Network capability and Shielded Pools support are separate: no Shielded Pools Preview deployment was verified or inferred. This check reads official release information; it does not probe network endpoints or test availability.

Public access and review limits

Checked 10 November 2026, using unauthenticated GitHub REST repository requests:

• App repository: HTTP 404, so it was not publicly accessible during this check. A 404 does not establish whether a repository is private, missing, or renamed. The app review relied on the available local checkout at the revision above. Readers cannot independently inspect that implementation through the public link at present.
• SDK repository: HTTP 200; the pinned commit endpoint also returned 200. The SDK is publicly accessible, under its own Apache-2.0 license.

No proprietary app implementation files are included in this documentation repository. Local source inspection supports the documented behavior but is not an independent contract audit, a real-wallet compatibility test, or a check of the live app’s deployed code. Do not use inaccessible app links as evidence of public availability.

Keeping these docs current

When app or SDK behavior changes, review the relevant code and update the affected guides and revision references together. Recheck time-sensitive network statements against official Midnight release notes, and record the date. Recheck public access separately when links change.

The production build and check:links are offline checks: they validate generated pages, internal links, metadata, social assets, and sitemap/404 behavior. They do not contact GitHub, Midnight, or other external sites. External checks described above were performed explicitly during this review.