📢 Contributions for the first AGIX staking epoch on Cardano are now OPEN! All whitelisted users can now deposit their tokens directly on our staking portal:

t.co

#AGIXonCardano

Contributions for the first AGIX staking epoch on Cardano are now OPEN! All whitelisted users can now deposit their tokens directly on our staking portal:

staking.singularitynet.io

Note: some amendments to the upgrade notice given yesterday. Please re-read entirely, if you are a validator. Hello, all our loyal validators. A proposal to upgrade Bluzelle chain will be put forth this week. The proposal will almost 100% pass, so we would like to ensure all our community is prepared to do the upgrade, based on the block height (TBA). As you all know, it is imperative that validators do the upgrade in a timely manner. Once the chain comes back up with the newly upgraded code, and starts to create blocks, any validators that have not yet upgraded will be considered "down". This means that they run the risk, given enough "down time" (ie: missed blocks), of being slashed and jailed. This is a highly undesirable outcome for any validator and its delegators. Obviously we absolutely want to avoid this situation, which is why we are giving you all as much of a heads up as is reasonably possible. Some points: =========== - The upgrade will be called "10.0". The current version is tagged "v.9.0", referring to our internal version 9.0. So, the upgrade will be tagged "v10.0", with the major number changing from 9 to 10 to signify a mandatory upgrade. Upgrades that do not result in state change will only have a change in the minor number. So, for example, if we subsequently released a new version that was non-state-changing, we might go from 10.0 to 10.1. But then, if an upgrade results in a new binary that has state changes, we'd go from 10.1 to 11.0. - Proposals go through and get accepted after the 7 day voting period set on Bluzelle chain. This having been said, we will reach the required quorum for the proposal to pass, within minutes or hours of the proposal being proposed. - The block height for the upgrade will be set to be approximately 10-14 days from when the proposal is proposed, to give the community more than adequate time to read these notes and prepare for the upgrade. - The new code for the upgrade is still being worked on, and will be made available on our "bluzelle-public" Github repo. This may happen before or at the time that the upgrade block height is reached. We will specifically tag the upgrade code as "v10.0" on bluzelle-public to avoid any confusion, and will announce this on Discord and Telegram. - We will also put out a release, on bluzelle-public, based on the code tagged at v10.0. Included in this release will be an amd64 Linux binary for the new version of "curiumd". Feel free to use this binary for your upgrade, or to build your own binary from code. The binary is provided as a convenience and comes with no warranties. - Once the upgrade height is reached, the chain will be DOWN for a short period of time, so that our validators and the community validators can upgrade to the new chain. - We leave the process of how community validators do the upgrade, to each operator. Some may choose to use Cosmovisor, while others may choose to do the upgrade by some other method. PLEASE be prepared to do the upgrade in a timely manner. We assume each validator operator is adept and experienced to do the upgrade without delay, when the block height is reached. - As mentioned above, timing is essential. The upgrade height may happen at a time that is not ideal for many timezones, so you need to plan to do the upgrade, despite this, and ensure you do not get slashed and jailed. A brief (not comprehensive) changelog: ===================================== - Fixed ipfs Network Address Translation issue with profile configuration transformer - Fixed ipfs directory reinitialization - Added optional argument to pinCid transaction, specifying ipfs node id of cid content provider - Added query to retrieve the last NFT collection ID - Updated grpc and genproto version

Greetings Singularitarians! Our valued first epoch stakers have already helped uncover the first Staking Portal issue! 😅 Updated Timeline: The launch of the staking portal is postponed 24 hours, to November 16th, 12:00 pm UTC. The first deposit period will last 11 days, whitelisted users will be able to deposit until November 27th, 09:00 am UTC. We are working hard with our partners at MLabs to resolve the logic issue, and have succeeded in closing the first half of the ticket. The second half is being worked on by the best developers on both of our teams, who feel confident it will be resolved within 24 hours. This issue has resulted in the need to dissolve the first pool-instance, and build a fresh one (our staking solution was designed to make the creation of new pools easy, allowing for staking pools with different parameters…a future community governance decision!). Thank you to our early testers for their diligence and patience in helping bring the best experience possible to our community. 🙏

This issue has resulted in the need to dissolve the first pool-instance, and build a fresh one. Our staking solution is designed to make the creation of new pools easy, allowing for future staking pools with different parameters…a future community governance decision! 3/4

Any additional instructions will be emailed directly to our first-epoch stakers. Thank you to our early testers for their diligence and patience in helping bring the best experience possible to our community. 🙏 4/4

STAKING UPDATE -- The launch of the staking portal is postponed 24 hours, to November 16th, 12:00 pm UTC. The first deposit period will last 11 days, whitelisted users will be able to deposit until November 27th, 09:00 am UTC. 1/4👇🧵