THE DEVELOPMENT & MARKETING LAB FOR COTI
Privacy Consortium brings development and marketing together to grow COTI—and create a route toward more decentralized ownership.
PRIVATE COMPUTATIONTHE LAB
Our work starts with COTI: better tools for developers, a clearer story for the market, and more ways for the community to shape what comes next.
Make COTI easier to build on and more useful in practice. Start with the tools, integrations, and reference applications that developers need.
Give COTI a clear voice and help its technology find users. Work closely with developers so the story reflects what the network can actually do.
THE ROADMAP / 2026–2027
Start with confidential treasury and payment workflows, then private issuance and allocations. Build services that organizations use repeatedly and pay for.
Proposed delivery planTarget windows, subject to operational access, an approved team, and the results of each phase.
PHASE 01 / Sep–Oct 2026
The first 30 days establish the operational baseline, customer demand, and priorities for COTI’s next releases.
Ten buyer interviews, three qualified design partners, and every production component and authority identified.
Adapted from the COTI Roadmap Review, with an evidence cut-off of 10 September 2026. This is an independent proposal, not official COTI guidance. The windows assume a September 2026 start; dates and targets are planning assumptions, not completed milestones. Ownership arrangements and participation rights remain to be agreed.
Begin with verified operational access and a named decision-making group. Discovery and architecture review can proceed while a handover is pending; ownership-dependent changes require the relevant authority.
Days 1–14
Product · CTO
Reconcile the roadmap and deployment status. Review bridge and Portal incidents, operator controls, fee routes, emissions, and existing customer agreements.
An agreed internal baseline, a public list of supported networks and program status, and a named owner for every gap.
Days 15–30
Solutions · Product
Interview ten target buyers, qualify three design partners, select two product workflows, and rank the first external-chain route.
Each partner has a real workflow, an integration owner, a decision date, and a reason to pay. Unnamed prospects do not count toward the target.
Days 31–60
Engineering · Security
Pin SDK and deployment versions, implement request tracking and reconciliation, scope an external review, build payment and allocation prototypes, and publish gCOTI decision options.
Independent integrators reproduce the workflows in the agreed environment. Security findings and commercial blockers have owners.
Days 61–90
Site reliability · Solutions
Run restricted pilots, recovery drills, and recurring customer cycles. Publish the first monthly fee and emissions report, then review the public launch criteria.
Three organizations use pilots, two pay unsubsidized invoices, and financial state reconciles. Broader release depends on audit and reliability results.
Independent end-to-end review of the released route and application. No unresolved critical or high findings; upgrade and emergency authorities verified.
Target at least 99.5% of valid, funded requests completing within the documented pilot service window over 30 days. Count stuck and timed-out requests as failures and report exclusions.
Reconcile assets, fees, and application outcomes for every pilot action. Trace each eligible burn route from collection through settlement.
Agree with each customer what stays public, who can decrypt each field, and how recovery and employee or officer changes work.
If security or recovery criteria fail, keep the service restricted and repair it. If customers use a pilot but will not pay, revisit the product and pricing before adding another chain. Release depends on meeting the criteria.
OWNERSHIP
The Consortium is designed to help COTI move toward a more decentralized ownership structure. That starts by making the work, the decisions, and the responsibilities easier to see.
Broaden who can
contribute.
Broaden who can
take responsibility.
Set out which rights, assets, and decisions could be part of a COTI ownership transition—and what approvals they need.
Develop clear ways for engineers, marketers, and community contributors to participate in the work and its direction.
Test the model, publish the terms, and review each step before extending it. Any transfer follows an agreed framework.
THE TECHNOLOGY
COTI uses garbled circuits to compute on encrypted data. The lab’s job is to make that technology easier to build with, explain, and put to work.
COTI uses garbled circuits to enable computation on encrypted data. This is the technical foundation for the lab’s development work.
Read the COTI documentationWHY A CONSORTIUM
Privacy Consortium brings engineers, marketers, and contributors around a shared COTI roadmap. Development and marketing are its day-to-day work. A broader ownership base is the longer-term aim.
The institution should become less dependent on any one team as more people take responsibility for its direction.
Return to the roadmap