@zbase-protocol/core 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 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 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 Support. 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 support.
+
+   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 2026 Goh Ee Sheng / zBase contributors
+
+   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,20 @@
+zBase
+Copyright 2026 Goh Ee Sheng / zBase contributors
+
+This product includes software developed by 0xbow
+(https://github.com/0xbow-io/privacy-pools-core), licensed under the
+Apache License, Version 2.0.
+
+The Privacy Pools cryptographic primitives and contract patterns
+(commitment/nullifier scheme, association-set Merkle construction, and the
+Groth16 withdrawal circuit lineage) are adapted from that codebase, which
+implements the Privacy Pools research co-authored by Vitalik Buterin.
+
+zBase adds, as new work: the x402 payment-facilitator layer, the
+Association Set Provider (ASP) screening + threshold-postman tooling, the
+agent-identity layer, the UTXO/shielded-transfer extension, and a Solana
+(Anchor) port. The Solana program crate name `zx402_privacy_pool` is
+retained for IDL stability; the product brand is zBase.
+
+Licensed under the Apache License, Version 2.0. You may obtain a copy of
+the License at http://www.apache.org/licenses/LICENSE-2.0

package/README.md

@@ -0,0 +1,118 @@
+# @zbase-protocol/core
+
+> Chain-agnostic ZK privacy primitives for x402 AI agent payments.
+
+[![npm](https://img.shields.io/npm/v/@zbase-protocol/core.svg)](https://www.npmjs.com/package/@zbase-protocol/core)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+
+🧪 **Status: testnet.** Currently live against Base Sepolia via the hosted facilitator at [zbase.app](https://zbase.app). Mainnet ships on first signed pilot. The SDK code itself is chain-agnostic — `facilitatorURL` and `networkId` are configurable.
+
+## Privacy model (honest)
+
+Before you integrate, know exactly what this gives your users.
+
+**Provides today (live on Base Sepolia):**
+- **Sender/receiver unlinkability.** The recipient address has no on-chain link to the depositor's wallet. The link is broken by a Groth16 proof of pool membership + a nullifier that marks the note spent.
+- **Compliance-gated privacy.** Only deposits from clean addresses (ASP-approved subset) can withdraw. This is the Vitalik-Buterin-coauthored design, not Tornado Cash.
+
+**Does NOT provide today:**
+- **Amount hiding.** `_value` is emitted in plaintext on both `Deposited` and the withdrawal/settle event. Anyone watching the chain sees deposit amounts and withdrawal amounts — only the *link* between them is broken.
+- **Timing-correlation defense.** The decoy scheduler (`scripts/decoy-scheduler.ts`) exists but is not running in prod. A single withdrawal in a quiet window is trivially attributable.
+- **Amount-frequency-attack defense.** A `$99.99` deposit followed by a `$99.99` settle is correlatable.
+
+**Roadmap (scaffolded, not deployed):**
+- UTXO notes (`circuits/note_spend.circom`, `createNote` / `splitNote` / `mergeNotes` in this SDK) → true amount hiding. Needs trusted setup ceremony.
+- Threshold-signed ASP (`ThresholdEntrypoint.sol`) → distributed compliance trust.
+- Decoy scheduler in prod → defeats FIFO temporal de-anon.
+
+**Anonymity-set size is the privacy metric, not TVL.** The pool can hold 0 USDC and still provide full anonymity to new deposits — the commitment Merkle tree grows on every deposit and never shrinks on withdrawal. Low TVL only blocks *other* users' withdrawals, not your privacy.
+
+Full deep-dive: **[zbase.gitbook.io/threat-model](https://zbase.gitbook.io/threat-model)**.
+
+zBase is built on Vitalik Buterin's [Privacy Pools research](https://github.com/0xbow-io/privacy-pools-core) (Apache 2.0, audited reference implementation by 0xbow). This package contains the chain-agnostic primitives shared across all chain implementations.
+
+## Install
+
+```bash
+npm install @zbase-protocol/core
+```
+
+## Quickstart
+
+```ts
+import {
+  generateDepositSecrets,
+  computeCommitment,
+  computeNullifierHash,
+} from "@zbase-protocol/core";
+
+// 1. Generate fresh nullifier + secret for a deposit
+const secrets = generateDepositSecrets();
+
+// 2. Compute the commitment hash (what goes on-chain)
+//    value is atomic USDC (6 decimals): 1_000_000 = 1 USDC
+const commitment = computeCommitment(
+  1_000_000n,
+  secrets.nullifier,
+  secrets.secret
+);
+
+// 3. Settle a private payment via the hosted facilitator
+const response = await fetch("https://zbase.app/api/facilitator/settle", {
+  method: "POST",
+  headers: { "Content-Type": "application/json" },
+  body: JSON.stringify({
+    paymentDetails: {
+      scheme: "exact",
+      networkId: "eip155:84532", // Base Sepolia
+      payTo: "0xProviderAddress",
+      maxAmountRequired: "500000", // 0.5 USDC
+    },
+    zbaseDeposit: { ...secrets, value: "990000", label: "...", commitment: "..." },
+  }),
+});
+```
+
+For a full end-to-end test (deposit → settle → withdraw) on Base Sepolia, see [`scripts/integration-sdk-vs-facilitator.mjs`](https://github.com/goheesheng/zBase/blob/main/scripts/integration-sdk-vs-facilitator.mjs).
+
+## What's exported
+
+| Area | Symbols |
+|---|---|
+| **Account / secrets** | `generateDepositSecrets`, `computeCommitment`, `computePrecommitment`, `computeNullifierHash`, `computeLabel`, `feToBE32`, `SNARK_SCALAR_FIELD`, `createAccount`, `serializeAccount`, `deserializeAccount` |
+| **ZK proofs** | `generateWithdrawalProof`, `verifyProofLocally` (Groth16 via snarkjs) |
+| **Merkle tree** | `buildMerkleTree`, `generateMerkleProof`, `getTreeDepth` (LeanIMT) |
+| **UTXO notes** (scaffold) | `createNote`, `commitmentOf`, `nullifierHashOf`, `splitNote`, `mergeNotes`, `planSpend`, `serializeNote`, `deserializeNote`, `generateViewingKey`, `encryptNote`, `decryptNote`, `scanNotes` |
+| **ERC-5564 stealth** | `generateMetaAddress`, `parseMetaAddress`, `deriveStealthAddress`, `scanForPayments`, `computeStealthPrivateKey`, `STEALTH_SCHEME_ID` |
+| **Privacy scanner** | `analyzeTransfers` |
+
+Full TypeScript types exported alongside. 38 named exports total.
+
+## Status of the hosted facilitator
+
+The default facilitator at `https://zbase.app` runs on **Base Sepolia** today. Mainnet ships on first signed pilot — same code path, env-var flip only. Check live status:
+
+```bash
+curl https://zbase.app/api/facilitator/supported
+```
+
+## How to test
+
+Three paths, depending on persona:
+
+- **Browser**: [zbase.app/test](https://zbase.app/test) — connect wallet, get Sepolia USDC, deposit + withdraw privately
+- **Agent (curl)**: pure HTTP, no SDK required. See [`/api/skill`](https://zbase.app/api/skill) for AI coding agents
+- **SDK**: this package. See `scripts/integration-sdk-vs-facilitator.mjs` in the repo for a runnable smoke test
+
+## Links
+
+- 🌐 [zbase.app](https://zbase.app)
+- 📖 [Documentation (GitBook)](https://zbase.gitbook.io)
+- 🐙 [GitHub](https://github.com/goheesheng/zBase)
+- 🐦 [@zbase__](https://twitter.com/zbase__)
+- 🐰 Companion: [@zbase-protocol/svm (Solana)](https://www.npmjs.com/package/@zbase-protocol/svm)
+- 🤖 Companion: [@zbase-protocol/mcp (Claude Desktop / Cursor)](https://www.npmjs.com/package/@zbase-protocol/mcp)
+
+## License
+
+Apache 2.0. Built on Vitalik Buterin's [Privacy Pools research](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4563364) and the [0xbow reference implementation](https://github.com/0xbow-io/privacy-pools-core).

package/dist/account.d.ts

@@ -0,0 +1,79 @@
+/**
+ * @zbase-protocol/core — Chain-agnostic account management
+ *
+ * Hashing matches the upstream Privacy Pools circom circuit exactly:
+ *   * `precommitment = Poseidon(2)([nullifier, secret])`
+ *   * `commitment    = Poseidon(3)([value, label, precommitment])`
+ *   * `nullifierHash = Poseidon(1)([nullifier])`
+ *   * `label         = keccak256(scope || nonce_be32) % SNARK_SCALAR_FIELD`
+ * See packages/circuits/circuits/commitment.circom in the 0xbow/privacy-pools-core
+ * repo for ground truth. Any deviation here breaks proof verification.
+ */
+import type { AccountSecrets, ZX402AccountData, ChainType } from "./types.js";
+export declare const SNARK_SCALAR_FIELD = 21888242871839275222246405745257275088548364400416034343698204186575808495617n;
+/**
+ * Generate a fresh nullifier + secret.
+ * The full commitment depends on `value` and `label`, both of which only
+ * become known at deposit time — so this returns just the secrets.
+ */
+export declare function generateDepositSecrets(): {
+    nullifier: string;
+    secret: string;
+};
+/**
+ * `precommitment = Poseidon(2)([nullifier, secret])`.
+ * Sent to the on-chain `deposit` instruction. The pool then computes
+ * `commitment = Poseidon(3)([value, label, precommitment])` itself, so the
+ * depositor cannot lie about which value/label their commitment claims.
+ */
+export declare function computePrecommitment(nullifier: string, secret: string): string;
+/**
+ * `commitment = Poseidon(3)([value, label, precommitment])`. Mirrors the
+ * `CommitmentHasher` template in `commitment.circom`.
+ */
+export declare function computeCommitment(value: string | bigint, label: string | bigint, precommitment: string | bigint): string;
+/**
+ * `nullifierHash = Poseidon(1)([nullifier])`. Used as the spend marker
+ * on-chain (and as PDA seed on Solana). Output is the second public signal
+ * of the withdraw circuit.
+ */
+export declare function computeNullifierHash(nullifier: string | bigint): string;
+/**
+ * `label = keccak256(scope || nonce_be32) % SNARK_SCALAR_FIELD`. Mirrors the
+ * EVM pool's on-chain label derivation and the SVM program's
+ * `crypto::compute_label`. Both `scope` and `nonce` are encoded as 32-byte
+ * big-endian values to match the on-chain Solana implementation.
+ */
+export declare function computeLabel(scope: string | bigint, nonce: number | bigint): string;
+/**
+ * Encode a field element as 32-byte big-endian. Required by the on-chain
+ * Solana program (and by `groth16-solana` for proof public inputs).
+ */
+export declare function feToBE32(value: string | bigint): Uint8Array;
+/**
+ * Create a full account from secrets + on-chain data.
+ */
+export declare function createAccount(secrets: AccountSecrets, chain: ChainType, depositTxHash?: string): ZX402AccountData;
+/**
+ * Serialize account to JSON for storage.
+ */
+export declare function serializeAccount(account: ZX402AccountData): string;
+/**
+ * Deserialize account from JSON.
+ */
+export declare function deserializeAccount(json: string): ZX402AccountData;
+/**
+ * Generate a uniformly-random field element in the BN254/BN128 scalar field,
+ * via REJECTION SAMPLING (audit F7).
+ *
+ * The naive `random256() % SNARK_SCALAR_FIELD` is biased: 2^256 is not a
+ * multiple of the field order, so the lowest values in [0, 2^256 mod r) are
+ * slightly more likely. For per-note `nullifier`/`secret` values that bias is a
+ * small but real statistical weakness. Rejection sampling — redraw whenever the
+ * 256-bit sample is >= the largest multiple of r below 2^256 — yields an exactly
+ * uniform result. The reject probability is < ~6e-39 per draw (r is ~2^253.6),
+ * so this terminates in one iteration in practice.
+ *
+ * Uses `crypto.getRandomValues` (CSPRNG), never Math.random.
+ */
+export declare function randomFieldElement(): bigint;

package/dist/account.js

@@ -0,0 +1,140 @@
+/**
+ * @zbase-protocol/core — Chain-agnostic account management
+ *
+ * Hashing matches the upstream Privacy Pools circom circuit exactly:
+ *   * `precommitment = Poseidon(2)([nullifier, secret])`
+ *   * `commitment    = Poseidon(3)([value, label, precommitment])`
+ *   * `nullifierHash = Poseidon(1)([nullifier])`
+ *   * `label         = keccak256(scope || nonce_be32) % SNARK_SCALAR_FIELD`
+ * See packages/circuits/circuits/commitment.circom in the 0xbow/privacy-pools-core
+ * repo for ground truth. Any deviation here breaks proof verification.
+ */
+import { poseidon1, poseidon2, poseidon3 } from "poseidon-lite";
+import { keccak_256 } from "@noble/hashes/sha3";
+export const SNARK_SCALAR_FIELD = 21888242871839275222246405745257275088548364400416034343698204186575808495617n;
+/**
+ * Generate a fresh nullifier + secret.
+ * The full commitment depends on `value` and `label`, both of which only
+ * become known at deposit time — so this returns just the secrets.
+ */
+export function generateDepositSecrets() {
+    return {
+        nullifier: randomFieldElement().toString(),
+        secret: randomFieldElement().toString(),
+    };
+}
+/**
+ * `precommitment = Poseidon(2)([nullifier, secret])`.
+ * Sent to the on-chain `deposit` instruction. The pool then computes
+ * `commitment = Poseidon(3)([value, label, precommitment])` itself, so the
+ * depositor cannot lie about which value/label their commitment claims.
+ */
+export function computePrecommitment(nullifier, secret) {
+    return poseidon2([BigInt(nullifier), BigInt(secret)]).toString();
+}
+/**
+ * `commitment = Poseidon(3)([value, label, precommitment])`. Mirrors the
+ * `CommitmentHasher` template in `commitment.circom`.
+ */
+export function computeCommitment(value, label, precommitment) {
+    return poseidon3([BigInt(value), BigInt(label), BigInt(precommitment)]).toString();
+}
+/**
+ * `nullifierHash = Poseidon(1)([nullifier])`. Used as the spend marker
+ * on-chain (and as PDA seed on Solana). Output is the second public signal
+ * of the withdraw circuit.
+ */
+export function computeNullifierHash(nullifier) {
+    return poseidon1([BigInt(nullifier)]).toString();
+}
+/**
+ * `label = keccak256(scope || nonce_be32) % SNARK_SCALAR_FIELD`. Mirrors the
+ * EVM pool's on-chain label derivation and the SVM program's
+ * `crypto::compute_label`. Both `scope` and `nonce` are encoded as 32-byte
+ * big-endian values to match the on-chain Solana implementation.
+ */
+export function computeLabel(scope, nonce) {
+    const buf = new Uint8Array(32 + 8);
+    feToBE32(BigInt(scope)).forEach((b, i) => (buf[i] = b));
+    // 8 bytes big-endian nonce
+    let n = BigInt(nonce);
+    for (let i = 7; i >= 0; i--) {
+        buf[32 + i] = Number(n & 0xffn);
+        n >>= 8n;
+    }
+    const h = keccak_256(buf);
+    let x = 0n;
+    for (const b of h)
+        x = (x << 8n) | BigInt(b);
+    return (x % SNARK_SCALAR_FIELD).toString();
+}
+/**
+ * Encode a field element as 32-byte big-endian. Required by the on-chain
+ * Solana program (and by `groth16-solana` for proof public inputs).
+ */
+export function feToBE32(value) {
+    const out = new Uint8Array(32);
+    let v = BigInt(value);
+    if (v < 0n)
+        throw new Error("feToBE32: negative");
+    for (let i = 31; i >= 0; i--) {
+        out[i] = Number(v & 0xffn);
+        v >>= 8n;
+    }
+    if (v !== 0n)
+        throw new Error("feToBE32: value > 2^256");
+    return out;
+}
+/**
+ * Create a full account from secrets + on-chain data.
+ */
+export function createAccount(secrets, chain, depositTxHash) {
+    return {
+        secrets,
+        depositTxHash,
+        chain,
+        withdrawn: false,
+        createdAt: Date.now(),
+    };
+}
+/**
+ * Serialize account to JSON for storage.
+ */
+export function serializeAccount(account) {
+    return JSON.stringify(account);
+}
+/**
+ * Deserialize account from JSON.
+ */
+export function deserializeAccount(json) {
+    return JSON.parse(json);
+}
+/**
+ * Generate a uniformly-random field element in the BN254/BN128 scalar field,
+ * via REJECTION SAMPLING (audit F7).
+ *
+ * The naive `random256() % SNARK_SCALAR_FIELD` is biased: 2^256 is not a
+ * multiple of the field order, so the lowest values in [0, 2^256 mod r) are
+ * slightly more likely. For per-note `nullifier`/`secret` values that bias is a
+ * small but real statistical weakness. Rejection sampling — redraw whenever the
+ * 256-bit sample is >= the largest multiple of r below 2^256 — yields an exactly
+ * uniform result. The reject probability is < ~6e-39 per draw (r is ~2^253.6),
+ * so this terminates in one iteration in practice.
+ *
+ * Uses `crypto.getRandomValues` (CSPRNG), never Math.random.
+ */
+export function randomFieldElement() {
+    // Largest multiple of r that fits in 256 bits; samples >= this are rejected.
+    const TWO_256 = 1n << 256n;
+    const limit = TWO_256 - (TWO_256 % SNARK_SCALAR_FIELD);
+    const bytes = new Uint8Array(32);
+    for (;;) {
+        crypto.getRandomValues(bytes);
+        let value = 0n;
+        for (const byte of bytes)
+            value = (value << 8n) | BigInt(byte);
+        if (value < limit)
+            return value % SNARK_SCALAR_FIELD;
+        // else: in the biased tail — redraw (astronomically rare).
+    }
+}

package/dist/experimental.d.ts

@@ -0,0 +1,27 @@
+/**
+ * @zbase-protocol/core/experimental — UNFINISHED UTXO surface. NOT PRODUCTION.
+ *
+ * ⚠️ These variable-amount UTXO primitives are a PRE-DEPLOYMENT scaffold. The UTXO
+ * pool is not deployed (routes return 501) and the trusted-setup ceremony has not
+ * run. The 2026-07-09 SDK audit found integrator fund-lock footguns here:
+ *   - the note wire format is inconsistent (packCiphertext is length-prefixed but
+ *     the scanner decodes a fixed bytes32[4]) → a recipient may be unable to
+ *     decrypt their own note;
+ *   - createNote defaults NPK material to 0 → a note addressable to nobody;
+ *   - deriveViewingKeyFromSeed diverges from the mnemonic path for non-64-byte
+ *     seeds → recovery can silently fail.
+ *
+ * This surface lives on a SEPARATE subpath (not the main entry) so no integrator
+ * reaches it by accident: you must explicitly `import ... from
+ * "@zbase-protocol/core/experimental"` and thereby accept it is unfinished. Do
+ * NOT rely on the UTXO wire format or these APIs against real funds until the
+ * pool + ceremony land and these are re-audited.
+ */
+export type { Note, ViewingKeyPair, EncryptedNote } from "./notes.js";
+export { createNote, createDummyNote, commitmentOf, npkOf, nullifierHashOf, splitNote, mergeNotes, planSpend, consolidateNotes, serializeNote, deserializeNote, generateViewingKey, encryptNote, decryptNote, scanNotes, NoteValueError, commitmentAAD, encryptNoteForTransfer, decryptNoteWithAAD, packCiphertext, unpackCiphertext, CIPHERTEXT_WIRE_VERSION, } from "./notes.js";
+export type { DerivedNPK, DeriveRecipientNPKParams } from "./npk.js";
+export { deriveRecipientNPK, recoverViewingPKBlind, bytesToField } from "./npk.js";
+export type { ViewingKey } from "./viewingKeyHD.js";
+export { ZBASE_VIEWING_KEY_PATH_PREFIX, DEFAULT_MNEMONIC_STRENGTH_BITS, generateNewMnemonic, deriveViewingKeyFromMnemonic, deriveViewingKeyFromSeed, exportMnemonic, mnemonicFromEntropy, isValidMnemonic, } from "./viewingKeyHD.js";
+export type { ScannerEvent, ScannerConnectedEvent, ScannerSpentEvent, ScannerTransferredInEvent, ScannerTransferredOtherEvent, ScannerErrorEvent, ScannerOptions, DecodedTransferredLog, } from "./noteScanner.js";
+export { createScanner, decodeSpentLog, decodeTransferredLog, tryDecryptTransferred, scanTransferredLogs, SPENT_TOPIC, TRANSFERRED_TOPIC, } from "./noteScanner.js";

package/dist/experimental.js

@@ -0,0 +1,23 @@
+/**
+ * @zbase-protocol/core/experimental — UNFINISHED UTXO surface. NOT PRODUCTION.
+ *
+ * ⚠️ These variable-amount UTXO primitives are a PRE-DEPLOYMENT scaffold. The UTXO
+ * pool is not deployed (routes return 501) and the trusted-setup ceremony has not
+ * run. The 2026-07-09 SDK audit found integrator fund-lock footguns here:
+ *   - the note wire format is inconsistent (packCiphertext is length-prefixed but
+ *     the scanner decodes a fixed bytes32[4]) → a recipient may be unable to
+ *     decrypt their own note;
+ *   - createNote defaults NPK material to 0 → a note addressable to nobody;
+ *   - deriveViewingKeyFromSeed diverges from the mnemonic path for non-64-byte
+ *     seeds → recovery can silently fail.
+ *
+ * This surface lives on a SEPARATE subpath (not the main entry) so no integrator
+ * reaches it by accident: you must explicitly `import ... from
+ * "@zbase-protocol/core/experimental"` and thereby accept it is unfinished. Do
+ * NOT rely on the UTXO wire format or these APIs against real funds until the
+ * pool + ceremony land and these are re-audited.
+ */
+export { createNote, createDummyNote, commitmentOf, npkOf, nullifierHashOf, splitNote, mergeNotes, planSpend, consolidateNotes, serializeNote, deserializeNote, generateViewingKey, encryptNote, decryptNote, scanNotes, NoteValueError, commitmentAAD, encryptNoteForTransfer, decryptNoteWithAAD, packCiphertext, unpackCiphertext, CIPHERTEXT_WIRE_VERSION, } from "./notes.js";
+export { deriveRecipientNPK, recoverViewingPKBlind, bytesToField } from "./npk.js";
+export { ZBASE_VIEWING_KEY_PATH_PREFIX, DEFAULT_MNEMONIC_STRENGTH_BITS, generateNewMnemonic, deriveViewingKeyFromMnemonic, deriveViewingKeyFromSeed, exportMnemonic, mnemonicFromEntropy, isValidMnemonic, } from "./viewingKeyHD.js";
+export { createScanner, decodeSpentLog, decodeTransferredLog, tryDecryptTransferred, scanTransferredLogs, SPENT_TOPIC, TRANSFERRED_TOPIC, } from "./noteScanner.js";