Answers, in plain English.

No. 4orm Finance is institution-grade infrastructure for real-world assets: tokenized bonds, tokenized deposits, real estate, private credit, resource and infrastructure assets. It does not list speculative crypto-assets, does not serve retail traders, and does not custody bearer assets outside of a regulated perimeter.

It means issuing a digital certificate of ownership for a real asset (a bond, a building, a loan, a deposit) on a shared ledger, with the rules of ownership built into the certificate itself. Transfer restrictions, KYC requirements, eligibility, and settlement instructions all live inside the token. The token is not the asset. It is the registered, programmable claim on the asset.

Canadian institutions today rely on correspondent banking chains, SWIFT messaging, T+2 settlement cycles, and parallel statutory reporting to FINTRAC and the CSA. That stack works but it is slow, expensive, and produces no single canonical record of a trade. The Bank of Canada's Project Samara (March 2026, $100M tokenized bond with RBC, TD, and EDC) validated that a Canadian-anchored DLT rail can settle the same instruments atomically. 4orm Finance is the regulated rail that operationalizes that pattern at scale.

Kinexys (formerly Onyx) is a J.P. Morgan-operated network that has cleared over $1.5T in tokenized cash and intraday repo. It is excellent infrastructure, but it is bank-owned, U.S.-anchored, and built for J.P. Morgan's counterparty universe. 4orm Finance is the Canadian equivalent: neutral and multi-institution by design, anchored in Canada under Canadian regulation, structured so no single bank owns the rail.

Three things. First, it removes settlement risk: the asset and the cash change hands at the same instant or the trade fails cleanly. Second, it eliminates trapped liquidity that today sits in transit or as collateral buffers across a two-day cycle. Third, it collapses the reconciliation overhead: a single canonical ledger entry replaces parallel records at each counterparty and intermediary. For a mid-size Canadian bank, those three together free up working capital that today is locked inside Nostro and Vostro accounts.

4orm Finance Holdings Inc. is a Canadian-incorporated entity, governed independently of any single bank. The technology is developed and licensed by KCS Capital, an independent Canadian institutional finance and research firm. The legal structure is HoldCo / OpCo / CustodyCo, the three-entity configuration required by the CIRO Digital Asset Custody Framework Tier-2 target.

4orm is engaging with CIRO (marketplace and custody), CSA (Project Tokenization), OSFI (banking-aligned settlement), and FINTRAC (AML/ATF) on a coordinated pathway. The sandbox application is targeted for Q3 2026. The custody entity is structured against the CIRO Digital Asset Custody Framework Tier-2 target from day one. All regulator engagement is conducted in writing and on the record.

At present, no. 4orm Finance is a sandbox-stage platform in development. The roadmap requires CSA recognition as a marketplace, CIRO membership as a member-firm operator, and a Trust and Loan Companies Act charter (or equivalent provincial trust authority) for the custody entity. Each of those is an explicit milestone, not a side project, and each will be announced when achieved.

All transaction data, identity attestations, audit logs, and ledger state remain inside Canadian sovereign data residency. The technology stack is operated on Canadian-anchored infrastructure. Cross-border data flows, where they exist, are limited to non-identifying telemetry and follow the same residency rules as Canadian banks today.

Statutory filings remain the institution's responsibility. 4orm Finance does not file on behalf of members. What changes is the underlying record: instead of each institution generating its own reconciled view of a trade, the canonical ledger entry is the same record both sides reference. STR, LCTR, and EFTR obligations continue to apply. The platform makes the source data cleaner and timelier.

Personally identifying information is never written to the on-ledger record. KYC attestations are issued by qualified KYC providers and referenced by hash; the underlying PII remains inside the issuing institution under standard PIPEDA controls. Provincial private-sector privacy regimes (Quebec Law 25, Alberta PIPA, British Columbia PIPA) are addressed via residency and provincial data-handling controls in each pilot's data-processing agreement.

Where tokenized CAD is used as the cash settlement leg, yes, the platform integrates with whichever regulated stablecoin or bank-issued tokenized deposit the participating institution selects. 4orm is provider-neutral. Cash leg options include regulated stablecoins (e.g., Stablecorp's QCAD) and bank-issued tokenized deposits. Each participating bank chooses the cash asset that fits its regulatory posture.

No. The blockchain is the execution surface underneath; the regulated control plane stays with the institution. Banks integrate via standard rails: ISO 20022, APIs, and existing core banking and treasury systems. The deployment model is a closed-loop pilot first, never a big-bang migration. From the bank's perspective the integration looks much like adding a new clearing or correspondent connection, just one that settles atomically and produces a canonical record.

Three layers. (1) Connectivity: the bank's treasury or payments system connects over ISO 20022 messaging or REST APIs to a 4orm-side adapter. (2) Compliance hooks: the institution's existing KYC/AML provider issues attestations that 4orm references; sanctions screening can run on either side or both. (3) Settlement: the bank operates a node or uses a managed connection to read and write canonical ledger state. No core banking system replacement is required, and no bank-side database needs to be deprecated.

Atomic settlement runs in approximately twelve seconds end-to-end inside the current sandbox configuration, dominated by consensus finality and attestation. That timing is consistent with Project Samara's published Bank of Canada results. Throughput in the sandbox supports institutional-scale daily volume; production scaling targets are set against the published Payments Canada Real-Time Rail profile (build complete Q3 2025, launch 2026 to 2027).

4orm uses a permissioned, Canadian-anchored ledger stack with a Hyperledger-family foundation and ERC-3643 (permissioned token) compatibility for the asset layer. Selected components are open source under permissive licenses; the orchestration, compliance hooks, and custody layer are proprietary. Source review is available to participating institutions under NDA during the pilot phase.

4orm is a settlement rail for tokenized assets, not a payments rail. Where payments are required to fund or defund the platform, they continue to use Lynx, ACSS, or the upcoming Real-Time Rail as appropriate. The platform produces ISO 20022-compliant messages and reconciles cleanly against existing nostro, vostro, and clearing accounts during pilot operations.

Inside the bank's existing HSM infrastructure, or under a qualified Canadian custodian (e.g., Tetra Trust) for institutions that do not yet operate their own digital asset key custody. Signing material never leaves the institution or its qualified custodian, and key recovery follows the same governance procedures the bank already operates for SWIFT keys or RTGS access.

Verified, whitelisted institutional members only. Transfer rules are embedded in the token contracts; no bearer transfers, no anonymous wallets. KYC/AML credentials are reusable across the network so onboarding compounds rather than repeats. Retail counterparties are explicitly excluded from the regulated rail.

4orm settles in tokenized CAD. The cash leg is either a regulated Canadian-dollar stablecoin (e.g., Stablecorp's QCAD) or bank-issued tokenized CAD deposits, depending on the participating institution's preference and regulatory posture.

The platform operates atomic delivery-versus-payment. Either both legs settle in the same transaction or neither does. If either side cannot complete (insufficient balance, attestation failure, compliance flag), the trade is rejected and both balances remain untouched. There is no half-settled state. Disputes resolve against the canonical ledger entry, which is append-only.

Pilots typically reduce daily reconciliation breaks by 60 to 90 percent on the in-scope flow. The remaining recon work shifts from "matching two ledgers" to "validating the canonical entry against the institution's general ledger." Most pilots are able to reassign half a recon FTE per $5B in tokenized AUM after the first quarter of live operation.

Tokenized assets do not change the regulatory treatment of the underlying asset under the current OSFI framework. What changes is the working-capital efficiency: T+0 settlement reduces the size of nostro positions held against pending trades, reduces collateral buffers required for unsettled counterparty exposure, and improves intraday liquidity reporting accuracy. Institutions typically model 5 to 15 basis points of LCR improvement on the in-scope flow.

The canonical ledger is replicated across multiple Canadian data centres with active-active failover. RPO is zero (no committed transaction can be lost), RTO targets are under fifteen minutes. The platform's own runbook is reviewed against OSFI Guideline B-10 and the equivalent provincial-regulator continuity expectations annually. Each pilot includes a documented institution-side continuity plan.

The canonical ledger and the bank's tokenized positions on it are not 4orm's property. They are entries the institution itself owns and signs. In the event of 4orm winding down, member institutions retain full read and write access to their positions and to the canonical record, and a successor operator can be appointed by the governance council without forcing migration. This is by design and is a condition of the regulated-marketplace posture.

Issuers like exempt market dealers, real estate platforms, mining and energy projects, and private credit funds keep their dealer registration and asset specialization. 4orm provides the institutional bridge: bank counterparties, secondary liquidity, an institutional investor pool, and the secondary market needed to actually offload at scale. Revenue share is structured per pilot.

Through a discovery engagement and, when appropriate, a closed-loop pilot. Use cases include tokenized municipal debt, infrastructure revenue financing, sovereign and sub-sovereign instruments, and Crown-aligned tokenized programs that benefit from a Canadian-sovereign rail. Procurement follows the standard provincial or federal pathway; 4orm responds to RFIs and RFPs through the normal channels.

Typical pilot from kickoff to first settled in-scope trade is 12 to 16 weeks. Phase 1 (weeks 1 to 4): scoping, regulatory map, integration architecture. Phase 2 (weeks 5 to 10): technical integration, compliance hook testing, runbook drafting. Phase 3 (weeks 11 to 16): closed-loop live trades, daily reconciliation against existing systems, regulator briefings. After phase 3, the pilot either expands to additional flows or sunsets cleanly.

Pilots are priced on a fixed-fee basis covering integration, regulator engagement support, and the first three months of operation. Steady-state pricing is per-transaction at a per-trade fee materially below the all-in correspondent banking cost it replaces. Detailed pricing is shared under NDA during the discovery phase.

Yes. The pilot agreement includes an explicit sunset clause that allows the institution to walk away at the end of the pilot with no continuing obligation, no data lock-in, and a clean exit of any in-flight positions. The pilot is a discovery exercise, not a sales funnel.

An hour of executive sponsor time, a mutual NDA, and a single technical or compliance contact who can route follow-ups internally. That is enough to scope whether a pilot makes sense for your institution.

KCS Capital is the independent technology and research firm that develops the platform. 4orm Finance operates it as a separately incorporated, independently governed regulated entity, structured as HoldCo / OpCo / CustodyCo per the CIRO Digital Asset Custody Framework. The arrangement is contractual: KCS Capital licenses the technology to 4orm Finance under a long-term agreement, with safeguards against the technology vendor becoming a market participant in conflict with the platform's neutrality.

4orm Finance is in pre-seed, closing Q2 2026. Closed-loop pilots are opening throughout 2026. The architecture, custody framework, and regulatory pathway are in flight today. Production timing depends on regulatory sandbox progression and pilot results.

Pre-seed is a SAFE (Simple Agreement for Future Equity) on standard Canadian terms, raised into 4orm Finance Holdings Inc. The round is sized to fund regulator engagement, the sandbox application, the first two closed-loop pilots, and the founding technical team through to seed close. Detail is shared with qualified investors under NDA.

The founding team is on the Leadership page. KCS Capital is led by Mike Sammut, a Canadian institutional finance founder with operating experience across capital markets infrastructure. The 4orm Finance operating team is being assembled against the CIRO and OSFI fit-and-proper requirements for the marketplace and custody entities respectively.

Selectively. Current open priorities are: a Chief Compliance Officer with CIRO and CSA-side experience, a Head of Custody with qualified-custodian operating experience, and senior engineers with permissioned-ledger production experience. Inquiries to founders@kcs-capital.com.

For pilots and partnerships: the institutional waitlist. For investor inquiries: founders@kcs-capital.com. For compliance and regulator coordination: compliance@kcs-capital.com. For press: same address, mark the subject "Press."