Can a version number be placed on the windows executable or maybe just under the button to download it? That way we know when an upgrade will be needed without having to install it to see if a version changes.
Implemented. Now when our config manager does a release the version will automatically be sent here:
http://biblepay.org/#wallets-section
PS, the reason you cant see the release from the properties of the windows downloaded file is a limitation in the gitian build. We are working on a solution to that. EDIT: The version is the "1.0.6.9" you see to the right of BiblePay Wallets. |
|
|
|
Rob,
I am out of PMs today so could not send you one. Im offering the guy help. He is clearly stressed out due to money. And this season is usually very stressful for many people due to family, jobs, and cold weather.
Peace
I PM'd the guy when I saw his posts getting deleted. I know he's probably very frustrated at the moment, but if he could just have a little more patience, he would find that this community can be really helpful. Sorry, but I dont want any posts with profanity or vulgarity. If you want your post to survive then dont lace it with profanity or vulgarity. Anyone who re-quotes it is going to risk the post being deleted also. After PMing him and apologizing I got a kick in the face back, so as far as Im concerned I forgive him and hope he goes to another community. |
|
|
|
I also want to use this post to highlight something that I would like to have more insight in: there are a lot of 'winnings' where the same masternode wins two times in a row. For example: "21718": "BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS:3",
"21719": "BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS:7",
"21720": "BLWrBmujyTdv2qxwn8KDFpUFrTvH7AbmD1:7",
"21721": "BLWrBmujyTdv2qxwn8KDFpUFrTvH7AbmD1:4",
"21722": "BNkdFRRo2Cycyvc37tVaNW4FCiFDrR9QDV:4",
"21723": "BNkdFRRo2Cycyvc37tVaNW4FCiFDrR9QDV:4",
"21724": "BQ4kjMzQUEcQdMMpvhDMNt2McfhxzKztRX:3",
"21725": "BQ4kjMzQUEcQdMMpvhDMNt2McfhxzKztRX:7",
"21726": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:3",
"21727": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:4", The winner is based on the delta between the masternode vin and the blockhash, so that makes the winner random, thats why they can repeat back to back. |
|
|
|
asked this above but it remained unanswered so I'm repeating : Rob , is there a way to track all the history of MN winners from the very beginning using CLI ? "masternode winners" outputs just a sliding 30 blocks window. Dash has an excellent site for this purpose : https://www.dashninja.pl/do we plan to have a similar service ? Btw, Alex is working on everything the Dash Masternode has for Sanctuaries! EDIT: Looks like 'masternode winners nLookback' can be used. I dont see a limit in the code, so you should be able to get all-time if you want. Btw, we have the 'exec subsidy height' command also that shows amount paid, and address paid to. If you want I can put the masternode address and amount in there also. |
|
|
|
Hi Rob, Alex,
Thanks for your hard work over the last few days. let's hope this version is stable and doing what we need it to!
Just wanted to let you know that the pool is still telling people to upgrade to v1.0.6.7 so perhaps we should update that message.
Thanks
Yeah, had a dentist appointment. Things are coming together now. Thanks for reminding me. |
|
|
|
Can a version number be placed on the windows executable or maybe just under the button to download it? That way we know when an upgrade will be needed without having to install it to see if a version changes.
Great idea Pew! Thanks for the original thinking here. Let me look into it. If its not done by tomorrow please remind me. (It must be automated, if its in BiblePay!) |
|
|
|
|
BiblePay - 1.0.6.9
Mandatory Upgrade
- Enable superblocks and masternode payments at block #21710
** Note: Windows upgrade is ready. **
|
|
|
|
Dont be sorry Rob!, Only a few awesome volunteers helped test things in testnet while the rest chased profits  You did it for profits too! You ask for money as I check the proposal. So you are not a volunteer. Wait, lets stop here for a minute, I just want to stick up for Togo. He had the intention of doing this for free even if we did not have a proposal budget. He probably puts in a few hours a day manning all of our social media services and does not charge us for that. Alex stayed up all night last night analyzing payments and prior blocks and does not charge for that. I dont charge for being in slack and debugging with the devs. But my point is, I do want our budgets to be strong enough to pay a team of developers, especially if our price rises. So hopefully you wont consider me greedy (and no longer a volunteer) when I add a proposal for 40 hours of work. I dont think we should be labeled as "greedy" as soon as we ask for something back, thats all. You probably didnt even intend it that way either! Just for transparency sake, Im going to eventually be adding proposals for 40 hour payroll every 2 weeks. All the other time is pretty much volunteered- time spent answering emails for the pool, maintaining the pool, etc. If we can make this a consistent business, our coin will thrive and grow forever! Long live BiblePay! All Grace to God, the Highest God, Yeshua. |
|
|
|
An amazing idea life changing idea Biblepay for the homelessLook what someone has experimented with https://www.youtube.com/watch?v=ZvHicsIN8J4Imagine mining to help homeless people with real items they need. Delivered anonymously or ministered in person! Delivered within hours! I messaged Rob, but at a minimum let us think of items the homeless need. And add it to the store catalog My list so far - sleeping bags
- blankets
- socks / beanies
- small cooking kits
"And if anyone gives even a cup of cold water to one of these little ones because he is My disciple, truly I tell you, he will never lose his reward.""One who is gracious to a poor man lends to the LORD, And He will repay him for his good deed."This is an awesome idea! Just out of curiosity, I wonder if we should offer moving blankets for sale from the wallet? Wouldnt it be better to get 12 for the price of $90 and help 12 homeless people? We could offer both: https://www.amazon.com/dp/B01EX3A8DS |
|
|
|
yes updates without testing ... daaaamn it guys/girls=cos we got between us too ...
all updates could be in testnet and then applicate in da PROD ...
last 3 updates was what?
I dont know, I heard Klondike tested it and told us it was working fine? Whats wrong with that Klondike guy. |
|
|
|
i see buddie but where we have to fast run? ..... more ppl asking me about BBP that wiki is important and no updates ... every excellent coin got excellent web with excellent new informations .... take it as advice till now your main web www.biblepay.org missing NEW RELEASES of WALLET ... it so hard to do this? its simple easy we no need hurry hurry hurry hurry MASTERNODES ... let it cool down a little, cos ppl is angry on your nonstop updating take it as advice Take my advice: its better to ensure our features are working right now while the exchange is down. Thats why we are doing this. |
|
|
|
|
BiblePay - 1.0.6.9
Mandatory Upgrade
- Enable superblocks and masternode payments at block #21710
** Note: This is the linux upgrade. Windows will be ready in 3 hours **
|
|
|
|
if didnt help our helps then fast way will install new biblepay=question about few minute but this helped all if you have TW i can help you via remote  and Rob: you wrote tons of pages before that MN will be start 26.12 and you wanna start it now? dont understand your thinking We were originally going to go through this painful upgrade process the week of Christmas with a target date of Christmas to go live. However, with CCEX and Coins having us down for maintenance, we want to take this opportunity to test every chain-breaking risky feature now before giving them the green light to upgrade. |
|
|
|
Bible_pay: could you please leave some time like 12hours for the coming upgrade? It is Monday now.
The block wont hit for 40 more blocks so you do have some time. We need to get this upgrade propogation started while we are down at ccex. Hes going on vacation soon, and also, I have PMs from people counting on masternodes to go live, and its paramount we test our feature in order to verify we are safe for exchange consumption as soon as possible. CoinsMarkets.Com is also waiting. |
|
|
|
Please find a satanic community. |
|
|
|
|
Alright guys, I found the problem... Unfortunately Superblocks must be enabled for Sanctuary Payments to actually flow back into the miners block.
I took a look at that situation while we were in testnet, and convinced myself that we could push superblocks out a little further, and that is not the case. Sorry about that, my intention was to make things safer.
So what this means is we will need yet another mandatory, hopefully the last one for two quarters.
On the bright side, we can get the suspense out of the way for our superblock feature, and go through this right now while we are down at c-cex and get this pain out of the way. In addition only half of the network upgraded to 1068, so this is not going to be painful for everyone.
So, please keep your eyes peeled for the linux version in one hour, and then the windows version of 1.0.6.9 in 4 hours.
I apologize for the hassle.
Rob
|
|
|
|
Did all that, and I am still sitting at node 21559, 25 hours behind now, and just getting larger.
You need to upgrade to 1.0.6.8 to get past 21559. Then delete %appdata%\biblepaycore chainstate and blocks Then restart. |
|
|
|
Fresh linux install gets error loading block database. Do you want to rebuild the block detabasenow? Y/n doesnt do anything
Hey Guys, Im running the Docker version (by gagaha, https://hub.docker.com/r/gagaha/biblepay/, which autocompiles from the source) from linux command line. After upgrading to 1.0.6.8b it does load upto block xxx, but im getting the following error a number of times: "CMasterNodeBlockPayees:: IsTransactionValid -- ERROR: Missing required payment, possible payees: ....."Any idea? Will cleaning up the install help? How do i do this in a docker volume? That should be OK, as that is normal before you are completely synced and then synced with sanctuary data. Please do mnsync status and see if its 999. After its 999 you should no longer receive that error in the log. |
|
|
|
I thought masternode payment is started?
Maybe we must vote for payment?
We are already in the masternode payment season, so I have to assume we dont have enough votes yet for the first payment. I just audited the chain to the tip and no one has been paid yet. Looking at masternode winners, I see a few 10's in there. Our governance min quorum is 10 (see getgovernanceinfo). The nodes auto-vote for themselves for payment, so that is not a problem. The votes are definitely working, as we see them in slack. Ill do a little poking around in the next hour to see if we need 11 votes or not. |
|
|
|
|
Show Posts
