Pages:
Author

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

hero member
Activity: 966
Merit: 501
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.
legendary
Activity: 2114
Merit: 1090
=== NODE IS OK! ==
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 Wink
legendary
Activity: 2114
Merit: 1090
=== NODE IS OK! ==
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
hero member
Activity: 966
Merit: 501
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.
legendary
Activity: 2114
Merit: 1090
=== NODE IS OK! ==
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
hero member
Activity: 966
Merit: 501
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?
legendary
Activity: 2114
Merit: 1090
=== NODE IS OK! ==
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.
hero member
Activity: 966
Merit: 501
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.
legendary
Activity: 2114
Merit: 1090
=== NODE IS OK! ==
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 Wink

Quote
member
Activity: 87
Merit: 10
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']
legendary
Activity: 2114
Merit: 1090
=== NODE IS OK! ==
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.
member
Activity: 87
Merit: 10
start node-->overview-->mining?
member
Activity: 87
Merit: 10
member
Activity: 87
Merit: 10
2016-06-28 17:08:17,815 (53) Mempool: Reward status: Mined (61)
2016-06-28 17:08:27,815 (53) Mempool: Reward status: Mined (61)
2016-06-28 17:08:37,816 (53) Mempool: Reward status: Mined (61)
2016-06-28 17:08:47,818 (53) Mempool: Reward status: Mined (61)
2016-06-28 17:08:57,818 (53) Mempool: Reward status: Mined (61)
2016-06-28 17:09:07,819 (53) Mempool: Reward status: Mined (61)
2016-06-28 17:09:17,819 (53) Mempool: Reward status: Mined (61)
2016-06-28 17:09:27,819 (53) Mempool: Reward status: Mined (61)
2016-06-28 17:09:37,819 (53) Mempool: Reward status: Mined (61)
2016-06-28 17:09:47,821 (53) Mempool: Reward status: Mined (61)
2016-06-28 17:09:57,822 (53) Mempool: Reward status: Mined (61)

??
legendary
Activity: 2114
Merit: 1090
=== NODE IS OK! ==
as of right now =)

2016-06-28 01:32:38,391 handle(698) Node: Client is at block 131
2016-06-28 01:32:38,391 handle(703) Node: Client has the latest block

Awesome, I confirm this to be the latest block. Also, mining should be possible now again since we are in a new block segment, so feel free to try it out Wink

current fee: 0.03 Bismuth after my spam
everyone is now fully synced
newbie
Activity: 29
Merit: 0
as of right now =)

2016-06-28 01:32:38,391 handle(698) Node: Client is at block 131
2016-06-28 01:32:38,391 handle(703) Node: Client has the latest block
legendary
Activity: 2114
Merit: 1090
=== NODE IS OK! ==
Stuck at block 74?

Hi, can you please send me information from your node.log?
It looks like you are at 74 and one guy is at 61. 5 other guys are fully synced. Are you using the latest version? There were some issues with the old blockchain. Also it might be an issue with sync mechanism I was not able to notice on a lower scale, because you should basically roll back to the last known block of the longest chain, looks like modifications are needed. Unless you have doubled transactions in the blockchain (2 with the same signature, and possibly same block number)
legendary
Activity: 2114
Merit: 1090
=== NODE IS OK! ==
Please remove all references to me and Vcash as we do not endorse, support or have any affiliation with this project. Cool

References removed

Quote
Copyright infringement, Intellectual Property Theft, Illegal use of the Vcash trademark to promote the ICO scam (Bismuth). This matter has been handed off to Vcash attorneys.

You seriously banned me on your forum for endorsing your project, while calling mine a scam and an ICO? After I spent months on development and ideas while you secretly forked Peercoin? Why you must be sucha nut.. And you threatened me with a lawsuit? I even stopped posting there. I used to feel sad, guilty and inproper on your forum, now I just feel that you might be doing amphetamine derivates a little too much.
There goes my investing in VCASH I guess and the promotion and our Twitter love affair
sr. member
Activity: 596
Merit: 251
Please remove all references to me and Vcash as we do not endorse, support or have any affiliation with this project. Cool
hero member
Activity: 966
Merit: 501
Stuck at block 74?
Pages:
Jump to: