⛓️Quest Object
"quest object" : how it relates to "on-chain activity"
Last updated
"quest object" : how it relates to "on-chain activity"
Last updated
Our quests cover a variety of on-chain activities, such as viewing a user's past gas fees, checking liquidity on Uniswap, viewing token balances, and reviewing gitcoin contribution history.
Each object is carefully designed to represent its associated activity.
Quest objects can be minted when the user meets certain conditions.
Quest Name | Quest Condition |
---|---|
Web3 ENS Owner | Own an ENS domain |
Web3 ENS Lookup | Configured ENS Reverse Record to current address |
Web3 ENS Avatar | Configured the 'avatar' record in your primary ENS |
Web3 ENS Website | Configured the 'url' record in your primary ENS with your philand URL |
Web3 ENS Subdomain | Setup an ENS subdomain |
Silver $ENS Hodler | Hold at least 100 $ENS |
Gold $ENS Hodler | Hold at least 1000 $ENS |
Quest has Network info. Uniswap Quest is Ethereum Quest. it means that if you create a tx, in Polygon, you can't claim this quest Object.
Initially, we planned to implement quest objects as non-transferable tokens that would be bound to a specific user (like SBT, Soulbound Token), but in the current implementation, quest objects can be transferred. You can also buy and sell on Opensea.
https://opensea.io/collection/phi-quest-object
Two smart contracts related to Quest Object:
QuestObject: '0x3D8C06e65ebf06A9d40F313a35353be06BD46038'
https://polygonscan.com/address/0x3D8C06e65ebf06A9d40F313a35353be06BD46038
PhiClaim: '0x754e78bC0f7B487D304552810A5254497084970C' https://polygonscan.com/address/0x754e78bC0f7B487D304552810A5254497084970C
In PhiClaim's claimQuestObject, ECDSA signatures are used. (This mechanism is similar to creating a Philand.)
The PhiClaim contract records user's address user who has claimed each token.
Using this information, we grant some roles on Discord for guild.xyz.
This phiClaimedLists is used to track completed quest information. You can check quickly by the account page.
When a user claims a quest object, the frontend sends a request for a coupon to the backend. Next, the backend checks the user's balance of USDC, and if it is sufficient, the system creates a token using an admin private key.
If the coupon is successfully created, the user can obtain the quest object by calling the 'claimQuestObject' function from the frontend using the PhiClaim contract.
As a unique feature, all quest objects have the concept of "exp." Currently, there is no significant utility to the exp value, but quest objects can be placed in a "philand" to increase the "Landpower." The exp value is determined when the quest object is created.
As demonstrated in the tweet example, our quest can drive the growth of the Ethereum ecosystem by collaboration with other web3 services. By using these other services, we can expand and enhance services, which will be beneficial for users, service providers, and PHI.
Collaboration with other web3 services will continue to be a crucial issue to address in the future
We are planning to gradually decentralize the creation of our QuestObject in future updates.
Please look forward to these updates.