[TESTNET]Bismuth - New Language, Interpretation Engines, DAPPs

[kamiyama]

mining

module (53)mining will start once there are transaction in the mempool
↑
What should I do?

[1713270990]

1713270990

[1713270990]

1713270990

[1713270990]

1713270990

[1713270990]

1713270990

[ALATAY2K16]

mining

module (53)mining will start once there are transaction in the mempool
↑
What should I do?

I've sent some tx,  it should of started your miner

[kamiyama]

https://i.imgur.com/jb0AJil.jpg

I do not know why  can not mininｇ.

[HCLivess]

Hello, we have identified a bug related to long strings during synchronization of blocks and mempool. The bug has been finally confirmed today not to be related to switches/semafors. The fix is under development now, patience is advised.

Ledger synchronization may malfunction on long blocks

Here is the prototype code:

Code:

import time

mempool_txs = "1a2sdadsasd, asdlkajwldkjaslkdjalksdjalksd, asdlkhjahakjsd, akshdkajshdkjahdjkahdkjahdskjsahkjash222dkjahds"

def split2len(s, n):
    def _f(s, n):
        while s:
            yield s[:n]
            s = s[n:]
    return list(_f(s, n))

mempool_split = split2len(mempool_txs, 50)
mempool_count = len(mempool_split)  # how many segments of 500 will be sent
while len(str(mempool_count)) != 10:
    mempool_count = "0" + str(mempool_count)  # number must be 10 long
#s.sendall(str(mempool_count))  # send how many segments will be transferred
print (str(mempool_count))

mempool_index = -1
while int(mempool_count) > 0:
    mempool_count = int(mempool_count) - 1
    mempool_index = mempool_index + 1

    segment_length = len(mempool_split[mempool_index])
    while len(str(segment_length)) != 10:
        segment_length = "0" + str(segment_length)
    #s.sendall(segment_length)  # send how much they should receive, usually 500, except the last segment
    print(segment_length)
    time.sleep(0.1)
    #s.sendall(mempool_split[mempool_count])  # send segment
    print (mempool_split[mempool_index])
    time.sleep(0.1)

Preliminary tests are succesful:

Code:

2016-11-30 13:07:40,461 worker(1316) Client: Segment to dispatch: ...
2016-11-30 13:07:40,562 worker(1314) Client: Segment length: 0000000004
2016-11-30 13:07:40,562 handle(756) Node: Segment length: 0000000004
2016-11-30 13:07:40,663 worker(1316) Client: Segment to dispatch: =')]
2016-11-30 13:07:40,663 handle(758) Node: Received segment: =')]
2016-11-30 13:07:40,663 handle(761) Node: Combined segments: .....
....
2016-11-30 13:07:40,671 merge_mempool(116) That transaction is already in our mempool
2016-11-30 13:07:40,671 merge_mempool(116) That transaction is already in our mempool

The whole mempool sync is now segmented, tested and works. Proceeding to ledger segmentation.

The whole ledger sync is now segmented, tested and works. Preparing to release.

[Sam123]

Hello, we have identified a bug related to long strings during synchronization of blocks and mempool. The bug has been finally confirmed today not to be related to switches/semafors. The fix is under development now, patience is advised.

Ledger synchronization may malfunction on long blocks

Here is the prototype code:

Code:

import time

mempool_txs = "1a2sdadsasd, asdlkajwldkjaslkdjalksdjalksd, asdlkhjahakjsd, akshdkajshdkjahdjkahdkjahdskjsahkjash222dkjahds"

def split2len(s, n):
    def _f(s, n):
        while s:
            yield s[:n]
            s = s[n:]
    return list(_f(s, n))

mempool_split = split2len(mempool_txs, 50)
mempool_count = len(mempool_split)  # how many segments of 500 will be sent
while len(str(mempool_count)) != 10:
    mempool_count = "0" + str(mempool_count)  # number must be 10 long
#s.sendall(str(mempool_count))  # send how many segments will be transferred
print (str(mempool_count))

mempool_index = -1
while int(mempool_count) > 0:
    mempool_count = int(mempool_count) - 1
    mempool_index = mempool_index + 1

    segment_length = len(mempool_split[mempool_index])
    while len(str(segment_length)) != 10:
        segment_length = "0" + str(segment_length)
    #s.sendall(segment_length)  # send how much they should receive, usually 500, except the last segment
    print(segment_length)
    time.sleep(0.1)
    #s.sendall(mempool_split[mempool_count])  # send segment
    print (mempool_split[mempool_index])
    time.sleep(0.1)

Preliminary tests are succesful:

Code:

2016-11-30 13:07:40,461 worker(1316) Client: Segment to dispatch: ...
2016-11-30 13:07:40,562 worker(1314) Client: Segment length: 0000000004
2016-11-30 13:07:40,562 handle(756) Node: Segment length: 0000000004
2016-11-30 13:07:40,663 worker(1316) Client: Segment to dispatch: =')]
2016-11-30 13:07:40,663 handle(758) Node: Received segment: =')]
2016-11-30 13:07:40,663 handle(761) Node: Combined segments: .....
....
2016-11-30 13:07:40,671 merge_mempool(116) That transaction is already in our mempool
2016-11-30 13:07:40,671 merge_mempool(116) That transaction is already in our mempool

The whole mempool sync is now segmented, tested and works. Proceeding to ledger segmentation.

The whole ledger sync is now segmented, tested and works. Preparing to release.

Great, will give it a trial. I was unable to mine previously

[HCLivess]

New version is out
Incompatible with old versions, testnet ver. 4
https://github.com/hclivess/Bismuth/releases/tag/1.11

[Sam123]

New version is out
Incompatible with old versions, testnet ver. 4
https://github.com/hclivess/Bismuth/releases/tag/1.11

Running the latest version now

[Sam123]

New version is out
Incompatible with old versions, testnet ver. 4
https://github.com/hclivess/Bismuth/releases/tag/1.11

The algorithm SHA224 is efficient on GPU?
How about this project: Is it better mining with CPU or GPU ?

[HCLivess]

New version is out
Incompatible with old versions, testnet ver. 4
https://github.com/hclivess/Bismuth/releases/tag/1.11

The algorithm SHA224 is efficient on GPU?
How about this project: Is it better mining with CPU or GPU ?

Hi, there is no GPU miner and I don't know how to make one so it's only CPU
Did you guys sync blocks? Currently at block 18. Some switches are needed to optimize sync, but it should do so without any errors now.

[Sam123]

Hi,

I'm getting some errors: What does it mean?

Thanks

---------------------------------------
Exception happened during processing of request from ('127.0.0.1', 56844)
Traceback (most recent call last):
  File "SocketServer.py", line 599, in process_request_thread
  File "SocketServer.py", line 334, in finish_request
  File "SocketServer.py", line 655, in __init__
  File "node.py", line 725, in handle
error: [Errno 10054] An existing connection was forcibly closed by the remote host
----------------------------------------
2016-11-30 21:23:06,943 handle(728) Node: Received:  from 127.0.0.1
2016-11-30 21:23:06,944 handle(1089) Node: Communication error
2016-11-30 21:23:06,944 handle(1094) Node: Lost connection
2016-11-30 21:23:06,944 handle(1095) exceptions must be old-style classes or derived from BaseException, not NoneType
2016-11-30 21:23:06,946 consensus_remove(380) Client 127.0.0.1 not present in the consensus pool
----------------------------------------
Exception happened during processing of request from2016-11-30 21:23:06,948 worker(1116) Client: Connected to 94.113.207.67 2829
 ('127.0.0.2016-11-30 21:23:06,951 worker(1120) Current active pool: ['94.113.207.67:2829']
1', 56846)
Traceback (most recent call last):
  File "SocketServer.py", line 599, in process_request_thread
  File "SocketServer.py", line 334, in finish_request
  File "SocketServer.py", line 655, in __init__
  File "node.py", line 1090, in handle
TypeError: exceptions must be old-style classes or derived from BaseException, not NoneType
----------------------------------------
2016-11-30 21:23:07,418 worker(1134) Client: Node protocol version matches our client
2016-11-30 21:23:07,634 worker(1144) Client: Received peers______ from 94.113.207.67:2829
2016-11-30 21:23:07,878 worker(1153) [('127.0.0.1', '2829'), ('94.113.207.67', '2829'), ('90.216.208.18', '2829')]
2016-11-30 21:23:07,878 worker(1154) 3
2016-11-30 21:23:07,884 worker(1164) [('127.0.0.1', '2829'), ('94.113.207.67', '2829')]
2016-11-30 21:23:07,884 worker(1182) Client: ('127.0.0.1', '2829') is not a new peer
2016-11-30 21:23:07,884 worker(1182) Client: ('94.113.207.67', '2829') is not a new peer
2016-11-30 21:23:07,884 worker(1169) Client: ('90.216.208.18', '2829') is a new peer, saving if connectible
2016-11-30 21:23:07,888 worker(1179) Not connectible
2016-11-30 21:23:16,759 manager(399) 127.0.0.1:2829
2016-11-30 21:23:17,437 manager(404) ---Starting a client thread <_MainThread(MainThread, started 7016)>---
2016-11-30 21:23:17,437 manager(399) 94.113.207.67:2829
2016-11-30 21:23:17,443 worker(1116) Client: Connected to 127.0.0.1 2829
2016-11-30 21:23:17,443 manager(409) Only 1 connections active, resetting the try list
2016-11-30 21:23:17,443 worker(1120) Current active pool: ['94.113.207.67:2829', '127.0.0.1:2829']
2016-11-30 21:23:17,443 manager(412) Connection manager: Threads at 3/25
2016-11-30 21:23:17,447 handle(728) Node: Received: version____ from 127.0.0.1
2016-11-30 21:23:17,453 manager(413) Tried: []
2016-11-30 21:23:17,453 manager(414) Current active pool: ['94.113.207.67:2829', '127.0.0.1:2829']
2016-11-30 21:23:17,457 manager(415) Current connections: 2
2016-11-30 21:23:17,552 handle(738) Node: Protocol version matched: testnet4___
2016-11-30 21:23:17,654 worker(1134) Client: Node protocol version matches our client
2016-11-30 21:23:17,753 handle(728) Node: Received: helloserver from 127.0.0.1
2016-11-30 21:23:17,755 handle(829) Node: ('127.0.0.1', '2829')

[HCLivess]

Hi,

I'm getting some errors: What does it mean?

Thanks

Hi, "An existing connection was forcibly closed by the remote host" from 127.0.0.1 is an error produced when miner disconnects after submitting a block to the node. Nothing to worry about, it's just that the miner doesn't say goodbye so node isn't sure what happened.

Also, exciting news, version 1.12 will be much faster than current 1.11, because I removed some redundant code that was necessary for "proof of transaction". After successfully separating mempool mechanics from the ledger,w e can go much faster now. I'll release today.

Also, there will be a rollback to block 9 due to a double signature bugfix, shutting down my node until then.

Also, I started working on hyperblock technology for pruning and blockchain-less currency:

https://github.com/hclivess/Bismuth/issues/8

Code:

import sqlite3




conn = sqlite3.connect('ledger.db')
conn.text_factory = str
c = conn.cursor()

hype = sqlite3.connect('hyperblocks.db')
hype.text_factory = str
h = hype.cursor()
try:
    h.execute(
        "CREATE TABLE transactions (block_height INTEGER, timestamp, address, recipient, amount, signature, public_key, block_hash, fee, reward, confirmations, openfield)")
except:
    pass

end_balance = 0
addresses = []
for row in c.execute('SELECT * FROM transactions ORDER BY block_height'):
    db_address = row[2]
    db_recipient = row[3]
    addresses.append (db_address)
    addresses.append (db_recipient)

unique_addressess = set(addresses)


for x in set(unique_addressess):
    if x != "genesis":
        c.execute("SELECT sum(amount) FROM transactions WHERE recipient = '" + x + "'")
        credit = c.fetchone()[0]
        if credit == None:
            credit = 0

        c.execute("SELECT sum(amount) FROM transactions WHERE address = '" + x + "'")
        debit = c.fetchone()[0]
        if debit == None:
            debit = 0

        c.execute("SELECT sum(fee) FROM transactions WHERE address = '" + x + "'")
        fees = c.fetchone()[0]
        if fees == None:
            fees = 0

        c.execute("SELECT sum(reward) FROM transactions WHERE address = '" + x + "'")
        rewards = c.fetchone()[0]
        if rewards == None:
            rewards = 0

        end_balance = credit - debit - fees + rewards
        print x
        print end_balance

        if end_balance > 0:
            h.execute("INSERT INTO transactions VALUES (?,?,?,?,?,?,?,?,?,?,?,?)", ("0","past chain",x,str(float(end_balance)),"0","0","0","0","0","0","0","0"))

hype.commit()
hype.close()

[HCLivess]

Here is the new release, as promised:

https://github.com/hclivess/Bismuth/releases/tag/1.12

[Sam123]

Here is the new release, as promised:

https://github.com/hclivess/Bismuth/releases/tag/1.12

Hi,

I just downloaded the latest version.
1) How long does it take to mine one block?
2) I'm getting errors:
      a) Not connectible

2016-12-01 09:35:30,926
 worker(1166) Client: ('90.216.208.18', '2829') is a new
peer, saving if connectible
2016-12-01 09:35:30,927 worker(1176) Not connectible

       b) I'm getting Connection to 94.113.207.67:2829 terminate
 due to timed out

Thanks










2016-12-01 09:33:30,765 handle(959) Node: Will seek the following block: ef4f05
d0f9039161025860af5bf4ec1f155f690f881836f693f774e
2016-12-01 09:33:30,767 handle(970) Node: Client is at block 1
2016-12-01 09:33:30,769 handle(975) Node: Client has the latest block
2016-12-01 09:33:30,861 consensus_add(343) Opinion of 127.0.0.1 hasn't changed
2016-12-01 09:33:30,862 consensus_add(357) Consensus IP list:['127.0.0.1']
2016-12-01 09:33:30,862 consensus_add(358) Consensus opinion list:[1]
2016-12-01 09:33:30,864 consensus_add(359) Consensus hash list:['none']
2016-12-01 09:33:30,864 consensus_add(364) Current active connections: 2
2016-12-01 09:33:30,865 consensus_add(365) Current block consensus: 1 = 100.0%
2016-12-01 09:33:30,865 worker(1141) Client: Received nonewblocks from 127.0.0.
:2829
2016-12-01 09:33:30,967 worker(1433) Client: Extracted from the mempool: []
2016-12-01 09:33:30,970 handle(735) Node: Received: mempool____ from 127.0.0.1
2016-12-01 09:33:30,970 handle(754) Node: Number of incoming segments: 00000000
1
2016-12-01 09:33:31,069 handle(760) Node: Segment length: 0000000002
2016-12-01 09:33:31,069 worker(1453) Client: Segment length: 0000000002
2016-12-01 09:33:31,173 worker(1455) Client: Segment to dispatch: []
2016-12-01 09:33:31,174 handle(762) Node: Received segment: []
2016-12-01 09:33:31,176 handle(765) Node: Combined segments: []
2016-12-01 09:33:31,178 handle(792) Node: Extracted from the mempool: []
2016-12-01 09:33:31,273 worker(1469) Client: Number of incoming segments: 00000
0001
2016-12-01 09:33:31,279 handle(812) Node: Segment length: 0000000002
2016-12-01 09:33:31,279 worker(1475) Client: Segment length: 0000000002
2016-12-01 09:33:31,381 handle(815) Node: Segment to dispatch: []
2016-12-01 09:33:31,381 worker(1477) Client: Received segment: []
2016-12-01 09:33:31,384 worker(1480) Client: Combined segments: []
2016-12-01 09:33:31,384 worker(1492) Client: We seem to be at the latest block.
Paused before recheck
2016-12-01 09:33:33,242 manager(399) 127.0.0.1:2829
2016-12-01 09:33:33,243 manager(399) 94.113.207.67:2829
2016-12-01 09:33:33,244 manager(409) Only 2 connections active, resetting the t
y list
2016-12-01 09:33:33,246 manager(412) Connection manager: Threads at 6/25
2016-12-01 09:33:33,247 manager(413) Tried: []
2016-12-01 09:33:33,249 manager(414) Current active pool: ['127.0.0.1:2829', '9
.113.207.67:2829']
2016-12-01 09:33:33,250 manager(415) Current connections: 2
2016-12-01 09:33:34,726 worker(1503) Will remove 94.113.207.67:2829 from active
pool ['127.0.0.1:2829', '94.113.207.67:2829']
2016-12-01 09:33:34,729 consensus_remove(380) Client 94.113.207.67 not present
n the consensus pool
2016-12-01 09:33:34,730 worker(1513) Connection to 94.113.207.67:2829 terminate
 due to timed out
2016-12-01 09:33:34,733 worker(1514) ---thread <Thread(Thread-8, started 84828)
 ended---

[ALATAY2K16]

Here is the new release, as promised:

https://github.com/hclivess/Bismuth/releases/tag/1.12

Hi,

I just downloaded the latest version.
1) How long does it take to mine one block?
2) I'm getting errors:
      a) Not connectible

2016-12-01 09:35:30,926
 worker(1166) Client: ('90.216.208.18', '2829') is a new
peer, saving if connectible
2016-12-01 09:35:30,927 worker(1176) Not connectible

       b) I'm getting Connection to 94.113.207.67:2829 terminate
 due to timed out

Thanks










2016-12-01 09:33:30,765 handle(959) Node: Will seek the following block: ef4f05
d0f9039161025860af5bf4ec1f155f690f881836f693f774e
2016-12-01 09:33:30,767 handle(970) Node: Client is at block 1
2016-12-01 09:33:30,769 handle(975) Node: Client has the latest block
2016-12-01 09:33:30,861 consensus_add(343) Opinion of 127.0.0.1 hasn't changed
2016-12-01 09:33:30,862 consensus_add(357) Consensus IP list:['127.0.0.1']
2016-12-01 09:33:30,862 consensus_add(358) Consensus opinion list:[1]
2016-12-01 09:33:30,864 consensus_add(359) Consensus hash list:['none']
2016-12-01 09:33:30,864 consensus_add(364) Current active connections: 2
2016-12-01 09:33:30,865 consensus_add(365) Current block consensus: 1 = 100.0%
2016-12-01 09:33:30,865 worker(1141) Client: Received nonewblocks from 127.0.0.
:2829
2016-12-01 09:33:30,967 worker(1433) Client: Extracted from the mempool: []
2016-12-01 09:33:30,970 handle(735) Node: Received: mempool____ from 127.0.0.1
2016-12-01 09:33:30,970 handle(754) Node: Number of incoming segments: 00000000
1
2016-12-01 09:33:31,069 handle(760) Node: Segment length: 0000000002
2016-12-01 09:33:31,069 worker(1453) Client: Segment length: 0000000002
2016-12-01 09:33:31,173 worker(1455) Client: Segment to dispatch: []
2016-12-01 09:33:31,174 handle(762) Node: Received segment: []
2016-12-01 09:33:31,176 handle(765) Node: Combined segments: []
2016-12-01 09:33:31,178 handle(792) Node: Extracted from the mempool: []
2016-12-01 09:33:31,273 worker(1469) Client: Number of incoming segments: 00000
0001
2016-12-01 09:33:31,279 handle(812) Node: Segment length: 0000000002
2016-12-01 09:33:31,279 worker(1475) Client: Segment length: 0000000002
2016-12-01 09:33:31,381 handle(815) Node: Segment to dispatch: []
2016-12-01 09:33:31,381 worker(1477) Client: Received segment: []
2016-12-01 09:33:31,384 worker(1480) Client: Combined segments: []
2016-12-01 09:33:31,384 worker(1492) Client: We seem to be at the latest block.
Paused before recheck
2016-12-01 09:33:33,242 manager(399) 127.0.0.1:2829
2016-12-01 09:33:33,243 manager(399) 94.113.207.67:2829
2016-12-01 09:33:33,244 manager(409) Only 2 connections active, resetting the t
y list
2016-12-01 09:33:33,246 manager(412) Connection manager: Threads at 6/25
2016-12-01 09:33:33,247 manager(413) Tried: []
2016-12-01 09:33:33,249 manager(414) Current active pool: ['127.0.0.1:2829', '9
.113.207.67:2829']
2016-12-01 09:33:33,250 manager(415) Current connections: 2
2016-12-01 09:33:34,726 worker(1503) Will remove 94.113.207.67:2829 from active
pool ['127.0.0.1:2829', '94.113.207.67:2829']
2016-12-01 09:33:34,729 consensus_remove(380) Client 94.113.207.67 not present
n the consensus pool
2016-12-01 09:33:34,730 worker(1513) Connection to 94.113.207.67:2829 terminate
 due to timed out
2016-12-01 09:33:34,733 worker(1514) ---thread <Thread(Thread-8, started 84828)
 ended---

hey buddy :-), i've got node and miner running, not a problem. are you still struggling to connect? 

[Sam123]

Here is the new release, as promised:

https://github.com/hclivess/Bismuth/releases/tag/1.12

Hi,

I just downloaded the latest version.
1) How long does it take to mine one block?
2) I'm getting errors:
      a) Not connectible

2016-12-01 09:35:30,926
 worker(1166) Client: ('90.216.208.18', '2829') is a new
peer, saving if connectible
2016-12-01 09:35:30,927 worker(1176) Not connectible

       b) I'm getting Connection to 94.113.207.67:2829 terminate
 due to timed out

Thanks

hey buddy :-), i've got node and miner running, not a problem. are you still struggling to connect?  

Yes sir.

1) How long does it take to mine one block?
2) Are you getting Connection to 94.113.207.67:2829 terminate
 due to timed out or  Not connectible

2016-12-01 10:04:39,063 worker(1513) Connection to 94.113.207.67:2829 terminated
 due to [Errno 10061] No connection could be made because the target machine act
ively refused it
2016-12-01 10:04:39,065 worker(1514) ---thread <Thread(Thread-7, started 88368)>
 ended---
2016-12-01 10:04:39,141 consensus_add(343) Opinion of 127.0.0.1 hasn't changed




The miner is stuck at
2016-12-01 09:32:25,826 <module>(60) Mining will start once there are transactions in the mempool




Thanks

[HCLivess]

Here is the new release, as promised:

https://github.com/hclivess/Bismuth/releases/tag/1.13
https://github.com/hclivess/Bismuth/releases/tag/1.12

Hi,

I just downloaded the latest version.
1) How long does it take to mine one block?
2) I'm getting errors:
      a) Not connectible

2016-12-01 09:35:30,926
 worker(1166) Client: ('90.216.208.18', '2829') is a new
peer, saving if connectible
2016-12-01 09:35:30,927 worker(1176) Not connectible

       b) I'm getting Connection to 94.113.207.67:2829 terminate
 due to timed out

Thanks










2016-12-01 09:33:30,765 handle(959) Node: Will seek the following block: ef4f05
d0f9039161025860af5bf4ec1f155f690f881836f693f774e
2016-12-01 09:33:30,767 handle(970) Node: Client is at block 1
2016-12-01 09:33:30,769 handle(975) Node: Client has the latest block
2016-12-01 09:33:30,861 consensus_add(343) Opinion of 127.0.0.1 hasn't changed
2016-12-01 09:33:30,862 consensus_add(357) Consensus IP list:['127.0.0.1']
2016-12-01 09:33:30,862 consensus_add(358) Consensus opinion list:[1]
2016-12-01 09:33:30,864 consensus_add(359) Consensus hash list:['none']
2016-12-01 09:33:30,864 consensus_add(364) Current active connections: 2
2016-12-01 09:33:30,865 consensus_add(365) Current block consensus: 1 = 100.0%
2016-12-01 09:33:30,865 worker(1141) Client: Received nonewblocks from 127.0.0.
:2829
2016-12-01 09:33:30,967 worker(1433) Client: Extracted from the mempool: []
2016-12-01 09:33:30,970 handle(735) Node: Received: mempool____ from 127.0.0.1
2016-12-01 09:33:30,970 handle(754) Node: Number of incoming segments: 00000000
1
2016-12-01 09:33:31,069 handle(760) Node: Segment length: 0000000002
2016-12-01 09:33:31,069 worker(1453) Client: Segment length: 0000000002
2016-12-01 09:33:31,173 worker(1455) Client: Segment to dispatch: []
2016-12-01 09:33:31,174 handle(762) Node: Received segment: []
2016-12-01 09:33:31,176 handle(765) Node: Combined segments: []
2016-12-01 09:33:31,178 handle(792) Node: Extracted from the mempool: []
2016-12-01 09:33:31,273 worker(1469) Client: Number of incoming segments: 00000
0001
2016-12-01 09:33:31,279 handle(812) Node: Segment length: 0000000002
2016-12-01 09:33:31,279 worker(1475) Client: Segment length: 0000000002
2016-12-01 09:33:31,381 handle(815) Node: Segment to dispatch: []
2016-12-01 09:33:31,381 worker(1477) Client: Received segment: []
2016-12-01 09:33:31,384 worker(1480) Client: Combined segments: []
2016-12-01 09:33:31,384 worker(1492) Client: We seem to be at the latest block.
Paused before recheck
2016-12-01 09:33:33,242 manager(399) 127.0.0.1:2829
2016-12-01 09:33:33,243 manager(399) 94.113.207.67:2829
2016-12-01 09:33:33,244 manager(409) Only 2 connections active, resetting the t
y list
2016-12-01 09:33:33,246 manager(412) Connection manager: Threads at 6/25
2016-12-01 09:33:33,247 manager(413) Tried: []
2016-12-01 09:33:33,249 manager(414) Current active pool: ['127.0.0.1:2829', '9
.113.207.67:2829']
2016-12-01 09:33:33,250 manager(415) Current connections: 2
2016-12-01 09:33:34,726 worker(1503) Will remove 94.113.207.67:2829 from active
pool ['127.0.0.1:2829', '94.113.207.67:2829']
2016-12-01 09:33:34,729 consensus_remove(380) Client 94.113.207.67 not present
n the consensus pool
2016-12-01 09:33:34,730 worker(1513) Connection to 94.113.207.67:2829 terminate
 due to timed out
2016-12-01 09:33:34,733 worker(1514) ---thread <Thread(Thread-8, started 84828)
 ended---

Hi, I needed to fix more bugs https://github.com/hclivess/Bismuth/releases/tag/1.13 we need to confirm that this is working first still
Mining should take about 1500-5000 cycles

[Sam123]

Downloaded the latest: https://github.com/hclivess/Bismuth/releases/tag/1.13

See below. Why?
Thanks


2016-12-01 10:55:08,734 manager(412) Connection manager: Threads at 5/25
2016-12-01 10:55:08,736 manager(413) Tried: []
2016-12-01 10:55:08,736 manager(414) Current active pool: []
2016-12-01 10:55:08,737 manager(415) Current connections: 0
2016-12-01 10:55:08,928 handle(1103) Node: Lost connection
2016-12-01 10:55:08,930 handle(1104) [Errno 10054] An existing connection was forcibly closed by the remote host
2016-12-01 10:55:08,931 consensus_remove(380) Client 127.0.0.1 not present in the consensus pool
----------------------------------------
Exception happened during processing of request from ('127.0.0.1', 58801)
Traceback (most recent call last):
  File "SocketServer.py", line 599, in process_request_thread
  File "SocketServer.py", line 334, in finish_request
  File "SocketServer.py", line 655, in __init__
  File "node.py", line 744, in handle
error: [Errno 10054] An existing connection was forcibly closed by the remote host
----------------------------------------
2016-12-01 10:55:08,940 handle(747) Node: Received:  from 127.0.0.1

[HCLivess]

Hi, I've taken down the node, there's a problem with passive nodes syncing from active nodes (so far mempool). I will send a patch as soon as I resolve this.

[HCLivess]

https://github.com/hclivess/Bismuth/releases/tag/1.21

I spent the night hunting those bugs Sam and Alatay have reported. Please upgrade to 1.21
I have not been able to reproduce these errors with this new version.

Everyone can mine now all the time
keep your nodes running while doing so

[kamiyama]

http://imgur.com/a/1uPuK

Is this correct?
The screen disappears in about 1 minute