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

So the way Masternodes.Pro calculates annual ROI (Return On Investment) is:

"To get the annual ROI we sum the 24 hours rewards multiply that by 365 then divide that product by the amount of coin required and multiply that by 100 to get the percentage.
We're just doing getblockhash then get block with that hash and taking the information given to us by that to get the txids and such to get all this information."

And I guess first txid in the getblock tx list is always the new coin generation transaction?, and then they probably use gettxout txid 0 and gettxout txid 1 to get the values?

I noticed last budget that our monthly budget pumped our ROI up by 4x for 24 hours, so I think they added code to start ignoring incorrect masternode reward for superblock from getgovernanceinfo, and with the new daily research superblock, I believe this also would pump up our ROI, and I think they might start ignoring incorrect masternode reward for the superblock from exec getboincinfo

Which leads just regular blocks left, which I believe 90% is Masternode Reward and 10% is Proof of Work reward, is this correct?

This is all very interesting, Im not sure our ROI has ever been totally correct on the masternode statistics sites
and Im not sure if my understanding is fully correct yet either
Im not sure if the way they are doing things works with superblocks involved

Thanks Jaap for the forum PR about the 'Website Enhancements & Suggestions'!

http://forum.biblepay.org/index.php?board=8.0

Slovakia, add suggestion as Issue on Pool Github code page:  https://github.com/biblepay/BiblePayPool/issues >> New Issue

Most future users of BiblePay will not be miners, future users will just use a desktop or mobile wallet to store and send coins

Interested to write better mining documentation ride22?

Distributed Computing:
http://wiki.biblepay.org/Distributed_Computing_Start_Guide
http://wiki.biblepay.org/Distributed_Computing

Togo Step Guide:
http://wiki.biblepay.org/Distributed_Computing_2

Lichtsucher Guide:
https://www.biblepay-central.org/en/mining-how-to/

The wiki is open to anyone to edit, just have to create an account, look forward to what you contribute.

Grandma doesn't care about mining.

What she needs is a mobile wallet and a decent exchange to convert the $$$ into BBP easily so she can tithe at the church.

It will help! Your work is very much appreciated, Lichtsucher!

Oh okay

I agree that the proposals could be separated a bit more clearly (maybe with an extra separation-line or something). And it shouldn't matter if you click on the black or gray part to get the vote command (or the pop-up shouldn't appear when you click on the black part).

But the most important thing to me is that it works.

Rob already gave me access to the data behind the proposal lists of the pool. I will add a more stylish version with more graph to the next version of the Biblepay-Central site. Hope that will help.

jaapgvk i know how to vote: but it looks bad : all melts together, descirption is under proposal 

You can find it in the pool in 'governance > proposal list' (of course, you know this). But you need to right-click in the grey area of the proposal and select 'copy vote for proposal'.

ROB give here link for voting for IT ... im lost from web,forum,btctalk,pool,github,reddit .... we need max 2 webs for this .... ill go vote for IT and blockchain is right now  

can you made better proposal on pool? looks very mish-mash, that lines is horrible for knowing

columns with TriggerTime   FundedTime       Height  deletes and add description together in 1 line

7500000.0000   View Proposal   Charity   1  March 2018 Compassion.com Recurring Orphan Sponsorship Premiums  etc


voted yes for all things

Thank you for your awesome coding work, Rob! What you do in a month an average developer does in a year!

I have voted Yes for IT expenses and I remind all sanctuary owners to vote for that proposal every month.

for me is better to wait, as i still have locked big buch of coins on c-cex... )

7 days for voting is enough: how long being ELECTIONs less than 24 hours

Technically yes. I think Rob was looking at making things a bit more automatic but that is in the works.

However, right now to make full use of your RAC you need 500 BBP per magnitude. With your RAC where it is you won't need to change anything until the 1st of April (when we switch to another # of BBP per magnitude, or BBP per RAC).

Thanks guys, it works for me. But before the balance reaches 50k, I have to update it manually?

I think this is one of those situations where Rob cannot win!
If he waits until 1st April then people are upset that we have to wait so long.
If he changes early then people complain that he cut the vote short and accuse of removing democrazy.

Better to just stick with whatever date is set already, in my opinion.

Ok then add

Then in the debug console try doing

if you not specified in config, then default is 50001, do you have at least this amount in wallet?

this error means that you dont have enough coins to stake (not staked coins), so if you have 50k coins and stake 20k coins, then if you change config to stake 50k it failes because you have only 30k not staked...
you need to wait for all coins will be again available, check exec stakebalance to see how many.. and then do podcupdate
it works for me in this way