# Build Plan

This is the master plan for building the Temple protocol.

The steps are listed in order as much as possible, but this order may change slightly.

Temple aims to offer an L3 chain to distribute, protect and monetise creative content / IP

What to build?

• ERC20 token contract
• Token Allocation Vesting contract
• Deployment scripts
• MORFD NFT contracts
• Orbit L3 chain
• Message bridging contracts/oracles

Here is a representation of the plan in a mindmap figure :

• Strict ERC20 standard
• Support snapshots or checkpoints for voting platforms
• Support voting functions -- need to define what this entails
• 18 Decimals
• Verify the Name and Symbol fall within the Orbit Gas token requirements
• Determine the following:
  • if upgradeability is required
  • Other functions such as pause
  • Max supply -- should this be removed to be a gas token?
  • Do we need a governance contract?

• Review existing implementations:

https://github.com/AbdelStark/token-vesting-contracts

https://github.com/moleculeprotocol/token-vesting-contract

• Either use one of the above as a base or write a custom implementation using some of the features from existing implementations above

• Deploy TASTE token contract with the chosen Name, Symbol, Decimals, and other params as specified by the team
• Deploy the Vesting contract

• Deploy an early L3 testnet to verify the TASTE token works for gas fees
• this can be turned on/off as needed
• can deploy this using Conduit or other free infra providers

• Token allocations API and Database
  • determine database to use
  • Define the database schema
  • Define the API endpoints
• POAP API and Database
  • determine the database to use (prefer the same as above)
  • Define the database schema
  • Define the API endpoints

TBD

TBD

TBD