Alright guys, this has to be our last mandatory for a few months.
This is a pre-release notification for Linux only, if you are on linux you can start upgrading:
BiblePay - 1.0.8.1
Mandatory Upgrade for entire network
Cutover Height: 25910
- Filter botnet
- 7 minute block targets
- At block 25910, old clients fork
Windows is compiling...
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 705. (Read 243376 times)
January 15, 2018, 06:59:45 PM
January 15, 2018, 06:36:02 PM
I've got the next video tutorial done. https://youtu.be/5-WiMBCvI8g. Updating Linux Masternode. Will work some more on the basic installing on Windows and hope to have it out quicker than the turnaround this one took. On the plus side, got the video editor working better, so it looks more professional.
Awesome! Ill add it to the sanctuary guide!
Will you post a link to Klondike's tutorial? Thanks
Slovakia and Klondike are one and the same person
And I don't understand why Slovakia is bashing on the youtube videos, because West is gonna make a lot more and help people like Slovakia. Slovakia happens to be someone who isn't good at reading instructions. I helped him set up a masternode in testnet, and he was continuously saying that the instructions were bad, but in reality he just wasn't reading them with enough attention. So video's would probably help (people like) Slovakia tremendously in setting up and updating stuff, since his efforts will be reduced to copying the graphical representation that is shown to him. January 15, 2018, 06:26:13 PM
I've got the next video tutorial done. https://youtu.be/5-WiMBCvI8g. Updating Linux Masternode. Will work some more on the basic installing on Windows and hope to have it out quicker than the turnaround this one took. On the plus side, got the video editor working better, so it looks more professional.
Nicely done 616westmoth. I check some of it out and your voice and content organization are great. My only comment would be to change the initial splash screen. It has a very washed out feel to it. Try to use all white colors so the text stands out
I'll adjust it next video, the white background was just way too bright for me so that's how I ended up there. But I'll give it a second look and go from there, maybe it looks different on YouTube than in my graphics program. I used GIMP for graphics, Davinci Resolve for video editing and the audio recording, and GeForce Experience's built in screen recording on my NVidia Card.
January 15, 2018, 06:12:27 PM
I've got the next video tutorial done. https://youtu.be/5-WiMBCvI8g. Updating Linux Masternode. Will work some more on the basic installing on Windows and hope to have it out quicker than the turnaround this one took. On the plus side, got the video editor working better, so it looks more professional.
Nicely done 616westmoth. I check some of it out and your voice and content organization are great. My only comment would be to change the initial splash screen. It has a very washed out feel to it. Try to use all white colors so the text stands out
January 15, 2018, 06:08:31 PM
Alright, let's kick off the botnet.
The release will be ready in 4 hours.
This next release is just going to accept blocks > 1.0.8.0 and not do anything new with POS-POBH.
The release will be ready in 4 hours.
This next release is just going to accept blocks > 1.0.8.0 and not do anything new with POS-POBH.
Sound great to kick it, but what does it means? Will that mean that all users then need the new release (> 1.0.8.0 including 1.0.8.0b) or is the current release (>= 1.0.8.0b) ok?
In anycase it is a really good motivation for me to go on with the debian package topic (http://forum.biblepay.org/index.php?topic=79.msg1053), I'm starting to hate the compilation on my systems
By the way, it would be fantastic if more people could give me feedback on that topic (includes two proposal ideas)
The forum seems a little bit "deserted", would it be better to post such topics here in the future?I'm already diving deep into the debian package topic (I really think it is a good idea
), but I would still really love getting feedback on the pool idea. As far as what technically happens, we will release 1.0.8.1 in about 3 hours (30 minutes for linux), and everyone will be required to be on 1.0.8.1 before block 25900. After block 25900, we will reject blocks from pre 1.0.8.0 clients.
Actually while we are doing this, why dont we go to 7 minute blocks also? We might as well fix that now so that we can have more reliable superblocks and have the ability to pay compassion.com every 30 days?
Hang on guys... Ill push it back a little further and fix that now.
January 15, 2018, 06:04:59 PM
Alright, let's kick off the botnet.
The release will be ready in 4 hours.
This next release is just going to accept blocks > 1.0.8.0 and not do anything new with POS-POBH.
The release will be ready in 4 hours.
This next release is just going to accept blocks > 1.0.8.0 and not do anything new with POS-POBH.
Sound great to kick it, but what does it means? Will that mean that all users then need the new release (> 1.0.8.0 including 1.0.8.0b) or is the current release (>= 1.0.8.0b) ok?
In anycase it is a really good motivation for me to go on with the debian package topic (http://forum.biblepay.org/index.php?topic=79.msg1053), I'm starting to hate the compilation on my systems
By the way, it would be fantastic if more people could give me feedback on that topic (includes two proposal ideas)
The forum seems a little bit "deserted", would it be better to post such topics here in the future?I'm already diving deep into the debian package topic (I really think it is a good idea
), but I would still really love getting feedback on the pool idea. Guys, I hate seeing 3100 pool users hitting the pool and only solving 10% of the daily blocks, so that added to the motivation to do this.
I know this is just a game of cat & mouse with the botnet, but we might as well give them one more night of "chasing us" since they now will have to recompile at least 500 PCs in my estimation and will at least be running the latest software with instantsend.
But yes, I agree, I am not really going to play this game of cat and mouse much longer. It happened with Darkcoin (they eventually abandoned PC mining algorithms, it happened with Vertcoin - they had a botnet take over the supermajority of their hashpower, and now, this botnet is trying to do it to us). Im pretty sure we will need a hybrid proof-of-bible-stake algorithm mixed in next, but it needs to be done with more patience and testing this time around.
Tom, I understand where you are coming from, but I already went ahead and coded it, I think we can just go ahead and bite the bullet with one more upgrade, sorry for the inconvenience... At least in 3 hours, the botnet will be gone and we will be the wild west over here for the night!
January 15, 2018, 05:51:25 PM
Alright, let's kick off the botnet.
The release will be ready in 4 hours.
This next release is just going to accept blocks > 1.0.8.0 and not do anything new with POS-POBH.
The release will be ready in 4 hours.
This next release is just going to accept blocks > 1.0.8.0 and not do anything new with POS-POBH.
Sound great to kick it, but what does it means? Will that mean that all users then need the new release (> 1.0.8.0 including 1.0.8.0b) or is the current release (>= 1.0.8.0b) ok?
In anycase it is a really good motivation for me to go on with the debian package topic (http://forum.biblepay.org/index.php?topic=79.msg1053), I'm starting to hate the compilation on my systems
By the way, it would be fantastic if more people could give me feedback on that topic (includes two proposal ideas)
The forum seems a little bit "deserted", would it be better to post such topics here in the future?I'm already diving deep into the debian package topic (I really think it is a good idea
), but I would still really love getting feedback on the pool idea. January 15, 2018, 05:49:55 PM
I know its hard to upgrade so many devices, but 1.0.7.1 might be too old to tolerate - at least at this stage as the network isn't big enough to do it automatically.
I say lets move forward and kick them.
I say lets move forward and kick them.
To you, Tiras, Slovakia, and the others complaining about the low hash power of the pool, yes I agree- maybe we should boot the botnet off.
I don't like the fact that a botnet has basically taken over the majority of the hash power here and refuses to run the latest code, which in some cases, is dangerous, as we are really a cutting edge community here.
The biggest issue I have with this is Id hate to just kick them off so they are forced to upgrade (by issuing a mandatory that refuses old blocks) and then have them upgrade and just do it again- then we are back at square 1 for our next upgrade.
The only way we can really do this properly is to make Biblepay a partial Proof-Of-Biblehash/Proof-of-stake hybrid, in the sense that you have to stake some of your balance in order to mine. That would tend to kick off the botnets, the ones who have zero or low balances, and force the PC to re-stake old coins; it also requires a PC to create the block.
The idea here is lets say we make your (coin-age * coin-amount-staked) equal to the hash-target-boost you receive for that block. Then we would tend to reward our loyal community with solutions, and not bot nets.
I'm willing to research the solution tonight and see if we can potentially put this in testnet, as long as this can be done as a mandatory before c-cex reopens. Otherwise we should probably deal with the botnet until June and explore the option for potential future release.
Even though I'd like to see the botnet gone, with just a few days til C-cex reopens it seems wise to wait. Another mandatory upgrade at this point will just raise stress levels and is unlikely to help the situation very much. We could find ourselves in a tight-spot if C-cex reopens early.
January 15, 2018, 05:39:22 PM
I've got the next video tutorial done. https://youtu.be/5-WiMBCvI8g. Updating Linux Masternode. Will work some more on the basic installing on Windows and hope to have it out quicker than the turnaround this one took. On the plus side, got the video editor working better, so it looks more professional.
Awesome! Ill add it to the sanctuary guide!
Will you post a link to Klondike's tutorial? Thanks
January 15, 2018, 05:37:49 PM
Alright, let's kick off the botnet.
The release will be ready in 4 hours.
I'll be back in about an hour when linux is ready to compile.
Get ready for one more release.
This next release is just going to accept blocks > 1.0.8.0 and not do anything new with POS-POBH.
That future feature really has to be developed with care and tested in testnet for a couple months, then we can put it in the June release, as long as everyone likes the design.
The release will be ready in 4 hours.
I'll be back in about an hour when linux is ready to compile.
Get ready for one more release.
This next release is just going to accept blocks > 1.0.8.0 and not do anything new with POS-POBH.
That future feature really has to be developed with care and tested in testnet for a couple months, then we can put it in the June release, as long as everyone likes the design.
January 15, 2018, 05:28:21 PM
Swongel is translating the ANN post into Dutch, got a message from him:
"I was translating and I stumbled upon what I think might be an error just checking with you before bothering Rob;
https://bitcointalksearch.org/topic/biblepay-10-to-orphan-charity-randomx-mining-sanctuaries-masternodes-2388064 says 18% Deflation per year (1.5% per month).
1.5% per months would be 19,56% per year (1.01512) if I'm not mistaken;
also shouldn't it be Inflation? Since there will be coins added to the circulation and not subtracted?" -Swongel
Thanks, updated the OP to refer to 19.5% compounded and deflationary and added the wiki link."I was translating and I stumbled upon what I think might be an error just checking with you before bothering Rob;
https://bitcointalksearch.org/topic/biblepay-10-to-orphan-charity-randomx-mining-sanctuaries-masternodes-2388064 says 18% Deflation per year (1.5% per month).
1.5% per months would be 19,56% per year (1.01512) if I'm not mistaken;
also shouldn't it be Inflation? Since there will be coins added to the circulation and not subtracted?" -Swongel
There is a post on this forum explaining the compounding effect - I think it is about 10 pages back.
January 15, 2018, 05:25:54 PM
I know its hard to upgrade so many devices, but 1.0.7.1 might be too old to tolerate - at least at this stage as the network isn't big enough to do it automatically.
I say lets move forward and kick them.
I say lets move forward and kick them.
The only way we can really do this properly is to make Biblepay a partial Proof-Of-Biblehash/Proof-of-stake hybrid, in the sense that you have to stake some of your balance in order to mine. That would tend to kick off the botnets, the ones who have zero or low balances, and force the PC to re-stake old coins; it also requires a PC to create the block.
The idea here is lets say we make your (coin-age * coin-amount-staked) equal to the hash-target-boost you receive for that block. Then we would tend to reward our loyal community with solutions, and not bot nets.
I'm willing to research the solution tonight and see if we can potentially put this in testnet, as long as this can be done as a mandatory before c-cex reopens. Otherwise we should probably deal with the botnet until June and explore the option for potential future release.
January 15, 2018, 05:21:30 PM
Hey guys just finished a PI setup guide. If you have a PI and want to try it please do so and let me know if you run into an issues.
https://www.reddit.com/r/BiblePay/comments/7qnbp4/bbp_miner_on_pi/
I check the forms but reddit is the best way to let me know if you have an issue.
Thanks and god bless.
https://www.reddit.com/r/BiblePay/comments/7qnbp4/bbp_miner_on_pi/
I check the forms but reddit is the best way to let me know if you have an issue.
Thanks and god bless.
January 15, 2018, 05:20:47 PM
I've got the next video tutorial done. https://youtu.be/5-WiMBCvI8g. Updating Linux Masternode. Will work some more on the basic installing on Windows and hope to have it out quicker than the turnaround this one took. On the plus side, got the video editor working better, so it looks more professional.
Awesome! Ill add it to the sanctuary guide!
January 15, 2018, 05:18:56 PM
I know its hard to upgrade so many devices, but 1.0.7.1 might be too old to tolerate - at least at this stage as the network isn't big enough to do it automatically.
I say lets move forward and kick them.
I say lets move forward and kick them.
To you, Tiras, Slovakia, and the others complaining about the low hash power of the pool, yes I agree- maybe we should boot the botnet off.
I don't like the fact that a botnet has basically taken over the majority of the hash power here and refuses to run the latest code, which in some cases, is dangerous, as we are really a cutting edge community here.
The biggest issue I have with this is Id hate to just kick them off so they are forced to upgrade (by issuing a mandatory that refuses old blocks) and then have them upgrade and just do it again- then we are back at square 1 for our next upgrade.
The only way we can really do this properly is to make Biblepay a partial Proof-Of-Biblehash/Proof-of-stake hybrid, in the sense that you have to stake some of your balance in order to mine. That would tend to kick off the botnets, the ones who have zero or low balances, and force the PC to re-stake old coins; it also requires a PC to create the block.
The idea here is lets say we make your (coin-age * coin-amount-staked) equal to the hash-target-boost you receive for that block. Then we would tend to reward our loyal community with solutions, and not bot nets.
I'm willing to research the solution tonight and see if we can potentially put this in testnet, as long as this can be done as a mandatory before c-cex reopens. Otherwise we should probably deal with the botnet until June and explore the option for potential future release.
January 15, 2018, 05:12:22 PM
Swongel is translating the ANN post into Dutch, got a message from him:
"I was translating and I stumbled upon what I think might be an error just checking with you before bothering Rob;
https://bitcointalksearch.org/topic/biblepay-10-to-orphan-charity-randomx-mining-sanctuaries-masternodes-2388064 says 18% Deflation per year (1.5% per month).
1.5% per months would be 19,56% per year (1.01512) if I'm not mistaken;
also shouldn't it be Inflation? Since there will be coins added to the circulation and not subtracted?" -Swongel
"I was translating and I stumbled upon what I think might be an error just checking with you before bothering Rob;
https://bitcointalksearch.org/topic/biblepay-10-to-orphan-charity-randomx-mining-sanctuaries-masternodes-2388064 says 18% Deflation per year (1.5% per month).
1.5% per months would be 19,56% per year (1.01512) if I'm not mistaken;
also shouldn't it be Inflation? Since there will be coins added to the circulation and not subtracted?" -Swongel
January 15, 2018, 05:12:01 PM
Hey Rob, SEO_Account was attempting to create a Proposal on the Pool website but he noticed this message:
"** Note: Each new Proposal costs 2500 BBP. Please do not Save the proposal unless you agree to pay 2500 BBP **"
Does the proposal fee come out of the pool account? How does this work?
(If it does come out of the pool account, is there a way to send funds to ones pool account?)
If BBP price is about $0.01 per BBP, thats about ~$25?
My understanding is that proposal fee is to help reduce spamming of proposals?
Thanks!, Togo
"** Note: Each new Proposal costs 2500 BBP. Please do not Save the proposal unless you agree to pay 2500 BBP **"
Does the proposal fee come out of the pool account? How does this work?
(If it does come out of the pool account, is there a way to send funds to ones pool account?)
If BBP price is about $0.01 per BBP, thats about ~$25?
My understanding is that proposal fee is to help reduce spamming of proposals?
Thanks!, Togo
Yeah, someone tried to create a proposal pointed to a web site that had a virus on the page. I think theyve tried pretty much everything now.
(That almost beats the one where they uploaded a virus into an orphans letter).
So I had to raise the bar a little bit to enter proposals.
You know, in Dash, its 5 dash to create a proposal, and since that is like $5000, over there the proposer usually asks for reimbursement inside the proposal.
So I recommend doing the same thing here, pad the 2500 bbp on top of your proposal amount.
The amount is deducted from the users pool balance.
Its also there to help reduce proposals down to serious proposals only, the least I would expect is someone to spend $25 up front to ask us to evaluate the proposal (as it takes all of our time to vote on it and read it and discuss it) etc.
I could deposit BBP into ones pool account if a person sends me BBP, Ill credit the pool account if need be.
Awesome!, oh man so many terrible people in the world... ugh
The 5 Dash fee has been interesting to watch given how much it costs now, its hard for the average joe to create proposals over there,
I think theyve been debating a lower fee, but also theyve debating ideas like sub DAOs, and having organizations that vet projects and fund the fee,
very interesting to watch unfold. There was one pretty awesome team that I saw that proposed creating a hardware wallet device for Dash and they got rejected, RIP $5k
Currently I only have ~400 BBP in my pool account and I guess SEO_Account doesnt have much BBP in his either,
I know your pool site abstracts the complexity of creating the proposal in the blockchain, which is awesome!,
but yeah It would be cool to be able to fund my pool account if possible!
I think this is going to cause it to be harder for individuals who want to do work with us who dont mine on the pool or who dont have any coins
(especially new charities/nonprofits and such), and I believe it also centralizes the process and causes you to have to do more work
(which Id like to lift as much extra work as possible from you!), but I do think the proposal fee is totally necessary.
Is there a way to enter the proposal into the blockchain without using the pool?
I believe there is, I can dig into it and write instructions, but not sure if it would show up on the pool website, hmmm
Ok, credited you the BBP to your pool account.
The commands to do it from the chain are actually in the pool source code, its not easy, but its not rocket science. It requires dumping 6-7 fields in notepad, creating a hex proposal with rpc commands, sending money to escrow in the chain, recording txid, sending the thing into the chain as a proposal with escrow, so yes it can be done manually.
I would not worry about this centralization too much right now, as I think the weed and feed nature weeds out corruption and is a greater benefit than spending time on the issue, we have a lot to do, and technically its still decentalized anyway. I think we should take a look at creating a spreadsheet of third world countries and filling fields with attributes for the unbanked, and starting an initiaitve to add a bbp feature taht services the unbanked and somehow, provides food to starving children in that area. We could ask Webster to make us a mobile electrum wallet, and lets try to be the creator of some high technology that lets you buy a loaf of bread in that area, or use bbp like a checking account.
The stragglers will come on the board and beg you to enter a proposal, not a problem.
You rang.. lol
Yeah Id love to do that and actually AM doing that. I am considering different server side options for the RPC side. There are many libs out there to choose from . I have dug a bit into electrum server and got it installed but then got distracted with the UI side of things. Ive got several learning curves im going through with all these technologies (front and back) and languages so bear with me as I figure out several approaches.
Also Ill never be able to mine 2500 bbp...with the missing blocks and my very low cpu resources id be lucky to reach that target in weeks. So to submit a proposal I will have to forward you some coins when Im ready to put something together. And I def want to get into this next blocks budget. Also have some interesting ideas for a PR project. Going to be a very busy next two weeks for me...
... I am going back to my coding cave now to absorb the bookmarks.... if only i could pause time to let my brain catch up to all these different bits of pieces ....
Ok, sounds like you are very passionate about this project, thats what we need! Sweet. Yeah, we will back you when we need to put the proposal in, awesome.
January 15, 2018, 05:10:30 PM
Sent 50k BBP to B74TWhTE5aCXc2WfPfZUcgQ3mnvcqFXm7J
Pool username is: togo_w
Looks like its still unconfirmed until we pass block 25865
Thanks!
Pool username is: togo_w
Looks like its still unconfirmed until we pass block 25865
Thanks!
Ok, thanks a lot, credited.
January 15, 2018, 05:06:24 PM
"Regarding the dynamics of solving blocks on prior versions I will go into detail on that after church."
So although we required a mandatory upgrade between 1.0.7.7 and 1.0.7.8+, this was intended to upgrade instantsend, but not to kick the miners off the current block algorithm.
So the enforcement in this case was set for a protocol upgrade (for sanctuaries) and a soft-hangup on old versions.
This means that blocks solved on prior versions are not discarded unless mined on a fork. So when we get to the point of a 50% upgrade level, those old versions are going to be wasting hashpower. I see we have 63% right now on 1.0.7.1 that has not upgraded.
So this effect will come into play when the 63% solo level drops to 49%. That hash power is going to go to waste and provide more coins for the early birds who did upgrade.
Now here is a Very interesting effect that is happening right now and might answer some of our network questions. I flipped the switch on the pool requiring 1.0.7.9+ to hash against the pool. There are 63% now that are either solo mining or have a private pool, as they are still solving blocks at the 63% level on the network currently right this second (and cant be in the pool as the pool refuses the connection). That explains where 63% out of our 75% is, but we still do not know if its a solo group, a botnet or a private pool.
Sorry for my ignorance, but I still don't get it what is happening now after the "mandatory" upgrade to 1079. From MY understanding a "mandatory" upgrade results in a fork (at a certain block). Apparantely this is NOT what this is, since you write that all blocks solved on older versions are still valid ("unless mined on a fork"
). Then you write "when we get to the point of a 50% upgrade level, those old versions are going to be wasting hashpower". How so? On the other mandatories you were afraid that at the key block not enough would have upgraded and therefore the blockchain would fork with the majority on the "wrong end". Isn't this exactly what this is right now? The botnet (and judging by the non-existent pool solutions about 90% of the overall hashpower....) are on a major fork and the pool (so "we all") are the minor "wrong" fork?Please explain what has happened the last 2 days and how you ever expect the botnet and all the solo miners to update, considering that the current state works just marvellous for them...
Let me talk a little about the magical missing pieces.
I try to be fair for everyone. Since this mandatory involved the IS vulnerability only and was not a mining algo change, I feel its a little unfair for me to hard fork the miners, so I incremented the protocol version required for sancs (since they provide the instant send service), and required a mandatory for the regular network with the punishment being that we hang up on older nodes. I did not create a fork however.
So basically, if you are one of those botnet users, you cant instant send funds. Our sancs had to upgrade, since they would stop getting paid (so they all did already, I can see that). Anyone who upgraded can now send IS again.
So our only problem is 1000 or so PCs on 1.0.7.1 wont upgrade and they are 60% of our network hash power.
The reason they still exist, is someone is acting as a bridge between the old version and the new version.
I could potentially kick them off... but should we?
BTW, to answer your question, our version 1080 will hang up on those nodes and not service them. You are correct, since we are newer, they will not hang up on us. Someone out there is acting as a bridge, and forwarding their blocks to our chain, could be a fraudulent client with a fake protocol version compiled in.
Should we kick them off?
Rob, there have been tons of mandatory upgrades since 1071 .
why the heck 1071 is still usable . if there's a way to kick them out just do it then .
Code:
1.0.8.0-Mandatory
- Fix bug in instant send
commit e2c57306af1fc1a765e5898c4a0e01cae8491c51
Author: biblepay
Date: Sat Jan 13 13:59:29 2018 -0600
1.0.7.9-Mandatory
- Fix instantsend security bug
- Increment protocol to 70714
commit a84cead3c51500d029f3f7f720cef3e93d30ff89
Author: biblepay
Date: Sat Jan 13 08:33:41 2018 -0600
1.0.7.8-Mandatory
- System wide upgrade to protocol version 70713
commit 210b099cc1a7e15f70102e8c6986b2287fb8bd02
Author: biblepay
Date: Fri Jan 12 15:07:29 2018 -0600
1.0.7.7.c-Mandatory Upgrade
- Fix Logging Bug
commit b83449d41e7a3cd835548fc801a830b64d6002a5
Author: biblepay
Date: Fri Jan 12 14:49:13 2018 -0600
1.0.7.7b-Mandatory Upgrade
- Bump protocol_version to 70713
commit 544258ddd52344a21194187589597245e46def8e
Author: biblepay
Date: Fri Jan 12 12:36:40 2018 -0600
1.0.7.7-Mandatory Upgrade
- Fix instantsend security bug
commit 66c28959e1637dc4a135c8274d065ac22656e979
Author: biblepay
Date: Thu Jan 4 15:57:39 2018 -0600
1.0.7.6-Leisure
- Fix bug in HTTPS pool communication
- Show a bible verse in popup balloon when receiving a transaction
Yes if version mandatory should kick people with versions much lower then current. What if hardfork happen and half the miners stay on there? We get bbp classic token? Lol
January 15, 2018, 05:02:47 PM
I've got the next video tutorial done. https://youtu.be/5-WiMBCvI8g. Updating Linux Masternode. Will work some more on the basic installing on Windows and hope to have it out quicker than the turnaround this one took. On the plus side, got the video editor working better, so it looks more professional.
Awesome! Ill add it to the sanctuary guide!
Jump to: