Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-sites domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-schema-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the uael domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the convertpro-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6131) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1902
{"id":1462,"date":"2022-12-09T10:16:31","date_gmt":"2022-12-09T10:16:31","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1462"},"modified":"2022-12-09T10:16:38","modified_gmt":"2022-12-09T10:16:38","slug":"metabear-nfts-official-utility-information","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/metabear-nfts-official-utility-information\/","title":{"rendered":"MetaBear NFTs: Official Utility Information"},"content":{"rendered":"\n
Amulet has been on quite the journey over the last 12 months. From initial ideation, project announcement, our impressive seed funding raise to the launches of the AmuNation app, TestNet and finally on the MainNet.<\/p>\n\n\n\n
MetaBear NFTs were introduced to the AmuNation in October 2022. The first phase release to our Early Contributors was successful and we’ve seen our MetaBears showcased across the Web3 bubble ever since.<\/p>\n\n\n\n
We’re delighted to present our official utility information for our MetaBear NFTs. <\/p>\n\n\n\n
As many will know, our NFTs are grouped into 3 separate categories: Gold\/Pro (88), Silver\/Elite (888) and Bronze\/Daily (8,888).<\/p>\n\n\n\n
The numbers in brackets indicate the current supply for each NFT category.<\/p>\n\n\n\n
This blog will reveal the utility that is already live and functioning on the MainNet today as well as the planned future benefits of holding onto the MetaBear NFTs.<\/p>\n\n\n\n
Please note that numbers indicated for the future can be subject to change.<\/p>\n\n\n\n
Live NFT Utlity – Q4 2022<\/strong><\/p>\n\n\n\n We’ve gone live with the first phase of the use case for our MetaBear NFTs. <\/p>\n\n\n\n This utility is for our Cover Discounts. <\/p>\n\n\n\n