|
We hit and passed block #21600!
|
|
|
|
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 ). Thank you for all your hard work Rob! and thank you for your hard work too Alex! I look forward to the developer team growing! I hope you guys get paid well from the IT budget for your hard work! |
|
|
|
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! I had to rename wallet.dat to wallet.old as well as the other instructions. Worked instantly. Uh oh, that doesnt sound right! Your wallet.dat I believe has your private key, so all your coins on your original wallet are now in that wallet.old file (If Im understanding wallet.dat files correctly) "wallet is a collection of private keys" https://en.bitcoin.it/wiki/Wallet |
|
|
|
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 |
|
|
|
|
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
|
|
|
|
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 |
|
|
|
|
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?
|
|
|
|
The pool hasn't been updated yet. Rob should be back in 45 minutes.
Hopefully Rob comes back soon and updates it On the Pool Website if you go to the "About" tab, it shows the version is still 1.0.6.7 |
|
|
|
With difficulty lower, how can I take a chance at solo mining a block?
What settings do I need in biblepay.conf?
Do you think I have a better shot than where it was on thursday?
Given all the updates solo mining may be easier given that a lot of people are not updated, but even 2 or so months ago it takes a LONG time to find a solo block with weaker PCs To solo mine just edit your biblepay.conf file and comment out the pool config settings by adding a # in front of them Like how long do you figure? End of the year long? Or a week? How do I get any results something got paid? And how does it know what address to pay? Getmininginfo show hashps 0 and poolmining false You can check your wallet amount to see how many coins got changed since last time you checked your wallet, also command is: getwalletinfo (not sure if your using windows or linux) Back 2 months ago, it would take a weak PC a whole month to get a solo block reward Its hard to say since we dont really know the network hash rate, you could mathematically calculate an estimate knowing your own HPS and the Network HPS, hopefully we get a correct network hash rate going forward, we shall see! |
|
|
|
With difficulty lower, how can I take a chance at solo mining a block?
What settings do I need in biblepay.conf?
Do you think I have a better shot than where it was on thursday?
Given all the updates solo mining may be easier given that a lot of people are not updated, but even 2 or so months ago it takes a LONG time to find a solo block with weaker PCs To solo mine just edit your biblepay.conf file and comment out the pool config settings by adding a # in front of them |
|
|
|
CLEAN UP GUIDE:Remove some folders and files, add Alex's node, and then reindex cd ~/.biblepaycore
rm blocks -R
rm chainstate -R
rm banlist.dat fee_estimates.dat governance.dat mncache.dat mnpayments.dat netfulfilled.dat peers.dat
vi biblepay.conf
addnode=node.biblepay-explorer.org #####COMMENT: press i to go into insert mode
:wq #####COMMENT press ESC to go into command mode
cd /home/YOURUSERNAME/biblepay/src
./biblepayd -daemon -reindex
|
|
|
|
|
Adding your node worked! I am on block 21561 now!
|
|
|
|
Here's the code to redo that cd ~/.biblepaycore
rm blocks -R
rm chainstate -R
rm banlist.dat fee_estimates.dat governance.dat mncache.dat mnpayments.dat netfulfilled.dat peers.dat
cd /home//YOURUSERNAME/biblepay/src
./biblepayd -daemon -reindex
However, after doing that both my Linux boxes are stuck on block 20000. Updated the backup block explorer and did the above and looks to be stuck on 21559, I will add node.biblepay-explorer.org to biblepay.conf and restart again cd ~/.biblepaycore
vi biblepay.conf
addnode=node.biblepay-explorer.org
:wq
|
|
|
|
Could we please have a few Prod users download the windows version 1067c now.
Lets see if we make it through the tithe block at 21350 that is giving us trouble...
Alex and I have been testing two scenarios on linux, but those are our Plan B solutions.
Please help us move the chain forward.
|
|
|
|
Please review:
Please contact us if you'd like to add BiblePay to masternodes.online
Listing advantages
- Accurate stats and comparison tool for investors
- Free Masternode monitoring for BBP MN holders
- Daily of exposure to 1000s of visitors on fastest growing masternodes site
- Page dedicated to your coin's detailed stats
- Daily Twitter broadcasts of top % gainers
- Coin included in popular telegram bot
Our Listing bounty ~.125 BTC - payable in BBP.
All my best!
Cryptosandwich
Communications for masternodes.online & NODEshare.in
If good, someone please enter a proposal.
Id advise getting listed on masternode.pro https://masternodes.pro/They show up as top google result when searching for keywords "masternode coins and "masternode list" I sent a submission form a while back, but never heard anything from them: https://goo.gl/forms/vz313NokCtnVD5Yk2Im also in their discord: https://discord.gg/ju5AbMxI believe the fee is $400 to get listed for 1 year haha I was going to say the exact same thing. I think .125 btc is pretty expensive but I'm not sure which one is the most popular/best.
From my google searching of keywords, I would DEFINITLEY advise masternode.pro, they are the top google result for the various "masternode" keyword variations, but I dont know their fees yet If anyone could submit another form to them, that would be awesome!, I just contacted them again in Discord, but I think they are asleep Good news, we will be listed on masternode.pro tonight! Jason from masternode.pro contacted me back in the Discord! "mnp_jason - Today at 10:23 AM @Togoshige i will get it listed tonight" I will post more details as I find out more |
|
|
|
|
Show Posts
