Topic: [TESTNET]Bismuth - New Language, Interpretation Engines, DAPPs - page 15. (Read 49730 times)

１×７　Sent

I was able to mining today.
Thanks for the advice.

jump on to slack just now if you can

Block Height 112
Where do you see in the GUI what you send me?

you should get a tx from me too :-) and if you dont mind me asking what block are you on just now?

Already running. I got ~600 and in block 107
Thanks

try the miner you should get some :-)

Seems working great 
If you want to send some Bismuth coin to test it here my address
ae248382f457989761949e2beffedb9603e06ef7bd377c992e8a64b6
Thanks

you need to have node running when you are mining (or change mining ip in config file)

Next version will include an automatic message telling you to switch node on instead of shutting down. Also, you will be able to configure mining threads to go after that 100% CPU usage

I will try installing again.

thats you mining buddy :-) but my screen has not disappeared, hmm,  did you run the node and miner as administrator? what dose it say in your miner.log?

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

Is this correct?
The screen disappears in about 1 minute

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

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.

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

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

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
 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 (60) Mining will start once there are transactions in the mempool




Thanks

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

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

Here is the new release, as promised:

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