Imagine two large banks settling a simple repo deal. One side needs collateral valued at a clear market number. An oracle feeds them a clean one hundred dollar reference. Yet the banks quietly settle on ninety-eight between themselves. Who gets to see that private number? Only the two of them. That exact scenario sits at the heart of the latest move by RedStone, and it feels like a quiet but meaningful step for institutional blockchain work.
RedStone Secures Substantial Canton Funding For CAPS
RedStone has received formal approval for a grant of fifteen million seven hundred seventy-five thousand Canton Coin. The baseline funding value sits around one point eight three million dollars. The money supports a twelve-month program aimed at building the Canton Access and Privacy Standard, better known as CAPS. Half the payouts depend on real adoption rather than pure engineering progress. That structure already signals a practical mindset I find refreshing in this space.
The decision itself came through on September sixteenth with unanimous support. RedStone made the public announcement on October twenty-ninth. In the accompanying note the team walked through the repo example in clear terms. An oracle supplies the open reference price. The counterparties keep their negotiated valuation private. The oracle never learns the final figure or the positions involved. Simple idea. Harder to execute cleanly on a shared ledger.
I’ve watched oracle projects for a while now. Most public feeds work fine for open DeFi. Institutions play a different game. They need shared reference points without broadcasting every commercial term. CAPS tries to solve exactly that tension. Whether it fully succeeds remains to be seen, but the design choices look carefully considered.
How The Funding Structure Encourages Real Use
The public grant record lists eight distinct milestones. Payments split evenly between technical delivery and proven network activity. RedStone adjusted the payout schedule during the review process. A September ninth comment explained the shift. The change places stronger weight on actual usage, which makes sense if the goal is lasting infrastructure rather than a short-lived demo.
By month six the plan calls for at least twenty active Zenith mainnet feeds. Those feeds must deliver ten thousand successful price updates across thirty consecutive days. Acceptance requires on-chain records plus evidence that ecosystem partners use the data for collateral pricing. Another later target demands more than one million dollars in liquidity bridged through Memora from Solana, Stellar or Base. At least one hundred distinct bridging events must appear. A further payment links to one million dollars in monthly trading volume that relies on CAPS.
Final acceptance includes an external security audit, any needed remediation, and concrete institutional usage evidence. Where compliance rules block public disclosure the grant allows private confirmation to the committee. That flexibility feels necessary. Institutions rarely publish every trade detail. Tying money to verifiable activity while respecting those constraints shows thoughtful design.
Milestone payments use a seven-day average of the Canton Coin price. The one point eight three million figure serves only as a baseline. Actual dollar value will move with the token. Still, the structure keeps everyone focused on delivery and adoption instead of pure token price speculation.
Early Design Partners And Planned Applications
Zenith and Memora appear as the first design partners. Integrations remain under active development. Memora intends to lean on CAPS for reserve attestations. Zenith focuses on pricing that applications can consume. Temple Digital Group plans to test the framework during rollout. These names matter because they bring practical use cases rather than theoretical interest alone.
Viv Diwakar, head of the Canton Foundation, described the intended outcome as a shared privacy and licensing framework. Multiple data providers should be able to serve the network under consistent rules. That vision sits at the center of the whole effort. One provider should not dominate simply because it arrived first. Clear interfaces and licensing rules help keep the door open.
RedStone already brings relevant experience. Earlier this year the team launched a dedicated Stellar price oracle. That work supported configurable feeds for applications relying on external asset prices. Later reporting placed Stellar’s tokenized asset market above three billion dollars according to RedStone data, while certain RWA-enabled pools sat only slightly above two million. The contrast highlights how standardized pricing can support broader growth. CAPS extends similar thinking into a more private institutional setting.
The Public Standards Draft Arrived First
A standards draft appeared in Canton’s public repository on October twenty-sixth, three days before the announcement. The submission still carries the temporary label Draft and uses the alias cip-redstone-caps while awaiting a formal proposal number. The text specifies Daml interfaces for publishing, distributing and verifying oracle data. Reference fixings land on the ledger. Consumption of that data stays invisible to the oracle operator.
The proposal text itself sits under a CC0-1.0 license. Code follows Apache-2.0. The linked reference implementation includes interfaces, templates, verification components, tests and documentation. That level of openness helps other builders evaluate the approach early.
Data arrives in numbered rounds. Each round carries a price-free record plus a separate capsule holding the actual data. Licensed distributors can create capsules limited to their own clients. Consumers verify both authenticity and consistency with the recorded round through their own participant. Freshness, licensing status and the round’s signatories all form part of the checks an application should perform.
The implementation builds directly on the Canton Data Standard’s PublishedDataPoint interface. An application already written for that interface can read a CAPS capsule without changing its consumer side. Providers join by implementing a verifier for their own signing and aggregation scheme. The codebase ships with a RedStone-specific verifier alongside the generic framework. Tests cover publication failures, sublicensing, revocation, visibility rules and verification against signed payloads. That breadth suggests serious attention to edge cases.
Why Privacy Matters For Institutional Pricing
Public blockchains excel at transparency. Institutions often need the opposite for commercial terms. A shared reference price creates a common starting point. The negotiated adjustment remains bilateral. CAPS keeps those two layers cleanly separated. The oracle never learns the private valuation. Counterparties never expose their full position through the price calculation itself.
In my view this distinction is more important than many outsiders realize. Banks already run complex internal valuation models. They still benefit from an independent, auditable reference. They simply refuse to broadcast every commercial discount or premium. CAPS attempts to give them both the shared reference and the commercial privacy. If the model holds up under real volume it could lower a meaningful barrier to institutional participation.
Consider the repo example again. Collateral needs a clear market number for regulatory and risk purposes. The actual funding rate or haircut stays between the two desks. On a fully transparent ledger those numbers might leak. On a pure private system the reference itself becomes harder to audit across participants. CAPS sits in the middle. The reference lives on the ledger. The commercial terms stay off it.
Only the two banks should know the ninety-eight dollar figure. That single sentence captures the entire design goal.
The approach also supports multiple data providers. One firm should not become a single point of failure or a pricing monopoly. Clear licensing and verification rules let several oracles operate under the same privacy model. Institutions gain choice. The network gains resilience.
Milestone Timeline And Adoption Targets
The twelve-month calendar breaks into clear phases. Early months focus on core engineering and the first live feeds. Mid-program targets emphasize measurable activity on Zenith and bridging volume through Memora. Later stages require trading volume that depends on CAPS plus the external audit.
Twenty active feeds and ten thousand successful updates over thirty days set a concrete bar. One million dollars bridged with one hundred distinct events provides another. One million dollars in monthly CAPS-dependent volume adds commercial pressure. These numbers are not enormous by global market standards, yet they force real operational work rather than slide-deck progress.
I appreciate the equal weight on adoption. Many grants pay out for code alone. Code that never sees meaningful use creates little lasting value. Tying half the capital to demonstrated activity aligns incentives more tightly with the network’s long-term health.
- Month six: twenty Zenith mainnet feeds and ten thousand price updates
- Month eight: over one million dollars bridged via Memora with one hundred events
- Later stages: one million dollars monthly trading volume relying on CAPS
- Final gate: external audit plus institutional usage evidence
Private confirmation options protect institutions that cannot publish every transaction. The committee can still verify progress without forcing public disclosure. That pragmatic middle path increases the chance of genuine institutional engagement.
Technical Foundations Under The Standard
CAPS rests on numbered data rounds. Each round contains a price-free record visible on the ledger and a separate capsule holding the actual pricing payload. Only licensed parties can create capsules for their clients. Consumers perform their own verification of authenticity and consistency with the published round. The design keeps the oracle operator out of the consumption path.
Applications already built against the Canton Data Standard’s PublishedDataPoint interface can consume CAPS data without rewriting their consumer logic. That backward compatibility lowers the cost of adoption for existing projects. Providers implement a verifier matching their own signing and aggregation method. RedStone ships one such verifier. Others can follow the same pattern.
Documented tests address publication failures, sublicensing flows, revocation, visibility rules and payload verification. Edge-case coverage of this sort usually separates early prototypes from production-ready frameworks. Whether every edge case appears in the first live deployments remains an open question, yet the preparation looks thorough.
Freshness checks, licensing status and signatory validation form part of the recommended application-side logic. Developers retain control over how strictly they enforce each rule. That flexibility suits different institutional risk appetites.
Broader Context Of Institutional Ledger Work
The grant arrives at a moment when larger infrastructure players continue expanding on Canton. DTCC recently launched its tokenization service with Canton and a private Besu network as initial integrations. Twenty DTC participants signed access agreements, among them major banks and asset managers. Eligible users can create tokenized representations of securities already held at DTC and move between traditional and tokenized forms while preserving ownership rights and economic entitlements.
DTC holds more than one hundred fourteen trillion dollars in custody. That figure describes the existing book, not assets already tokenized. The platform grew with input from more than one hundred fifty firms. Further network integrations are planned for the following year. Against that backdrop a privacy-preserving pricing standard looks timely. Tokenized securities still need reliable reference prices. Institutions still need commercial confidentiality.
RedStone’s earlier Stellar work already touched tokenized Treasuries, credit products and fund instruments. CAPS extends similar pricing discipline into a setting where privacy constraints run higher. The combination of public reference integrity and private commercial terms may prove useful beyond the initial design partners.
Potential Benefits And Remaining Questions
Shared reference prices reduce disputes over collateral valuation. Private negotiated terms protect competitive positioning. Multiple licensed providers prevent single-vendor lock-in. On-ledger verification supports audit requirements without forcing full transparency of every commercial detail. Those benefits sound attractive on paper.
Several practical questions remain. Will enough institutions generate the required trading volume within the twelve-month window? Can the licensing model scale cleanly as more providers join? How will regulators view the separation between public reference and private adjustment? Will the external audit surface issues that slow adoption? These points will decide whether CAPS becomes lasting infrastructure or a well-documented experiment.
In my experience the projects that survive are those that survive contact with real operational friction. Milestone-based funding that rewards usage increases the odds of that contact happening early. The presence of design partners with concrete use cases further improves the outlook. Still, twelve months is a short window for institutional processes. Many internal approval cycles move slower than pure technology development.
Perhaps the most interesting aspect is the attempt to keep the oracle itself out of the private commercial conversation. Many existing oracle models assume the data provider sees every consumer. CAPS deliberately breaks that assumption. Whether that architectural choice holds under load and under scrutiny will shape future privacy-preserving data standards.
What Success Could Look Like
Success does not require overnight dominance of institutional pricing. Steady growth in active feeds, measurable bridging volume and genuine trading activity that depends on the standard would already mark progress. Additional design partners joining after the first wave would signal broader interest. Clean audit results and smooth remediation would build confidence. Over time a library of verifiers from different providers would demonstrate the open nature of the framework.
If those pieces fall into place, CAPS could become a quiet piece of plumbing that institutions rely on without thinking much about it. Reference prices appear when needed. Commercial terms stay bilateral. Auditors can still verify the shared numbers. That outcome would feel like a practical win rather than a flashy announcement.
Failure modes are equally clear. Missed adoption milestones would reduce funding and slow development. Technical issues that surface late could delay institutional comfort. Competitive standards from other providers might fragment attention. Any of those paths remains possible. The grant structure at least forces early visibility into which path is unfolding.
Practical Implications For Market Participants
Asset managers exploring tokenized products gain a potential source of independent pricing that respects commercial privacy. Banks running internal collateral systems can test shared references without exposing every negotiation. Developers building on Canton receive a documented interface and reference implementation they can evaluate today. Data providers considering the network see a licensing model that supports multiple participants.
None of these groups needs to commit capital tomorrow. The public draft and reference code already allow technical evaluation. Design partner activity will generate the first operational lessons. Milestone reports will show whether usage materializes. Market participants can watch those signals with relatively low cost and form their own view.
I’ve found that the most useful infrastructure often looks boring from the outside. Clean interfaces, clear licensing, verifiable data and sensible privacy boundaries rarely generate headlines. They do, however, lower friction for serious capital. CAPS aims for exactly that kind of quiet usefulness.
Looking Ahead Over The Next Year
The next twelve months will reveal whether the combination of funding, design partners and open standards produces measurable institutional activity. Early feed launches and bridging volume will offer the first concrete data points. The external audit will test security claims under independent eyes. Trading volume targets will show whether applications actually rely on the standard for commercial decisions.
Parallel developments in tokenized securities and larger custody platforms create a supportive backdrop. Institutions already exploring Canton for other reasons may find a privacy-aware pricing layer convenient. Whether they actually adopt it depends on operational fit, regulatory comfort and competitive alternatives. Those factors sit outside any single grant’s control.
For now the project has capital, a clear roadmap, initial partners and public technical material. That combination places it ahead of many earlier oracle experiments. Execution over the coming months will decide how far the advantage extends. The separation of public reference and private commercial terms remains the core idea worth watching. If that separation proves robust under real conditions, CAPS could influence how future institutional data standards are written.
The story is still early. Grants get approved. Code gets written. Partners begin testing. Real volume either appears or it does not. The structure of this particular grant at least ensures the outcome will become visible rather than remaining hidden inside private progress reports. That transparency itself is a useful feature.
Institutions have waited a long time for ledger systems that respect both shared truth and commercial confidentiality. CAPS is one attempt to deliver both. The coming year will show whether the attempt lands cleanly enough for broader use. Until then the practical details of feeds, bridges, audits and volume will tell the real story more clearly than any announcement ever could.
