Trying to sync from scratch I get: 2017-05-02 15:54:06,492 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,506 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,513 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,525 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,527 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,528 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,571 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,576 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,584 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,592 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,607 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,614 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,626 execute(148) Retrying database execute due to no such table: transactions
2017-05-02 15:54:06,629 execute(148) Retrying database execute due to no such table: transactions Use the latest version 3.13 for GitHub: https://github.com/hclivess/Bismuth/releases/tag/3.13I still have this problem... Is anybody actually reading this ?  Strange that you have problems.. file static/ledger.db seem doesn't exist. Or mempool.db. But I think first one, because I have this problem because deleted old one and didn't replace with new one.. |
|
|
|
51% attack owning the chain but with a different timespan and the most of the coin making all node rejecting new block mined ? Possible ?
Possible.. |
|
|
|
And by the way pool is working again. Happy mining..
It appears there are 6 hours of missed blocks. I wonder if that will end up being adjusted or if truly no blocks were solved by the pool for 6 hours. Were not mined.. Daemon stopped because of Scash daemon. It spammed log for 60GB. |
|
|
|
Such a shitcoin launch. Typical orphan race when few people control mining nodes. Fix it and relaunch few weeks after to save it. Instamined coins have no future.
Very very strange. Why they are dissapearing? |
|
|
|
|
Who knows where does the wallet stores?
|
|
|
|
Tried a lot of combimations of server in Google Compute. No luck to compile. So there is only one think last. GP...CPU of course  |
|
|
|
Pool zoi.acc-pool.pw is not working anymore....
Who said? Just moving to a new server. Stratum working. Payouts too. |
|
|
|
|
Hm..
from: too many arguments
from: too many arguments
./node.py: line 5: import: command not found
./node.py: line 6: $'\r': command not found
from: too many arguments
from: too many arguments
from: too many arguments
from: too many arguments
./node.py: line 11: $'\r': command not found
./node.py: line 12: syntax error near unexpected token `('
'/node.py: line 12: `app_log = log.log("node.log")
Does anyone know why won't run on Ubuntu 16?
|
|
|
|
How can I solve the problem of block loss?
This very strange. There are two variants. 1) Someone with powerfull hardwaree spams with blocks. So a lot of forks and most of our blocks are dissapeared. 2) Problem with diff so everybody spams with blocks, but only one accepted. I have only eight blocks, last block in the wallet yesterday evening at 22.00 now Italian Then all the last blocks found are lost eight blocks? some people mined thousands blocks and over 12000 coins. I have only one question... With what software and hardware? Fair start... CPUs 12, 24 cores.. |
|
|
|
How can I solve the problem of block loss?
This very strange. There are two variants. 1) Someone with powerfull hardwaree spams with blocks. So a lot of forks and most of our blocks are dissapeared. 2) Problem with diff so everybody spams with blocks, but only one accepted. |
|
|
|
Seems its working now, but to the point of: Please check carefully bellow code and notice that at the beginning almost all shares are accepted but at some point (end of code) all starts to be rejected. [2017-05-01 22:50:51] Starting Stratum on stratum+tcp://zoi.acc-pool.pw:8828
[2017-05-01 22:50:51] Stratum difficulty set to 0.0005
[2017-05-01 22:50:51] 48 miner threads started, using 'lyra2z330' algorithm.
[2017-05-01 22:51:00] CPU #19: 112 H, 24.32 H/s
[2017-05-01 22:51:00] Accepted 1/1 (100%), 112 H, 24.32 H/s, 61C
[2017-05-01 22:51:00] CPU #0: 132 H, 27.14 H/s
[2017-05-01 22:51:00] Accepted 2/2 (100%), 244 H, 51.46 H/s, 61C
[deleted]
[2017-05-01 22:55:53] CPU #1: 1492 H, 24.82 H/s
[2017-05-01 22:55:53] CPU #34: 483 H, 25.97 H/s
[2017-05-01 22:55:53] Accepted 34/34 (100%), 46.86 kH, 707.40 H/s, 62C
[2017-05-01 22:55:56] CPU #46: 1517 H, 26.84 H/s
[2017-05-01 22:55:58] CPU #42: 1516 H, 25.43 H/s
[2017-05-01 22:56:00] CPU #11: 1477 H, 24.66 H/s
[2017-05-01 22:56:02] CPU #32: 1537 H, 26.16 H/s
[2017-05-01 22:56:06] CPU #0: 1500 H, 24.72 H/s
[2017-05-01 22:56:10] CPU #10: 7955 H, 25.26 H/s
[2017-05-01 22:56:13] Stratum difficulty set to 0.0430565
[2017-05-01 22:56:13] CPU #14: 1376 H, 23.31 H/s
[2017-05-01 22:56:14] Rejected 1/35 (2.9%), 54.28 kH, 735.12 H/s, 62C
[2017-05-01 22:56:14] reject reason: low difficulty share of 0.0023501585941370523
Everything was fine until the pool raised the stratum difficulty, it's a pool problem. Hm.. I think you are right. Will lower diff. |
|
|
|
Ok just tried to compile and finding this warnings /usr/bin/ld: warning: libssl.so.1.0.2, needed by /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libcurl.so, may conflict with libssl.so.1.1
/usr/bin/ld: warning: libcrypto.so.1.0.2, needed by /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libcurl.so, may conflict with libcrypto.so.1.1
I'm on debian testing intel64 arch, anyone to help? Should I downgrade this two packages? or how to force it to work with 1.1 version? apt-get install automake autoconf pkg-config libcurl4-openssl-dev libjansson-dev libssl-dev libgmp-dev I haven't got libjannson-dev , after installing ./build.sh is finishing without errors but still with above warnings. Second problem is with ZOI.ACC.pool -
[2017-04-29 18:39:14] Starting Stratum on stratum+tcp://zoi.acc-pool.pw:8828
[2017-04-29 18:39:14] Stratum difficulty set to 0.0005
[2017-04-29 18:39:14] Stratum authentication failed
[2017-04-29 18:39:14] ...retry after 10 seconds
[2017-04-29 18:39:14] 48 miner threads started, using 'lyra2z330' algorithm.
[2017-04-29 18:39:24] Stratum difficulty set to 0.0005
[2017-04-29 18:39:24] Stratum authentication failed
[2017-04-29 18:39:24] ...retry after 10 seconds
[2017-04-29 18:39:34] Stratum difficulty set to 0.0005
[2017-04-29 18:39:34] Stratum authentication failed
[2017-04-29 18:39:34] ...retry after 10 seconds
[2017-04-29 18:39:44] Stratum difficulty set to 0.0005
Then after 6-10 mins
[2017-04-29 18:45:16] CPU #39: 59 H, 80.51 H/s
[2017-04-29 18:45:16] CPU #35: 143 H, 195.56 H/s
[2017-04-29 18:45:16] CPU #41: 59 H, 81.91 H/s
[2017-04-29 18:45:16] CPU #43: 59 H, 82.02 H/s
[2017-04-29 18:45:16] CPU #40: 60 H, 82.41 H/s
[2017-04-29 18:45:16] CPU #38: 60 H, 80.98 H/s
[2017-04-29 18:45:16] CPU #42: 59 H, 80.84 H/s
[2017-04-29 18:45:25] CPU #31: 211 H, 23.98 H/s
[2017-04-29 18:45:25] Rejected 1/1 (100.0%), 1622 H, 1993.96 H/s, 47C
[2017-04-29 18:45:25] reject reason: unauthorized worker
[2017-04-29 18:45:28] CPU #36: 272 H, 23.13 H/s
[2017-04-29 18:45:28] Rejected 2/2 (100.0%), 1894 H, 2017.09 H/s, 47C
[2017-04-29 18:45:28] reject reason: unauthorized worker
[2017-04-29 18:45:29] CPU #6: 321 H, 24.57 H/s
[2017-04-29 18:45:29] Rejected 3/3 (100.0%), 2215 H, 2041.66 H/s, 48C
[2017-04-29 18:45:29] reject reason: unauthorized worker
^C[2017-04-29 18:45:38] SIGINT received, exiting
Im still getting this problems with stratum authentication. ANYONE FROM THIS POOL TO HELP?[/size] Maybe you need to use Your added workername and it's pass. If you have some.. If not just create. |
|
|
|
Where is no exact calculator. But can make one. |
|
|
|
Whats the total supply of zoi?
21 millions. It would be around 12 millions after the first 6 months. This is not true, this coins source is based on XZC's source where a big error in the code allowed "hackers" to create an arbitrary number of coins for themselves using malicious zerospend transactions. https://zcoin.io/zcoins-zerocoin-bug-explained-in-detail/You can't really tell how much coins where maliciously generated, until you do some investigations with the block explorer but probably a lot I don't read code but the exploit has since been fixed on 28th March release right? https://github.com/zoincoin/zoin/releasesAt time of bug, ZOIN was 'dead' with a CAP of a few thousand so it's less likely it was exploited than Zcoin & Zcoin now has a valuation of $15 million despite that. Myself used Zoin to test the exploit actually because it wasn't fixed and if you check the block explorer, or rather the log files of the daemon you see lots of zero transactions (coinspends) before suddenly someone 'fixed' it by disabling the zeromints at all. The 'half dead' state was actually the best thing to happen for exploiters as you could test everything possible with very low difficulty and no one sniffing in the logs Okay, crypto is a gamble and you should never invest what you can't afford to lose, I wish you all the best with this coin I just wanted to point out (again, if you check back my posts in this thread) that there is at least some caution needed when playing with this coin. @Ocminer can you please reopen the Zoin Pool ? You don't like mine?( |
|
|
|
Whats the total supply of zoi?
21 millions. It would be around 12 millions after the first 6 months. This is not true, this coins source is based on XZC's source where a big error in the code allowed "hackers" to create an arbitrary number of coins for themselves using malicious zerospend transactions. https://zcoin.io/zcoins-zerocoin-bug-explained-in-detail/You can't really tell how much coins where maliciously generated, until you do some investigations with the block explorer but probably a lot I don't read code but the exploit has since been fixed on 28th March release right? https://github.com/zoincoin/zoin/releasesAt time of bug, ZOIN was 'dead' with a CAP of a few thousand so it's less likely it was exploited than Zcoin & Zcoin now has a valuation of $15 million despite that. Myself used Zoin to test the exploit actually because it wasn't fixed and if you check the block explorer, or rather the log files of the daemon you see lots of zero transactions (coinspends) before suddenly someone 'fixed' it by disabling the zeromints at all. The 'half dead' state was actually the best thing to happen for exploiters as you could test everything possible with very low difficulty and no one sniffing in the logs Okay, crypto is a gamble and you should never invest what you can't afford to lose, I wish you all the best with this coin I just wanted to point out (again, if you check back my posts in this thread) that there is at least some caution needed when playing with this coin. I will try to count how many coins were generated. |
|
|
|
Guys premine every time is good  |
|
|
|
|
You kidding, just launched two masternodes....
|
|
|
|
|
Show Posts
