feat(chainlink): CCIP cross-chain funding and payout, and CRE-driven escrow release
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
调研方向
Start by reading the proposal_service._release_all_escrow flow and the linked dependency issues #2 and #3. Check CCIP lane and token availability for candidate testnets, along with CRE access and pricing. Done means a decision record under docs/ and either a testnet funding demo or a documented feasibility reason; file follow-up issues if the approach is adopted.
由索引模型根据 Issue 内容生成。
描述
Summary
Explore using Chainlink CCIP to accept proposal funding on one chain and pay out on another, and Chainlink's runtime environment (CRE) to release escrow after a job result hash is verified.
Motivation
Funders and workers may sit on different chains. CCIP can move value across them, and a verified-delivery release removes the platform as the sole trigger for payouts.
Current state in this repo
- Proposal escrow release is triggered by the backend (
proposal_service._release_all_escrow).
Proposal
- Spike: choose two registry testnet chains with CCIP support and prototype token transfer plus message (funding on A, accounting on B).
- Spike: a CRE workflow that reads a result hash from an authenticated backend endpoint and authorises an escrow release.
- Decision record covering trust assumptions, costs and failure handling.
Acceptance criteria
- Written decision record under
docs/. - A testnet demo of a cross-chain funding flow, or a documented reason it is not feasible yet.
- If adopted, follow-up implementation issues are filed.
Out of scope
- Production deployment.
Dependencies
- #2
- #3
Verify before implementing
- CCIP lane availability and supported tokens between the chosen testnets.
- CRE availability, pricing and access requirements.
References
- Chainlink CCIP docs: https://docs.chain.link/ccip
Part of ##1. Ground rules for all issues in this roadmap are listed there (testnet-first, no secrets in the repo, chain logic behind the registry, tests and docs with every PR).
- 主要语言
- Python
- 星标
- 2
- 派生
- 4
- 平均合并
- 5 小时 19 分钟
- 30 天内合并 PR
- 11
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
QMeshPy/distributed-quantum 的其他 Issue
-
enhancement good first issue helia storage tier-1
难度 2/5 1-3 小时 新手友好度 78/100
QMeshPy/distributed-quantum#53 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 4/5 3-5 天 新手友好度 55/100
QMeshPy/distributed-quantum#78 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 3/5 1-2 天 新手友好度 66/100
QMeshPy/distributed-quantum#77 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments tier-2
难度 5/5 一周以上 新手友好度 35/100
QMeshPy/distributed-quantum#76 ·
维护者通常 1 天内回复
-
documentation good first issue kubo storage tier-1
难度 2/5 1-3 小时 新手友好度 42/100
QMeshPy/distributed-quantum#75 ·
维护者通常 1 天内回复
查看 QMeshPy/distributed-quantum 的全部 Issue
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 88/100
fossasia/visdom-dev#69 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
BUG: PROD: v1.3.0-beta Onboarding Profile Picture Misaligns When Name Validation Error Appears可能已有人在做 @RitikaSen27 今天认领。 未关闭bug good first issue
难度 2/5 1-3 小时 新手友好度 82/100
AOSSIE-Org/PictoPy#1647 · 2 条评论 ·
维护者通常 2 天内回复
-
[oblt-aw][autodoc] Update workflow docs for gh-aw v0.92.5 and detector permission scope可能已有人在做 @github-actions 今天认领。 未关闭
难度 1/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复