Reporting Issues and Bugs
The SwssChain testnet period is a structured programme designed to surface and resolve issues before mainnet. Developer and validator reports of unexpected behaviour are a critical input to the SwssChain engineering process. All reported issues are reviewed by the core development team.
What to Report
Report any of the following when encountered on the SwssChain testnet:
- Consensus Anomalies: Blocks that appear to be accepted by the network but violate expected SCP rules; forks that are not resolved within the expected time; Finality Certificates signed by fewer validators than the required threshold.
- RPC Inconsistencies: JSON-RPC methods returning results that differ from the specified behaviour; responses that vary between RPC node instances for the same query at the same block height.
- Deed Settlement Failures: Valid Deed settlement transactions that are rejected, produce incorrect Finality Certificate content, or fail to emit expected events.
- Settlement Combustion Model Discrepancies: TSL amounts deducted that differ from the published formula; ERRP distributions that do not match the declared distribution ratios.
- EVM Incompatibilities: Solidity or Yul constructs that behave differently on SwssChain compared to the reference EVM implementation at the same EVM version (Cancun).
- SDK Bugs: SDK methods that return incorrect results, fail silently, or behave inconsistently with the documented specification.
- Explorer Errors: Data displayed on the testnet explorer that does not match the underlying on-chain data.
How to Submit a Report
All testnet issues are submitted through the issue tracker in the SWSS DevHub dashboard. An approved developer account is required: see Developer and Validator Access. Include the following information in every report:
- Issue Category: Select from the predefined categories (Consensus, RPC, Deed Settlement, SCM, EVM, SDK, Explorer).
- Severity: Critical (network halted or funds at risk), High (significant unexpected behaviour), Medium (unexpected behaviour with workaround), Low (cosmetic or minor inconsistency).
- Description: A clear statement of expected behaviour and the actual observed behaviour.
- Reproduction Steps: The minimum steps required to reproduce the issue. Include transaction hashes, block numbers, contract addresses, and code snippets where relevant.
- Environment: Testnet reset number (visible in the explorer footer), SDK version, network client version if applicable.
- Logs: Attach relevant node logs, RPC response bodies, or explorer screenshots.
Security Vulnerabilities
If the issue represents a potential security vulnerability (one that could be exploited to steal funds, compromise validator keys, or disrupt consensus) do not submit it publicly via the issue tracker. Follow the responsible disclosure process described in the Security section of this documentation. Security vulnerability reporters who follow the responsible disclosure process are eligible for recognition in the SwssChain security acknowledgements.
Response Times
| Severity |
Initial Response |
Resolution Target |
| Critical | 4 hours | 24 hours |
| High | 24 hours | 7 days |
| Medium | 72 hours | 30 days |
| Low | 1 week | Next release cycle |
Issue Lifecycle
Submitted issues move through the following states: Submitted → Triaged → Confirmed → In Progress → Resolved → Closed. Issue reporters receive email notifications at each state transition. Confirmed issues are published in the public issue tracker with a sanitised description that does not include exploitable details for security-sensitive reports.
Recognition
Developers who report confirmed High or Critical issues during the testnet period will be recognised in the SwssChain Testnet Contributor Registry, published on SWSS DevHub and referenced in the SwssChain mainnet launch documentation.