DEEP Connects Bold Ideas to Real World Change and build a better future together.

DEEP Connects Bold Ideas to Real World Change and build a better future together.

Coming Soon

Conduit: Unix-Philosophy CLI for ASI:Chain

chevron-icon
RFP Proposals
Top
chevron-icon
project-presentation-img

Conduit: Unix-Philosophy CLI for ASI:Chain

Expert Rating

n/a

Overview

Everyone else is building another IDE. I'm building grep for smart contracts. Five CLI tools: `conduit parse` dumps Rholang/MeTTa ASTs as JSON. `conduit verify` catches deadlocks and type errors. `conduit deploy` ships to DevNet and tracks BlockDAG finality. `conduit test` runs behavioral tests under CBC Casper conditions. `conduit ai` generates code via Singularity Compute. They pipe together. They run in CI/CD. They work in any editor. Like Foundry for Ethereum but built for process algebra and AI-native from the ground up. No GUI. No lock-in. Just tools that compose.

RFP Guidelines

Open for Proposals

An AI-native Development Environment for...

Ending on:

13 Feb. 2026

Days
Hours
Minutes
  • Type SingularityNET RFP
  • Total RFP Funding $50,000 USD
  • Proposals 21
  • Awarded Projects n/a

An AI-native Development Environment for the ASI:Chain

Proposal Submission (1 days left)
  • Type SingularityNET RFP
  • Total RFP Funding $50,000 USD
  • Proposals 21
  • Awarded Projects n/a
author-img
SingularityNET
Feb. 4, 2026

This RFP seeks proposals for the development of an AI-native Development Environment (IDE) that improves the efficiency and accessibility of blockchain application development for the ASI:Chain.

Proposal Description

Our Team

We build developer infrastructure. Shipped CLI toolchains for Ethereum-compatible chains. Built parsers, AST analyzers, and verification tools. Deep experience in Rust CLI design, Linux systems programming, and DevOps infrastructure. We know how to make tools developers actually use.

Company Name (if applicable)

Kestrel Engineering

Project details

Every other proposal here is building an IDE. That's the wrong answer.

 

Blockchain dev tools peaked with Foundry. Not because of its UI — it doesn't have one. Because it gave you `forge`, `cast`, `anvil`, and `chisel`. Small tools. Composable. You pipe them together. You script them. You run them in CI/CD. They work in any editor. grep didn't need a GUI. Neither does smart contract deployment.

 

ASI:Chain deserves the same philosophy. Not another web IDE that locks you into someone's idea of a workflow. A toolkit you compose yourself.

 

**conduit parse** reads Rholang or MeTTa source and spits out JSON ASTs. For Rholang: full process algebra parsing — parallel composition, sequential composition, name creation, pattern matching on channels, all contract forms. The AST preserves source locations for error reporting and annotates concurrent process structure. For MeTTa: atom expressions, type annotations, grounded atoms, Atomspace query patterns. Type inference results included. The JSON output is the interchange format for everything else. Pipe it to `jq` for custom queries. Feed it to your own scripts. Use it as input to codegen tools.

 

```

conduit parse contract.rho | jq '.processes[] | select(.type == "parallel")'

conduit parse agent.metta --format=graphviz | dot -Tpng > ast.png

conduit parse *.rho --check-syntax | conduit verify --strict

```

 

**conduit verify** does the hard work: type checking and concurrency analysis. Level 1 is types — MeTTa dependent types against Atomspace, Rholang behavioral types checking that processes use channels consistently. Level 2 is concurrency analysis for Rholang: deadlock detection (circular channel dependencies), race conditions (unguarded shared state), channel misuse (sending on a channel no one receives on). Level 3 is cross-language boundary checking — when MeTTa generates or calls Rholang, do the type assertions match the behavioral types? Are channel names consistent? Level 4 is property checking. You write assertions like "token balance never negative" or "governance vote can't be counted twice" in a lightweight spec language, and `conduit verify` checks them. Static where possible, counterexample generation where not. Output is structured JSON. CI/CD pipelines consume it. Terminals render it. Multi-contract projects aggregate it.

 

**conduit deploy** handles the full DevNet deployment cycle. Compiles Rholang contracts. Signs them. Submits to DevNet with configurable phlogiston parameters. Tracks BlockDAG position in real-time — where is this transaction in the DAG? Monitors CBC Casper finality — has it reached sufficient finality threshold? Outputs deployment receipts as JSON: transaction hash, block position, DAG depth, finality status, phlogiston consumed. Multi-contract deployment works with automatic dependency ordering based on channel references. Rollback support records state before deployment so you can abort cleanly.

 

Deployment is scriptable. A shell script can deploy ten contracts in sequence, check finality for each, and abort if any fails. Interactive IDE deployment panels can't do that.

 

```

conduit deploy token.rho --network devnet --wait-finality=0.95

conduit deploy governance.rho --network devnet --depends-on=token.rho

conduit deploy --manifest deploy.json --parallel --max-concurrent=3

```

 

**conduit test** is a testing framework for concurrent smart contracts under CBC Casper. Unit tests run isolated Rholang processes with mock channels. Integration tests run multi-contract interactions on a local DevNet node. Consensus tests run contract behavior under different BlockDAG orderings — simulating the non-determinism CBC Casper introduces. Fuzzing generates random inputs and channel message orderings to find edge cases. Coverage tracks which Rholang processes and MeTTa inference paths get exercised. Test results are JSON. They compose with CI/CD pipelines and reporting tools.

 

```

conduit test tests/ --consensus-scenarios=10 --fuzz-iterations=1000

conduit test --coverage | conduit report --format=html

```

 

**conduit ai** brings intelligence to the command line without an IDE. Code generation: `conduit ai generate "a token contract with transfer limits"` produces Rholang. Code review: `conduit ai review contract.rho` analyzes concurrency patterns and suggests improvements. Explanation: `conduit ai explain contract.rho:42-67` explains a specific section. Pattern search: `conduit ai patterns --category=governance` lists relevant patterns from the built-in library. Refactoring: `conduit ai refactor contract.rho --goal="reduce channel complexity"` suggests refactored code. All inference runs on Singularity Compute — keeping it in the ASI:Chain ecosystem. The AI understands Rholang process algebra and MeTTa Atomspace semantics. Not a generic LLM wrapper. A specialized code intelligence system.

 

```

conduit ai generate "auction contract with sealed bids" | conduit verify

conduit ai review *.rho --output=report.json

cat contract.rho | conduit ai explain --verbose

```

 

The real power is composition. Every tool reads and writes structured data — JSON, source code, AST. You build workflows that monolithic IDEs can't touch:

 

```

# Parse, verify, deploy in one pipeline

conduit parse contract.rho | conduit verify --strict && conduit deploy contract.rho

 

# AI-generate, verify, test

conduit ai generate "escrow contract" | conduit verify | conduit test --quick

 

# Batch verification of entire project

find . -name "*.rho" | xargs conduit verify --report=json | conduit report

 

# CI/CD integration

conduit test tests/ --ci --fail-on-warning && conduit deploy --manifest prod.json

```

 

This composability means Conduit integrates into any development environment. VS Code tasks. Neovim commands. Emacs compile mode. GitHub Actions. GitLab CI. Jenkins. Bare shell scripts. No lock-in.

 

Conduit connects to Atomspace/Hyperon for MeTTa operations. `conduit parse` and `conduit verify` query local or remote Atomspace instances for type resolution and knowledge base operations. `conduit ai` uses Atomspace as a knowledge graph for pattern retrieval and semantic code search.

 

`conduit deploy` and `conduit test` understand BlockDAG structure and CBC Casper consensus deeply. Deployment monitoring tracks DAG position, not just block confirmation. Testing simulates multiple DAG orderings to catch consensus-dependent bugs. This isn't surface-level integration. It's built into the core execution model.

 

ASI:Chain developers are technical. Command-line literate. Distributed across many editors and environments. A CLI toolkit meets them where they are. It composes into existing workflows. It scales to enterprise CI/CD. It runs on servers, in containers, in automated testing infrastructure. And it costs a fraction of the maintenance a custom IDE requires.

Open Source Licensing

MIT - Massachusetts Institute of Technology License

Background & Experience

I've been building CLI tools for 15 years. Rust compilers, Ethereum deployment managers, smart contract fuzzers. My team shipped a deployment toolkit for an EVM chain that 200+ developers use in production. We built parsers for domain-specific languages and a behavioral type checker for concurrent process calculus. We're experienced engineers coming from Linux systems programming, Foundry/Hardhat tooling, and DevOps infrastructure. We discovered ASI:Chain through a conference talk and saw an obvious gap: no one's building command-line tools. We're brand new to this ecosystem. But we know how to build tools that work.

Links and references

Team: https://david-kowalski.vercel.app

 

Proposal Video

Not Avaliable Yet

Check back later during the Feedback & Selection period for the RFP that is proposal is applied to.

  • Total Milestones

    3

  • Total Budget

    $47,000 USD

  • Last Updated

    13 Feb 2026

Milestone 1 - Core CLI: parse, verify, and deploy tools

Description

Build the three foundational CLI tools that form Conduit's core pipeline. `conduit parse` implements full Rholang and MeTTa parsers producing JSON ASTs with source location tracking, concurrent process structure annotations (Rholang), and type inference results (MeTTa). The parser handles error recovery so partial files produce partial ASTs instead of failures. `conduit verify` implements four verification levels: type checking (MeTTa dependent types, Rholang behavioral types), concurrency analysis (deadlock/race detection), cross-language boundary checking, and user-specified property assertions with counterexample generation. `conduit deploy` implements DevNet deployment with compilation, signing, submission, BlockDAG position tracking, CBC Casper finality monitoring, multi-contract dependency resolution, and structured JSON deployment receipts. All three tools follow Unix conventions: structured JSON output, standard exit codes, stdin/stdout piping, and composable flags. Each tool includes comprehensive --help documentation and man-page-style references.

Deliverables

1. `conduit parse` for Rholang: full process algebra parser with error recovery, source location tracking, concurrent structure annotations, and JSON AST output compatible with jq and standard JSON tools 2. `conduit parse` for MeTTa: atom expression parser with type annotations, grounded atom resolution, Atomspace binding info, and pattern match structure in JSON AST 3. `conduit verify` Level 1-2: MeTTa dependent type checking against Atomspace type system, and Rholang concurrency analysis detecting deadlocks, race conditions, and channel misuse 4. `conduit verify` Level 3-4: cross-language MeTTa-Rholang boundary type checking, and user-specified property assertions with counterexample generation for violated properties 5. `conduit deploy`: one-command DevNet deployment with compilation, signing, submission, BlockDAG position tracking, and CBC Casper finality monitoring with configurable thresholds 6. Multi-contract deployment with automatic dependency resolution via channel reference analysis, rollback support, and structured JSON deployment receipts 7. Unix-standard I/O: all tools support JSON stdin/stdout piping, standard exit codes, composable flags, and man-page-style --help 8. Test suite: 100+ test cases across all three tools covering parsing edge cases, verification accuracy, and deployment scenarios 9. All code published on GitHub under MIT license with CI/CD pipeline and contributor documentation

Budget

$10,000 USD

Success Criterion

1. `conduit parse` correctly parses 95%+ of Rholang programs from the official examples repository, with error recovery producing partial ASTs for incomplete code 2. `conduit parse` correctly parses 95%+ of MeTTa programs from the Hyperon examples, including grounded atom types and Atomspace query patterns 3. `conduit verify` detects 4 of 5 known deadlock patterns and 3 of 5 known race conditions in test Rholang programs 4. `conduit verify` cross-language check catches type mismatches and channel naming inconsistencies at the MeTTa-Rholang boundary 5. Property checking generates valid, minimal counterexamples for 3 of 5 violated properties in test contracts 6. `conduit deploy` successfully deploys and confirms 10 different contract types on DevNet with complete deployment receipts 7. All tools produce valid JSON output that pipes correctly through `jq`, and all exit codes follow Unix conventions 8. Full pipeline `parse | verify && deploy` completes in <30 seconds for standard contracts on DevNet 9. External developer composes a 3-step pipeline using only --help output, without reading additional documentation

Milestone 2 - Conduit test + conduit ai + Singularity Compute

Description

Build the testing framework and AI code intelligence tool. `conduit test` implements four testing modes: unit tests (isolated process testing with mock channels), integration tests (multi-contract interaction on local DevNet), consensus tests (behavioral testing under simulated CBC Casper conditions with multiple BlockDAG orderings), and fuzzing (random input and message ordering generation). Test results are structured JSON with coverage tracking across Rholang processes and MeTTa inference paths. `conduit ai` implements five capabilities: code generation from natural language, code review with concurrency analysis, code explanation for selected regions, pattern search from a curated library of 50+ Rholang/MeTTa patterns, and refactoring suggestions. All AI inference runs on Singularity Compute. The AI is specialized for Rholang process algebra and MeTTa Atomspace patterns — it understands channel semantics, concurrent composition, and behavioral types, not just surface syntax. Both tools integrate with the existing parse/verify/deploy pipeline through standard JSON I/O.

Deliverables

1. `conduit test` unit testing: Rholang process isolation with mock channel injection, assertion library, and structured JSON test results 2. `conduit test` integration testing: multi-contract interaction testing on local DevNet node with automatic setup and teardown 3. `conduit test` consensus testing: behavioral tests under 10+ simulated BlockDAG orderings with CBC Casper finality variation 4. `conduit test` fuzzing: random input and message ordering generation with configurable iterations, seed control, and minimized failing case output 5. Test coverage tracking: process-level Rholang coverage and inference-path-level MeTTa coverage with JSON and HTML report output 6. `conduit ai generate`: natural language to Rholang/MeTTa code generation with process-algebra-aware output 7. `conduit ai review`: automated code review identifying concurrency issues, channel misuse, and optimization opportunities 8. `conduit ai explain`: code section explanation with concurrency analysis; `conduit ai patterns`: searchable library of 50+ verified patterns 9. Singularity Compute integration: all AI inference runs on decentralized compute with local fallback for offline use 10. 50+ curated and verified patterns covering tokens, governance, oracles, agents, and multi-party coordination protocols

Budget

$33,000 USD

Success Criterion

1. Unit tests correctly isolate individual Rholang processes with mock channel injection, preventing cross-test state leakage 2. Integration tests catch 4 of 5 known multi-contract interaction bugs in a curated test suite of 15+ interaction scenarios 3. Consensus tests detect behavior differences across 3 of 5 known ordering-sensitive contracts when run with varied BlockDAG orderings 4. Fuzzer discovers at least 2 previously unknown edge cases in the test contract set with reproducible failing seeds 5. Coverage reports accurately track process-level and inference-path-level execution, outputting both JSON and human-readable HTML 6. AI generates compilable Rholang for 8 of 10 natural language descriptions, with correct concurrent process composition 7. AI review correctly identifies concurrency issues (deadlocks, races, channel misuse) in 4 of 5 test programs 8. Singularity Compute processes AI requests with <10 second average response time, with graceful local fallback 9. Complete pipeline `ai generate | verify | test` works end-to-end without manual intervention for 5 test scenarios

Milestone 3 - Integration, CI/CD Templates & Ecosystem Launch

Description

Polish the complete toolkit for production use, create CI/CD integration templates, conduct user testing, and launch to the ASI:Chain ecosystem. Integration work includes ensuring all five tools compose seamlessly through pipes and JSON, adding global configuration management (`conduit config`), and creating workspace-level project files (`conduit.toml`) for multi-contract project settings. CI/CD templates provide ready-to-use GitHub Actions, GitLab CI, and generic shell script configurations for automated build-verify-test-deploy pipelines. Editor integration provides configuration snippets for VS Code tasks, Neovim commands, and Emacs compile mode. User testing recruits 5+ ASI:Chain developers to use Conduit for real projects, collecting feedback on CLI ergonomics, error messages, and pipeline composition patterns. Documentation includes a comprehensive CLI reference, a pipeline cookbook with 20+ composition recipes, and a tutorial series for new developers. Production hardening covers error handling, offline mode for parse/verify, and graceful degradation when Singularity Compute or DevNet are unavailable.

Deliverables

1. Global configuration management: `conduit config` for API keys, network settings, defaults 2. Project files: `conduit.toml` for multi-contract project configuration and dependency specs 3. CI/CD templates: GitHub Actions, GitLab CI, and shell script configurations 4. Editor snippets: VS Code tasks.json, Neovim commands, Emacs compile-mode configurations 5. User testing report: feedback from 5+ ASI:Chain developers using Conduit for real projects 6. CLI reference documentation: all commands, flags, output formats, and exit codes 7. Pipeline cookbook: 20+ composition recipes for common development workflows 8. Tutorial series: 3 guided walkthroughs from installation to DevNet deployment 9. npm/cargo packages published for cross-platform installation 10. Production hardening: offline mode, graceful degradation, comprehensive error messages

Budget

$4,000 USD

Success Criterion

1. All five tools compose correctly through pipes for 20+ documented pipeline patterns 2. CI/CD templates run successfully in GitHub Actions and GitLab CI test environments 3. Editor integration works in VS Code, Neovim, and Emacs without custom configuration 4. 5 external developers successfully build and deploy contracts using Conduit pipelines 5. User satisfaction score of 4+/5 on CLI ergonomics and error message quality 6. Documentation enables a new developer to install and run a full pipeline within 20 minutes 7. Offline mode correctly handles parse and verify operations without network access 8. Cross-platform installation works on Linux, macOS, and Windows via npm/cargo 9. Total toolkit install size is under 50MB (keeping the Unix philosophy of small tools)

Join the Discussion (0)

Expert Ratings

Reviews & Ratings

    No Reviews Avaliable

    Check back later by refreshing the page.

Welcome to our website!

Nice to meet you! If you have any question about our services, feel free to contact us.