Pre-compiled libraries, proto files, and copy-paste samples for building confidential apps on the IronWeave ledger.
Every release is published from CI to a public mirror. The buttons always resolve to the newest build, and the link you copy is permanent — pinned to a version, content-addressed, and shipped with SHA-256 checksums.
Pedersen commitments, Bulletproof range proofs, Schnorr equality proofs, Ed25519 signing, ECDH encryption — with transcript-bound transfers.
Native libraries
Packages & bindings
Chunked AES-256-GCM streaming for large payloads, multi-party key sharing, and signed protobuf envelopes — anchored on-chain. Builds on iwcrypto.
Native libraries
Packages & bindings
dotnet add package IronWeave.Crypto
· every artifact ships with SHA-256 checksums.
Thin building blocks you link straight into your app — the same primitives the fabric uses to keep balances and payloads private.
Every confidential operation on IronWeave is built from three primitives plus a binding trick. You don't have to implement them — iwcrypto does — but here's what's happening under the hood.
Combine a secret value with a random blinding factor over two public curve points. The result looks like gibberish, yet it's hiding (reveals nothing), binding (you can't change your mind), and additive — so hidden balances can be summed without ever being seen.
Prove a committed value lies in [0, 2⁶⁴) without revealing it. Without this, an attacker could spend a negative amount — which wraps into a huge positive on the curve. Bulletproofs need no trusted setup.
Prove two commitments hide the same value even after re-randomizing the blinding (for privacy). The value terms cancel in the difference — what's left is a Schnorr proof over the blinding delta.
Every proof's challenge is hashed together with five context fields, cryptographically gluing the proof to one specific operation. Replay it anywhere else — different op, role, token, or account — and it simply fails to verify.
| Operation | Equality proofs | Range proofs | Balance check |
|---|---|---|---|
| Transfer | 3 | 3 | Homomorphic |
| Mint | 1 | 1 | Public amount |
| Burn | 1 | 1 | Public amount |
| Reset | 1 | 0 | — |
| Rerandomize | 1 | 0 | — |
| Assertion | 0 | 2 | — |
Every operation composes from the same building blocks — the simplest use one proof; a transfer uses six plus a homomorphic balance check.
The core API is four RPCs, available as gRPC or plain HTTP/JSON. No client library required to get started — just curl.
Sign the serialized bytes with Ed25519 and submit. Consensus writes a block to every participant's chain.
Fetch the latest block on any chain by its public-key address — ID only, or the full block.
Look up any block by hash or transaction ID and walk history via back-references.
Discover public API endpoints and supported protocol versions for peer connection.
# read a chain's head over plain HTTP/JSON curl -k -X POST \ https://api.testnet.ironweave.io:21042/ironweave/api/core/chain/head/get \ -H "Content-Type: application/json" \ -d '{ "chainAddress": { "addressType": "ADDRESS_TYPE_ED25519", "value": "<base64 public key>" }, "returnBlock": true }'
The getting-started repo teaches the API in five small, self-contained steps — the same concepts, in the same order, in every language.