25.55K
total weekly downloads
50 packages
@umbra-privacy/arcium-codama
Generated Codama clients for the Arcium protocol
@umbra-privacy/ceremony
Terminal UI for the Umbra Phase 2 trusted setup ceremony
@umbra-privacy/circuit-artifacts
Resolve a circuit's proving key, witness calculator and verifying key onto a device: three wire encodings, the caller's choice of store, and a verifying key derived from the bytes so the chain can be the integrity anchor. Pre-release (0.x): every API, typ
@umbra-privacy/codama
Generated Codama clients for the Umbra protocol
@umbra-privacy/coordinator-client-core
The envelope every Umbra process coordinator answers in: an upstream reply, the status rules a reply is held to, and the readers that turn the coordinator's JSON into checked values. A lane's own client names its coordinator, its routes and its request bo
@umbra-privacy/crypto-suite
The TypeScript half of libs/rust/crypto-suite: SP 800-185 KMAC and TupleHash, the dealer's hybrid ML-KEM plus X25519 encapsulation, and the composite ML-DSA-87 and Ed25519 signer the guardian and fee-enclave operators sign with. Whoever builds a request f
@umbra-privacy/data-endorser-client
The Umbra data endorser over HTTP: endorse a process3x3x2x2 or a register, and read the node identity. JSON only, in its own snake_case plus base64 dialect. Pre-release (0.x): every API, type and behaviour is subject to change at any time, as and when the
@umbra-privacy/fee-enclave-client
The Umbra fee enclave over HTTP: read its boot parameters, seal a fee claim to its transport key, and read its attestation. Pre-release (0.x): every API, type and behaviour is subject to change at any time, as and when the Nimbus Privacy team (built by Um
@umbra-privacy/guardian-client
One guardian share node over HTTP: fetch its KEM key for a fresh label, seal a share pair to it, and endorse a process3x3x2x2 or a registration. Pre-release (0.x): every API, type and behaviour is subject to change at any time, as and when the Nimbus Priv
@umbra-privacy/indexer-proto-gen
Generated TypeScript protobuf types for the Umbra Indexer services
@umbra-privacy/indexer-read-service-client
TypeScript client for the Umbra Indexer Read Service
@umbra-privacy/indexer-write-service-client
TypeScript client for the Umbra Indexer Write Service
@umbra-privacy/key-words
Typed word encodings for BN254 field elements and 64-byte secrets: the BIP-39 English list at lengths no wallet accepts, with a checksum bound to what the secret is and where it belongs. Loads nothing at run time. Pre-release (0.x): every API, type and be
@umbra-privacy/klend-sdk
Typescript SDK for interacting with the Kamino Lending (klend) protocol
@umbra-privacy/nimbus-hash
The circuits' Poseidon constructions and domain table, and BN254 field encoding and constant-time arithmetic, as circuits/zk/hash defines them, over an injected permutation; the base every protocol core builds on. Pre-release (0.x): every API, type and be
@umbra-privacy/nimbus-identity
The Umbra identity commitment: keys, ML-KEM keypair, bindings and root, derived through a labelled HKDF and sampled in constant time, with every outside function injected by the caller. Pre-release (0.x): every API, type and behaviour is subject to change
@umbra-privacy/nimbus-instructions-solana
Every Solana instruction the SDK sends, byte for byte, and the accounts and program addresses they name, as the programs in contracts/solana define them. Pre-release (0.x): every API, type and behaviour is subject to change at any time, as and when the Ni
@umbra-privacy/nimbus-merkle
The circuits' mixed-arity and indexed Merkle trees, as circuits/zk/merkle defines them, with the tree shape always an argument. Pre-release (0.x): every API, type and behaviour is subject to change at any time, as and when the Nimbus Privacy team (built b
@umbra-privacy/nimbus-note
The note as circuits/zk/protocol/{note,nullifier,value} defines it: plaintext, commitment, tree leaf and nullifiers, and the sealed note blob every reader must agree on byte for byte. Pre-release (0.x): every API, type and behaviour is subject to change a
@umbra-privacy/nimbus-primitives
The primitives every nimbus package is handed, named for the published standards and Anza formats they implement: their types, their known-answer checks, the guard every call passes through, and the one error the protocol cores throw. Pre-release (0.x): e
@umbra-privacy/nimbus-primitives-wasm
Every @umbra-privacy/nimbus-primitives member filled from one single-threaded WebAssembly module built from libs/rust/nimbus-primitives-wasm, with randomness from an injected getRandomValues. Pre-release (0.x): every API, type and behaviour is subject to
@umbra-privacy/nimbus-solana
The Umbra wallet SDK for Solana: register, deposit, withdraw and transfer, and the wallet's state, on the protocol cores, with every outside function, format and party injected through deps. Dependency-free: `@umbra-privacy/nimbus-solana-web` fills it for
@umbra-privacy/nimbus-solana-web
The Solana SDK for browsers with every dependency filled: load it for a cluster from its bundled preset, open a session for the connected wallet, and run the flows, with crypto in WASM, IndexedDB storage, the prover's WASM, the service clients and @solana
@umbra-privacy/nimbus-statement
The inputs and public aggregate of each entry circuit the wallet proves, transaction (process_3x3x2x2) and registration, as circuits/zk and its manifest define them. Pre-release (0.x): every API, type and behaviour is subject to change at any time, as and
@umbra-privacy/nimbus-storage-solana
The Solana wallet's storage, for the shielded pool on Solana: an ordered key-value port with all-or-nothing conditional commits, the row envelope every store writes, and the backends that implement the port, with every outside function injected by the cal