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

Nice job. It is very intuitive and it'll be very useful for newbies.
Add there also info about how to make unbanked arm account - on pool.

oh... and additional info about previously written things here.
I hitted about 10 blocks on first day, but in last 24h I hit only 1. And yes I have my wallet.dat on 2 machines + 1 sometimes

Awesome job, Lichtsucher! You made the guide beautiful, clear and easy to follow. Please share your BBP address for tips.

I think you are on the network now but the current contract doesn't have you in there yet.

cat magnitude | grep 328a
BRYo1mSUS9NB79RokuDF3N1NbFWdUvTBMK,328ae544f566cd3ec2191b0e825b38c3,0.201,1987605,15044,3650,100,977248,0,100.00,197,197

Rob you got true with that exponencial btw..... but why you set only 20 000BBP max?   all ppl in slovak chat room told that we can vote for more high 50 000bbp for 1MAG ..... better for ... but you have to implement immediately this SYSTEM STAKE-BBP/MAG cos botnet in these days mined mooooore BBP ... you know it

Rob is working on an auto-unlock feature in headless. Yes, you will need to unlock it.

I'm mining a new coin with Nvidia 1060 and I have about 11 Coin/ day
Price: 0,0004Btc, sell now.
So you have 0.0044BTC/day =>39$
BTC price: 8879$
How to? which coin?
Join discord for to know

https://discord.gg/KrbNXEq

Do I need to unlock my Sanctuary wallet to start the POW mining before run "exec associate rosetta_email_address rosetta_password true"? Is it safe to keep the wallet unlocked in the Sanctuary server while mining? Or it is better to turn off the mining in sanctury server?

Thanks for clearing it up.

Can you clarify this for me? I am mining last 2 days and this is the results I get. I am staking 3500 BBP and have my RAC seen over last 3 blocks but 0 magnitude and 0 payouts...

 "Command": "getboincinfo",
  "CPID": "328ae544f566cd3ec2191b0e825b38c3",
  "Address": "ADRESS",
  "CPIDS": "328ae544f566cd3ec2191b0e825b38c3;",
  "CPID-Age (hours)": 422439,
  "NextSuperblockHeight": 34235,
  "NextSuperblockBudget": 2660579,
  "328ae544f566cd3ec2191b0e825b38c3_ADDRESS": "ADRESS",
  "328ae544f566cd3ec2191b0e825b38c3_RAC": 387.43,
  "328ae544f566cd3ec2191b0e825b38c3_TEAM": 15044,
  "328ae544f566cd3ec2191b0e825b38c3_TaskWeight": 100,
  "328ae544f566cd3ec2191b0e825b38c3_UTXOWeight": 3650,
  "Total_RAC": 387.43,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 7981737,
  "Superblock Count (One Week)": 3,
  "Superblock Hit Count (One Week)": 3,
  "Superblock List": "34030,33825,33620",
  "Last Superblock Height": 34030,
  "Last Superblock Budget": 2660579,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Update on the mechanics of the Sanctuary Quorum - Affects big dogs:

So everyone can understand the effects of the next mandatory that is hitting the network now, the stake-per-magnitude UTXO vote and the current PODC network UTXO requirement:

Between Now and block 35110 we have a certain percentage of Sancs that still enforce the old UTXO weight rules (IE 50001 stake per day gives you a 100% UTXO weight).

After block 35110, we switch to the new rules called stake-per-mangitude (SPM).  At that point your UTXO weight is a number (IE 75,000 means you staked 75000 BBP over the last 24 hours).

For a smoother cutover, the current spork level for the network is already set at 500 stake-per-magnitude.

This means that after 51% of the sancs upgrade to the mandatory, the contract will be requiring 500 per mag to receive full credit.

So for example, if we have a supermajority upgrade by Tuesday the 13th, this rule will *already be in effect*.

If your magnitude is 100, you will need 50000 SPM to receive 100% credit.

After the poll ends, we will enter a spork-config update with the poll results and all sancs will immediately adhere to the new value.

Either way, the deadline for the sancs to upgrade is block 35110.

We can still potentially allow exchanges to upgrade and exit maintenance before then, but lets go 24 more hours and re-assess the situation, and possibly notify exchanges tomorrow.

Im in the process of double checking our new mandatory RC and ensuring we have enough reporting for UTXO weight before notifying exchanges.

Hi everybody,

as most of you already learned, the new Setup for Biblepay mining is not simple. It might be one of the most complex of all crypto coins out there.

But a good documentation can always make it easier. To help here, I used the last days to work an a easier and more straight forward Mining How-To for Biblepay.

And here is the first Alpha: The Biblepay Central Mining How-To
https://www.biblepay-central.org/en/mining-how-to/

It is not finished, but maybe already useful for some users. As I'm not a native speaker in English, it will contain some errors. Help is always welcome


The rest of the website is under construction, I will post more about that later

what is that magnitude  I guess  I have 22000 bbp in my wallet... so what will I get I don't understand, or where I have to read get info

Since this coin is partially for charity - would it be possible make an increase in the 10% to charity based on higher computing power?
10% base PC - higher % based on higher level CPU / multiple CPUs per ID being dedicated to mining.
Eliminate the greed effect in this manner and level the playing field?
PM

Please vote:
http://forum.biblepay.org/index.php?topic=127.0


The problem with exponential increases is it persuades users to split the CPID into multiple CPIDs.
Its still a cat & mouse game if we do that.

I think the #1 line of defense is vote as high as possible for UTXO per magnitude first.

The first thing the user would do is split CPIDs if we had a rule that said: Require double the UTXO if Mag > 100, then they would create two cpids....  Im not a fan of squirrely program logic that we will have trouble supporting- and be frowned upon by the peer review panel for questionable logic.

Thanks, yes 1110 finally fixed the bug we introduced with PODC and heat-mining.  
The users mining against the pool are controller wallets with CPIDs, but some of them are copying the wallet.dat out to multiple machines and hitting the pool with the same CPID from multiple machines.

This "game" is OK right now in the sense that more hashpower is going toward that block from a legal CPID.

hmm good to know that new payments for next superblock are ready few minutes after last superblock payouts...
you can check them now

It seems a lot of users had problems upgrading there system to the new mining logic. You can see the low in my own mining
Some users hadn't submitted much on the 8th and 9th of march because of the switch, but it seems that most users are solving there problems right one.

Same for the main pool. The switch to the new logic came quick, many users need to adjust

Yay! My first payment came through on the last superblock.
Also that last wallet update 1110 has fixed the POW mining issues
I was having. Back on the pool again thanks Rob

On a side note, now we are mining on boinc, we should have the one control wallet
Linked to that account, so I noticed that on the pool people have
Multiple machines mining pow, not sure how this is possible without having a bunch
 of control wallets is this thinking correct?

Thx for your quick response. Oh well, I might have taken a break in between and the returned to your pool.
However, judging by the statistics table all the blocks from march 10th and 11th have been divided between your address and some others, but e. g. number 2 and 3 in the list (and also others) have their last share at march 9th, so this is what confused me.


btw: the next superblock went through, congrats everyone and good job! Now let's see if we can get the dynamic stake requirement in, to give more incentive for holding (or buying) coins rather than mining and dumping them as quickly as possible.

Just because you experience the world in a certain way doesn't mean that everyone else also experiences it in that way. You twist words and refuse - or are incapable - to see the point I was trying to make. I'm sorry, but that's your problem, and not mine, and I'm going to leave it at that.

Don't really understand your post. As you can see, the pool is finding blocks quite fine. If you say you left 3 days ago, then you didn't contributed much, as the pool got better after you had left... looks like the pool didn't need you
And that you hadn't really contributed anything, or we had seen the rise int he pool before with your "great" help.

I can't see what you are doing now, but as said, I don't thrust you. And really, I don't care that much. I think I will end this discussion here, was enough fun for me, I need to go on and work on useful things for the community.