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":1155,"date":"2022-09-06T12:50:00","date_gmt":"2022-09-06T12:50:00","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1155"},"modified":"2022-09-06T13:53:19","modified_gmt":"2022-09-06T13:53:19","slug":"amulet-protocol-officially-launches-on-the-testnet-a-monumental-step-towards-launching-onto-the-mainnet","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/amulet-protocol-officially-launches-on-the-testnet-a-monumental-step-towards-launching-onto-the-mainnet\/","title":{"rendered":"Amulet Protocol officially launches on the TestNet, a monumental step towards launching onto the mainnet."},"content":{"rendered":"\n
Amulet Protocol is delighted to confirm their official TestNet launch, opening the test platform to members of the AmuNation. <\/p>\n\n\n\n
This news will come as no shock to \u201cEarly Contributors\u201d for Amulet, who were given exclusive 24-hour early-access as a reward for all the hard work that they have dedicated to promoting our project since our announcement in April. <\/p>\n\n\n\n
As September has now arrived, we are entering the most pivotal moment in our history to date. As per our official roadmap<\/mark><\/strong>,<\/a> the TestNet launch is a decisive step before we can launch onto the mainnet itself and users are able to start to protect their digital assets with Amulet officially. \u00a0<\/p>\n\n\n\n Access to our TestNet is available here: https:\/\/testnet.amulet.org\/<\/mark><\/a><\/strong><\/p>\n\n\n\n To be a success, we need to ensure that our solution is market ready. Deploying onto the TestNet now, allows our dedicated community members to experience our product and check out the functionality. <\/p>\n\n\n\n It is a vital element for our journey, and we need our community to work together to decipher potential bugs or issues. This allows us to continue to BUIDL in the background while also fixing potential errors that can only be found through others testing. <\/p>\n\n\n\n As a result, we have launched a new channel on our Discord to report anything or to provide any feedback. You can have a real effect on the success of Amulet Protocol. Just enter our server: Discord.gg\/AmuletProtocol<\/mark><\/strong><\/a> and find the #testnet-support-zone<\/strong> channel. \u00a0<\/p>\n\n\n\n As you will have seen, we recently announced our official relationship with Kudelski<\/mark><\/strong>.<\/a> They are conducting our audit to ensure that our platform will be market ready at the end of the month.\u00a0<\/p>\n\n\n\n Good news, it\u2019s ready. We will release this to the public later this week with all the key findings. <\/p>\n\n\n\n Now, the TestNet is open to our whole community (the AmuNation) after Early Contributors enjoyed their \u201cSneak Peek\u201d yesterday. <\/p>\n\n\n\n To take part, enter this link: https:\/\/testnet.amulet.org\/<\/mark><\/strong><\/a> and check out all the functionalities of our future platform. You should be able to test all the various functions \u2013 underwrite, cover, and earn via this link.\u00a0<\/p>\n\n\n\n Make sure you change the network in your wallet to “Test Network” and you can receive test SOL from this website: http:\/\/solfaucet.com<\/mark><\/a><\/strong><\/p>\n\n\n\n We will also be adding some TestNet tasks to the AmuNation App \u2013 this means you can earn rewards while testing our project. Sign up\/Log in here.<\/mark><\/strong><\/a>\u00a0<\/p>\n\n\n\n Vigilant testers will also be able to spot some of our partners that we have yet to announce publicly. More reasons to get stuck in and test. <\/p>\n\n\n\nWhy have we launched on the TestNet? <\/h3>\n\n\n\n
What about audit news? <\/h3>\n\n\n\n
So how do I take part? <\/h3>\n\n\n\n