- 1.1 Fat contract design
- 1.2 Data storage infrastructure
- 1.3 Kusama Grant Integration
- 1.4 Fees and token abstraction
- 1.5 Evaluate the limitations
-
Aim
- Define and evaluate the design based on user experience.
- Define the design effectiveness based on the cost of operation ( fees ).
-
- Qualitative ( Discussion with other team including Phala ).
-
- Define and evaluate storage layout in the contract.
- Define and evaluate external storage infrastructures ( Crust and others ).
Both include database reads and writes , cost of operations and user experience
-
- Provide a straight forward on-chain grant application for newly kusama users.
-
- Provide a notification system for users interactions on grants
- Abstracting chain centric approach user experience thus including but limiting to construction of preimages.
-
- Enabling users to use any token or fiat to apply for Kusama treasury grant.
-
- Ordum handling token conversion.
- Aiming to include subscription model to buy future blockspace for fees.
-
- Evaluate short comings of Fat Contracts e.g data races.
- Evaluate uptime and execution of Fat Contract.
- Evaluate portability of the issued certificates.