Topic: 🤖[ANN][BIS]Bismuth 2.0 - Beyond DeFi - page 153. (Read 156070 times)

99,999,980 is by mining...premine(dev reward) is 10% or 9,999,980.. I think

Latest release
Bismuth Main Network 3.141
https://github.com/hclivess/Bismuth/releases

No, it shouldn't, though it is weird.
The easy way to do this is to download the latest release (let's say 3.141 now) and use it.
Copy your address, pub key and private key file to the new folder, and run node.py.

Is a mistake, will be 10% the correct number is (109,999,978)

is your node up to date? mine says last block found 150-170s ago..

WTB some as well, pm please

WTB pm offers

Is the beta balance cleared?
After upgrading to version 3.13, my wallet balance is 0,

Yes, I kept them
Privkey. Der
Privkey_encrypted. Der
Pubkey. Der
And copy it to the location of the new wallet
My wallet has not changed underground
But the balance is zero
0 c01056c761aa38d4106c8bc915cbc32fc67fa179113af3614475d8f

Here some of my error i get when i try mining.
1. node.py is slower with syncing so few blocks behind.
2. miner now only mines orphanes .
3. if u get 'good blocks' u will loose more and more peers until ure totally forked -> resync blockchain.
4. even while everything works, miner gets socket lost error :

2017-05-02 23:18:57,060 manager(653) Current connections: 6
2017-05-02 23:18:57,130 worker(1565) Outgoing: Block not found
2017-05-02 23:18:57,145 worker(1482) Outgoing: Node is at block height: 30106
2017-05-02 23:18:57,149 worker(1485) Outgoing: We have a higher, sending
2017-05-02 23:18:57,150 worker(1521) Outgoing: Will seek the following block: 39391d88ddca6db9807b5d28bff40bd18d3c3c6e8c0af0743f0c8c57
2017-05-02 23:18:57,150 consensus_add(579) Opinion of 173.208.172.138 hasn't changed
2017-05-02 23:18:57,150 consensus_add(589) Consensus IP list: ['69.197.167.10', '198.204.224.194', '107.150.46.42', '192.151.159.58', '173.208.192.114', '173.208.172.138']
2017-05-02 23:18:57,151 consensus_add(590) Consensus opinion list: [29638, 30169, 30169, 30168, 30104, 30106, 30106]
2017-05-02 23:18:57,151 consensus_add(596) Current outgoing connections: 6
2017-05-02 23:18:57,151 consensus_add(597) Current block consensus: 30169 = 28.5714285714%
2017-05-02 23:18:57,333 handle(1357) Incoming: Lost connection to 127.0.0.1
2017-05-02 23:18:57,335 handle(1358) Incoming: Socket timeout
2017-05-02 23:18:57,335 consensus_remove(611) Will remove 127.0.0.1 from consensus pool ['69.197.167.10', '198.204.224.194', '107.150.46.42', '192.151.159.58', '173.208.192.114', '173.208.172.138']
2017-05-02 23:18:57,336 consensus_remove(616) IP of 127.0.0.1 not present in the consensus pool
----------------------------------------
Exception happened during processing of request from ('127.0.0.1', 50522)
Traceback (most recent call last):
  File "/usr/lib/python2.7/SocketServer.py", line 596, in process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib/python2.7/SocketServer.py", line 331, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python2.7/SocketServer.py", line 652, in __init__
    self.handle()
  File "node.py", line 1106, in handle
    data = receive(self.request, 10)
  File "node.py", line 184, in receive
    raise RuntimeError("Socket timeout")
RuntimeError: Socket timeout
----------------------------------------
2017-05-02 23:18:57,476 worker(1565) Outgoing: Block not found
2017-05-02 23:18:58,016 worker(1476) Outgoing: Sending block height to compare: 30154
2017-05-02 23:18:58,264 worker(1476) Outgoing: Sending block height to compare: 30154
2017-05-02 23:18:58,671 digest_block(935) Digest: Appending transaction back to block with 0 transactions in it
2017-05-02 23:18:58,685 digest_block(944) Digest: Removed processed transaction from the mempool
2017-05-02 23:18:58,698 digest_block(975) Block 30155 valid and saved
2017-05-02 23:18:58,789 worker(1482) Outgoing: Node is at block height: 30106
2017-05-02 23:18:58,789 worker(1485) Outgoing: We have a higher, sending
2017-05-02 23:18:58,790 worker(1521) Outgoing: Will seek the following block: 39391d88ddca6db9807b5d28bff40bd18d3c3c6e8c0af0743f0c8c57
2017-05-02 23:18:58,790 consensus_add(579) Opinion of 173.208.172.138 hasn't changed
2017-05-02 23:18:58,790 consensus_add(589) Consensus IP list: ['69.197.167.10', '198.204.224.194', '107.150.46.42', '192.151.159.58', '173.208.192.114', '173.208.172.138']
2017-05-02 23:18:58,791 consensus_add(590) Consensus opinion list: [29638, 30169, 30169, 30168, 30104, 30106, 30106]
2017-05-02 23:18:58,791 consensus_add(596) Current outgoing connections: 6
2017-05-02 23:18:58,791 consensus_add(597) Current block consensus: 30169 = 28.5714285714%
2017-05-02 23:18:59,175 worker(1565) Outgoing: Block not found
2017-05-02 23:18:59,183 digest_block(746) Valid signature
2017-05-02 23:18:59,618 worker(1482) Outgoing: Node is at block height: 29638
2017-05-02 23:18:59,619 worker(1485) Outgoing: We have a higher, sending
2017-05-02 23:19:00,008 worker(1521) Outgoing: Will seek the following block: ba02ffc0bd86d941e4124311a95d3b620fd3b5a71ee92994e66392ea
2017-05-02 23:19:00,008 consensus_add(579) Opinion of 69.197.167.10 hasn't changed
2017-05-02 23:19:00,009 consensus_add(589) Consensus IP list: ['69.197.167.10', '198.204.224.194', '107.150.46.42', '192.151.159.58', '173.208.192.114', '173.208.172.138']
2017-05-02 23:19:00,009 consensus_add(590) Consensus opinion list: [29638, 30169, 30169, 30168, 30104, 30106, 30106]
2017-05-02 23:19:00,011 consensus_add(596) Current outgoing connections: 6
1 Comment

I can make only one conclusion.
I tried ti mine some blocks with 120 Cores cluster, no luck.
And very interesting. Address that spams with blocks autoupdates his wallet. Or someone updates it's immediately after new version released. So i think it's a dev mining via GPU

As you can see.. I thought so, but no.

▣  Total tokens: 99,999,980 (1,099,99,978 including dev rewards)

90% dev reward, hahaha

Hello!
 
If you need russian thread, contact me please.
 
Best regards.

Dev is on slack actually pass by and ask him ocminer

shouldn't it be recreated when it gets deleted ? I'm trying to resync as my node keeps forking

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..

i am but i can offer little help im more of a web developer right now. looks like its sayin it cant connect to the db because the transaction table dosent exist

Is anybody actually reading this ?

well im def on a fork BH 18742

mad coins tho lol

Possible..