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

@devteam
https://coinomi.com/AddingSupportForANewCurrency/

Hi friend, you are very correct.
Most of time dont even bother replying to fud like that.
Negative attention is negative feelings.
Positive attention positive feelings
God bless

ok. thanks.
I was thinking, that this is report of all wallet version on blockchain
My misunderstanding

They are the only wallets that solved a block in the last 24 hours.

Rob, when I run versionreport it gives me only 1.0.8.1 wallets... why?

  "Version": "Popularity,Percent %",
  "1.0.8.1": "205; 100.00%"

Congratulations!

We have now surpassed the 250 vote goal for the Next.Exchange vote!
https://nextexchange.featureupvote.com/suggestions/3384/biblepay-bbp#comment30547

Apparently, the Next.Exchange team will be contacting us regarding the possibility of being listed. I am unsure how long this will take.

In the meanwhile, feel free to continue to vote/encourage others to vote. Some other coins have vote tallys into the thousands. If we get more votes then we will possibly get more notice from users browsing the next.exchange feature upvote list.

Many many thanks to you all for voting!

The community only deserves posts from Good people.

Biblepay - 1.0.8.2 - Leisure Upgrade

- Fix crash during mining



This has been released for windows if anyone is experiencing a crash.  I'll announce it tomorrow once we determine this is definitely the fix.

I was!  I'm starting to receive enough bbp emails to keep me busy til noon though.

Regarding keeping the botnet off of this version, all we really did was force everyone to upgrade or go off on a fork- if they are official clients, then they would have had to upgrade.  So its possible we still have the same number of clients solo mining again, while the pool is really only 25% of biblepay now.

It would have been necessary for those clients to upgrade because (even though the 7 minute target isnt working), the parameter that was changed required an upgrade to continue on our 1.0.8.1 chain (IE that 7 minute parameter change forced the entire net to upgrade as it changed the future blockhashes).

Regarding the longer term plan, Im receiving some ideas in the inbox, one from West that I will take a look at in a few minutes.  The one Alex and I spoke about in slack was :  Merging in the PIVX stake miner, staking on thread zero.  However Im a little conflicted on this still, as I think we should fully evaluate what we are trying to solve.  I am against a botnet mining for greed with no loyalty, and the idea with the stakeminer is we are rewarding the loyal biblepay user more of a chance to solve a block, by asking them to stake part of their balance for a greater chance of mining that block.  The pool is what complicates this, as people staking a balance to pool mine does not work very well with fractional shares.  However, if we reward a BONUS to the one who found the block in proportion to the amount of BBP they staked (to help the pool find the block) that may work.  Another words, Im leaning on the idea of making it easier to POW mine with staked balances across the board- whether pool mining or solo mining. 

Let me take a look at Wests idea and we can discuss further.

ROB  thanks for fast answer:   are you sleeping? :O

Regarding crashing miners and crashing sanctuaries....

I confirm that half of my nodes were affected through the night.

It looks like the problem is a line of code in 1.0.8.1's instand send fix (for logging purposes) that actually crashes the miner.  I'm not even 100% sure that this is the complete fix, but I am creating an emergency fix for this now.

If you crashed, please upgrade to 1.0.8.2 and lets see if this is the problem.  Alex and I will need to valgrind this later today to know for sure.

In the mean time, the unofficial release is out there for 1.0.8.2 for linux only.

tommorow im updated to new protocol MN,i hope that is OK

We now have only about 54 Masternodes running ?
I see many with stauts EXPIRED and NEW_START_REQUIRED
Only 43 is ENABLED and 11 WATCHDOG_EXPIRED

next update will be 15% blocks

what i see,new update wil be worse, lol

So, in 3 days hopefully we will see CCEX back. Although I am not sure they will have BBP available for withdrawl/deposit as the wallet is still in maintenance.
Anyone knows anything otherwise?

Thanks!

% is couning with 200+ blocks/day but we are on 150/day, so it should be around 20-25%
but still bad

my miners crashing too

is there any problem with pool again? more miners crashed/missing

It's kinda strange, but it's actually loading if you are patient. The browser doesn't show that it's loading, but it is, and I think it's like that only the first time. The desktop app loads fine for me.


Actually, it isn't related to the number of coins, but the number of masternodes controlled by a single entity. Since Instant Send goes through 6 masternodes for confirmations, someone who has 6 or more masternodes could do something to improve their chances of being selected for a transaction. Then they could send themselves some coins, then double spend it and also confirm the second tx with their masternodes, even though that second transaction would be invalid otherwise.

Before this BiblePay update, I was researching about Dash Instant Send and found about that bug, which was fixed by Dash at the time, but BiblePay was forked from Dash just before the version in which that was fixed. So I notified Rob about my findings, and he was very quick to issue a patch. He said 10M BBP just because that's the rough amount when you multiply the amount of coins needed for 6+ masternodes. So for Dash it would be "just" 6000+ coins. I presume he said it like that to not expose how it's done until it's patched. Now that more than 90% of nodes are on 1.0.8.1, I guess it's fine to share for learning purposes?

Read more about the vulnerability here:
https://themerkle.com/dash-developers-disable-instantsend-on-the-network/
There's also a forum link in the article which goes into more depth.