Pure python faster than stock miner.
https://pastebin.com/Ta8Ny2D0
Let me know if it finds blocks. Well tested with an older version of Bismuth, but there might be syncing issues with the latest version. Please test with different Bismuth versions.
Topic: 🤖[ANN][BIS]Bismuth 2.0 - Beyond DeFi - page 137. (Read 156212 times)
Seems situation is normalized again.
At least all three of my nodes are synchronized, the blocks are coming up correctly and I can mine again.
But it's very bad that more than 50% of the network is in the hands of one miner and it can generate 5 blocks in less than a minute.
At least all three of my nodes are synchronized, the blocks are coming up correctly and I can mine again.
But it's very bad that more than 50% of the network is in the hands of one miner and it can generate 5 blocks in less than a minute.
It's not just bad, it's terrible
. Makes the whole of point mining this coin worthless.It is the pool, i guess. You have to use the fast miner and this miner is very fast, compared to the original one, developed by the dev.
Seems situation is normalized again.
At least all three of my nodes are synchronized, the blocks are coming up correctly and I can mine again.
But it's very bad that more than 50% of the network is in the hands of one miner and it can generate 5 blocks in less than a minute.
At least all three of my nodes are synchronized, the blocks are coming up correctly and I can mine again.
But it's very bad that more than 50% of the network is in the hands of one miner and it can generate 5 blocks in less than a minute.
It's not just bad, it's terrible
. Makes the whole of point mining this coin worthless.yes,very agree,it make whole of bismuth worthless.
I have told the dev about this, dev needs to solve this terrible problem.
Seems situation is normalized again.
At least all three of my nodes are synchronized, the blocks are coming up correctly and I can mine again.
But it's very bad that more than 50% of the network is in the hands of one miner and it can generate 5 blocks in less than a minute.
At least all three of my nodes are synchronized, the blocks are coming up correctly and I can mine again.
But it's very bad that more than 50% of the network is in the hands of one miner and it can generate 5 blocks in less than a minute.
It's not just bad, it's terrible
. Makes the whole of point mining this coin worthless.
Seems situation is normalized again.
At least all three of my nodes are synchronized, the blocks are coming up correctly and I can mine again.
But it's very bad that more than 50% of the network is in the hands of one miner and it can generate 5 blocks in less than a minute.
At least all three of my nodes are synchronized, the blocks are coming up correctly and I can mine again.
But it's very bad that more than 50% of the network is in the hands of one miner and it can generate 5 blocks in less than a minute.
My blockchain says it's 937 minutes behind after updating to latest version, and can't mine 
Are there problems in the network? Is forked or what? Hard to sync.
P.S. One address mined 6 blocks per 30 seconds.
Block explorers show different heights:
104006 and 103688
One node has 104014 and timestamp is actual - another 105003.
P.S. I received by 1-2 blocks before from other nodes. But now I received 7-10.
I think address "147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133" can mine long chain of blocks without publish every block and then only publish to the network all chain from 7-10 blocks.
Cause this is most power miner his chain is more difficult and accepted by the network. Blocks from other miners - not.
In any case I mined before, now I can't on the same difficulty cause I don't receive actual blocks on time.
New record: 5 blocks per 10 seconds:
P.S. One address mined 6 blocks per 30 seconds.
Code:
104005 2017/05/20,16:58:44 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104004 2017/05/20,16:58:32 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104003 2017/05/20,16:58:28 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104002 2017/05/20,16:58:16 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104001 2017/05/20,16:58:14 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104000 2017/05/20,16:58:10 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104004 2017/05/20,16:58:32 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104003 2017/05/20,16:58:28 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104002 2017/05/20,16:58:16 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104001 2017/05/20,16:58:14 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104000 2017/05/20,16:58:10 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
Block explorers show different heights:
104006 and 103688
One node has 104014 and timestamp is actual - another 105003.
Code:
2017-05-20 21:15:43,940 digest_block(944) Block 104010 valid and saved from 80.233.232.24
...
2017-05-20 21:17:13,719 manager(608) Connection manager: Consensus: 104010 = 100.0%
...
2017-05-20 21:17:28,265 digest_block(944) Block 104026 valid and saved from 204.12.195.202
...
2017-05-20 21:18:33,739 manager(608) Connection manager: Consensus: 104010 = 50.0%
2017-05-20 21:18:43,316 handle(1297) Outgoing: Received a block from miner
2017-05-20 21:18:43,316 handle(1314) Outgoing: Processing block from miner
2017-05-20 21:18:45,020 digest_block(944) Block 104027 valid and saved from 127.0.0.1
2017-05-20 21:18:47,114 blocknf(513) Node 94.23.102.99 didn't find block 104027, rolled back
2017-05-20 21:18:53,739 manager(606) Connection manager: Current connections: 14
2017-05-20 21:18:53,739 manager(608) Connection manager: Consensus: 105008 = 25.0%
2017-05-20 21:18:53,880 handle(1297) Outgoing: Received a block from miner
2017-05-20 21:18:53,880 handle(1318) Outgoing: Mined block was orphaned because node was not synced, we are at block 104026, should be at least 105005
...
2017-05-20 21:17:13,719 manager(608) Connection manager: Consensus: 104010 = 100.0%
...
2017-05-20 21:17:28,265 digest_block(944) Block 104026 valid and saved from 204.12.195.202
...
2017-05-20 21:18:33,739 manager(608) Connection manager: Consensus: 104010 = 50.0%
2017-05-20 21:18:43,316 handle(1297) Outgoing: Received a block from miner
2017-05-20 21:18:43,316 handle(1314) Outgoing: Processing block from miner
2017-05-20 21:18:45,020 digest_block(944) Block 104027 valid and saved from 127.0.0.1
2017-05-20 21:18:47,114 blocknf(513) Node 94.23.102.99 didn't find block 104027, rolled back
2017-05-20 21:18:53,739 manager(606) Connection manager: Current connections: 14
2017-05-20 21:18:53,739 manager(608) Connection manager: Consensus: 105008 = 25.0%
2017-05-20 21:18:53,880 handle(1297) Outgoing: Received a block from miner
2017-05-20 21:18:53,880 handle(1318) Outgoing: Mined block was orphaned because node was not synced, we are at block 104026, should be at least 105005
P.S. I received by 1-2 blocks before from other nodes. But now I received 7-10.
I think address "147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133" can mine long chain of blocks without publish every block and then only publish to the network all chain from 7-10 blocks.
Cause this is most power miner his chain is more difficult and accepted by the network. Blocks from other miners - not.
In any case I mined before, now I can't on the same difficulty cause I don't receive actual blocks on time.
New record: 5 blocks per 10 seconds:
Code:
104044 2017/05/20,17:40:18 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104043 2017/05/20,17:40:16 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104042 2017/05/20,17:40:14 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104041 2017/05/20,17:40:12 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104040 2017/05/20,17:40:08 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104043 2017/05/20,17:40:16 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104042 2017/05/20,17:40:14 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104041 2017/05/20,17:40:12 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
104040 2017/05/20,17:40:08 147c45831fa760c4ea9c1dd0908f7e75bde3f50d980268ef47614133
What parameters do I need to change to mine in the pool? because now it only works solo
Hi, guys. How many blocks per day can I mine with multi core CPU?
Are there anybody mining on a one CPU?
What is your cycles/seconds rate?
Are there anybody mining on a one CPU?
What is your cycles/seconds rate?
How do I use pool?
?
?
Can this be mined with a GPU? Or there is only CPU miner? How much hash power do you need to mine on your own?
where is miner?
How to join in the pool?I have not found any register link
./
How to join in the pool?I have not found any register link
Still without a public pool or an exchange?It is a month after the op lanch.
See the slack channel for the pool. Quite a few people seem to use it at the moment, as the hashrate of the pool address c09df7ed17aecc09145e054aa8f261ea2b56c4660720b5721cce1bfa is 90% of the network or so.
Thanks, but it seems there isn't a windows miner yet... no?
not yet...I'm also waiting for one.
check the slack channel. all the infos are posted there
See the slack channel for the pool. Quite a few people seem to use it at the moment, as the hashrate of the pool address c09df7ed17aecc09145e054aa8f261ea2b56c4660720b5721cce1bfa is 90% of the network or so.
Thanks, but it seems there isn't a windows miner yet... no?
See the slack channel for the pool. Quite a few people seem to use it at the moment, as the hashrate of the pool address c09df7ed17aecc09145e054aa8f261ea2b56c4660720b5721cce1bfa is 90% of the network or so.
Jump to: