Guys u need enforce MN payments. static const int64_t SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT_DEFAULT = TIME;// ON at 2017/11/09 @ 00:00 UTC LOL, pool.coin-miners.info back to enjoy 4.5 coins again, that happened few days again, now it again. Let us sell some coins before miner dump, then buy back. Important announcement! In connection with the work on the protocol for validating the blocks and preventing the creation of unplanned forks in the network in the future, payments to the Masternodes may be not regular. Do not worry, it's for a few days. It will not influence the network stability. Thank you for understanding. |
|
|
|
|
Important announcement!
In connection with the work on the protocol for validating the blocks and preventing the creation of unplanned forks in the network in the future, payments to the Masternodes may be not regular.
Do not worry, it's for a few days. It will not influence the network stability.
Thank you for understanding.
|
|
|
|
|
Dear community,
KZCash experienced a network fork, which resulted in appearance of several chains. It's happened as a result of several big miners misbehaving, who has ignored masternode payments.
How to switch to current valid chain:
1. Stop your wallet node.
2. Make a wallet.dat backup. Just in case.
2. Remove "blocks" and "chainstate" folders.
3. Remove peers.dat, banlist.dat.
4. Start wallet node.
Your wallet would sync to the valid chain and continue to work as expected.
If your masternode stuck in "NEW_START_REQUIRED" or "EXPIRED" mode, sync with valid chain, make sure that your node has synced metadata by checking "mnsync status" (must be MASTERNODE_SYNC_FINISHED) and try to "start-alias" it one more time.
|
|
|
|
|
Dear community,
We're temporary disabling InstantSend functionality due to potential quorum exploit method that was discovered in KZCash's codebase. This issue could lead to double spendings or a possible network forks, which is obviously not what we need right now.
As a result, right now any InstantSend transactions will fallback to normal confirmation times.
This part of protocol was inherited straight from Dash, and that's why they also desided to disable InstantSend network-wide too.
On the bright side, there are already known solution for this, so we have a chance of applying it through a network update a bit faster than Dash itself, as we don't have any strict hardfork schedule at this point that would limit us in doing that.
Thanks for understanding.
|
|
|
|
I was mining at kzpool for like 12hrs with 11hgz, not any payout made...im getting fud.. some1 pls guide me
ATTENTION! Concerning KZpool work. Minimum payouts are set at 5.00 KZC. User interface is still under development and will be improved in 5 days. Miners with relatively small power may suffer temporar delays in payments, but You can be sure all coins will be paid. Should any questions concerning pool payments appear please inform at pool@kzcash.kzWe will announce any improvements as they are completed. Thank You for supporting our Community! |
|
|
|
At last, we have p2pool for KZCash Open source, no hidden payments, no delays - if you find block - you take your reward.... Immediately see reward in your wallet.. Without "problem with interface and low HR" PPLNS metod - dont worry - your rewards are grow with time and if you take off your ASIC - you will take your rewards some more time after http://crypto.mine.nu:8279/static/P.S. To Devs - i think you must put this link to first page because - 1. Its first p2pool node for your coin; 2. It situated in Kazakhstan. P.S.S. If any people need (big DOA on this node - more than 2%) - we can start nodes in Russia and Europe, just let me know. Hmm.. technology uses p2pool, but> Browsers: 0 out, 0 in  |
|
|
|
first and last block, you know?? 79m ago 23m ago |
|
|
|
Thank you we all whaiting.
Want to underline that we appreciate and respect all the Community members. We announced earlier that we plan to arrange all technical issues by middle November (not only blockchain related) and move forward. Masternode holders are very important for us. And we do our best for the network to have as many independent Masternodes as possible at this stage to reach maximal decentralization. Please keep in mind that Masternode owners not only receive income but also have right to vote for DAO 10% distribution! Thank You again for Your support. Can I setup multiple Masternode on the same IP? no |
|
|
|
|
Good evening, dear Community!
Network has stabilized and working as expected.
To keep the network in stable state on current stage of development we must avoid enforcing of masternode payments verification, as it results in unexpected network forks in several cases with our current hashrate and lack of miners. At this point, payments to masternodes would happen randomly in average ratio of 40~70%.
This circumstance is caused by current protocol implementation (inherited from Dash), which is not suitable for bootstrapping with low network hashrate. In Dash's history there were similar cases when they were required to disable MN payment verification to avoid possible network forks, before network would get more mature.
Currently we're designing and testing possible protocol changes to achieve more guaranteed payments to masternodes without risks of network splitting.
In addition to that, we're working on inviting more pools and expanding mining ecosystem to avoid current mining centralization.
The final solution will be applied in the nearest future.
We work for You.
Follow our news.
|
|
|
|
|
Important announcement
With the 4500 block, the Dark Gravity Wave algorithm came into force, adjusting the size of the reward depending on the mining difficulty on KZCash network. The self-adjustment reward formula is known as: 2222222/(((Difficulty+2600)/9)^2)
Accordinlgy, with current difficulty, this is 86400 KZC per month = 4.5 coins per block + 10% reserved for DAO.
Possible range is between 86400 to 432000 KZC/month, depending on network difficulty.
|
|
|
|
We're glad to announce that KZCash network has successfully went through recent hardfork phase. Among with network strenghtening, it brings KZCash protocol change regarding masternodes payouts: blocks mined without honoring masternode protocol are now ignored by other nodes. Now, as majority of our users has upgraded to recent software and network has stablizied, you can continue to make transactions without any risks. If you've still didn't upgrade your node/wallet software, you can get it here: https://github.com/kzcashteam/kzcash/releasesIf your wallet has stuck on "out of sync" status: 1) Try to close your wallet. 2) Go to wallet's appdata (where it keeps local copy of a blockhain, including wallet.dat). 3) Make backup of your wallet.dat. 4) Remove folders "blocks" and "chainstate", and also banlist.dat. 5) Start your wallet. It would sync with recent network state and everything would go smooth from now. |
|
|
|
|
Dear community!
The hardFork of the KzCash coin is successfully rehabilitated.
New nodes now deny blocks from miners, who ignore the Masternode's reward.
Please, everyone who has not updated - do it right now.
|
|
|
|
|
Dear community!
As a result of recent protocol update, part of the network experienced split. We're working on a solution to stabilize network and will inform you about any required actions as soon as possible.
It is advisable to refrain from transactions at this time.
|
|
|
|
Hello I just added KZ CASH to https://pool.coin-miners.info stratum settings: -o stratum+tcp://stratum-eu.coin-miners.info:3533 -u KZCASH_WALLET_ADDRESS -p c=3533 Payouts are made automatically every 1 hours for all balances above 0.01, or 0.001 on Sunday. Thank's |
|
|
|
Dear community!
We want to inform you about the current situation and the next IMPORTANT changes.
Tomorrow 29.10.17 at 05.00 in Astana (23.00 GMT 28) until 19:00 in Astana (13.00 GMT) the developers will activate "SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT". The update includes an obligatory fee for Masternodes of 45%. The distribution was registered on the network since the launch of the project, but was optional. The attempt to implement the protocol at the network level without the hard-core failed. This was not a planned event, but the interests of clients for us are above all.
Our purpose is to fulfill our PROMISES according to the declared profits of the Masternodes on the network for their owners. Our team will hold the hardfork of the KzCash coin.
All owners of wallets, Masternodes will need to update the software.
Only the support of the new network and new software will be provided. It is also desirable to make backup copies of private keys before updating your clients. All balances will remain after the software update.
Users are advised to refrain from transfers on October 29, 17 to 19:00 in Astana (13.00 GMT).
All pools that wish to continue mining have to upgrade their console daemon KZCash. In case of any difficulties, please stop mining before resetting to eliminate useless waste of resources. We underline that we are interested in cooperation with all the pools and highly appreciate their input in network development.
Masternode owners will get instruction for setup (Linux).
We apologize for temporary inconvenience. All the balances will be safe at the hardfork moment.
We will keep you informed!
We will publish regularly our news in twitter.
Please follow us in twitter to get latest updates.
How to find the private key from wallet.dat file? Also will the previous wallet.dat work with the new software? Previous wallet.dat will work in the new version. |
|
|
|
New wallets will start rejecting the blocks of miners that ignore Masternode reward share at 18:00 in Astana (12.00 GMT)Updated version of the software! Do not use earlier versions!Windows wallet GUI - https://github.com/kzcashteam/kzcash/releases/download/v0.1.7.1/kzcash-1.7.1-gui-win-x86.zipLinux wallet GUI - https://github.com/kzcashteam/kzcash/releases/download/v0.1.7.1/kzcash-1.7.1-gui-linux-x86.zipAll owners of wallets, Masternodes will need to update the software.Only the support of the new network and new software will be provided. It is also desirable to make backup copies of private keys before updating your clients. All balances will remain after the software update. All pools that wish to continue mining have to upgrade their console daemon KZCash. We underline that we are interested in cooperation with all the pools and highly appreciate their input in network development. Linux Cli - https://github.com/kzcashteam/kzcash/releases/download/v0.1.7.1/kzcash-1.7.1-cli-linux-x86.zipNo additional actions required, just replace existing app with a new version.
It would detect and use existing blockchain automaticallyHOW TO UPGRADE MASTERNODE to 0.1.7.1 versionWINDOWS First, close your wallet and copy your wallet.dat to some safe place. Then just replace kzcash-qt.exe with a new one from the recent release. And run it. Than's all. LINUX We need to download new release, stop daemon, replace app and run it again. Let's do it! First, login as user under which KZCash daemon is running and stop your daemon. $ cd ~/kzcash
$ rm kzcash*
$ wget https://github.com/kzcashteam/kzcash/releases/download/v0.1.7.1/kzcash-1.7.1-cli-linux-x86.zip
$ unzip kzcash-1.7.1-cli-linux-x86.zip
$ rm kzcash-1.7.1-cli-linux-x86.zip
$ sudo chmod +x kzcash*
$ kzcash-cli stop
$ sudo cp kzcash* /usr/local/bin/
$ kzcashd -daemonThat's all. Wait a couple of minutes and check your node status: $ kzcash-cli masternode statusIt must end with: "status": "Masternode successfully started"
|
|
|
|
|
Dear community!
We want to inform you about the current situation and the next IMPORTANT changes.
Tomorrow 29.10.17 at 05.00 in Astana (23.00 GMT 28) until 19:00 in Astana (13.00 GMT) the developers will activate "SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT". The update includes an obligatory fee for Masternodes of 45%. The distribution was registered on the network since the launch of the project, but was optional. The attempt to implement the protocol at the network level without the hard-core failed. This was not a planned event, but the interests of clients for us are above all.
Our purpose is to fulfill our PROMISES according to the declared profits of the Masternodes on the network for their owners. Our team will hold the hardfork of the KzCash coin.
All owners of wallets, Masternodes will need to update the software.
Only the support of the new network and new software will be provided. It is also desirable to make backup copies of private keys before updating your clients. All balances will remain after the software update.
Users are advised to refrain from transfers on October 29, 17 to 19:00 in Astana (13.00 GMT).
All pools that wish to continue mining have to upgrade their console daemon KZCash. In case of any difficulties, please stop mining before resetting to eliminate useless waste of resources. We underline that we are interested in cooperation with all the pools and highly appreciate their input in network development.
Masternode owners will get instruction for setup (Linux).
We apologize for temporary inconvenience. All the balances will be safe at the hardfork moment.
We will keep you informed!
We will publish regularly our news in twitter.
Please follow us in twitter to get latest updates.
|
|
|
|
We are still writing a guide ...
Given the installation of the sentinel daemon, which is required from version 12.1 for correct operation
We need guide for windows masternode !!! To help WHATCHDOG_EXPIRED Please DO IT ! Devs ! And then somehow it is not fair for you there are two nodes stably working on the network, and other participants can not configure the nodes themselves since you do not give instructions on how to configure I do not understand why you write the same thing 20 times. I said above that we are writing a guide. If you do not know how to configure - expect and do not spam...pls |
|
|
|
|
We are still writing a guide ...
Given the installation of the sentinel daemon, which is required from version 12.1 for correct operation.
Pls..waiting
|
|
|
|
|
Show Posts
