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

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: ?? on ??

Hi Rob:

Block Height: 124660
Source: Smart-Contract-Payment
Transaction ID: 234eb0fed5151886cdfd843ebf39d11dfc06523c86d7c378b6b59cc2065a2c5d

To validate results, this is what I type in Debug Console?

leaderboard false 124455

It looks like payment is integer and the decimal is dropped off in the payment?

Is the one payment with decimals, the reward to the miner and no payment to masternode?
B6UueDe1mg1ZM9wPfFjvGwcY9z875gXwdV 2,807.33256586 BBP

Hi Sun,

You can now type 'exec analyze 124660 your_nickname', and it should contain a list of all known tithes from 124455 to 124250.

The sancs are running in 'compatibility mode' right now, so we are temporarily dropping the last 2 digits to be compatible until the last 60 new sancs upgrade. Then we can enable the spork that starts scaling out to the last 2 digits again (once we see 80% participation levels) on this latest version.

Sorry, could you paste the txid regarding the question about the sanc, I can't search for it by address.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: capulo on June 10, 2019, 01:50:51 PM

Quote from: bible_pay on June 10, 2019, 08:14:02 AM

Quote from: capulo on June 10, 2019, 03:16:35 AM

why are rewards per block in pow so low? they was above 5000 and now below 2000 in avg. nothins special that i have several with about 1200bbp/block

Reward:
http://wiki.biblepay.org/Evolution_Mining_Economics

If you got the whole reward on a block its because the sancs didn't vote on that blocks winner to a great extent (> 10 votes).
See 'masternode winners' for empty blocks.

hm i dont understand, there is POBH Mining Reward: 3750 BBP
but i cant see that high reward in previous blocks
this is from pool history
2579
2177
2074
2466
2176
1770
2420
1402
1206
1773
2184
1406
2626
1351
1221
1618
1864
2687
2917
2210
2087
1382
1686
2067
2199
i'm getting similar on solo machines

Take block 122579, your first one, I see a 5162 pobh reward and 5162 sanc reward.

Do you have a specific block # you would like to hone in on, and I can break it down.

Do realize that 48.5% is escrowed for Governance starting at 124,000, that is to fund the 950K per day reward going to the GSC contract. Its a deflating figure as usual.

capulo

newbie

Activity: 491

Merit: 0

Quote from: bible_pay on June 10, 2019, 08:14:02 AM

Quote from: capulo on June 10, 2019, 03:16:35 AM

why are rewards per block in pow so low? they was above 5000 and now below 2000 in avg. nothins special that i have several with about 1200bbp/block

Reward:
http://wiki.biblepay.org/Evolution_Mining_Economics

If you got the whole reward on a block its because the sancs didn't vote on that blocks winner to a great extent (> 10 votes).
See 'masternode winners' for empty blocks.

hm i dont understand, there is POBH Mining Reward: 3750 BBP
but i cant see that high reward in previous blocks
this is from pool history
2579
2177
2074
2466
2176
1770
2420
1402
1206
1773
2184
1406
2626
1351
1221
1618
1864
2687
2917
2210
2087
1382
1686
2067
2199
i'm getting similar on solo machines

MIP

newbie

Activity: 362

Merit: 0

Quote from: bible_pay on June 10, 2019, 10:51:34 AM

BiblePay
1.4.3.4-Leisure Upgrade

** Mac & Linux building, Windows released **

** Mac & Linux Ready **

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

BiblePay
1.4.3.4-Leisure Upgrade

- Added exec analyze height nickname. This command allows you to drill
into the details of a GSC contract by height and nickname.
- Added graceful GSC upgrade for sanctuaries (removing 51% risk), and
ability to enforce the latest GSC version after the supermajority has
upgraded.
- Added backward compatibility with our first Evo versions so as not to
make this a mandatory for sancs

** Mac & Linux building, Windows released **
** Sanctuaries, please upgrade within 7 days **

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: Borgholio on June 10, 2019, 09:48:57 AM

Hey all, I cant seem to be able to attach to the biblepay pool. I set up the biblepay.conf file correctly but it would keep giving me the error "worker ID empty in pool config". After letting it run overnight it no longer gives an error but just shows that pool mining is false and no pool url is listed when I get mining info. Here is my current config file:

addnode=explorer.biblepay.org

genproclimit=1

gen=1

minersleep=0

pool=https://pool.biblepay.org
workerid=Borgholio

Thanks in advance for any help.

I thought of one more possibility after I replied, as you confirmed, you already confirmed the debug.log in that directory has a recent timestamp, so that makes us sure you are in the right dir. So please take a look at this next.

In each OS we have a different carriage return delimiter.
Could you please try re-creating the biblepay.conf on your machine fresh (IE with notepad or nano) and typing in the lines delimited by a , and ensure there is an extra at the end of the file, then restart?

(Also ensure there are no extra blank carriage returns throughout the file - as I see above you have one after minersleep, take those out).

Thanks!

Thats probably it since we checked everything else.

Borgholio

newbie

Activity: 99

Merit: 0

Hey all, I cant seem to be able to attach to the biblepay pool. I set up the biblepay.conf file correctly but it would keep giving me the error "worker ID empty in pool config". After letting it run overnight it no longer gives an error but just shows that pool mining is false and no pool url is listed when I get mining info. Here is my current config file:

addnode=explorer.biblepay.org

genproclimit=1

gen=1

minersleep=0

pool=https://pool.biblepay.org
workerid=Borgholio

Thanks in advance for any help.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: SVK Noko on June 10, 2019, 08:27:06 AM

Quote from: bible_pay on June 10, 2019, 08:23:47 AM

Quote from: ?? on ??

As you wish.

Please stop posting here Noko, as you are banned (I've explained this to you multiple times and PMed you). Please PM me if you want to know why you are banned and what to do to be unbanned.

I have no bann. You are deleting messages manually, thats the difference.

1) You are banned (see the OP post).
2) There is a difference.
3) If you wish to be unbanned, you must PM me. Otherwise you are not only violating the ban, but you are acting disrespectfully and adding more reasons to be globally banned.

People in our community do not deserve this low-level disrespectful, unruly attitude Noko. Please stop it immediately in Jesus name.

SVK Noko

newbie

Activity: 267

Merit: 0

Quote from: bible_pay on June 10, 2019, 08:23:47 AM

Quote from: ?? on ??

As you wish.

Please stop posting here Noko, as you are banned (I've explained this to you multiple times and PMed you). Please PM me if you want to know why you are banned and what to do to be unbanned.

I have no bann. You are deleting messages manually, thats the difference.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: ?? on ??

As you wish.

Please stop posting here Noko, as you are banned (I've explained this to you multiple times and PMed you). Please PM me if you want to know why you are banned and what to do to be unbanned.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: inblue on June 10, 2019, 07:04:10 AM

What are pam_hash and pam_hash_internal? What does it mean when they are not same (local hash disagreeing with the network hash)?

In a nutshell, we have a release that is leisure that is about to be released later today (adding the 'exec analysis') command, and that will clear up the warning.

The internal pam hash means the contract assessed internally is different than the one currently being voted on (that will be cleared up with the next leisure release).

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: capulo on June 10, 2019, 03:16:35 AM

why are rewards per block in pow so low? they was above 5000 and now below 2000 in avg. nothins special that i have several with about 1200bbp/block

Reward:
http://wiki.biblepay.org/Evolution_Mining_Economics

If you got the whole reward on a block its because the sancs didn't vote on that blocks winner to a great extent (> 10 votes).
See 'masternode winners' for empty blocks.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: inblue on June 10, 2019, 07:04:10 AM

What are pam_hash and pam_hash_internal? What does it mean when they are not same (local hash disagreeing with the network hash)?

Please PM me security related questions.

inblue

full member

Activity: 462

Merit: 103

What are pam_hash and pam_hash_internal? What does it mean when they are not same (local hash disagreeing with the network hash)?

capulo

newbie

Activity: 491

Merit: 0

why are rewards per block in pow so low? they was above 5000 and now below 2000 in avg. nothins special that i have several with about 1200bbp/block

MasternodeCap

jr. member

Activity: 78

Merit: 1

Greetings,

masternodecap.com is now running the last version of BiblePay-Evolution: 1.4.3.1.
Nodes monitoring and stats for BBP.

You can be notified when:

the status of a node changes
your nodes get rewarded
an upgrade of your wallet is available

You can reach us in our Discord!

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: seeksilence1 on June 09, 2019, 03:49:35 PM

For pog, can I use the gui to send the gscc so I can control the inputs? Or will the "exec sendgscc" consolidate small amount entries from inputs?

Thanks.

I don't believe coin-control works properly yet - with GSC transmissions, however sending a Diary entry with coin control and Send "may" work, but I haven't specifically tested that (that is only good for HEALING anyway).

But to answer your question, 'exec sendgscc' gives you some control. It skips over locked coins and sancs. It does consolidate all applicable coins into one transaction - coins whose coin-age adds up to the "pog_coinagepercentage=.nn" percentage. So if you set that at .50, it would keep adding inputs that are not locked until half of your coin_age is accumulated in the transaction.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: inblue on June 09, 2019, 03:51:46 PM

Quote from: bible_pay on June 06, 2019, 12:15:23 PM

Prod requires contracts to have at least 20% of the enabled sanc count (thats about 26 now) in order for the GSC to pass. So that explains the required_votes value.
The reason we end up with barely enough every day is because the sancs are currently programmed to only vote if they need to (IE they check to see if the contract is passing) and ignore it if its already got more than enough votes. However, they have a very intelligent rule. If the sanc finds the popular contract hash disagrees with its internal view of the contract it will always vote against the popular one (and then it will create a new one and vote for it). So remember at the time we had 500+ sancs, I was thinking along the lines of efficiency (IE not to make every sanc do the work if we had 20% in agreement). I also think with this current logic - the other facet is if the contract changes - the sanc quorum must be nimble enough to make a quick change (and not have to reverse the entire farms votes of 100% being wrong) - since they do actively watch and monitor the voting outcome every 5 blocks, so they *will* jump in and vote for it if necessary. So Im thinking this is still predominantly good given the volatile potential nature of a competetive change in contract(s). Now on the downvote, that can happen if the contract changes (like right now we had a leisure upgrade that changed consensus). You will see the nodes who upgraded will be voting on the new style contract, and the old nodes on the old and only one will win. (We have a tie breaker piece of code in there also).

I am reading this again for this occasion. So the sancs which did not vote yet should now be voting before the next superblock to ensure that this contract passes, so there should be no concern? I see the votes are steadily increasing closer to the required number.

I think we have a way to make the new contract backward compatible and resolve this for now without a sanc mandatory upgrade tonight.

(I'm going to add a spork over the next hour that will make the contract backwards compatible with the first version).

Then over the next 10 days we can deal with easing in the new rule that allows smooth transitioning to upgraded business logic.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: dave_bbp on June 09, 2019, 03:16:30 PM

Quote from: bible_pay on June 09, 2019, 12:16:14 PM

So on this headless password, sorry, I gave you the wrong info. We made the first part of it an argument instead, this is to keep it out of the bash log (like FTP clients do).
So please try this (I think special chars will be OK):

biblepay-cli -headlesspassword

Then step 2:
biblepay-cli autounlockpasswordlength

The password that is memorized by the command will be used in the auto-unlock feature.

P.S. To script this, you can use an FTP-type script. MIP has one and I have one I could send you if you need it.

Awesome, now it works as it's supposed to do. I don't think I'll need an extra script for this since I won't use it too often and it's not really complicated once you know the trick. Cheesy

On a completely unrelated note: I can't delete workers from my workers list on pool.biblepay.org
There is the "garbage" symbol at the end of the line, but this is not clickable. Tested in Firefox and Vivaldi.

10-4 on the trash can. I just added this to my punchlist and will fix it asap.

inblue

full member

Activity: 462

Merit: 103

Quote from: bible_pay on June 06, 2019, 12:15:23 PM

Prod requires contracts to have at least 20% of the enabled sanc count (thats about 26 now) in order for the GSC to pass. So that explains the required_votes value.
The reason we end up with barely enough every day is because the sancs are currently programmed to only vote if they need to (IE they check to see if the contract is passing) and ignore it if its already got more than enough votes. However, they have a very intelligent rule. If the sanc finds the popular contract hash disagrees with its internal view of the contract it will always vote against the popular one (and then it will create a new one and vote for it). So remember at the time we had 500+ sancs, I was thinking along the lines of efficiency (IE not to make every sanc do the work if we had 20% in agreement). I also think with this current logic - the other facet is if the contract changes - the sanc quorum must be nimble enough to make a quick change (and not have to reverse the entire farms votes of 100% being wrong) - since they do actively watch and monitor the voting outcome every 5 blocks, so they *will* jump in and vote for it if necessary. So Im thinking this is still predominantly good given the volatile potential nature of a competetive change in contract(s). Now on the downvote, that can happen if the contract changes (like right now we had a leisure upgrade that changed consensus). You will see the nodes who upgraded will be voting on the new style contract, and the old nodes on the old and only one will win. (We have a tie breaker piece of code in there also).

I am reading this again for this occasion. So the sancs which did not vote yet should now be voting before the next superblock to ensure that this contract passes, so there should be no concern? I see the votes are steadily increasing closer to the required number.

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