Fairseal

io.fairseal由 fairseal.io 發布v0.2.4更新於 Nov 4, 2026

Verifiable entropy, provably-fair games, and receipt verification for AI agents (FairSeal API).

已驗證STDIO僅桌面金融開發者工具安全與監控

概覽

AI 產生的概覽

FairSeal MCP 伺服器透過 FairSeal API，讓助理取得可驗證亂度、可證明公平的抽選憑證，以及憑證驗證能力。

可以做什麼
  • 從公開的 drand 信標輪次取得可驗證亂數與亂度
  • 提交隨機抽選的承諾，並依已承諾規則解析結果
  • 建立、公證並錨定結果憑證，證明結果在揭曉前已固定
  • 離線驗證憑證並查詢使用統計
  • 向外部鏈提交錨定，取得可獨立查核的時間證明
適用情境
當助理需要執行或稽核他人事後可查核的隨機分配時使用，例如抽卡、掉落、配對、賽事種子、鑄造順序，或任何需要證明結果在揭曉前已承諾的情境。
執行需求
以 stdio 在本機執行，通常透過 npm 套件 @fairseal/mcp-server 安裝。受限工具需要 FAIRSEAL_API_KEY 中的 API 金鑰；可選用 FAIRSEAL_ANCHOR_API_KEY 與 FAIRSEAL_NOTARY_API_KEY 覆寫，未設定時回退至前者。FAIRSEAL_API_URL 可指向其他 API 位址。需要連線至 FairSeal API 與 drand 信標的網路。
安裝前請注意
API 金鑰屬於機密，可存取受限工具；沒有金鑰時這些工具會回傳 401。錨定與公證會向外部服務與公開鏈寫入紀錄，README 亦提到透過 x402 結算小額付款，呼叫可能產生費用。憑證與承諾會提交給第三方並可被公開查核。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Fairseal，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Fairseal 🦭

Provably fair selections for games, loot boxes, and any randomized allocation.

Fairseal creates verifiable receipts (CSRs) proving that a selection was committed before the outcome was knowable. Every loot drop, gacha pull, and randomized selection — independently verifiable, trustlessly.

[@fairseal/commit] [@fairseal/core] [graded]

Try It Now

bash
npx @fairseal/commit

One command. A verifiable gacha pull in your terminal. No setup.

Quick Start

bash
npm install @fairseal/commit
typescript
import { createCommitment, resolveCommitment, createReceipt, verifyReceipt } from '@fairseal/commit';
// 1. Lock your loot table BEFORE the outcome is knowableconst commitment = createCommitment({  rule: JSON.stringify(LOOT_TABLE),  inputs: [playerId, pullNumber.toString()],  revealAfter: 10,});
// 2. Resolve with verifiable entropy from drandconst resolution = await resolveCommitment(commitment);
// 3. Your algorithm + verifiable entropy = provably fair dropconst drop = yourWeightedPull(LOOT_TABLE, resolution.beaconRandomness);
// 4. Package as a receipt anyone can verifyconst receipt = createReceipt(commitment, resolution);const proof = await verifyReceipt(receipt); // ✅ PARTIAL

How It Works

  1. Commit — Lock your drop table + player ID into a hash before the randomness exists
  2. Entropy — Wait for a public drand beacon round (Cloudflare + Protocol Labs)
  3. Resolve — Derive the selection from beacon entropy + your committed rule
  4. Verify — Anyone can re-run every step. drand beacon signatures are BLS12-381-verified; FairSeal receipt signatures use EIP-191 (secp256k1) / Ed25519 — receipts are never BLS-signed. No trust required.

Performance

OperationTime
Commitment creation0.006ms (170,000+/sec)
Beacon fetch~200ms
drand beacon verification (BLS12-381)~150ms
Receipt size0.9 KB

Client-side. No server. No account. No fees for PARTIAL verification.

Packages

PackageDescription
@fairseal/gameGame API for RGS studios. Slots, gacha, loot boxes. (v0.1 ALPHA)
@fairseal/commitCommitted selection receipts. Core library.
@fairseal/coreCryptographic primitives, signing, Merkle trees.
@fairseal/verifyIndependent receipt verification.
@fairseal/mcp-serverMCP server for AI agents. Verifiable entropy, provably-fair games, cryptographic receipt verification via Model Context Protocol.

Use Cases

ScenarioHow
Gacha / loot boxEvery pull has a receipt. Players verify drops match published rates.
Boss loot dropsDrop table committed per encounter. No ninja-nerfing.
MatchmakingPairing algorithm committed. Players verify no favoritism.
Tournament bracketsSeeding provably random, not rigged.
NFT mint orderQueue provably fair — no insider front-running.
Slot machinesSeed Commitment Model — verifiable spins, no nonce chain.

Result Notarization vs. Activity Receipts

Most "agent receipts" today are activity receipts: the platform logs what an agent did, and you trust whoever wrote the log. Fairseal receipts are result notarization — a different trust model:

Activity receipts (platform logs)Fairseal result notarization
Who do you trust?The operator writing the logNo one — receipts verify offline
What is proven?That an action was recordedThat a result was committed before the outcome was knowable
Time proofServer timestamp (operator-controlled)External anchor on Base (independently checkable)
Tamper evidenceDepends on log integrityHash-anchored; any modification breaks verification

Related standards: payment-authorization protocols like Google/Mastercard AP2 (mandates), Visa TAP, and OpenAI/Stripe ACP prove that an agent may act and who it is. Fairseal proves what happened — that a result was committed and hasn't been altered since. Fairseal settles micropayments over Coinbase's x402 and does not implement AP2/TAP/ACP; the layers are complementary.

Links

Listings

License

MIT — Fairseal

來源：README.md，提交 8ff9498

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

2
  1. v0.2.4最新Sep 30, 2026
  2. v0.2.3Sep 27, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分