Acquisition

​

Available for acquisition

AlgoVoi is a production multi-chain stablecoin payment infrastructure business open to acquisition. Sole proprietorship, sole authorship, no outside equity, no debt. A clean transfer is possible. Contact: Christopher Hopley, [email protected] Indicative pricing and a diligence pack are available under mutual NDA. Direct discussions only.

---

​

What a buyer acquires on day one

A fully operational payments and compliance layer that a buyer can drop into an existing product or customer base without rebuilding. There is no construction phase: the stack is in production.

---

​

Commercial product tier: Substrate 2

Beyond the Apache-2.0 open substrate, AlgoVoi ships Substrate 2, an integrated commercial product that bundles the advanced trust layer under a single commercial licence. Three enhanced capabilities, enabled by default, are what separate it from the open substrate:

• Post-quantum by default. Falcon-1024 and ML-DSA signatures (ML-DSA per NIST FIPS 204; Falcon per the draft FN-DSA / FIPS 206) are standard, not an add-on. Evidence signed today stays verifiable after the migration to post-quantum cryptography; classical signatures remain available where PQC is not yet needed.
• Zero-knowledge reputation. Prove an agent cleared a trust threshold without revealing its score. Range-proof-backed credentials, offline-verifiable, with no disclosure of the underlying behaviour data.
• Cross-issuer federation. Compose trust credentials from multiple independent issuers into one verifiable token, with no shared trust root. Each credential is verified on its own merits.

Wrapped in commercial terms (warranty, indemnification, SLA) with no open-source attribution obligations to carry through a buyer’s own product, and in production today as the evidence substrate behind the AlgoVoi payment gateway, deployed to sign and verify agentic and x402 payment receipts. Included in the Enterprise and On-premise plans, this is a packaged, enterprise-licensable commercial product sitting on top of the open substrate, not just a set of open-source components.

---

​

The commercial application suite: live and self-serve

On top of Substrate 2, AlgoVoi ships a suite of separately-licensed commercial applications, each binding to the Substrate 2 evidence core. As of June 2026 they are live and self-serve purchasable: a working, productised commercial surface, not a roadmap. The platform is pre-revenue: the build risk is retired and the applications are deployed and purchasable today; standing up the first commercial customers is the buyer’s opportunity, not a construction project.

• Storefront: docs.algovoi.co.uk/substrate-2: each application on its own page with one-click checkout, paid in USDC across 7 chains, backed by the live /suite-store on the production gateway.
• Two parent bundles: the estate ships as two self-hosted, perpetual-licence bundles installed by one key each: Payment Rails ($5,000) and the [Verifiable Compliance Suite](/verifiable-compliance-suite) ($5,000). Individual components ship inside their parent bundle rather than being sold standalone.
• Licensing: perpetual, value-based, self-hosted, two installs per licence, optional 5%/yr support. Enterprise and OEM terms are order-form-driven.
• Runtime enforcement: every package refuses to run without a valid, offline-verifiable Falcon-1024 licence key (fail-closed, package-matched). The commercial moat is enforced in code, not just in contract.

The standalone-purchasable applications on top of Substrate 2: The remaining agentic-payments components (Agent Passport, Spend Guardrail, Settlement Verification, Compliance Gate, Security Suite) are not sold à-la-carte. They ship inside the Payment Rails and Verifiable Compliance Suite bundles. Published Starter pricing shown; enterprise and OEM are the upsell. The application suite also includes Archive-Auditor and an S3 storage variant. For an acquirer this is a built, productised, licence-enforced commercial surface, deployed and self-serve-purchasable today, pre-revenue: self-serve in crypto, with the first commercial onboarding and a clean path to enterprise and OEM deals as the upside.

---

​

Compliance and records suite: regulated industries

A second commercial line sits on the same post-quantum, offline-verifiable evidence substrate, aimed at regulated record-keeping and audit readiness (health, legal, financial). Each application produces signed, offline-verifiable evidence and bolts into the Compliance Command Center, a self-hosted console that ingests every product’s evidence, re-verifies each signed chain offline, and shows one proven compliance posture. Bundled as the Verifiable Compliance Suite, licence-enforced, deployed today. These components are not sold à-la-carte. They ship inside the single Verifiable Compliance Suite bundle: The evidence model is the differentiator: a buyer’s auditor or regulator verifies the evidence offline, with a bundled verifier, without trusting the seller or AlgoVoi. The same suite re-maps cleanly across regulated verticals (the constructions align with EU record-keeping and audit obligations; this is a record-keeping and evidence capability, not legal advice).

---

​

Platform architecture

The platform documentation covers each service at schema and API level: what it does, what it accepts, and what it returns. No source code is included. Full infrastructure specifications, technology stack details, and operating runbooks are available under NDA as part of the diligence pack.

---

​

Who this is for

---

​

What it would cost to build from scratch

Eighteen months minimum for a five-person team covering:

• Substrate layer with cross-implementation validation (10 languages, 1226/1226 byte-for-byte matrix)
• PQC upgrade (ML-DSA-65 / FIPS 204 final, 6-verifier cross-product matrix)
• Seven-chain gateway with live facilitator and failover
• IETF I-D filings, ecosystem engagement across x402, A2A, AP2, and MPP
• Compliance and audit infrastructure with WORM retention
• Published package suites across two registries
• Recurring payments with PSD2-aligned mandate lifecycle
• KYC/KYB pipeline with daily sanctions refresh

AlgoVoi transfers all of this as a working, deployed system, pre-revenue and ready for a buyer’s customer base.

---

​

Substrate authorship

The canonicalisation substrate is the foundational layer that makes multi-party, multi-chain receipts verifiable across independent implementations.

• urn:x402:canonicalisation:jcs-rfc8785-v1: JCS RFC 8785 receipt-body canonicalisation with in-band canon_version pin and transactional-claim-type lifecycle conventions.
• urn:x402:canonicalisation:jcs-rfc8785-v2: PQC-aware successor. Strictly additive over v1. 12-row signature_algorithm open-enum covering ES256, Ed25519, ML-DSA-65 (FIPS 204 final), Falcon-1024, SLH-DSA, and hybrid schemes. Fail-closed verifier discipline.
• ATB Pass Certificate format: Falcon-1024 signed reputation credential issued by ATB hubs. Federated multi-issuer protocol with AlgoVoi-signed Adopters Registry. The substrate is Apache 2.0; AlgoVoi operates the reference hub and controls the registry root key. Cross-validated against three independent Falcon-1024 implementations (PQClean Python + Rust, BouncyCastle Java).

Nine IETF Internet-Drafts: all Independent Submission, Informational, sole AlgoVoi authorship:

• 880/880 cross-implementation agreements across 8 independent JCS implementations (Python, TypeScript, Go, Rust, Java, PHP, .NET, Ruby) over 14 distinct vector sets — byte-for-byte, independently reproduced (cumulative as of 2026-06-18).
• PQC cross-product matrix: 48/48 agreements across 6 producers and 8 verifiers (PQClean, @noble/post-quantum, Bouncy Castle 1.84, RustCrypto). ML-DSA-65 (FIPS 204 final) and Falcon-1024 cross-validated across four independent audit-grade implementations.
• RFC 9421 HTTP signatures: 24/24 cross-implementation agreement across 8 languages.
• Conformance vector corpus: the full open corpus, reproducible from any environment (see the canonicalisation substrate page).
• JSON SchemaStore entry for the compliance receipt v1 schema (merged PR #5726).
• Substrate Adopters Registry: six entries (AlgoVoi v1, AlgoVoi v2, Supership/Crest, PEAC Protocol, Nobulex, Vauban Pay) with AlgoVoi as registry editor.

---

​

Standards posture

The AlgoVoi substrate was not built as a standards-track proposal. It was built because no existing single specification covered the surface that a production multi-chain payment platform requires. x402 specified the HTTP 402 payload but not transactional lifecycle. RFC 8785 specified JSON canonicalisation but not version pinning, transactional claim types, or PQC migration discipline. AP2 specified mandates but not settlement receipts. The various chain-specific signing standards did not compose across Algorand, VOI, Hedera, Stellar, Base, Solana, and Tempo. AlgoVoi needed byte-deterministic, audit-grade, multi-chain, lifecycle-complete receipts in production, and the substrate emerged from solving that engineering problem. The IETF Internet-Drafts, the Apache 2.0 reference implementations, and the cross-implementation validation matrix were the natural consequence of doing the work in the open rather than keeping it private. AlgoVoi adopts the overall standard where one emerges and contributes cooperatively to working-group discussion. The substrate AlgoVoi authored continues to exist alongside it, byte-deterministic and production-proven, and composes cleanly with whatever shape the broader standard takes. The substrate-author position does not depend on any single working group or maintainer accepting a particular pull request. It is anchored where corporate gatekeepers cannot reach:

• IETF Independent Submission stream: nine Internet-Drafts on the public datatracker under sole AlgoVoi authorship, with citation-stable URLs that do not depend on any commercial sponsor.
• Apache 2.0 reference implementations: published on PyPI and npm, independently installable, version-pinned, and byte-for-byte cross-validated across eight languages.
• Public Adopters Registry: six entries published at docs.algovoi.co.uk/adopters with AlgoVoi as registry editor. Adoption is observable in the open without requiring a vendor’s permission.
• Production deployment: bolted into a live multi-chain payment gateway at api.algovoi.co.uk serving compliance-auditable traffic across seven chain families. The substrate is not a paper proposal; it is the wire format of a running system.

If a working group prefers a different design, AlgoVoi’s design still has a place. Two designs can coexist in the ecosystem; downstream adopters choose, and the Adopters Registry is the public record of who chose what. The substrate-author claim rests on the IETF anchor, the package suite, the production deployment, and the Adopters Registry, not on any single PR being merged.

---

​

Transferable assets

The chopmob-cloud GitHub identity is personally tied to the founder and is not transferable. A buyer-controlled organisation is created at closing and all relevant repositories are transferred into it under a documented authorship-continuity note.

---

​

Diligence pack

Available under mutual NDA. Includes:

• Full infrastructure inventory and monthly operating cost breakdown
• Compliance posture documentation and audit-chain forensic walkthrough
• Substrate-author provenance ledger: every upstream contribution, gist, PR, and IETF I-D timestamped and content-addressed
• Cross-implementation validation attestations
• Open work items and realistic time-to-revenue estimates
• Known risk register, including the key buyer exposure: standing up commercial onboarding from a substantially complete pre-revenue platform

---

​

Contact

Christopher Hopley: founder, sole author, sole proprietor. Email: [email protected] GitHub: chopmob-cloud Please include in your first message: who you are, your organisation, intended use, and a brief indication of the structure you have in mind (asset purchase, acqui-hire, full transfer, licensing, etc.). All initial discussions are direct, by email, and confidential by default.