BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[ermintrude]

Everything all good once again with the fresh update.. Woohoo Thanks for all the hard work you guys have put in!

On a somewhat related note, coinsmarkets BBP-BTC market can't be accessed..

https://coinsmarkets.com/trade-BTC-BBP.htm

You end up at LTC-BTC instead.. Saw this mentioned the other day, and assumed it was just a temporary glitch..

[1714009288]

1714009288

[1714009288]

1714009288

[1714009288]

1714009288

[1714009288]

1714009288

[httpb]

Everything all good once again with the fresh update.. Woohoo Thanks for all the hard work you guys have put in!

On a somewhat related note, coinsmarkets BBP-BTC market can't be accessed..

https://coinsmarkets.com/trade-BTC-BBP.htm

You end up at LTC-BTC instead.. Saw this mentioned the other day, and assumed it was just a temporary glitch..

I have seen this with other coins too. I think this happens when the coin is not available due to maintenance, wallet being offline,...

[znffal]

I'm having trouble syncing the wallet for two days now.

It is showing 44 hours behind and with the message "No block source available" even though I have active connections.

The log is showing bunch of:
Misbehaving: SOME_IP:40000 (0 -> 1)
Misbehaving: SOME_OTHER_IP:40000 (1 -> 2)
....

Any suggestions on how to solve this?

Hi. What OS are you on?

Try reindexing

[znffal]

something is wrong with new update    crashing mining miners again ... before it was stable

I've been watching CPU and memory usage on my workstation.  Memory usage has kept climbing from 4.1GB to 10.1 GB.  I think that's what has been crashing the old Pentium 4 I was dinking around with.  

I haven't had any memory errors. 2 Machines closing the daemon for some reason and a couple with much lower hps than I would expect.
But in general, very nice indeed.

[jaapgvk]

I tried voting for some proposals, but when I click 'copy vote for budget' in the pool, I get 'Unable to locate Budget'.

[httpb]

I'm having trouble syncing the wallet for two days now.

It is showing 44 hours behind and with the message "No block source available" even though I have active connections.

The log is showing bunch of:
Misbehaving: SOME_IP:40000 (0 -> 1)
Misbehaving: SOME_OTHER_IP:40000 (1 -> 2)
....

Any suggestions on how to solve this?

Hi. What OS are you on?

Try reindexing

I'm using Win10. I just tried to reindex and again the sync stops at "2 days ago". I also tried to delete everything in "AppData/Roaming/BiblePayCore" except for wallet.dat and .conf file and that also didn't help.

The log is showing this error:

Code:

2017-12-19 11:41:34 InvalidChainFound: invalid block=a242f61a6c63193a10d29502387aac7d3f7aa3449579fff9c83a3b643235a52f  height=21560

If I type "getblockcount" into console, I get 21559.

So, the wallet gets stuck at block height of 21560.

[bible_pay]

Why are 6 pair of socks $54 at the store?
thats $9 for a pair of socks

The blanket is $63.90



https://i.imgur.com/pZmyHz8.png

If you don't like the prices please start your own store.

The pool is already giving everything away, and we answered your questions before, but you continue to troll this community. 

Please, find something to do with your time, come out of your basement, get some exercise.

[znffal]

I'm having trouble syncing the wallet for two days now.

It is showing 44 hours behind and with the message "No block source available" even though I have active connections.

The log is showing bunch of:
Misbehaving: SOME_IP:40000 (0 -> 1)
Misbehaving: SOME_OTHER_IP:40000 (1 -> 2)
....

Any suggestions on how to solve this?

Hi. What OS are you on?

Try reindexing

I'm using Win10. I just tried to reindex and again the sync stops at "2 days ago". I also tried to delete everything in "AppData/Roaming/BiblePayCore" except for wallet.dat and .conf file and that also didn't help.

The log is showing this error:

Code:

2017-12-19 11:41:34 InvalidChainFound: invalid block=a242f61a6c63193a10d29502387aac7d3f7aa3449579fff9c83a3b643235a52f  height=21560

If I type "getblockcount" into console, I get 21559.

So, the wallet gets stuck at block height of 21560.

Strange. What does

./biblepay-cli getinfo

tell you? What wallet version are you on?

[ferohers]

Had some issues as well. Strangely only a few computers got affacted.

(Always backup your wallet first)
Q - Some of my miners having an issue and do not appear on the pool. CPU on htop/top shows %100.

A - Stop biblepay first. ./biblepay-cli stop

Reindex for about 5-10mins.  ./biblepayd -rescan -reindex

Still not working?
Remove blocks, chainstate, database under .biblepaycore and restart Biblepay.

[Hardijs]

I'm having trouble syncing the wallet for two days now.

It is showing 44 hours behind and with the message "No block source available" even though I have active connections.

The log is showing bunch of:
Misbehaving: SOME_IP:40000 (0 -> 1)
Misbehaving: SOME_OTHER_IP:40000 (1 -> 2)
....

Any suggestions on how to solve this?

Hi. What OS are you on?

Try reindexing

I'm using Win10. I just tried to reindex and again the sync stops at "2 days ago". I also tried to delete everything in "AppData/Roaming/BiblePayCore" except for wallet.dat and .conf file and that also didn't help.

The log is showing this error:

Code:

2017-12-19 11:41:34 InvalidChainFound: invalid block=a242f61a6c63193a10d29502387aac7d3f7aa3449579fff9c83a3b643235a52f  height=21560

If I type "getblockcount" into console, I get 21559.

So, the wallet gets stuck at block height of 21560.

Disable the both original node address with # and add "node.bibplepay-explorer.org" in  your .conf file, delete again everything (except wallet.dat) and then reindex! If you pass 21559, delete the # marks in .conf file and restart application.

biblepay.conf:
#addnode=node.biblepay.org
#addnode=biblepay.inspect.network
addnode=node.bibplepay-explorer.org
.....

[Alex873434]

Had some issues as well. Strangely only a few computers got affacted.

(Always backup your wallet first)
Q - Some of my miners having an issue and do not appear on the pool. CPU on htop/top shows %100.

A - Stop biblepay first. Reindex for about 5-10mins. If not work please remove

./biblepay-cli stop
 ./biblepayd -rescan -reindex

Still not working?
Remove blocks, chainstate, database under .biblepaycore and restart Biblepay.

Also make sure to have the latest mandatory version. You should be using 1.0.6.9.

[ferohers]

Had some issues as well. Strangely only a few computers got affacted.

(Always backup your wallet first)
Q - Some of my miners having an issue and do not appear on the pool. CPU on htop/top shows %100.

A - Stop biblepay first. Reindex for about 5-10mins. If not work please remove

./biblepay-cli stop
 ./biblepayd -rescan -reindex

Still not working?
Remove blocks, chainstate, database under .biblepaycore and restart Biblepay.

Also make sure to have the latest mandatory version. You should be using 1.0.6.9.

Hi Alex,

15/3 of my vps servers got affected. 2 of them cured by reindexing. The other one I had to remove chainstate db etc. Then it just worked as usual.

[httpb]

I'm having trouble syncing the wallet for two days now.

It is showing 44 hours behind and with the message "No block source available" even though I have active connections.

The log is showing bunch of:
Misbehaving: SOME_IP:40000 (0 -> 1)
Misbehaving: SOME_OTHER_IP:40000 (1 -> 2)
....

Any suggestions on how to solve this?

Hi. What OS are you on?

Try reindexing

I'm using Win10. I just tried to reindex and again the sync stops at "2 days ago". I also tried to delete everything in "AppData/Roaming/BiblePayCore" except for wallet.dat and .conf file and that also didn't help.

The log is showing this error:

Code:

2017-12-19 11:41:34 InvalidChainFound: invalid block=a242f61a6c63193a10d29502387aac7d3f7aa3449579fff9c83a3b643235a52f  height=21560

If I type "getblockcount" into console, I get 21559.

So, the wallet gets stuck at block height of 21560.

Strange. What does

./biblepay-cli getinfo

tell you? What wallet version are you on?

If I type "getinfo" in console, I get the following:


Code:

{
  "version": 1000606,
  "protocolversion": 70710,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.6.6",
  "balance": 400.00000000,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 21559,
  "timeoffset": 16,
  "connections": 5,
  "proxy": "",
  "difficulty": 217.5915334033695,
  "testnet": false,
  "keypoololdest": 1511822547,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

[Alex873434]

@httpb

You're not using the right version. That's the issue. You should be using 1.0.6.9.

[znffal]

I'm having trouble syncing the wallet for two days now.

It is showing 44 hours behind and with the message "No block source available" even though I have active connections.

The log is showing bunch of:
Misbehaving: SOME_IP:40000 (0 -> 1)
Misbehaving: SOME_OTHER_IP:40000 (1 -> 2)
....

Any suggestions on how to solve this?

Hi. What OS are you on?

Try reindexing

I'm using Win10. I just tried to reindex and again the sync stops at "2 days ago". I also tried to delete everything in "AppData/Roaming/BiblePayCore" except for wallet.dat and .conf file and that also didn't help.

The log is showing this error:

Code:

2017-12-19 11:41:34 InvalidChainFound: invalid block=a242f61a6c63193a10d29502387aac7d3f7aa3449579fff9c83a3b643235a52f  height=21560

If I type "getblockcount" into console, I get 21559.

So, the wallet gets stuck at block height of 21560.

Strange. What does

./biblepay-cli getinfo

tell you? What wallet version are you on?

If I type "getinfo" in console, I get the following:


Code:

{
  "version": 1000606,
  "protocolversion": 70710,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.6.6",
  "balance": 400.00000000,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 21559,
  "timeoffset": 16,
  "connections": 5,
  "proxy": "",
  "difficulty": 217.5915334033695,
  "testnet": false,
  "keypoololdest": 1511822547,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

"wallet_fullversion": "1.0.6.6",

That line, you need to download the newest version, 1.0.6.9

[Alex873434]

Had some issues as well. Strangely only a few computers got affacted.

(Always backup your wallet first)
Q - Some of my miners having an issue and do not appear on the pool. CPU on htop/top shows %100.

A - Stop biblepay first. Reindex for about 5-10mins. If not work please remove

./biblepay-cli stop
 ./biblepayd -rescan -reindex

Still not working?
Remove blocks, chainstate, database under .biblepaycore and restart Biblepay.

Also make sure to have the latest mandatory version. You should be using 1.0.6.9.

Hi Alex,

15/3 of my vps servers got affected. 2 of them cured by reindexing. The other one I had to remove chainstate db etc. Then it just worked as usual.

Yeah depending on which version you're coming from, it -might- have been needed to delete the blockchain and redownload it.

Also guys, you shouldn't need to add node.biblepay-explorer.org anymore and it should work out of the box.

[bible_pay]

I tried voting for some proposals, but when I click 'copy vote for budget' in the pool, I get 'Unable to locate Budget'.

Just so you are aware, proposals are not the same as budgets.  The proposals become budgets after they reach a supermajority and have a triggerheight for a superblock.

But the problem was all Togos prposals went into the budget stage prematurely because we went live and then changed the rules on the system.

So another words you were trying to vote on a budget - not a proposal.  The budget didnt have its BudgetID yet because the system couldnt access it- hence the reason you got the clipcopy error on the budget row.

So to fix this I had to move the items back to the proposal state one time to get everything in sync.  So now you can vote on the proposals.

[znffal]

Hi Rob, happy with how everything is looking? No more updates necessary at this stage?

[httpb]

I deleted everything except wallet.dat and installed the newest version and it works now.

Thank you.

[bible_pay]

On the subject of proposals, I think we need to add a nice Red bar for one that is failing (IE where net Nos exist).  Ill work on that.