Skip to content
CCPEDIAby Unity Nodes
Mailing Lists/Validator Operator Batch Approvals: Bulls Eye Technologies, Cantield Labs Inc, CFi Solutions, Inc., Crosslynx Technologies Private Limited, CRX, Decenter R&D, fromjava, Klariq Technologies Limited, Lithium Digital Limited, Old Block Ventures, P2P Company, RAW Protocol, Inc, SEA CAPITAL, Skopino, Solido Money Corp, STAKR.space, Zephr Technologies.Source on lists.sync.global ↗

Validator Operator Batch Approvals: Bulls Eye Technologies, Cantield Labs Inc, CFi Solutions, Inc., Crosslynx Technologies Private Limited, CRX, Decenter R&D, fromjava, Klariq Technologies Limited, Lithium Digital Limited, Old Block Ventures, P2P Company, RAW Protocol, Inc, SEA CAPITAL, Skopino, Solido Money Corp, STAKR.space, Zephr Technologies.

tokenomics-announce0 messages
  1. #1Pedro Neves19-08-2026source ↗

    Validator Approval

    Congratulations on having your validator approved! We're very excited to have you spin up your validator node and join us online. Please find the next steps below. Feel free to reach out with any questions.

    IP Whitelisting

    For IP whitelisting requests, please fill this form.

    Important: Whitelisting is required for your validator node to communicate with the network environments.

    Deploy Your Validator

    • Set up your own node using the public docs - TestNet / MainNet.

    • Alternatively, ask one of our partners to spin up your validator node today. Reach out via email to any of them for more information.

    Note: Partner deployment can significantly speed up setup if you prefer a managed approach.

    MainNet Allocation

    We currently have a waitlist for deploying to MainNet, please wait for an allocation.

    We recently implemented a weekly validator allocation process to manage access. The current policy prioritizes "GTM-ready" projects—those with functional builds on DevNet or TestNet ready for immediate MainNet activation.

    • Current capacity: 50 validators per week

    • Allocations processed: every Wednesday

    For more details on the specific requirements and how the queue is managed, please refer to:

    Important: You will not be able to proceed to MainNet without an official allocation.

    High-Level Steps

    DevNet

    • Spin up your node on DevNet

    • Share the fixed IP you'd like whitelisted on DevNet for your Validator node with your SV sponsor

    • Spin up your node for DevNet

    • Request a DevNet onboarding secret - via API call (curl)

    Tip: Ensure your node is fully functional on DevNet before progressing.

    TestNet

    • Spin up your node on TestNet

    • Share your fixed IP you'd like whitelisted on TestNet for your Validator node with your SV sponsor

    Tip: TestNet readiness is a key signal for MainNet prioritization.

    MainNet

    • Spin up your node on MainNet

    • Reach out directly to your SV sponsor to request a MainNet onboarding secret after you have an allocation

    Important: Your MainNet onboarding secret will only be issued after allocation is granted, and must be requested directly from your SV sponsor before your node can join MainNet.

    Stay Connected

    There are a few other mailing lists you might consider joining to stay updated:

    Socials

    Get social with us on LinkedIn or X.

    Tip: Following updates helps you stay informed about network changes, allocations, and announcements.


    Total submissions in this batch: 17


    Bulls Eye Technologies

    Name of Applying Institution:
    Bulls Eye Technologies

    URL to website of Applying Institution:
    https://rebal.cc

    Applying Entity / Institution Description:
    We are building Rebal, an autonomous portfolio rebalancing engine that facilitates users to set target allocations across Canton-native assets, define a drift band, and Rebal rebalances the moment the band breaks by settling the minimum set of legs needed to return the portfolio to mandate.

    Reason for Applying to Operate a Validator:
    A rebalancing mandate that fails mid-execution leaves a portfolio in an unintended state. Atomic settlement is the core product guarantee and it depends entirely on the execution environment being reliable and under our control. A third-party validator introduces the exact availability risk that breaks the all-or-nothing settlement promise we make to every desk running a live mandate.

    The privacy model reinforces this further. Every rebalance reveals portfolio composition to the infrastructure processing it. Our own validator means that information stays within our controlled node and never reaches a third party by construction rather than by policy.

    Expected Contributions to the Network:
    We plan to publish our playbook library and Daml mandate templates openly after audit so other Canton builders can use the same rules-based allocation framework as a foundation for their own portfolio products.

    How did you hear about Canton / the validator program?
    AIC IIT Delhi

    Country of Incorporation:
    India


    Cantield Labs Inc

    Name of Applying Institution:
    Cantield Labs Inc

    URL to website of Applying Institution:
    https://cantield.xyz

    Applying Entity / Institution Description:
    Cantield is a yield vault protocol on Canton Network. Deposits are routed into tokenized treasuries and short-duration credit with collateral that is verifiable on-chain and yield paid entirely from real interest income with no emissions schedule inflating the number.

    Reason for Applying to Operate a Validator:
    We make a specific promise to every depositor which is that their collateral is verifiable on-chain and their yield settles in under a second. Both of those promises depend on the execution environment being reliable and fully under our control. A third-party validator puts both at risk. Vault operations including rebalancing between collateral types, yield distribution across depositors, and collateral state updates all need to execute on a consistent and dependable infrastructure layer. We cannot make guarantees to depositors about settlement finality and then outsource the infrastructure that delivers that finality to someone else.

    Expected Contributions to the Network:
    We will publish our vault and collateral architecture openly so other Canton builders can use the same model as a foundation for their own yield products.

    How did you hear about Canton / the validator program?
    We came across Canton Network while researching settlement infrastructure for yield products backed by real-world assets.

    Country of Incorporation:
    Canada


    CFi Solutions, Inc.

    Name of Applying Institution:
    CFi Solutions, Inc.

    URL to website of Applying Institution:
    http://www.cfi.ag

    Applying Entity / Institution Description:
    Agricultural finance company enabling farmers finance seed, fertilizer and chemicals at point of sale/purchase.

    Reason for Applying to Operate a Validator:
    CFi originates and administers agricultural input loans (~$250M+ utilized in 2026) and plans to represent those loans on Canton, then settle payments, then issue them as digital securities to capital providers. Because we are a party to every loan contract and our records contain farmer credit data, we need to hold our own keys, sign our own transactions, and keep that data on infrastructure we control. Our capital partners and future investors will also expect CFi to control its records directly rather than depend on a third party's node.

    Expected Contributions to the Network:
    We plan to build applications on Canton that bring agricultural loans on-chain - first representing our $250M+ portfolio, then payment settlement, then tokenized loan securities — and to introduce our counterparties (Farm Credit institutions, capital providers, agricultural retailers) to the network along the way.

    How did you hear about Canton / the validator program?
    Direct introduction to Vivek.

    Country of Incorporation:
    USA


    Crosslynx Technologies Private Limited

    Name of Applying Institution:
    Crosslynx Technologies Private Limited

    URL to website of Applying Institution:
    https://opaq.cc

    Applying Entity / Institution Description:
    OPAQ is a private CDP lending protocol on Canton Network. Users lock collateral including Canton Coin, tokenized T-bills, tokenized deposits and Canton-wrapped BTC and ETH, then mint USDo, an overcollateralized stablecoin, against it. Collateral, debt and liquidation price live inside one Daml contract with two signatories, so no other node ever receives it and there is no dataset for a liquidation bot to index.

    Reason for Applying to Operate a Validator:
    We prefer to operate ourselves because liquidation determines whether the protocol stays solvent. The Liquidate choice has to execute at oracle price the moment a position breaches its ratio, in one transaction, with no delay, and an external operator adds latency and availability risk to the one operation where neither is survivable. A late liquidation is bad debt against USDo and every holder carries it. Privacy compounds the same argument. Every vault contract names two signatories and is delivered to two nodes, so running execution through infrastructure we do not control puts vault data on a node that was never meant to be party to it.

    Expected Contributions to the Network:
    USDo gives Canton a native overcollateralized stablecoin backed by Canton-native collateral rather than an asset bridged in from another chain. Every Canton application that needs a stable unit of account for settlement, swaps, repo or DvP can use it. Because tokenized T-bills and tokenized deposits are accepted collateral, growth in OPAQ is direct growth in demand for Canton's RWA infrastructure.

    How did you hear about Canton / the validator program?
    AIC IIT Delhi (Incubation)

    Country of Incorporation:
    India


    CRX

    Name of Applying Institution:
    CRX

    URL to website of Applying Institution:
    https://crxfx.com/

    Applying Entity / Institution Description:
    FX non-deliveranle forward venue

    Reason for Applying to Operate a Validator:
    CRX builds an FX derivatives clearing application on Canton and we already run the full stack locally, so operating a validator is work we do today. Our clients' trade data and signing keys must stay on our own node, not with a third-party operator.

    Expected Contributions to the Network:
    Launch our FX derivatives clearing app on Canton and bring our FX market makers onto the network.

    How did you hear about Canton / the validator program?
    via an Introduction

    Country of Incorporation:
    United States of America


    Decenter R&D

    Name of Applying Institution:
    Decenter R&D

    URL to website of Applying Institution:
    https://www.decenter.com

    Applying Entity / Institution Description:
    Decenter R&D is a research and development centre and project incubator that has been building on public blockchains since the early days of DeFi. Our main product is Heat, a self-funded, non-custodial application for creating and managing derivatives positions, used globally and best known for pioneering trustless automated strategies, meaning automated liquidation protection and leverage management that execute without users handing over custody. We have also built and shipped analytics tooling.

    Reason for Applying to Operate a Validator:
    We have run production blockchain infrastructure continuously for several years. We already operate node infrastructure, monitoring and on-call practices where downtime and correctness have direct financial consequences for users. Running a validator is a smaller operational commitment than what we already do daily.

    We would prefer to operate our own node because we are doing protocol-level R&D rather than consuming an existing application. That work needs control the hosted route does not give us: uploading and re-uploading our own DARs as they change, allocating and managing parties freely, testing against different Splice versions to see what upgrades do to our package IDs, and iterating many times a day without waiting on someone else's operations team. Relying on a third party for DAR uploads and party allocation would make our development loop hours long instead of minutes.

    Expected Contributions to the Network:
    First, by building. We are working on applications on Canton and will keep going; running our own node is what makes that sustainable.

    Second, by bringing developers across. We have spent years in the Ethereum and DeFi developer community and know a lot of teams there. Very few have looked seriously at Canton, mostly because Daml and the privacy model look unfamiliar rather than because they are hard. We are well placed to translate between the two worlds and intend to write up what we learn, the parts that surprised us and the parts the docs do not cover yet, and to onboard more of our own developers.

    Third, by feeding back. Coming from a completely different stack, we hit rough edges that people already inside the ecosystem have stopped noticing. We would rather report those than work around them quietly.

    How did you hear about Canton / the validator program?
    ETH CC Cannes

    Country of Incorporation:
    Serbia


    fromjava

    Name of Applying Institution:
    fromjava

    URL to website of Applying Institution:
    https://fromjava.id

    Applying Entity / Institution Description:
    We are an e-commerce platform in the furniture sector. Here, we want to be part of the canton for implementing payments on our website so that it can be realized for all countries where web3 has become part of the world economy, so we want to reach several countries for export, especially abroad.

    Reason for Applying to Operate a Validator:
    As a developer, I already understand the world of web3 and also have a web3 background for the past few years, so I remain committed to this belief.

    Expected Contributions to the Network:
    build applications

    How did you hear about Canton / the validator program?
    I understand from several platforms especially on Twitter

    Country of Incorporation:
    indonesia


    Klariq Technologies Limited

    Name of Applying Institution:
    Klariq Technologies Limited

    URL to website of Applying Institution:
    https://klariq.xyz

    Applying Entity / Institution Description:
    Klariq is autonomous compute infrastructure for institutions that cannot be seen shopping for GPU capacity. Every job is a bilateral Daml contract between workload operator and hardware provider with exactly two readers and no others. Provider agents bid privately, an SLA oracle verifies delivery against the contract, and payment releases atomically the instant the SLA clears. No escrow, no invoicing, no counterparty trust required. Every agent operates within mandate limits enforced at the ledger level so institutions can delegate compute procurement autonomously without giving agents unlimited reach. The venue asset managers, banks and clinical research institutions can use without putting their model roadmap on a ledger their competitors can read.

    Reason for Applying to Operate a Validator:
    The privacy guarantee Klariq makes is architectural. Every compute contract contains exactly two parties and the data in that contract never reaches any node that is not one of them. The moment we route execution through a third-party validator we have introduced a third reader into a system built around the absolute exclusion of third readers. That is not a risk we can manage around. It is a structural contradiction in the product itself.

    Beyond that our settlement model is atomic delivery versus payment. The SLA oracle must verify and sign delivery before the payment choice can execute. That sequence depends on our execution environment being available, consistent, and under our direct control. A missed verification window means an unreleased payment which means a broken SLA for an institutional client who has a regulator to answer to.

    Our team includes a blockchain engineers, full-stack developers and backend engineers in house. We have the capacity to operate this infrastructure to the standard institutional clients will hold us to.

    Expected Contributions to the Network:
    Klariq brings a category of participant to Canton that no other application is targeting which is institutions that cannot touch a public marketplace for regulatory or competitive reasons. Every asset manager, bank, insurer, or sovereign fund that routes compute through Klariq is a Canton participant that would never have arrived through a DeFi application or a public token market. They come because Canton is structurally the only network that satisfies their procurement, risk, and regulatory requirements at the same time.

    We also bring a new class of hardware provider to Canton. Enterprise clusters sitting idle between training runs have no trusted venue to sell those hours institutionally today. Every provider we attest and onboard is new Canton infrastructure and new Canton economic activity that did not exist before. As we grow both sides of the market we plan to introduce our institutional operator and provider network to the Canton Foundation directly and will publish our bilateral contract model and mandate architecture openly so other Canton builders can apply the same pattern to their own institutional infrastructure products.

    How did you hear about Canton / the validator program?
    Apps Factory

    Country of Incorporation:
    England


    Lithium Digital Limited

    Name of Applying Institution:
    Lithium Digital Limited

    URL to website of Applying Institution:
    https://www.lithiumdigital.com/

    Applying Entity / Institution Description:
    Uk based blockchain infrastructure company, existing Canton Network validator operator, and operator of Cauri Wallet, a non-custodial Canton wallet and Featured App.

    Reason for Applying to Operate a Validator:
    Lithium Digital already operates a validator on the Canton Network and is seeking a Third validator to support Cauri Wallet, its Featured Application.

    Expected Contributions to the Network:
    Build more applications, expand Cauri Wallet’s capabilities, and support issuers and ecosystem participants.

    How did you hear about Canton / the validator program?
    Existing Canton Network validator operator and ecosystem participant.

    Country of Incorporation:
    United Kingdom


    Old Block Ventures

    Name of Applying Institution:
    Old Block Ventures

    URL to website of Applying Institution:
    https://dyad.exchange

    Applying Entity / Institution Description:
    We (DYAD) are a concentrated liquidity AMM where every swap is a bilateral Daml contract naming exactly two parties as signatories and readers. Pool depth, trade size, execution price, and counterparty identity are structurally absent from the rest of the network by construction rather than by cryptography. A fund rotating out of AAPL (apple) into USDCx executes a private contract between two participant nodes and nothing else exists on the ledger for anyone else to observe.

    Reason for Applying to Operate a Validator:
    The privacy model depends on a swap projection reaching exactly two participant nodes and stopping there. A third-party validator is a third node in a contract built around the absolute exclusion of third parties. That is not a risk we manage around. It makes every privacy guarantee we make to institutional desks technically false.

    Expected Contributions to the Network:
    DYAD creates the first swap venue on Canton where LP positions and trade data are structurally private. Every institutional block trade that flows through DYAD is a Canton settlement transaction from real economic activity that could not happen on any public chain without leaking intent to the market. Asset managers, market makers, and corporate treasuries that currently cannot use on-chain venues for size are net new Canton participants the moment they can.

    How did you hear about Canton / the validator program?
    T-Labs Venue

    Country of Incorporation:
    Singapore


    P2P Company

    Name of Applying Institution:
    P2P Company

    URL to website of Applying Institution:
    https://p2p.company

    Applying Entity / Institution Description:
    Multi party based Escrow system for p2p deals of Bitcoin and CC

    Reason for Applying to Operate a Validator:
    Already built a one way p2p market which got more than $50K in volume in few days, now looking to scale that infra to higher and privacy based trustless system.

    Expected Contributions to the Network:
    build applications

    How did you hear about Canton / the validator program?
    Google

    Country of Incorporation:
    India


    RAW Protocol, Inc

    Name of Applying Institution:
    RAW Protocol, Inc

    URL to website of Applying Institution:
    https://rawproto.com

    Applying Entity / Institution Description:
    settlement infrastructure company building the verified-delivery layer for the compute economy

    Reason for Applying to Operate a Validator:
    RAW Protocol is a verified-delivery and settlement layer for AI compute built natively on Canton: our application anchors edge-signed delivery telemetry on-ledger and settles compute contracts against it. For us, the validator is part of the product's trust chain, not an infrastructure convenience. Delivery records and settlement anchors are counterparty-sensitive, and settlement in our system is gated on continuous anchored telemetry, so validator availability and signing integrity are product guarantees. Keeping the node under the same operational control as the rest of our verification pipeline, rather than routing it through a third party, preserves that chain end to end. On qualification: RAW is built by the founding team of Hive OS, software that managed 5M+ devices across 180+ countries and, at its peak, roughly 70% of Ethereum hashrate before the merge, alongside in-house Canton/Daml engineering. Running distributed, high-availability, key-custodial infrastructure at global scale is our core competence. Using an external operator would mean outsourcing the one thing we do best.

    Expected Contributions to the Network:
    Build applications

    How did you hear about Canton / the validator program?
    from our network

    Country of Incorporation:
    United States of America


    SEA CAPITAL

    Name of Applying Institution:
    SEA CAPITAL

    URL to website of Applying Institution:
    https://www.sea-capital.xyz

    Applying Entity / Institution Description:
    capital and advisory firm investing in Southeast Asia's frontier industries ecotourism, sustainable fishing, artificial intelligence, natural resources, and human capital bridging innovative business with environmentally conscious growth across the region.

    Reason for Applying to Operate a Validator:
    We are building out use cases around tokenizing real-world assets and value flows in sectors such as sustainable fishing and natural resources across Southeast Asia, where transparent, verifiable settlement can strengthen trust and open up new capital access. We maintain a small in-house development team and prefer to self-operate our validator so we can directly build and test against Canton's infrastructure as we develop these use cases, rather than depending on a third-party operator for uptime, key custody, and performance.

    Expected Contributions to the Network:
    We plan to explore and build real-world asset use cases from sectors like sustainable fishing and natural resources onto Canton, and introduce partners and operators from our Southeast Asia network to the Canton Foundation as our involvement in the ecosystem grows.

    How did you hear about Canton / the validator program?
    Influencer or Community on X

    Country of Incorporation:
    Singapore


    Skopino

    Name of Applying Institution:
    Skopino

    URL to website of Applying Institution:

    Applying Entity / Institution Description:
    We are a Web3-native team exploring token settlement infrastructure. We've spent time studying Canton's architecture and its approach to privacy-enabled interoperability, and we see strong long-term potential in the network as a settlement layer for tokenized assets.

    Reason for Applying to Operate a Validator:
    Our team has hands-on experience with Web3 infrastructure and a specific interest in token settlement use cases. Operating our own validator gives us direct control over our infrastructure costs and configuration, which is particularly important during this exploratory phase, as we are testing settlement flows and want to closely observe and tune performance and cost characteristics firsthand rather than relying on a third-party operator. Running our own node also lets us build the operational expertise we'll need as we move from testing toward production use cases.

    Expected Contributions to the Network:
    As we validate token settlement use cases on Canton, we plan to share learnings from our testing with the ecosystem and, longer-term, contribute as an Application on the Network.

    How did you hear about Canton / the validator program?
    Through our own research into token settlement infrastructure across the broader Web3 ecosystem.

    Country of Incorporation:
    Germany


    Solido Money Corp

    Name of Applying Institution:
    Solido Money Corp

    URL to website of Applying Institution:
    https://solido.money

    Applying Entity / Institution Description:
    Solido Money is a DeFi platform building financial applications and liquidity infrastructure. Solido develops products across lending, stablecoin liquidity, and yield, and is expanding its infrastructure and applications to the Canton Network.

    Reason for Applying to Operate a Validator:
    Solido Money develops and operates DeFi applications and has experience managing production blockchain infrastructure supporting financial products.

    As we expand our applications to the Canton Network, operating our own validator will allow us to maintain direct control over the infrastructure supporting our applications, including deployment, monitoring, operational security, and integration with our application stack.

    Given that the validator will form part of the infrastructure underlying Solido's Canton applications, we believe direct operation is preferable to outsourcing this responsibility to an existing operator. This gives our engineering team greater control over availability, security policies, upgrades, incident response, and future application integrations while allowing us to build deeper operational expertise within the Canton ecosystem.

    Expected Contributions to the Network:
    Solido plans to build and deploy DeFi applications and financial infrastructure on the Canton Network, including products across lending, liquidity, stablecoins, and yield.

    Beyond operating our own applications, we intend to contribute by bringing existing users and liquidity into the Canton ecosystem, integrating with other Canton-native applications and assets, and supporting greater composability between financial products across the network.

    How did you hear about Canton / the validator program?
    Through our involvement with and ongoing development within the Canton Network ecosystem.

    Country of Incorporation:
    Panama


    STAKR.space

    Name of Applying Institution:
    STAKR.space

    URL to website of Applying Institution:
    https://stakr.space

    Applying Entity / Institution Description:
    independent professional multi-chain validator, securing blockchains since May 2020, having millions of dollars in staked assets and decentralized infrastructure validating Solana, ETH, EigenLayer, Symbiotic, Hyperliquid, Doublezero, Monad, Fermah, Aztec, and others.

    Reason for Applying to Operate a Validator:
    We already passed KYB in 2025 and would start developing on Canton Network

    Expected Contributions to the Network:
    build applications, introduce projects to the Foundation, apply the expertise and promote the chain

    How did you hear about Canton / the validator program?
    ETHcc

    Country of Incorporation:
    UK


    Zephr Technologies

    Name of Applying Institution:
    Zephr Technologies

    URL to website of Applying Institution:
    https://www.zephrtech.xyz

    Applying Entity / Institution Description:
    Zephr is an agentic collaboration network where each member owns a personal AI agent that routes work to a network of specialist agents, including other members' agents. Every agent runs its own wallet with tiered spend limits, dual-certificate identity verification, and a real-time audit trail. The product is currently in invite-only private beta.

    Reason for Applying to Operate a Validator:
    Zephr provisions every member a personal agent with its own wallet, tiered spend limits and a dual-certificate identity, and that agent delegates paid work to specialist agents across the network — including other members' agents. Payments therefore clear between independent parties, autonomously, inside a live workflow. Canton lets us express exactly that: spend tiers, approval thresholds and settlement finality encoded as Daml contracts, with each agent-to-agent payment visible only to its counterparties rather than to the whole network. We prefer to self-operate because micro-payments settle mid-task, so uptime and latency cannot depend on a shared endpoint we cannot tune or debug. Key custody and identity binding are already the core of our security model, and building our own Daml templates requires direct Ledger API and party management access rather than a restricted managed endpoint.

    Expected Contributions to the Network:
    We plan to build Zephr's agent payment and identity layer natively in Daml: per-agent wallets, tiered spend limits, owner approval for high-value actions, and escrow so a specialist agent is paid on delivery. We will publish an open-source Canton adapter that lets autonomous agents transact safely with scoped permissions and action budgets, and contribute feedback on the validator stack and the token standard around agent identity and programmable spend authorization.

    How did you hear about Canton / the validator program?
    dorahack and other dev

    Country of Incorporation:
    India