I see you’re an existing risk platform. Your repo mentions you’re focused on uniswap and balancer monitoring which are not relevant on Nervos currently. Could you provide links to your existing implementations and outline other networks you’re currently attempting to integrate with. I couldn’t find them via google search and could only find your other enquiries from the last 2 weeks about grants on other blockchains.
", "like_count": 0, "quote_count": 0 }, { "post_id": 24126, "post_number": 3, "topic_id": 10218, "topic_title": "[DIS] Quantir Risk Intelligence for CKB Ecosystem and Cross-Chain Monitoring", "topic_slug": "dis-quantir-risk-intelligence-for-ckb-ecosystem-and-cross-chain-monitoring", "author": "Ckroamer", "created_at": "2026-05-04T13:22:51.052000+00:00", "updated_at": "2026-05-04T13:22:51.052000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/dis-quantir-risk-intelligence-for-ckb-ecosystem-and-cross-chain-monitoring/10218/3", "content_text": "How do you identify RISKs you listed for CKB network? I guess there exists huge gap between UTXO-based blockchain and the Account-based ones, because I see your main experience is put on EVM-based blockchains, I hope you understand the difficulty of integration on CKB.", "content_html": "How do you identify RISKs you listed for CKB network? I guess there exists huge gap between UTXO-based blockchain and the Account-based ones, because I see your main experience is put on EVM-based blockchains, I hope you understand the difficulty of integration on CKB.
", "like_count": 0, "quote_count": 0 }, { "post_id": 24131, "post_number": 4, "topic_id": 10218, "topic_title": "[DIS] Quantir Risk Intelligence for CKB Ecosystem and Cross-Chain Monitoring", "topic_slug": "dis-quantir-risk-intelligence-for-ckb-ecosystem-and-cross-chain-monitoring", "author": "Quantir", "created_at": "2026-05-04T18:11:23.238000+00:00", "updated_at": "2026-05-04T18:11:23.238000+00:00", "reply_to_post_number": 2, "url": "https://talk.nervos.org/t/dis-quantir-risk-intelligence-for-ckb-ecosystem-and-cross-chain-monitoring/10218/4", "content_text": "The current public repository largely reflects an early stage of development, where the main focus was on Uniswap and basic balancing. At this point, the system has evolved significantly and goes beyond the scope of a single network or a specific DEX.\nThe architecture is now built around a protocol + network model, which allows us to scale the solution to different ecosystems without being tightly tied to a specific implementation (e.g., Uniswap). We are already working on integrating multiple networks (including L2) and expanding the set of data sources and risk factors.\nSome of our current work has not yet been published, as it is under active development and is being used in MVP/closed beta testing.\nWe plan to update the public repositories soon so that they better reflect the current state of the system and support for multi-network architecture.\nIf you are interested in specific integrations or architectural solutions, we would be happy to discuss them in more detail.", "content_html": "The current public repository largely reflects an early stage of development, where the main focus was on Uniswap and basic balancing. At this point, the system has evolved significantly and goes beyond the scope of a single network or a specific DEX.
\nThe architecture is now built around a protocol + network model, which allows us to scale the solution to different ecosystems without being tightly tied to a specific implementation (e.g., Uniswap). We are already working on integrating multiple networks (including L2) and expanding the set of data sources and risk factors.
\nSome of our current work has not yet been published, as it is under active development and is being used in MVP/closed beta testing.
\nWe plan to update the public repositories soon so that they better reflect the current state of the system and support for multi-network architecture.
\nIf you are interested in specific integrations or architectural solutions, we would be happy to discuss them in more detail.
", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10098, "title": "Spark Program | CKB-UGMP —— A Universal Spore/DOB Seamless Minting Infrastructure Prototype on CKB —— 基于 CKB 的通用 Spore/DOB 无感铸造基础设施原型", "slug": "spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob", "url": "https://talk.nervos.org/t/spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob/10098", "created_at": "2026-03-17T07:21:55.306000+00:00", "last_posted_at": "2026-05-04T14:14:07.555000+00:00", "category_id": 45, "tags": [ "In-Progress", "Spark-Program" ], "posters": [ "Original Poster, Most Recent Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster" ], "recent_posts": [ { "post_id": 24130, "post_number": 16, "topic_id": 10098, "topic_title": "Spark Program | CKB-UGMP —— A Universal Spore/DOB Seamless Minting Infrastructure Prototype on CKB —— 基于 CKB 的通用 Spore/DOB 无感铸造基础设施原型", "topic_slug": "spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob", "author": "HNO3Miracle", "created_at": "2026-05-04T14:14:07.555000+00:00", "updated_at": "2026-05-04T14:14:07.555000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob/10098/16", "content_text": "各位好，非常高兴和各位分享上周的工作。\n本周完成\n本周主要把第 1 周的上传占位推进成了可执行的 IPFS 上传流程。\n新增服务端上传接口：/api/uploads/pinata\n新增 Pinata 上传封装，避免在前端暴露 PINATA_JWT\n前端工作台支持选择图片、触发上传、展示上传状态\n上传成功后展示 CID 和 gateway URL\n初步生成 dob_metadata 草案，供后续 Spore 铸造交易使用\n补充 .env.example，明确 Pinata 相关环境变量\n当前状态\n当前 DApp 已经具备：\n钱包连接基础能力\n图片选择能力\nIPFS/Pinata 上传入口\n上传结果展示\nmetadata JSON 预览\nMint DOB 按钮仍然保持禁用，因为链上 createSpore 交易组装还没有进入本周范围。\n下周计划\n第 3 周计划正式开始进入 Spore 铸造交易层", "content_html": "各位好，非常高兴和各位分享上周的工作。
\n本周主要把第 1 周的上传占位推进成了可执行的 IPFS 上传流程。
\n新增服务端上传接口：/api/uploads/pinata
新增 Pinata 上传封装，避免在前端暴露 PINATA_JWT
前端工作台支持选择图片、触发上传、展示上传状态
\n上传成功后展示 CID 和 gateway URL
\n初步生成 dob_metadata 草案，供后续 Spore 铸造交易使用
补充 .env.example，明确 Pinata 相关环境变量
当前 DApp 已经具备：
\n钱包连接基础能力
\n图片选择能力
\nIPFS/Pinata 上传入口
\n上传结果展示
\nmetadata JSON 预览
\nMint DOB 按钮仍然保持禁用，因为链上 createSpore 交易组装还没有进入本周范围。
第 3 周计划正式开始进入 Spore 铸造交易层
", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 9845, "title": "[DIS] Fiber Link: A CKB Fiber-based Pay Layer (Tipping & Micropayments) for Communities", "slug": "dis-fiber-link-a-ckb-fiber-based-pay-layer-tipping-micropayments-for-communities", "url": "https://talk.nervos.org/t/dis-fiber-link-a-ckb-fiber-based-pay-layer-tipping-micropayments-for-communities/9845", "created_at": "2026-01-18T12:17:10.427000+00:00", "last_posted_at": "2026-05-04T13:38:07.281000+00:00", "category_id": 65, "tags": [], "posters": [ "Original Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster", "Most Recent Poster" ], "recent_posts": [ { "post_id": 24129, "post_number": 32, "topic_id": 9845, "topic_title": "[DIS] Fiber Link: A CKB Fiber-based Pay Layer (Tipping & Micropayments) for Communities", "topic_slug": "dis-fiber-link-a-ckb-fiber-based-pay-layer-tipping-micropayments-for-communities", "author": "Ckroamer", "created_at": "2026-05-04T13:38:07.281000+00:00", "updated_at": "2026-05-04T13:38:16.231000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/dis-fiber-link-a-ckb-fiber-based-pay-layer-tipping-micropayments-for-communities/9845/32", "content_text": "demo.fiberlink.me\n请问这个是 Demo 连接吗？目前是否已经暂时下架等待后续 Milestone 更新后再重新上架？", "content_html": "\n请问这个是 Demo 连接吗？目前是否已经暂时下架等待后续 Milestone 更新后再重新上架？
", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10193, "title": "CellScript - A DSL for Cell-Based Contracts", "slug": "cellscript-a-dsl-for-cell-based-contracts", "url": "https://talk.nervos.org/t/cellscript-a-dsl-for-cell-based-contracts/10193", "created_at": "2026-04-21T04:43:38.654000+00:00", "last_posted_at": "2026-05-04T13:37:50.240000+00:00", "category_id": 49, "tags": [ "CKB-VM", "CellScript", "DSL" ], "posters": [ "Original Poster, Most Recent Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster" ], "recent_posts": [ { "post_id": 24125, "post_number": 21, "topic_id": 10193, "topic_title": "CellScript - A DSL for Cell-Based Contracts", "topic_slug": "cellscript-a-dsl-for-cell-based-contracts", "author": "Ckroamer", "created_at": "2026-05-04T12:59:14.980000+00:00", "updated_at": "2026-05-04T12:59:14.980000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/cellscript-a-dsl-for-cell-based-contracts/10193/21", "content_text": "我记得以前也有个 CellScript 项目，最开始是一个在黑客松上产出的项目，也是类似于达到简化 CKB 合约编写难度的效果，但很可惜没有在维护了，看起来可能是一个同名的项目，可见英雄所见略同啊。\n对于这个项目我有些疑问：\n请问 .cell 文件如何确定合约 Entry 的？\n请问 CellScript 的编程自由度对比纯 Rust 合约有哪些限制？\n看起来 CellScript 是面向函数编程的？", "content_html": "我记得以前也有个 CellScript 项目，最开始是一个在黑客松上产出的项目，也是类似于达到简化 CKB 合约编写难度的效果，但很可惜没有在维护了，看起来可能是一个同名的项目，可见英雄所见略同啊。
\n对于这个项目我有些疑问：
\n.cell 文件如何确定合约 Entry 的？Hi Ckromer,
\nSpot on. When I started this ‘doppelganger’ CellScript project, I actually had not found the older cell-labs/cell-script project. I’ve summed up a bit and organised a table for comparison
| Topic | \nOlder cell-labs/cell-script | \nThis CellScript | \n
|---|---|---|
| Implementation | \nGo | \nRust | \n
| Style | \nMore like a general smart-contract language | \nCKB-first verifier DSL | \n
| Entry model | \nfunc main() | \nselected action or lock | \n
| Main focus | \nEasier contract programming | \nExplicit Cell transitions and verifier obligations | \n
| Core concepts | \nGeneral program logic | \nresource, shared, receipt, action, lock, witness, lock args, metadata | \n
To answer your questions,
\nFirstly, for .cell files, there are two different ‘entry’ concepts.
In Cell.toml:
entry = \"src/main.cell\"\nmeans the source entry file for the package.
\nThe actual contract entry compiled into a CKB artifact is an action or a lock. At this stage, I recommend selecting it explicitly:
\ncellc examples/nft.cell --target riscv64-elf --target-profile ckb --entry-action transfer\ncellc examples/nft.cell --target riscv64-elf --target-profile ckb --entry-lock nft_ownership\nThe compiler then generates a _cellscript_entry wrapper. That wrapper decodes witness data or Script.args according to the entry ABI, then dispatches to the selected action or lock.
There are fallback rules if no entry is specified: prefer action main, then the first zero-arg action, then the first action, then the first lock. But for real contract artifacts, explicit entry selection is much clearer.
Secondly, compared with pure Rust CKB contracts, CellScript is intentionally more constrained.
\nRust gives full low-level freedom: arbitrary syscalls, custom parsers, custom data structures, and manual transaction scanning. CellScript narrows that surface so the compiler can understand the contract shape. Cell state changes go through explicit primitives like consume, create, destroy, named outputs, read, protected, witness, and lock_args.
That trade-off is deliberate:
\n| Rust CKB contract | \nCellScript | \n
|---|---|
| Maximum freedom | \nMore structure | \n
| Manual tx parsing | \nExplicit Cell inputs / outputs | \n
| Custom low-level logic | \nCompiler-visible verifier obligations | \n
| Easy to express anything | \nEasier to audit specific Cell transitions | \n
| Developer controls everything | \nCompiler can reject more unsafe or ambiguous patterns | \n
So I would not so far describe CellScript as functional, at least not purely so:
\nIt supports ordinary imperative local code: let mut, loops, match, helper functions, and local vectors. But at the contract boundary it is deliberately verifier-oriented:
action describes a proposed Cell transition;lock describes a spend predicate;fn helpers are intentionally effect-free: they may compute values, validate data, transform local structs, or share reusable logic, but they cannot directly perform Cell effects such as consume, create, destroy, read, or protected. Those operations must remain visible inside action or lock bodies, so the compiler and auditors can clearly see where the contract touches Cells.The project is still at an early stage. The main thing proven so far is that the bundled business flows can compile and run smoothly on a local CKB devnet, with real transaction building and verifier execution. That is a useful milestone, but there is still plenty to improve.
\nSo please treat it as an early technical preview for now. If anyone is interested, I would be very happy to have people test & break it, review the design, and suggest how it could fit better into the CKB developer workflow.
", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10214, "title": "Spark Program | CKB-VM Sail Formal Verification — Proving CKB-VM RISC-V Instruction Equivalence via Sail Specification and Coq Theorem Prover / CKB-VM Sail 形式化验证 — 基于 Sail 规范与 Coq 定理证明器的 CKB-VM RISC-V 指令等价性证明", "slug": "spark-program-ckb-vm-sail-formal-verification-proving-ckb-vm-risc-v-instruction-equivalence-via-sail-specification-and-coq-theorem-prover-ckb-vm-sail-sail-coq-ckb-vm-risc-v", "url": "https://talk.nervos.org/t/spark-program-ckb-vm-sail-formal-verification-proving-ckb-vm-risc-v-instruction-equivalence-via-sail-specification-and-coq-theorem-prover-ckb-vm-sail-sail-coq-ckb-vm-risc-v/10214", "created_at": "2026-04-27T21:14:40.905000+00:00", "last_posted_at": "2026-05-04T13:33:27.644000+00:00", "category_id": 49, "tags": [ "Spark-Program" ], "posters": [ "Original Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster", "Most Recent Poster" ], "recent_posts": [ { "post_id": 24127, "post_number": 5, "topic_id": 10214, "topic_title": "Spark Program | CKB-VM Sail Formal Verification — Proving CKB-VM RISC-V Instruction Equivalence via Sail Specification and Coq Theorem Prover / CKB-VM Sail 形式化验证 — 基于 Sail 规范与 Coq 定理证明器的 CKB-VM RISC-V 指令等价性证明", "topic_slug": "spark-program-ckb-vm-sail-formal-verification-proving-ckb-vm-risc-v-instruction-equivalence-via-sail-specification-and-coq-theorem-prover-ckb-vm-sail-sail-coq-ckb-vm-risc-v", "author": "Ckroamer", "created_at": "2026-05-04T13:33:27.644000+00:00", "updated_at": "2026-05-04T13:33:27.644000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/spark-program-ckb-vm-sail-formal-verification-proving-ckb-vm-risc-v-instruction-equivalence-via-sail-specification-and-coq-theorem-prover-ckb-vm-sail-sail-coq-ckb-vm-risc-v/10214/5", "content_text": "形式化验证这个方向很有意思，但感觉可能存在不小的技术障碍，而且项目在交付后的实际可用性是否能得到充分保证也值得进一步探讨，不过始终都值得一试。", "content_html": "形式化验证这个方向很有意思，但感觉可能存在不小的技术障碍，而且项目在交付后的实际可用性是否能得到充分保证也值得进一步探讨，不过始终都值得一试。
", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10131, "title": "Spark Program | CKB Developer Onboarding Guide", "slug": "spark-program-ckb-developer-onboarding-guide", "url": "https://talk.nervos.org/t/spark-program-ckb-developer-onboarding-guide/10131", "created_at": "2026-03-26T08:49:26.745000+00:00", "last_posted_at": "2026-05-04T09:07:56.947000+00:00", "category_id": 49, "tags": [ "In-Progress", "Spark-Program" ], "posters": [ "Original Poster, Most Recent Poster", "Frequent Poster", "Frequent Poster" ], "recent_posts": [ { "post_id": 24124, "post_number": 16, "topic_id": 10131, "topic_title": "Spark Program | CKB Developer Onboarding Guide", "topic_slug": "spark-program-ckb-developer-onboarding-guide", "author": "Mateja3m", "created_at": "2026-05-04T09:07:56.947000+00:00", "updated_at": "2026-05-04T09:07:56.947000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/spark-program-ckb-developer-onboarding-guide/10131/16", "content_text": "Hi @xingtianchunyan\nBased on the progress and work completed so far, I would like to submit a mid-term funding request.\nIf there is any problem, please let me know.\nRequested amount: 40$ equivalent\nPayment preference: 50% CKB/50% USDI\nBest regards,\nMilan", "content_html": "\nBased on the progress and work completed so far, I would like to submit a mid-term funding request.
\nIf there is any problem, please let me know.
\nRequested amount: 40$ equivalent
\nPayment preference: 50% CKB/50% USDI
Best regards,
\nMilan