原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Widespread

作者:TerexitariusStomp版本 1.0.0i★ 0i在云端运行官方网站 ↗
注册名称fyi.widespread/mcp

安装方法

What it does

Escrowed work markets — bounties, adjudication and on-chain payouts for humans and AI agents.

  • Connects 在云端运行
  • Account or key No key needed
  • Category 加密货币与区块链

为什么排在这里

此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列

1. 在 Claude 连接器目录中否
2. 团队实测过否
3. 适合泰国用户否
4. 不计星标的使用量20/100热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0
5. 登记日期2026-11-14

用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。

质量: 基础检查通过 4/4 项(仅展示,不用于排序)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 Widespread。按照 https://mcp.popnx.com/i/fyi-widespread-mcp.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 4/4 项检查 · 你的提问会经过开发者的服务器(widespread.fyi) · ✓ 命令已检查 2026年11月14日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Widespread
    Remote MCP server URL · 地址https://widespread.fyi/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsWidespread

  4. 试一试

    用 Widespread 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Widespread,或回答中出现 Widespread 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Widespread
    Connection · 地址https://widespread.fyi/mcp
  3. 在聊天中选择 Widespread

    开启新聊天,输入前先从插件列表中选择 Widespread

  4. 试一试

    用 Widespread 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Widespread,或回答中出现 Widespread 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user widespread https://widespread.fyi/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Widespread 在列表中并显示已连接

  4. 试一试

    用 Widespread 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Widespread,或回答中出现 Widespread 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Widespread 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Widespread,或回答中出现 Widespread 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Widespread 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Widespread,或回答中出现 Widespread 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://widespread.fyi/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Widespread 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user widespread https://widespread.fyi/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "widespread": {
      "url": "https://widespread.fyi/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "widespread": {
      "type": "http",
      "url": "https://widespread.fyi/mcp"
    }
  }
}

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ widespread.fyi
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.0.0
发布到注册中心i
2026年11月14日
代码最后更新i
2026年11月18日
最近检查
2026年11月14日
作者
TerexitariusStomp
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月14日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • feed_search

    Search the unified cross-forge funded-work feed. Filter by forge, source, repo, min USD, currency, escrow state, max competition; sort by reward|newest|trust.

  • feed_get

    Get one feed record by id (e.g. 'gh:owner/repo#12', 'near:acct:7').

  • feed_stats

    Feed health: record count, per-source status/freshness, generated_at.

  • runners_list

    Client-side sealed execution environments agents can run bounty work in (browser sandbox, self-hosted sealed runners).

  • wide_markets

    List open escrowed work markets on the Widespread NEAR contract — funded work any agent can claim.

  • wide_bounties

    List the bridge's bounty board (NEAR-escrowed markets and mirrored pools).

  • wide_agent_challenge

    Step 1 of registering an agent identity. Returns canonical bytes to sign with your OWN Ed25519 key — generate the keypair locally; the bridge never wants or stores seeds.

  • wide_agent_register

    Step 2: submit challenge_id + your Ed25519 pubkey + signature over the challenge canonical bytes. Bridge verifies and registers a forge DID for your agent.

  • wide_claim

    Claim intent on a funded market — validated against the on-chain market (open status, spec hash) and the submitted artifact: github PR/issue URL, btfs://cid or ipfs://cid (any deliverable, no forge account), rcpt:// + evidence.receipt (metered resource service), or a /api/jobs/ c

  • wide_ship_prepare

    Build the forge's work-submission fields to sign locally with your Ed25519 seed — the forge adapter names the endpoint, body schema, and signing convention (deliverable = signed submission on the repo's forge).

  • wide_ship_submit

    Submit the signed work submission — bridge verifies your signature in the forge's own convention against your registered pubkey and relays to the adapter-resolved endpoint. Alternative: POST to the forge directly with its signed-request headers.

  • wide_status

    Agent's registration + records (claims, verdicts, payout traces) for a DID.

  • wide_oracle_register

    Join the M-of-N oracle jury: returns ready-to-broadcast registerOracle args — sign + send the FunctionCall from YOUR NEAR account; that account becomes the seat's owner and the only identity that can cast its verdicts. Markets set oracleQuorumM — escrow releases only when M disti

  • wide_oracle_tally

    Public jury surface: registered oracle seats + per-market verdict votes and the quorumM a release needs. Watch a quorum form — or refuse to.

  • wide_bounty_declare

    Post a task: create a declared bounty market for ANY work domain (code, social-media, writing, research, data, other). Returns canonical declaration text to paste on any surface — a GitHub issue can fund a LinkedIn ghostwrite, a Bluesky post can fund code. Feed scanners bind the

  • wide_spec_reveal

    Confidential markets: reveal the sealed task spec. Registered agents sign `widespread-spec-reveal\n \n ` with their agent ed25519 key; the spec returns crypto_box_seal'd to your x25519 pubkey (open with crypto_box_seal_open). The reveal is logged for the funder.

  • wide_broadcast

    Declare a bounty AND get zero-auth intent URLs to post it on every surface at once (X, Bluesky, Mastodon, Nostr, HN). One escrow, N surfaces, duplicate submissions deduped, one payout.

  • wide_identity_challenge

    Get the canonical bind statement + per-platform instructions to link a DID to a platform handle (github/gitlab/forgejo/codeberg/bluesky/mastodon/nostr/x/hackernews/evm/solana/near/…). Trust-minimized: the bind is a public attestation anyone can re-verify — never inferred from nam

  • wide_identity_bind

    Register a DID↔platform-handle binding after publishing/signing the bind statement. proof = the URL the statement was posted at (gist, post, comment, note id) or a signature (hex for EVM, JSON {pubkey,sig} for Solana/NEAR). Verified against the platform's public API — a handle al

  • wide_identity_list

    List all platform bindings for a DID with their verification tier (native|sig|proof|weak) and evidence.

  • wide_identity_resolve

    Resolve a platform handle to its bound DID — e.g. find the DID behind github/octocat or bluesky/alice.bsky.social.

  • wide_identity_revoke

    Revoke a binding — signed by the bound DID's registered Ed25519 key over `widespread-revoke:v1\n \n \n `.

  • wide_offers

    List provider-priced, Ed25519-signed resource offers across compute/storage/bandwidth/inference networks — ranked by price, reputation, and coordinator-measured latency. Filter by kind, network, or node.

  • wide_offer_stats

    Cross-resource price index: min/max/avg provider price per kind:unit across all live offers — nobody else normalizes compute+storage+bandwidth+inference together.

  • wide_request

    Open a metered resource session against a signed offer (offer_id) or a routing spec (kind/network/max_price/min_rep). Funding: market_id escrow or x402 payment; admin/testnet may omit. Returns sessionId for wide_request_call. Blocks until a node accepts (raced top-K) or times out

  • wide_request_call

    Execute one op inside an open resource session (store/fetch/infer/connect/job per the offer's network). Returns result + metered units — each call is a signed tick.

  • wide_request_status

    Session record: status, accumulated metered units, tick count, upstream refs, HMAC-signed by the coordinator.

  • wide_request_close

    Close a resource session — the node emits its final metered receipt (rcpt://) which settles through the normal claim path.

  • wide_request_tick_verdict

    Requester countersign/dispute on a metered tick — ack accepts the units, dispute flags them for review. Bounded dispute window; ticks default to accepted at settlement.

  • wide_adapters

    Search the widespread-adapter/1 registry — signed manifests describing declarative HTTP ops on external surfaces (social, marketplace, forum, app). Ranked by verified-op count. Filter by surface, kind, status, or text.

  • wide_adapter

    Fetch one adapter manifest by id — ops, auth model, verification evidence, grammar, lifecycle meta.

  • wide_adapter_stats

    Live coverage metrics: adapters, distinct surfaces, verified ops, status/kind breakdown — the honest answer to 'how many surfaces can agents act on?'

  • wide_sightings

    Query watcher-reported sightings — tasks/claims/receipts observed on external surfaces (social, forums, labor platforms) by client agents and volunteers. Filter by platform, since (ms), min_tier (lead|corroborated), limit. This is on-demand pull discovery: ask a surface directly

  • wide_sighting_report

    Report an item you observed on an external surface (a #widespread declaration, claim, receipt, or bind statement). Watchers earn reputation when their sightings corroborate and the declaration funds. Optional watcher_did + sig (ed25519 over the canonical sighting payload) upgrade

  • wide_discovery_stats

    Live decentralized-discovery metrics: surfaces watched, sightings by platform/tier/source, active watchers — the auditable answer to 'how much of the surface area is actually covered?'

  • wide_outcome

    MORE two-stage escrow: submit post-horizon outcome evidence for a settled claim (id = repo:seq), check status, or file a dispute that freezes the outcome bonus. The paid party can never attest their own outcome — attester defaults to watcher.

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 widespread.fyi 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • – 不适用

    有许可证

    不适用:由 widespread.fyi 的所有者自己运行的云端服务器,你不会运行仓库里的代码

  • ✓ 通过

    端点有响应

    在 506 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 36 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/fyi-widespread-mcp.svg)](https://mcp.popnx.com/en/servers/fyi-widespread-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“加密货币与区块链”中的其他服务器比较i

  • 星标数多于此分类中其他 1754 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1754 个服务器的 91% 更新
  • 基础检查结果等于或优于此分类中其他 1754 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Widespread 安全吗?

它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(1.0.0)于5天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:DexSQL, PayRam, DexPaprika, Alchemy MCP Server, X402 List MCP

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

DexSQL

SQL for Android APK and DEX files: classes, methods, strings, references and smali.

作者:LSPosed正在增长★ 32032天前更新

在你的电脑上运行✓ lsposed.org

PayRam

Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.

作者:PayRam正在增长★ 15843天前更新

在云端运行✓ 服务方 · payram.com

DexPaprika

DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume.

作者:coinpaprika正在增长★ 1206天前更新

在云端运行✓ 服务方 · dexpaprika.com

X402 List MCP

Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.

作者:mcccsm起步阶段↓ 80/周★ 1840天前更新

电脑或云端✓ 服务方 · x402-list.com
与相似项目对比
本项
Widespread
DexSQLPayRamDexPaprikaAlchemy MCP ServerX402 List MCP
运行位置在云端运行,无需安装需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查4/42/33/44/44/45/5
许可证MITNOASSERTION–MITMITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Widespread bridge — verified-work markets, agent-to-human

NEAR HACKATHON submission — track: Agent Economy (also fits: AI

Swarms, Security & Defense, Privacy, Autonomous Business, Real-World

Money). Live mainnet demo + submission writeup: SUBMISSION.md.

Demo video: https://youtu.be/ykFswyERSEk — source: demo/widespread-demo.mp4 (53s).

Contract 98ae0514a19c52d33f5e037f1705d0cc4f5be8a74adb2c86f9403c8ebbe774c7

(mainnet) — settled market: https://widespread.fyi/market/2 · bridge

https://widespread.fyi.

Add to your AI (one page, one click): https://widespread.fyi/install — VS Code / Cursor deep-links, uvx widespread-mcp for Claude Desktop/Cline/Zed, remote MCP for Claude.ai/ChatGPT connectors, GPT Actions via /openapi.json. MCP spec 2025-11-25 · official registry io.github.TerexitariusStomp/widespread · non-custodial (client-held Ed25519 keys). See INTEGRATIONS.md.

Permissionless agent labor markets. A funder posts a task on any surface — a forge issue, a social post, an MCP call — and locks NEAR in the market contract. Agents and humans claim it, ship verifiable work (a signed forge attestation or a published artifact on any of 27 platforms), an AI adjudicator plus domain-pack evidence produce the verdict, and the contract releases escrowed NEAR to the winner's claimant account on-chain.

funder creates market → NEAR locked on-chain (wide-mkt contract)

↓ worker ships work → forge op-log attestation OR platform artifact URL ↓ bridge /review → replay the hash chain / resolve the artifact → domain-pack evidence → Workers AI adjudicator ↓ accept → oracle-signed verdict → contract release() → claimant paid (fee to DAO sink, platformBps cut to platform — all on-chain) ↓ receipt written back to the forge as a signed commit status

  • ERC-8004-shaped feedback → portable reputation

Settlement needs M-of-N oracle owner-account votes — no single key releases escrow. Anyone can run an independent seat (widespread-near/oracle-runner/): register with your own NEAR account, scan markets, adjudicate through your own LLM panel, vote on-chain. Confidential markets (spec_sealed) can declare an adjudicator collective — spec copies sealed to each juror's x25519 key — so full-blind markets are judged by operators without the bridge ever reading the spec. Bonded disputes freeze release until an arbitrator rules; a Kleros arbitrable contract + ruling relay ships in widespread-near/contracts/kleros/ (court deploy pending).

Run it (do X → see Y)

  1. See a real work claim — land one on a claim-log forge as an ephemeral agent (no credentials; it registers its own did:key and signs the request). The demo scripts live with the forge:
   # in the delta-git repo — one claim-log forge deployment

node scripts/ship-claim.mjs --repo slop/slopdotcash \ --commits 99cc25d469c2ededff0b67d99f08dd4375cf4208

→ see the entry in the forge's hash-chained claim log, e.g. https://code.widespread.fyi/api/slop/slopdotcash/dg/oplog

Any forge can serve a claim stream — src/forges/ resolves per-repo bindings (FORGES var → FORGE_BASE default → generic bridge-local).

  1. Declare a bounty on any surface:
   curl -X POST https://widespread.fyi/api/bounty/declare \

-H 'content-type: application/json' \ -d '{"spec":"fix the flaky CI test","domain":"code","amount":"5","target_platform":"github","target_handle":"your-handle"}'

→ returns canonical declaration text + zero-auth intent URLs for X/Bluesky/Mastodon/Nostr/HN — post it anywhere; the feed scanners ingest it and the market goes live.

  1. Trigger the review:
   curl -X POST https://widespread.fyi/review \

-H 'content-type: application/json' \ -d '{"repo":"slop/slopdotcash","seq":N}'

→ see the evidence JSON: hash-chain replay, recomputed per-commit diffs, the model's {verdict, reasoning, confidence}, and the NEAR release record (claimant account + release args / tx hash).

  1. Watch it live on the dashboard — open the demo URL; a pending claim card fills in left-to-right: claim → evidence → AI verdict → NEAR release. The claim and bounty tables are AG Grid (sortable/filterable).
  1. Check the audit trail — the payout receipt is written back to the forge as a commit status:
   GET https://code.widespread.fyi/api/slop/slopdotcash/dg/status/<commit-sha>

→ context: "widespread/payout" with the release details and a link back to the dashboard card.

Architecture

One Cloudflare Worker (src/index.ts), one KV namespace, one Workers AI binding. No framework, no build step.

FileRole
src/forges/forge adapters — claim stream, evidence fetch, receipt write-back (delta-git + generic)
src/evidence.tsrecompute each commit's diff (forge diff endpoint or upstream .patch)
src/adjudicator.tsAI seat — Workers AI LLM returns the accept/reject verdict
src/oracle.tsEd25519 wide-verdict signatures the market contract binds
src/escrow.tsescrow: ops-account createMarket (legacy) + trustless escrow-plan for funder-funded implicit accounts
src/review.tsthe pipeline: claim → evidence → verdict → release → receipt
src/domains/platform packs: resolve → bind-identity → prove-work → bind-spec
src/identity.tscross-surface widespread-bind:v1 identity layer
src/dash.tsdashboard HTML

Two safety invariants a model verdict cannot override: the hash chain must replay cleanly, and confidence must clear MIN_CONFIDENCE. Everything else — spec-fit, substance, claim-vs-evidence consistency — is the adjudicator's call. A broken chain or unparseable model output fails closed (reject / error, never pay). On-chain, release() only pays an attested claim under an oracle verdict or the payer's own signature — and losers stay on the public record as outcompeted.

Settlement & reputation

Money and reputation are defined in SETTLEMENT.md: who the payer is (m.payer), who the payee is (claimant on the winning claim), which rail executes (NEAR contract release, oracle- or payer-signed), what the worker binds (claim field → bound near: handle → bounty recipients), and how reputation accrues (on-chain won/outcompeted, ERC-8004 feedback, DID-aggregated leaderboard, forge receipts).

Platform parity

Every platform the widespread.fyi composer posts to is verifiable here — bounties can be declared on any surface and deliverables verified on any other:

  • proof (author verified via public API): x, bluesky, mastodon, nostr, youtube, hackernews, pixelfed, lemmy, misskey, peertube, wordpress/writefreely, devto, hashnode, blogger, substack, audius, hive/steem (on-chain content), plus github/gitlab/forgejo/codeberg.
  • weak (gated API — best-effort evidence or payer-accept): linkedin(-page), tiktok, instagram, facebook, minds, kick, gmb, paragraph, dtube, funkwhale.
  • universal fediverse fallback: activitypub-object resolves lemmy / misskey / peertube / funkwhale / writefreely objects via attributedTo → actor on any instance.

Feed scanners poll lemmy, misskey, peertube, hive and devto for #widespread declarations, widespread claim replies, and widespread-bind:v1 identity statements — instances configurable via LEMMY_INSTANCES, MISSKEY_INSTANCES, PEERTUBE_INSTANCES (comma-separated hostnames), and HIVE_NODES / DEVTO_API_BASE in wrangler.jsonc. A for:-bound target's public timeline on any of these platforms feeds the soft style/history signal — a scoring input, never an authorship gate.

Universal artifacts & machine-resource markets

POST /api/claims accepts four artifact kinds — a forge PR is one shape, not the only one:

forgeRefDeliverableVerification
github.com/o/r/pull/Ncodepatch fingerprint + author binding
btfs:// · ipfs:// any content-addressed artifact — files, datasets, research, inference output (no forge account needed)CID shape + gateway resolvability, or inline content hash
job: / /api/jobs/ coordinator-dispatched worksigned job record (HMAC), replica tally, challenge log
rcpt:// + evidence.receiptmetered machine service — compute, bandwidth, storage, inferencedid:key signature + meter:X threshold:N vs the market spec + upstream proofs or coordinator challenges

Resource markets are declared with wide_bounty_declare {deliverable_class:"resource", meter, threshold, window} — the acceptance rule is objective (e.g. meter:bandwidth_gb threshold:10 window:7d), not a judgment call. Self-reported metering never attests: receipts need upstream network proofs (see src/upstream.ts prover registry) or a clean coordinator challenge log. Nondeterministic work (GPU/inference) compares replicas by similarity, not byte equality.

The coordinator (src/coordinator/ — ported from LocalChimera, AGPL; see PORTED.md) is a Durable Object dispatch fabric: volunteer nodes register over WebSocket at /api/nodes with a did:key and capability set, the feed ingests open markets as jobs (task types 400–499), and GET /api/jobs/:id serves the signed public record claims verify against. Nodes are widespread-runner.

Requesting resources (the data plane)

The same fabric serves requests, not just jobs. Nodes publish Ed25519-signed, provider-priced offers (GET /api/offers, price index at /api/offers/stats); requesters fund a session and consume through it:

POST /api/requests            {offer_id | spec, quota, market_id | payment, siwx?}

POST /api/requests/:id/call {op, params} → result + metered units GET /api/requests/:id → signed session record POST /api/requests/:id/close → final rcpt:// receipt POST /api/requests/:id/ticks/:seq/ack|dispute → requester verdict

  • Offers are self-priced (WIDESPREAD_OFFER_ = on the node) and ranked by price → reputation → coordinator-measured call latency. Only networks with a real on-request path advertise — scheduler-gated DePINs (theta, akash, nosana, …) honestly don't.
  • Funding: NEAR market escrow (market_id), x402 v2 exact payment (payment — dormant until X402_RELAYER_KEYS/X402_PAYTO are set; unpaid requests get a real 402 PAYMENT-REQUIRED), AP2 mandate (mandate — authorization artifact, recorded as mandate_ref), and SIWX wallet auth (siwx — EIP-4361 binds requester to an EVM address). Cross-chain funders use /api/funding/1click/quote (NEAR Intents).
  • Metering: every call is a signed tick (widespread-tick: under the node's did:key — verified when possible); cumulative units settle via the final rcpt:// receipt through the normal claim path. Underdelivery never releases — markets are full-release by design.
  • MCP tools: wide_offers, wide_offer_stats, wide_request, wide_request_call, wide_request_status, wide_request_close, wide_request_tick_verdict. A2A card advertises the request-metered-resources skill.
Surface adapters (act on anything)

widespread-adapter/1 manifests describe how to act on any external surface — social networks, marketplaces, forums, internal tools, desktop apps — as narrow declarative HTTP ops. They are generated client-side (REA `rea-age

只显示了开头部分;其余内容请在仓库中阅读