Skip to main content
NTL development follows a phased approach, from specification to production readiness.

​
Phase 0: Foundation

Status: Complete
  • Core concept definition
  • Documentation skeleton (Mintlify)
  • Protocol specification beta_0.0.0
  • Signal format, including delivery class and receipts
  • Crypto interface specification
  • Learning model — reward signal, update rule, decay, exploration
  • Threat model, with an explicit out-of-scope list
  • Delivery semantics — best-effort and acknowledged classes
  • Storage interface — pluggable, no named database
  • Repository structure and CI
Goal: A complete, reviewable specification that any team could implement.

​
Phase 1: Reference Implementation (Current)

Status: In Progress
  • Signal encoding/decoding (CBOR)
  • Node identity and keypair management, persisted across restarts
  • Crypto module: classical (Ed25519)
  • Crypto module: post-quantum (Dilithium + Kyber)
  • Pluggable storage: NodeStore trait, SQLite backend, conformance suite
  • Synapse formation and signed handshake
  • Propagation engine with stochastic path selection
  • Activation gate — batched firing, bounded queue, latency guard
  • Learning loop — receipts, timeout sweep, influence caps, normalisation
  • CLI tooling (ntl init, start, emit, listen, synapses, status, topology)
  • ntl-node and ntl-edge binaries
  • Two-node learning demonstration
  • Benchmarks and CI, including a wasm32 build check on ntl-core
  • QUIC transport (currently TCP with length-prefixed CBOR)
  • Public test network with bootstrap nodes
Goal: A working Rust implementation that can form a network and propagate signals. Two nodes on one machine already do.

​
Phase 2: Adapters and Integration

Status: Not Started
  • Web2 adapter (HTTP, WebSocket)
  • Web3 adapter (EVM chains, DID)
  • Legacy API adapter
  • PostgreSQL storage backend
  • Correlation engine for request-response patterns
  • Signal compression (LZ4)
  • Edge node (lightweight) implementation
Goal: NTL can connect to real-world systems and persist state.

​
Phase 3: Production Hardening

Status: Not Started
  • Advanced propagation (Targeted, Gradient scopes)
  • Dynamic threshold tuning
  • Synapse topology optimization
  • Monitoring and observability (OpenTelemetry)
  • Performance benchmarking suite
  • Security audit
  • Formal verification of core protocol properties
Goal: NTL is production-ready for real workloads.

​
Phase 4: Ecosystem

Status: Not Started
  • Client libraries: Go, Python, TypeScript, C
  • Kubernetes operator
  • Docker images and compose files
  • Managed NTL service (The Bundu Foundation)
  • Developer documentation and tutorials
  • Community governance formalization
Goal: NTL has a thriving ecosystem and is used in production by multiple organizations.

​
Long-term Vision

  • Formal IETF standardization process
  • Quantum-era crypto module updates as standards evolve
  • Integration with AI agent frameworks as native transport
  • Global bootstrap network operated by community
  • NTL as the default transport for Mukoko and the broader Bundu ecosystem
Last modified on September 11, 2026