A technology and financial infrastructure group operating since 2019 across four registered jurisdictions, engineering artificial intelligence, cybersecurity, cloud, smart infrastructure and regulated payment systems for institutions and governments.
SWSS Chain is one programme within that company, the settlement layer its own products run on. This page sets out the group, its structure and its record, and publishes only what can be checked against a running system or a filed document.
SWSS Fintech engineers the systems that regulated institutions, governments and developers depend on: artificial intelligence, cybersecurity, cloud platforms, smart infrastructure and payments. SWSS Chain is one programme within that company, and the distinction matters to anyone assessing it.
The group's work is the unglamorous half of digital transformation: the settlement, identity, security and infrastructure layers that sit underneath whatever a client shows the public. That is delivered as enterprise engagements through six divisions, and it is the business that funded the protocol work rather than the other way around.
Because the company builds the infrastructure it sells, it also runs it. The public networks, the identity authority and the developer platform are operated by the same teams under the same release process, which is why a published figure on this page can be read from a running system instead of copied from a brochure.
One engineering organisation operating under four registrations, with counsel retained in each.
AI, cybersecurity, blockchain, cloud, smart infrastructure and regulated payments.
Money Services Business registration covering virtual currency, payment services and foreign exchange.
Enterprise delivery from the first year
Rolling availability across the public networks
Two legal entities carry the group's four offices. SWSS Foundation holds the parent in the British Virgin Islands and the engineering centre in Malaysia; SWSS Fintech holds the licensed payments entity in Canada and commercial operations in the United Kingdom. Each office exists for a reason, and the reason is written below it.
The British Virgin Islands entity is the parent of the group and the owner of its intellectual property, including the SWSS Chain protocol and the products that settle on it. Group-level governance, treasury policy and the mandate of every operating office are set here, and material counterparty agreements are executed at this level so that a single entity carries the obligation rather than a chain of local subsidiaries.
The Canadian entity holds the group's Money Services Business registration covering virtual currency services, payment service provision and foreign exchange. It is the office through which regulated payment flows are operated and supervised, which is why payment products are built against its compliance programme rather than against a general engineering standard. Its obligations, which cover identification, record keeping, reporting and ongoing monitoring, set the floor for identity handling across the whole ecosystem.
The London office carries European commercial operations: institutional relationships, enterprise delivery in the region and the engagement of local counsel. Counterparties in the United Kingdom and the European Economic Area contract with a locally advised presence and are supported in their own timezone, which matters more for enterprise procurement than it does for a protocol.
The Asia Pacific centre is the group's principal engineering hub, and the majority of its technical headcount sits here. Core protocol work, the product teams, security engineering and research are run from this office under one release process, which is what allows seventeen products to share an identity layer, a settlement standard and a single published source of facts instead of diverging into seventeen local decisions.
The group's revenue comes from enterprise engineering across six practices. They share architecture review, security standards and a single release process, so a client buying one division is buying the discipline of all six.
Applied artificial intelligence delivered into production systems rather than into pilots: custom models, enterprise language systems, predictive analytics and computer vision, built to run against a client's own data under their own governance.
Defensive engineering for organisations whose exposure is measured in regulatory consequence: continuous threat monitoring, security operations, identity and access management, and the hardening work that keeps an estate defensible after the project ends.
Distributed ledger engineering for enterprises, from private settlement networks to the public infrastructure the group operates itself. This is the division whose own long-running programme became SWSS Chain.
Multi-cloud architecture, infrastructure as code and delivery automation. The group runs its own public networks on this practice, so what is sold to clients is the same discipline that carries production traffic internally.
The physical layer: building management, industrial IoT, sensor networks and the real-time monitoring that turns a building or a plant into an instrumented asset with data a financial system can act on.
Payment gateway engineering and core banking modernisation, operated out of the group's registered payments entity. It is the division where regulated money movement and distributed settlement meet in the same system.
Nine sectors, each with its own regulatory weight and its own definition of acceptable downtime. Client names are theirs to disclose and are not published here.
Smart buildings, asset instrumentation and tokenised property settlement
Payment infrastructure, core modernisation and settlement rails
Smart city programmes, public registries and sovereign-grade identity
Digital health platforms and records engineering under strict privacy duty
Industrial IoT, plant telemetry and supply chain traceability
Smart grid systems, metering and consumption analytics
Commerce platforms, payment acceptance and loyalty systems
Connected vehicle data, provenance and dealer systems
Learning platforms and verifiable credential issuance
SWSS Chain is not the company. It is the settlement layer produced by one of the group's six divisions, and the layer the group's own identity, custody, asset and validator products are built on. The structure below is the honest shape of the thing being assessed.
SWSS Fintech was delivering enterprise systems before any of this settled on a chain, and it still does. The protocol was funded by that work rather than by a sale, which is why the divisions are the business and the network is infrastructure the business owns.
SWSS Chain is the output of the blockchain and decentralised systems division, the largest single programme the group runs, but one of six practices. Assessing the company by the network alone measures a part and calls it the whole.
Identity, custody, assets and validator operations are group products that settle on the group's chain. That makes the network a dependency of real systems with real users, not a venue waiting for someone else to build on it.
Every product below shares one identity authority, one settlement standard and one published source of facts. That is the group's actual asset: not seventeen separate applications, but seventeen that cannot contradict each other about who a user is or what a transaction did.
Every product authenticates through SWSS IVL, so a member is the same verified party in all of them.
DEED-1 and its Finality Certificates are the record format across the portfolio, not per product.
Versions, counts and parameters are published once from the content hub and read by every property.
Operating on the public networks today, with users and settlement behind them.
The settlement layer itself: EVM compatible, deterministic finality.
Pays for settlement and network operations, and secures the validator set.
Wallet, staking and treasury movement for members, under IVL identity.
Real world assets recorded and exchanged as DEED-1 instruments.
Validator onboarding and the parameters governing the operating set.
SDKs, contract templates and the documentation builders work from.
Asset transfer to and from external networks, validator secured.
Provably fair on-chain draws settled through the same rail.
Under active engineering against a published specification, not yet released.
Compute capacity issued and traded as a DEED instrument.
The applied intelligence platform the group's own systems call.
The reasoning core: four layers, jurisdiction aware, edge capable.
Merchant acceptance and borderless settlement at sub-second confirmation.
Scoped and documented in the roadmap, scheduled behind the work above.
Portable credentials and attestations anchored to IVL.
A browser-based simulation environment for real world asset flows.
Travel booking and loyalty settled on chain.
Non-custodial swaps with liquidity routing across protocols.
Parameter votes and treasury decisions, recorded on chain.
Six layers in production, each owned by a named team and released through one gated process. Every version below is read from the running network rather than written into this page, so what you see is what the chain reports about itself.
Four pillars, SAPE, DSA, PCA and BFTFA, producing deterministic finality rather than probabilistic confirmation.
The zero-knowledge layer, which lets a settlement be proven without exposing the parties or the amount.
SWSS IVL: authentication, KYC, KYB, credentials and signing, held apart from anything that moves value.
The deed transaction standard and its Finality Certificates, which is what makes an asset record citable.
The Transactional Settlement Levy and the supply retirement it drives, applied by protocol rather than by policy.
The 17 products that settle on the chain, sharing one identity authority and one source of facts.
Protocol versions are read from both networks every hour and published from one source, which exists because a version once sat five releases behind the chain for fifty-four days while every SWSS property quoted it. If a figure here disagrees with the chain, the chain is right and this page is a bug.
SWSS Coin is the native coin of the network, used to pay for settlement and network operations. The protocol mints no further supply after genesis, so every figure below is a share of a number that cannot grow.
SWSS. Every coin that will ever exist was created at genesis. Nothing is minted afterwards; the supply is held and released by contract against a published schedule.
Bars are drawn to the largest bucket so the ranking is readable; the percentage on each row is the share of total supply, and the right-hand column is that share expressed in coins.
Allocations are held and released by contract, not by discretion. A bucket cannot be moved because somebody decided it should be, and the contract is the same public artefact a reader can inspect.
Every bucket carries its own schedule, set out in the white paper. That document is the commitment; this page is a summary of it and does not vary from it.
Changes to allocation run through governance on the record, never through an operator acting alone. The process is the protection, and it is visible from outside.
These are protocol parameters, not a capitalisation table. The allocation above governs the network's native coin and carries no ownership interest, voting right or economic claim in SWSS Fintech or any entity in the group. Corporate ownership is a separate matter and is not published here.
The group's record, not the protocol's alone: the company, its divisions and the network, in the order they actually happened. Forward plans are published separately on the roadmap and are not restated here. This section records what can be asked for and confirmed.
SWSS Fintech is established and the settlement problem is defined, starting the consensus research that everything since has been built on.
Delivery teams, the platform and the core technology stack are put in place, and the group begins shipping enterprise systems.
The artificial intelligence and analytics practices open, and the first working consensus prototypes run against a private network.
Cloud engineering becomes a division in its own right and the group's delivery portfolio widens across sectors.
External builders reach the network for the first time and the deed settlement standard lands, alongside expansion into new verticals.
Registration across the four jurisdictions completes, and SwssChain mainnet enters production carrying real settlement.
Identity, wallet, explorer and the developer platform reach production alongside the chain, operated by the same teams under one release process.
The Settlement Combustion Model and the zero-knowledge privacy layer enter production, and the published facts begin syncing from the networks themselves.
Regulated activity sits in the entity licensed to perform it, and the authorities inside the ecosystem are deliberately held apart so that no single component can both establish who someone is and move what they hold.
The group's Canadian entity holds a Money Services Business registration covering virtual currency services, payment service provision and foreign exchange. Regulated money movement is operated through that entity and against its compliance programme. Identification, record keeping, reporting and ongoing monitoring in turn set the floor for how identity is handled everywhere else in the ecosystem.
Systems are built against the control frameworks their sector requires, so that a client's own audit finds the evidence it expects where it expects it. Framework alignment is an engineering standard and is stated as such; it is not a representation that the group holds a certificate against each one.
Four authorities, four domains, no overlap. Each owns its domain completely and holds nothing belonging to the others.
Authentication, KYC, KYB, credentials and signing. IVL holds no balance, stakes nothing and bridges nothing: it establishes who a party is and signs what that party approves.
Wallet operations, staking, treasury movement and bridging. Everything a member's holdings do happens here, under the identity IVL has established and never inside it.
The DEED-1 instruments, their records and the exchange data around them. Asset truth is owned here and nowhere else in the ecosystem.
Validator onboarding, the operating set and the parameters that govern it. Who may produce a block is decided in one place, on the record.
The platforms the group's systems are engineered on and operated through: compute, network edge, orchestration, data and observability. Listed as the engineering record of what is under production, not as an endorsement by any vendor named.
Vendor marks are the property of their respective owners and appear here for identification only.
The specification, the policies and the public ledger. Nothing on this page asks to be believed without one of them, and anything a reader cannot find below can be requested from the desk at the end of the page.
Chain IDs, block time, consensus versions and uptime can all be read directly from the public networks. Where this page and the chain disagree, the chain is right.
Corporate information, documentation and questions about the group's entities, its registrations and the networks it operates, routed to the office that owns the answer.
For corporate information, documentation requests, and questions about the group, its registered entities and the networks it operates. Enquiries are answered by the office responsible for the subject rather than by a central mailbox.
Corporate Information
Entities, registrations, structure
Documentation
Specification and policy requests
Handled In Confidence
No distribution beyond the desk
Direct Contact
This page is published for information only. It is not an offer to sell, or a solicitation of an offer to buy, any security, coin or financial instrument, and nothing on it constitutes investment, legal, tax or financial advice.
SWSS Coin is the native coin of the SWSS Chain network, used to pay for settlement and network operations. No return, yield, profit or appreciation is promised, projected or implied by anything on this page, and past or present network metrics are not an indication of future outcomes. Supply allocation is a protocol parameter and confers no interest in any entity in the group.
Statements about work in development or planned reflect present intention and are not commitments to deliver on any date. Framework alignment described above is an engineering standard and is not a representation that a certification is held against each framework named.
Distributed ledger technology carries risk, including the total loss of value. Before any decision, read the Risk Disclosure and the white paper, and take your own professional advice.