The Organisation Behind SWSS Chain
How the company is led, how it decides, and what it is building toward. This page publishes functions and accountabilities rather than personal profiles, because what a counterparty needs to know is who answers for what.
SWSS Fintech was established in 2019 to build payment and enterprise systems for organisations operating across borders and sectors. In engagement after engagement we encountered the same structural problem. Counterparties agreed that a transaction had taken place, their systems recorded it differently, and the work of reconciling that difference became a permanent operating cost rather than an exception.
We concluded that the deficiency was not one of accounting practice. No shared record existed that both parties already trusted, and the components required to establish one, namely identity, custody, compliance and a settlement standard, were held by separate providers with divergent incentives. A settlement layer assembled from those parts inherits every assumption each of them has made.
Our decision was to build and operate all four within a single organisation, accountable for the result end to end. That decision determined the shape of the group: an enterprise engineering business across six divisions, a licensed payments entity, registration in four jurisdictions, and a Layer 1 network built rather than rented. SWSS Chain is one programme within that structure, and the company predates it by several years.
We publish only what can be independently verified. Protocol versions, network parameters and product counts shown across our properties are read from the running networks on a schedule rather than entered by hand, and where this page and the network differ, the network prevails. We regard that as a governance commitment rather than a technical convenience, and it is the undertaking by which we would prefer this company to be judged.
swss://founding-decisions5 recordsWhy The Company Is Built This Way
Five decisions taken at founding, and what each one costs us
Own The Settlement Layer
Build and operate a Layer 1, with our own client, validator set and upgrade path, rather than renting space on a network whose roadmap we do not control.
cost Consensus, client maintenance and validator operations become permanent obligations
Deterministic Finality
SCP and its four pillars, SAPE, DSA, PCA and BFTFA, so a settlement is final when the receipt is issued rather than probably final a few blocks later.
cost A bounded, coordinated validator set, harder to grow than an open race for blocks
The Deed Is A Protocol Object
DEED-1 and its Finality Certificates live inside the settlement standard, so an asset record is something the chain understands rather than something an application asserts.
cost A public standard to maintain, version and defend, permanently
Identity Signs, Custody Moves
SWSS IVL establishes who a party is and signs what they approve. It holds no balance and moves nothing, so no single component can both know who you are and move what you hold.
cost More systems, more integration surface, and no shortcut when the two must agree
Stay Inside The Regulated Path
A Money Services Business registration, with payment products built against its compliance programme rather than around it.
cost Identification, record keeping, reporting and monitoring duties on every launch they touch
Six Functions, One Accountable Group
SWSS publishes functions and the accountabilities behind them rather than personal profiles. What a counterparty needs is to know who answers for what, and that does not change when a person does. Between them these six carry 123 years of operating experience in the domains this network settles.
Group Direction
Real Estate & Hospitality
Sets group strategy and carries the operating experience the settlement problem came from. Decades of property development and hospitality, where reconciliation between parties is a daily cost rather than a theory.
What the group chooses to be, and what it refuses to become
Protocol & Engineering
Software, AI & Cloud Architecture
Owns the protocol and the engineering agenda across the chain, the identity layer and every product built on them, from consensus design through to the SDKs developers actually hold.
Whether the network does what this site says it does
Finance & Treasury
Corporate Finance · Chartered Accountant
Financial planning, treasury policy and corporate reporting across four registered jurisdictions, including the reporting discipline a regulated counterparty expects before it contracts.
That the group's numbers are the same in every room
Operations & Delivery
Global Operations
Runs delivery across the engineering organisation and the operational framework behind the four jurisdictions, so that scale is a process question rather than a headcount one.
That what was committed is what ships, on the date it was promised
Security & Custody
Cybersecurity & Enterprise Security Architecture
Security strategy for custody, key handling and the identity layer. It is the part of a settlement chain where a mistake is not recoverable, and it is held apart from the teams whose work it reviews.
The one failure class the group cannot undo
Partnerships & Markets
Strategic Partnerships
Builds the counterparty, institutional and technology relationships that turn a settlement layer into a network with something to settle, and carries the obligations those relationships create.
That the network has real counterparties, not announcements
Four Horizons, And How Anyone Would Know
Ambition is easy to write and hard to check, so each horizon below comes with the signal that would tell an outsider it had happened. These are objectives rather than commitments, and they carry no dates, because SWSS does not publish schedules it has not already met.
Settlement At Institutional Scale
The network exists to settle real world value, and the measure of that is not transaction counts but what kind of asset a serious institution is willing to put on it. The work ahead is widening the asset classes the DEED-1 standard covers and hardening the operational guarantees around them.
More asset classes settled, and institutions operating on the network in their own name
Regulated Reach
An office is not a licence. The group already holds a payments registration in Canada, and the direction is to hold permissions, not merely presence, in the jurisdictions where counterparties need a regulated party on the other side of the agreement.
Jurisdictions where the group holds a licence rather than only an entity
A Platform Others Build On
A settlement layer used only by its own author is a product, not infrastructure. The developer platform, the SDKs and the documentation exist so that work which has nothing to do with SWSS can still settle on it.
Independent builders shipping against the SDKs without needing us in the room
Progressive Decentralisation
The validator set and the governance process are deliberately on a path away from the company that started them. Control that cannot be handed over is a dependency, and a settlement layer that depends on one company is only as durable as that company.
Validator independence and governance participation that does not run through us
How We Behave While Getting There
The four habits that decide whether any of the above happens, each of them visible in how the group already works rather than aspirational.
Build The Missing Layer
When the thing we need does not exist, we build it rather than work around its absence. That is why there is a chain here at all.
Structure Over Procedure
A protection that holds because of how a system is arranged survives a bad day. One that depends on everybody remembering does not.
Publish What Can Be Checked
A figure that cannot be traced to a running system or a filed document does not go on a page where somebody makes a decision.
One Organisation, Four Registrations
The offices are jurisdictions, not silos. The same standards and the same review apply in all of them.
SWSS Chain has operated since 2019 as a company and carries 17 products across its ecosystem today. Nothing on this page is a forecast of financial performance, and nothing here promises a return of any kind.
Who Decides What
A title tells you where somebody sits. A decision right tells you what that seat can actually do. Four classes of decision run this company, and they are deliberately not all made in the same place.
Decided At Parent Level
Strategy, capital allocation, the jurisdictional structure itself, and any move into a regulated activity. These are decisions that change what the company is, so they are taken once, at the top, and recorded.
Decided By The Practice
Architecture within a practice, delivery commitments, tooling and hiring. The people accountable for a system choose how it is built, because a decision made away from the work is a decision made without the facts.
Decided By The Check, Not A Person
Whether a change ships is answered by automated verification. A failing gate blocks the release, and seniority does not open it. This is deliberately the one decision in the company that nobody is allowed to make by hand.
Decided On Chain
Protocol parameters, allocation changes and the rules governing the validator set go through governance on the record. An operator acting alone cannot change them, which is the point of putting them there.
Engineering & Development
A distributed engineering organisation working across time zones, structured around the path a transaction takes rather than around products.
Protocol & Full-Stack
Consensus, node software, RPC surfaces and the applications on top, one team across the whole path a transaction takes.
AI & Machine Learning
The OwlX runtime and the agent surfaces built on it, including the tool and connector layer that lets an agent act against chain data.
Cloud Architecture
Scalable, resilient infrastructure across regions, so validator and indexing capacity is an operational decision rather than a rebuild.
Security Engineering
Audit readiness, key management and the review discipline applied before anything reaches a network carrying real value.
Quality & Release
Automated verification gates every release; published facts are measured from the running networks rather than transcribed by hand.
Product Engineering
Seventeen products across identity, payments, deeds, validators and developer tooling, each shipped against the same settlement core.
Distributed By DesignPowering Innovation Worldwide
Over 100 developers work remotely across multiple time zones and four registered jurisdictions, which keeps review and release moving around the clock and widens the pool the organisation hires from. The same discipline applies everywhere: what the site publishes is measured from the running networks, and a release is gated on that check rather than on someone remembering to look.
The Engineering Organisation, In Figures
Four of these are read from the running networks every hour. None of them is typed into this page, which is the only reason they can be trusted to still be right.
What Happens On A Bad Day
Leadership is easy to describe when everything works. These are the parts that matter when it does not: who reviews, who owns a live problem, and what can stop a release no matter who is asking for it.
Review Before Build, Not After
Architecture and security review happen against a written specification before the work starts, by people who are not writing it. A review that arrives after the code is an opinion; a review that arrives before it is a decision.
One Owner Per Incident
An incident gets a single named owner by role for its whole life, including the write up. Shared ownership of a live problem means nobody owns it, and the handover is where the detail gets lost.
Anyone Can Stop A Release
A failing check blocks a release regardless of who is waiting for it, and an engineer who believes something is unsafe can hold it without needing permission from a title. The cost of a delayed release is known; the cost of a bad one is not.
Findings Carry Forward
Every finding is recorded with what it means for the next environment, so a problem solved on testnet does not have to be rediscovered on mainnet. The record outlives the people who wrote it.
When Something Breaks
Detected
By a gate, a monitor or a person. All three count equally.
Owned
A single role takes the incident, and says so in writing.
Contained
Stop the harm before explaining it. Explanation can wait.
Recorded
Written up with the carry forward for the next environment.
A Settlement First Developer Platform
SWSS DevHub is not a generic blockchain SDK. Every primitive, from RPC to deed templates, assumes that each transaction will issue a Finality Certificate under the Deed Transaction Standard, so builders ship apps with regulator grade settlement out of the box.
Expert Legal Counsel
Counsel retained across four jurisdictions, so counterparties in each region deal with a locally advised entity. Counsel coverage and the registration list are not the same four: the group is registered in the British Virgin Islands, Canada, the United Kingdom and Malaysia, and retains counsel where its counterparties are.
Canada
Toronto
Supports the licensed payments entity, including the obligations that come with the Money Services Business registration.
United Kingdom
London
Covers European commercial agreements, intellectual property and the regulatory questions institutional counterparties raise first.
Malaysia
Kuala Lumpur
Serves the engineering centre and the banking and real estate work that the asset side of the ecosystem depends on.
Singapore
Singapore
Retained for Asia Pacific fintech regulation and cross border matters. Counsel coverage, not a registered office.
Build the Future With Us
Join a distributed engineering organisation building settlement infrastructure for real world assets: protocol, identity, payments and the tooling developers build on.
Remote First
Four jurisdictions, multiple time zones
Real Systems
Production networks carrying real value
Shipping Weekly
Guarded releases, measured claims
Speak To Counsel
Regulatory, corporate and commercial questions about operating with SWSS, routed to counsel in the relevant jurisdiction.
Request Legal Opinion
Counsel qualified across our registered jurisdictions, ready to assist with regulatory, corporate and commercial questions about operating with SWSS.
Comprehensive Analysis
Detailed legal opinions
Multi-Jurisdiction
4 countries covered
Confidential
Privileged communication
Direct Contact
[email protected]