Build with SwissDLT

Quickstart

Add the network to an EVM wallet, get native BCTS for gas, and read the chain.

Add SwissDLT to my wallet

First read

curl https://rpc.swissdlt.ch \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
# {"jsonrpc":"2.0","id":1,"result":"0x5e"}

viem

import { createPublicClient, http, defineChain } from 'viem'

export const swissdlt = defineChain({
  id: 94, name: 'SwissDLT',
  nativeCurrency: { name: 'BCTS', symbol: 'BCTS', decimals: 18 },
  rpcUrls: { default: { http: ['https://rpc.swissdlt.ch', 'https://rpc2.swissdlt.ch'],
                        webSocket: ['wss://rpc.swissdlt.ch/ws'] } },
  blockExplorers: { default: { name: 'SwissDLT Explorer', url: 'https://explorer.swissdlt.tech' } },
})

const client = createPublicClient({ chain: swissdlt, transport: http() })
console.log(await client.getBlockNumber())

RPC and WebSocket

Follow new blocks

const ws = new WebSocket('wss://rpc.swissdlt.ch/ws')
ws.onopen = () => ws.send(JSON.stringify({ jsonrpc: '2.0', id: 1, method: 'eth_subscribe', params: ['newHeads'] }))
ws.onmessage = (e) => { const m = JSON.parse(e.data); if (m.params) console.log(parseInt(m.params.result.number, 16)) }

Who sealed a block?

In Clique the miner field carries signer votes, not the producer. Recover the sealer from the last 65 bytes of extraData: hash the RLP-encoded header with those bytes removed and recover the signing address. This site does exactly that in your browser; see assets/js/site.js.

Gas and EVM

• EVM level Berlin. Compile with evmVersion: "berlin"; Shanghai's PUSH0 and later opcodes will fail.
• Send legacy (type 0) transactions. There is no EIP-1559 base fee, although some chain registries say otherwise.
• Gas price 1 gwei is the observed norm. Blocks every 4 seconds.
• No safe or finalized block tags. Wait for confirmations and follow the association's checkpoint policy for high-value flows.

Foundry

# foundry.toml
[profile.default]
evm_version = "berlin"
solc = "0.8.24"

forge create src/MyToken.sol:MyToken --rpc-url https://rpc.swissdlt.ch \
  --legacy --gas-price 1gwei --private-key $KEY

Hardhat

networks: {
  swissdlt: { url: 'https://rpc.swissdlt.ch', chainId: 94, gasPrice: 1_000_000_000 }
},
solidity: { version: '0.8.24', settings: { evmVersion: 'berlin', optimizer: { enabled: true, runs: 200 } } }

Contracts

Canonical addresses as observed on 7 November 2026. A signed, versioned registry from the association will replace this table.

SwissDLT, chain 94

Governance on Polygon

Assets

On SwissDLT

• BCTS is the native gas asset: 72'000'003 allocated at genesis, most of it in six treasury accounts; there is no block reward.
• Wrapped BCTS exists in two backed deployments (see Contracts). Wrap and unwrap 1:1 against native BCTS.
• Bridged from Polygon through the legacy bridge: WPOL 4'562.862, DAI 72.213, ZCHF 1.1 (observed supplies, matching the Polygon lockbox).

BCTS on other chains

These are issued directly by Blockchain Trust Solutions AG or bridged via Axelar. They are not minted by a SwissDLT bridge and cannot pay gas on chain 94.

Displayed pool reserves on other chains are not liquidity or a market price. We do not publish token prices.

Bridges

Legacy Polygon bridge (ChainBridge)

A lock-and-mint bridge between Polygon and SwissDLT with a relayer threshold of one. Last observed deposits in September 2023. Relayer identity, liveness and recovery process are not published, so we recommend against new deposits until the association either operates it properly or decommissions it.

DogeOS MVP

Test bridge to DogeOS Chikyū, not configured. See Build, bridge.

Planned: Hyperlane corridor

Native BCTS collateral on SwissDLT backing a synthetic ERC-20 on Base, verified by a 3-of-5 validator set of independent operators with rate limits, timelocked administration and daily supply reconciliation. Planning estimate for the first corridor: 12 to 22 person-weeks plus an external review.

Data and APIs

MCP endpoints for AI agents are listed under Build, AI agents.

For AI agents and Thirdfy

Each service keeps its own Thirdfy package. The packages are prepared for submission: nothing has been submitted, no listing is claimed, and Thirdfy wallet execution on chain 94 is not established. Three files on this site tie the services together.

Checked 12:02 UTC, 8 November 2026. "Not published yet" means the file did not answer at that check; the submission index records each check.

Run a node

Signers are admitted by the association and voted in through Clique. Archive and RPC nodes can be run by members to serve applications.

• Client: go-ethereum. Public RPCs run 1.11 and 1.12; 1.13 is the newest release that can still seal Clique blocks, and 1.14 and later cannot. Upgrades are coordinated across all signers.
• Genesis: use the current chain-94 genesis from the SwissDLT node setup repository. Older guides for chain 999 or 99 are for retired networks.
• Signers: never expose RPC or an unlocked account on a signer; keep static peers to at least three other nodes; back up keystores offline.
• Operations: a watchdog that restarts a stuck client, automatic recovery for hung machines, daily disk snapshots, and alerts for halted blocks, fewer than five active signers, unhealthy nodes and full disks.

Governance

The network is governed by the Verein Nodebetreiber der SwissDLT. Its on-chain record is a DAO on Polygon, created on 3 June 2023, with 13 member addresses, 30 proposals and 109 votes between June 2023 and July 2024. Quorum is 54% and the voting period one week.

What is still missing, and planned: published statutes and board, an operator map linking each signer key to a named organisation, a current meeting cadence, and resolution of the remaining full-permission administrative key on the DAO. See About, governance.

Security and incidents

• Report vulnerabilities to [security@swissdlt.ch]. Please do not test on mainnet with value.
• A status line is published within one hour of a confirmed incident, and a post-mortem with owner and corrective actions within 14 days.
• None of the new apps has completed an independent security audit yet. Use small amounts.

FAQ

Is SwissDLT a public blockchain?

Anyone can read it and send transactions; only admitted signers seal blocks. It is a permissioned consortium chain.

Where do I get BCTS?

Native BCTS on chain 94 comes from existing holders; there is no faucet or exchange listing. We do not publish a price.

Is there an SDK?

No dedicated SDK is needed. viem, ethers, Foundry and Hardhat work with the settings above.

Is data stored in Switzerland?

Chain data is replicated on every node. Three signer nodes run in Zurich; the full hosting map will be part of the operator map.