Really nice day for BBP. Huge dump, c-cex almost closed, broken wallet and southxchange bbp wallet offline. What is coming next for BBP?  I would expect all the exchanges to have issues before this is fixed. |
|
|
|
almost 10mil dumped on c-cex   look at the price action did somebody call it quits with bbp ? Looks like it.. and/or trying to cash out while they can. Could be monthly superblock sale as well? dunno for sure. |
|
|
|
|
Great day to be MIP lol
Of the last 151 blocks:
top 5 winners:
CPID: 96892ec0fc8a2710fa84f26c9c84cd3e 48 Blocks
CPID: 6f10570756afd25e02ca7d0ca6bf1a44 18 Blocks
CPID: 684b644e09134455f34639d65bea3851 10 Blocks
CPID: fa5062d1c29baf2e298b674f40ee59b7 5 Blocks
CPID: 4928c2303e4e4ff44eb031b5a95403b3 4 Blocks
24 blocks to "unknown" / no CPID
|
|
|
|
|
We're experiencing rollbacks....
I've been tallying the "you got a block" alerts.. I had one for 49345, and 49348
my client is showing it JUST reached a height of 49345, again..
it seems like there are many mini-forks going on..
This could explain all the client crashes..
edit:
I get there were issues the last 2 months with this, but I don't recall this level of chaos happening.. is it more people, or is something different this time?
|
|
|
|
Just tried starting POW mining on another linux machine, now there is an additional error block constantly occuring: 2018-05-29 16:45:06
ProcessBlockFound::Generated 531.66911489
2018-05-29 16:45:06 CPID is not in prior superblock. Contextual check block failed. CPID db10b6e68bce4cf573a2937ddd7f4d10, Payments: 0.000000 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-05-29 16:45:06 ERROR: ProcessBlockFound -- ProcessNewBlock() failed, block not accepted
2018-05-29 16:45:06 CPID is not in prior superblock. Contextual check block failed. CPID db10b6e68bce4cf573a2937ddd7f4d10, Payments: 0.000000 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-05-29 16:45:06 ERROR: ProcessBlockFound -- ProcessNewBlock() failed, block not accepted
2018-05-29 16:45:06 CPID is not in prior superblock. Contextual check block failed. CPID db10b6e68bce4cf573a2937ddd7f4d10, Payments: 0.000000 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-05-29 16:45:06 ERROR: ProcessBlockFound -- ProcessNewBlock() failed, block not accepted
2018-05-29 16:45:06 CPID is not in prior superblock. Contextual check block failed. CPID db10b6e68bce4cf573a2937ddd7f4d10, Payments: 0.000000 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-05-29 16:45:06 ERROR: ProcessBlockFound -- ProcessNewBlock() failed, block not accepted
While the error itself seems to be normal, the rate with which it occurs surely isn't (maybe two dozen of these per second...).  I honestly wonder who is mining the blocks right now, because somehow the pools (or at least the main pool) don't seem to have gotten a single paid block since 49200.. They are going to folks that are heat mining, but only to folks after 15min has elapsed since the last block was generated. 49299 : 96892ec0fc8a2710fa84f26c9c84cd3e
49300 : fa5062d1c29baf2e298b674f40ee59b7
49301 : fa5062d1c29baf2e298b674f40ee59b7
49302 : 96892ec0fc8a2710fa84f26c9c84cd3e
49303 : 684b644e09134455f34639d65bea3851
49304 : 684b644e09134455f34639d65bea3851
49305 : 96892ec0fc8a2710fa84f26c9c84cd3e
49306 : 4ccf98820bb7e49687830de075251942
49307 : 4ccf98820bb7e49687830de075251942
49308 : 96892ec0fc8a2710fa84f26c9c84cd3e
49309 :
49310 :
49311 : 96892ec0fc8a2710fa84f26c9c84cd3e
49312 : 4928c2303e4e4ff44eb031b5a95403b3
49313 : 4928c2303e4e4ff44eb031b5a95403b3
49314 : 96892ec0fc8a2710fa84f26c9c84cd3e
49315 : 3f78732b8867b33a2b34197cab50f4f2
49316 : 3f78732b8867b33a2b34197cab50f4f2
49317 : 96892ec0fc8a2710fa84f26c9c84cd3e
49318 :
49319 :
49320 : 96892ec0fc8a2710fa84f26c9c84cd3e
49321 :
49322 :
49323 : 96892ec0fc8a2710fa84f26c9c84cd3e
49324 :
49325 :
49326 : 96892ec0fc8a2710fa84f26c9c84cd3e
49327 : 684b644e09134455f34639d65bea3851
49328 : 684b644e09134455f34639d65bea3851
49329 : 96892ec0fc8a2710fa84f26c9c84cd3e
49330 : 81a9edf3cda71577fa658525188b5982
49331 : 81a9edf3cda71577fa658525188b5982
49332 : 96892ec0fc8a2710fa84f26c9c84cd3e
49333 : 4928c2303e4e4ff44eb031b5a95403b3
49334 : 4928c2303e4e4ff44eb031b5a95403b3
49335 : 96892ec0fc8a2710fa84f26c9c84cd3e
49336 : 684b644e09134455f34639d65bea3851
49337 : 684b644e09134455f34639d65bea3851
49338 : 96892ec0fc8a2710fa84f26c9c84cd3e
What I find interesting is the blocks with no CPID, these folks would not be able to mine generally.. edit: also since cpid's are allowed to double-up mine.. this puts us at risk of a double-spend with less effort, so keep miners running ... |
|
|
|
Too many bugs after the Superblock ..
Hope Rob can fix it A.S.A.P. , and it should make other way for superblock payment to prevent these bugs occurs.
Rob commented a while ago about knowing what went wrong, but not wanting to force another mandatory update prior to the June one. Hopefully the fix is in place before the next monthly block. |
|
|
|
Dang thanks for the notice on the debug.log... 5k on my linux machine So far I have watched as 3 more blocks I "mined" were stripped away heh.. They all got 1 confirmation, then disappeared after the next block was mined. this is going to be a fun day  edit: not that I expected anywhere near that many to be mined.. but this is the first time I believe I've seen mined blocks orphaned. edit2: Interesting... many blocks being mined right after the other by a single cpid... This would explain some of it.. 49312 was one I lost, as well as 49315 and 49327 49312 : 4928c2303e4e4ff44eb031b5a95403b3 49313 : 4928c2303e4e4ff44eb031b5a95403b3 49314 : 96892ec0fc8a2710fa84f26c9c84cd3e 49315 : 3f78732b8867b33a2b34197cab50f4f2 49316 : 3f78732b8867b33a2b34197cab50f4f2 49317 : 96892ec0fc8a2710fa84f26c9c84cd3e 49318 : 49319 : 49320 : 96892ec0fc8a2710fa84f26c9c84cd3e 49321 : 49322 : 49323 : 96892ec0fc8a2710fa84f26c9c84cd3e 49324 : 49325 : 49326 : 96892ec0fc8a2710fa84f26c9c84cd3e 49327 : 684b644e09134455f34639d65bea3851 49328 : 684b644e09134455f34639d65bea3851 |
|
|
|
|
I had a few wallet crashes this morning as well.
I've mined a block or two this morning, get at least 1 confirm only to have them yanked away... must be tough competition and a lot of orphans being generated.
At this rate it will be another 24hr till the next superblock (due to 15min wait till mining opens)
|
|
|
|
Hello,
I am having this error. Anyone can help?
"poolinfo1": "Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; ",
"poolinfo2": "Submitting Solution 05-27-2018 15:15:17; Submitting Solution 05-27-2018 15:15:27; Submitting Solution 05-27-2018 15:15:19; Failed to sign CPID Signature (Address does not refer to key); Submitting Solution 05-27-2018 15:15:18; Failed to sign CPID Signature (Address does not refer to key); Submitting Solution 05-27-2018 15:15:24; ",
This is a fresh install. I followed the guide strictly.
The wallet is generated automatically and sent 2 bbp to it a few hours ago.
Unable to sign CPID is either your wallet is locked (and you didn't use the PODCUNLOCK) option, or your cpid has not been associated to the wallet (Being that new) run "exec getboincinfo" from the debug window and paste the results here How can I use PODCUNLOCK ? what's the command? "Command": "getboincinfo", "CPID": "", "Address": "", "CPIDS": "", "CPID-Age (hours)": 424288, "NextSuperblockHeight": 49200, "NextSuperblockBudget": 15375000, "Total Payments (One Day)": 0, "Total Payments (One Week)": 0, "Total Budget (One Day)": 1161612, "Total Budget (One Week)": 8131284, "Superblock Count (One Week)": 8, "Superblock Hit Count (One Week)": 8, "Superblock List": "48995,48790,48585,48380,48175,47970,47765,47560", "Last Superblock Height": 48995, "Last Superblock Budget": 1161612, "Last Superblock Payment": -2, "Magnitude (One-Day)": 0, "Magnitude (One-Week)": 0 You don't have cpid/address assigned you need to associate your rosetta account with bbp look for that part in the mining guide podc unlock is " -setpodcunlockpassword" param |
|
|
|
Hello,
I am having this error. Anyone can help?
"poolinfo1": "Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; ",
"poolinfo2": "Submitting Solution 05-27-2018 15:15:17; Submitting Solution 05-27-2018 15:15:27; Submitting Solution 05-27-2018 15:15:19; Failed to sign CPID Signature (Address does not refer to key); Submitting Solution 05-27-2018 15:15:18; Failed to sign CPID Signature (Address does not refer to key); Submitting Solution 05-27-2018 15:15:24; ",
This is a fresh install. I followed the guide strictly.
The wallet is generated automatically and sent 2 bbp to it a few hours ago.
Unable to sign CPID is either your wallet is locked (and you didn't use the PODCUNLOCK) option, or your cpid has not been associated to the wallet (Being that new) run "exec getboincinfo" from the debug window and paste the results here |
|
|
|
I understand the sporks are there, and you hold the keys to them all.
And this specific situation is a bit of a mess..
My concern here is, how was the decision to fade WCG rac made? Was there any discussion with others, or was it a choice you made?
I think it's important to share this thought process with the group.
If you don't like the fact that I started this coin and we dont have more than one lead dev yet, then please start your own coin. EDIT: Its not a bit of a mess. We are decentralized, and we are actually working on a plan behind the scenes to address business continuity and a trust. I'm working with the non-argumentative core group. I dont know exactly when I can start this project, but I will make a wiki page outlining the general idea of this trust; and it would address the following concerns: - The ability for biblepay.org to have an institutional gdax/coinbase account, with several appointed individuals holding multisig keys to perform liquidation of assets for cameroon, bloom or compassion or a charity partner monthly - Business continuity in the case of a trust member leaving - More than one lead dev holding spork keys - requiring all lead devs to sign the spork for it to execute - Merging non compassion charity expenses into accountability.biblepay.org totals - An SQL backup for tax purposes - An annual tax report made public, and this also holds harmless the directors of the trust (from tax consequences and liabilities) The primary focus here is to provide a mechanism for biblepay to appoint trustees or directors to the trust and cross train so that when one individual leaves the trust we have continuity. We are scheduling time to have a call with our advisor within 30 days and I believe we will set this up in a basic form before the end of this year. ... I'm still trying to HELP alleviate fears that are being expressed. Thank you for actually answering the question this time. I don't understand the purpose of deleting my post, but quoting it in reply.. this seems strange to me. EDIT: The mess being WCG suddenly changing policies not anything bbp related, not everything said is an attack on you/bbp... All I would like to see is some discussion going on, I was hoping there was some behind the scenes you could fill us in on.... Also, Masternodes have the ability to vote on SPORKS and it would be a clean way to gain a true consensus. Odd's are they wouldn't vote against you Rob, and it is in line with the DASH model. so maybe an option to consider in the future? |
|
|
|
OUCH .. Perhaps they would make an exception for humanitarian efforts? lol They seem to be adding things left and right, and several coins that I would be surprised to see they have that much to spend... Can't hurt to ask? |
|
|
|
I think the prayer system is being abused again. The Romans 1:20 verse has been modified and posted.
So I found the tx associated with the prayer via the block explorer, but not sure what a person can do with it from there. I suppose one could track back the addresses until we got to something someone recognized (assuming they didn't use privatepay or something) and then direct message the sender and have a "grown-up" conversation. On a larger scale, though, public broadcast ability is always going to be tricky if unmoderated. Even this forum is moderated somewhat. Should we consider introducing a "report" function on prayers that are inappropriate? If so, how do we stop THAT from being abused? It's a difficult situation. The other abuse was removed fairly quickly.. I suspect Rob has a way to push a prayer deletion. |
|
|
|
rosetta@home update: We're out of Android tasks! good job team |
|
|
|
interesting putting names to faces! lol Nice show guys |
|
|
|
Licht:
While I have your attention, can you increase your apache header size... I'm still getting occasional 400 errors when submitting shares.
Funny timing, I just increased it 10 minutes ago. Is your our example new or older then 10 minutes? Lol Older.. i can run another test for a while though (or your logs can tell you) |
|
|
|
Hey guys, questions How to setup config on multiple computers correctly?
On Main computer same wallet and CPID
addnode=node.biblepay.org
gen=1
genproclimit=-1
pool=https://pool.purepool.org
workerid=yQwwRT4NtwBw442eyz37NYTYzyfwxiHLk1
On second computer same wallet and CPID
addnode=node.biblepay.org
gen=1
genproclimit=-1
utxooverride=-1
pool=https://pool.purepool.org
workerid=aQhhs4hh34sdsds235455675gccsdsd
vs having the same worker id on both computers
Set the Core Limit for mining (careful too high and this can make the rest of your pc crawl) genproclimit=3 also don't forget this if your machine is ONLY POBH mining. minersleep=0 Error code: on pool.purepool.org
Invalid_CPID Default 4
Illegal_CPID Default 16
Error code: on pool.biblepay.org
CPID_SIGNATURE_INVALID
CPID_HAS_NO_MAGNITUDE
I am getting the CPID, Magnitude, Task Weight, UTXO Weight with values.
Also getmininginfo and exec getboincinfo on console shows up good.
Note: I believe these questions can also help out other people.
Would be extremely helpful if someone can help me.
Occasional errors are ok and just noise, that is showing a count of total errors (not including the valid submissions) if you see your "share count" going up you should be ok. |
|
|
|
Licht: While I have your attention, can you increase your apache header size... I'm still getting occasional 400 errors when submitting shares. <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Size of a request header field exceeds server limit.</p>
<hr>
<address>Apache/2.4.18 (Ubuntu) Server at www.purepool.org Port 80</address>
</body></html>
|
|
|
|
The problem with OpenSSL sounds reasonable. I also just realized that my test build that worked didn't used ubuntu 18.04 but ubuntu 16.04. I'm running a new build right now, to test if it will fail again.
@all users:
Is there anybody who is using BiblePay with Ubuntu 18.04 right now? If so, have you downgraded openssl? Or solved it any other way?
basically in the src/wallet/crypter.cpp 2 functions, BibleEncrypt and BibleDecrypt comment: EVP_CIPHER_CTX ctx; uncomment: EVP_CIPHER_CTX *ctx = EVP_CIPHER_CTX_new(); change the lines in the function remove the & from &ctx I don't belive anything in here has changed the last few commits, but compare just in case. open file: src/wallet/crypter.cpp change bool BibleEncrypt(std::vector<unsigned char> vchPlaintext, std::vector<unsigned char> &vchCiphertext)
{
if (!fKeySetBiblePay) LoadBibleKey("biblepay","eb5a781ea9da2ef36");
int nLen = vchPlaintext.size();
int nCLen = nLen + AES_BLOCK_SIZE, nFLen = 0;
vchCiphertext = std::vector<unsigned char> (nCLen);
EVP_CIPHER_CTX ctx;
// EVP_CIPHER_CTX *ctx = EVP_CIPHER_CTX_new();
bool fOk = true;
EVP_CIPHER_CTX_init(&ctx);
if (fOk) fOk = EVP_EncryptInit_ex(&ctx, EVP_aes_256_cbc(), NULL, chKeyBiblePay, chIVBiblePay);
if (fOk) fOk = EVP_EncryptUpdate(&ctx, &vchCiphertext[0], &nCLen, &vchPlaintext[0], nLen);
if (fOk) fOk = EVP_EncryptFinal_ex(&ctx, (&vchCiphertext[0])+nCLen, &nFLen);
EVP_CIPHER_CTX_cleanup(&ctx);
if (!fOk) return false;
vchCiphertext.resize(nCLen + nFLen);
return true;
}
bool BibleDecrypt(const std::vector<unsigned char>& vchCiphertext,std::vector<unsigned char>& vchPlaintext)
{
LoadBibleKey("biblepay","eb5a781ea9da2ef36");
int nLen = vchCiphertext.size();
int nPLen = nLen, nFLen = 0;
EVP_CIPHER_CTX ctx;
// EVP_CIPHER_CTX *ctx = EVP_CIPHER_CTX_new();
bool fOk = true;
EVP_CIPHER_CTX_init(&ctx);
if (fOk) fOk = EVP_DecryptInit_ex(&ctx, EVP_aes_256_cbc(), NULL, chKeyBiblePay, chIVBiblePay);
if (fOk) fOk = EVP_DecryptUpdate(&ctx, &vchPlaintext[0], &nPLen, &vchCiphertext[0], nLen);
if (fOk) fOk = EVP_DecryptFinal_ex(&ctx, (&vchPlaintext[0])+nPLen, &nFLen);
EVP_CIPHER_CTX_cleanup(&ctx);
if (!fOk) return false;
vchPlaintext.resize(nPLen + nFLen);
return true;
} to: bool BibleEncrypt(std::vector<unsigned char> vchPlaintext, std::vector<unsigned char> &vchCiphertext)
{
if (!fKeySetBiblePay) LoadBibleKey("biblepay","eb5a781ea9da2ef36");
int nLen = vchPlaintext.size();
int nCLen = nLen + AES_BLOCK_SIZE, nFLen = 0;
vchCiphertext = std::vector<unsigned char> (nCLen);
// EVP_CIPHER_CTX ctx;
EVP_CIPHER_CTX *ctx = EVP_CIPHER_CTX_new();
bool fOk = true;
EVP_CIPHER_CTX_init(ctx);
if (fOk) fOk = EVP_EncryptInit_ex(ctx, EVP_aes_256_cbc(), NULL, chKeyBiblePay, chIVBiblePay);
if (fOk) fOk = EVP_EncryptUpdate(ctx, &vchCiphertext[0], &nCLen, &vchPlaintext[0], nLen);
if (fOk) fOk = EVP_EncryptFinal_ex(ctx, (&vchCiphertext[0])+nCLen, &nFLen);
EVP_CIPHER_CTX_cleanup(ctx);
if (!fOk) return false;
vchCiphertext.resize(nCLen + nFLen);
return true;
}
bool BibleDecrypt(const std::vector<unsigned char>& vchCiphertext,std::vector<unsigned char>& vchPlaintext)
{
LoadBibleKey("biblepay","eb5a781ea9da2ef36");
int nLen = vchCiphertext.size();
int nPLen = nLen, nFLen = 0;
//EVP_CIPHER_CTX ctx;
EVP_CIPHER_CTX *ctx = EVP_CIPHER_CTX_new();
bool fOk = true;
EVP_CIPHER_CTX_init(ctx);
if (fOk) fOk = EVP_DecryptInit_ex(ctx, EVP_aes_256_cbc(), NULL, chKeyBiblePay, chIVBiblePay);
if (fOk) fOk = EVP_DecryptUpdate(ctx, &vchPlaintext[0], &nPLen, &vchCiphertext[0], nLen);
if (fOk) fOk = EVP_DecryptFinal_ex(ctx, (&vchPlaintext[0])+nPLen, &nFLen);
EVP_CIPHER_CTX_cleanup(ctx);
if (!fOk) return false;
vchPlaintext.resize(nPLen + nFLen);
return true;
}
|
|
|
|
|
Show Posts
