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? 
Topic: 🤖[ANN][BIS]Bismuth 2.0 - Beyond DeFi - page 155. (Read 156070 times)
Quote
Total tokens: 99,999,980 (1,099,99,978 including dev rewards)
Really?! Only 10% to be distributed via mining ?
Just a mistake i think... The separator of 1,099,99,978 is not in order...
Anyway dev must clarify this....
Also a total restart with network correction is neccessary...
Bismuth Main Network 3.13
hard fork at block 60000 to increase difficulty to log(1e20) and disallow backwards block submission
So that was? Somebody used a flaw to steal blocks?
60.000 blocks x 15 = 900.000 coins
hard fork at block 60000 to increase difficulty to log(1e20) and disallow backwards block submission
So that was? Somebody used a flaw to steal blocks?
60.000 blocks x 15 = 900.000 coins
yet it is supported lol
Bismuth Main Network 3.13
hard fork at block 60000 to increase difficulty to log(1e20) and disallow backwards block submission
So that was? Somebody used a flaw to steal blocks?
60.000 blocks x 15 = 900.000 coins
hard fork at block 60000 to increase difficulty to log(1e20) and disallow backwards block submission
So that was? Somebody used a flaw to steal blocks?
60.000 blocks x 15 = 900.000 coins
Quote
Total tokens: 99,999,980 (1,099,99,978 including dev rewards)
Really?! Only 10% to be distributed via mining ?
I updated my wallets and seems to download the blocks well
i think the dev is using this launch to correct bug , i should not be surprise that a relaunch will follow when all is corrected , for then waiting the 60k block to see what is doing the hardfork.
ITS OBVIOUSLY FUCKED
biff has not changed looks like the update created problems
6 machines equaling 32 cores at 2.8-3.2 ghz nothing
DEstroying all my droplets
biff has not changed looks like the update created problems
6 machines equaling 32 cores at 2.8-3.2 ghz nothing
DEstroying all my droplets
a cluster i dont think so , a gpu miner or using a flaw in the code mostly
What is strange is the only those 3-4 addresses get blocks , it must be a bug ...else I couldn't understand.
Anyway this centralization is not so good....
Anyway this centralization is not so good....
I can mine with my e5 using 3.13. However, it is very hard to mine a block.
a72ee0df3ea55616df36fc9d8bdad28310013b0d383216d44572aca2 has now over 2/5 blocks mined.
The owner must be have a cluster or sth I don't know, e.g., gpu-miner?
Trying to sync from scratch I get:
Code:
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.13
I am using 3.13
I have no problem with 3.13. Make sure you didn't have the old ledger.db file in static folder.
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.
What is strange is the only those 3-4 addresses get blocks , it must be a bug ...else I couldn't understand.
Anyway this centralization is not so good....
Anyway this centralization is not so good....
Trying to sync from scratch I get:
Code:
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.13
I am using 3.13
with 3.13 still the same...found blocks disappear
hardfork at 60k why not in 10 days , in this way more coin for the first miner ... he is going to have over 1 million coin alone for free lol
Trying to sync from scratch I get:
Code:
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.13
Maybe this is the premine the dev wrote about in the OP
Nope! I found that dev is hard working. If you are in the slack, you can find that the dev released the latest version 3.13. And there is a hard fork since 60k blocks. The sync is improved (maybe still not perfect yet).
yeah saw it thanks!
Yes , I agree. This coin needs to be restarted, and then I'll mine again..
Until then..powering down..
Until then..powering down..
Maybe this is the premine the dev wrote about in the OP
Nope! I found that dev is hard working. If you are in the slack, you can find that the dev released the latest version 3.13. And there is a hard fork since 60k blocks. The sync is improved (maybe still not perfect yet).
Jump to: