|
|
AlisterPlus
Newbie
 Offline
Activity: 11
Merit: 0
|
 |
March 16, 2019, 07:33:04 PM |
|
Hello! I'm back after many months and happy to see that I'm coming after the storm  I restored my wallet and my coins are still there !!  What is this "evolution"? Is it going to be a new coin or it will replace the current BBP? Should I do something with my balance (bbp)? Sorry for my ignorance.... |
|
|
|
|
|
|
AlisterPlus
Newbie
Offline
Activity: 11
Merit: 0
|
|
March 16, 2019, 07:54:12 PM |
|
Thanks togoshigekata but that is another coin. Right? I thought that evolution was something that will change in Biblepay... Sorry. |
|
|
|
|
|
togoshigekata
|
|
March 16, 2019, 08:00:02 PM
Last edit: March 16, 2019, 08:26:00 PM by togoshigekata |
|
Thanks togoshigekata but that is another coin. Right? I thought that evolution was something that will change in Biblepay... Sorry. Yeah sorry for not explaining further, BiblePay is a fork of the Dash code, our code started out as some version of the Dash coin code, but we havent included (merged in) all the latest Dash code changes (we have had our own developments and only merged in security things) Dash has released a few new updates called Dash Evolution, and Rob is going to add those into BiblePay A little more technical, I believe Rob is going to start with the latest Dash code, and then put all the BiblePay stuff inside of it and go from there Hope this makes sense I dont believe this will be a new BiblePay coin, same coin, just updated with latest Dash changes https://coinmarketcap.com/currencies/dash/= Rough BiblePay Evolution Timeline https://bitcointalk.org/index.php?topic=2388064.msg50078231#msg50078231Other Updates: https://bitcointalk.org/index.php?topic=2388064.msg50161396#msg50161396https://bitcointalk.org/index.php?topic=2388064.msg50149576#msg50149576 |
|
|
|
AlisterPlus
Newbie
Offline
Activity: 11
Merit: 0
|
|
March 16, 2019, 08:18:09 PM |
|
Thank you!!!! Very clear now. So nothing is changing for me as a bbp user I will need to just update my wallet. |
|
|
|
|
Lichtsucher
Jr. Member
Offline
Activity: 219
Merit: 3
|
|
March 16, 2019, 08:30:43 PM
Last edit: March 16, 2019, 09:09:50 PM by Lichtsucher |
|
guys, just use multiwallet, you can screw this system, and mine maximum from your PC.
for example, xeon 2695 v3, which has 14 cores, can have e.g. 14 * 4 wallets, each bbp daemon willl use 50%, just generate users under ubuntu, and run biblepayd on different ports,
this way you can mine much more.
BUT, when botnet starts mining, even this will be not that effective...
Simply set minersleep= and the right amount of genproclimit Running more wallets only forces the OS to do more context switches, so you will be slower. There is no way to "screw this system", as there is no artifical block in POBH. You get a block if you can calculate the right result, running more clients won't help, as your system is not getting more powerful this way. There might be edge cases in which two wallets might help, but running 56 Wallets is bullshit  Edit: If "system" means the official pool, that might be a different story. I remember hacks like this. But this is not biblepay itself. |
Purepool Biblepay Pool (https://www.purepool.org)
Mining How-To (https://www.biblepay-central.org/en/mining-how-to/)
|
|
|
|
togoshigekata
|
|
March 16, 2019, 08:45:17 PM
Last edit: March 17, 2019, 02:40:23 PM by togoshigekata |
|
Im not sure if the information in this link is still true, but inblue tested it back in September 2017 http://wiki.biblepay.org/Multiple_InstancesId rather everyone know about it, than just a few |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
March 16, 2019, 08:52:17 PM |
|
Yes, this is exactly right, BiblePay Evolution is going to be our next version, and it includes all the features of Dash Evolution (deterministic sanctuaries, chainlocks, non-financial transactions, atomic trade and lightning support, daaps, decentralized api, segwit, all the new DIPS, all the latest bitcoin commits for security, all the stuff that happened over the last year in Dash, the Depends system for devs, c++14 source code, new compiler support, easier building, etc) lots of good things to be a base from. And we do whats called a "re-base", meaning we merge our biblepay code into Evolution, and offer a new release. This will be in testnet in 5-6 days. I don't anticipate a huge change or learning curve or problems in test, as Ive confirmed we have 95% compatibility now. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
March 16, 2019, 08:55:58 PM |
|
I never saw this document, and I think what I want to do now is have someone test this publically here, and tell me if there really is any multiwallet exploit Now, and let us fix our hash algo if there is before we reopen the exchanges. I want progress halted until I know the truth, and will not re-open on the exchanges until we work through this together! There should be NO EXPLOITS IN OUR PRODUCTION ENVIRONMENT FOR USERS WHO ATTEMPT TO STEAL COINS THROUGH SYSTEM CONFIGURATIONS!
|
|
|
|
Cryptoalt1990
Newbie
Offline
Activity: 48
Merit: 0
|
|
March 16, 2019, 09:18:23 PM |
|
I never saw this document, and I think what I want to do now is have someone test this publically here, and tell me if there really is any multiwallet exploit Now, and let us fix our hash algo if there is before we reopen the exchanges. I want progress halted until I know the truth, and will not re-open on the exchanges until we work through this together! There should be NO EXPLOITS IN OUR PRODUCTION ENVIRONMENT FOR USERS WHO ATTEMPT TO STEAL COINS THROUGH SYSTEM CONFIGURATIONS!
You probably forgot that https://imgur.com/cpYrhoL |
|
|
|
|
thesnat21
Jr. Member
Offline
Activity: 490
Merit: 4
|
|
March 16, 2019, 09:24:12 PM |
|
I never saw this document, and I think what I want to do now is have someone test this publically here, and tell me if there really is any multiwallet exploit Now, and let us fix our hash algo if there is before we reopen the exchanges. I want progress halted until I know the truth, and will not re-open on the exchanges until we work through this together! There should be NO EXPLOITS IN OUR PRODUCTION ENVIRONMENT FOR USERS WHO ATTEMPT TO STEAL COINS THROUGH SYSTEM CONFIGURATIONS!
I wouldn't consider this an exploit, seems more like it's helping the algorithm to work more efficiently? The overall gains are marginal. |
|
|
|
|
capulo
Newbie
Offline
Activity: 491
Merit: 0
|
|
March 16, 2019, 11:24:46 PM |
|
from pool: one limit is 40k and then when you click confrim in email: This withdrawal amount exceeds BiblePay's hot wallet limit; please withdraw less than 1001 bbp. and last: Sorry, a user has recently withdrawn a large sum of BBP. Please wait 120 seconds and try again. large=1000  increase limits, i dont want to do 120 withdrawals in 2 min intervals |
|
|
|
|
secoccular
Jr. Member
Offline
Activity: 226
Merit: 2
|
|
March 17, 2019, 12:13:15 AM |
|
I don't see the error in what Dash announced. Their model seems totally different than BBPs. They are allowing Dash payments to be sent directly to people in need. It's decentralized because there isn't a middle man. It's pretty innovative, as they've married teaching and using crypto with the charity work. So it's giving to people and encouraging their adoption of it at the same time. Smart. Maybe BBP can do something similar with debit cards? I'm not sure how they could publish accountability before the feature's launch? Anyway, the models are so different. BBP takes rewards and distributes some of them to charity. Dash is allowing you or me to send payments directly as charity. How could they be accountable, when Dash isn't holding anything centrally? What I don't get is, in a country where children only have 1-2 meals a day, how is it everyone has a phone to take Dash? |
|
|
|
|
eyedoctrader1
Newbie
Offline
Activity: 6
Merit: 0
|
|
March 17, 2019, 02:53:17 AM |
|
Hello fellow miners. I need some help getting my wallet to go into syncing mode. After the past week with all the changes to the wallet I discovered that I could not get my wallet to connect to the network. I heard about adding "minersleep=0" to biblepay.conf file which I added. I also increased my genproclimit up to the number of cores of my Xeon processor (4). I upgraded to wallet version 1.2.0.1. When I run the wallet it opens up showing it's behind by 9 days and then just sits there and says no block source available for hours. It never connects to the network to perform the final syncing. Also, I cannot run my masternode either while my wallet is in this non-operational state. Can anyone tell me what changes I need to make to either biblepay.conf file or deletions to files in the biblepaycore directory that will reinstate the syncing process?
Here's a copy of my current biblepay.conf file:
addnode=node.biblepay.org
addnode=biblepay.inspect.network
#tithe=1
gen=1
genproclimit=4
minersleep=0
poolport=80
pool=https://pool.biblepay.org
workerid=eyedoctrader7_3
Thanks in advance to anyone who can help me get back online!
|
|
|
|
|
dave_bbp
Jr. Member
Offline
Activity: 405
Merit: 3
|
|
March 17, 2019, 07:41:34 AM |
|
Hello fellow miners. I need some help getting my wallet to go into syncing mode. After the past week with all the changes to the wallet I discovered that I could not get my wallet to connect to the network. I heard about adding "minersleep=0" to biblepay.conf file which I added. I also increased my genproclimit up to the number of cores of my Xeon processor (4). I upgraded to wallet version 1.2.0.1. When I run the wallet it opens up showing it's behind by 9 days and then just sits there and says no block source available for hours. It never connects to the network to perform the final syncing. Also, I cannot run my masternode either while my wallet is in this non-operational state. Can anyone tell me what changes I need to make to either biblepay.conf file or deletions to files in the biblepaycore directory that will reinstate the syncing process?
Here's a copy of my current biblepay.conf file:
addnode=node.biblepay.org
addnode=biblepay.inspect.network
#tithe=1
gen=1
genproclimit=4
minersleep=0
poolport=80
pool=https://pool.biblepay.org
workerid=eyedoctrader7_3
Thanks in advance to anyone who can help me get back online!
If you are already on 1.2.0.1 wallets then it should be pretty simple to get you back on track. Close your wallets and first of all remove the "poolport" line from the config, since this is wrong for connecting via http s. Then on Linux do the following: cd ~/.biblepaycore
rm -rf banlist.dat blocks/ chainstate/ database/ *.log fee_estimates.dat governance.dat mncache.dat mnpayments.dat netfulfilled.dat SAN/ peers.dat .lock .cookie (On Windows simply paste "%appdata%/biblepaycore" in the explorer and delete everything in there except for "backups", "wallet.dat" and both configs (bbp and mn). Then restart the wallet and let it sync from scratch. As I've written yesterday, this should be pretty fast right now. Check if you are on the correct chain with getblockhash 107525
c6622f1ea9417e463925207ff578f1f697ee1209651e3890b23e2d45dfdd7bb7
Good luck! |
|
|
|
|
dave_bbp
Jr. Member
Offline
Activity: 405
Merit: 3
|
|
March 17, 2019, 07:51:28 AM |
|
I never saw this document, and I think what I want to do now is have someone test this publically here, and tell me if there really is any multiwallet exploit Now, and let us fix our hash algo if there is before we reopen the exchanges. I want progress halted until I know the truth, and will not re-open on the exchanges until we work through this together! There should be NO EXPLOITS IN OUR PRODUCTION ENVIRONMENT FOR USERS WHO ATTEMPT TO STEAL COINS THROUGH SYSTEM CONFIGURATIONS!
I did a short (quick and dirty) test yesterday on the main pool with 2 identical machines (dual L5640 each). Machine A with 1 wallet (nproclimit=24) and machine B with 12 wallets (nproclimit=2). It came down to this: A: wallet-hps: approx. 5000-5500; pool: 100-120 shares, HPS2 120-150k B: wallet-hps: approx. 500 each; pool: 8-12 shares each, HPS2 7-14k each. It's not easy to say, because the pool is wildly fluctuating in its hashrate display, but I think the advantage of running multiple wallets was (at least in this case) maybe 10-15 %. Not sure if this can be considered an "exploit". Maybe I will test the same on purepool, but as I recall we tested this back in 2017 and on purepool there was no difference/advantage whatsoever ... P.S.: one of my wallets sometime during the night crashed with the following ouput: biblepayd: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed. The debug.log only showed this (but from a different timestamp than the crash): terminate called after throwing an instance of 'std::length_error'
what(): basic_string::_M_create
2019-03-17 00:54:22 CGovernanceManager::UpdateCachesAndClean -- erase obj eda7079b949f1b75d4095d67ce6e30a3ad5f477892abe4017fcb079553f84b07
2019-03-17 00:54:22 CGovernanceManager::UpdateCachesAndClean -- erase obj cab433f02578c62fa70bf82c7e38a601b9d7f28ef4afaf4f0ded8606c7a3b5ac
|
|
|
|
|
capulo
Newbie
Offline
Activity: 491
Merit: 0
|
|
March 17, 2019, 09:56:13 AM
Last edit: March 17, 2019, 11:36:01 AM by capulo |
|
from pool: one limit is 40k and then when you click confrim in email: This withdrawal amount exceeds BiblePay's hot wallet limit; please withdraw less than 1001 bbp. and last: Sorry, a user has recently withdrawn a large sum of BBP. Please wait 120 seconds and try again. large=1000 increase limits, i dont want to do 120 withdrawals in 2 min intervals im wrote to texas ass 100times about that 1000 withdrawals .... his code is very weak.... pool looks like monkey retard face capulo : are you using hundreds threads fake again? no, everything is real and correct, real wallet, real pool, real config... only problem is non linearity of hash2 ... but it is not our problem, miners just adapt to it |
|
|
|
|
capulo
Newbie
Offline
Activity: 491
Merit: 0
|
|
March 17, 2019, 10:56:14 AM |
|
I never saw this document, and I think what I want to do now is have someone test this publically here, and tell me if there really is any multiwallet exploit Now, and let us fix our hash algo if there is before we reopen the exchanges. I want progress halted until I know the truth, and will not re-open on the exchanges until we work through this together! There should be NO EXPLOITS IN OUR PRODUCTION ENVIRONMENT FOR USERS WHO ATTEMPT TO STEAL COINS THROUGH SYSTEM CONFIGURATIONS!
I did a short (quick and dirty) test yesterday on the main pool with 2 identical machines (dual L5640 each). Machine A with 1 wallet (nproclimit=24) and machine B with 12 wallets (nproclimit=2). It came down to this: A: wallet-hps: approx. 5000-5500; pool: 100-120 shares, HPS2 120-150k B: wallet-hps: approx. 500 each; pool: 8-12 shares each, HPS2 7-14k each. It's not easy to say, because the pool is wildly fluctuating in its hashrate display, but I think the advantage of running multiple wallets was (at least in this case) maybe 10-15 %. Not sure if this can be considered an "exploit". Maybe I will test the same on purepool, but as I recall we tested this back in 2017 and on purepool there was no difference/advantage whatsoever ... P.S.: one of my wallets sometime during the night crashed with the following ouput: biblepayd: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed. The debug.log only showed this (but from a different timestamp than the crash): terminate called after throwing an instance of 'std::length_error'
what(): basic_string::_M_create
2019-03-17 00:54:22 CGovernanceManager::UpdateCachesAndClean -- erase obj eda7079b949f1b75d4095d67ce6e30a3ad5f477892abe4017fcb079553f84b07
2019-03-17 00:54:22 CGovernanceManager::UpdateCachesAndClean -- erase obj cab433f02578c62fa70bf82c7e38a601b9d7f28ef4afaf4f0ded8606c7a3b5ac
you are not right, difference is much much more than 10-15%, at least 500%, just not adjusting config, run more times same as single. so forgot about # cpu, put nproclimit 20+ everywhere but this is not bug, it is pool feature to 'help poor miners' boosting their hash power arificialy (hash2) |
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
March 17, 2019, 01:45:17 PM |
|
I never saw this document, and I think what I want to do now is have someone test this publically here, and tell me if there really is any multiwallet exploit Now, and let us fix our hash algo if there is before we reopen the exchanges. I want progress halted until I know the truth, and will not re-open on the exchanges until we work through this together! There should be NO EXPLOITS IN OUR PRODUCTION ENVIRONMENT FOR USERS WHO ATTEMPT TO STEAL COINS THROUGH SYSTEM CONFIGURATIONS!
You probably forgot that  Well, sort of, it was back when I only had post 115 lol, and did forget we made Inblues results into a wiki page at the time yes, but, in addition, I remember we had 12 versions of POBH, and this testing was done during the 2nd or 3rd iteration, Inblue ran those tests, and we specifically addressed those exploits in later versions of POBH - so after time, I believed there was no longer a multi-wallet exploit, and forgot about the whole original situation. So let's dig this back up and see how this fits in today. |
|
|
|
|
