TrusTrove is currently in active development and deployed on Stellar testnet only. No mainnet deployment exists. Smart contracts have not undergone a formal audit.
| Version | Supported |
|---|---|
| 0.1.x (testnet) | ✅ |
| mainnet | ❌ Not deployed |
The following are in scope for security reports:
- Smart contract logic errors in
contracts/(registry, invoice, escrow, pool) - Authentication bypass or unauthorized fund access in Soroban contracts
- Integer overflow or underflow in amount calculations
- Incorrect state transitions in the invoice lifecycle
- USDC drainage vulnerabilities in the pool or escrow contracts
- Frontend issues that could cause users to sign unintended transactions
The following are out of scope:
- Stellar protocol-level issues (report to SDF directly)
- Freighter wallet vulnerabilities (report to Freighter team)
- Testnet-only issues with no mainnet impact path
- UI cosmetic bugs
Do not open a public GitHub issue for security vulnerabilities.
Report vulnerabilities by emailing: security@trusttrove.xyz (If this address is not yet active, open a private GitHub Security Advisory via the Security tab on this repository.)
Include in your report:
- Description of the vulnerability
- Steps to reproduce
- Affected contract or component
- Potential impact
- Suggested fix if you have one
| Action | Target Time |
|---|---|
| Acknowledgement | 48 hours |
| Initial assessment | 5 business days |
| Fix or mitigation | 14 business days |
TrusTrove follows coordinated disclosure. We ask that you give us reasonable time to assess and address a vulnerability before public disclosure.
We will credit researchers who report valid vulnerabilities in our changelog unless they prefer to remain anonymous.
TrusTrove smart contracts have not been formally audited. Users interact with testnet contracts at their own risk. A security audit is planned prior to any mainnet deployment.
TrusTrove is experimental software. Do not deposit real funds. All contracts operate on Stellar testnet with test USDC only.