Testnet
Connecting to Testnet
Pre-launch
Section
Testnet
Documentation category
Type
Guide
Technical reference
Summary
Step-by-step guide to connecting development tools, wallets, and SDKs to the SwssChain testnet environment.
SWSS Foundation Notice

This documentation is restricted to authorised members of the SWSS Developer Community. Access is granted exclusively through SWSS DevHub, after KYB and SWSS Foundation approval.

All SwssChain GitHub repositories are private. Significant updates are currently deploying across the full SWSS Ecosystem. SDK and API specifications are subject to change at any time in accordance with security requirements and SwssChain Foundation governance decisions.

Join SWSS DevHub →Have a question? Use the Need Help? button below.
SDK Update Notice

SWSS SDK v2.1 is deploying across the ecosystem. API signatures may change during this period. Ensure your integration uses the latest schema from SWSS DevHub.

Article Content
Testnet Access: SWSS DevHub Required

Access to SwssChain testnet 122606 is limited to developers the SWSS Foundation has approved. Credentials, endpoints and testnet allocation are issued together on approval: see how access is granted. Testnet access is not publicly open.

Connecting to Testnet

SwssChain testnet 122606 is a permissioned settlement test network. Connecting to it, for reading as well as for submitting transactions, requires developer credentials issued by SWSS DevHub once KYB is complete and the SWSS Foundation has approved the application. Endpoints, allocation and rate limits are provisioned with those credentials; they are not published here.

Network Details

Parameter Value
Network NameSwssChain Testnet
Chain ID122606
RPC URL (HTTPS)Issued by SWSS DevHub on approval
WebSocket URLIssued by SWSS DevHub on approval
Block Explorerhttps://testnet.swssscan.swss.io
Currency SymbolSWSS
Currency Decimals18

Connecting an EVM Wallet

To add the SwssChain testnet to a compatible EVM wallet manually, use the network details above. Most EVM wallets also support automatic network addition by visiting the testnet explorer and clicking "Add to Wallet".

SDK Configuration

import { SwssChain, networks } from '@swsschain/sdk';

// Use networks.testnet — all endpoints pre-configured
const client = new SwssChain({
  network: networks.testnet,
  privateKey: process.env.TESTNET_PRIVATE_KEY as `0x${string}`,
});
from swsschain import SwssChain, networks
import os

client = SwssChain(
    network=networks.testnet,
    private_key=os.environ['TESTNET_PRIVATE_KEY'],
)
client, err := swss.NewClient(&swss.Config{
    Network:    swss.Testnet,
    PrivateKey: os.Getenv("TESTNET_PRIVATE_KEY"),
})

Hardhat Configuration

// hardhat.config.ts
import { HardhatUserConfig } from 'hardhat/config';

const config: HardhatUserConfig = {
  solidity: {
    version: '0.8.24',
    settings: { evmVersion: 'cancun' },
  },
  networks: {
    swssTestnet: {
      url: process.env.SWSSCHAIN_TESTNET_RPC_URL,   // issued by SWSS DevHub
      chainId: 122606,
      accounts: [process.env.TESTNET_PRIVATE_KEY!],
      gasPrice: 'auto',
    },
  },
};

export default config;

Foundry Configuration

# foundry.toml
[profile.default]
src = "src"
out = "out"
libs = ["lib"]
evm_version = "cancun"

[rpc_endpoints]
swss_testnet = "${SWSSCHAIN_TESTNET_RPC_URL}"   # issued by SWSS DevHub
# Deploy to testnet with Foundry
forge create --rpc-url swss_testnet   --private-key $TESTNET_PRIVATE_KEY   src/MyContract.sol:MyContract

# Run scripts against testnet
forge script script/Deploy.s.sol   --rpc-url swss_testnet   --private-key $TESTNET_PRIVATE_KEY   --broadcast

JSON-RPC Direct Connection

# Verify testnet connection
curl -X POST "$SWSSCHAIN_TESTNET_RPC_URL"   -H "Content-Type: application/json"   -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

# Expected response
# {"jsonrpc":"2.0","id":1,"result":"0x1deee"}

Environment Variable Best Practices

Store all testnet credentials in environment variables, never in committed code files. Use a .env file during development and ensure it is listed in .gitignore. Do not reuse testnet private keys for mainnet: generate separate key pairs for each environment.

# .env.testnet (never commit this file)
TESTNET_PRIVATE_KEY=0x...
SWSSCHAIN_TESTNET_RPC_URL=   # issued by SWSS DevHub
TESTNET_CHAIN_ID=122606
Frequently Asked Questions
6 questions
Can I add SwssChain testnet to my wallet manually?

Yes, using the network details on this page and the RPC URL issued with your credentials. The chain id is 122606 and the currency symbol is SWSS with 18 decimals.

Is the testnet reset, and do I lose my contracts?

It is reset periodically. Balances, deployments, deed records and transaction history are all cleared. Keep contract addresses in version-controlled configuration and script your deployment and test data setup so a reset costs you a command rather than a day.

How much notice is given before a reset?

A minimum of seven days, announced through the SWSS DevHub change log and the developer mailing list.

Does testnet run the same protocol version as mainnet?

Both networks report the same client version. Testnet may carry pre-release protocol flags ahead of mainnet; where it does, that is stated with the flag rather than implied by a version number.

Can I reuse a mainnet private key on testnet?

No. Generate a separate key pair for each environment, and keep testnet keys in a .env file that is listed in .gitignore.

Why does my transaction fail with a chain id mismatch?

EIP-155 replay protection incorporates the chain id into the signing hash. A transaction signed for 122605 cannot be submitted to 122606 and the reverse is also true: check the chain id your signer is configured with, not just the endpoint.