Architecture Constraints

2. Architecture Constraints

Any requirement that constrains software architects in their freedom of design and implementation decisions or decision about the development process. These constraints sometimes go beyond individual systems and are valid for whole organizations and companies.

Table 2.1 Technical Constraints
Constraint	Explanation
C1	Participation in the prediction market will require using $TOKEN as the medium of exchange.
C2	Prediction market contracts must be deployed on Arbitrum One.
C3	Admin, and eventually, select creators must be able to create prediction markets.
C4	Positions in markets must be tradeable after being opened.
C5	Positions in markets must be closeable after being opened, but before the market resolves.
C6	Any arbitrary question must be able to be handled by the oracle.