0xc598275452fa319d75ee5f176fd3b8384925b425
As of 21 Nov 2026, Trustblock’s record holds 0xc598275452fa319d75ee5f176fd3b8384925b425 on BNB Chain as a contract of Stream Chain 2.0. 1 audit report on Trustblock lists this address: CertiK, 30 May 2022. 3 findings in it are recorded as open or acknowledged.
Each report’s scope as stored on Trustblock names this address on BNB Chain.
| Audit | Security firm | Date | Commit named in the report | Report |
|---|---|---|---|---|
| Stream-Coin | CertiK | Not recorded (see the report) | Open |
2 High, 1 Low. In the firm’s own words; statuses are the firm’s, from each report.
In the contract `Stream` the role `HiddenOwner` has authority over the following functions: - transferOwnership - transferHiddenOwnership Any compromise to the `HiddenOwner` account may allow the hacker to take advantage of this authority. In the contract `Stream` the role `locker` has authority over the following functions: - lock Any compromise to the `locker` account may allow the hacker to take advantage of this authority. In the contract `Stream` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority. 
The audit on Trustblock · Open the reportAll of the STRM tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute STRM tokens without obtaining the consensus of the community.
The audit on Trustblock · Open the reportThere should always be events emitted in the sensitive functions that are controlled by centralization roles.
The audit on Trustblock · Open the reportThe Stream Chain 2.0 security record · Every Stream Chain 2.0 address · This address on the explorer