SHANTI contract 0xd77f…3457 on BNB Chain

0xd77fef555f2595f60c0b2289e770781a71053457

As of 21 Nov 2026, Trustblock’s record holds 0xd77fef555f2595f60c0b2289e770781a71053457 on BNB Chain as a contract of SHANTI. 1 audit report on Trustblock lists this address: CertiK, 7 Mar 2023. 4 findings in it are recorded as open or acknowledged.

Audit reports that list this address1

Each report’s scope as stored on Trustblock names this address on BNB Chain.

AuditSecurity firmDateCommit named in the reportReport
SHANTICertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports4

1 High, 3 Low. In the firm’s own words; statuses are the firm’s, from each report.

HighInitial Token DistributionSHANTI · CertiKAcknowledged

All of the `SHANTI` tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute `SHANTI` tokens without obtaining the consensus of the community.

The audit on Trustblock · Open the report
LowChecks Effects Interaction Pattern Not UsedSHANTI · CertiKOpen

In the current implementation, the function `transferFrom()` does not follow the Checks-Effects-Interactation standard, as the transfer is completed before the allowances are checked. While this does not create any security issues in this implementation, it does not follow the standard and thus is only informational.

The audit on Trustblock · Open the report
LowThird Party DependencySHANTI · CertiKOpen

The contract is serving as the underlying entity to interact with a third party ServicePayer. The scope of the audit treats third party entities as black boxes and assume their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. ```solidity=577 constructor(address payable receiver, string memory serviceName) payable { ``` - The function `ServicePayer.constructor` interacts with third party contract with `IPayable` interface via `receiver`.

The audit on Trustblock · Open the report
LowUnchecked Blocks Can Optimize ContractSHANTI · CertiKOpen

The following function can use unchecked blocks to save gas on each call: - `decreaseAllowance()`: `_approve` can be put inside of an unchecked block to save gas due to the require statement preventing overflow and underflow. - `_transfer()`: the change in values in `_balances[sender]` and `_balances[recipient]` can be put inside of an unchecked block due to it not being able to overflow or underflow as `_totalSupply` cannot pass the max value of uint256. - `_mint()`: the change in value inside of `_balances[account]` can be put inside of an unchecked block due to it not being able to overflow or underflow as `_totalSupply` cannot pass the max value of uint256. - `_burn()`: the amount burned inside of `_balances[account]` and `_totalSupply` can be put inside of an unchecked block due to the require statement preventing overflow and underflow.

The audit on Trustblock · Open the report

The SHANTI security record · Every SHANTI address · This address on the explorer