district0x / district-designer Goto Github PK

1. Implement contracts for marketplace.

2. Create separate migration file for marketplace module.
   Migration should go like:

• (It's assuming core migration to be done, for deploying ProxyFactory, DistrictFactory, District)
• deploy FixedPricesOffer.sol
• deploy DynamicPriceOffer.sol
• deploy HighestBidAuctionOffer.sol
• deploy MultiTokenAuctionOffer.sol
• deploy DeliverableAuctionOffer.sol
• deploy OfferGroup.sol
• deploy OfferGroupFactory.sol
• create OwnerProxy for OfferGroupFactory

3. Add tests

1. Implement contracts for tokens.

2. Create separate migration file for tokens module.
   Migration should go like:

• (It's assuming core migration to be done, for deploying ProxyFactory, DistrictFactory, District)
• deploy ERC20TokenFactory.sol
• deploy ERC721TokenFactory.sol
• deploy ERC1155TokenFactory.sol
• deploy TokenFactory.sol
• create OwnerProxy for TokenFactory

3. Add tests

1. Implement contracts for TCR.

2. Create separate migration file for TCR module.
   Migration should go like:

• (It's assuming core migration to be done, for deploying ProxyFactory, DistrictFactory, District)
• deploy RegistryEntry.sol
• deploy ParamChangeEntry.sol
• deploy TCR.sol
• deploy TCRFactory.sol
• create OwnerProxy for TCRFactory

3. Add tests

1. Implement DistrictFactory.sol and District.sol.
2. Create migrations to deploy contracts. We'll have separate migration file for deploying contracts of each module.
   Migration will go like:

• deploy ProxyFactory.sol
• deploy District.sol
• deploy DistrictFactory.sol
• Call ProxyFactory.createOwnerProxy to create a proxy which forwards to deployed DistrictFactory. (This is further explained in contract comments)

3. Create tests for ProxyFactory, DistrictFactory, District.
   As for storing contract addresses, normally contract addresses will be stored in orbitdb, but you can come up with some temporary solution meanwhile to pass addresses to the tests. Or maybe tests can have different way of obtaining addresses than the app. Leaving this for your ideas.

Migrate project from lein to shadow-cljs.
Add appropriate documentation into readme.