mainnet's Introduction

DEPRECATED LEGACY CHAIN

Vidulum 2.2.1

What is Vidulum (VDL)?

One minute block time
10 VDL total per block
3.2 VDL for masternodes per block
4.8 VDL for proof of work miners per block
2.0 VDL for Vidulum Reward System V-Staking
1440 Estimated blocks per day
Trading on STEX, CREX24, and Instaswap

Security Warnings

Vidulum is experimental and a work-in-progress. Use at your own risk.

Deprecation Policy

This release is considered deprecated 52 weeks after the release day. There is an automatic deprecation shutdown feature which will halt the node some time after this 52 week time period. The automatic feature is based on block height and can be explicitly disabled.

Building

Install dependencies

On Ubuntu/Debian-based systems:

$ sudo apt-get install \
      build-essential pkg-config libc6-dev m4 g++-multilib \
      autoconf libtool ncurses-dev unzip git python python-zmq \
      zlib1g-dev wget bsdmainutils automake curl

NOTE: Ubuntu 20.04 requires

$ sudo apt-get install python3-zmq

On Fedora-based systems:

$ sudo dnf install \
      git pkgconfig automake autoconf ncurses-devel python \
      python-zmq wget gtest-devel gcc gcc-c++ libtool patch curl

Windows:

sudo apt-get install \
    build-essential pkg-config libc6-dev m4 g++-multilib \
    autoconf libtool ncurses-dev unzip git python \
    zlib1g-dev wget bsdmainutils automake mingw-w64

On Mac systems:

brew tap discoteq/discoteq; brew install flock
brew install autoconf autogen automake
brew install gcc5
brew install binutils
brew install protobuf
brew install coreutils
brew install wget llvm

Check GCC version

gcc/g++ 4.9 or later is required. Vidulum has been successfully built using gcc/g++ versions 4.9 to 7.x inclusive. Use g++ --version to check which version you have.

On Ubuntu Trusty, if your version is too old then you can install gcc/g++ 4.9 as follows:

$ sudo add-apt-repository ppa:ubuntu-toolchain-r/test
$ sudo apt-get update
$ sudo apt-get install g++-4.9

Fetch the software and parameter files

Fetch our repository with git and run fetch-params.sh like so:

$ ./zcutil/fetch-params.sh

Build Linux/MAC

Ensure you have successfully installed all system package dependencies as described above. Then run the build, e.g.:

$ git clone https://github.com/vidulum/vidulum.git
$ cd vidulum/
$ ./zcutil/build.sh

This should compile our dependencies and build vidulumd

Build Windows

Ensure you have successfully installed all system package dependencies as described above. Then run the build, e.g.:

$ git clone https://github.com/vidulum/vidulum.git
$ cd vidulum/
HOST=x86_64-w64-mingw32 ./zcutil/build.sh

Need Help?

Join our Discord: https://discord.gg/bF2P5bV

Participation in the Vidulum project is subject to a Code of Conduct.

License

For license information see the file COPYING.

mainnet's People

Contributors

Stargazers

mainnet's Issues

Request - Add build options in the Makefile for cleveldb and rocksdb

For example, Osmosis and Stargaze both have added support for compiling their daemon with cleveldb and rocksdb support.
When you have time your leige, can we add these database options as a build option when compiling from source? :D

https://github.com/public-awesome/stargaze/blob/main/Makefile

https://github.com/osmosis-labs/osmosis/blob/main/Makefile

Dragonberry Update - Debrief

Devnet and testnet testing went well.

Halt height set by majority validators - did not stop chain.

guidance was incorrect due to the way several validators were set up with blockstorage.
we should have reset the attempt to use a designated halt height.

The chain was abruptly halted by turning off the needed validators to achieve 34%.

result was different validators had different halt heights.
guidance should have been provided to have everyone sync to the official halt height on 1.0 binary before updating to 1.2

Achieving 67% of the stake necessary to restart the chain was complex.

Validators need to be more readily available to support the chain during periods of upgrade.
Notice was not something we could provide due to the security risks
We highly recommend users delegate across the active set especially to those who were actively engaged in bringing the chain back online.

After achieving enough stake to bring the chain back online, due to the issues above several validators had the incorrect block header. They had signed the chain tip, last block, with the wrong binary, 1.0.0.

This was observed by Crypto Crew and Jabbey.
Crypto Crew tested the theory, and promptly provided instructions to the Vidulum Core team.
After review these instructions were made available on the official Vidulum github and further guidance was provided to the validator operators.

Shout out to those who were responsive in testing, halting, and coming back online. Unfortunately we didnt know if certain validators to bring the chain back online within the top 10. It was huge effort from the validators that was tackled with knowledge sharing, teamwork, and analysis from the group.

Key Observations:

During these events, instructions should be filtered through the Vidulum Core team and made publicly available through official Vidulum Mainnet Git. This would avoid confusion, reduce cyber risk, streamline any issues management.
A user notified that the issue with conflicting block headers occurred on unrelated cosmos sdk chain under unrelated circumstances. https://github.com/persistenceOne/incident-reports/blob/main/07-Sept-2022_V3_upgrade_halt.md

Recommend Projects

vidulum / mainnet Goto Github PK