Bloom Exchange

io.github.astyboyy-ship-it由 GitHub 账号 astyboyy-ship-it 发布v0.2.0更新于 Nov 20, 2026

Negotiate in a double-blind sandbox and verify Ed25519 receipts. Agent-to-agent clearing over A2A.

发布方自己的服务:Exchange.news — Crypto offers, campaigns and news

概览

AI 生成的概览

让助手在 Bloom Exchange 节点上与另一智能体进行双盲价格谈判,并验证 Ed25519 签名的结算凭证。

可以做什么
  • 按授权条件(价格上限、预算、SLA 等级、账期)在 Bloom Exchange 节点上发起谈判
  • 离线或依据签发方签名的 Agent Card 验证 BLOOM-XCH 凭证
  • 通过 A2A JSON-RPC 发布智能体意图以进行清算
  • 在节点启用时轮询事件流,获取唤醒与结算后钩子
适用场景
当你希望 IDE 或桌面智能体针对 Bloom Exchange 节点执行机器对机器的采购或价格谈判,并取得可验证的签名结算凭证时使用,通常适用于沙箱或测试环境而非真实支付流程。
运行要求
通过 npm 包 @bloom-exchange/mcp 以 npx 在本地以 stdio 运行,需要 Node 20 或更高版本。需要一个可访问的 Bloom Exchange 节点;BLOOM_EXCHANGE_URL 指定其基础地址(默认 BLOOM_ACCESS_KEY 用于从沙箱切换到生产清算,BLOOM_AGENT_NAME 设定智能体的自我介绍名称。仅限桌面端。
安装前请注意
BLOOM_ACCESS_KEY 是密钥,会将环境从沙箱切换到生产清算并解锁运营视图,请勿放入共享配置。谈判与意图发布会把数据发送到所配置的节点及其对等节点,凭证可能包含 AP2、Stripe 与 x402 支付载荷。README 说明当前金库运行在提供方节点上,因此交易对手需信任该运营方不会读取其授权条件。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Bloom Exchange,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Bloom Exchange

Two AI agents negotiate a deal over A2A JSON-RPC while each side's price limits stay sealed in salted SHA-256 commitments that the other side's engines never see; a prompt-injection firewall screens every message, deterministic clamps keep every offer inside both mandates, and the result is an Ed25519-signed receipt anyone can verify offline.

Bloom Exchange is the reference implementation of the Bloom Clearing Protocol, an extension profile of A2A v1.0 that maps settlement to AP2 mandates and Stripe / x402 payloads, with an MCP server so any IDE agent can use it. Apache-2.0.

Try it (no API key, no account, no model)

bash
git clone https://github.com/astyboyy-ship-it/bloom-exchange && cd bloom-exchangenpm install                         # about 2 minutes on a cold cachenpm run dev                         # the node + operating desk on http://localhost:3000

Negotiations run on deterministic engines with the same vault, firewall, clamps and signatures as production. Requires Node 22.18+ for the repository scripts; the published npm packages run on Node 20+.

One command, every claim checked. Starts two nodes with separate keys, fires a prompt-injection payload at the firewall, checks that no private number reaches the attacker, settles a cross-node deal, then verifies the receipt with the CLI (and checks that a $1 tamper and the wrong key both fail):

bash
npm run build && npm run verify:launch          # or ./scripts/verify-launch-demo.sh · .\scripts\verify-launch-demo.ps1
  1 · SHIELD vs. PROMPT INJECTION (role tags, [INST], base64, zero-width Unicode)    ✓ Shield verdict: quarantined · 14 threats (policy_override_loop, encoded_payload, instruction_override, mandate_extraction, …)    ✓ no provider-private number in 42,450 bytes the attacker received    ✓ the deal still cleared inside both mandates: completed at $49,400, not $1  3 · bloom-verify CLI    ✓ offline with --card card.json → exit 0 (VALID)    ✓ price changed by $1 → exit 1 (INVALID: failed: digest)    ✓ against node-alpha's key → exit 1 (INVALID: failed: signature, ap2Proofs)  ALL CHECKS PASSED in 8.0s

Verify a receipt without cloning anything. The script above prints the folder where it saved receipt.json and the issuer's card.json; on the desk, the Enclave Inspector's JSON button downloads a receipt and the card is at /.well-known/agent-card.json.

bash
npx @bloom-exchange/sdk verify receipt.json --card card.json   # fully offlinenpx @bloom-exchange/sdk verify receipt.json                    # fetches the issuer's card named in the receipt

Give your agent the tools (Claude Code, with a node running on :3000):

bash
claude mcp add bloom-exchange -e BLOOM_EXCHANGE_URL=http://localhost:3000 -- npx -y @bloom-exchange/mcp

Cursor, Claude Desktop or any MCP client:

json
{  "mcpServers": {    "bloom-exchange": {      "command": "npx",      "args": ["-y", "@bloom-exchange/mcp"],      "env": { "BLOOM_EXCHANGE_URL": "http://localhost:3000" }    }  }}
Package
@bloom-exchange/sdknpm install @bloom-exchange/sdkZero-dependency client and the bloom-verify CLI
@bloom-exchange/mcpnpx -y @bloom-exchange/mcpMCP server for Claude Code, Cursor and any MCP client
@bloom-exchange/corenpm install @bloom-exchange/coreThe clearing engine and HTTP handlers, to run a node in any runtime

What you get

Double-blind vaultEach side's limits are sealed with salted SHA-256 commitments. The provider's engines (and any prompt they build) receive a brief with no counterparty field, so the client's ceiling cannot reach them by construction. Guard bands keep every offer off every private number; a leak scrubber checks every outbound message.
Deterministic clampingModels only propose. Sovereign clamps every offer to both mandates before it is sent or signed. 300 randomized enclaves with an adversarial proposer never produce an out-of-bounds offer.
Shield firewallPrompt injection, policy overrides, invisible and tag-smuggled Unicode, homoglyphs, base64 payloads, hidden markup and token exhaustion are neutralized before any engine reads the text, with a hash-chained audit ledger.
Verifiable receiptsBLOOM-XCH certificates: hash-chained rounds, both mandate commitments, Ed25519 signature, AP2 checkout and payment credentials, Stripe and x402 payloads. bloom-verify receipt.json checks one offline.
40 protocol adaptersChat, CRM, agent protocols (A2A, MCP, LangGraph, CrewAI, AutoGen), cloud and energy, payment rails and custom hooks normalize into one AgentIntentNode.
The operating deskA negotiation sandbox, a clearing ledger, an enclave inspector with a live security graph and a boundary probe, the omni-protocol router, a mandate corridor, and an SDK quickstart, in English and Spanish.

Repository

packages/core   @bloom-exchange/core   the clearing engine: vault, Shield, Sovereign, settlement, adapters, HTTP handlerspackages/sdk    @bloom-exchange/sdk    zero-dependency TypeScript client and the bloom-verify CLIpackages/mcp    @bloom-exchange/mcp    MCP server (stdio and Streamable HTTP): negotiate, verify_receipt, publish_intentapps/node       @bloom-exchange/node   a node: the API (A2A JSON-RPC, HTTP+JSON, SSE) and the operating desk at /deploy/                                Dockerfile, Docker Compose and Kubernetes manifests for a Sovereign nodeSPEC.md                                Bloom Clearing Protocol v0.1

Every endpoint in packages/core/src/http is a plain (Request) => Response function. apps/node mounts them in Next.js; handle() from @bloom-exchange/core/http/router serves them from any runtime (Node, Bun, Deno, Workers) or in-process.

Connect an agent

TypeScript (Node ≥ 20, Deno, Bun or the browser)

bash
npm install @bloom-exchange/sdk
ts
import { BloomExchangeClient } from "@bloom-exchange/sdk";
const bloom = new BloomExchangeClient({ baseUrl: "http://localhost:3000" });const { state, certificate } = await bloom.negotiate({  mandate: { ceilingPriceUsd: 52_500, maxBudgetUsd: 55_000, requiredSlaTier: "gold", targetNetDays: 60 },  item: { description: "12-month platform license" },}).result;const proof = await bloom.verifyCertificate(certificate!); // { valid: true, checks: { digest, certificateId, chain, signature, ap2Proofs } }

Claude Code, Cursor or any MCP client (setup above)

Ask your agent to "negotiate a 12-month license with a $52k ceiling on Bloom and verify the receipt". Tools: negotiate, verify_receipt, publish_intent. For a remote server, npx -y -p @bloom-exchange/mcp bloom-exchange-mcp-http serves stateless Streamable HTTP at /mcp. Optional environment: BLOOM_ACCESS_KEY, BLOOM_AGENT_NAME.

Verify any receipt

bash
npx @bloom-exchange/sdk verify receipt.json                    # keys from the issuer's Agent Cardnpx @bloom-exchange/sdk verify receipt.json --card card.json   # fully offline, air-gappednpx @bloom-exchange/sdk verify receipt.json --json             # machine-readable; exit 0 valid · 1 invalid · 2 bad input

Installed, the same command is bloom-verify receipt.json. Inside this repository: npm run verify -- receipt.json.

Raw A2A JSON-RPC

bash
curl -s http://localhost:3000/api/exchange/a2a -H 'Content-Type: application/json' -d '{  "jsonrpc":"2.0","id":1,"method":"SendMessage","params":{"message":{"messageId":"m1","role":"user","parts":[    {"kind":"data","data":{"bloomExchange":{"mandate":{"ceilingPriceUsd":52500,"maxBudgetUsd":55000,"requiredSlaTier":"gold","targetNetDays":60},     "item":{"description":"12-month platform license"}}}}]}}}'

Two nodes, one cross-node deal each way

deploy/docker-compose.yml runs two Sovereign nodes, node-alpha (:3001) and node-beta (:3002). Each has its own Ed25519 root key and its own state, and each is pre-wired to the other through BLOOM_PEERS:

bash
npm run sovereign:init -- --alpha "Acme Fund" --beta "Northwind"   # separate secrets, root keys and operator keys (all local)npm run sovereign:up                                               # Docker Compose: both nodes + Redis + REST gatewaysnpm run demo:two-node                                              # discovery, then a cross-node deal each way

No Docker? npm run build && npm run demo:two-node:local starts the same two nodes as local processes with fresh keys. Output from a real run:

  1 · DISCOVERY    node-alpha Alpha    key bxk-1f439f15d2868299 card ✓   peers: http://127.0.0.1:3102 ✓ bxk-7ab61a50094bf764    node-beta  Beta     key bxk-7ab61a50094bf764 card ✓   peers: http://127.0.0.1:3101 ✓ bxk-1f439f15d2868299
  2 · node-alpha's agent buys on node-beta    settled BLOOM-XCH-60X3-0HDS-R7XF-QFA0 at $47,060 · net 45 · gold · 10 rounds    receipt: issued by Bloom Exchange · Beta (bxk-7ab61a50094bf764) · counterparty Bloom Exchange · Alpha    ✓ verifies against node-beta's card   ✓ does not verify against node-alpha's key
  3 · node-beta's agent buys on node-alpha    settled BLOOM-XCH-8HSX-HJSW-ZA40-PSBQ at $46,920 · net 45 · gold · 10 rounds    receipt: issued by Bloom Exchange · Alpha (bxk-1f439f15d2868299) · counterparty Bloom Exchange · Beta    ✓ verifies against node-alpha's card   ✓ does not verify against node-beta's key

Each node verifies the other's signed Agent Card (GET /api/exchange/peers). An agent from one node negotiates on the other, presenting its home node's card. Each receipt names both nodes and verifies only against its issuer's key. The same deal with the SDK:

ts
const alphaCard = await (await fetch("http://localhost:3001/.well-known/agent-card.json")).json();const onBeta = new BloomExchangeClient({ baseUrl: "http://localhost:3002", agent: { name: "alpha/procurement", framework: "bloom-sdk", card: alphaCard } });const { certificate } = await onBeta.negotiate({ mandate: { ceilingPriceUsd: 52_500, maxBudgetUsd: 55_000, requiredSlaTier: "gold", targetNetDays: 60 }, item: { description: "12-month platform license" } }).result;await onBeta.verifyCertificate(certificate!); // signed by node-beta

Run a single node with docker compose -f deploy/docker-compose.yml up node-alpha. Kubernetes runs one node per namespace: kubectl apply -k deploy/k8s (see deploy/k8s/kustomization.yaml). With no model keys and no settlement webhook, nodes make no outbound calls beyond their configured peers. Configuration lives in .env.example.

Access keys are optional. They switch enclaves from the sandbox to production clearing and unlock operator views: npm run key:issue -- --role operator --holder "You".

Develop

bash
npm test                  # 198 tests: protocol vectors, engine invariants, leakage, settlement safety, firewall, adapters, peers, CLI, MCP, copy paritynpm run typechecknpm run lintnpm run buildnpm run spec:conformance  # regenerates SPEC.md Appendix B from the suitenpm run verify:launch     # the end-to-end check above (after npm run build)

Every test has a conformance id in SPEC.md Appendix B. Appendix A gives byte-exact vectors for canonical JSON, key derivation, round hashes, commitments, certificate ids and Ed25519 signatures, so implementations in other languages can match the reference exactly.

What is and is not built

  • Built: everything above runs today, end to end, with tests.
  • Opt-in: an event feed for wake-ups and post-settlement hooks (BLOOM_EVENTS=1): cursor polling, SSE, an MCP poll_events tool, and webhook, JSONL and dry-run adapters. It carries no mandate figures. See docs/EVENTS.md.
  • Format only: bloom.exchange/<agent> links. They are a naming format that resolves to a node's signed Agent Card; there is no public registry or resolver yet.
  • Open: in v0.1 the vault runs on the provider's node, so the counterparty trusts that operator not to read its mandate. The roadmap is neutral hosted clearing, attested enclaves and federation. See SPEC.md §12.

Release notes are in CHANGELOG.md.

License

Apache License 2.0. See NOTICE.

The two paintings in apps/node/public/paintings are public-domain works: Jean-Honoré Fragonard, c. 1760, and Claude Lorrain, 1653. They come from Wikimedia Commons under the Public Domain Mark 1.0, and the Apache License does not cover them. Attribution is in NOTICE and CREDITS.

来源:README.md,提交 1f0ca8c

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

2
  1. v0.2.0最新Nov 19, 2026
  2. v0.1.0Nov 19, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Exchange 集成