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":1640,"date":"2023-04-06T10:20:25","date_gmt":"2023-04-06T10:20:25","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1640"},"modified":"2023-04-06T12:19:12","modified_gmt":"2023-04-06T12:19:12","slug":"amulet-lists-lido-on-mainnet","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/amulet-lists-lido-on-mainnet\/","title":{"rendered":"Amulet lists Lido on MainNet"},"content":{"rendered":"\n
\n\n\n\n
\n\n\n\n

Amulet Protocol<\/mark><\/a><\/strong> is delighted to announce that we have partnered with Lido<\/mark><\/a><\/strong> and listed their protocol on our MainNet. <\/p>\n\n\n\n

As Amulet is still Solana native, (our multi-chain plans are still being worked on in the background), we’ve listed Lido for assets on the Solana blockchain. In the future, there is potential to open this up to alternative chains as we grow.<\/p>\n\n\n\n

This is an exciting moment for Amulet as listing one of the biggest names in the world of blockchain, accelerates our mission to protect as many web3 users as possible.<\/p>\n\n\n\n

Lido (Solana) is LIVE on our MainNet today and users can stake $aUWT at an opening approximate APY of 10.39%<\/strong><\/p>\n\n\n\n

Limited capacity is already available for Lido users to protect their Solana assets. <\/p>\n\n\n\n

Get started staking\/protecting here: app.amulet.org<\/a><\/strong><\/p>\n\n\n\n

To understand the terms and conditions of our Smart Contract Vulnerability Cover, please refer to this document.<\/a><\/strong><\/p>\n\n\n\n

\n\n\n\n

More about Lido<\/strong><\/p>\n\n\n\n

Lido is the leading liquid staking solution, providing an easy and secure way for users to earn interest on their digital assets.<\/p>\n\n\n\n

Staking into Lido ensures that your assets remain liquid and can be used across a range of DeFi applications, creating opportunities for users to earn additional yield. <\/p>\n\n\n\n

Lido on Solana is a Lido-DAO governed liquid staking protocol specifically for the Solana ecosystem. Those staking SOL into Lido are issued with an on-chain representation of SOL staking with Lido validators named stSOL. <\/p>\n\n\n\n

Lido, specifically on Solana, gives users:<\/p>\n\n\n\n