See the stars

ChainPilot Specification

Home / ChainPilot / ChainPilot Specification

ChainPilot

The AI Builder for Solana Protocols


Overview

ChainPilot is an open-source, AI-powered development platform designed to simplify the creation, testing, security verification, deployment, and ongoing maintenance of Solana blockchain protocols and decentralized applications. It enables developers to describe application requirements in natural language and transform them into structured protocol designs, smart contracts, and application components.

ChainPilot combines AI-assisted development with security-focused engineering, automated testing, deployment controls, and upgrade lifecycle management. Its modular architecture provides a comprehensive set of core capabilities while allowing optional plugins to extend functionality for specialized protocols, development workflows, security tools, and integrations.

The platform follows a human-in-the-loop approach. AI-generated code, recommendations, security assessments, deployments, and upgrades remain subject to review and configurable authorization controls. AI suggestions do not constitute permission to execute consequential actions.

Goals and Principles

  • Simplify Solana protocol and decentralized application development.
  • Reduce the expertise required to create and maintain blockchain applications.
  • Integrate security analysis and automated testing throughout the development lifecycle.
  • Support verifiable, controlled deployments and upgrades.
  • Preserve developer ownership and control over source code, credentials, administrative permissions, and deployment decisions.
  • Provide transparent records of generated artifacts, test results, security findings, and release decisions.
  • Support extensibility through optional modules and plugins.
  • Avoid presenting automated security assessments as guarantees of correctness or safety.
  • Enable local development, self-hosted deployments, and configurable AI provider integrations.

Core Modules

Natural Language Protocol Builder

  • Translate natural-language requirements into structured protocol specifications.
  • Identify functional requirements, user roles, account relationships, transaction flows, and authorization rules.
  • Ask clarifying questions when requirements are incomplete, contradictory, or ambiguous.
  • Generate protocol architecture proposals for developer review.
  • Identify dependencies, assumptions, trust boundaries, and security-sensitive operations.
  • Maintain traceability between original requirements, design decisions, generated code, and tests.
  • Support iterative refinement without silently changing previously approved requirements.
  • Produce implementation plans and acceptance criteria before generating code.

AI Smart Contract Generation

  • Generate Solana program logic from approved protocol specifications.
  • Support account definitions, instruction handlers, validation rules, state transitions, and error handling.
  • Generate reusable contract components and protocol-specific templates.
  • Produce explanations of generated logic, account relationships, and security assumptions.
  • Support code editing through natural-language instructions and conventional developer workflows.
  • Identify incomplete implementations, placeholder logic, and unresolved requirements.
  • Regenerate selected components while preserving unrelated developer changes.
  • Track the relationship between generated code and the requirements that informed it.
  • Require review and validation before generated code is considered ready for release.

AI Development Workspace

  • Provide a unified workspace for protocol planning, code generation, editing, testing, and documentation.
  • Organize projects, program versions, requirements, test results, and security findings.
  • Support contextual AI assistance for explaining code, diagnosing failures, and proposing improvements.
  • Display proposed changes before applying them.
  • Provide change comparisons and preserve recoverable versions of modified files.
  • Allow developers to accept, reject, or revise AI-generated changes individually.
  • Maintain project-specific instructions and approved design decisions.
  • Support collaboration through review workflows, comments, and configurable access permissions.

Security Analysis and Verification

  • Analyze smart contracts for common vulnerability patterns and unsafe assumptions.
  • Validate account ownership, signer requirements, account relationships, and authorization boundaries.
  • Inspect instruction handling, state transitions, arithmetic operations, token interactions, and cross-program invocations.
  • Identify missing validation, unintended privilege escalation, unsafe account substitutions, and inconsistent state handling.
  • Examine dependency risks and changes in external program assumptions.
  • Support static analysis, fuzz testing, property-based testing, and adversarial transaction simulation.
  • Generate tests for access controls, invalid inputs, boundary conditions, and protocol invariants.
  • Analyze reentrancy-like interaction risks where applicable to Solana execution and cross-program invocation behavior.
  • Produce prioritized findings with evidence, affected components, severity estimates, and recommended remediation.
  • Distinguish confirmed findings from potential issues and unverified assumptions.
  • Generate security reports suitable for developer review and independent assessment.
  • Support repeatable verification runs and comparisons between program versions.

Security scores and AI-generated assessments must not be treated as proof that a program is secure. Critical findings and unresolved assumptions must remain visible in release decisions.

Automated Testing and Simulation

  • Generate unit, integration, property-based, and regression tests from approved requirements.
  • Simulate instructions and transaction sequences before deployment.
  • Validate expected account state changes and transaction outcomes.
  • Test successful operations, rejected transactions, unauthorized access, malformed inputs, and failure conditions.
  • Support local environments and Solana Devnet testing workflows.
  • Analyze compute-unit consumption, transaction behavior, and resource constraints.
  • Evaluate protocol invariants across sequences of transactions.
  • Support reproducible test configurations and retained test results.
  • Compare test outcomes across code changes and program versions.
  • Prevent failed mandatory checks from being silently treated as successful.
  • Generate reports covering test coverage, failures, unresolved risks, and recommended next steps.

Protocol Economics and Risk Analysis

  • Model protocol fees, rewards, incentives, token flows, and other economic mechanisms.
  • Simulate selected user behaviors and transaction scenarios.
  • Identify potential economic exploits, unintended incentives, and adverse edge cases.
  • Analyze assumptions about liquidity, supply, distribution, and protocol participation where applicable.
  • Support sensitivity analysis for configurable economic parameters.
  • Explain model limitations and distinguish simulated outcomes from predictions.
  • Require explicit review of economic assumptions before they are incorporated into production decisions.

Deployment and Release Management

  • Prepare deployment plans for supported Solana environments.
  • Support local development, Devnet testing, and controlled Mainnet release workflows.
  • Validate required configuration, program identifiers, deployment permissions, and release artifacts.
  • Run configurable testing and security checks before deployment.
  • Present deployment details, expected effects, and outstanding risks for review.
  • Support wallet-based signing and authorized deployment procedures.
  • Integrate with continuous integration and continuous delivery workflows.
  • Maintain release records, artifact identifiers, verification results, and deployment outcomes.
  • Provide deployment previews and clear confirmation steps for consequential operations.
  • Prevent AI agents from bypassing configured approval requirements.
  • Support recovery planning and documented procedures for failed or interrupted releases.

Mainnet deployments must require explicit authorization from an appropriately privileged human or an explicitly configured governance process. Production signing credentials must not be exposed to unrestricted AI execution.

Upgrade Lifecycle Management

  • Track program versions, release artifacts, configuration changes, and deployed versions.
  • Analyze proposed changes for compatibility, regressions, and potential security implications.
  • Identify breaking changes to instructions, account layouts, state assumptions, and client integrations.
  • Generate migration plans for program state and dependent application components.
  • Simulate upgrade and migration procedures before execution.
  • Support Solana-native program upgrade authorities and applicable governance mechanisms.
  • Integrate with multisignature approval processes, decentralized governance, and timelocks where configured.
  • Require authorized approval before changing upgrade authorities or executing production upgrades.
  • Preserve previous release records and provide comparisons between deployed and proposed versions.
  • Document migration prerequisites, expected effects, rollback limitations, and recovery options.
  • Detect configurations in which a program is immutable or cannot be upgraded through the proposed process.
  • Avoid assuming that every program supports proxy-based upgrades or that every upgrade can be reversed.

Upgrade operations must respect Solana’s actual program ownership, loader, authority, and governance constraints. ChainPilot must not imply that an irreversible operation can always be rolled back.

Decentralized Application Builder

  • Generate application interfaces from protocol requirements and approved design specifications.
  • Create reusable user interface components for common decentralized application workflows.
  • Connect application components to relevant program instructions and account data.
  • Support wallet connection, transaction preparation, transaction signing, and confirmation feedback.
  • Explain requested wallet permissions and transaction effects where information is available.
  • Generate client-side validation and transaction error handling.
  • Keep interface behavior consistent with the protocol’s authorization and state rules.
  • Support application previews and testing against simulated or development environments.
  • Validate application integrations when underlying program interfaces change.
  • Allow developers to modify generated interfaces without requiring complete regeneration.

Monitoring and Incident Response

  • Monitor supported on-chain program activity and relevant operational signals.
  • Track transaction failures, unexpected state changes, resource usage, and configured protocol invariants.
  • Identify unusual behavior and potential security incidents for human investigation.
  • Generate alerts with supporting transaction references, relevant observations, and confidence limitations.
  • Compare observed behavior with approved protocol requirements and expected operating conditions.
  • Support incident timelines, investigation notes, and evidence preservation.
  • Recommend containment or recovery actions without automatically exercising privileged controls.
  • Support configurable emergency procedures and authorized suspension mechanisms where the protocol provides them.
  • Record incident responses and subsequent remediation.
  • Avoid claiming that monitoring can detect every exploit or prevent every loss.

Documentation and Developer Guidance

  • Generate and maintain protocol documentation from approved requirements and implementation details.
  • Document program instructions, accounts, state transitions, authorization requirements, and errors.
  • Generate setup instructions, integration guides, testing guidance, and deployment procedures.
  • Produce upgrade notes, migration documentation, and release summaries.
  • Explain security assumptions and unresolved implementation limitations.
  • Update documentation when relevant code or approved specifications change.
  • Identify inconsistencies between documentation, generated code, and test expectations.
  • Support human editing and review before documentation is published.

Governance and Access Control

  • Define project roles and permissions for development, review, deployment, upgrades, and administration.
  • Separate code generation permissions from production deployment authority.
  • Support configurable approval requirements for sensitive operations.
  • Integrate with multisignature systems and supported governance mechanisms.
  • Maintain records of authorization decisions and administrative changes.
  • Protect secrets, signing credentials, and sensitive project configuration.
  • Apply least-privilege principles to AI tools, integrations, and automated workflows.
  • Provide explicit controls for disabling AI execution and revoking integration permissions.
  • Ensure that emergency procedures do not silently bypass required authorization controls.

Auditability and Reproducibility

  • Record generated code changes, developer edits, test results, security findings, and release decisions.
  • Maintain traceability between requirements, implementation artifacts, and verification evidence.
  • Identify the versions of relevant inputs, dependencies, tools, and configurations used in a build.
  • Support reproducible builds where the underlying environment permits them.
  • Generate integrity records for release artifacts and verification reports.
  • Distinguish generated content, human-authored changes, automated findings, and human approvals.
  • Preserve relevant audit records according to configurable retention policies.
  • Support independent review without requiring trust in AI-generated summaries alone.

Privacy and Local-First Operation

  • Support self-hosted deployments and local development workflows.
  • Allow configurable selection of AI providers and locally hosted models.
  • Provide controls over the information shared with external services.
  • Keep private keys, seed phrases, and wallet recovery secrets outside AI prompts and ordinary project logs.
  • Apply access controls to source code, project data, credentials, and generated artifacts.
  • Provide configurable retention and deletion policies for project data.
  • Disclose external service dependencies and data-sharing behavior.
  • Support operation without external AI services when the selected configuration and functionality permit it.

Integration and Automation

  • Provide integration points for version control, issue tracking, build automation, testing, and release workflows.
  • Support configurable automation pipelines for code generation, validation, review, and deployment preparation.
  • Expose documented interfaces for supported external tools and services.
  • Allow automation to run only within explicitly configured permissions.
  • Require appropriate authorization for sensitive operations initiated through integrations.
  • Provide clear error reporting and recovery guidance for failed automation tasks.
  • Preserve audit records for automated changes and consequential actions.

Optional Plugin Modules

Additional AI Providers

  • Integrate additional hosted or locally operated AI models.
  • Allow projects to select providers according to privacy, capability, availability, and cost requirements.
  • Support configurable model selection for planning, generation, testing, and documentation.
  • Preserve review and authorization controls regardless of the selected provider.

Advanced Security Engines

  • Integrate additional static analyzers, fuzzers, symbolic analysis tools, and formal verification systems.
  • Add specialized security rules for particular protocol designs and program behaviors.
  • Import findings from external security tools.
  • Normalize findings and retain links to supporting evidence.
  • Support independent audit workflows and verification reports.

Protocol Templates and Component Marketplace

  • Provide reusable templates for common Solana protocol patterns.
  • Support reviewed components for token utilities, governance, staking, payments, marketplaces, and other supported use cases.
  • Record component versions, licenses, dependencies, provenance, and verification status.
  • Allow developers to inspect components before incorporating them.
  • Distinguish reviewed components from community submissions that have not been independently verified.
  • Support controlled publication, updates, and removal of components.

Governance Integrations

  • Integrate with supported multisignature wallets, decentralized autonomous organizations, and governance frameworks.
  • Prepare proposals and approval packages for authorized review.
  • Track proposal status and applicable execution conditions.
  • Verify that governance integrations match the deployed program’s actual authority configuration.
  • Never treat proposal generation as approval or execution authorization.

Specialized Protocol Analysis

  • Add domain-specific checks for decentralized exchanges, lending protocols, staking systems, payment applications, and other protocol categories.
  • Provide specialized economic simulations and threat models.
  • Validate assumptions relevant to each supported protocol type.
  • Allow teams to define additional invariants and risk policies.

Frontend and Wallet Integrations

  • Add support for additional wallet providers and application frameworks.
  • Generate specialized interface components and transaction flows.
  • Validate wallet interaction behavior and user-facing transaction summaries.
  • Provide compatibility checks for supported wallets and client integrations.

Monitoring and Alerting Integrations

  • Connect external monitoring systems, notification services, and incident management platforms.
  • Configure alert delivery, severity thresholds, and escalation procedures.
  • Correlate on-chain observations with relevant operational events.
  • Respect configured privacy and access policies.

CI/CD and Repository Integrations

  • Integrate with supported source control and build systems.
  • Automate test execution, security scans, artifact generation, and release preparation.
  • Enforce configurable quality gates.
  • Require explicit authorization before production actions when required by project policy.
  • Preserve traceability between source changes and deployed artifacts.

Enterprise Collaboration

  • Add organization-level project management, team policies, and approval workflows.
  • Support configurable access controls and audit retention.
  • Provide centralized policy management for multiple projects.
  • Allow organizations to integrate their own security requirements and review procedures.

Human Oversight and Safety Requirements

  • AI-generated code must remain inspectable and editable by developers.
  • Production deployments, upgrades, authority changes, and other consequential operations must require appropriate explicit authorization.
  • AI systems must not independently change approved security policies, economic parameters, spending limits, or governance authority.
  • Automated actions must remain within the permissions granted to the relevant component.
  • Sensitive credentials must not be exposed to unrestricted model contexts or ordinary logs.
  • Security findings must include sufficient evidence for independent review wherever possible.
  • Unverified assumptions and unresolved critical findings must remain visible.
  • The platform must distinguish recommendations, prepared actions, authorized actions, and completed actions.
  • Emergency controls must be documented, access-controlled, and auditable.
  • Users must be able to disable automation and revoke integrations without relying on the AI system itself.
  • No security score, automated test result, or AI-generated report may be represented as a guarantee of correctness or protection from financial loss.

Roadmap

Initial Release

  • Natural-language protocol specification and planning.
  • AI-assisted smart contract generation.
  • Developer review and code editing.
  • Local testing and Solana Devnet workflows.
  • Initial security checks and test generation.
  • Documentation generation.
  • Explicit human authorization for deployment actions.

Upgrade Lifecycle Management

  • Program version tracking and compatibility analysis.
  • Upgrade planning and migration preparation.
  • Simulation of proposed upgrades.
  • Governance and multisignature integrations.
  • Controlled release approvals and upgrade records.

Extensible Ecosystem

  • Plugin interfaces and permissions.
  • Protocol templates and reusable components.
  • Additional AI providers and security engines.
  • Specialized protocol analysis.
  • Collaboration and organization-level controls.

Specification Branding License (SBL)

Standard

Optional


License & Notice Requirements

ChainPilot is released under the GNU Affero General Public License v3.0 or later (AGPL-3.0+).

By contributing to any Open Arsenal project, you agree that your contributions will also be released under this license.

Please note the following:

  • All contributions must comply with the AGPL-3.0+ terms.
  • Under Section 7 of the license, all redistributions, forks, and derivative works must preserve attribution to Roxanne Ardary and roxanneardary.com.
  • ChainPilot specifications are free to use with attribution. A Specification Branding License can be negotiated upon request.
  • The project’s notice.md file tracks attribution requirements and contributor acknowledgments. Any update that adds new contributors or modifies attribution should also update notice.md.
  • When submitting a pull request, ensure that any new files maintain the attribution headers where applicable.
  • Network-deployed versions of this software must also remain fully AGPL-3.0+ compliant, including exposure of source code modifications when applicable under the license.

For full legal details, please refer to the AGPL-3.0+ license and the project’s notice.md file.


Notice – ChainPilot

Attribution Requirement: Under Section 7 of the AGPL 3.0+ license, all redistributions, forks, and derivative works, including network-deployed versions of this project, must provide attribution to Roxanne Ardary and roxanneardary.com.

Contributors

This file tracks contributors and their specific contributions to the project.

  • Roxanne Ardary, roxanneardary.com – October 26, 2026
    Created the repository for ChainPilot. Developed the project concept for an open-source, AI-powered Solana development platform featuring smart contract generation, security analysis, automated testing, deployment, and upgrade lifecycle management.
  • [Add other contributors here] – [Date]
    [Describe contribution in one sentence]

License – ChainPilot

This repository is licensed under the GNU Affero General Public License v3.0 or later (AGPL-3.0+).

Key Points

  • You are free to use, modify, and distribute the code.
  • All redistributions, forks, and derivative works or network-deployed versions must also be licensed under AGPL-3.0+ and provide attribution to Roxanne Ardary and roxanneardary.com as required under Section 7 of the license.
  • The software is provided “as is,” without warranty of any kind.

For the full license text, see GNU AGPL-3.0 License.