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

[bible_pay]

Im a little late, but my understanding is that if we request too many coins from the budget,
the budget will only pay out the proposals with the most yes votes (pays out in descending order of yes votes),
is that correct?

If we request too many, the budget will not be converted and approved as a superblock (the chain will fail with Superblock amount too big).  We need to be careful to not insert too many proposals into the next budget next time.

We basically voted in an invalid budget.

[1715077767]

1715077767

[1715077767]

1715077767

[1715077767]

1715077767

[1715077767]

1715077767

[bible_pay]

Biblepay Dev#2 pulling down code and attempting to merge in one Dash Evolution commit into testnet.

Dev #1 (Rob) will be creating new Testnet branch today.

Welcome aboard Bhavani!  The best of luck to you.

[operabit]

So it looks like the root of the problem is the pool is somehow not taking into account deflation (for proposal budgets).  Will be fixing that next.

Maybe you need to add to the new pool, because normally it will work again if the problem is just a miner pool.

[bible_pay]

So it looks like the root of the problem is the pool is somehow not taking into account deflation (for proposal budgets).  Will be fixing that next.

Maybe you need to add to the new pool, because normally it will work again if the problem is just a miner pool.

I added a field to 'getgovernanceinfo: nextsuperblockbudget' so problem will be fixed after next leisure release.

[ermintrude]

Confused with pools and blocks now..
Robs pool is at 30759..
My miner on the new pool is reporting 30749..
My wallet is reporting 30749..
biblepay-explorer.org is stuck 6 hours in the past on 30732..

edit: And robs pool is reporting zero masternodes, whereas explorer, and my wallet report the correct 148.. Has a fork occurred here ?
edit: And my masternode agrees with Robs pool at 30762.. Balls..
edit: Resynced wallet, and seem to be back from whatever parallel universe I ended up in.. No idea what happened there..

[togoshigekata]

Confused with pools and blocks now..
Robs pool is at 30759..
My miner on the new pool is reporting 30749..
My wallet is reporting 30749..
biblepay-explorer.org is stuck 6 hours in the past on 30732..

edit: And robs pool is reporting zero masternodes, whereas explorer, and my wallet report the correct 148.. Has a fork occurred here ?
edit: And my masternode agrees with Robs pool at 30762.. Balls..

I run a backup explorer:
http://explorer.biblepay.org:3001/

Is Alex still a part of the project? I heard he might have left?

Alex runs the main explorer:
https://biblepay-explorer.org/

[znffal]

Next.Exchange vote is now up to 900!

Great work all! But we are falling off the first page! Please keep voting. We can make 1000!

Thanks
https://nextexchange.featureupvote.com/suggestions/3384/biblepay-bbp

[inblue]

I run a backup explorer:
http://explorer.biblepay.org:3001/

Is Alex still a part of the project? I heard he might have left?

Alex runs the main explorer:
https://biblepay-explorer.org/

I've talked with Alex, he is unfortunately not a part of the project anymore. I've asked will the block explorer be shut down and this is his answer:

I haven't decided on how to do the transition for the block explorer yet. For now I will make sure it keeps running correctly, I will just not add functions or correct minor bugs anymore.

I will do the same for other services I am running such as the dns seed servers. I am shutting down the Iquidus BX and testnet one though.

Going further I would advise people to use http://explorer.biblepay.org:3001/ as the main explorer.

[bible_pay]

Confused with pools and blocks now..
Robs pool is at 30759..
My miner on the new pool is reporting 30749..
My wallet is reporting 30749..
biblepay-explorer.org is stuck 6 hours in the past on 30732..

edit: And robs pool is reporting zero masternodes, whereas explorer, and my wallet report the correct 148.. Has a fork occurred here ?
edit: And my masternode agrees with Robs pool at 30762.. Balls..
edit: Resynced wallet, and seem to be back from whatever parallel universe I ended up in.. No idea what happened there..

The pool, my node and my sancs are all on 30772 now, so Im not sure if we were forked at 30750 or not.
I know that we hung at 30750 for one hour while we corrected the superblock.

NOTE:  Please do not rely on the pool about page for the official block #.  That page is cached for 10 distinct hits at a time.

[orbis]

Going further I would advise people to use http://explorer.biblepay.org:3001/ as the main explorer.

That's not good news, because this pool has closed access to API

[bible_pay]

Hey Webster are you still out there?  Still working on the mobile wallet?

We had a mention of it in the inbox today by Adams, he is someone passionate about starting a ministry in Africa with it.

[bible_pay]

Going further I would advise people to use http://explorer.biblepay.org:3001/ as the main explorer.

That's not good news, because this pool has closed access to API

Could you be more specific, do you mean Alexs API, or Togos api?

[orbis]

Going further I would advise people to use  as the main explorer.

That's not good news, because this pool has closed access to API

Could you be more specific, do you mean Alexs API, or Togos api?

I mean Togo's API. He has allowed only API for block hash: http://explorer.biblepay.org:3001/api/getblock?...
Other request are not allowed...
On Alex's explorer you can use API to access data for your wallet address and use it with JSON parser.

[joelles]

Did we fork?

[togoshigekata]

Going further I would advise people to use  as the main explorer.

That's not good news, because this pool has closed access to API

Could you be more specific, do you mean Alexs API, or Togos api?

I mean Togo's API. He has allowed only API for block hash: http://explorer.biblepay.org:3001/api/getblock?...
Other request are not allowed...
On Alex's explorer you can use API to access data for your wallet address and use it with JSON parser.

I can update the explorer to allow API, I disabled it awhile back because I thought it was interfering with something,
but it was another issue, and I forgot to enable it back on

[togoshigekata]

Im a little late, but my understanding is that if we request too many coins from the budget,
the budget will only pay out the proposals with the most yes votes (pays out in descending order of yes votes),
is that correct?

If we request too many, the budget will not be converted and approved as a superblock (the chain will fail with Superblock amount too big).  We need to be careful to not insert too many proposals into the next budget next time.

We basically voted in an invalid budget.

bin/watchman.py
Line 94: proposals = Proposal.approved_and_ranked(...)
Line 98: sb = dashlib.create_superblock(proposals, event_block_height, budget_max, sb_epoch_time)
https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/bin/watchman.py#L94


lib/models.py
approved_and_ranked()  "return all approved proposals, in order of descending vote count"
https://github.com/biblepay/watchman/blob/e944d85fe5edc89d0ad4459c2428127cbc3b4d16/lib/models.py#L338


lib/biblepaylib.py
create_superblock()
Line 105: if (budget_allocated + proposal.payment_amount) > budget_max:  "# skip proposals that are too expensive..."
https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/lib/biblepaylib.py#L89


So to me it looks like watchman, sorts the proposals before sending them to create in the superblock
and in the superblock creation the proposals get added up 1 by 1 unless they go over the budget limit at which point they get skipped

What was the error that you saw exactly Rob? Im interested to dig into this

If the above is correct, then it should have theoretically skipped the passing proposals that went over budget with the least amount of votes,
specifically the PR Communications Marketing proposal I think, I believe it had the least amount of votes

[bible_pay]

Im a little late, but my understanding is that if we request too many coins from the budget,
the budget will only pay out the proposals with the most yes votes (pays out in descending order of yes votes),
is that correct?

If we request too many, the budget will not be converted and approved as a superblock (the chain will fail with Superblock amount too big).  We need to be careful to not insert too many proposals into the next budget next time.

We basically voted in an invalid budget.

bin/watchman.py
Line 94: proposals = Proposal.approved_and_ranked(...)
Line 98: sb = dashlib.create_superblock(proposals, event_block_height, budget_max, sb_epoch_time)
https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/bin/watchman.py#L94


lib/models.py
approved_and_ranked()  "return all approved proposals, in order of descending vote count"
https://github.com/biblepay/watchman/blob/e944d85fe5edc89d0ad4459c2428127cbc3b4d16/lib/models.py#L338


lib/biblepaylib.py
create_superblock()
Line 105: if (budget_allocated + proposal.payment_amount) > budget_max:  "# skip proposals that are too expensive..."
https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/lib/biblepaylib.py#L89


So to me it looks like watchman, sorts the proposals before sending them to create in the superblock
and in the superblock creation the proposals get added up 1 by 1 unless they go over the budget limit at which point they get skipped

What was the error that you saw exactly Rob? Im interested to dig into this

If the above is correct, then it should have theoretically skipped the passing proposals that went over budget with the least amount of votes,
specifically the PR Communications Marketing proposal I think, I believe it had the least amount of votes

Hmm....  Ive never seen that ...  We have our own superblock creation function, so our is atomic - either create it right or it blows up.

We dont use watchman for superblocks.

I'll have to take a look at that and see if its of benefit to us.

Probably wont be til tomorrow though. 

[dave_bbp]

Quick recap regarding the shares count on lichtsucher's purepool:

machine                                     24h shares

Raspberry Pi 3 Mod. B:                 55
Core2Duo T9400:                        180
Rented 2 cores (of Xeon X56XX)   300
Xeon E3-1230 v3                         700
Dual Xeon L5640                         2200

Seems perfectly proportional to their computing power.

Those 2 blocks we hit yesterday were obviously pure luck; let's see when we'll strike again.

[slovakia]

dave_bbp very weird for rented 2 CPUs 56xx and dual xeon L5640  ...

[capulo]

maybe he think 2 cores..

for me, dual x5660 >2500, dont know exactly as there was small outage (~2 hrs)