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

[HCLivess]

start node-->overview-->mining?

Yes, correct, overview is optional (GUI), but looks like miner has an issue now, it does not calculate block height correctly. Fixing in progress.

[1715660847]

1715660847

[1715660847]

1715660847

[a3860903]

Paused before recheck.
2016-06-28 17:29:57,526 worker(861) Client: Received data from 94.113.207.67:282
9
2016-06-28 17:29:57,628 worker(961) Client: Sending block height to compare: 135

2016-06-28 17:29:58,148 manager(72) 94.113.207.67:2829
2016-06-28 17:29:58,148 manager(72) 127.0.0.1:2829
2016-06-28 17:29:58,148 manager(81) Only 2 connections active, resetting the try
 list
2016-06-28 17:29:58,148 manager(84) Connection manager: Threads at 7/25
2016-06-28 17:29:58,150 manager(85) Tried: []
2016-06-28 17:29:58,150 manager(86) Current active pool: ['127.0.0.1:2829', '94.
113.207.67:2829']
2016-06-28 17:29:58,400 worker(970) Client: Node is at block height: 00000000135

2016-06-28 17:29:58,400 worker(985) Client: We have the same block height, hash
will be verified
2016-06-28 17:29:58,403 worker(994) Client: txhash to send: 1e6166faba6d9c9777b2
81626279fed7f68681460b95149a9936fde5
2016-06-28 17:29:58,813 worker(861) Client: Received data from 94.113.207.67:282
9
2016-06-28 17:29:58,813 worker(1162) Restoring local transactions from backup
2016-06-28 17:29:58,815 restore_backup(94) Node: Digesting backup
2016-06-28 17:29:58,815 digest_mempool(132) Node: Digesting mempool
2016-06-28 17:29:58,818 digest_mempool(275) Mempool empty
2016-06-28 17:29:58,819 restore_backup(125) Backup empty, sync finished
2016-06-28 17:29:58,819 worker(1164) Client: We seem to be at the latest block.
Paused before recheck.
2016-06-28 17:30:01,703 handle(427) Node: Received: sendsync___ from 127.0.0.1
2016-06-28 17:30:01,802 worker(861) Client: Received data from 127.0.0.1:2829
2016-06-28 17:30:01,904 handle(427) Node: Received: blockheight from 127.0.0.1
2016-06-28 17:30:01,904 worker(961) Client: Sending block height to compare: 135

2016-06-28 17:30:01,905 handle(612) Node: Received block height: 00000000135
2016-06-28 17:30:01,905 handle(632) Updating 127.0.0.1 in consensus
2016-06-28 17:30:01,907 handle(636) Consensus IP list:['127.0.0.1']
2016-06-28 17:30:01,907 handle(637) Consensus opinion list:[135]
2016-06-28 17:30:01,907 handle(641) Current active connections: 2
2016-06-28 17:30:01,907 handle(642) Current block consensus: 135 = 100.0%
2016-06-28 17:30:02,006 worker(970) Client: Node is at block height: 00000000135

2016-06-28 17:30:02,006 worker(985) Client: We have the same block height, hash
will be verified
2016-06-28 17:30:02,009 worker(994) Client: txhash to send: 1e6166faba6d9c9777b2
81626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:02,009 handle(673) Node: We have the same block height, hash wi
ll be verified
2016-06-28 17:30:02,009 handle(690) Node: Will seek the following block: 1e6166f
aba6d9c9777b281626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:02,012 handle(698) Node: Client is at block 135
2016-06-28 17:30:02,013 handle(703) Node: Client has the latest block
2016-06-28 17:30:02,108 worker(861) Client: Received data from 127.0.0.1:2829
2016-06-28 17:30:02,109 worker(1162) Restoring local transactions from backup
2016-06-28 17:30:02,109 restore_backup(94) Node: Digesting backup
2016-06-28 17:30:02,111 digest_mempool(132) Node: Digesting mempool
2016-06-28 17:30:02,112 digest_mempool(275) Mempool empty
2016-06-28 17:30:02,112 restore_backup(125) Backup empty, sync finished
2016-06-28 17:30:02,114 worker(1164) Client: We seem to be at the latest block.
Paused before recheck.
2016-06-28 17:30:08,151 manager(72) 94.113.207.67:2829
2016-06-28 17:30:08,151 manager(72) 127.0.0.1:2829
2016-06-28 17:30:08,151 manager(81) Only 2 connections active, resetting the try
 list
2016-06-28 17:30:08,151 manager(84) Connection manager: Threads at 7/25
2016-06-28 17:30:08,153 manager(85) Tried: []
2016-06-28 17:30:08,153 manager(86) Current active pool: ['127.0.0.1:2829', '94.
113.207.67:2829']
2016-06-28 17:30:09,229 worker(861) Client: Received data from 94.113.207.67:282
9
2016-06-28 17:30:09,331 worker(961) Client: Sending block height to compare: 135

2016-06-28 17:30:10,098 worker(970) Client: Node is at block height: 00000000135

2016-06-28 17:30:10,099 worker(985) Client: We have the same block height, hash
will be verified
2016-06-28 17:30:10,101 worker(994) Client: txhash to send: 1e6166faba6d9c9777b2
81626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:10,512 worker(861) Client: Received data from 94.113.207.67:282
9
2016-06-28 17:30:10,513 worker(1162) Restoring local transactions from backup
2016-06-28 17:30:10,513 restore_backup(94) Node: Digesting backup
2016-06-28 17:30:10,513 digest_mempool(132) Node: Digesting mempool
2016-06-28 17:30:10,516 digest_mempool(275) Mempool empty
2016-06-28 17:30:10,516 restore_backup(125) Backup empty, sync finished
2016-06-28 17:30:10,516 worker(1164) Client: We seem to be at the latest block.
Paused before recheck.
2016-06-28 17:30:12,115 handle(427) Node: Received: sendsync___ from 127.0.0.1
2016-06-28 17:30:12,214 worker(861) Client: Received data from 127.0.0.1:2829
2016-06-28 17:30:12,315 handle(427) Node: Received: blockheight from 127.0.0.1
2016-06-28 17:30:12,316 worker(961) Client: Sending block height to compare: 135

2016-06-28 17:30:12,316 handle(612) Node: Received block height: 00000000135
2016-06-28 17:30:12,318 handle(632) Updating 127.0.0.1 in consensus
2016-06-28 17:30:12,318 handle(636) Consensus IP list:['127.0.0.1']
2016-06-28 17:30:12,318 handle(637) Consensus opinion list:[135]
2016-06-28 17:30:12,319 handle(641) Current active connections: 2
2016-06-28 17:30:12,319 handle(642) Current block consensus: 135 = 100.0%
2016-06-28 17:30:12,417 worker(970) Client: Node is at block height: 00000000135

2016-06-28 17:30:12,417 worker(985) Client: We have the same block height, hash
will be verified
2016-06-28 17:30:12,420 worker(994) Client: txhash to send: 1e6166faba6d9c9777b2
81626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:12,421 handle(673) Node: We have the same block height, hash wi
ll be verified
2016-06-28 17:30:12,421 handle(690) Node: Will seek the following block: 1e6166f
aba6d9c9777b281626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:12,424 handle(698) Node: Client is at block 135
2016-06-28 17:30:12,424 handle(703) Node: Client has the latest block
2016-06-28 17:30:12,519 worker(861) Client: Received data from 127.0.0.1:2829
2016-06-28 17:30:12,520 worker(1162) Restoring local transactions from backup
2016-06-28 17:30:12,520 restore_backup(94) Node: Digesting backup
2016-06-28 17:30:12,522 digest_mempool(132) Node: Digesting mempool
2016-06-28 17:30:12,523 digest_mempool(275) Mempool empty
2016-06-28 17:30:12,523 restore_backup(125) Backup empty, sync finished
2016-06-28 17:30:12,525 worker(1164) Client: We seem to be at the latest block.
Paused before recheck.
2016-06-28 17:30:18,153 manager(72) 94.113.207.67:2829
2016-06-28 17:30:18,154 manager(72) 127.0.0.1:2829
2016-06-28 17:30:18,154 manager(81) Only 2 connections active, resetting the try
 list
2016-06-28 17:30:18,154 manager(84) Connection manager: Threads at 7/25
2016-06-28 17:30:18,154 manager(85) Tried: []
2016-06-28 17:30:18,154 manager(86) Current active pool: ['127.0.0.1:2829', '94.
113.207.67:2829']
2016-06-28 17:30:20,928 worker(861) Client: Received data from 94.113.207.67:282
9
2016-06-28 17:30:21,032 worker(961) Client: Sending block height to compare: 135

2016-06-28 17:30:21,796 worker(970) Client: Node is at block height: 00000000135

2016-06-28 17:30:21,798 worker(985) Client: We have the same block height, hash
will be verified
2016-06-28 17:30:21,799 worker(994) Client: txhash to send: 1e6166faba6d9c9777b2
81626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:22,220 worker(861) Client: Received data from 94.113.207.67:282
9
2016-06-28 17:30:22,220 worker(1162) Restoring local transactions from backup
2016-06-28 17:30:22,220 restore_backup(94) Node: Digesting backup
2016-06-28 17:30:22,221 digest_mempool(132) Node: Digesting mempool
2016-06-28 17:30:22,223 digest_mempool(275) Mempool empty
2016-06-28 17:30:22,224 restore_backup(125) Backup empty, sync finished
2016-06-28 17:30:22,224 worker(1164) Client: We seem to be at the latest block.
Paused before recheck.
2016-06-28 17:30:22,526 handle(427) Node: Received: sendsync___ from 127.0.0.1
2016-06-28 17:30:22,625 worker(861) Client: Received data from 127.0.0.1:2829
2016-06-28 17:30:22,726 handle(427) Node: Received: blockheight from 127.0.0.1
2016-06-28 17:30:22,729 worker(961) Client: Sending block height to compare: 135

2016-06-28 17:30:22,730 handle(612) Node: Received block height: 00000000135
2016-06-28 17:30:22,730 handle(632) Updating 127.0.0.1 in consensus
2016-06-28 17:30:22,730 handle(636) Consensus IP list:['127.0.0.1']
2016-06-28 17:30:22,730 handle(637) Consensus opinion list:[135]
2016-06-28 17:30:22,730 handle(641) Current active connections: 2
2016-06-28 17:30:22,730 handle(642) Current block consensus: 135 = 100.0%
2016-06-28 17:30:22,829 worker(970) Client: Node is at block height: 00000000135

2016-06-28 17:30:22,829 worker(985) Client: We have the same block height, hash
will be verified
2016-06-28 17:30:22,832 worker(994) Client: txhash to send: 1e6166faba6d9c9777b2
81626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:22,834 handle(673) Node: We have the same block height, hash wi
ll be verified
2016-06-28 17:30:22,834 handle(690) Node: Will seek the following block: 1e6166f
aba6d9c9777b281626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:22,835 handle(698) Node: Client is at block 135
2016-06-28 17:30:22,836 handle(703) Node: Client has the latest block
2016-06-28 17:30:22,933 worker(861) Client: Received data from 127.0.0.1:2829
2016-06-28 17:30:22,933 worker(1162) Restoring local transactions from backup
2016-06-28 17:30:22,934 restore_backup(94) Node: Digesting backup
2016-06-28 17:30:22,934 digest_mempool(132) Node: Digesting mempool
2016-06-28 17:30:22,937 digest_mempool(275) Mempool empty
2016-06-28 17:30:22,937 restore_backup(125) Backup empty, sync finished
2016-06-28 17:30:22,937 worker(1164) Client: We seem to be at the latest block.
Paused before recheck.
2016-06-28 17:30:28,157 manager(72) 94.113.207.67:2829
2016-06-28 17:30:28,157 manager(72) 127.0.0.1:2829
2016-06-28 17:30:28,157 manager(81) Only 2 connections active, resetting the try
 list
2016-06-28 17:30:28,157 manager(84) Connection manager: Threads at 7/25
2016-06-28 17:30:28,158 manager(85) Tried: []
2016-06-28 17:30:28,158 manager(86) Current active pool: ['127.0.0.1:2829', '94.
113.207.67:2829']
2016-06-28 17:30:32,637 worker(861) Client: Received data from 94.113.207.67:282
9
2016-06-28 17:30:32,740 worker(961) Client: Sending block height to compare: 135

2016-06-28 17:30:32,937 handle(427) Node: Received: sendsync___ from 127.0.0.1
2016-06-28 17:30:33,038 worker(861) Client: Received data from 127.0.0.1:2829
2016-06-28 17:30:33,138 handle(427) Node: Received: blockheight from 127.0.0.1
2016-06-28 17:30:33,140 worker(961) Client: Sending block height to compare: 135

2016-06-28 17:30:33,141 handle(612) Node: Received block height: 00000000135
2016-06-28 17:30:33,141 handle(632) Updating 127.0.0.1 in consensus
2016-06-28 17:30:33,141 handle(636) Consensus IP list:['127.0.0.1']
2016-06-28 17:30:33,141 handle(637) Consensus opinion list:[135]
2016-06-28 17:30:33,141 handle(641) Current active connections: 2
2016-06-28 17:30:33,142 handle(642) Current block consensus: 135 = 100.0%
2016-06-28 17:30:33,240 worker(970) Client: Node is at block height: 00000000135

2016-06-28 17:30:33,240 worker(985) Client: We have the same block height, hash
will be verified
2016-06-28 17:30:33,243 worker(994) Client: txhash to send: 1e6166faba6d9c9777b2
81626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:33,244 handle(673) Node: We have the same block height, hash wi
ll be verified
2016-06-28 17:30:33,244 handle(690) Node: Will seek the following block: 1e6166f
aba6d9c9777b281626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:33,246 handle(698) Node: Client is at block 135
2016-06-28 17:30:33,247 handle(703) Node: Client has the latest block
2016-06-28 17:30:33,345 worker(861) Client: Received data from 127.0.0.1:2829
2016-06-28 17:30:33,345 worker(1162) Restoring local transactions from backup
2016-06-28 17:30:33,345 restore_backup(94) Node: Digesting backup
2016-06-28 17:30:33,346 digest_mempool(132) Node: Digesting mempool
2016-06-28 17:30:33,348 digest_mempool(275) Mempool empty
2016-06-28 17:30:33,349 restore_backup(125) Backup empty, sync finished
2016-06-28 17:30:33,349 worker(1164) Client: We seem to be at the latest block.
Paused before recheck.
2016-06-28 17:30:33,507 worker(970) Client: Node is at block height: 00000000135

2016-06-28 17:30:33,507 worker(985) Client: We have the same block height, hash
will be verified
2016-06-28 17:30:33,510 worker(994) Client: txhash to send: 1e6166faba6d9c9777b2
81626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:33,930 worker(861) Client: Received data from 94.113.207.67:282
9
2016-06-28 17:30:33,930 worker(1162) Restoring local transactions from backup
2016-06-28 17:30:33,931 restore_backup(94) Node: Digesting backup
2016-06-28 17:30:33,933 digest_mempool(132) Node: Digesting mempool
2016-06-28 17:30:33,934 digest_mempool(275) Mempool empty
2016-06-28 17:30:33,934 restore_backup(125) Backup empty, sync finished
2016-06-28 17:30:33,936 worker(1164) Client: We seem to be at the latest block.
Paused before recheck.
2016-06-28 17:30:38,160 manager(72) 94.113.207.67:2829
2016-06-28 17:30:38,161 manager(72) 127.0.0.1:2829
2016-06-28 17:30:38,161 manager(81) Only 2 connections active, resetting the try
 list
2016-06-28 17:30:38,161 manager(84) Connection manager: Threads at 7/25
2016-06-28 17:30:38,161 manager(85) Tried: []
2016-06-28 17:30:38,161 manager(86) Current active pool: ['127.0.0.1:2829', '94.
113.207.67:2829']
2016-06-28 17:30:43,351 handle(427) Node: Received: sendsync___ from 127.0.0.1
2016-06-28 17:30:43,451 worker(861) Client: Received data from 127.0.0.1:2829
2016-06-28 17:30:43,552 handle(427) Node: Received: blockheight from 127.0.0.1
2016-06-28 17:30:43,555 worker(961) Client: Sending block height to compare: 135

2016-06-28 17:30:43,556 handle(612) Node: Received block height: 00000000135
2016-06-28 17:30:43,558 handle(632) Updating 127.0.0.1 in consensus
2016-06-28 17:30:43,559 handle(636) Consensus IP list:['127.0.0.1']
2016-06-28 17:30:43,559 handle(637) Consensus opinion list:[135]
2016-06-28 17:30:43,562 handle(641) Current active connections: 2
2016-06-28 17:30:43,562 handle(642) Current block consensus: 135 = 100.0%
2016-06-28 17:30:43,657 worker(970) Client: Node is at block height: 00000000135

2016-06-28 17:30:43,657 worker(985) Client: We have the same block height, hash
will be verified
2016-06-28 17:30:43,661 worker(994) Client: txhash to send: 1e6166faba6d9c9777b2
81626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:43,665 handle(673) Node: We have the same block height, hash wi
ll be verified
2016-06-28 17:30:43,667 handle(690) Node: Will seek the following block: 1e6166f
aba6d9c9777b281626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:43,670 handle(698) Node: Client is at block 135
2016-06-28 17:30:43,671 handle(703) Node: Client has the latest block
2016-06-28 17:30:43,763 worker(861) Client: Received data from 127.0.0.1:2829
2016-06-28 17:30:43,765 worker(1162) Restoring local transactions from backup
2016-06-28 17:30:43,766 restore_backup(94) Node: Digesting backup
2016-06-28 17:30:43,767 digest_mempool(132) Node: Digesting mempool
2016-06-28 17:30:43,769 digest_mempool(275) Mempool empty
2016-06-28 17:30:43,770 restore_backup(125) Backup empty, sync finished
2016-06-28 17:30:43,772 worker(1164) Client: We seem to be at the latest block.
Paused before recheck.
2016-06-28 17:30:44,355 worker(861) Client: Received data from 94.113.207.67:282
9
2016-06-28 17:30:44,459 worker(961) Client: Sending block height to compare: 135

2016-06-28 17:30:45,236 worker(970) Client: Node is at block height: 00000000135

2016-06-28 17:30:45,236 worker(985) Client: We have the same block height, hash
will be verified
2016-06-28 17:30:45,240 worker(994) Client: txhash to send: 1e6166faba6d9c9777b2
81626279fed7f68681460b95149a9936fde5
2016-06-28 17:30:45,663 worker(861) Client: Received data from 94.113.207.67:282
9
2016-06-28 17:30:45,664 worker(1162) Restoring local transactions from backup
2016-06-28 17:30:45,664 restore_backup(94) Node: Digesting backup
2016-06-28 17:30:45,667 digest_mempool(132) Node: Digesting mempool
2016-06-28 17:30:45,670 digest_mempool(275) Mempool empty
2016-06-28 17:30:45,671 restore_backup(125) Backup empty, sync finished
2016-06-28 17:30:45,671 worker(1164) Client: We seem to be at the latest block.
Paused before recheck.
2016-06-28 17:30:48,161 manager(72) 94.113.207.67:2829
2016-06-28 17:30:48,164 manager(72) 127.0.0.1:2829
2016-06-28 17:30:48,164 manager(81) Only 2 connections active, resetting the try
 list
2016-06-28 17:30:48,165 manager(84) Connection manager: Threads at 7/25
2016-06-28 17:30:48,167 manager(85) Tried: []
2016-06-28 17:30:48,167 manager(86) Current active pool: ['127.0.0.1:2829', '94.
113.207.67:2829']

[HCLivess]

Here is the new release, fixed miner.py and node.py, because they had wrong reward handling and mining was not really possible

outdated link

basic test passed

also, I just synced about 70 blocks from someone successfully

https://github.com/hclivess/Bismuth/commit/1ef9a6dc01c88afce9d97dd9a5e30d6a3866701e
https://github.com/hclivess/Bismuth/commit/f0883a78e11221c3c12c0477eea8c9313a39693b

[Charloz24]

Ok installed the newest release, and now see that you send me 10 000. Miner is started, but seem to not use cpu cycles, normal?

BTW Node is at block 136 as of right now.

[HCLivess]

The miner is not really very optimized for maximum performance, it is lightweight and paused if it sees that reward has been awarded for a segment

Reward should have gone to e31fd787e1c547996fb3059c4478a4364c8079df6e49a5616c870394, but it seems my node ignored it. Strange.

[Charloz24]

The miner is not really very optimized for maximum performance, it is lightweight and paused if it sees that reward has been awarded for a segment

Reward should have gone to e31fd787e1c547996fb3059c4478a4364c8079df6e49a5616c870394, but it seems my node ignored it. Strange.

That is my adress, andBTW in the wallet is there a way to do the paste function (for entering adress) I don't see it?

[HCLivess]

The miner is not really very optimized for maximum performance, it is lightweight and paused if it sees that reward has been awarded for a segment

Reward should have gone to e31fd787e1c547996fb3059c4478a4364c8079df6e49a5616c870394, but it seems my node ignored it. Strange.

That is my adress, andBTW in the wallet is there a way to do the paste function (for entering adress) I don't see it?

Either from GUI/Overview (CTRL+C) or from address.txt
Found the bug, client compares hash to local, not received address. Fixing

[Charloz24]

The miner is not really very optimized for maximum performance, it is lightweight and paused if it sees that reward has been awarded for a segment

Reward should have gone to e31fd787e1c547996fb3059c4478a4364c8079df6e49a5616c870394, but it seems my node ignored it. Strange.

That is my adress, andBTW in the wallet is there a way to do the paste function (for entering adress) I don't see it?

Either from GUI/Overview (CTRL+C) or from address.txt
Found the bug, client compares hash to local, not received address. Fixing

I try to send you back some, but how to paste your adress in recipient? CTRL+P doesn't work.

[HCLivess]

New release, mining finally working
https://github.com/hclivess/Bismuth/releases/tag/0.76



Also, let me warn you that you may not currently mine unless you have at least some coins, because the fee needs to be paid on every transaction.

There could be an exception added in the future

[HCLivess]

The miner is not really very optimized for maximum performance, it is lightweight and paused if it sees that reward has been awarded for a segment

Reward should have gone to e31fd787e1c547996fb3059c4478a4364c8079df6e49a5616c870394, but it seems my node ignored it. Strange.

That is my adress, andBTW in the wallet is there a way to do the paste function (for entering adress) I don't see it?

Either from GUI/Overview (CTRL+C) or from address.txt
Found the bug, client compares hash to local, not received address. Fixing

I try to send you back some, but how to paste your adress in recipient? CTRL+P doesn't work.

CTRL+V

[Charloz24]

DOH! Yeah it worked I sended you 100.

I'm on windows 7 and after installing, if I check gui, miner and node, they fail to start. I must open them manually and select run as an admin for them to work.

[Charloz24]

Ok I tried another 100 sended to you, and it turn out to send it 3 times 100.

[HCLivess]

Ok I tried another 100 sended to you, and it turn out to send it 3 times 100.

Thanks, looks like there is some duplication when syncing from multiple nodes. This might take a longer time to fix.
Strange that you need to select admin mode, they should automatically start in admin mode (I will double check on installer version)

[Charloz24]

Other thing, in the GUI I have to do a manual refresh to see new transactions.

[Charloz24]

Ok I tried another 100 sended to you, and it turn out to send it 3 times 100.

Thanks, looks like there is some duplication when syncing from multiple nodes. This might take a longer time to fix.

Tries again, but with 10 this time, it is still 3X 10

[Charloz24]

Last thing for this morning (must go to work now) in the GUI I see mined: 75, but it is not added to my balance.

[HCLivess]

Last thing for this morning (must go to work now) in the GUI I see mined: 75, but it is not added to my balance.

mining went goof, I fixed it here.
-link outdated-
Please update to prevent unintentional spending

I'll take a look if it's still not added to the balance -> tested, it's adding on genesis address. I'll test a random one.



Seems to be working

[Charloz24]

Last thing for this morning (must go to work now) in the GUI I see mined: 75, but it is not added to my balance.

mining went goof, I fixed it here.
https://github.com/hclivess/Bismuth/releases/tag/0.77
Please update to prevent unintentional spending

I'll take a look if it's still not added to the balance -> tested, it's adding on genesis address. I'll test a random one.



Seems to be working

Indeed, send you 15 and it worked

[HCLivess]

Somebody is now spamming the network with the public post-geneis address, the fees seem to be getting paid correctly (around 4 bismuth per 1 bismuth transaction ) But that person is running an old client I think

[adorid]

Somebody is now spamming the network with the public post-geneis address, the fees seem to be getting paid correctly (around 4 bismuth per 1 bismuth transaction ) But that person is running an old client I think

My bad  I started from topic begining and tested all old clients)) btw new client getting in node windows some errors... but anyway i testet sending to myself and mining... But mining hard to understand because text is too fast ))