metafam / chievemints Goto Github PK

Is your feature request related to a problem? Please describe.
The current app is awesome but I think it is time to improve on the UI.

Describe the solution you'd like
Improved UI which would enhance UX and make the app more consistent with the MG brand.

Describe alternatives you've considered

Additional context

Is your feature request related to a problem? Please describe.
When I go to the Chieves UI at https://chiev.es and look at the prior NFTs, I do not like seeing the additional NFTs & roles that are not associated with MetaGame - Not-A-Cop, Cop Accustion etc. imo, these should have been created on a completely separate UI & contract to the MG chieves UI.

IMO it is confusing and inconsistent with the brand for a user visiting https://chiev.es to carry out MG business finds stuff relating to HotRocks. Likewise if someone visits the contract page on OpenSea, it shouldn't have non-MG related NFT displaying.

Describe the solution you'd like
I'd like to see the chieves contract redeployed, replaced in the app and only used for MG related NFTs

Describe alternatives you've considered
Hiding the NFTs from the UI would be one solution but they would still show up on OpenSea as NFTs minted on that contract and I don't think it looks great.

Additional context

Is your feature request related to a problem? Please describe.
Often I will want to test an NFT or something without it showing up on the main contract in OpenSea and such. I would love to be able to mint test NFTs to testnet before I create the final production copy that will be sent out.

Describe the solution you'd like
Deploy a clone of the UI which uses a contract deployed on testnet.

Describe alternatives you've considered
Not really sure if there is an alternative. Happy to go with what others think is best but would like some ability to run tests and to not have to put everything on mainnet polygon.

There is a desire to create tokens that are transferable by their owners without creating individual permission tokens for each owner.

A solution for this would be to create a new type of permission token. Currently there are two types: universal tokens that give a user a permission for all token types and specific tokens that give a permission only for a particular type. The new permission type will disable that particular permission type, so creating one for transfer for a token type would allow any user to transfer without a check.

The token ids are bit fields. There is a flag that represents a token is a gating token. An additional field represents the type of gating. Another option could be added to that field for the new type.

With the current token types, a check is made if the requesting user holds the pertinent token. For this new type it is sufficient simply that the type exists. This is possible because we maintain a mapping between token ids and their index in the all types array.

Is your feature request related to a problem? Please describe.
As a player/innkeeper/event host in a community Discord, I want to award another player/member or maybe everyone in vc with a fun chiev by using a slash command and for an NFT to get minted to their MetaGame registered wallet. Like we had with the original Chievmint but evolved

Describe the solution you'd like
A bot in Discord that is able to mint chiev NFTs to a players registered address. The artwork generated by Stable Diffusion and set pieces done by artists of MetaGame.

A user types the command along the lines of !chiev to: @Musashi, reason: being a great host or simply for a host to use !chiev voice for a poap to those present and the content of the command or the event name & image in Discord become the metadata & artwork for the NFT. Maybe used as part of a seed for generating the artwork with SD.

Describe alternatives you've considered
Would love to hear thoughts from folks.

Is your feature request related to a problem? Please describe.

Problem 1: As an onboarding user who is new to blockchain and never used Polygon before, I get put off by hearing I have to pay for gas to mint an NFT because I don't have any MATIC and only used mainnet. I want to be able to claim my NFT for free or at least not have to jump down another rabbit hole in order to claim it.

Problem 2: Imagine There's a Chiev NFTs bot in Discord and it needs to be able to mint NFTs to player wallets on command and shouldn't need the awarding user or receiver to pay any gas.

Describe the solution you'd like
Like we had with dekan's Chievmint; a chiev fundster NFT that when minted, the user pays $1, $5, $n and that funds the wallet that has the minter role which pays for users using the system.

Maybe down the line the $ from the fundsters buys seeds which gets staked and the yield pays the gas.

A user with a Creator token is able to generate new token types. When a new type is created a maintainer is specified. The maintainer is given Minting, Metadata Configuration, and Limiting permission tokens for the newly generated type.

Currently the permission tokens are not working. The first 32 bits of each token are an id. For vanilla tokens that id is the index of the token in the list of all tokens (and thus unique). For permission tokens, those bits are the id of the token that the token permissions.

My best guess is the permission token isn't being created of dereferenced properly.

What should be done is the creation of a new Chai test stepping through the creation process to use to identify the exact issue.

Is your feature request related to a problem? Please describe.

One of our grant milestones is deploying the chiev contracts on Optimsim

Describe the solution you'd like

Simple deployment, and swap out the cheiv network/address to OP on Metagame.wtf

https://app.charmverse.io/op-grants/page-27013511701775395