Copyright (c) 2009-2014 Bitcoin Developers
Copyright (c) 2017-2019 The Linx Partnership
What is Linx?
Linx is an experimental cryptocurrency designed for the electronic music community that uses scrypt as a proof-of-work algorithm.
- 60 second block targets
- Retargets every block using Dark Gravity Wave 3
- 2mb block size
- Block reward reduces in stages depending on current coin supply (50,25,10,5,2,0)
- 100,000,000 total coins
- Block rewards end around the year 2030
- 6 confirmations
- 140 for newly minted coins
Block Reward Schedule In Detail
|From Block#||Block Reward||Est. Date||Total Supply|
Release notes for v188.8.131.52
There was a protocol upgrade in this version which includes important security fixes. All previous wallet versions must be updated to at least v184.108.40.206 as they will no longer be able to connect to the network. This rule came into effect on December 18th 2018 and you can read more about it here.
Download the latest compiled binaries for Windows and OSX here.
cd linX qmake make
See docs for flags, deps and more info.
If you are running linXd (the daemon) or want to run the Linx Wallet (Qt version) on the testnet you will need to create a .conf file.
- Create a blank text file and paste in the following:
rpcuser=ChooseAUserName rpcpassword=ChooseAStrongRandomPassword addnode=seed.mylinx.io addnode=testnet.mylinx.io
Save the file as linX.conf
Place it inside the following DIR depending on your system:
- Start Daemon / Wallet
Notes about the compiled Ubuntu binaries
This is NOT a static build. It requires external libraries for it to work. If you have built other wallets on your computer before, the chances are that you will already have all of the required libraries. If not see the build docs.
Other useful links
Main website : https://mylinx.io
Linx Twitter : https://twitter.com/linxcoin
Linx Mining pool : http://pool.mylinx.io
Linx Block Explorer : http://explorer.mylinx.io
Linx Block Explorer v2 : http://explorer2.mylinx.io
Slack Channel : https://linxcoin.slack.com
Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.
If it is a simple/trivial/non-controversial change, then one of the Linx development team members simply pulls it.
If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion with the devs and community.
The patch will be accepted if there is broad consensus that it is a good thing.
Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see
doc/coding.txt) or are controversial.
master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Linx.
The brand Linx and all logos and images are copyright (c)2017 The Linx Partnership.
Linx is an entirely experimental project and we offer no warranties or guarantees. Use entirely at your own risk.