@chainvue/verus-sapling 0.0.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,74 @@
+@chainvue/verus-sapling
+Copyright (c) 2026 Robert Lech
+
+Licensed under the Apache License, Version 2.0.
+
+This package targets the Verus (VRSC) shielded protocol, which is stock Zcash
+Sapling: unmodified circuit, byte-identical MPC parameters, and the stock
+consensus branch id 0x76b809bb. Unlike @chainvue/verus-sdk, this package bundles
+no VerusCoin source — the only Verus-specific value is that branch id.
+
+--------------------------------------------------------------------------------
+Bundled third-party software (statically linked into the published WASM artifact,
+crate/pkg/verus_sapling_prover_bg.wasm)
+--------------------------------------------------------------------------------
+
+The WASM prover is compiled from the Rust crate in crate/ and links the following
+libraries into its object code. Each remains under its own license.
+
+Zcash Sapling protocol implementation — Electric Coin Company:
+  * sapling-crypto        (MIT OR Apache-2.0) — Sapling circuit, Groth16 prover,
+                          RedJubjub signatures, note encryption, bundle builder.
+  * zcash_note_encryption (MIT OR Apache-2.0) — ZIP-212 note encryption.
+  * bellman               (MIT OR Apache-2.0) — Groth16 zk-SNARK proving system.
+                          Copyright (c) Sean Bowe and the bellman contributors.
+
+zkcrypto pairing / elliptic-curve libraries — Sean Bowe and the zkcrypto
+contributors (all MIT OR Apache-2.0):
+  * bls12_381, jubjub, group, ff, pairing, pasta_curves
+
+RedDSA / RedJubjub signature scheme — Henry de Valence and the Zcash Foundation
+(all MIT OR Apache-2.0):
+  * reddsa, redjubjub
+
+Utility libraries:
+  * blake2b_simd  (MIT)            — Copyright (c) Jack O'Connor
+  * subtle        (BSD-3-Clause)   — Copyright (c) Isis Lovecruft, Henry de Valence
+  * rand, rand_core, rand_chacha
+                  (MIT OR Apache-2.0) — The Rand Project Developers
+  * hex           (MIT OR Apache-2.0)
+  * serde_json    (MIT OR Apache-2.0) — Copyright (c) David Tolnay, Erick Tryzelaar
+
+The full text of the Apache License 2.0 is in LICENSE. Copies of the MIT and
+BSD-3-Clause licenses accompany the respective upstream projects; see each
+crate's repository (https://github.com/zcash, https://github.com/zkcrypto,
+https://github.com/ZcashFoundation) for its license text and copyright notices.
+
+Bundled protobuf definitions (proto/*.proto):
+  * The lightwalletd gRPC definitions (compact_formats.proto, service.proto,
+    darkside.proto) are the stock Zcash lightwalletd protos.
+    Copyright (c) 2019-2020 The Zcash developers. License: MIT (each file
+    retains its MIT header). Verus's lightwalletd fork does not modify them.
+
+--------------------------------------------------------------------------------
+Proving parameters — NOT bundled
+--------------------------------------------------------------------------------
+
+The Sapling proving parameters (sapling-spend.params ~47 MB, sapling-output.params
+~3.5 MB) are the canonical Zcash Sapling MPC parameters and are NOT included in
+this package. Consumers obtain them separately and pass their bytes to the prover.
+Verify integrity by SHA-256:
+
+  sapling-spend.params   8e48ffd23abb3a5fd9c5589204f32d9c31285a04b78096ba40a79b75677efc13
+  sapling-output.params  2f0ebbcbb9bb0bcffe95a397e7eba89c29eb4dde6191c339db88570e3f3fb0e4
+
+These parameters are the output of the Zcash Sapling "Powers of Tau" and
+parameter-generation ceremonies; see https://z.cash for provenance.
+
+--------------------------------------------------------------------------------
+Optional npm dependencies (installed under their own licenses, not bundled)
+--------------------------------------------------------------------------------
+
+  * @grpc/grpc-js, @grpc/proto-loader (Apache-2.0) — used only by the optional
+    Node lightwalletd client (@chainvue/verus-sapling/lightwalletd). The package
+    root and the browser subpath pull in no gRPC runtime.

package/README.md

@@ -0,0 +1,194 @@
+# @chainvue/verus-sapling
+
+<p>
+  <a href="https://github.com/chainvue/verus-sapling/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/chainvue/verus-sapling/actions/workflows/ci.yml/badge.svg"></a>
+  <a href="https://www.npmjs.com/package/@chainvue/verus-sapling"><img alt="npm" src="https://img.shields.io/npm/v/@chainvue/verus-sapling?color=cb3837&logo=npm"></a>
+  <img alt="node" src="https://img.shields.io/node/v/@chainvue/verus-sapling">
+  <img alt="types" src="https://img.shields.io/badge/types-included-3178c6?logo=typescript&logoColor=white">
+  <a href="./LICENSE"><img alt="license" src="https://img.shields.io/badge/license-Apache--2.0-blue"></a>
+  <img alt="offline" src="https://img.shields.io/badge/network-none%20in%20signer-success">
+</p>
+
+> **Offline signing of Verus _shielded_ (Sapling) transactions** — `t→z`, `z→z`,
+> `z→t`, with encrypted memos. It builds and signs bytes; your consumer
+> broadcasts. **No full node on the signing host.**
+
+Companion to [`@chainvue/verus-sdk`](https://www.npmjs.com/package/@chainvue/verus-sdk)
+(transparent transactions). Where the SDK stays pure-TS and tiny, this package
+adds the one thing shielded signing genuinely needs — a Sapling zk-prover —
+compiled to WASM and kept opt-in.
+
+- 🔐 **All three shielded flows:** shield (`t→z`), private send (`z→z`), deshield (`z→t`), each with a ZIP-302 memo.
+- 🧾 **Real zk-proving in WASM** (`sapling-crypto` → Groth16/BLS12-381), RedJubjub spend-auth & binding signatures, note encryption.
+- 🛰️ **Client-side note detection** — trial-decrypts compact blocks; no `z_listunspent`, no wallet daemon.
+- 🌐 **Browser-ready** — a gRPC-web transport and Web Worker prover ship; a runnable MV3 extension broadcasts a private `z→z` from Chrome.
+- 💰 **`bigint` satoshis end-to-end** — one checked crossing into float64, never a silent `number`.
+- ✅ **Daemon-verified** — the byte-layout bar is acceptance by a real Verus daemon, not self-consistent tests.
+
+> [!WARNING]
+> Proven on **testnet**. Before mainnet or real funds, read
+> [`SECURITY.md`](SECURITY.md) — the full spending key is present on the signing
+> host (the same trust surface as a transparent WIF).
+
+## Contents
+
+- [Install](#install) · [Quick start](#quick-start) · [How it works](#how-it-works)
+- [Proving parameters](#proving-parameters) · [Backend](#backend-the-one-unavoidable-dependency)
+- [Security](#security) · [Examples](#examples) · [Project layout](#project-layout) · [Contributing](#contributing)
+
+## Install
+
+```bash
+npm install @chainvue/verus-sapling
+```
+
+The compiled WASM prover is shipped in the package (`crate/pkg/`). You supply the
+two Sapling [proving parameters](#proving-parameters) (~50 MB, fetched once) at
+runtime.
+
+## Quick start
+
+Load the prover, then use the lightwalletd-driven orchestration. Chain data comes
+through a `LightwalletdTransport`; the concrete Node gRPC client lives on the
+`./lightwalletd` subpath (the package root pulls in **no** gRPC).
+
+```ts
+import { detectNotes, buildShieldedSpend, initSapling } from '@chainvue/verus-sapling';
+import { LightwalletdClient } from '@chainvue/verus-sapling/lightwalletd';
+
+await initSapling(wasmBytes);                       // load the wasm module once
+const client = new LightwalletdClient('lightwalletd:9077');
+
+// 1. Find the wallet's own notes — no z_listunspent, no full node.
+const notes = await detectNotes(client, detectProver, {
+  key: { dfvkHex },              // a viewing key is enough to scan (recommended)
+  fromHeight: walletBirthday,    // toHeight defaults to the chain tip
+});
+
+// 2. Spend one detected note (z→z / z→t) with a memo.
+const { hex } = await buildShieldedSpend(client, spendProver, {
+  note: { txid: notes[0].txid, outputIndex: notes[0].outputIndex, extskHex },
+  shieldedOutputs: [{ address, valueSats, memo }],   // valueSats is a bigint
+});
+await client.sendTransaction(hex);
+```
+
+`detectProver` / `spendProver` are thin callbacks you wire to the WASM builders
+(`detectNotes` on the main thread; `spendShielded` in a Web Worker for the ~20 s
+prove — see [`examples/extension`](examples/extension)). Memos are `string`,
+≤ 512 bytes. For `t→z` shielding, call the `shieldT2z` builder directly.
+
+> **Scan with a viewing key, spend with the spending key.** `detectNotes` needs
+> only a Diversifiable Full Viewing Key (`dfvkHex`); load the full spending key
+> (`extskHex`) only to sign a spend. See [`SECURITY.md`](SECURITY.md).
+
+## How it works
+
+The Rust crate (`crate/`) is compiled to WASM and owns the parts that must be
+byte-exact: the **ZIP-243 sighash**, the **v4 transaction serializer**, Sapling
+**proving**, the signatures, and note encryption. The TypeScript layer (`src/`)
+stays thin: input validation, the `bigint` money invariant, the lightwalletd
+transport, and address/key marshalling.
+
+### Verus = stock Zcash Sapling
+
+Confirmed against Verus source and a live mainnet node: Verus shielded is
+**stock Zcash Sapling** — unmodified `zcash/librustzcash` circuit, byte-identical
+MPC parameters, stock consensus branch id `0x76b809bb`, version group id
+`0x892f2085`, tx v4. Consensus is frozen at Sapling on **both** mainnet and
+testnet (Canopy — which would gate ZIP-212 — is not in Verus's upgrade set), so
+ZIP-212 enforcement is `Off`. The only Verus-specific value in the entire path is
+that branch id, injected into the sighash. Even the lightwalletd wire protocol is
+stock — `VerusCoin/lightwalletd`'s protos are byte-identical to Zcash's.
+
+### Backend: the one unavoidable dependency
+
+- **`t→z` (shielding)** needs **no** commitment-tree witness — only the
+  transparent UTXOs you already fetch. The true "sign privately with zero extra
+  backend" case.
+- **`z→z` / `z→t`** spend shielded notes, which need each note's Merkle **witness
+  + anchor** and **note detection**. Those come from a chain-scanning service —
+  a stock **Verus lightwalletd** (standard gRPC `GetBlockRange` / `GetTreeState`).
+  The signing host still runs no full node, but this service is required.
+  Browsers additionally need a gRPC-web proxy in front of it.
+
+## Proving parameters
+
+The prover needs two parameter files — the **canonical Zcash Sapling MPC
+parameters**, byte-identical for Verus. They are **not** bundled (≈50 MB would
+bloat every install); fetch them once and pass their bytes to `initSapling` and
+the prover.
+
+| file | size | SHA-256 |
+| --- | --- | --- |
+| `sapling-spend.params` | ~47 MB | `8e48ffd23abb3a5fd9c5589204f32d9c31285a04b78096ba40a79b75677efc13` |
+| `sapling-output.params` | ~3.5 MB | `2f0ebbcbb9bb0bcffe95a397e7eba89c29eb4dde6191c339db88570e3f3fb0e4` |
+
+**Always verify the SHA-256.** Get them from any Zcash full node
+(`zcutil/fetch-params.sh`), a local Verus install, or your own host — then cache
+them (IndexedDB / Cache API in the browser, the filesystem in Node). Non-canonical
+params produce proofs the daemon rejects.
+
+## Security
+
+This library signs money and the spending key is present on the signing host.
+[`SECURITY.md`](SECURITY.md) documents the trust model in full — what is
+guaranteed (the key never crosses the network, is never logged, and is not in the
+signed tx) and what is not (WASM memory is not zeroized; host/supply-chain
+compromise). **Report vulnerabilities privately** via a GitHub security advisory,
+never a public issue.
+
+<details>
+<summary><b>Daemon-verified on testnet</b> — txids</summary>
+
+All three flows were built by this code and accepted by a Verus testnet daemon:
+
+- **t→z** `1edf8aa6…6623` (native) and `d142edf8…a0ef` (built in WASM)
+- **z→z** `53ea99fc…89feb` — fully private, recipient received 9.9999
+- **z→t** `86951c8d…bd8a` — transparent recipient received 0.05
+- **z→z, fully lightwalletd-sourced** `07e3b38e…f996` — every byte of chain data
+  from lightwalletd, signed in WASM, no full node
+
+Note detection is cross-checked against consensus: the nullifier it predicts for
+a note matches the on-chain nullifier of the spend that later consumed it,
+byte-for-byte. The ZIP-243 serializer/sighash is regression-tested against
+daemon-made golden vectors (`cargo test`).
+
+</details>
+
+## Examples
+
+- [`examples/extension`](examples/extension) — a runnable **MV3 browser
+  extension**: detect notes, read the inbox, and broadcast a private `z→z` from
+  Chrome, proving in a Web Worker.
+- [`examples/messenger`](examples/messenger) — an end-to-end **shielded-memo
+  messenger**: framed messages carried in zero-value notes.
+
+## Project layout
+
+```
+src/            TypeScript: validation, money, wallet orchestration, transport
+  browser/      gRPC-web transport + Web Worker prover (no external gRPC dep)
+crate/          Rust: ZIP-243 sighash, v4 serializer, Sapling proving
+  pkg/          committed WASM build (so a fresh clone works without Rust)
+proto/          stock Zcash lightwalletd gRPC definitions
+examples/       runnable extension + messenger demos
+test/           vitest suite (money, hex, protobuf, gRPC-web, wallet, zaddr, …)
+```
+
+Docs: [SECURITY](SECURITY.md) · [CONTRIBUTING](CONTRIBUTING.md) ·
+[RELEASING](RELEASING.md) · [NOTICE](NOTICE) ·
+[Code of Conduct](CODE_OF_CONDUCT.md)
+
+## Contributing
+
+Contributions are welcome — see [CONTRIBUTING.md](CONTRIBUTING.md). The gate is
+`npm run build` → `npm run typecheck` → `npm test`, plus `cargo test` for the
+crate. Commits follow [Conventional Commits](https://www.conventionalcommits.org/)
+(they drive the automated release).
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE). Third-party provenance for the WASM prover's
+bundled Rust crates, the vendored lightwalletd protos, and the proving parameters
+is in [NOTICE](NOTICE).

package/crate/pkg/package.json

@@ -0,0 +1,17 @@
+{
+  "name": "verus-sapling-prover",
+  "type": "module",
+  "description": "Sapling proving/signing core for Verus shielded transactions (t->z, z->z, z->t). Native + wasm32.",
+  "version": "0.0.0",
+  "license": "Apache-2.0",
+  "files": [
+    "verus_sapling_prover_bg.wasm",
+    "verus_sapling_prover.js",
+    "verus_sapling_prover.d.ts"
+  ],
+  "main": "verus_sapling_prover.js",
+  "types": "verus_sapling_prover.d.ts",
+  "sideEffects": [
+    "./snippets/*"
+  ]
+}

package/crate/pkg/verus_sapling_prover.d.ts

@@ -0,0 +1,71 @@
+/* tslint:disable */
+/* eslint-disable */
+
+/**
+ * Detect the wallet's own notes by trial-decrypting compact outputs (read path
+ * — no params, no proving). `spec_json` is the note-detection request (see
+ * `json_api::detect_notes_from_json`). Returns a JSON array of detected notes.
+ * Cheap (milliseconds); safe to call on the main thread.
+ */
+export function detect_notes(spec_json: string): string;
+
+/**
+ * Fully decrypt one incoming output (value + recipient + memo) with the
+ * wallet's viewing key. `spec_json` is the read request (see
+ * `json_api::read_note_from_json`). Returns a JSON object, or the string
+ * "null" if the output is not for this key. Cheap (no params, no proving).
+ */
+export function read_note(spec_json: string): string;
+
+/**
+ * Build + sign a t->z shielding transaction. `spec_json` is the t->z request
+ * (see `json_api::build_t2z_from_json`). Returns the transaction hex; the caller
+ * still has the daemon fill the transparent scriptSig (signrawtransaction).
+ */
+export function shield_t2z(spec_json: string, spend_params: Uint8Array, output_params: Uint8Array): string;
+
+/**
+ * Build + sign a z->z / z->t transaction that spends a shielded note. Complete
+ * after this (no transparent inputs) — broadcast directly.
+ */
+export function spend_shielded(spec_json: string, spend_params: Uint8Array, output_params: Uint8Array): string;
+
+export type InitInput = RequestInfo | URL | Response | BufferSource | WebAssembly.Module;
+
+export interface InitOutput {
+    readonly memory: WebAssembly.Memory;
+    readonly detect_notes: (a: number, b: number) => [number, number, number, number];
+    readonly read_note: (a: number, b: number) => [number, number, number, number];
+    readonly shield_t2z: (a: number, b: number, c: number, d: number, e: number, f: number) => [number, number, number, number];
+    readonly spend_shielded: (a: number, b: number, c: number, d: number, e: number, f: number) => [number, number, number, number];
+    readonly __wbindgen_exn_store: (a: number) => void;
+    readonly __externref_table_alloc: () => number;
+    readonly __wbindgen_externrefs: WebAssembly.Table;
+    readonly __wbindgen_malloc: (a: number, b: number) => number;
+    readonly __wbindgen_realloc: (a: number, b: number, c: number, d: number) => number;
+    readonly __externref_table_dealloc: (a: number) => void;
+    readonly __wbindgen_free: (a: number, b: number, c: number) => void;
+    readonly __wbindgen_start: () => void;
+}
+
+export type SyncInitInput = BufferSource | WebAssembly.Module;
+
+/**
+ * Instantiates the given `module`, which can either be bytes or
+ * a precompiled `WebAssembly.Module`.
+ *
+ * @param {{ module: SyncInitInput }} module - Passing `SyncInitInput` directly is deprecated.
+ *
+ * @returns {InitOutput}
+ */
+export function initSync(module: { module: SyncInitInput } | SyncInitInput): InitOutput;
+
+/**
+ * If `module_or_path` is {RequestInfo} or {URL}, makes a request and
+ * for everything else, calls `WebAssembly.instantiate` directly.
+ *
+ * @param {{ module_or_path: InitInput | Promise<InitInput> }} module_or_path - Passing `InitInput` directly is deprecated.
+ *
+ * @returns {Promise<InitOutput>}
+ */
+export default function __wbg_init (module_or_path?: { module_or_path: InitInput | Promise<InitInput> } | InitInput | Promise<InitInput>): Promise<InitOutput>;