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

It's being redeployed but it takes a while due to the last step - I believe it will be out in < 10 mins (roughly).  I'm waiting for it and will re-post when it redeploys successfully.

Rob, does this mean you believe .8 is out there now?

Polish patriot makes parade float with Hillary Clinton, Obama and Trump:

https://twitter.com/PolishPatriotTM/status/1143233269707825153

I don't have any opinion or political view on this, except that we should continue to pray for our appointed leader.

Windows is working great, Slovakia, please see PM.

Its being regenerated; glitch being fixed now; 1438 will be redeployed very soon.

Is this by plan Slovakia or just a miss on the page setup? Do you know? Seems like the .8 release is supposed to fix some of the non responsiveness of the gui

Hmm your right, let me check whats wrong.

Is 1.4.3.8 out for 64bit Windows?? Only downloading 1.4.3.7 from the link

i never experienced 'delay' like now with 1437 version, even if i was trying multiwallets= i started 128 wallets, each with 40 threads on one 24 core machine... there was no problem to run bbp cli commands and get response immediately
i'm going to try 1438 now

Could someone that experienced a deadlock after finding a block, or a lag try 1.4.3.8?
MIP has already deployed all versions.

This version technically only addresses the deadlock after finding a block (not the lag).

One other thing I need help with:  Please try minersleep=10 and multiple threads, let me know if the lag stops but the HPS is still 99% high (as since threads overlap, you should still technically get the HPS from the machine).  We just want to see if the UI is usable.

I make all assumptions that you are running QT and having a problem typing commands in the debug console.  Not in the linux bash shell.

BiblePay
1.4.3.8-Leisure Upgrade

- Add spent_amount and spent_time to getrawtransaction output
- Add POG rule to prevent sanctuary scalping
- Added deadlock mutex in CreateAntiBotNetTransaction

Well the reason I ask is we really had the same hashpower before ABN, and the only difference with ABN is it creates an ABN transaction before it starts mining.  Thats not a huge dent in horsepower (since a transaction is guaranteed to last at least 60 seconds).

So when you say lag, please tell us if you used to lag before ABN, or if this is new.  And what does lag mean exactly?

Im running a windows miner with just 5 threads, and I can type fine into the debug console in QT and notice no lag.  But I have always been afraid to set up 20 threads - regardless of ABN or not, as the whole machine starts to lag.  Which is normal if you use 100% of the processor on every core.

i'm using linux binary, biblepayd and biblepay-cli. i run 'biblepay-cli exec getabnweight 256000 1' and need to wait few minutes to get results
wallet is still running, sometimes it works instantly, sometimes i must wait


btw i have several orphan tx in log:

  {
    "account": "",
    "address": "BH47JYAojbjMntpTY1xAf16pApKtc5k1mb",
    "category": "orphan",
    "amount": 3276.10000611,
    "vout": 0,
    "confirmations": 0,
    "instantlock": false,
    "generated": true,
    "trusted": false,
    "txid": "a1e5a6fa70a1c5d53fa70ea65fd2c74c821e8be7fdf8f89ade7a23f05220a5cb",
    "walletconflicts": [
    ],
    "time": 1561484920,
    "timereceived": 1561485171
  },
  {
    "account": "",
    "address": "BAyu8o73Vk3FMpUn8s9ub4Y14muDBdLXWa",
    "category": "orphan",
    "amount": 3240.99597774,
    "vout": 0,
    "confirmations": 0,
    "instantlock": false,
    "generated": true,
    "trusted": false,
    "txid": "603a6e7594b61430dd2b8408f46a9201a958c2c252c3129ed7837b6e37b49823",
    "walletconflicts": [
    ],
    "time": 1561488625,
    "timereceived": 1561488755
  },
  {
    "account": "",
    "address": "BPtKaCXTBX3VLvGQevS23awdXHcjERwPsz",
    "category": "orphan",
    "amount": 3291.33382975,
    "vout": 0,
    "confirmations": 0,
    "instantlock": false,
    "generated": true,
    "trusted": false,
    "txid": "b8824db9b3eaf06e723c4660f45fb00a1fd9caafda191a97f04f97f78ba45223",
    "walletconflicts": [
    ],
    "time": 1561489787,
    "timereceived": 1561489907
 

Hi,
now I'm using all of my coins only for mining.
Today I solved 9 blocks. I'm using 1436 version on my VPS and 1437b on WIN. Yes, it is laggy, but it works. It looks that I need around 2 hours to reach 256k weight again, I hit the block, It spends all of my coins for ABN and then it goes round and round again. I have not used  exec bankroll, but maybe I ll try it. But definitelly it looks, that it is not neccessary, because when you mine all the time, I always hit the block right after all of my coins have coinage 256k and they are spended all.

What are your thoughts on limiting coin age to 1 day for PoG rewards? Someone could stop PoG for a week, then their 25M gets more BBP for that day once a donation is made. Limiting coin age to 1 day means continuous giving is encouraged rather than donating in spurts to dominate for a specific day. This would have the desired side effect of limiting the value one would get from an aged masternode.

Best solution we have for overloading the server with > 20 threads:

- Upgrade to 1.4.3.8 to prevent deadlocks (out in a couple hours)
- Run the miner with a very high thread count, overloading the server and procs

To access the machine, use biblepay-cli:
./biblepay-cli setgenerate false

Then administer the machine, then restart the miner using cli again, etc.

This type of thread management problem is basically why most mining programs end up being external, but here - we only support full nodes with BiblePay.

No difference.

When you say freezing do you mean you cant type when its mining, or it only freezes when it finds a block?  Please describe in great detail what you mean.

And if you use qt.

is there any difference between minersleep=0 and minersleep=-1?
my wallet freezing also, but i need to have >20 threads as i have 40 cores...

On a side note, I put in a deadlock preventer for the next release; we will get it out if we hear any more reports of a freeze after a block is solved.

In the mean time though, your 0% cpu usage is because you have low abn weight.

Once the ABN is spent, your miners stop running until you replenish your abn weight.

It was frozing but CPU load was 0-1% for biblepay

I changed the conf to the following and it's not frozen


CPU load still 0-1%