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":1502,"date":"2023-01-20T10:56:34","date_gmt":"2023-01-20T10:56:34","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1502"},"modified":"2023-01-26T06:41:53","modified_gmt":"2023-01-26T06:41:53","slug":"introducing-amulets-2023-roadmap","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/introducing-amulets-2023-roadmap\/","title":{"rendered":"Introducing Amulet’s 2023 Roadmap!"},"content":{"rendered":"\n
\n\n\n\n

Story So Far:<\/strong><\/p>\n\n\n\n

Amulet was first announced as a project on April 20th 2022 at DevCon in Amsterdam. Since then, we’ve grown at an extraordinary rate. Within weeks we announced our seed funding news and our community (the AmuNation) started to grow. A successful launch of our AmuNation app loyalty program, TestNet with incredible feedback and eventually onto the MainNet on September 29th 2022, Amulet has seen steady month-on-month success. <\/p>\n\n\n\n

All this during a turbulant time for the industry overall. Within days of introducing Amulet’s simple, reliable cover for everyone in web3, the Luna\/Terra crisis unfolded and UST depegged causing significant shockwaves across the entire industry. <\/p>\n\n\n\n

Amulet came out fighting and grew steadily organically across the crypto landscape. The UST situation provided further substance to our BUIDL as it highlighted the issues within the risk protection industry and the dilemmas current cover providers were about to face. Payout and annoy stakers or don’t pay out and lose crediblity – a question that would never be asked of Amulet thanks to our innovative PCR (Protocol Controlled Reserves).<\/p>\n\n\n\n

Launching on the MainNet at the end of September saw us continue a rise with sales as high as 580%<\/strong> ahead of competitors at their time of launch. This created additional hype as we prepared for Solana Breakpoint in Portugal.<\/p>\n\n\n\n

Then the second crisis penetrated the crypto industry. While at Breakpoint, rumours potential issues at major exchange FTX were spreading on Twitter. As we launched on the Solana chain, we understood the implications this could have on the whole market but, in particular, on Solana. <\/p>\n\n\n\n

FTX’s collapse and bankruptcy has been in all international mainstream news. Amulet has always been cautious – (our solution is literally to protect DeFi users!) and we were fortunate to face 0 exposure to the crisis. That being said, we acted fast to pause immediate sales and our TVL was drastically reduced.<\/p>\n\n\n\n

Sales have now resumed and Amulet ended the year with continued social and community growth. Smashing through 30k<\/strong> Discord members and 40k<\/strong> Twitter Followers KPIs that had been set previously. On Twitter, Amulet has the biggest following against every other major cover protocol in web3. <\/p>\n\n\n\n

As of time of writing, we’ve now sold 784 covers<\/strong> across 8 protocols<\/strong>. Capacity is regularly increasing as users stake $aUWT into our MainNet and users are generating high %APYs by staking $amtSOL.<\/p>\n\n\n\n

As the market starts to stabalize (and we hope it continues!), our TVL is starting to recover and we have high expectations of huge increases throughout 2023.<\/p>\n\n\n\n

Access our MainNet here: app.amulet.org<\/mark><\/a><\/strong><\/p>\n\n\n\n

Introducing our plans for the year ahead.<\/p>\n\n\n\n

\n\n\n\n

2023 Roadmap:<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

We have high ambitions for 2023 and we’re delighted to share our intial vision for the next 12 months. Please understand that unexpectated scenarios can occur and there may be modifications or changes to this roadmap in the coming weeks and months. <\/p>\n\n\n\n

Q1:<\/strong><\/p>\n\n\n\n