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":1801,"date":"2023-07-19T12:04:27","date_gmt":"2023-07-19T12:04:27","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1801"},"modified":"2023-10-23T10:56:07","modified_gmt":"2023-10-23T10:56:07","slug":"amunation-ama-recap-18th-july-2023","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/amunation-ama-recap-18th-july-2023\/","title":{"rendered":"AmuNation AMA Recap: 18th July 2023"},"content":{"rendered":"\n
\n\n\n\n
The team sat down with the AmuNation for one of our regular AMA sessions. Well attended, considering a lot of our community are currently on their vacations, the Amulet team discussed some of the exciting things to come in the next weeks and months.<\/p>\n\n\n\n
One of the announcements during the AMA was Rupert’s transition to an advisor role within the project. His wealth of experience and industry knowledge will continue to guide us towards success. Additionally, the team unveiled thrilling plans for upcoming products, further fueling excitement among the AmuNation.<\/p>\n\n\n\n
We are delighted to present the audio recording and transcript of this engaging AMA session, allowing you to immerse yourself in the discussions that took place and gain a comprehensive understanding of Amulet Protocol’s latest developments.<\/p>\n\n\n\n