Decentrawood contract 0xe77a…5235 on Polygon (POS)

0xe77abb1e75d2913b2076dd16049992ffeaca5235

As of 21 Nov 2026, Trustblock’s record holds 0xe77abb1e75d2913b2076dd16049992ffeaca5235 on Polygon (POS) as a contract of Decentrawood. 1 audit report on Trustblock lists this address: CertiK, 7 Aug 2024. 3 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 Polygon (POS).

AuditSecurity firmDateCommit named in the reportReport
Decentrawood - AuditCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports3

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

HighCentralization Risks in Decentrawood.solDecentrawood - Audit · CertiKOpen

In the `Decentrawood` contract: - The `owner` has authority over the following functions: 1. `renounceOwnership`: Renounce the ownership of the contract. 2. `transferOwnership`: Transfer ownership of the contract to a new contract. - The `admin` has authority over the following functions: 1. `allotmentByAdmin`: Allot a certain number of tokens to the specified account. - The `marketingTeamAddress` has authority over the following functions: 1. `allotmentByMarketingTeam`: Allot a certain number of tokens to the specified account. - The `developmentTeamAddress` has authority over the following functions: 1. `allotmentByDevelopmentTeam`: Allot a certain number of tokens to the specified account. - The `strategicAllianceTeamAddress` has authority over the following functions: 1. `allotmentByStrategicAllianceTeam`: Allot a certain number of tokens to the specified account. Compromising the privileged roles within this smart contract could enable attackers to misuse their authority by allotting token to accounts on behalf of themselves. Such actions could result in unfair token distribution.

The audit on Trustblock · Open the report
HighInitial Token DistributionDecentrawood - Audit · CertiKOpen

The initial 100 million `Deod` tokens are sent to several externally-owned account (EOA) addresses [`airdropWalletAddress`](https://polygonscan.com/address/0x4a8ca6f4e245a3573a88fbe5925f445bc1724419) (20 million) and [`liquidityWalletAddress`](https://polygonscan.com/address/0xcf6418116002b1e5681cd3279aab579e53742910) (80 million). This is a centralization risk because the deployer or the owner(s) of the EOAs can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.

The audit on Trustblock · Open the report
LowVariables That Could Be Declared as ImmutableDecentrawood - Audit · CertiKOpen

The linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.

The audit on Trustblock · Open the report

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