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

HPS is what the machine shows in getmininginfo, HPS2 is what the pool is measuring about your machine.

As far as mining with 4500 BBP, it will help, as I believe the algo will be tweaked in testnet until its 90% easier to POL mine than to be in outer darkness, so please, come over to testnet and help test it and make that happen for small balances.

In testnet, its about 24 hours after you received the coins, but its better if you understand each of the key factors in getmininginfo over there,
 post the questions about each of the keys there please.

I find the idea of helping distressed and poor people interesting. In my area there are a couple of catholic organizations with strong projects in developing countries (wells, bridges, schools...)

How would I create solid "user cases" for BBP tech helping those organizations? We are talking about countries with little or none banking infraestructure.

we start to receive first POL/POS coins  after 24hours?

what's the difference between H/s and HPS? The pool shows my workers in HPS but when i look up a CPU online it shows it in HS.  I might look at upgrading my CPU.

Also with the changes based on having a stake how will that affect me as i only have 4.5K BBP?

Thank You

Hello bible_pay, my account in the pool does not access and I do not receive the email to recover, how do I proceed to withdraw my coins?

Ok. Thanks! I'll give it a try when I have more time. I always look for optimizations that's why I want to try some code + compile optimizations. Maybe I should do my tests in VMware directly in Linux.

It does work in both daemon and QT in testnet, but I have not finished the feature that lets you know your block was a POL clearly in the daemon in the rpc listtransactions command yet.

I guess you can get around that in the daemon by keeping a list of the block numbers you mine then do this:
showblock blocknumber

If the block was a POL, it will have 5 additional fields on it.

In QT, the block is marked proof-of-loyalty in the transaction list.

You can go ahead and go to 1083.  1083 in prod is the same as 1082. 

We have a  feature in the wallet that keeps the POL feature shut off until enabled with a switch, so Prod is safe to go to 1083.

Alex and I tested windows in prod last night to make sure.

do i need gui for testing pol? or it will work also from cli?

I have a few miners on 1081. I didn't upgrade to 1082 because they weren't crashing.

If I upgrade using

git pull origin master

will I end up on 1082 or 1083?
If I end up on 1083 can I still mine on the pool or only use this for testnet?

Hi, I noticed that BBP is no more listed on Masternode.pro. What's the reason?

Yes, download 1083 first, and the feature is created in a way where it is separate from Prod, but if you download latest and start with the -testnet flag, then ensure you are solo mining.  Its not OK to not mine:  the POL system still requires mining, but, if you wanted to be green you could now mine with one thread      if you want...

Lets post all that in the testnet thread though:
http://forum.biblepay.org/index.php?topic=89.0

Thank you, I understand. I want to help on the testnet. Since I already have some tBBP you sent me some time ago, then all I need to do is download the 1.0.8.3, start my wallet with the -testnet flag and just let it sit there for 24 hrs? Is it OK if I don't mine?

Now that C-CEX is partially up (on the bitcoin side, not on the BBP side), I have paid this months Orphan Recurring expenses successfully.

If you navigate (in the pool) to Orphans | Orphan Fundraisers, and Orphans | Expenses Paid, you can see that after being in business for 6 full months, we have finally broken even!

So on a positive note, Biblepay is self-sustaining in the most basic sense: It is now supporting 189 orphans around the world on its own!  Congratulations all of you warm hearted tithers!

Although we met the milestone (using superblocks and being self sustaining) finally (since as of last month, we had a deficit of $10k), on the downside we do not have a surplus yet, here is the grand total state of biblepay:

$37,691 income to date
$37,267 expenses to date

(Well, yes, we do have a $500 surplus now), but my point is we still have had only barely enough to cover the recurring expenses and have not yet paid orphan premiums in advance as we plan to.

With the superblocks at 40 day spacing, and the budgets at almost half of what they were when we started, its going to be close, but I also believe we have an extremely bright future, along with the state of the sinking economy, and crypto in general - a very bright future.

(On a side note, we plan to fix the block spacing, the network hashps, and the superblock funding levels in testnet to have changes ready for the next mandatory that may include POL, so that effect should be resolved).

Thats correct, coin age is when you received the coins in your wallet.

If you spend them to yourself coin-age starts over.


Realize that almost every POL transaction is going to be measure as:  the historical date of the last POL spend To the date of the current POL spend, so its probably easier to grasp it that way, than think this has something to do with buying coins on the exchange.  The initial funding age will pale in comparison to day to day operations.

Yes, I think we should have a proposal to vote on, otherwise people will blame me for making a unilateral decision.  Ill put one in before the end of the day.

We should solo mine at first in testnet and ensure the stakeage calculation works well, then later on in the process Ill fire up the testnet pool again and we can test pool mining with POL.

The coin age is, if I'm reading it correctly, the age since they were last transacted.  If you have advanced coin control enabled in your wallet, if you select inputs, it will show the age of each coin in your wallet.

So buying BBP, mining BBP, sending a transaction to yourself all end up with a coin age of zero.   The source doesn't affect coin age, merely how long it has been in YOUR wallet.

Thanks for taking the time to explain, I was thinking at worst it would only be attempted to be double spent if more than one machine solved the same block, but am eager to learn.

Secondly, for something of this magnitude, do you think we should put a proposal up and have the Masternode Network vote on it?

Finally, I should have a box on testnet by tomorrow.  Should we be solo mining on testnet?

Please help me understand - when I read the PoL wiki, I thought coin age was the time period since coins have started to be staked or since they have been last moved? It doesn't matter when they were actually created, right?

Because if the coin age is the time period since the coins have been mined, then as you said, someone who buys coins from an exchange can get older coins, and therefore have better conditions to mine, and the botnet miners will always have the newest coins because they never buy from an exchange, they only mine and immediately sell. But then, obviously, a buyer on the exchange can also buy the new coins, and they probably even have a higher chance to buy the new coins because those miners also sell instantly or put sell orders at the top.

And if the coin age is the time period since the coins have been last moved, then I don't get the buying BBP on the exchange part, because when I withdraw the coins to my wallet, coin age will be reset to 0?