RedStone details CAPS, its confidential institutional data project on Canton

A new presentation of funding approved in September

RedStone detailed the Canton Access and Privacy Standard, or CAPS, on October 29, 2026, a pricing-data distribution project for institutions using Canton. The presentation date must be separated from funding approval: the Canton Development Fund approved the proposal on September 16. The framework remains in development. The announcement is therefore neither a new vote this week nor immediate opening of a pricing service already deployed for every network participant.

The program envisages 15,775,000 Canton Coin over twelve months and eight milestones. Half of payments depend on demonstrated adoption rather than technical delivery alone. A committee reviews milestones publicly on GitHub. The token amount should not be substituted with a fixed dollar value: RedStone describes a mechanism incorporating an average price when milestones are accepted. The commitment does not mean all funds had already been paid at publication.

Sharing a price without exposing each transaction's terms

CAPS addresses a specific institutional-market problem: using a common reference while keeping positions and negotiated terms confidential. Under the proposed design, a provider publishes a reference price, and institutions calculate their own figures privately from that same input. The provider should not receive commercial information needed only by counterparties. Intended privacy therefore concerns data usage and participant agreements, not an absence of traceability for the reference price.

RedStone identifies tokenized funds, private assets, and lending collateral as potential uses. A reference value can support valuation or a threshold without revealing an entire portfolio to a data provider. This separation may interest institutions seeking digital trading alongside commercial confidentiality. It still needs demonstration in contracts and integrations actually delivered. An architectural description is not yet evidence that every production application meets the claimed properties.

Open software accompanies integrations still being built

The project envisages open components under Apache 2.0, allowing multiple providers to use the framework without depending solely on RedStone's services. A licensing module is also intended to preserve commercial terms attached to some data. The combination seeks a shared standard without automatically making every piece of information free. Code openness and data access rights are separate questions whose rules must remain explicit for institutional users and publishers.

Zenith and Memora are among design partners for initial integrations still in development. The schedule includes a standards proposal, deployments, and an external security audit. Progress must therefore be measured through approved milestones and demonstrated usage, without treating funding as established adoption. October's presentation clarifies an institutional privacy project; its practical value depends on delivery and multiple actors using common references without disclosing their individual terms.