Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.algovoi.co.uk/llms.txt

Use this file to discover all available pages before exploring further.

​
Status

AlgoVoi is open to acquisition discussions as of May 2026. Sole proprietorship, sole authorship across the substrate stack, no outside equity, no investors, no debt. A clean transfer is possible. This page is the canonical inbound surface for serious enquiries. Contact: chopmob@gmail.com (Christopher Hopley, AlgoVoi founder and sole author).

​
Indicated headline figure

£50,000 for the full IP and tech stack. Single payment, clean asset transfer, no earn-out, no founder retention beyond a defined handover period. Covers: all substrate IP, IETF Internet-Draft authorship continuity, all 16 packages on PyPI and npm, all GitHub repositories, the production multi-chain gateway and audit chain, all domains, all infrastructure, Substrate Adopters Registry editorship, and the full ecosystem-integration stack documented below. Buyer covers all transaction costs. Both sides’ legal fees and any applicable transfer taxes are paid by the buyer. The £50,000 figure is net to the seller. Direct discussions only. Diligence pack available under mutual NDA.

​
What is on offer

A single transferable bundle covering:

​
Substrate authorship position

  • urn:x402:canonicalisation:jcs-rfc8785-v1 — AlgoVoi-authored canonicalisation discipline. JCS RFC 8785 receipt-body canonicalisation, in-band canon_version pin, transactional-claim-type lifecycle conventions.
  • urn:x402:canonicalisation:jcs-rfc8785-v2 — PQC-aware additive successor. 12-row signature_algorithm open-enum registry covering Ed25519, ES256, ML-DSA-65 (FIPS 204 final), and Falcon-1024. Fail-closed verifier discipline.
  • Four IETF Internet-Drafts filed on the IETF Datatracker under Independent Submission stream, sole AlgoVoi authorship:
  • Cross-implementation validation matrices. 192/192 byte-for-byte agreements across eight JCS implementations (Python, TypeScript, Go, Rust, Java, PHP, .NET, Ruby). 24/24 PQC cross-product matrix across four producers and six verifiers.
  • Substrate Adopters Registry. Six entries at docs.algovoi.co.uk/adopters: AlgoVoi v1, AlgoVoi v2, Supership / Crest, PEAC Protocol, Nobulex, and Vauban Pay. AlgoVoi is the registry editor.

​
Production platform

  • Live multi-chain gateway at https://api.algovoi.co.uk across Algorand, VOI, Hedera, Stellar, Base, Solana, and Tempo.
  • Compliance and audit chain. Public /compliance/attestation and /compliance/screen endpoints. SHA-256 hash chain across audit_log, screening_hits, and compliance_events. Off-VM B2 Object Lock COMPLIANCE retention, seven-year horizon (current 2033-05-04).
  • Agent-protocol coverage. First-party implementations of x402, MPP, AP2, A2A v1.0, and Solana Actions. First compliance-aware Bazaar facilitator.
  • xChain settlement. Cross-chain bridging via Allbridge and CCTP V2; seven EVM source chains feeding non-EVM destinations.
  • Recurring payments. Recurr Tier 1 (push) and Tier 2 (pull executor) live across four funded chains; PSD2-aligned mandate lifecycle.
  • KYC and KYB. OCR Tier 1 (tesseract + poppler), sanctions screening against OFSI, OFAC, UN, and EU lists (daily refresh), Fernet-encrypted at rest.

​
Packages on public registries

Sole AlgoVoi authorship, Apache 2.0, currently versioned 0.x.1:
  • PyPI (8 packages): algovoi-substrate, algovoi-substrate-pqc, algovoi-refund-receipt, algovoi-settlement-attestation, algovoi-cancellation-receipt, algovoi-composite-trust-query, algovoi-audit-verifier, algovoi-rfc9421-verifier.
  • npm (8 packages): @algovoi/substrate, @algovoi/substrate-pqc, @algovoi/refund-receipt, @algovoi/settlement-attestation, @algovoi/cancellation-receipt, @algovoi/composite-trust-query, @algovoi/audit-verifier, @algovoi/rfc9421-verifier.
  • MCP server. 28-tool MCP server distributed on PyPI, npm, and GitHub Releases; covers 26-network discovery surface.

​
Ecosystem integrations

E-commerce adapters for Shopify, WooCommerce, BigCommerce, OpenCart, PrestaShop, Shopware, Ghost, plus Xero and Calendly. Bots for X, Telegram, Viber, and Discord. ElizaOS plugin shipped (@algovoi/plugin-elizaos).

​
Conformance vectors and tooling

Public conformance-vector repository covering AP2 Open Mandate Hash v0, CTEF + APS v1, privacy-class v0.1, per-chain envelope v0, action-ref namespace v0, action-ref transactional v0, compliance-receipt v1, refund-receipt v1, settlement-attestation v1, cancellation-receipt v1, and composite-trust-query v1. Cross-implementation runner harness, RFC 9421 verifier suites in eight languages.

​
Transferable assets

A clean handover transfers:
  • All eight PyPI package namespaces and all eight npm package scopes (@algovoi/*).
  • All public GitHub repositories under chopmob-cloud related to AlgoVoi (substrate, conformance vectors, individual packages, MCP server, dashboards, gateway, control plane).
  • IETF Datatracker submissions remain authored by Christopher Hopley by convention; buyer succession is documented in the registry and on substrate-authorship-provenance.
  • Domain portfolio: algovoi.co.uk, algovoi.io, api.algovoi.co.uk, recurr.algovoi.co.uk, docs.algovoi.co.uk, dashboard.algovoi.co.uk, related subdomains, and Cloudflare account.
  • Production infrastructure: four production VMs (gateway, control plane, dashboard, facilitator-1, facilitator-2 failover, cloud-gateway, store containers). Vultr account.
  • Backblaze B2 bucket holding the audit chain under seven-year Object Lock retention.
  • All cryptographic keys (with rotation playbook), KYB Fernet keys, signing keys, and operational secrets.
  • Substrate Adopters Registry editorship.
  • The chopmob-cloud GitHub identity used across substrate authorship is personally tied to the founder and is not transferable; a buyer-controlled organisation (e.g. algovoi-substrate GitHub org) is created at closing and substrate repositories are transferred into it under a documented authorship-continuity note.

​
Information for serious enquirers

A diligence pack is available on signature of mutual NDA. The pack includes:
  • Full infrastructure inventory and operating-cost breakdown.
  • Compliance posture documentation and audit-chain forensic walkthrough.
  • Substrate-author provenance ledger (substrate-authorship-provenance) — every upstream contribution, gist, PR, and IETF I-D timestamped and content-addressed.
  • Cross-implementation validation attestations (eight-implementation JCS matrix, six-verifier PQC matrix, four-implementation cancellation-receipt matrix, etc.).
  • Open work items and roadmap.
  • Known risk register, including the buyer’s main exposure: standing up commercial onboarding from a substantially complete platform that is currently pre-revenue.

​
Why a buyer might want this

  • Substrate-author position is a defensible standards-track posture. Independent Submission I-Ds carry the AlgoVoi-authored canonicalisation discipline into the IETF process. Across the x402, A2A, AP2, and MPP ecosystems, downstream parties anchor to the canon_version pin AlgoVoi defined.
  • The production platform is substantially complete. A buyer with commercial reach and an existing customer base can drop the substrate and gateway in as a compliance-aware payment layer for stablecoin commerce, agent payments, and recurring authorities — and not have to build it.
  • Compliance posture is auditable on day one. Public attestation endpoints, hash-chained audit log, off-VM WORM retention, SAMLA-tipping-off compliant by design. A buyer’s risk and compliance function inherits a transparent surface, not a black box.
  • Multi-chain coverage is rare. Seven blockchains under one API with xChain bridging is a small handful of comparable shops; most facilitators are mono-chain.

​
What is not on the table

  • No exclusive licence carve-outs of the substrate (the canonicalisation discipline remains Apache 2.0 in perpetuity; buyer acquires the author’s continuity rights and registry editorship, not a proprietary fork).
  • No earn-out structures requiring founder retention beyond a defined handover period (transfer mechanics negotiable; ongoing founder engagement is not).
  • No deal that requires existing adopters to be informed before closing (the Substrate Adopters Registry update can be staged for post-close communication).

​
Contact

Christopher Hopley — founder, sole author, sole proprietor. Email: chopmob@gmail.com GitHub: chopmob-cloud Initial discussions are direct, by email, and confidential by default. Please include in your first message: who you are, organisation, intended use, and a brief indication of the structure you have in mind (acqui-substrate, asset purchase, full company, etc.). Serious enquiries only. No introducers, no third-party brokers.