To learn more about how businesses are integrating blockchain and AI together, download our latest data report in which we polle
15 Nov 2023, 00:36
To learn more about how businesses are integrating blockchain and AI together, download our latest data report in which we polled more than 600 IT decision-makers across the U.S., China, U.K., Germany, Austria and Switzerland.
Download:
Same news in other sources
215 Nov 2023, 00:50
Hi @everyone π£
There are a bunch of proposals waiting for your vote in the Governance dApp
π³π³π³π³π³
VNP-016 CHANGE MARKET.LIQUIDITY.STAKETOCCYVOLUME FROM 1 TO 20
VMP-16 CHANGE ETH/USDT-231231 FUTURE SLA commitment Min Time Fraction FROM 0.95 TO 0.85 π³
VNP-018 CHANGE MARKET.LIQUIDITY.SLA.NONPERFORMANCEBONDPENALTYMAX FROM 0.05 TO 0. π³
VMP-17 CHANGE BTC/USDT-231231 FUTURE SLA COMMITMENTMINTIMEFRACTION FROM 0.95 TO 0.85. π³
Let Vote π³ π³ π³ to participate in the governance process and future direction of Vega!π«Άπ«Άπ«Ά
Hi @everyone. There are a bunch of proposals waiting for your vote in the Governance dApp. VNP-016 CHANGE MARKET. LIQUIDITY.
Hi @everyone π£
There are a bunch of proposals waiting for your vote in the Governance dApp
π³π³π³π³π³
VNP-016 CHANGE MARKET.LIQUIDITY.STAKETOCCYVOLUME FROM 1 TO 20
VMP-16 CHANGE ETH/USDT-231231 FUTURE SLA commitment Min Time Fraction FROM 0.95 TO 0.85 π³
VNP-018 CHANGE MARKET.LIQUIDITY.SLA.NONPERFORMANCEBONDPENALTYMAX FROM 0.05 TO 0. π³
VMP-17 CHANGE BTC/USDT-231231 FUTURE SLA COMMITMENTMINTIMEFRACTION FROM 0.95 TO 0.85. π³
Let Vote π³ π³ π³ to participate in the governance process and future direction of Vega!π«Άπ«Άπ«Ά
15 Nov 2023, 00:48
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 "alfa", and for now, we will adopt a scheme of using the phonetic alphabet to name each upgrade, in ascending order. So, the next upgrade after alfa will be "bravo", etc.
- 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 "alfa" on bluzelle-public to avoid any confusion, and will announce this on Discord and Telegram.
- 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
Hello, all our loyal validators. A proposal to upgrade Bluzelle chain will be put forth this week.
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 "alfa", and for now, we will adopt a scheme of using the phonetic alphabet to name each upgrade, in ascending order. So, the next upgrade after alfa will be "bravo", etc.
- 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 "alfa" on bluzelle-public to avoid any confusion, and will announce this on Discord and Telegram.
- 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