On the other hand, Paul, I had received two payments, one confirmed and one conflicted, from my MN in V2000 when I have updated my controller wallet to v2010. Just for info.
|
|
|
I have lot of problems after editing the darknet.conf with the :wq (pushed simultaneously, one after another, first : then wq???) I have tried some combinations but due the server lag, or my imcopetency or another thing I has been unable to record my changes. Then I have tried to stop the scrypt execution when the config file is opened. I have corrected it manually with nano darknet.conf in the .darknet directory and checked changes have been saved. All seems to be ok, ./darknetd, server started, then ./darknet-cli, but when the blockchain finish to load, i have this: { "version" : 2000100, "protocolversion" : 70300, "walletversion" : 61000, "balance" : 0.00000000, "obfuscation_balance" : 0.00000000, "blocks" : 259200, "timeoffset" : 0, "connections" : 10, "proxy" : "", "difficulty" : 48.59999131, "testnet" : false, "keypoololdest" : 1463951312, "keypoolsize" : 1001, "paytxfee" : 0.00000000, "relayfee" : 0.00010000, "staking status" : "Staking Not Active", "errors" : ""}
Version seems to be correct but blocks seems to be stucked in 259200. Is this normal or the way I have updated the server doesn't work?? Thanks
|
|
|
I also like that idea, and it's only a 0.14 % of the total supply, so no influence in price expected.
|
|
|
Showing pow blocks, maybe it's following a v1 fork???
|
|
|
Meanwhile on Bittrex, someone bought all the sell orders up to 800 sat. (Approx. 210K of DNET)
The current plan for the reduction in block rewards makes the next few months a good time to be running masternodes and staking. Let's hope there is the next few months adoption of DNET for than just for trading and speculation. So is it ok to use the master release from github? Are we there yet? :-) For the moment, wait to the next version to solve the comm problem happened with 2.0.0.0
|
|
|
I am working with the DNET team to implement a fix to the node communication issue. We worked late into the night and got quite a bit done. Now we are in the testing phase. Hope to have some better information for you all soon. As of now, I would expect to consider anything after 259200 as not valid. I think best route going forward will be for us to make sure this fix works, then mint 10-20 PoS blocks and then hard checkpoint it into the wallet, then distribute the new version.
I feel bad, this is my error in the code. Sorry to let you all down.
The only way to not fail it's not try it. I think that everyone involved in this coin from its early stage know that you were trying to get a new high to the Dashcoin scheme, and it would have its risk (first in something is always a risk, being this to land a rocket or to make the first POS wallet in the last bitcoin protocol). Big wallets in Bitrex are (unfortunately) not dumping so it's clear that almost everyone knows your honestity, professionality and work. Let's hope we can have that wallet working as soon as possible, if any testnet windows version can be run to help, don't hesitate to ask.
|
|
|
More than 6 hours, minging LYRA2REV2 at 45-55Mh/s and i earn 0.00070726 BTC....
Sometimes seems like these numbers get locked, more than 3 hours mining and this number don't go UP, but every hour goes down.
I really don't recomend this pool, Something weird about this, AT nicehash and Miningpool hub the gains are slower but are real.
LYRA2REV2 is highly influenced for the number of MONA and VERT found in a period of time. I'm mining in multialgo and this algo gets a good amount of time, and in the long run seems to be quite profitable. The only algo I have found real problems in zpool is myr-gr, SAFRON has been looking for a blake block for hours in the past and this has made a good amount of hash being inneficiently used. But in the long run, payments are quite constant and similar to other forums, with the advantage of its internal change rate, that allows to be paid in coins that are in an acumm state and sold it with 2x, 3x or more benefit. Yes, sometimes it doesn't happen and the coin never evolve from the shitcoin state, but that's a inherent risk in trading algos. Crackfoo, Safron blockchain seems not to have this problem anymore, can you confirm this to include it again in the round robin? Thanks.
|
|
|
I'm trying to resync using this conf file: addnode=173.245.158.8 addnode=108.61.151.69 addnode=coin-server.com addnode=dnetxn4m5kfh4xhr.onion:989 addnode=dnetxu5edp35e4rm.onion:989 addnode=dnetxef3rmouy5qo.onion:989 addnode=dnetxcvx4iqeunnk.onion:989 as recommended before in the tread. But I'm connected to Darknet but after waiting for 15 minutes no block have been synced. Any ideas??? Thanks.
|
|
|
Hi Paul, I know there is some problems with the POS transition. Two of my MN seems to be stucked at block 259200 but shows no errors, but the third one show this message "version" : 2000000, "protocolversion" : 70200, "walletversion" : 61000, "balance" : 0.00000000, "obfuscation_balance" : 0.00000000, "blocks" : 259200, "timeoffset" : 6, "connections" : 40, "proxy" : "", "difficulty" : 48.59999131, "testnet" : false, "keypoololdest" : 1460397145, "keypoolsize" : 1001, "paytxfee" : 0.00000000, "relayfee" : 0.00010000, "staking status" : "Staking Not Active", "errors" : "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."
Is there something we can do to solve this? Reinstall the update or something? Thanks HI its not our systems thats the issue it the coin they guys are working on a solution and im sure they will update it soon thanks Paul Ok, I know that it has no relation with the hosting, with the wallet itself instead. But I was wondering if maybe could be something we could do. Thanks
|
|
|
Hi Paul, I know there is some problems with the POS transition. Two of my MN seems to be stucked at block 259200 but shows no errors, but the third one show this message "version" : 2000000, "protocolversion" : 70200, "walletversion" : 61000, "balance" : 0.00000000, "obfuscation_balance" : 0.00000000, "blocks" : 259200, "timeoffset" : 6, "connections" : 40, "proxy" : "", "difficulty" : 48.59999131, "testnet" : false, "keypoololdest" : 1460397145, "keypoolsize" : 1001, "paytxfee" : 0.00000000, "relayfee" : 0.00010000, "staking status" : "Staking Not Active", "errors" : "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."
Is there something we can do to solve this? Reinstall the update or something? Thanks
|
|
|
Hi Crackfoo,
If I'm correct Dnet has finished its POW at height 259200. Please, check it and finish its mining if needed.
Thanks
|
|
|
Wallet synced ok, MN's synced ok, but I haven't received last payment from zpool's wallet, maybe it's only a matter of wallet syncing but I'm a bit concerned about it. On the other hand, havr you see volume and order book in Bittrex? Looks really promising.
payments take a bit longer after update i imagine good volume i agree You were totally correct, everything seems to be working very fine now. Time to wait for a really smooth pass to POS.
|
|
|
Wallet synced ok, MN's synced ok, but I haven't received last payment from zpool's wallet, maybe it's only a matter of wallet syncing but I'm a bit concerned about it. On the other hand, havr you see volume and order book in Bittrex? Looks really promising.
|
|
|
DNET seems to be mining only orphans. Related with the wallet update???
|
|
|
Hi Paul,
Now that DNET is going to pass to POS phase and well, I hope to the moon and so on I'm a bit concerned about MN's security. Is there something we should know or we can follow the instructions of some of the (very good) DASH MN's security setup available out there???
Thanks.
|
|
|
Before ask for entering c-cex maybe you should read the last posts of the Cryptojacks (CJ) thread... Salute
|
|
|
It's any of you having problems with difficulty settings?. I'm using a slightly modified version of JK scrypt and everything seems to work fine except initial diff adjustment(,d=value), and not sure it's a problem with my scrypt modification or with the pool.
|
|
|
Now I'm working ok in mine1.zpool.com. Yesterday I received blocks from it but although the computer was hashing the zpool web didn't show any hashing from my wallet. If I try to connect to mine.zpool.com I received no blocks from the stratum in lyra2r2 and x11evo at least.
|
|
|
I can no longer make a connection to lyra2v2 using mine.zpool.ca, mine1.zpool.ca worked.
can you try again? as well as mine2? Same problem here, with lyra2v2 and x11evo. Both working in mine1. Don't test in mine2, sorry. In both algos, apparently no block received from server (or no connection)
|
|
|
|