ROADMAP.md

Roadmap

This document tracks planned development of Bot Protocol from v0.1 (current draft) to v1.0 (production-ready stable).

Current status: v0.1 (April 2026)

• Whitepaper published at botprotocol.io
• GitHub repository public for community review
• Specification chapters 01-02 complete
• Specification chapters 03-09 are placeholders pointing to whitepaper

Q2 2026 — Community review (current)

• Publish whitepaper v0.1
• Open GitHub repository
• Receive community feedback through issues
• First batch of clarifications and corrections
• Glossary expansion based on questions received

Q3 2026 — Specification v0.5

• Complete chapters 03-09 with full technical detail
• Formal threat model expansion
• Test vectors for token signing and verification
• Reference implementation in Python (alpha)
  • Identity creation and key management
  • Delegation token issuance and verification
  • Action receipt generation
  • Basic revocation client
• Examples directory with runnable code
• Comparison documents (vs OAuth, DID, SPIFFE, C2PA)

Q4 2026 — First pilots

• Pilot integration with at least one financial sector partner
• Pilot integration with at least one telecom partner
• Field testing of revocation latency
• Performance benchmarks for high-throughput scenarios
• Specification v0.7 incorporating pilot learnings

Q1 2027 — Working group

• Open working group with banks, telecom, regulators
• Public meetings and minutes
• Reference implementation in TypeScript
• Documentation translation (English, Russian)

Q2 2027 — v1.0 release

• Specification v1.0 stable
• All RFC 2119 normative requirements finalized
• Production-ready Python and TypeScript implementations
• Compliance test suite

Q3-Q4 2027 — Ecosystem

• Compliance certification process
• Russian regulatory alignment (federal AI law expected September 2027)
• Integration patterns with national biometric system (EBS)
• Patterns for KEP (qualified electronic signature) integration

Long-term goals (2028+)

• IETF or W3C standardization track (after v1.0 stability)
• International regulatory alignment (EU AI Act, US frameworks)
• Hardware security module (HSM) profile for high-assurance deployments
• Post-quantum cryptography migration plan

How to influence the roadmap

• Open feature-request issues for missing capabilities
• Comment on existing issues to indicate priority
• Volunteer to implement roadmap items by opening pull requests
• Sponsor specific deliverables by contacting the maintainer

The roadmap is a living document. It is reviewed and updated quarterly.