• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
Ethermon DAOEthermon DAOby0xe7F3E12203685fB1c0b62b0C1D829A23A0438fB2ethermondao.eth

7 Day REVOTE - Thunderzen Drop Error Disposition

Voting ended almost 3 years agoSucceeded

This DAO Vote options are to finalize the disposition plan for Frosslord which was airdropped as Thunderzen class ID.

Background: Frosslord was supposed to be dropped for players; however, a mistake was made during airdrop that Thunderzen (a rare and limited) mon class was dropped instead. The DAO have seek community feedback and concluded with the following options for a DAO vote.

The most chosen option will be followed and executed to the current team and community to the best of its ability.

Option 1) Replace Thunderzen class entirely as Frosslord A New Thunderzen class will be created, and dropped to the original 9 holders.

Positive Effect to original Thunderzen holders:

  • The original 9 holders with the rightful owner of Thunderzen (under a new classID)
  • The original 9 holders will also get a free Frosslord.

Negative Effects to original Thunderzen holders:

  • User’s new Thunderzen perfection likely will be different than before. To mitigate this effect, the team will provide 1 free perfection reroll option for these mons. (Creating a new contract to adjust perfection can create a backdoor, and rolling each mons on dev side till it’s better than previous perfection before sending to users have been ruled out as a none-option at this time)
  • User’s tokenID will be swapped, specifically Thunderzens airdropped to existing 9 players will have tokenIDs updated.

Other Side Effects:

  • The XP of new Thunderzens sent will be mapped to old Thunderzens, so players can get back their "original" Thunderzen’s exp. All exp for Thunderzens will be offchain, and users may need to pay gas to claim back their levels. In another word, all new thunderzens would be set back to on chain level 1, onchain and offchain exp will be ported as offchain exp only.

Option 2) Unintended minted IDs (Thunderizen) are converted to burnable ticket NFTs which can be burned for spin a wheel tickets . These NFT will no longer be able to play in game (behave like other tickets. (Exact same treatment as Snobbit and Hambrisk NFT as burn tickets for the reward wheel)

Frosslord to be sent to all users as originally intended to receive one.

Only these tokenID that are added to a special burn tokenID list which will be detected when burn as the same as Snobbit and Hambrisk as an off chain spin a wheel ticket. These tokenID will be updated, and special handling will be done on the current Ethermon games by adding offchain exception list to the fullstack to have special treatment to these IDs to the front end ethermon website. Essentially this act as a soft ban.

Significant large amount of patching work needs to be done here, and may expect loop holes that need to be patched in various parts of the game and ecosystem as users discover them and report them across the ecosystem.

Positive Effect to original Thunderzen holders:

  • No immediate difference as before the event happens, thus no impact to their collector’s value and rarity.

Negative Effects to original Thunderzen holders:

  • The class may be considered tinted, from a onchain perspective, most of the mitigation is being executed in an offchain manner. Any one checking data only on chain for classes in the future can not tell a difference between the valid and none valid mons. The data is als not immutable as all control are front end basis, any future utility of Ethermon NFT in any interoperable and permissionless way may have no idea on the difference and thus threatening them the same.

Option 3) Request user to send back mon with enforcement measures

The current core team will attempt to get back from all users with volunteering help from community members. The team have been preliminary assess that it’s possible to be able to reach out to at least 80% of the users which have received the unintended drop. However, although many have preliminary responses they are willing and okay to send back to a centralized location or for permanent burn, some users have declined such invitations while some users are also unidentified or may be inactive.

Only those who have returned the untended drop of Thunderzen will be replaced with the originally intended Frosslord NFT drop.

Handling for any mons not returned will be done in a strict manner. i.e. Ban may be applied to users who choose not company by taking measures via any currently applicable centralized pressures until it is returned. Such measures may include and not limited to ban the mon from usage, ban user from earning, no longer allowing user to login.

Possible Side effect: spillover effect of any account which the mon is transfer or sold to likely need to be applied to prevent account flights, however this may create unintended consequences such as strategic or intentional and hostile usage of such bans in unintended ways. Such as sending a mon to top ranking users to temporarily disable them; or purchases by users who miss seeing the visual flags. Further on going developer intervention may be needed to take place until the side effects are eliminated or reduced over time.


Option 4) Request users to send mon back with community based oversight (Motivation same as Option 3, with different enforcement plans)

Currently the core team will attempt to get back from all users with volunteering help from community members. The team have been preliminary assess that it’s possible to be able to reach out to at least 80% of the users which have received the unintended drop. However, although many have preliminary responses they are willing and okay to send back to a centralized location or for permanent burn, some users have declined such invitations while some users are also unidentified or may be inactive.

Only those who have returned the untended drop of Thunderzen will be replaced with the intended Frosslord NFT.

Those who choose not to return and keep the mons are at their own judgement and discretion and for their own conscious decision and possible future community member peer pressure to return or continue to use the mons as normal. No special ban or penalty will be in place in any currently available centralized controllable ways. In this option these mons which are currently marked as "RESPAWNING IN PROGRESS" "TRADERS AWARE" will also be removed such that to avoid FUD or feature of people who could fear of purchases which may be in the future get locked/ban.

Off-Chain Vote

Retrieve Mon w/o Enforcement
566.49K EMON & EMONA5.4%
Retrieve Mon w/ Enforcement
5.16M EMON & EMONA49.3%
Swap ClassIDs Permanently
1.53M EMON & EMONA14.6%
Turn Mons to Wheel Tickets
3.2M EMON & EMONA30.6%
Quorum:349%
Download mobile app to vote

Timeline

Apr 30, 2023Proposal created
May 01, 2023Proposal vote started
May 08, 2023Proposal vote ended
Oct 26, 2023Proposal updated