Hosted by SQRL
SQRL cloud
- The node
- Run by SQRL in the SQRL cloud
- Your team
- Sets rates and approves payments
SQRL DeveloperEarly accessDeveloper access
for banks.
The settlement layer for tokenised money. Deploy contracts, issue tokenised deposits and connect your subnet. Access is curated and starts in the sandbox.
Banks
Issue tokenised deposits, set who may hold them, and pay other banks from your own subnet.
Corridor partners
Fund the corridors you run, set the rate on each payment, and settle through the hub.
Regulated institutions
Deploy SQRL contracts, issue tokenised deposits and connect your systems to the network.
From access to first payment. Six steps from a request to a settled test payment in the sandbox.
1
Request access
Tell us about your institution and what you plan to build. Qualified teams get a sandbox with funded test balances.
2
Set up your subnet
Run it in your data centre or let SQRL host it. Add your team, signers and a first vault.
3
Deploy your first contract
Set the token parameters and send the deployment to your vault's signers. The contract is live once it confirms.
4
Mint and whitelist
Add the addresses that may hold the token, then mint into a vault. The vault that owns the contract signs each change.
5
Connect your systems
Connect your backend to the subnet through the API. The reference ships with access.
6
Settle a test payment
Lock a quote, send through the hub and follow it to settlement. No customer money moves.
token.scl
contract Token { @writeable_by(init, transfer_ownership) owner: Str; @writeable_by(init, mint, burn) total_supply: Int; @writeable_by(init) max_supply: Int; fn mint(to: Str, amount: Int) { let sender = SENDER_ADDRESS(); if (owner != sender) { return 0; } let temp = total_supply + amount; if (temp > max_supply) { return 0; } // shortened }}Deploy a contract. Start from the token template, or write your own contract in SQRL.
The token template
Enter name, ticker, decimals, initial supply and maximum supply. SQRL compiles the contract; your team does not have to write SQRL.
Your own SQRL
A contract holds constants, fields with explicit write permissions, events and functions. The compiler produces bytecode, an ABI and metadata.
Anchored for settlement
A hash of the compiled contract is committed on the settlement layer. Once that confirms, the transaction id is the contract's id.
Bounded on purpose
Every execution is bounded, and clocks, randomness and outside data are excluded, so every node reaches the same result.
Control the tokens you issue. The vault that deploys a token owns it. Its signers approve each change on-chain.
Mint
Send new tokens to a vault you choose. The maximum supply is fixed at deployment, and the contract refuses anything past it.
Burn
Retire tokens when a holder redeems. The vault has to own the contract and hold the balance.
Whitelist
Restrict a token to the addresses on its whitelist. Approval is per token, so one token's list says nothing about another's.
Pause
The owner can pause a contract, which stops transfers until the owner unpauses it.
Connect to the hub. One connection from your subnet reaches every other subnet. A payment moves in four steps.
01
Lock a quote
Ask for a rate on a corridor. The quote can lock one payment while it holds.
02
Pay the hub
Your payment reaches the hub and waits there. Tokens travel inside the payment, so routing hops need no knowledge of the asset.
03
The hub pays the receiver
The receiver is paid first, in their own currency when the corridor converts in flight.
04
The payment settles
Only then does the hub collect from you. If the payout fails, your payment is never collected.
Fund your corridors. Balances sit in channels under your own keys. SQRL does not take custody.
Channels
Each channel opens with a settlement transaction. Closing one returns its balance to your wallet.
Runway
See how long a balance lasts at the current pace of payouts, so you can add to it before it runs out.
Corridors
Set the rate, a cap per payment and a cap per day on each direction. Pause or halt one at any time.
Approved moves
Every move of funds needs a quorum of approvers other than the requester. It stays within per-asset limits and goes to whitelisted addresses only.
Choose where your subnet runs. SQRL hosts it, or your team runs it in your own data centre. The controls are the same.
Hosted in your data centre
Your data centre
- The node
- Run by your team, on your servers
- Your team
- Funds corridors, sets rates and spreads
What your bank sets up. These are the controls your risk team will review before a pilot.
Workspaces
Each workspace is set to one network, so sandbox work stays apart from production.
Roles
Give each person a role. A role in one workspace grants nothing in another, and no global administrator can see everything.
Signing keys
Signers use a hardware wallet or a software profile in their own browser. SQRL holds public keys only and cannot recover a lost key.
Vaults
A vault is an M-of-N multisig on Bitcoin, for example two of three. Nothing broadcasts until the threshold is met.
Spending limits
Limits apply per role and per vault on weekly or monthly cycles. A vault with no policy refuses by default.
Audit trail
Sign-ins, signatures and broadcasts go into an append-only log. Your auditors can export it as CSV.
Questions from engineers. What your team will ask first.
Access is curated. Tell us about your institution and what you plan to build, and the team reviews the request. Qualified institutions get a sandbox environment with funded test balances.
No. Developer access runs in the public sandbox, with no customer money moving and no financial service provided.
Through a JSON API covering signing keys, vaults, transaction proposals, tokens and contracts, whitelists, spending limits and audit logs. The reference comes with access. For corridor pricing and FX quotes from your own systems, talk to our engineers.
Not to issue a token. SQRL compiles your parameters into the contract. You write SQRL when you need a contract of your own, and the language is documented publicly.
With your signers. SQRL holds public keys only. Signing happens on your own device or wallet, and SQRL cannot recover a lost key.
Your funds do not depend on it. You can close a channel without the hub, and the balance returns to your wallet after a timelock.
Financial services on the SQRL Network are FSCA-authorised, Category I and II, crypto assets included. FSP 54623. SQRL builds the technology. Your compliance team confirms what your own licence covers.
Explore the other products. They all run on the same settlement network, under the keys and policies you set.
Request developer access.
Tell us what you plan to build. The team reviews each request.
