We hit block #21350! https://biblepay-explorer.org/- F8000 (Proof-of-Bible-Hash) Starts at block #21350 - Sanctuaries go live at Block #21350 - Amazon integration (in wallet e-commerce) goes live at block 21350 - Sanctuary payments go live at block #21551 - Proposals and Budgets go live at block 21551 - Superblocks start at block 30001 - Superblock are monthly We should be hashing in f8000 right now in (upcoming) block 21351. Therefore HPS should have dropped. This should be a very interesting block. Block 21351 should make all non-upgraded nodes veer off-track and blow up.... I think half of the network on node.biblepay.org is on a fork, so I think I will lose half of my connections very soon... EDIT: I was just thinking, this might be a long block... Because half of the network who has not upgraded is not going to count toward solving it (as their solutions are invalid) so we have a 10965 diff, we might sit here for 30 minutes to solve it. Time to go outside and do some yardwork... Tiras Im checking, I havent found a problem in the pool yet to put a finger on it. Deadlock is definitely fixed, pool is caught up... |
|
|
|
I opened up a ticket with them. In the body I told them to contact you, and provided all of the coin information.
Yeah, I opened up two tickets with them in the past, and all I got was a canned reply saying how they would integrate if we send them 2 BTC blindly... |
|
|
|
|
Note to Sanctuaries for voting on proposals:
If you operate more than one sanctuary you can vote for all of them at once from the controller with one command.
Just copy the vote-many command by right clicking the proposal you want to vote on and copy the Vote for funding command to the clipboard and paste it in your controller wallet RPC.
It will vote for you on every sanctuary and give you a reply: Voted on Y on X nodes Successfully.
|
|
|
|
Coinexchange is an exchange that has alot of volume and loves masternode coins. I think we should consider asking them. https://www.coinexchange.io/They quoted me 2btc to do it then I asked for a contact to start integration and never got a reply. Feel free to contact them and get a firm contact to answer our questions. |
|
|
|
I feel weird asking for coins for work I did (Im just happy to be part of the project and to see the coins I have already grow in value), I will spend time over the next week or so looking at DASH and other masternode coins to see how they do proposals and if they have proposal guides/tips. For now I guess I will ask for: How many hours I spent working on a specific thing multiplied by an okay Hourly rate and convert that to BiblePay coins based on current BBP price? (Is there an easy way to get an average BBP price as of past 30 days?) I dont want to undervalue myself but I dont want to overvalue either. Ill just take a stab and I guess we shall see what happens! Will be an interesting experiment. === Just saw your last post Rob, yeah any help would be greatly appreciated! Im going to pass out after work today hahaha (Ive been slacking at work too LOL, dont tell my boss! LOL  ) BiblePay Wiki: http://wiki.biblepay.org/Main_PageWiki Formatting: https://www.mediawiki.org/wiki/Help:FormattingMy Current Proposal Submission Guide: http://wiki.biblepay.org/Create_Sanctuary_2#SUBMIT_PROPOSALId use the current price of bbp, instead of the 30 day avg as when you cash the proposal thats what you have in value in your native currency, Id just use the price per coin here: https://coinmarketcap.com/currencies/biblepay/And type in what you did for each set of hours and a fair rate per hour and a grand total. |
|
|
|
Can you explain how you expect this to work?
I propose my amount and then pitch it? Or develop some of it first, and then propose?
What do you suggest best chance for winning proposals?
How will it be approved? How soon (if it does)
Stuff like that
I propose that someone creates a wiki article for this- someone other than Togo who is overloaded, and znffal who is writing all the PDF guides, someone else who wants to help out and understands proposals and budgets. Ill post the Proposal independent audit report. |
|
|
|
On the fork we have a lot going for us. One, between 1065 & 1064 we almost have a supermajority already and 1064 should have enough in it to favor f8000's hashes. However the fork side is going to completely blow up... They are going to get banned by 1064+ within one block of the cutover. The reason this will end well for us is I can put a checkpoint in before we ask c-cex to come back online, so those forked coins will be worthless. So we might as well let them play as long as they want as that means more coins for the earlybird side.
Dev - 1. Can you explain this further? The coins from older clients will be worthless? Existing coins? 2. What do you mean 'more coins for the earlybird side' ? No, all coins are still safe, what I mean is after block 21350, if someone decides to deliberately Not upgrade and mine on a fork, the newly generated coins, only the new coins on their branch will become worthless. What I mean on the earlybird comment is: If we truly do have a botnet out there of 300 machines (IE 30% of our network hash power) running a tweaked version of 1.0.4.0 - modified in their own hombrew fashion for speed, if they do not upgrade within the next 17 blocks, whats going to happen is all their hashpower is going to go toward their own electric bill - and that means it will be 30% EASIER for Us to mine coins on the Legitimate branch. So another words, if they are really resisting the upgrade, that is more coins for us on our Legit - earlybird side. |
|
|
|
Thank you Rob!, I stayed up till 4am last night working on the 2nd guide O_O
I consider it more complete and tested now (though still might be a little confusing in some parts)
Any and all feedback is welcome!
Should I set up a donation address? or maybe submit a proposal?
(Im really curious to learn more about and try out proposals)
Togo, Let me make a dedicated top level thread for Prod proposals over on the forum, and let me test one real quick..... Hang on... Togo, I created a top level thread here for our proposals: http://forum.biblepay.org/index.php?topic=44.0... and deployed Proposals to Prod... Go ahead and unleash your proposal. |
|
|
|
Thank you Rob!, I stayed up till 4am last night working on the 2nd guide O_O
I consider it more complete and tested now (though still might be a little confusing in some parts)
Any and all feedback is welcome!
Should I set up a donation address? or maybe submit a proposal?
(Im really curious to learn more about and try out proposals)
Togo, Let me make a dedicated top level thread for Prod proposals over on the forum, and let me test one real quick..... Hang on... |
|
|
|
I have a more step by step Sanctuary Guide that I am working on, its not complete nor thoroughly tested yet, but I wanted to throw it out here to help anyone!, I hope to completely step through it and finalize it tonight after work http://wiki.biblepay.org/Create_Sanctuary_2Wow, that is quite extensive! Great job! I see you are starting to cover proposals also. Thank you Rob!, I stayed up till 4am last night working on the 2nd guide O_O I consider it more complete and tested now (though still might be a little confusing in some parts) Any and all feedback is welcome! Should I set up a donation address? or maybe submit a proposal? (Im really curious to learn more about and try out proposals) Yes, we should start debugging Prod proposals. Before you create one, let me ensure the proposals are deployed to prod in the pool. Ill be back in 30 mins or so and Ill let you know when its ready to test a prod proposal. In the mean time you can still create a forum link for it. You might want to see if we have a "Production" mother topic set up for proposals, if not please create that first and put yours under it. |
|
|
|
bounced back at 12:26pm to ~ 60% :
So I see the pools SQL server is relatively overloaded, its got some deadlocks going on. Ive been looking for the cause of the deadlock and I see the #1 deadlock is people trying to view the Block Distribution a lot per day. So I made a change where we cache the block distribution report between blocks. Lets see if this fixes the problem... Let me know if there is an improvement... If not Ill have to go down the list to the next deadlock. |
|
|
|
Now as far as our network status, we dont have a supermajority on 1065 yet!
According to exec versionreport, we have a botnet running 1.0.4.0 (who will be kicked off the network when we get a supermajority, but this botnet is 30% of our nodes, probably solo mining on this old version because they have tweaked it or something).
But we have a pretty big problem still... We need to get 1.0.6.5 up to 51% of the network....
Please everyone upgrade... We have to kick off 1.0.4.0 off the network in 50 more blocks, or we risk a fork.
I have a question. What happens if there will be less than 51% of upgraded wallets? The botnet will kick out those 1.0.4.0 before the cutover block? When the botnet kick out those nodes, it still won't be more then 51% upgraded wallets? And offtopic  Is there some config option before compile, to speed up compilation, for example without QT, if you are running only on VPS? For example when i try it on VM or for masternode. Thanks. On the speedier compiling, I think the answer is "make -j4" try that to see if it uses all 4 cores. On the fork we have a lot going for us. One, between 1065 & 1064 we almost have a supermajority already and 1064 should have enough in it to favor f8000's hashes. However the fork side is going to completely blow up... They are going to get banned by 1064+ within one block of the cutover. The reason this will end well for us is I can put a checkpoint in before we ask c-cex to come back online, so those forked coins will be worthless. So we might as well let them play as long as they want as that means more coins for the earlybird side. |
|
|
|
I just got a message that the deal fell through [to add us to Two Top 5 exchanges in Jan 2018]. So I am modifying the client to Not mint the 3.5 BTC block.
(Note, the block was for 3.3 BTC for integration fees + .2 BTC for service fees that is why it was 3.5 btc).
I just wanted to update anyone that was waiting in the wings - not buying BBP to realize that we wont have any special deal to buy at next week, so I didnt want to stop anyone if you were holding off. Now going forward, everything is voted in by the sanctuaries.
Is there any particulair reason why they wont even want to add BBP for around $50.000 ?!? Such a huge amount and still then they don't want to add it.. Hmmm, not liking the sound of that. Answers on all question except this one? Overlooked or...? Regarding the high fees its because these exchanges have a 400 coin backlog, so they are in control right now. |
|
|
|
switched 2 best nodes to pool2 but the issue is still there and all my nodes keep loosing hps and shares every 30 min or so.
Can you provide more exacting details that would allow me to reproduce? On a side note, I created two fresh nodes last night on vultr, and they are still mining and I earned 353 BBP in the last 24 hours, I dont see a problem. One more note, in 49 more blocks we go live with f8000, so it may be best to save this issue up for then and debug together. Either way I welcome fine details necessary to reproduce. |
|
|
|
an interesting project, is algo asic and gpu resistant? are there any independent miners workers anywhere without wallets? hmmm
Take a look at kjv.cpp BibleHash function, and then our whitepaper in the OP post. I dont think we have asics or GPUs, but Im sure we have hobbyists out there running tweaked versions. |
|
|
|
so we lost about 600 unaware miners. Hopefully they ll understand whats going on.
Edit: It would be cool to add notification feature to the biblepay website and use push notifications.
I had to enable the switch on the pool to enforce 1065 to try to cattle prod miners to upgrade now, as block 21350 is coming in only 50 more blocks... At that point these 600 miners were booted off the pool. I hope they come to the forum and find out they need to upgrade. Ill change our Pool slogan now to help explain whats going on. |
|
|
|
Thanks for all your hard work Rob. I think you have to learn to love the trolls. So many threads here have at least one. Adrianbits is either deliberately twisting things or has a genuine problem. Either way, it can't be much fun not living in reality. The natural reaction is to get angry when someone posts a lot of lies but I think its better to laugh it off and your post with the facts was much more powerful.
Ahhh the wisdom in this post is great, thank you sharpshot. |
|
|
|
yes: im mining with multiwallet still and working excellent tested this 1 xeon 12c/24t gave me 300 000 hash2 .. classic destroy powerhash all this update was for nothing.....  Have you read the release notes? We arent live yet until the cutover block in 49 more blocks! Slovakia..Slovakia... tisk tisk tisk... =-=-=-=-=- Now as far as our network status, we dont have a supermajority on 1065 yet! According to exec versionreport, we have a botnet running 1.0.4.0 (who will be kicked off the network when we get a supermajority, but this botnet is 30% of our nodes, probably solo mining on this old version because they have tweaked it or something). But we have a pretty big problem still... We need to get 1.0.6.5 up to 51% of the network.... Please everyone upgrade... We have to kick off 1.0.4.0 off the network in 50 more blocks, or we risk a fork. |
|
|
|
Devs -
"PLEASE UPGRADE PLEASE UPGRADE" message is showing when withdrawing by email.
Bug? I have updated all miners to 1.0.6.5
Thats quite funny! LOL. Will fix right now......... Argh. If anyone had trouble withdrawing from the pool: FIXED. |
|
|
|
|
Show Posts
