DOCS / SDK

flipforge-sdk: trust the key, not the endpoint.

The SDK is a thin typed client over the API with one opinion: every response should be re-verified locally. It ships the published key, recomputes the digest and checks the signature — so your integration never has to trust FlipForge's infrastructure, only its key. Zero dependencies beyond noble crypto; works in Node 18+ and the browser.

Install

npm i flipforge-sdk▌

Usage

import { FlipForge } from "flipforge-sdk";

const ff = new FlipForge(); // → https://useflipforge.xyz

// reads — every answer is a SignedResponse<T>
const status = await ff.status();
const mint   = await ff.mint("2b1kV6Dk…u24GXo");
const acct   = await ff.account("AKJ5Lpxy…QgSjB");
const tx     = await ff.transaction("4L8j3NVF…eksep");
const reg    = await ff.registry();
const act    = await ff.activity("mainnet");

// offline verification against the pinned key
const check = await ff.verify(mint);
check.ok;             // true
check.digestMatches;  // sha-256 over canonical bytes
check.signatureValid; // ed25519 against FLIPFORGE_PUBKEY▌

Methods

METHOD	RETURNS	WHAT
status()	SignedResponse<{ clusters }>	ZK program probe, both clusters
mint(address, cluster?)	SignedResponse<MintInfo>	header + TLVs + confidential config
account(address, cluster?)	SignedResponse<AccountInfo>	public header + encrypted balances
transaction(sig, cluster?)	SignedResponse<TxInfo>	decoded proof instructions
registry()	SignedResponse<{ mints }>	known confidential mints, live
activity(cluster?)	SignedResponse<{ transactions }>	recent ZK-program txs
verify(signed)	VerifyResult	offline receipt verification

What tampering looks like

// flip one digit of the supply…
mint.result.header.supply = mint.result.header.supply.replace(/0$/, "1");

const bad = await ff.verify(mint);
bad.ok;            // false
bad.digestMatches; // false — verification fails closed▌