EOS

In the contract `system_contract`, the `self` can execute functions: - init - retire - blockswapto - swaptrace If the deployer controls the contract account’s `active` permission, they can effectively call any action that `require_auth(get_self())`. - `require_auth(get_self())` ensures that only the contract itself can authorize the action. - However, the deployer (or any other entity controlling the contract's permissions) can sign transactions as the contract account. - This means the deployer can call any self-protected action because they can authorize it on behalf of the contract. Any compromise to the deployer account may allow a hacker to take advantage of this authority and burn all the XYZ, block any account from calling `swapto()`, or emit `swaptrace`.