Proposal: Agentic Wallet Infrastructure with ZK Counterparty Risk Verification

Review Feedback — Agentic Wallet Infrastructure with ZK Counterparty Risk Verification

Thank you for the submission and for contributing a proposal focused on wallet infrastructure, agent-based workflows, and privacy-preserving risk verification.

The proposal is ambitious and touches on several important areas for the Canton ecosystem, including identity-linked wallets, automated financial workflows, and zero-knowledge–based verification.

That said, a few areas would benefit from clarification:

1. Scope and focus

The proposal spans multiple large areas:

• wallet infrastructure
• agentic workflows
• RWA integrations
• zero-knowledge risk verification
• regulatory integration

It would be helpful to:

• more clearly define a Phase 1 scope
• distinguish core deliverables from longer-term vision

2. Evidence of ecosystem demand

While the proposal references large external user bases and partners, it is not yet clear:

• which Canton ecosystem participants are actively requesting or planning to use this
• whether there are committed integrations on Canton

3. Adoption expectations

It would help to clarify:

• what measurable adoption looks like on Canton (beyond external user counts)
• how usage will extend beyond the initial wallet deployment

4. Complexity and deliverability

Given the breadth of the proposal and aggressive timelines, it would be useful to:

• clarify sequencing and dependencies between milestones
• ensure each milestone is independently achievable and verifiable

5. Positioning within the ecosystem

The proposal would benefit from clearer positioning relative to:

• existing wallet efforts
• emerging standards (e.g., CIP-0103)
• how this integrates vs. overlaps with other ecosystem components

Overall, this is a high-potential proposal with ambitious goals. Clarifying scope, demand, and phased delivery would strengthen confidence in execution and ecosystem impact.

1. Scope and focus

The proposal spans multiple large areas:

• wallet infrastructure
• agentic workflows
• RWA integrations
• zero-knowledge risk verification
• regulatory integration

It would be helpful to:

• more clearly define a Phase 1 scope
• distinguish core deliverables from longer-term vision

This proposal outlines a plan to bring millions of institutional users to Canton Network by enabling authenticated autonomous AI agents to operate within privacy-preserving financial systems. With stablecoins becoming the primary payment rail for AI-driven transactions—projected to handle over $56 trillion annually by 2030—and zero-knowledge proofs (ZKPs) emerging as a critical solution for mitigating counterparty risk, the initiative combines agentic infrastructure with privacy-preserving risk management. Key milestones include agent authentication via Vodafone and Twilio, integration with Pillar Wallet and OpenClaw, institutional RWA integration with the Tokenized Asset Financing solution by Vodafone’s Pairpoint, and the development of ZK-based frameworks for counterparty risk verification and regulatory alignment.

We believe that with the race to bring agentic commerce on-chain speeding our solution will bring the Canton network a range of tools that will enable this to take place at scale in 2026, as it leverages the telecoms phone number identity that is already being used to authenticate merchant payments globally. The fact that many of the financial institutions in Canton are already using phone number payments authentication means that adoption for the agentic commerce extension will be easier as it will be designed as an add-on to what they already have for business and consumer payments.

The proposal consists of two phases.

Phase 1 focuses on building and deploying an agentic wallet on the Canton Network, designed to support automated payment workflows, simplified onboarding, and enterprise-grade transaction flows. A key component is phone number–based authentication, which enables identity-linked accounts and supports compliance workflows, including KYC where required. This is the key enabler for automated stablecoin and/or AI agent payments.

This phase includes:

• wallet infrastructure with phone-based login
• agent-assisted workflows for executing transactions
• integration with selected RWA applications

Phase 1 is delivered through three milestones:

Milestone 1: Phone number auth for wallets & agents (Vodafone + Twilio)

- Combine phone number-based authentication with wallet-based transaction authorization to enable identity-linked accounts.
- Enable identity-linked accounts that support transaction authentication (in conjunction with Vodafone (PairPoint)— already hosting a node on Canton, and Twilio’s Verify API — API provides wider access to other telecom operators globally).

Milestone 2: Pillar Agentic Wallet Integration live on Canton

• Support for end users and service providers interacting through the wallet.
• Use of wallet and phone number–based identity to enable service discovery and transactions.
• Leveraging existing tools and infrastructure (such as PillarX Wallet).

Milestone 3: Integration of RWA Applications within the Wallet
For RWA we will integrate Vodafone’s Pairpoint ‘proof of use’ protocol into Pillar which will be used to link financing repayments for tokenized assets starting with telecom towers to usage of the asset.

• Integrate Vodafone’s Pairpoint Proof of Use RWA platform into the wallet as an in-wallet app.
• Enable wallet-based access to RWA services and transactions, including proof of use for connected assets and infrastructure Companies working with Pairpoint on the initial phase include Chainlink and Lloyds.
• Showcase the wallet working with phone number identity and agentic plug in integration with marketing.

Phase 2 focuses on building a privacy-preserving framework for counterparty risk verification using zero-knowledge (ZK) proofs and includes:

• zero-knowledge–based risk verification
• regulatory and compliance integrations

2. Evidence of ecosystem demand

While the proposal references large external user bases and partners, it is not yet clear:

• which Canton ecosystem participants are actively requesting or planning to use this
• whether there are committed integrations on Canton

We are integrating with a Tokenisation platform by Vodafone’s Pairpoint which is being deployed on Canton and PillarX is providing the wallet component of the deployment.

This platform introduces a new tokenised asset financing solution for adding AI capabilities to telecommunication infrastructure (Telco Towers and data centers). Involved parties are Vodafone —Pairpoint, ChainLink, Pillar, GSMA (industry association)

RWA usage based finance can go outside the realm of towers into other assets such as EV charge point financing,an initiative we took part in alongside Vodafone-Pairpoint. This setup is also ideal for RWA platforms such as Lloyds to leverage very easily.

The design of this proposal is aligned with emerging needs around agent-assisted interactions and delegated execution.

Potential beneficiaries of this proposal include applications such as Hecto Finance, Lattice Finance, Deploy Finance, and other ecosystem applications, where simplified user onboarding, identity-linked transactions (KYC), and interactions mediated by agents can improve accessibility and user experience.

3. Adoption expectations

It would help to clarify:

• what measurable adoption looks like on Canton (beyond external user counts)
• how usage will extend beyond the initial wallet deployment

The integrations will provide the Canton members with easy access to:

• Secure and trusted agentic payments authentication using phone number digital identity to link AI agent payment to a business or person, building on the existing payments authentication used by merchants for existing business and consumer payments, The adoption will focus on existing payments companies across the Canton ecosystem, however as this functionality provides unique functionality not currently available on other chains, we expect other payments and financial companies will adopt the solution on Canton to access it so they can move quickly to bring solutions to market
• Linking Real World Assets to trusted usage will enable financial institutions to offer new asset usage based lending products. For new industries like AI where assets may have lower use initially but then increase in the medium term this would allow them access market share. This would be available to existing Canton members, but we also expect this unique feature to attract others to the eocsystem.

Primary targets for release and integration are:

• The initial implementation will be delivered as a fork of the PillarX wallet.

• Integration with RWA solution by Vodafone's Pairpoint, which is in the process of rolling out on Canton

Secondary targets will be

• Other financial institutions already working with Canton and Vodafone’s Pairpoint eg Lloyds

Tertiary targets will be apps already deployed on Canton such as:

• Hecto Finance, Lattice Finane, Deploy Finance

While the initial implementation is delivered through the PillarX wallet, the components developed in this proposal are designed to be reusable by other Canton participants.

• A phone number-linked identity layer that can be adopted by other applications on Canton Network.
• Transaction authorization flows that can be integrated into third-party services.
• Agent interaction that can be extended beyond the wallet.

4. Complexity and deliverability

Given the breadth of the proposal and aggressive timelines, it would be useful to:

• clarify sequencing and dependencies between milestones
• ensure each milestone is independently achievable and verifiable

Technically, Phase 2 can be delivered independently. However, we plan to execute the phases sequentially, starting with Phase 1, as it provides the foundation for testing Phase 2.

Phase 1 includes:
1. Phone number-based authentication for wallets and agents (with Vodafone and Twilio);
2. Bringing the Pillar agentic wallet live on Canton (requires the initial authentication layer);
3. Integration of an RWA application within the wallet (requires the initial authentication layer).

While all milestones are connected, milestones 2 and 3 will be developed in parallel after the initial authentication layer is in place.

Phase 2 builds on this foundation and includes:

1. A risk model and commitment framework;
2. ZK-based privacy-preserving risk verification (requires the risk model & commitment framework);
3. Third-party verification and regulatory integration (requires the risk model & commitment framework and ZK-based privacy-preserving risk verification).

These milestones are also interconnected and will be delivered in sequence.

5. Positioning within the ecosystem

The proposal would benefit from clearer positioning relative to:

• existing wallet efforts
• emerging standards (e.g., CIP-0103)
• how this integrates vs. overlaps with other ecosystem components

This proposal is positioned not as a standalone wallet competing with existing solutions, but as a way to demonstrate how identity-linked wallets and agent-assisted transactions can work in practice on Canton Network. In particular, it focuses on enabling phone number–based identity, simplified onboarding, and automated transaction flows that are important for real-world and enterprise use cases.

At the same time, the components developed in this proposal are designed to be reusable, allowing existing and future applications on Canton to leverage this infrastructure to improve onboarding, user experience, and transaction flows.

With regard to emerging standards such as CIP-0103, the approach taken in this proposal is designed to be compatible and adaptable. As standards evolve, the components developed (e.g. identity layer, transaction flows, agent interactions) can be aligned to ensure interoperability within the Canton ecosystem.

This proposal is designed to integrate with existing Canton components rather than overlap with them. It focuses on the user interaction layer, how users authenticate, access services, and execute transactions.

1. Summarise the existing wallets on canton and clearly highlight our differentiation (phoneId authentication and how Telco tower rollout leverages that, and how that opens a new world for wallet and agent based interactions)

The Canton ecosystem includes a number of user-facing wallets, such as 5N Loop, Console Wallet, C8 Wallet, Send and Nightly. These wallets primarily focus on secure key management, transaction signing, and providing access to Canton applications. They offer the core functionality required to interact with the network, typically relying on Canton’s underlying identity model (e.g. Party IDs) and supporting features such as transaction signing, passkeys, and browser-based access.

Our proposal builds on that foundation by introducing additional capabilities focused on identity, automation, and real-world usability.

First, it introduces phone number-based identity as a core part of the wallet experience. Unlike existing approaches that rely on abstract identifiers, this enables identity-linked accounts that are easier to use, support account recovery, and can integrate with compliance workflows such as KYC. By leveraging telecom infrastructure, this approach also creates a scalable path for onboarding a broader user base.

Second, our proposal enables agent-assisted transactions, where predefined agents can execute actions on behalf of users/accounts within defined rules and permissions. This supports more advanced interaction models such as automated payments, recurring transactions, and merchant settlement flows, going beyond standard transaction signing.

Third, the wallet is designed as an interaction and integration layer that enables services such as RWA applications to integrate directly. Rather than acting only as a standalone wallet, it provides a foundation for RWA and tokenisation services to plug into and operate within a consistent environment.

2. Yes, we will be leveraging CIP-0103 to allow our wallet to interact with dapps on Canton.
3. Ecosystem components we can leverage within Canton.

• Support for the Canton token standard in the agentic wallet
• Support for ERC-8004 equivalent on Canton (For the Identity and Reputation management of agents)
• Support for CIP-0103, to allow the wallet to seamlessly interact with dapps on Canton network.
• For zkproof, we are evaluating to use either SuccintLabs SP1 or a16z’s jolt for both proof generation and verification.

[image1]: <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAoIAAACiCAYAAADVw6wKAAArZklEQVR4Xu2dh1sUSfe2f//v5+670ZxdMbuGdc1rBAkCkhRFxQwCgqAoAopiIIoBBQG1vnlOc5qamkFnBnB66Oe+rnP1dHWo6u5h5qaqp8//GUIIIYQQEkr+zy0ghBBCCCHhgCJICCGEEBJSKIKEEEIIISGFIkgIIYQQElIogoQQQgghIYUiSAghhBASUiiChBBCCCEhhSJICCGEEBJSKIKEEEIIISGFIkjIDyT/ZI358/+dZDAYDAZj1qIg8t2SKhRBQn4AA/3vY/5wGQwGg8GYzXj3dsT9+vkuFEFC5hhKIIPBYDB+VLx/l5wMUgQJmWPcP1IGg8FgMOYykoEiSMgcwnsCgxs7Np41rS3PY8rnUyxccNJsXlsaU54JUVZ4x5QWNsSUz7fYt6MqpixTArhl8y0y9foU5d52vo2mhyJIyBzi/nGmOw7suhjTLnC2pClm3W/FlarWmLJ4cSa/Pqa+oAQ+4Dvbe2PK0xkXK++ZL1++RpXlnbiV9Dm8efWRTBf9lG1u3+qMWa7xovu1aazviqkzCHGhokXCLU93uNeiofZxTNn3Au+99cuL4+7Pjo8fx8zdO0/N589fzMo/82OWpzu+1fZ0BN7vbpvwz5Bb9r04nVPrv05k20TWSUckCkWQkDnE/cNMd0AEnz0ZMJtWl/hlTyPztgjmHr9ldm46G7XNxsj6OUduyPy29eVybCjXdQpP3TZLfjkVU9/qRQXm0YNXMeVBiKCKIK7PwgXZfpn7XsK1wTXS+V2bz5l/tp03R/dflfm9f1/wr4+K4H97q+P2bEAEMb1xpc2sCphoBFUEe1+9NY11Xf48mJj44s8f2H3JHD90bWo+ch0W/5wjfyOYX/Zrrnlw74X/Nwfwt4W/K7seXLvz5c3yGjKDbdy2pDvs92UQAucMfz8F2VMid6+p2wxa92mv+CNPesuwLubxvkfo6M1fy4rM2NiE//kG7M8/N9YsPi3ru+VBiEShCBIyh7h/mOkOfLidPHzdfBj+5JdBCu0vpaURocN/xC2Nz/yy7VnlZn9k2462HikbHRn3t8d6+KKb7ngpgokHRBBfRDpkvTQiDXduP/HPLXrvcG1wjbQMrF1SaMqLG01l2V2/DFPtIVn2W665d7fb7Nl+PqZOxMjIWExZuiOoItjX89Y/vwgIhIrg64Fh88/WSrNuaaH04qEM4O9rxe95/nalpxsiQn/OX47rhB+V4bq69SHwHoDwu+XpDvs8BCFwHm9da49q19evxrx981FeQ7afdQ3I6+H3oyLl+Ew8su+K2bDyjPk06n2u3W+eumUEuJ9/dgCKICFkWtw/zHQHPvSK8+rki2nzmlL5MNy9pVLm8SFZXnTHX1fbbx+HfuHZIqjx8cOUXNpBEUw8IIJb/yqTc2YPc7lTBO6fg0zY513Pta6HfWjvFa5vvFsA7H0GKYIqgvgnCsLWFJHykgLvHkb9u7CFQGXePr/62hVBTIvz683uiES69SHQ68Qewe8H3u/4xxQyjn+Y7jd3S9nE+GdZjqF2e32cU3tkQ4/HFUF9bff8IiCZK//Il3UwtZcFIRKFIkjIHOL+YaY7RAQjXzh4DYHo73snXz4qCP297/x1tf32cegHYbweJIrgzAMiCGHDl1fHox5Te6NDyvUa4ItH1+2LXCsMGQ4ODPtl8URQ7xGMJ4IH/7kU04agRFBFUN/nCl7r34X9t6L3Xdpl+hoC+T0RRK/izStt/nwQH0NlH1sQQkSwaWokQ6+BXp/6mscma4V3b2b2kRsii/FFsDumzN6PxqE9lyUApvayIESiUAQJmUMw9OD+caYzbBGE9OHeGFsEq862yJAWwFAWyoBurx+El8/fj0hJ9A8MKIIzDxVBvLZ/wKHXYPnk8CKuA64ByuKJIO77xPX5ngjaBK3HKegiiHvG9EdT+nexZW2pnEuce71PEOi2+hpD+cD+IYMrggi8P8c+Tcj+7PtGgxL2sQUhbBHEP1GH//XkzBa4kY9j8o+sinU8EVS5s8vc/dgRxKFhfPckCkWQkDkkiP/FM7zAl0b2f9djyhnBCNy7ipv03XJGcOLF86GYMkYwAverJgpFkJA5BvfguX+kDAaDwWDMReAeyWSgCBLyA8AvQd0/VgaDwWAwZjPWLy9yv36+C0WQkB+EPhOMwWAwGIzZDtwDnAoUQUJ+MMgUgOFiPHvP/UNmMBgMBiPRwKOF8J0yEyiChBBCCCEhhSJICCGEEBJSKIKEEEIIISGFIkgIIYQQElIogoQQQgghIYUiSAghhBASUiiChBBCCCEhhSJICCGEEBJSKIKEEEIIISGFIkjIHOI+BZ7BmIsghJBUmZEIXr30wC0KNF+/fnWLfL61bLb4EXWQYOF+YTMYcxGEEJIqCYvgnm3nTWd7r2lrfel/8Py1rMhZK3nWLy82K37Pc4ujQH0fhj+5xQlTX/N4ctrpLJni9s0Ot0hY9FO2W5Q0ucdvyXS6Osj8xf3CZjDmIgghJFWSEkGl9HSDTFf+mW+W/Zprel6+kfmlkderFhb488sjgrcqss7TJwMyj2VIkDzY/97b0ST2vt0PtdGRcfMwIp/b1pf7ZZCzlX/ky7qfP38xi3/OkQAH/7lkNq8tlXXGxz+bjavO+PvU6ZZ1ZSKgtpjpsv27LkaWFUl9EEiUY58AdSz7LdeMj0342xzac9l/rfuwz4PWD5HV5RDDjatLzIlD12T+1LGbItUF2bUyv2HlGWnfrWvtMk8yF/cLm8GYiyCEkFRJSgSL8+pEVlYvKpAy/QDa+/cFo6OeELcdGyrktYoNxK/2RoeZmPgi8wsXRH9w2SLosmvzOZnqOnW3OqNEbN3SQn/dsyVN5u/JusH58maZao8g1u/rfWeeP3st8xXFjf66eiw6zVpZLFPtEcw5csNbMcI/WytF3oAtgiDeedAeQV2n6myLTHVoPXty37p856azMkVbSWbjfmEzGHMRhBCSKkmJoIsODWMZer8aaj3h2p7lCRCkqPpCq4gO5AfraNjE27eCDzn0OmLaVN9lqqtao5YhdJ9v33z0e+9AZeldmdoi+KSzL+4ws36Y5hz1pAy9ikBFcN/OKr+e/oigHZ4UwNM5nuzq9vHOgy2CuE+wsa5L5ltbnstUeybtD/TbEeHdsOqMP08yE/cLm8GYiyCEkFSZNRHsfjpoCk7WSGxaXSK9dvt2VIns/Le3WqQQw6S4z3D3lsqo/dj7Prr/

Hello @hythloda, apologies for the delayed response. I’ve now clarified and expanded on all the questions you raised in the original proposal.

Also @hythloda, I noticed the proposal is currently tagged under wallet-apps. Since it incorporates agentic AI through the wallet and leverages ZK proofs, it might be more appropriate to include tags such as AI, wallets, and tooling (ZK).

@ch4r10t33r from a product perspective, the problem space feels compelling. It also looks like there is a meaningful opportunity for growth over the next few years.

The main question I still have is around customer pull. As I reviewed other agentic wallet proposals, I couldn't yet get a clear picture of which Canton ecosystem participants are actively asking for this, evaluating it, or planning to use it in the near term

@ch4r10t33r from a product perspective, the problem space feels compelling. It also looks like there is a meaningful opportunity for growth over the next few years.

The main question I still have is around customer pull. As I reviewed other agentic wallet proposals, I couldn't yet get a clear picture of which Canton ecosystem participants are actively asking for this, evaluating it, or planning to use it in the near term

The core direction we are converging on is identity-linked execution for policy-based financial operations. Concretely, this means agents that can execute predefined workflows such as treasury actions, distributions, or rollover operations under explicit authorization and counterparty constraints. From a technical perspective, the problem we are interested in is not autonomous agents in the abstract, but reducing operational coordination overhead across multi-party financial workflows while preserving identity, permissions, and privacy guarantees native to Canton. We’re already working with Vodafone, Lloyds Banking Group, and Pairpoint (Vodafone and Sumitomo joint venture) around an agentic wallet interface tied to mobile-phone-based authentication for usage-based finance products. This is an RWA implementation where AI processing on the edge is facilitated through leveraging processing capacity within Telco Towers and the Lloyds RWA platform enables the financing where revenue share with investors is generated in real-time as the platform is used by end users, hence usage based finance is realised. Initial phase will focus on a handful Towers out of the 38k operating within the UK A large part of the learning from those discussions has been around how identity-bound execution, delegated permissions, and machine-mediated financial interactions can operate within existing enterprise trust and authentication systems. The phone identity layer in the proposal is therefore primarily an authentication and recovery primitive that integrates with existing enterprise and telecom identity systems. The “wallet”, more of a dashboard, itself is intended to function as an execution and authorization layer for programmable workflows rather than a standalone end-user crypto wallet. We agree that adoption needs to be demonstrated through concrete ecosystem usage. Phase 1 of the proposal is focused on:

• a smaller number of independently verifiable workflows
• clearer integration targets within the Canton ecosystem
• measurable execution and usage metrics tied to those workflows
• The broader vision around generalized agent infrastructure and ZK-based verification remains important, but we do not think it needs to be front-loaded into Phase 1.

@ch4r10t33r wanna followup on @joel-da Joel's Que above, we have an Agent wallet already made via dev fund so how's this gonna be different and as for now anyone in the community or enterprise side has not shown any need or demand for agentic infra so I am confused btw two things before it comes to vote:

• How'd this be different from already approved agent kit and wallet tool.
• Where's the demand for this in current canton ecosystem.
• Why a dev fund funding for this where we have many community built proposals earning via their usage and txns and not using dev fund ffor a grant.

Hey @Jatinp26 , my responses below:

• How'd this be different from already approved agent kit and wallet tool. Based on the publicly available information, our understanding is that the approved Agent Kit focuses on enabling agent development within applications and wallets. Our proposal addresses a different challenge: interoperability between independently operated institutional agents across multiple Canton domains.

Rather than providing another wallet or agent runtime, we provide an interoperability layer that allows independently operated institutional agents to discover, coordinate and participate in shared financial workflows under institution-defined permissions and user-controlled delegated authority. This solution leverages phone/SIM identity authentication allowing users to establish a persistent authorization relationship with autonomous agents.. Phone/SIM-backed identity is not intended to replace institutional KYC, but to provide a persistent user-controlled authorization anchor for agent delegation, recovery and accountability across institutional domains.

• Where's the demand for this in current canton ecosystem. The emergence of institutional AI agents creates a new interoperability problem. Institutions will increasingly deploy proprietary agents, but those agents will remain siloed unless a common orchestration framework exists.

We believe Canton is uniquely positioned to solve this problem because multiple regulated institutions can already coordinate shared workflows while maintaining private state.

Our collaboration with Lloyds, Vodafone and Chainlink demonstrates a real institutional workflow that cannot be solved by isolated platform agents alone. The workflow spans infrastructure providers, financial institutions and tokenized asset platforms. No single participant owns the entire workflow, making orchestration across institutional boundaries a core requirement rather than an optional feature.

We are currently working in a usage-based-finance initiative expanding the realm of RWA. The assets in use are available processing capacity of telco towers (38k towers in the UK only), where it is used for AI computing on the edge. The telco towers receive investments where they then subsequently share revenue with the investors. This is an institutional investment scheme where a traditionally conservative sector benefits from new financial instruments made available through blockchain technologies.

This demonstrates how Canton can unlock entirely new categories of institutional RWAs beyond traditional financial assets.

• Why a dev fund funding for this where we have many community built proposals earning via their usage and txns and not using dev fund ffor a grant. While our initial implementation is driven by the Lloyds/Vodafone/Chainlink initiative, the outputs of this work—including agent orchestration interfaces, delegated authorization models and cross-domain coordination mechanisms—are intended to become reusable infrastructure for the wider Canton ecosystem.

The dev fund funding for this initiative is absolutely essential as this expands the RWA narrative to infrastructure players that were normally excluded from innovative solutions and the nature of Canton’s business oriented approach to transaction processing meshes well with the highly regulated infrastructure sector which are desperate for more investment infusion. The grant is a very small outlay by Canton in order to expedite the realisation of this exciting opportunity. This work extends Canton into infrastructure sectors that have historically had little interaction with blockchain technology, creating opportunities for long-term institutional adoption beyond existing digital asset use cases.

We are building an agentic orchestration framework leveraging phone number and sim based identity authentication allowing users to coordinate autonomous financial workflows across multiple institutional applications through a consistent orchestration layer.

We believe the next interoperability challenge on Canton is no longer asset interoperability, but autonomous workflow interoperability between independently operated institutional agents.

Building pairwise integrations between every institution does not scale. PillarX provides a common orchestration layer that avoids an N×N integration model by allowing each institution to integrate once and participate in interoperable workflows with many counterparties.

Rather than providing another wallet or agent runtime, we provide an interoperability layer that allows independently operated institutional agents to discover, coordinate and participate in shared financial workflows under institution-defined permissions and user-controlled delegated authority. This solution leverages phone/SIM identity authentication allowing users to establish a persistent authorization relationship with autonomous agents.. Phone/SIM-backed identity is not intended to replace institutional KYC, but to provide a persistent user-controlled authorization anchor for agent delegation, recovery and accountability across institutional domains.

What would this mean security wise esp for enterprises and institutions?

We believe Canton is uniquely positioned to solve this problem because multiple regulated institutions can already coordinate shared workflows while maintaining private state.

Our collaboration with Lloyds, Vodafone and Chainlink demonstrates a real institutional workflow that cannot be solved by isolated platform agents alone. The workflow spans infrastructure providers, financial institutions and tokenized asset platforms. No single participant owns the entire workflow, making orchestration across institutional boundaries a core requirement rather than an optional feature.

We are currently working in a usage-based-finance initiative expanding the realm of RWA. The assets in use are available processing capacity of telco towers (38k towers in the UK only), where it is used for AI computing on the edge. The telco towers receive investments where they then subsequently share revenue with the investors. This is an institutional investment scheme where a traditionally conservative sector benefits from new financial instruments made available through blockchain technologies.

My Que was specific to canton ecosystem currently, about any data or feedback or anything that indicates the demand of this by any player in the existing ecosystem.

The dev fund funding for this initiative is absolutely essential as this expands the RWA narrative to infrastructure players that were normally excluded from innovative solutions and the nature of Canton’s business oriented approach to transaction processing meshes well with the highly regulated infrastructure sector which are desperate for more investment infusion. The grant is a very small outlay by Canton in order to expedite the realisation of this exciting opportunity. This work extends Canton into infrastructure sectors that have historically had little interaction with blockchain technology, creating opportunities for long-term institutional adoption beyond existing digital asset use cases.

We are building an agentic orchestration framework leveraging phone number and sim based identity authentication allowing users to coordinate autonomous financial workflows across multiple institutional applications through a consistent orchestration layer.

We believe the next interoperability challenge on Canton is no longer asset interoperability, but autonomous workflow interoperability between independently operated institutional agents.

Building pairwise integrations between every institution does not scale. PillarX provides a common orchestration layer that avoids an N×N integration model by allowing each institution to integrate once and participate in interoperable workflows with many counterparties.

If dev fund covers only small part of its working, so need some info here:

• How much of this is already build? Have you taken funding before from any other chain for giving this infra.
• Dev fund is for free opensource public good, so if fund covers small part of it then will this still be open to be used by all as opensource public good tool?

Before voting: My verdict is still in confusion of demand and build of this as this shows mostly market narrative but not clear demand in existing canton ecosystem, need clarity on that.

What would this mean security wise esp for enterprises and institutions? This works along with the KYC/KYB already done by institutions such as Lloyds. The phone number verification, will allow KYCed users of Lloyds spin up verified agents that perform specific tasks.

Example, a Lloyds user purchases an RWA token and they want to trade that on a different Canton ecosystem dapp. The solution enables them to setup an agent that orchestrates the communications between the two different domains (Lloyds and another canton ecosystem secondary market/dapp). So that the user, sees a unified UX, where there will have a single agent that automates the whole process.

My Que was specific to canton ecosystem currently, about any data or feedback or anything that indicates the demand of this by any player in the existing ecosystem.

We are working with Lloyds, Chainlink and Vodafone to build this on Canton. They are the Canton ecosystem institutional players I was referring to earlier.

If dev fund covers only small part of its working, so need some info here:

• How much of this is already build? Have you taken funding before from any other chain for give this infra.
• Dev fund is for free opensource public good, so fund covers small part of it then will this still be open to be used by all as opensource public good tool?

• Pillar wallet is MIT licensed open-source wallet. It already supports 20+ EVM chains. All of our code is open-source and audited. Our repository is https://github.com/pillarwallet/x .We have already added support for Vodafone/Twilio phone number verification for user-onboarding. We are working on adding support for Canton and the ability to orchestrate agents from the wallet.
• We haven't accepted funds for building this set of things from any other chain.

We are working with Lloyds, Chainlink and Vodafone to build this on Canton. They are the Canton ecosystem institutional players I was referring to earlier.

How that'd be useful for other players apart from these?? Any survey or research u did to show some data on adoption?

Pillar wallet is MIT licensed open-source wallet. It already supports 20+ EVM chains. All of our code is open-source and audited. Our repository is https://github.com/pillarwallet/x .We have already added support for Vodafone/Twilio phone number verification for user-onboarding. We are working on adding support for Canton and the ability to orchestrate agents from the wallet.

So majorly this is an integration dev fund request into your protocol?

How that'd be useful for other players apart from these?? Any survey or research u did to show some data on adoption?

These are features that other institutional players that want to adopt the Agentic framework have raised with us. These are institutions that are potential adopters of the Canton ecosystem. If your question is focusing on services that are operating wallets on Canton, no, we have not run a survey on them, but willing to do so if they are open to it. As accessing teams and eliciting response can be a challenge on its own.

So majorly this is an integration dev fund request into your protocol?

We are creating a framework for orchestrating authenticated Agents. This is not an integrating Dev fund but extending our opensource offering, mainly focused on web3 user base, to cover institutional clients and their users.

These are features that other institutional players that want to adopt the Agentic framework have raised with us. These are institutions that are potential adopters of the Canton ecosystem. If your question is focusing on services that are operating wallets on Canton, no, we have not run a survey on them, but willing to do so if they are open to it. As accessing teams and eliciting response can be a challenge on its own.

Yes, majorly any info that shows the existing demand of this in canton ecosystem as canton is already working with some of the major institutional players so anything that help point out adoption need for this would be helpful.

We are creating a framework for orchestrating authenticated Agents. This is not an integrating Dev fund but extending our opensource offering, mainly focused on web3 user base, to cover institutional clients and their users.

just to be clear, so this is to cover the commercial cost of your services to current canton ecosystem partners so they can use it for free, am i right?

just to be clear, so this is to cover the commercial cost of your services to current canton ecosystem partners so they can use it for free, am i right?

This is the cost for us to develop these features in an opensource manner and will also adapt what we have created for features we are building for commercial clients who stand to bring big volumes to Canton. Clients who have specific needs and utilising the opensource library we create to achieve them.

So please confirm that, once integration and setup is done by dev fund, all given services/features by your tooling will be free and for public good of the canton builders right? @ch4r10t33r

So please confirm that, once integration and setup is done by dev fund, all given services/features by your tooling will be free and for public good of the canton builders right? @ch4r10t33r

I can confirm that all features of the wallet will be open source under MIT license.