Developer Reference
RPC Endpoint Reference
Pre-launch
Section
Developer Reference
Documentation category
Type
Guide
Technical reference
Summary
SwssChain RPC endpoint types, supported JSON-RPC methods including SwssChain-specific calls, ethers.js connection examples, and DevHub rate limits.
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.

RPC Endpoint Reference

SwssChain RPC endpoints are available to registered developers via SWSS DevHub. Registration provides access to personal endpoint credentials for both mainnet and testnet, with rate limits and endpoint types matched to your development tier. All standard Ethereum JSON-RPC methods are supported, plus three SwssChain-specific methods for accessing deed and Finality Certificate data.

Endpoint Types Available

Endpoint TypeUse CaseNotes
HTTP RPCStandard JSON-RPC calls: contract reads, transaction submission, block queriesFor most application use cases
WebSocket RPCReal-time event subscriptions: new blocks, log events, pending transactionsRequired for eth_subscribe
Archive NodeHistorical state queries at any past block numberRequired for analytics and indexing
Testnet HTTPDevelopment and integration testingFree to all registered DevHub accounts
Testnet WebSocketTestnet event subscriptionsFree to all registered DevHub accounts

Supported JSON-RPC Methods

All standard Ethereum JSON-RPC methods are supported, including:

  • eth_blockNumber, eth_getBlockByNumber, eth_getBlockByHash
  • eth_getTransactionByHash, eth_getTransactionReceipt
  • eth_call, eth_estimateGas, eth_sendRawTransaction
  • eth_getLogs, eth_getBalance, eth_getCode
  • eth_subscribe: WebSocket only (blocks, logs, pending transactions)

SwssChain-specific methods:

  • swss_getDeedTransaction: retrieve full deed transaction details by hash
  • swss_getFinalityCertificate: retrieve a Finality Certificate by transaction hash
  • swss_getChainStatus: live chain health, active validator count, and current block metrics

Connecting with ethers.js

import { ethers } from 'ethers';

// HTTP provider for standard calls
const provider = new ethers.JsonRpcProvider(
  process.env.SWSSCHAIN_RPC_URL
);

const network = await provider.getNetwork();
console.log(network.chainId); // 122605n

WebSocket Subscriptions

import { ethers } from 'ethers';

const wsProvider = new ethers.WebSocketProvider(
  process.env.SWSSCHAIN_WS_URL
);

// Subscribe to new blocks
wsProvider.on('block', (blockNumber) => {
  console.log('New block:', blockNumber);
});

// Subscribe to contract events
const contractFilter = {
  address: '0xYourContractAddress',
  topics: [ethers.id('Transfer(address,address,uint256)')]
};

wsProvider.on(contractFilter, (log) => {
  console.log('Transfer event:', log.transactionHash);
});

SwssChain-Specific RPC Call

// Retrieve a Finality Certificate via JSON-RPC
const certificate = await provider.send(
  'swss_getFinalityCertificate',
  ['0xYourTransactionHash']
);

console.log(certificate.deedType);       // e.g. 'Home Deed'
console.log(certificate.verified);       // true
console.log(certificate.jurisdiction);   // e.g. 'England and Wales'

Rate Limits by DevHub Tier

TierHTTP Requests/secWebSocket Connections
Standard100Up to 10 concurrent
Professional1,000Up to 50 concurrent
EnterpriseCustomCustom: contact DevHub

Next Steps

Frequently Asked Questions
6 questions
Which JSON-RPC methods are supported?

All standard Ethereum JSON-RPC methods, plus the SwssChain-specific swss_* methods for deed and Finality Certificate data. See Custom swss_* RPC Methods.

Do I need a WebSocket endpoint?

Only for eth_subscribe: new blocks, log events and pending transactions. Everything else works over HTTP.

When do I need an archive endpoint?

For historical state at a past block: analytics, indexing, and any query that reads balances or storage as of a specific height rather than latest.

Can I use a third-party RPC aggregator?

Not for settlement-critical infrastructure. Confirm the current endpoint from your issued configuration, an endpoint you did not obtain from the Foundation is an endpoint whose behaviour nobody has committed to.

What are the rate limits?

They are scoped to the tier your approval covers, and each key carries its own allocation. See Rate Limits and Throttling.

Can I share one key across development and production?

No. Use separate keys per environment so a development workload cannot exhaust the allocation your production traffic depends on, and so a compromised key can be revoked without an outage.