2 issues
1: When I open my BBP wallet it gives me a runtime error unless I leave the biblepay.conf file blank. But that's useless since I need to input the lines provided by these instructions. - https://www.reddit.com/r/BiblePay/comments/6umlqq/how_to_mine_biblepay_on_windows/
2: My other windows system is unable to sync with the network stating "no block source available"
Any thoughts?
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 788. (Read 243376 times)
December 17, 2017, 07:23:33 PM
December 17, 2017, 07:19:58 PM
BiblePay - 1.0.6.8c
Miners Of Men
** This is the windows release. Please upgrade to 1068 if you have not. Linux upgraded 4 hours ago **
http://biblepay.org/ ---> Downloads section
This worked for me and now my Windows Wallet is up to date and on block 21579
Yes, thanks this worked. So nsummy will have to update the minersofmen pool, too for continued mining and withdrawals?
Yes. His about page is frozen so maybe he is doing it now. Or maybe his biblepayd is crashed.
December 17, 2017, 07:18:06 PM
Alright, some good news: Our tithe blocks have officially ended. 21580 went to the pool.
The pool is now paying for tithe blocks also.
The pool is now paying for tithe blocks also.
December 17, 2017, 07:10:38 PM
BiblePay - 1.0.6.8c
Mandatory Upgrade
- Disable tithe blocks at #21565
- Ensure Sanctuary payments can go live at #21600
- Increment mandatory protocol version to 70911
- Superblocks start at block #30001
- Proposals and Budgets went live at block #21551
** This is the windows release. Please upgrade to 1068 if you have not. Linux upgraded 4 hours ago **
http://biblepay.org/ ---> Downloads section
Windows Cleanup:
- File Explorer: %appdata%/BiblePayCore
- Delete blocks and chainstate folders, delete banlist, fee_estimates, governance, mncache, netfulfiled and peers
- Add this line to biblepay.conf: addnode=node.biblepay-explorer.org
- In Wallet do Tools >> Wallet Repair >> Rebuild index
This worked for me and now my Windows Wallet is up to date and on block 21579
Yes, thanks this worked. So nsummy will have to update the minersofmen pool, too for continued mining and withdrawals?
December 17, 2017, 07:05:50 PM
BiblePay - 1.0.6.8c
Mandatory Upgrade
- Disable tithe blocks at #21565
- Ensure Sanctuary payments can go live at #21600
- Increment mandatory protocol version to 70911
- Superblocks start at block #30001
- Proposals and Budgets went live at block #21551
** This is the windows release. Please upgrade to 1068 if you have not. Linux upgraded 4 hours ago **
http://biblepay.org/ ---> Downloads section
Windows Cleanup:
- File Explorer: %appdata%/BiblePayCore
- Delete blocks and chainstate folders, delete banlist, fee_estimates, governance, mncache, netfulfiled and peers
- Add this line to biblepay.conf: addnode=node.biblepay-explorer.org
- In Wallet do Tools >> Wallet Repair >> Rebuild index
This worked for me and now my Windows Wallet is up to date and on block 21579
Once again: thank you for your help Togo (and of course also Rob, Alex and everyone else)!
My windows wallet seems in sync and the masternodelist seems to be populating again. Let's hope everything goes well this time
Yes and thank you for all your help also.
Lets hope we fly past 21600 without a problem as I would love to tackle more IT problems in one day in production, it would be great to pull a triple (long hour workday) today in IT, it excites me, and Alex said he stayed up all night last night, he likes it also, so we have a great team forming.
The good news is we should know within 2 hrs, making this an exciting day for IT.
That is our last big hurdle, as budgets and superblocks were tested in a way that will not be a threat to forking the chain (as masternode payments will be).
Of course we do need to check these masternode payments after block 21600! Lets get ready to do that also.
I remember 616 was mentioning this morning the payments were doubled and tripled, but looking at that issue mid-day, those were not actually masternode payments. To see those, grab the block, grab the transaction in the coinbase and type 'getrawtransaction coinbasetxid 1', then analyze the vout[1] (vout[0] is the miner who mined the block, vout[1] is the sanctuary payment). Ensure the sanc payment is correct amount, (it should be nBlockAmount - nBlockDistribution Deductions, * .40 ). Then ensure the payee is in the payee vector in order ( we can look at the masternode list ).
December 17, 2017, 07:04:44 PM
We are now listed on MasterNode.Pros!: https://masternodes.pro/
The fee is $400 in Bitcoin for 1 year of listing, I will make a proposal for it
The fee is $400 in Bitcoin for 1 year of listing, I will make a proposal for it
December 17, 2017, 07:00:39 PM
I have a transaction that sent at early version which is stucked at unconfirmed status. Any solution?
I'm in the same boat with a transaction cashing out from the pool.... Any help would be appreciated.
I credited it, please withdraw again.
You are awesome. Thanks for the quick response and all the hard work this weekend. Keep up the great work!
December 17, 2017, 06:58:49 PM
I have a transaction that sent at early version which is stucked at unconfirmed status. Any solution?
I'm in the same boat with a transaction cashing out from the pool.... Any help would be appreciated.
I credited it, please withdraw again.
December 17, 2017, 06:58:33 PM
Any sanctuary (masternode) owners will need to start them again: "masternode start-alias SANCTUARYNAME"
There was a protocol version upgrade again from 70710 to 70711
There was a protocol version upgrade again from 70710 to 70711
December 17, 2017, 06:58:04 PM
I have a transaction that sent at early version which is stucked at unconfirmed status. Any solution?
I saw there are 2 buttons at Wallet repair - "Recover transactions 1" and "Recover transactions 2", is it the solution? If yes, which button should I use?
Thanks!
If that does not work, restart with -zapwallettxes
and it will clear it.
December 17, 2017, 06:57:46 PM
I've followed all the above instructions, addnode etc. ver 1.0.6.8 linux. Still stuck on block 21559 (9 hours ago). Any ideas?
I know it might sound repetitive but did you try the instructions provided by Togo (deleting the files, etc)? Are sure you're running 1.0.6.8?
Thanks for replying
Absolutely. I'm gonna do it again too.
If no-one else is stuck I'll delete the whole shebang and start again. But it would be better to know why.I have the same problem...... put the remarks "#" before both original node adress in biblepay.conf, leave only "node.biblepay-explorer.org" ....delete folders and files as before!!!
After you pass the 21559 block - delete both remarks!
December 17, 2017, 06:51:24 PM
I have a transaction that sent at early version which is stucked at unconfirmed status. Any solution?
I'm in the same boat with a transaction cashing out from the pool.... Any help would be appreciated.
December 17, 2017, 06:50:57 PM
BiblePay - 1.0.6.8c
Mandatory Upgrade
- Disable tithe blocks at #21565
- Ensure Sanctuary payments can go live at #21600
- Increment mandatory protocol version to 70911
- Superblocks start at block #30001
- Proposals and Budgets went live at block #21551
** This is the windows release. Please upgrade to 1068 if you have not. Linux upgraded 4 hours ago **
http://biblepay.org/ ---> Downloads section
Windows Cleanup:
- File Explorer: %appdata%/BiblePayCore
- Delete blocks and chainstate folders, delete banlist, fee_estimates, governance, mncache, netfulfiled and peers
- Add this line to biblepay.conf: addnode=node.biblepay-explorer.org
- In Wallet do Tools >> Wallet Repair >> Rebuild index
This worked for me and now my Windows Wallet is up to date and on block 21579
Once again: thank you for your help Togo (and of course also Rob, Alex and everyone else)!
My windows wallet seems in sync and the masternodelist seems to be populating again. Let's hope everything goes well this time
December 17, 2017, 06:46:22 PM
I have a transaction that sent at early version which is stucked at unconfirmed status. Any solution?
I saw there are 2 buttons at Wallet repair - "Recover transactions 1" and "Recover transactions 2", is it the solution? If yes, which button should I use?
Thanks!
December 17, 2017, 06:43:14 PM
BiblePay - 1.0.6.8c
Mandatory Upgrade
- Disable tithe blocks at #21565
- Ensure Sanctuary payments can go live at #21600
- Increment mandatory protocol version to 70911
- Superblocks start at block #30001
- Proposals and Budgets went live at block #21551
** This is the windows release. Please upgrade to 1068 if you have not. Linux upgraded 4 hours ago **
http://biblepay.org/ ---> Downloads section
Windows Cleanup:
- File Explorer: %appdata%/BiblePayCore
- Delete blocks and chainstate folders, delete banlist, fee_estimates, governance, mncache, netfulfiled and peers
- Add this line to biblepay.conf: addnode=node.biblepay-explorer.org
- In Wallet do Tools >> Wallet Repair >> Rebuild index
This worked for me and now my Windows Wallet is up to date and on block 21579
December 17, 2017, 06:36:54 PM
I'm attempting to rebroadcast the last 6 withdrawals from the pool, they are all unconfirmed. This way we will be able to trace the txids.
It would be helpful if you included the txid in the email.
Only shows on first click. After that does not show it again - says coins are withdrawn already.
Suggest: The amount xyz was sent on tx 123. etc
December 17, 2017, 06:32:03 PM
1.0.6.8 working now on 3 windows PCs.
December 17, 2017, 06:31:28 PM
I'm attempting to rebroadcast the last 6 withdrawals from the pool, they are all unconfirmed. This way we will be able to trace the txids.
EDIT:
I credited the withdraws that failed to go out. Please withdraw again.
EDIT:
I credited the withdraws that failed to go out. Please withdraw again.
December 17, 2017, 06:23:35 PM
new version on windows ok, thanks.
December 17, 2017, 06:22:25 PM
I see v1.0.6.7 for Windows 32 bit exe after install,
I did a CTRL + SHIFT + R on the webpage to make sure I have latest version of the webpage (not sure it matters haha)
maybe the download link is taking time to propagate/update to different regions?
I did a CTRL + SHIFT + R on the webpage to make sure I have latest version of the webpage (not sure it matters haha)
maybe the download link is taking time to propagate/update to different regions?
I see there was a problem with the deploy, par for the course today! Bad IT day, Bad.
Please grab it now!
Full deploy successful this time.
Jump to: