Buidlers.Space

Screenshots

Problem Statement

ProblemNFT should be have value on it not just PFP. We create the super great Smart ContractBuidlerProtocolthat treat it as the central of the Builders! Every builders can create many build for themself for any project(every project is an NFT). Builder will continue add new build on the NFT, so their users(buyer) can mint NFT(buy it with $NST), then can sell it or make an Ask order, and the guy do not mint the NFT can buy NFT from the de-market or just make a new Bid for the NFT. While builder add new build for his/her NFT projects, they need to add the cidRaw and size, so later the SP can callactivateDealBySPto activate the deal, then call the withdrawReward with cidRaw to get the reward.

Solution

FEVM DataDAOwe use the FEVM Actor API in our smart contract to pay storage fee while builder add new item for their NFT build, and SP can activateDealBySP and withdrawReward. It depends the HyperActor from the @zondax/filecoin-solidityaddItem and pay $FIL to store deal: https://github.com/NftTopBest/buiders-space-fevm-lighthouse/blob/main/contracts/Item.sol#L12DataDAO: https://github.com/NftTopBest/buiders-space-fevm-lighthouse/blob/main/contracts/DataDAO.sollighthouse SDKencrypted content with access conditions: https://github.com/NftTopBest/buiders-space-fevm-lighthouse/blob/main/frontend/stores/mvStore.ts#L248decrypted content: https://github.com/NftTopBest/buiders-space-fevm-lighthouse/blob/main/frontend/stores/mvStore.ts#L224EIP2535 to build large contract https://eips.ethereum.org/EIPS/eip-2535Our contract is large, so we use the Diamond Tech to build our smart contract: use the diamond cut func to deploy more facts: https://github.com/NftTopBest/buiders-space-fevm-lighthouse/blob/main/contracts/DiamondCutFacet.sol