Walkup-world

In the contract `WalkupSneaker` 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 pause/unpause the contract and mint NFTs to arbitrary addresses.  ----- In the contract `WalkupToken` 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 pause and unpause the contract. 

The `WalkupSneaker` and `WalkupToken` contracts inherits upgradeable contracts, indicating that it is part of an upgradeable system. Upgradeable contracts often pair with a proxy contract that is responsible for managing contract upgrades. The `privileged roles` of the proxy often have the authority to update the implementation contract, i.e., the `WalkupSneaker` and `WalkupToken` contracts. Any compromise of the privileged account could allow a hacker to exploit this authority, potentially altering the implementation contract pointed to by the proxy and thus executing malicious functionality within the implementation contract.

All of the WALKUP TOKEN tokens are sent to the contract deployer 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.

HTTP/HTTPS should not be used for token metadata because the server owner can change token metadata at will, which can dramatically affect the token value.