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

on pool disappeared 99% miners  

Great job on the Pi man!

hasps = 7 k.  I have just got the latest version of wallet and will try now to operate solo for a few days and see how much luck i will have...

Exactly. But the shares system is only on the pool, isn't it? Or does it apply to solo as well?
By the way, how much hashps does that Ryzen give with 16 threads?

@dave_bbp
how many hashps does your weakest dual xeon get?

We are over halfway to the 250 vote goal!
As I write this we are at 129 upvotes.

If you have not yet voted to get BiblePay considered for listing on Next.Exchange, please do so!

If you know of anyone sympathetic to our cause, please ask them to vote, if their conscience agrees.



Please note that we can only get 50 votes per day and we have around 20 or so left for the next 12 hours or so

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

So how does the update to 1.0.7.9 technically work? Since it is mandatory, I thought this would mean it has some effect on the blockchain. But you said there wouldn't be a certain block, so it hasn't? That is a bit confusing, how is it mandatory then? For example the botnet could just stay on the old version and keep on mining.

On another note: just as a tip to people with more powerful machines (Ryzen, DualXeon etc.): try going solo for some days and test your luck. I have one of my Dual-Xeons (actually my weakest one...) on solo mining for maybe 5 days now (just updated to 79) and it already found 2 blocks (overall more than 10k BBP per week). Of course this could be pure luck, but it definitely is worth a shot!

So how does the update to 1.0.7.9 technically work? Since it is mandatory, I thought this would mean it has some effect on the blockchain. But you said there wouldn't be a certain block, so it hasn't? That is a bit confusing, how is it mandatory then? For example the botnet could just stay on the old version and keep on mining.

On another note: just as a tip to people with more powerful machines (Ryzen, DualXeon etc.): try going solo for some days and test your luck. I have one of my Dual-Xeons (actually my weakest one...) on solo mining for maybe 5 days now (just updated to 79) and it already found 2 blocks (overall more than 10k BBP per week). Of course this could be pure luck, but it definitely is worth a shot!

It looks like we hit our 50 vote per day limit. Great job everyone!

Anyone who tried to vote after the count was 51, could you please try again tomorrow?

second:

I think we need to find a way to 'block' the botnet.
I am not against solo mining. I am against solo mining with the profit going to wrong people. I think that's not the idea of the coin.
It feels pretty wrong and bad.

But, I also know it is quite hard/maybe even impossible. Are there coins that prevent solo mining??

Some suggestions:

New mandatory update, that would cripple there botnet for a while.
And we can find out if the theory is correct.

Make some 'registration' for solo miners.
If you are solo mining you need to provide a identification token that can be validated. The identification token must be requested 'by hand' via the pool/block chain.
ie: preventing automatic setup, users need todo some steps in order to be able to mine the coin. This way legit users can solo mine but botnet are likely to stop since it's lots of manual labour.

Could be something like a hash that need to be requested via a webpage with a captcha on it so that it can't be automated. Or anything.
Or block all solo mining (if possible). But that would be the least favourite option.
(although I think that if you have a low power cpu there is no reason not to join the pool, and we can prevent users from running there pc without any reason. Since the users with low cpu are probably less experienced miners)

What do you guys think?


p.s.

I can help with some work, I work as a javascript (nodejs/polymer) and java developer. C++ is a while ago, but at least I can help testing and think about solution maybe.

Sorry for the ambigious post and zero day deadline.

There are a lot of reasons for this, none are optimal:

- The upgrade is system wide for both core clients and sanctuaries.  Primarily because the instand send change requires a new instantsend vote algorithm, so we needed the entire network to upgrade (the sender and the facilitator and the receiver).

- There is no block number in this case, because the cutover involves a protocol change and is not driven by a block.

- Unit testing "appeared" to succeed, so I pushed 1077, and then discovered an additional bug.  That left the network partially upgraded and in a state where the only way to fix it is to force a mandatory the rest of the way.  (With 1.0.7.9).

- I want to get a supermajority of sanctuaries upgraded on 1.0.7.9 relatively soon since we only have 7 days left before c-cex reopens, and he said he might be opening early and I have a message in his inbox to compile BBP.  

As far as whats going on behind the scenes, the code wants 10 instand send Votes on 1.0.7.9 before it falls through to Sign the transactions, and 1.0.7.9 requires these votes to be placed within 60 seconds.  What Im seeing in the log is about 6 votes, but after trying 50+ times, Im still only seeing 6 votes.  Im under the impression that we just have to wait for more Sancs to upgrade to 1.0.7.9.

The only coins that can be lost are:  Coins mined on a fork, coins sent to an address you do not control, or coins in a lost wallet.

But coins sent from the wrong version to a wallet you control can be tracked.

PM me the txid.

mandatory to who? all or only sanctuaries?
and what block number to apply?

Oh no... I hit a manual withdrawal from the pool, and noticed that it didn't go through. I just saw this and I was running 1.0.7.6.
I suppose my coins are now lost as my client was on the old version?