FYI - there are some issues with zerocoin and it will be disabled and probably removed. We were due to go live with it on block 150,000, but due to another vulnerability with the protocol we are currently voting to remove it entirely from the next release. It will be votable at some point on the wallet, but if you wish to have your voice heard then please head over to discord and look for it in our proposals section.

---

We're going to drop ZeroCoin after maxnodes go live. It will continue to be in maintenance mode until then. Maintenance mode is essentially disabling the services. I think I am probably the only person who has some minted zLYTX, so it just impacts me.

---

Maxnodes are starting to come together, folks

We just updated out website yesterday. As for the official team it is myself doing the main coding, running the network, marketing and all that stuff. This is me on linkedin - www.linkedin.com/in/nat-h-6382b8157

We have a lot of community contributors like Eureka, Tybibourne, Multi21 (did the new website), luke, Bitcoinminion, LordSoylent and others that have helped with development, scripting, support, etc. It's a good community effort, so I encourage you to join us on Discord. We also have a very good, positive group on board. All very helpful and generally wonderful people from all over the world. Our community is absolutely our strength. 

So, we are in the top 5% in volume at Crex24 - right behind DASH. If only we could have the same price

---

Price increased 213% today on Crex24.com. We are #2 at Crex24 for biggest gains for the day.

When moon? Buy LYTX, buy LYTX, Buy LYTX!!! Arise LYTX!

---

sorry, just had to - reminds me of BTC-e back in the days of chikun

If you need to synch up quickly you can use the bootstrap.dat file that is on the latest release. That should get you over the hump and ready to stake.

Eureka was a real hero busting through block 100,000.

---

how bout nope

We should be on Crex next week. I wish they would get rid of the Copper Member BS. I see that and I immediately do not trust you.

---

we are on bisq.network now: https://bisq.network/downloads/

Larry should have his exchange ready soon.

Currently stuck at block 99,999 like block 14944. I'm trying to find a way past it but not able to fix it at the moment

I found a critical bug in the Proof of Stake conversion that would have only paid out 2 LYTX. So, to avoid this catastrophe I have to get everyone to update AGAIN (sorry.) All clients, masternodes, vps, anything Lyitx needs to be updated before PoS switch over in about 35 hours.

This version will up the reward from 30 to 100 LYTX (50 staker/50masternode) for 10,000 blocks. You can find the binaries here: https://github.com/LytixChain/lytix/releases/tag/v1.7.4. Mojave will be out tomorrow.

solo cpu only - there are only about 8000 blocks left before we go to PoS anyway

It will after about 17 hours.

I'll be switching on the spork, meaning move to 1.7.3 at Human time (GMT): Thursday, February 14, 2019 1:00:00 AM UTC

Mine with the wallet - go to Tools > Debug Console > Enter setgenerate true 1

If you are on the CLI use lytix-cli setgenerate true 1

to turn it off enter setgenerate false

If you want to use more processors change the 1 to the number of processors you want to use

---

All,

We are releasing version 1.7.0. This release is a MANDATORY release, because this is accelerating Proof of Stake from block 500,000 to block 100,000. To give time to coin holders and masternode operators we will enforce the release by activating spork 17 around block 90,000. Burning 1440 blocks a day that will be around Feb 19th.

On Tuesday Feb 19th at 1500 UTC I will enable spork 17 which will enforce protocol 71031 on all nodes. Nodes on 71030 or the previous releases will be dropped. Please upgrade at your earliest convenience.

Changes:

PoW to end at 100,000
Modifications to the treasury awards at 10%
ZeroCoin start at 150,000
Gitian build modifications
Block CheckPoints added
Re-added CTLV work
dnsseed changes

Release binaries are here: https://github.com/LytixChain/lytix/releases/tag/v1.7.0

---

Whitepaper added - https://www.lytixchain.org/lytix_whitepaper_v1_0.pdf

Add feedback - https://docs.google.com/document/d/1wMw4JuvG_hh45joXK-BAknDj1Mr4tJgQCzP-WyVfyn8/edit?usp=sharing

Thank you

---

New release - https://github.com/LytixChain/lytix/releases/tag/v1.7.3

Please make sure you upgrade to 1.7.2 or 1.7.3 if you are on a previous version. I will enable the spork to block previous versions in about 6 days. All clients and masternodes need to be updated to ensure continued service.

Thanks

The link in the ANN still works. It's not set to expire - same as the web page - https://discordapp.com/invite/CZfZ7Ex

---

All,

I just wanted to share a really innovative way a few of our coin holders have figured out how to have multiple masternodes on a single instance without needing another IP or using IPv6. I wrote this guide on discord, but wanted to share it with you as well. Our coin is based on PIVX, so any PIVX masternode coin will most likely be able to use the same methods.

To build multiple masternodes on the same host using the same binaries that are in your path

Assuming a 1 Processor VPS at vultr running Ubuntu 16.04

On the VPS create a directory to house the copies of the data folders (lytix.conf, wallet.dat, etc) - assuming you have rights to drop directories in / - /lytix can be whatever you want it to be

mkdir -p /lytix/mndir



Create subdirectories for each of the masternode hosts you want to run. We're going to assume 5 in addition to the one you probably already have running

mkdir mndir/mn1
mkdir mndir/mn2
mkdir mndir/mn3
mkdir mndir/mn4
mkdir mndir/mn5



Create a new lytix.conf in each directory that will have a different rpcport. For this example we will use port 28081 for mn1, 28082 for mn2, 28083 for mn3, 28084 for mn4, and 28085 for mn5
---- lytix.conf in mndir/mn1 ----

rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
rpcport=28081

---- lytix.conf in mndir/mn2 ----

rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
rpcport=28082

---- lytix.conf in mndir/mn3 ----

rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
rpcport=28083

---- lytix.conf in mndir/mn4 ----

rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
rpcport=28084

---- lytix.conf in mndir/mn5 ----

rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
rpcport=28085

I don't recommend starting them all at the same time, because they are all going to jump to about 30% system utilization downloading the chain and updating.
Just give each a little time to update. As of this writing the chain was at about 45,000 and it took a few minutes to fully retrieve the chain. Once the daemon has fully synched it will drop down
to around 4-8% system utilization.

Start each masternode by doing this:

lytixd -datadir=/lytix/mndir/mn1
lytixd -datadir=/lytix/mndir/mn2
lytixd -datadir=/lytix/mndir/mn3
lytixd -datadir=/lytix/mndir/mn4
lytixd -datadir=/lytix/mndir/mn5

On the gui client that you have the masternode.conf configured you will go through the same procedure in creating a regular masternode. Change the alias to something that you can remember:

masternode genkey


getaccountaddress mn101



send the 5000 LYTX to that address

Update the masternode.conf on the client with the same IP as the masternode, but with the alias above "mn101" and the other information like the output of genkey and the tx id that you see after
running

msaternode outputs

You will see multiple after it has confirmed, so look in the transactions and find the payment to self you just created to get the txid if you need it. You will now need to update the lytix.conf on the new masternodes with the following information: masternode=1 masternodeprivkey=private_key_from_output_of_masternode_genkey_above Restart the masternode to pick up the new config:

lytix-cli -datadir=/lytix/mndir/mn1 stop
lytixd -datadir=/lytix/mndir/mn1

Restart the gui client as well to pick up the new masternode.conf config. After 15 confirmations you can start the new masternode. Special thanks to our resident royalty LordSoylent for spelling this out for us

yes, read above - dev active - do stuff

So, made the decision to keep the coin as it is and not cause any more churn for our coinholders. The coin will be CPU minable via the wallet until block 100,000. We'll move to Proof of Stake at that period. If you want to mine the coin please use the client downloaded from our github site. No other method will work or be supported.

I have a Linux guide here: http://www.lytixchain.org/guides/masternode.html

We also have a lot of members that run them on Windows as well. Head over to our discord masternode channel if you need any help getting going.

cute purple font - not sure why you have not found a block yet. Only thing that I can guess is that your hashrate may not be enough to find one. We have about 64 people mining right now, so it may take some time to find a block. We've made some good investigative progress on debugging the client's adversity to pools. It looks like there is a discrepancy in the code with the nVersions. Wanting to start zerocoin off on block 1 I inadvertently pushed it to version 4 which caused some issues. I have a clone that I am going to try a few things to see how we can get past this with the least amount of disruption as possible.I'll keep you all informed as we make progress and when the fix will be in.

Thank you for finding that. I missed that in the Footer Card. I really liked Bulwark's block explorer and modified it to match Lytix. We aren't traded yet, but part of the cron jobs that get kicked off test for market price on coinmarketcap and for the time being I just left it to check for Bulwark's price. I added a notation stating that it is not the real Lytix price. I wish it were. That'd be fantastic.

Thank you for the well wishes. We have some initial bumps in the road with this coin, but I will keep on it and eventually we'll have a good product to market and bring good things to those that are involved.

Just so you know this project isn't about getting rich for me or stopping the effort and soon as we go to market. I'd never do that to folks. I hope that this coin and the foundation will be able to serve folks well and do some good in the world. We have a really smart, nice community (quiet, but when pools kick in it might get rowdy), so I encourage you all to join us on Discord - https://discord.gg/CZfZ7Ex. I'll always be responsive here, so if BCT is your mainstay then no worries. This is my home, too.

---

We just asked to be submitted at MNIFO - https://www.mnroi.info. Nice site with good info. Thanks for reaching out.

Not yet. We are working to get some going. What we've encountered is that we think the template that is getting sent down is off and is what is possibly causing shares to be rejected by mining pools. We are pretty close to figuring it out. I'm sorry it is taking so long to get this fixed, but it's an odd issue.

The worst case scenario will be possibly rechaining and forking. If that happens then I will credit everyone again in the new wallet with an additional hardship bonus. I hope it doesn't come to that, but our nBits are showing up as off. Wherever I make any changes to the chain with nBits then it will fork the chain.

I know it is frustrating, but you can still mine using the client for the time being. Rewards are still 15 for the miner and 15 for the masternode.

New pool -

POOLS
community run
icopool - stratum+tcp://icopool.club:27073 -a quark -u WALLET -p x

---

We really need some working pools, please. We have some great miners with super gear and I'd love to let them loose on the hashing.

---

testnet is now open to test mining on pools. Expect frequent changes. The ports are 27072 for main testnet and 27074 for rpc testnet. This is my main focus this week to solve the pool issue with the clients. i appreciate anyone's help in getting this going. I always drop LYTX for help and testing.

Miners and nodes that brought blocks 9999, 10000 and 10001 got 1000 LYTX each. We'll do the same for 15,000 Thanks for your support!