Author

Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 841. (Read 243376 times)

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
'Rob'

nephews came over this weekend. they saw on my computer the pool page and pictures of kids. i explained to them what the project was about..trying to explain how bitcoins / crypto are 'funny fake money' and have no real value other than what people believe. (yeah, you can imagine how far i got with that economics lesson)

anyway, they asked about the kids and i said that every time the computer made some funny money it helps those kids. they got excited about that

so, im calling a truce (if there ever was a 'war'). the project may do some good in the short term. ive given the warnings and its fallen on deaf ears. the majority want to make money money money

mid term, 'Rob', crytpos are causing hyperinflation of the real economies. the poor and working class will be decimated if they dont get into it. that is the whole devilish design of this and the road forward to 666. 'cant buy and sell without blockchain' will be reality very soon.

you should know that you are a part of this bigger plan even if you dont intend it. dont be blinded by money, ego, profit. try to make the project a REAL sanctuary for people

Dont be misguided.  I didnt create BiblePay to get rich.  I created it primarily to be a better alternative to a greed based inefficient system.  POW miners waste heat because they are all solving a single blockhash and clustering blackboxes in greedy rat race.  We require full nodes, providing POSE (proof of service) and help orphans at the same time, and we are more efficient because you cant run the algo on an ASIC.  Once people say "its better over here", then they may also financially benefit over the long term.  The deflationary aspect should bear out to be true over the long term, for each dollar invested for the orphans.  The highest benefit we provide is the pass through to compassion.  If we end up in the top 100, then we will be helping thousands of orphans per month.  That is the True end goal.

You are definitely misguided on the economy.  The central banks print money to fund wars and to get themselves out of hot water, as they have bills due, budgets to pay, and since they have the authority to print as much as they want, they never have to ask the general public if its OK.  We otoh, are confined to a budget and to a deflating reward.  We actually cant print money from thin air.  That means we are part of the solution and not the problem.

Finally I really am a true Christian.  I would never allow anything related to the mark of the beast in the code.

Ill be creating a topic soon on spreading the Gospel, as this community could really make a difference if we can quantify that part of Christianity.

Geeks spreading the gospel through the blockchain.


newbie
Activity: 42
Merit: 0
'Rob'

nephews came over this weekend. they saw on my computer the pool page and pictures of kids. i explained to them what the project was about..trying to explain how bitcoins / crypto are 'funny fake money' and have no real value other than what people believe. (yeah, you can imagine how far i got with that economics lesson)

anyway, they asked about the kids and i said that every time the computer made some funny money it helps those kids. they got excited about that

so, im calling a truce (if there ever was a 'war'). the project may do some good in the short term. ive given the warnings and its fallen on deaf ears. the majority want to make money money money

mid term, 'Rob', crytpos are causing hyperinflation of the real economies. the poor and working class will be decimated if they dont get into it. that is the whole devilish design of this and the road forward to 666. 'cant buy and sell without blockchain' will be reality very soon.

you should know that you are a part of this bigger plan even if you dont intend it. dont be blinded by money, ego, profit. try to make the project a REAL sanctuary for people





full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I just googled it and I was wondering if it could be that instead since 17.10 is using OpenSSL 1.1?

Quote
One of the primary differences between master (OpenSSL 1.1.0) and the 1.0.2 version is that many types have been made opaque, i.e. applications are no longer allowed to look inside the internals of the structures. The biggest impact on applications is that:

You cannot instantiate these structures directly on the stack. So instead of:

Code:
EVP_CIPHER_CTX ctx;

you must instead do:

Code:
EVP_CIPHER_CTX *ctx = EVP_CIPHER_CTX_new();
....
EVP_CIPHER_CTX_free(ctx);

You must only use the provided accessor functions to access the internals of the structure.

You have to use the version of OpenSSL in the build instructions.



I'm not sure if this will help you get on the compatible OpenSSL version, but I just checked in 1058c if you want to grab it.  In this version we log the openSSL version in the initialization sequence of the log, I added the OpenSSL field to the Gui in Tools | Information, and I added an rpc command: exec getversion, that also shows the SSL version.

Im using openssl 1.0.1t on my machines. I think the primary issue is staying between 101f and 101z for this software, as moving to 102 breaks compatibility.  Please try that.

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I just googled it and I was wondering if it could be that instead since 17.10 is using OpenSSL 1.1?

Quote
One of the primary differences between master (OpenSSL 1.1.0) and the 1.0.2 version is that many types have been made opaque, i.e. applications are no longer allowed to look inside the internals of the structures. The biggest impact on applications is that:

You cannot instantiate these structures directly on the stack. So instead of:

Code:
EVP_CIPHER_CTX ctx;

you must instead do:

Code:
EVP_CIPHER_CTX *ctx = EVP_CIPHER_CTX_new();
....
EVP_CIPHER_CTX_free(ctx);

You must only use the provided accessor functions to access the internals of the structure.

You have to use the version of OpenSSL in the build instructions.




I believe its 101k.  You could get away with 101g, h, i, j also.

I think weve just discovered the whole problem.  Its not ubuntu 64, its Open SSL and its relationship to the biblehash it creates.

Alex, I think your other machines are using a certain version of openssl that is producing slightly different biblehashes in some cases.

Can you please try pulling 101k and building on one specific machine and restarting in testnet?  See if that fixes the blockheader bug.

In the mean time, Ill add the OPENSSL Version to the core, and once we know if that fixes it, Ill add enforcement into the version message etc.

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I just googled it and I was wondering if it could be that instead since 17.10 is using OpenSSL 1.1?

Quote
One of the primary differences between master (OpenSSL 1.1.0) and the 1.0.2 version is that many types have been made opaque, i.e. applications are no longer allowed to look inside the internals of the structures. The biggest impact on applications is that:

You cannot instantiate these structures directly on the stack. So instead of:

Code:
EVP_CIPHER_CTX ctx;

you must instead do:

Code:
EVP_CIPHER_CTX *ctx = EVP_CIPHER_CTX_new();
....
EVP_CIPHER_CTX_free(ctx);

You must only use the provided accessor functions to access the internals of the structure.

You have to use the version of OpenSSL in the build instructions.

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Tried to compile the new version and this is what I'm getting:

wallet/crypter.cpp: In function ‘bool BibleEncrypt(std::vector, std::vector&)’:
wallet/crypter.cpp:226:20: error: aggregate ‘EVP_CIPHER_CTX ctx’ has incomplete type and cannot be defined
     EVP_CIPHER_CTX ctx;
                    ^~~
wallet/crypter.cpp: In function ‘bool BibleDecrypt(const std::vector&, std::vector&)’:
wallet/crypter.cpp:244:20: error: aggregate ‘EVP_CIPHER_CTX ctx’ has incomplete type and cannot be defined
     EVP_CIPHER_CTX ctx;

Thats something missing on the ubuntu box, try googling that particular error and it should show a dependency missing most likely.

Could you post the full list of dependencies for Bible?

They are in the github Building Biblepay documents already.

full member
Activity: 396
Merit: 106
Tried to compile the new version and this is what I'm getting:

wallet/crypter.cpp: In function ‘bool BibleEncrypt(std::vector, std::vector&)’:
wallet/crypter.cpp:226:20: error: aggregate ‘EVP_CIPHER_CTX ctx’ has incomplete type and cannot be defined
     EVP_CIPHER_CTX ctx;
                    ^~~
wallet/crypter.cpp: In function ‘bool BibleDecrypt(const std::vector&, std::vector&)’:
wallet/crypter.cpp:244:20: error: aggregate ‘EVP_CIPHER_CTX ctx’ has incomplete type and cannot be defined
     EVP_CIPHER_CTX ctx;

Thats something missing on the ubuntu box, try googling that particular error and it should show a dependency missing most likely.

Could you post the full list of dependencies for Bible?
member
Activity: 98
Merit: 10
I just googled it and I was wondering if it could be that instead since 17.10 is using OpenSSL 1.1?

Quote
One of the primary differences between master (OpenSSL 1.1.0) and the 1.0.2 version is that many types have been made opaque, i.e. applications are no longer allowed to look inside the internals of the structures. The biggest impact on applications is that:

You cannot instantiate these structures directly on the stack. So instead of:

Code:
EVP_CIPHER_CTX ctx;

you must instead do:

Code:
EVP_CIPHER_CTX *ctx = EVP_CIPHER_CTX_new();
....
EVP_CIPHER_CTX_free(ctx);

You must only use the provided accessor functions to access the internals of the structure.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Tried to compile the new version and this is what I'm getting:

wallet/crypter.cpp: In function ‘bool BibleEncrypt(std::vector, std::vector&)’:
wallet/crypter.cpp:226:20: error: aggregate ‘EVP_CIPHER_CTX ctx’ has incomplete type and cannot be defined
     EVP_CIPHER_CTX ctx;
                    ^~~
wallet/crypter.cpp: In function ‘bool BibleDecrypt(const std::vector&, std::vector&)’:
wallet/crypter.cpp:244:20: error: aggregate ‘EVP_CIPHER_CTX ctx’ has incomplete type and cannot be defined
     EVP_CIPHER_CTX ctx;

Thats something missing on the ubuntu box, try googling that particular error and it should show a dependency missing most likely.
member
Activity: 98
Merit: 10
Tried to compile the new version and this is what I'm getting:

wallet/crypter.cpp: In function ‘bool BibleEncrypt(std::vector, std::vector&)’:
wallet/crypter.cpp:226:20: error: aggregate ‘EVP_CIPHER_CTX ctx’ has incomplete type and cannot be defined
     EVP_CIPHER_CTX ctx;
                    ^~~
wallet/crypter.cpp: In function ‘bool BibleDecrypt(const std::vector&, std::vector&)’:
wallet/crypter.cpp:244:20: error: aggregate ‘EVP_CIPHER_CTX ctx’ has incomplete type and cannot be defined
     EVP_CIPHER_CTX ctx;

PS: Just saw your reply to the hashrate question. Thanks!
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords

One of my nodes is however having messages such as this, I'm not sure if it's the same issue:

2017-11-13 12:55:33 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 38218.000000 pindexPrev b9835678d35862d1cd982eb2bb83368bf64fa2f0b5accb4dc9f6e74191e7f79a
2017-11-13 12:55:33 ERROR: CheckBlockHeader(): proof of work failed
2017-11-13 12:55:33 ERROR: ProcessNewBlock: AcceptBlock FAILED
2017-11-13 12:55:33 ERROR: ProcessBlockFound -- ProcessNewBlock() failed, block not accepted

I was also wondering if it was normal for my hashrate to be 10k on testnet vs 250k on mainnet.

--

Finally (changing the subject totally), I tried to compile biblepay for Ubuntu 17.10 and I'm getting a compile error:

rpcblockchain.cpp: In function ‘void StartTradingThread()’:
rpcblockchain.cpp:2290:73: error: use of deleted function ‘void boost::cref(const T&&) [with T = int]’
  tradingThreads->create_thread(boost::bind(&TradingThread, boost::cref(0)));

I'm guessing it's a version issue?


My oh my weve got our hands full all of a sudden.  Yes, it looks like all of the checkblockheader errors can be lumped together into the same issue (BibleHash does not meet POW level) for both testnet and mainnet.  Yeah, I see the last night fix did not fix that nuisance.

So let me take a quick attempt at the compilation issue first.  The compilation problem on the ubuntu 17.1 box is due to a new feature for retirement trading.  I just chcked in 1.0.5.8b, could you please see if that compiles on Ubuntu 17.1?

In the mean time, I switched all my linux boxes over to debian, to make it easier to gitian-build biblepay, but Ill provision a new Ubuntu now in order to look at #1.



PS:  I forgot to answer your question about HPS:  Yes, thats normal, f8000 in TestNet is slower than f7000 in mainnet.


hero member
Activity: 714
Merit: 500
@Rob, I just realized that block explorer - http://biblepay.inspect.network/ stopped update on block 16174... I was checking it two days ago but wallet did not update with latest transfer from pool, then I thought it was delay, then I checked again just now and found that latest block is still 16174 which is two days ago.

Thanks, I saw multiple messages from Coinpimp claiming we did that on purpose or something lol, yeah, Happy_Merchant runs it.  I can PM him and see if he wakes up, will do now, Thanks!


No rush actually, I just wanted to inform about the issue only... Coinpimp posted a lot of non-sense, I did not really read through all his messages, haha~~
member
Activity: 98
Merit: 10
@Rob I'm still testing the new version both in testnet and mainnet.

I was wondering if you ever managed to reproduce my issue?
Hi Alex, so the last thing I did was added a patch to check that condition and verified it could mine a block in testnet, and checked in 1058.
Could you please tell me if 1058 has the same problem or something different?  I didnt see any new message after that (that was midnight last night).


Hi Rob, I did post a message this afternoon (for me) but decided to delete it as I wanted to be 100% sure and not waste your time.

--

My nodes on mainnet still sees errors such as this (happened a few seconds ago):

2017-11-13 13:35:06 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 16535.000000 pindexPrev a7ea3485fc32c1b9f9a44ecf1b704f46077c25a76af9a75e299d9878c439eaa0
2017-11-13 13:35:06 ERROR: CheckBlockHeader(): proof of work failed
2017-11-13 13:35:06 Misbehaving: 192.169.156.212:40000 (0 -> 1)
2017-11-13 13:35:06 ERROR: invalid header received 8d11169decf05a59707838c1b9f23310045c817e3ec2eeb549645a3f29144568

I'm still trying to see if I can see one of my updated miners being flagged on mainnet.

Edit: Just saw one of my updated miners being flagged.

--

I also have two nodes on testnet and I saw the exact same message above flagging one node from the other node but only once.

One of my nodes is however having messages such as this, I'm not sure if it's the same issue:

2017-11-13 12:55:33 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 38218.000000 pindexPrev b9835678d35862d1cd982eb2bb83368bf64fa2f0b5accb4dc9f6e74191e7f79a
2017-11-13 12:55:33 ERROR: CheckBlockHeader(): proof of work failed
2017-11-13 12:55:33 ERROR: ProcessNewBlock: AcceptBlock FAILED
2017-11-13 12:55:33 ERROR: ProcessBlockFound -- ProcessNewBlock() failed, block not accepted

I was also wondering if it was normal for my hashrate to be 10k on testnet vs 250k on mainnet.

--

Finally (changing the subject totally), I tried to compile biblepay for Ubuntu 17.10 and I'm getting a compile error:

rpcblockchain.cpp: In function ‘void StartTradingThread()’:
rpcblockchain.cpp:2290:73: error: use of deleted function ‘void boost::cref(const T&&) [with T = int]’
  tradingThreads->create_thread(boost::bind(&TradingThread, boost::cref(0)));

I'm guessing it's a version issue?



full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
@Rob I'm still testing the new version both in testnet and mainnet.

I was wondering if you ever managed to reproduce my issue?
Hi Alex, so the last thing I did was added a patch to check that condition and verified it could mine a block in testnet, and checked in 1058.
Could you please tell me if 1058 has the same problem or something different?  I didnt see any new message after that (that was midnight last night).


As far as reproducing the issue, not exactly.  I was able to confirm the issue was there, because I had it happen, but on my end it only happened twice in the entire 29 meg log, so I havent been able to make it happen quite as easily, which is actually very baffling.  Makes me wonder if its a dependency different causing a math rounding error. 
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords


Thank you. How many machines are mining this? estimate? 

We have about 1015 miners in the pool, we also have another pool (MinersOfMen.com) and some people solo mining, so probably 1300.
You can see the stats here: pool.biblepay.org | About

Welcome Aboard!
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
@Rob I'm still testing the new version both in testnet and mainnet.

I was wondering if you ever managed to reproduce my issue?
Hi Alex, so the last thing I did was added a patch to check that condition and verified it could mine a block in testnet, and checked in 1058.
Could you please tell me if 1058 has the same problem or something different?  I didnt see any new message after that (that was midnight last night).
newbie
Activity: 14
Merit: 0
I'm running Ubuntu 16.04 (64 bits) and I downloaded and compiled the latest version to try with testnet (1.0.5.6)

If I want to run this on linux do I have to compile myself?
Hi there,
I assume you are talking about the wallet and miner?

In all honesty, the easiest way to install on Ubuntu is through the bash script here
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b

1. Download that file and extract it somewhere on your machine.
2. Follow the instructions at that site (listed below)
2a) create an account and a worker name here (pool.biblepay.org)
2b) go to the downloaded directory (where you extracted that file)
2c) sudo chmod +x install_biblepay.sh
2d) ./install_biblepay.sh {number of mining threads} {pool worker name}
#    Eg: ./install_biblepay.sh 8 workername



EDIT: If you want to deploy the GUI after that, navigate in a terminal to the folder
$BP_ROOT/biblepay/src/qt

and type the command
./biblepay-qt

(you may need to restart the bbp service before this, I usually just restart my machine directly)

Thank you. How many machines are mining this? estimate? 
member
Activity: 98
Merit: 10
@Rob I'm still testing the new version both in testnet and mainnet.

I was wondering if you ever managed to reproduce my issue?
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
@Rob, I just realized that block explorer - http://biblepay.inspect.network/ stopped update on block 16174... I was checking it two days ago but wallet did not update with latest transfer from pool, then I thought it was delay, then I checked again just now and found that latest block is still 16174 which is two days ago.

Thanks, I saw multiple messages from Coinpimp claiming we did that on purpose or something lol, yeah, Happy_Merchant runs it.  I can PM him and see if he wakes up, will do now, Thanks!
hero member
Activity: 714
Merit: 500
@Rob, I just realized that block explorer - http://biblepay.inspect.network/ stopped update on block 16174... I was checking it two days ago but wallet did not update with latest transfer from pool, then I thought it was delay, then I checked again just now and found that latest block is still 16174 which is two days ago.
Jump to: