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.
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.
Custom swss_* RPC Methods
SwssChain extends the standard Ethereum JSON-RPC specification with a set of proprietary swss_* methods that expose settlement-specific protocol data unavailable through any standard Ethereum endpoint. These methods are native to SwssChain: they do not exist on any other EVM-compatible network.
Mainnet RPC: $SWSSCHAIN_RPC_URL: issued by SWSS DevHub
Testnet RPC: Testnet access requires registration at SWSS DevHub: see below.
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.
Method Reference
| Method | Category | Description | Status |
|---|---|---|---|
swss_getFinalityCert | Settlement | Retrieve a Finality Certificate by transaction hash | Live |
swss_getValidatorSet | Consensus | Return current active validator set with epoch and rotation history | Live |
swss_getGovernanceState | Governance | Return current on-chain governance state | Live |
swss_getGovernanceParams | Governance | Return protocol governance parameters | Live |
swss_getActiveProposals | Governance | Return all active on-chain governance proposals | Live |
swss_credentialValid | Identity | Instant boolean check: is a wallet address KYC credentialed? | Live |
swss_getCredential | Identity | Return full IVL credential details for a wallet address | Live |
swss_getCredentialByDeedId | Identity | Look up IVL credential by deed ID: supports audit and regulatory queries | Live |
swss_getDeedDetails | Deed Access | Return deed detail fields with ECDSA-signed auth: owner privacy enforced | Live |
swss_checkDeedAccess | Deed Access | Check a wallet's access rights to a specific deed | Live |
swss_getDeedGrants | Deed Access | Enumerate all active standing access grants for a deed | Live |
swss_getAgent | AI Agent | Return AI Agent Deed registration data by agent ID | Live |
swss_getAgentInvocations | AI Agent | Return invocation history for a registered AI agent | Live |
swss_getFinalityCert
Retrieves the Finality Certificate for a deed transaction by its on-chain transaction hash. Returns the full multi-validator signed certificate directly from the consensus layer: no intermediary.
{
"jsonrpc": "2.0",
"method": "swss_getFinalityCert",
"params": ["0x1deed7a3f..."],
"id": 1
}
Response:
{
"result": {
"version": 1,
"txHash": "0x1deed7a3f...",
"blockNumber": 154837,
"blockHash": "0xblockhash...",
"deedId": "SWSS-ESTATE-00001",
"assetRef": "LR-EW-4821953",
"chainId": 122605,
"timestamp": 1749254400,
"signatures": [
{ "validator": "0x36841E62...", "signature": "0xsig1..." },
{ "validator": "0x9b8d2290...", "signature": "0xsig2..." },
{ "validator": "0x2033FcD2...", "signature": "0xsig3..." }
]
}
}
swss_getValidatorSet
Returns the current active validator set including epoch number, current block, and rotation history for any validator that has performed an on-chain credential rotation.
{
"jsonrpc": "2.0",
"method": "swss_getValidatorSet",
"params": [],
"id": 1
}
Response:
{
"result": {
"epoch": 77,
"blockNumber": 155925,
"validators": [
{ "address": "0x36841E62...", "addedAtBlock": 0 },
{ "address": "0x9b8d2290...", "addedAtBlock": 0 },
{ "address": "0x2033FcD2...", "addedAtBlock": 0 },
{ "address": "0x5eD15343...", "addedAtBlock": 74000, "rotatedFrom": "0x06c40a72..." }
]
}
}
swss_credentialValid
Instant boolean check: returns whether a wallet address holds a valid SWSS IVL credential. Used by all SWSS products internally to gate access to DEED-1 settlement operations. Response is immediate: single round-trip to the consensus node.
{
"jsonrpc": "2.0",
"method": "swss_credentialValid",
"params": ["0xwalletaddress...", "KYC"],
"id": 1
}
Valid scope values: KYC, KYB, AML, FULL
{
"result": {
"valid": true,
"scope": "KYC",
"expiresAt": 1780790400,
"jurisdiction": "GB"
}
}
swss_getGovernanceState
{
"jsonrpc": "2.0",
"method": "swss_getGovernanceState",
"params": [],
"id": 1
}
Returns current governance phase, active proposal count, quorum threshold, and veto window parameters. Use alongside swss_getGovernanceParams and swss_getActiveProposals for full governance state.
swss_checkDeedAccess
Checks whether a specific wallet address has access to a deed record and returns the access tier. Access tiers map to the SWSS IVL three-tier architecture: PUBLIC (hash and timestamp only), VERIFIED (full metadata, requires IVL KYC credential), INSTITUTIONAL (complete record including private annotations, requires IVL KYB credential).
{
"jsonrpc": "2.0",
"method": "swss_checkDeedAccess",
"params": ["0xwalletaddress...", "SWSS-ESTATE-00001"],
"id": 1
}
{
"result": {
"deedId": "SWSS-ESTATE-00001",
"wallet": "0xwalletaddress...",
"tier": "VERIFIED",
"grantedAt": 1749254400
}
}
Calling swss_* Methods in JavaScript
async function callSwssRpc(method, params = []) {
const res = await fetch(process.env.SWSSCHAIN_RPC_URL, {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ jsonrpc: '2.0', method, params, id: 1 }),
});
const json = await res.json();
if (json.error) throw new Error(json.error.message);
return json.result;
}
// Examples
const cert = await callSwssRpc('swss_getFinalityCert', ['0xtxhash...']);
const validators = await callSwssRpc('swss_getValidatorSet');
const isValid = await callSwssRpc('swss_credentialValid', ['0xwallet...', 'KYC']);
All
swss_*methods are available on the mainnet endpoint issued with your SWSS DevHub credentials. Access to either network requires an approved developer account. How developer access is granted →
