BG Trade

In the contract `BGT` the role `_bridgeadmin` has authority over the functions shown in the diagram below.
Any compromise to the `_bridgeadmin` account may allow the hacker to take advantage of this authority and mint and burn tokens.
![](https://accelerator-tasks-prod.acc.corp.certik.com/d3ab94810dd04495b4a2032f58c6910b/diagrams/centralization_BGT-BGT-_bridgeadmin.svg)

In the contract `BGT` 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 and add bridge admin and Policeman to the contract.
![](https://accelerator-tasks-prod.acc.corp.certik.com/d3ab94810dd04495b4a2032f58c6910b/diagrams/centralization_BGT-BGT-_owner.svg)

In the contract `BGT` the role `_policemans` has authority over the functions shown in the diagram below.
Any compromise to the `_policemans` account may allow the hacker to take advantage of this authority and modify the Prohibit list.
![](https://accelerator-tasks-prod.acc.corp.certik.com/d3ab94810dd04495b4a2032f58c6910b/diagrams/centralization_BGT-BGT-_policemans.svg)

All of the BGT tokens are sent to the contract deployer or one or several externally-owned account (EOA) addresses. 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.

There should always be events emitted in the sensitive functions that are controlled by centralization roles.

One or more statements do not affect the functionality of the codebase and appear to be either leftovers from test code or older functionality.

```solidity=112
            amount;
```