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.
EVM Compatibility: Cancun
SwssChain is fully EVM-compatible at the Cancun hardfork level, supporting EIP-4844 (Proto-Danksharding) and EIP-1153 (Transient Storage). Any Solidity contract that runs on Ethereum mainnet will run on SwssChain without modification. All standard Ethereum developer tooling: Hardhat, Foundry, Remix, ethers.js, viem, wagmi: operates on SwssChain without additional configuration beyond the network parameters. SwssChain's EVM Cancun compatibility means every Ethereum developer can build on the world's first RWA settlement blockchain without learning a new toolchain.
What Cancun Compatibility Provides
EIP-4844: Proto-Danksharding: Blob transactions are supported on SwssChain. The blob fee market operates identically to Ethereum Cancun, providing the same reduced data availability costs for applications that use blob data. Layer 2 projects and data-intensive applications targeting SwssChain can leverage blob transactions from launch.
EIP-1153: Transient Storage: The TSTORE and TLOAD opcodes are available, enabling cheaper temporary storage within a transaction's execution context. This is particularly relevant for reentrancy lock patterns, a common requirement in DeFi contracts, and for flash loan implementations that need temporary state without incurring permanent storage costs.
Supported Solidity Versions and Opcodes
All Solidity versions compatible with the Cancun EVM are supported. The recommended minimum version is 0.8.20. Full opcode support includes PUSH0 (EIP-3855) and MCOPY (EIP-5656), both of which are available and functioning identically to their Ethereum Cancun implementations.
What Works Unchanged on SwssChain
| Tool / Feature | Status on SwssChain |
|---|---|
| Solidity smart contracts | Fully compatible: no changes required |
| Hardhat | Full support: add network config only |
| Foundry | Full support: add rpc_endpoint only |
| Remix IDE | Full support: connect via injected provider |
| OpenZeppelin Contracts | Full support: all versions, no changes needed |
| ethers.js | Full support: use JsonRpcProvider with SwssChain RPC |
| web3.js | Full support: standard connection |
| viem | Full support: define custom chain |
| wagmi | Full support: use custom chain config |
| Chainlink oracles | Compatible: check feed availability at DevHub |
| The Graph indexing | Compatible: deploy custom subgraph |
| IPFS integration | Compatible: no chain-level changes |
What Is Different on SwssChain
Four properties distinguish SwssChain from a standard Ethereum fork:
- Chain ID: 122605 (hex:
0x1DEED) for mainnet, 122606 (hex:0x1DEEE) for testnet, all network configs must be updated accordingly - Block time: 1 second: transactions confirm significantly faster than on Ethereum (12 seconds)
- Native currency: SWSS Coin: gas fees are denominated in SWSS Coin, not ETH
- Deed transactions: A first-class transaction type unique to SwssChain, processed through the SCP priority architecture, not available on any other EVM chain
Hardhat Configuration
// hardhat.config.ts
import { HardhatUserConfig } from 'hardhat/config';
import '@nomicfoundation/hardhat-toolbox';
import * as dotenv from 'dotenv';
dotenv.config();
const config: HardhatUserConfig = {
solidity: '0.8.24',
networks: {
swsschain: {
url: process.env.SWSSCHAIN_RPC_URL!,
chainId: 122605,
accounts: [process.env.PRIVATE_KEY!]
},
swsschain_testnet: {
url: process.env.SWSSCHAIN_TESTNET_RPC_URL!,
chainId: 122606,
accounts: [process.env.PRIVATE_KEY!]
}
}
};
export default config;
Foundry Configuration
# foundry.toml
[profile.default]
src = "src"
out = "out"
libs = ["lib"]
[rpc_endpoints]
swsschain = "${SWSSCHAIN_RPC_URL}"
swsschain_testnet = "${SWSSCHAIN_TESTNET_RPC_URL}"
Next Steps
- See RPC Endpoint Reference for how to obtain your SwssChain RPC URL from SWSS DevHub.
- Follow Smart Contract Deployment for a complete deployment walkthrough.
- Read Solidity Tooling Compatibility for the full tooling reference including viem and wagmi configuration.
