Don't waste your time with this..it obviously not out of alpha phase.
I give up on XZC ..before I completely destroy my drive.
Topic: [ANN] Zcoin (XZC) - Implementing ZKP privacy without trusted setup - page 255. (Read 663312 times)
February 09, 2017, 04:34:56 PM
February 09, 2017, 04:26:10 PM
no block source available my wallet says. MAc computer.
Help me please, i won't deposit my XZC to my mac wallet until i know what is that "no block source available" thing.
February 09, 2017, 03:53:59 PM
HAve also to create new wallet the old one got destroyed by the client.. which crappy codebase the dev took to make this built? Seriously these are old bitcoin-core issues.
Thanks for the upload but the wallet seems to have serious issue with this:
After this debug entry this wallet dies..crap crap crap..dev failed!
Then it starts rescanning over and over in a loop.. again dev you failed.
Let me sum it up: FAILED shit sorry but I can't find nicer words for this crap seriously.
Total written and totaled 3.5TB by zcoin-qt wallet..thanks for wear level my drive ...that sucks
Thanks for the upload but the wallet seems to have serious issue with this:
After this debug entry this wallet dies..crap crap crap..dev failed!
Quote
2017-02-09 20:59:20 ZCoin version v0.8.7.4-unk (2017-02-08 02:29:10 +0100)
2017-02-09 20:59:20 Using OpenSSL version OpenSSL 1.0.1j 15 Oct 2014
2017-02-09 20:59:20 Default data directory C:\Users\user1\AppData\Roaming\zcoin
2017-02-09 20:59:20 Using data directory C:\Users\user1\AppData\Roaming\zcoin
2017-02-09 20:59:20 Using at most 125 connections (2048 file descriptors available)
2017-02-09 20:59:20 Using 12 threads for script verification
2017-02-09 20:59:20 scrypt: using scrypt-sse2 as detected.
2017-02-09 20:59:20 init message: Verifying wallet...
2017-02-09 20:59:20 dbenv.open LogDir=C:\Users\user1\AppData\Roaming\zcoin\database ErrorFile=C:\Users\user1\AppData\Roaming\zcoin\db.log
2017-02-09 20:59:20 Bound to [::]:8168
2017-02-09 20:59:20 Bound to 0.0.0.0:8168
2017-02-09 20:59:20 init message: Loading block index...
2017-02-09 20:59:20 Opening LevelDB in C:\Users\user1\AppData\Roaming\zcoin\blocks\index
2017-02-09 20:59:20 Opened LevelDB successfully
2017-02-09 20:59:20 Opening LevelDB in C:\Users\user1\AppData\Roaming\zcoin\chainstate
2017-02-09 20:59:20 Opened LevelDB successfully
2017-02-09 20:59:20 LoadBlockIndexDB(): last block file = 0
2017-02-09 20:59:20 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=12100, size=34906947, heights=0...11120, time=2014-10-31...2016-12-10)
2017-02-09 20:59:20 LoadBlockIndexDB(): transaction index disabled
2017-02-09 20:59:20 LoadBlockIndexDB(): hashBestChain=f1d0747b36df0a7149982bbcb5d9f76b46c43863c3dff37099db14d93b18691c height=11120 date=2016-12-10 00:13:30
2017-02-09 20:59:20 init message: Verifying blocks...
2017-02-09 20:59:20 Verifying last 288 blocks at level 3
2017-02-09 20:59:20 Using OpenSSL version OpenSSL 1.0.1j 15 Oct 2014
2017-02-09 20:59:20 Default data directory C:\Users\user1\AppData\Roaming\zcoin
2017-02-09 20:59:20 Using data directory C:\Users\user1\AppData\Roaming\zcoin
2017-02-09 20:59:20 Using at most 125 connections (2048 file descriptors available)
2017-02-09 20:59:20 Using 12 threads for script verification
2017-02-09 20:59:20 scrypt: using scrypt-sse2 as detected.
2017-02-09 20:59:20 init message: Verifying wallet...
2017-02-09 20:59:20 dbenv.open LogDir=C:\Users\user1\AppData\Roaming\zcoin\database ErrorFile=C:\Users\user1\AppData\Roaming\zcoin\db.log
2017-02-09 20:59:20 Bound to [::]:8168
2017-02-09 20:59:20 Bound to 0.0.0.0:8168
2017-02-09 20:59:20 init message: Loading block index...
2017-02-09 20:59:20 Opening LevelDB in C:\Users\user1\AppData\Roaming\zcoin\blocks\index
2017-02-09 20:59:20 Opened LevelDB successfully
2017-02-09 20:59:20 Opening LevelDB in C:\Users\user1\AppData\Roaming\zcoin\chainstate
2017-02-09 20:59:20 Opened LevelDB successfully
2017-02-09 20:59:20 LoadBlockIndexDB(): last block file = 0
2017-02-09 20:59:20 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=12100, size=34906947, heights=0...11120, time=2014-10-31...2016-12-10)
2017-02-09 20:59:20 LoadBlockIndexDB(): transaction index disabled
2017-02-09 20:59:20 LoadBlockIndexDB(): hashBestChain=f1d0747b36df0a7149982bbcb5d9f76b46c43863c3dff37099db14d93b18691c height=11120 date=2016-12-10 00:13:30
2017-02-09 20:59:20 init message: Verifying blocks...
2017-02-09 20:59:20 Verifying last 288 blocks at level 3
Then it starts rescanning over and over in a loop.. again dev you failed.
Let me sum it up: FAILED shit sorry but I can't find nicer words for this crap seriously.
Total written and totaled 3.5TB by zcoin-qt wallet..thanks for wear level my drive ...that sucks
February 09, 2017, 03:49:33 PM
Boah it rescans all time the blocks.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
sorry haha, theres another reason to not download shit from others i guess :/ :/ (only official sources)
Could you please so kind to do it once again this way:
Do the snapshot as follows:
Close the client
copy blocks and chaindata, database and peers.dat that would be a fix.
I had this similar behavior on bitcoin..but not that much of wear level to an drive this is really insane.
Thanks
kk i highlighted those 4 and turned them into a zip, uploading now eta 20 mins
here you go, hope that works
https://mega.nz/#!a4ohlTYI!lXV7tZqmJqqAKLM2xPmAeDAQADIcSUwM8ZcnOm9yBNM February 09, 2017, 03:37:35 PM
Pointless to release GPU algorithm when the miner isnt optimized at all. Will only lead to instamining by those who do have access to an optimized miner, just like Zcash.
February 09, 2017, 03:31:43 PM
Boah it rescans all time the blocks.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
sorry haha, theres another reason to not download shit from others i guess :/ :/ (only official sources)
Could you please so kind to do it once again this way:
Do the snapshot as follows:
Close the client
copy blocks and chaindata, database and peers.dat that would be a fix.
I had this similar behavior on bitcoin..but not that much of wear level to an drive this is really insane.
Thanks
kk i highlighted those 4 and turned them into a zip, uploading now eta 20 mins
February 09, 2017, 03:29:17 PM
Boah it rescans all time the blocks.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
sorry haha, theres another reason to not download shit from others i guess :/ :/ (only official sources)
Could you please so kind to do it once again this way:
Do the snapshot as follows:
Close the client
copy blocks and chaindata, database and peers.dat that would be a fix.
I had this similar behavior on bitcoin..but not that much of wear level to an drive this is really insane.
kk i highlighted those 4 and turned them into a zip, uploading now eta 20 mins
February 09, 2017, 03:21:00 PM
Cpuminer working from block 20500
https://mega.nz/#!DN4SFDRD!IJaYuuYBsjzHR_7JHCTCCIBJU77thI8L-X-eSYTGBxA
no viruses
https://mega.nz/#!DN4SFDRD!IJaYuuYBsjzHR_7JHCTCCIBJU77thI8L-X-eSYTGBxA
no viruses
Can you post your AMD miner build ?
February 09, 2017, 03:19:14 PM
Apparently not worth it for any AMD type of GPUs with the current miner.
Basically a CPU is faster than most of the AMD GPUs.
RX 470 gets like 200-250KH/s which is same as an i5 CPU.
While an old GTX 960 gets 500KH/s
Basically a CPU is faster than most of the AMD GPUs.
RX 470 gets like 200-250KH/s which is same as an i5 CPU.
While an old GTX 960 gets 500KH/s
So basically, GPU mining is pointless.
Not on NVIDIA..
Here it performs very good.
4GTx1080 @ Stock doing 8500KH/s
February 09, 2017, 03:13:20 PM
Apparently not worth it for any AMD type of GPUs with the current miner.
Basically a CPU is faster than most of the AMD GPUs.
RX 470 gets like 200-250KH/s which is same as an i5 CPU.
While an old GTX 960 gets 500KH/s
Basically a CPU is faster than most of the AMD GPUs.
RX 470 gets like 200-250KH/s which is same as an i5 CPU.
While an old GTX 960 gets 500KH/s
So basically, GPU mining is pointless.
No idea if this will reduce botnets since there are many i3 and i5 cpus out there which perform reasonable pretty fast compared to GPUs.
February 09, 2017, 03:10:54 PM
Apparently not worth it for any AMD type of GPUs with the current miner.
Basically a CPU is faster than most of the AMD GPUs.
RX 470 gets like 200-250KH/s which is same as an i5 CPU.
While an old GTX 960 gets 500KH/s
Basically a CPU is faster than most of the AMD GPUs.
RX 470 gets like 200-250KH/s which is same as an i5 CPU.
While an old GTX 960 gets 500KH/s
So basically, GPU mining is pointless.
February 09, 2017, 03:09:08 PM
Boah it rescans all time the blocks.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
sorry haha, theres another reason to not download shit from others i guess :/ :/ (only official sources)
Could you please so kind to do it once again this way:
Do the snapshot as follows:
Close the client
copy blocks and chaindata, database and peers.dat that would be a fix.
I had this similar behavior on bitcoin..but not that much of wear level to an drive this is really insane.
February 09, 2017, 03:05:38 PM
Apparently not worth it for any AMD type of GPUs with the current miner.
Basically a CPU is faster than most of the AMD GPUs.
RX 470 gets like 200-250KH/s which is same as an i5 CPU.
While an old GTX 960 gets 500KH/s
Basically a CPU is faster than most of the AMD GPUs.
RX 470 gets like 200-250KH/s which is same as an i5 CPU.
While an old GTX 960 gets 500KH/s
February 09, 2017, 02:17:44 PM
Boah it rescans all time the blocks.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
sorry haha, theres another reason to not download shit from others i guess :/ :/ (only official sources)
February 09, 2017, 02:10:49 PM
Boah it rescans all time the blocks.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
Something was wrong when you made the copy CjMapope.
2TB this stupid client wear my SSD now..dev please really fix this odd behavior of this client this is killing drives in short time.
February 09, 2017, 02:00:50 PM
which one? what GPU? ;p goto #mining in Slack dude, there all mostly there getting built by people and testing
The last post in the #mining on the slack was last week. Its seems the entire slack is completely dead.
are you in the right slack friend? haha https://zcoinofficial.slack.com , (theres a few "zcoin" slacks), we just got compute for 5.0 compiled now and AMD is "on its way" . everyone should be hopefully good to go by fork i hope
lol
went to the wrong slack. Basically the one that was created when this coin was Scrypt-N algo
i KNEW that was the only explanation , you are far from a troll or stupid, glad your in!
Do I need an invite? Or is it free for all to join? Doesn't seem to let me inside.
it looks like it? https://get.slack.help/hc/en-us/articles/201330256-Invite-new-members-to-your-Slack-team
apparently i cant even see the link as i am but a guest account or w.e :/
well thats kinda a stupid barrier ...
Edit: found it in the OP!
http://invite.zcoin.io:3000/ February 09, 2017, 01:58:09 PM
Something went totally wrong with the blockchain and chainstate copy.
It wrote/changed 1TB of data to my disk 2h running wallet wont start.
What the crap..this is the worst bug i have seen ..even the cryptonite wallet was doing better.
You wear out my ssd so badly that very bad design seriously.
I have to start all over again..
It wrote/changed 1TB of data to my disk 2h running wallet wont start.
What the crap..this is the worst bug i have seen ..even the cryptonite wallet was doing better.
You wear out my ssd so badly that very bad design seriously.
I have to start all over again..
February 09, 2017, 01:54:39 PM
which one? what GPU? ;p goto #mining in Slack dude, there all mostly there getting built by people and testing
The last post in the #mining on the slack was last week. Its seems the entire slack is completely dead.
are you in the right slack friend? haha https://zcoinofficial.slack.com , (theres a few "zcoin" slacks), we just got compute for 5.0 compiled now and AMD is "on its way" . everyone should be hopefully good to go by fork i hope
lol
went to the wrong slack. Basically the one that was created when this coin was Scrypt-N algo
i KNEW that was the only explanation , you are far from a troll or stupid, glad your in!
Do I need an invite? Or is it free for all to join? Doesn't seem to let me inside.
February 09, 2017, 01:35:09 PM
which one? what GPU? ;p goto #mining in Slack dude, there all mostly there getting built by people and testing
The last post in the #mining on the slack was last week. Its seems the entire slack is completely dead.
are you in the right slack friend? haha https://zcoinofficial.slack.com , (theres a few "zcoin" slacks), we just got compute for 5.0 compiled now and AMD is "on its way" . everyone should be hopefully good to go by fork i hope
lol
went to the wrong slack. Basically the one that was created when this coin was Scrypt-N algo
i KNEW that was the only explanation , you are far from a troll or stupid, glad your in!
February 09, 2017, 01:33:53 PM
which one? what GPU? ;p goto #mining in Slack dude, there all mostly there getting built by people and testing
The last post in the #mining on the slack was last week. Its seems the entire slack is completely dead.
are you in the right slack friend? haha https://zcoinofficial.slack.com , (theres a few "zcoin" slacks), we just got compute for 5.0 compiled now and AMD is "on its way" . everyone should be hopefully good to go by fork i hope
lol
went to the wrong slack. Basically the one that was created when this coin was Scrypt-N algo
Jump to: