BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[bible_pay]

Pool Fees:   18%

 

i hope that 1 day we hold on  this usury

I'm a little overloaded right now, but here is a quick update:

Im running a database maintenance script, and had to consolidate your balances owed into one more succinct record (in contrast to thousands of "mining_credit" records), this caused the server to think your balances are immature.

All you have to do is subtract the two numbers and you will see the total owed is still the same as before the script was started.


Ill take a look at putting it back to the way it was by tomorrow, but either way it will work itself out within 24 hours.

Next, I have an idea how we can prevent the pool from being a hacking target.

In the Python pool, they require a valid receiving address in order to mine.
I think what we will do in the future is forcefully send your rewards out every time a block is solved - to your address on file.

Give me a couple weeks to look into that feature, it may take a while to get that completely working, but I think that feature will button down the pool.

The 18% fee is just temporary.  Hopefully you realize this is in order to keep the pool running.

[slovakia]

withdraw is temporary closed?

[bible_pay]

withdraw is temporary closed?

Yes.

[bible_pay]

I had around 1,500 BBP and now its all gone with no history of withdrawals (pool.biblepay.org).

where do I see history for withdrawals on the pool?

I have no emails to confirm the withdrawal.

I see no user under your handle name.

[bible_pay]

Withdraw stats are wrong for me also.

I see no user under your handle either.

[bible_pay]

Wow, got a message from a dentist that wants to accept biblepay.  At least one positive thing happened today!  Alright.

[hvdb]

Wow, got a message from a dentist that wants to accept biblepay.  At least one positive thing happened today!  Alright.

behind every cloud the sun is shining.

[togoshigekata]

616westwarmoth had fantastic advice on Backing up your Wallet: https://www.reddit.com/r/BiblePay/comments/7lksp4/backup_walletdat/
please everyone encrypt and backup your wallets, and dont forget the encryption password!

"jaapgvk 3 points 6 hours ago
I'm not sure, but since BBP is partly based on bitcoin, there is a way in which the bitcoin qt-wallet works that doesn't give you 100% certainty that only making a wallet.dat backup once is enough on the long run.

See this explanation:
Preventing and Recovering from Change Address Disasters.
Incorrect use of Bitcoin change addresses account for many cases of loss or theft of funds. Here are some disaster scenarios and ways to avoid them.

1. Backup Failure Alice uses Bitcoin-Qt. Understanding the importance of backups, she created an encrypted wallet backup long ago and stored it in a safe place. After making dozens of transactions with Bitcoin-Qt, Alice’s hard drive crashed.
Alice bought a new hard drive and then re-installed Bitcoin-Qt on it. She then restored her wallet backup. To her horror, Alice discovered the restored wallet was empty.

Explanation: Alice generated enough change addresses to overflow the original pool of 100. On the 100th spending transaction, Bitcoin-Qt moved Alice’s change (which happend to be her entire balance) into an address not in the backup. Restoring the backup only restored empty addresses.

Recovery: Even if a hard drive can’t boot an operating system, individual files can still be recovered. Using data recovery tools, Alice may be able to salvage the Bitcoin-Qt wallet from the faulty hard drive, and with it her lost funds.
Prevention:

Count the number of manually-created addresses and spending transactions since your last backup. If this number is greater than about 80, back up again. Weekly backups might be enough for most users. Set a very high value (e.g., 10,000) for the -keypool option, either as a command line parameter, or in the bitcoin.conf file. Switch to a deterministic wallet.

https://bitzuma.com/posts/five-ways-to-lose-money-with-bitcoin-change-addresses/"

===

jaavpgvk also has fantastic advice! Ive heard about this 100 thing but wasnt sure,
Could your provide any details on this 100 transaction functionality Rob?

Can anyone teach me more about this keypool thing?
Im worried about my private keys rotating/being reset and my backups of my wallet.dat in other locations becoming worthless.
Especially now that I am receiving daily payments from my Sanctuary.

[orbis]

Hi,
can you explain those new columns on leaderboard?
PhysicalMachines       LogicalMachines       ElectricBill

[capulo]

we are not hitting blocks, what can be problem?
last payout was on block 23356 but chain is already 10 blocks ahead, is this due to db maintenance or is there some other serious problem?

to prevent stoling coins, just add feature to autowithdraw once per day - this shoud be enough

ad proposals, could we create proposal for some big exchange entry fee? or for covering losts made by hacker?

[okane818]

Hello Dev Team,

I cannot login at this pool: http://pool2.biblepay.org/ and http://pool.biblepay.org/ yesterday I am logged in, I try to reset my account but it says "Unable to retrieve a user with that username" what happen? my username in pool: okane81

Can you fix this, I have mined balance over in the pool. WTF!

[togoshigekata]

Miner with pool name requiredtruth is seeing a negative balance:
https://www.reddit.com/r/BiblePay/comments/7mxxv7/negative_mature_pool_balance/

[bible_pay]

we are not hitting blocks, what can be problem?
last payout was on block 23356 but chain is already 10 blocks ahead, is this due to db maintenance or is there some other serious problem?

to prevent stoling coins, just add feature to autowithdraw once per day - this shoud be enough

ad proposals, could we create proposal for some big exchange entry fee? or for covering losts made by hacker?

Just walked in, let me check...

[requiredtruth]

I am the one called requiredtruth, with the reddit post, ill now keep my eye here, really itchen to move some BBP around.

[togoshigekata]

Recapping the pool issues:

We had two different problems hit the pool at once:  instability, this is what Tiras reported days ago, and inconsistent hash readings, this has to do with your shares relative to other people.

Tiras, Tom both reported similar things- where random workers would drop off the list.

I found the root cause of the problem for the instability.  Its now fixed, I believe permanently.

Next, Ill check on the HPS relative to others...

Pool issues fixed...

You should not see any missing workers in the pool, if one is missing, before posting here please restart the node once, and ensure it is running 1.0.7.1.  1.0.7.1 is now required by the pool for solutions to be correct.

I'll add two more columns to the pool for easier troubleshooting and for some new information...

Just when the pool was catching up with its deficit (I was about to lower the fee down to .04 from .05) as it was within -400,000 deficit range (for Slovakia thats how much was Lost since inception not counting the faucet that I spent 150K on), someone has hacked the pool last night.  There is no trace of entry on the box, or a request for the withdraw in the logs, but this means the pool is not going to be cheap again for a while.  If you prefer to solo mine due to the fees, I understand, go for it.  Im not out to make a profit.

Anyway, if anyone wants to try to trace the hacker, here is the info for some of the withdraws in the middle of the night around 02:02am CST US time:

https://biblepay-explorer.org/address/BA6wJpAbA4WCNK9X1UwgnweCSCXCGYPZ71

Id prefer to work in slack on the finer details.  Alex when you wake up please ping me.

unfortunately that means we have to write yet another system that requires withdrawals to go through a whole different server.

Ill work on this all day today and possibly unto the night to try to get the withdraws working again guys.

bible_pay if you using VULTR: they can monitoring loggin to your machine

Yeah, I am using Vultr?  Are they known to steal the passwords from crypto configs or config files?  If so maybe I should switch hosts.

Either way its going to be so locked down tonight nothings coming out of the box but encrypted traffic, but please fill me in on vultr...

Pool Fees:   18%

I'm a little overloaded right now, but here is a quick update:

Im running a database maintenance script, and had to consolidate your balances owed into one more succinct record (in contrast to thousands of "mining_credit" records), this caused the server to think your balances are immature.

All you have to do is subtract the two numbers and you will see the total owed is still the same as before the script was started.

Ill take a look at putting it back to the way it was by tomorrow, but either way it will work itself out within 24 hours.

Next, I have an idea how we can prevent the pool from being a hacking target.

In the Python pool, they require a valid receiving address in order to mine.
I think what we will do in the future is forcefully send your rewards out every time a block is solved - to your address on file.

Give me a couple weeks to look into that feature, it may take a while to get that completely working, but I think that feature will button down the pool.

The 18% fee is just temporary.  Hopefully you realize this is in order to keep the pool running.

[bible_pay]

I am the one called requiredtruth, with the reddit post, ill now keep my eye here, really itchen to move some BBP around.

Your balance is still correct: 1959, everything looks OK. 


Anyone with a negative balance showing, just download the CSV to verify your balance by clicking Transaction History | Printer icon.

The negatives will be gone tomorrow.

[bible_pay]

Hello Dev Team,

I cannot login at this pool: http://pool2.biblepay.org/ and http://pool.biblepay.org/ yesterday I am logged in, I try to reset my account but it says "Unable to retrieve a user with that username" what happen? my username in pool: okane81

Can you fix this, I have mined balance over in the pool. WTF!

That was just a fluke, I had the database locked down, please try the reset password now.

[bible_pay]

we are not hitting blocks, what can be problem?
last payout was on block 23356 but chain is already 10 blocks ahead, is this due to db maintenance or is there some other serious problem?

to prevent stoling coins, just add feature to autowithdraw once per day - this shoud be enough

ad proposals, could we create proposal for some big exchange entry fee? or for covering losts made by hacker?

Looks like we just had a dry spell, pool automatically checks for prior solved blocks, I see we solved the normal amount in the last two hours now.

Yeah, will be working on auto-withdraw asap, in one transaction per X frequency, across Y miners.

Ill comment on that proposal later; we have one more "potential" solution for the exchange and we should know within 23 more days whats going on with that...

[requiredtruth]

so does that mean i can widthdraw something or must wait 24 hours?

[bible_pay]

so does that mean i can widthdraw something or must wait 24 hours?

The server is not finished being upgraded, I will update everyone when withdraws open again.