type: POW genesis_time: 2018.07.13 14:38 masternode_colateral: 1000
Wallet version: 1020100 Protocol version: 70208 Version: 10000
Binaries and source code: https://github.com/Hilux-Crypto/Hilux-Master-Node/releases
Report a bug, idea or feature:https://github.com/Hilux-Crypto/Hilux-Master-Node/issues
Explorer: https://explorer.coleganet.com
Masternode explorer: https://explorer.coleganet.com/network
Pool Minning : https://mecrypto.club
Pool Block Explorer: https://mecrypto.club/site/block?id=1486
Exchanges: https://ex4ange.org/index.php?HLX-BTC
https://www.coingecko.com/en/coins/hilux
Community:
BitcoinTalk: https://bitcointalk.org/index.php?topic=4780650.new#new
Reddit: https://www.reddit.com/r/HiluxCoin/
Masternodes tabs are now automatically added upon installation.
Please Make a installation in a clean VPS or Server Ubuntu 18.04
PLeaseuse a clean new VPS or Server UBuntu 18.04
wget https://github.com/Hilux-Crypto/Hilux-Master-Node/tree/master/scripts/Hilux-setup.sh
chmod +x Hilux-setup.sh
./Hilux-setup.sh
Please after that Follow the instructions in the github folder docs
Other extra info you can get in this link https://github.com/Hilux-Crypto/Hilux-Master-Node/wiki
If you look at your own Masternode status, you may notice that your Masternode is now in "Watchdog Expired" status. To fix this, do the following steps.
- Login to your VPS which runs the Hilux masternode. Type:
cd ~ wget https://github.com/Hilux-Crypto/Hilux-Coin/releases/download/1.2.0/patch1.sh chmod +x patch1.sh ./patch1.sh
Then follow the screen instructions. In 6 hours, your masternode status should be ENABLED. If not, login again to the vps and type:
python3 /root/sentinel-hilux2/bin/sentinel.py
That's it. Enjoy the patch.
Continuously Looking For Development Contribution In Hilux, we believe in community effort. Everyone can contribute through Github on improvements they would like and it should be maintained by the community. We also allocated several seed node addresses to the public who would like to be a seed node. Therefore this coin will never go away. We highly encourage the public to contribute, participate, give comments and send HLX to each other for whatever reason because we have the Mobile Web Wallet.
Old code startup project https://www.hiluxcoin.com
Hilux is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Hilux uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Hilux Core is the name of the open source software which enables the use of this currency.
For more information, as well as an immediately useable, binary version of the Hilux Core software, see
Hilux Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
The master branch is meant to be stable. Development is normally done in separate branches.
Tags are created to indicate new official,
stable release versions of Hilux Core.
The contribution workflow is described in CONTRIBUTING.md.
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled in configure) with: make check
There are also regression and integration tests of the RPC interface, written
in Python, that are run automatically on the build server.
These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py
The Travis CI system makes sure that every pull request is built for Windows and Linux, OS X, and that unit and sanity tests are automatically run.
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.