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

[Nipar]

@Togo block explorer seems to be stuck at 153102
@chainz they also seem to be stuck at 153102

Interestingly, when I did getblock 153103 my macOS wallet just crashed. Not saying you should do it, but maybe explorers are stuck because they crashed?

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler

```

did you also notice these two blocks did not require ABN?

153101   3ab96d892f7b683f473b12773d83f0d49aaba0cebbf02b28bb6875f928d5f4a2   2   2265.18550198   Wed, 23 Oct 2019 15:39:56 GMT
153100   c6c37ee47940584215f75d44c5bc2cd91d0039262268962d143151ca8916b390   2   2086.88312508   Wed, 23 Oct 2019 15:37:46 GMT

That does not make me very happy - Im glad we got past 153103.

I confirm that if you type this command, you will crash.

I believe we will need to work on this issue today and fix this next.

Ill make this the next high priority.

the chainz explorer is still stuck at 153102

[1715445904]

1715445904

[1715445904]

1715445904

[1715445904]

1715445904

[bible_pay]

@Togo block explorer seems to be stuck at 153102
@chainz they also seem to be stuck at 153102

Interestingly, when I did getblock 153103 my macOS wallet just crashed. Not saying you should do it, but maybe explorers are stuck because they crashed?

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler

```

did you also notice these two blocks did not require ABN?

153101   3ab96d892f7b683f473b12773d83f0d49aaba0cebbf02b28bb6875f928d5f4a2   2   2265.18550198   Wed, 23 Oct 2019 15:39:56 GMT
153100   c6c37ee47940584215f75d44c5bc2cd91d0039262268962d143151ca8916b390   2   2086.88312508   Wed, 23 Oct 2019 15:37:46 GMT

That does not make me very happy - Im glad we got past 153103.

I confirm that if you type this command, you will crash.

I believe we will need to work on this issue today and fix this next.

Ill make this the next high priority.

the chainz explorer is still stuck at 153102

New release will be out in 30 minutes to fix this;

In the mean time, linux users - and Togo you can upgrade using git pull.

I'll notify chainz right now.

[Nipar]

someone is using the wrong payment address on NOMP pool:
WRK-AJPC-NOMP

whoever it is please use a valid wallet address !!

EDIT: the user was found and has added a valid address

[bible_pay]

someone is using the wrong payment address on NOMP pool:
WRK-AJPC-NOMP

whoever it is please use a valid wallet address !!

Yeah, I also just turned on the feature where the wallet will show 'unauthorized' if they enter an invalid username.

[Nipar]

someone is using the wrong payment address on NOMP pool:
WRK-AJPC-NOMP

whoever it is please use a valid wallet address !!

Yeah, I also just turned on the feature where the wallet will show 'unauthorized' if they enter an invalid username.

Can it detect valid/invalid wallet address?

[bible_pay]

someone is using the wrong payment address on NOMP pool:
WRK-AJPC-NOMP

whoever it is please use a valid wallet address !!

Yeah, I also just turned on the feature where the wallet will show 'unauthorized' if they enter an invalid username.

Can it detect valid/invalid wallet address?

Yeah, the pool actually checks the name with base58, then tells the client to say unauthorized.  So another words he probably stopped mining until he sees the message.

[togoshigekata]

New release will be out in 30 minutes to fix this;

In the mean time, linux users - and Togo you can upgrade using git pull.

I'll notify chainz right now.

Okay cool, Ill upgrade now, Thanks Rob!

[bible_pay]

Chainz has been updated.

They are purring like a kitten again, as usual.

EDIT:  Thanks Togo!

[bible_pay]

BiblePay - Core Wallet
1.4.5.1-Leisure Upgrade

- Prevent wallet from crashing when using getblock to query a block with
missing element

** Release Ready **

[bible_pay]

I wanted to mention this, I believe we are the First coin to support Windows Sancs!

If anyone wants to try it, go for it.  I believe it will work, since we are the only coin with watchman-in-the-wall compiled in.

[Nipar]

NOMP pool miners: connection refused
about 10 minutes now

[bible_pay]

NOMP pool miners: connection refused
about 10 minutes now

Yeah, I went ahead and upgraded it to the new version, give me another 5 mins to restart it.

Sorry for the inconvenience.

[Nipar]

NOMP pool miners: connection refused
about 10 minutes now

Yeah, I went ahead and upgraded it to the new version, give me another 5 mins to restart it.

Sorry for the inconvenience.

Thanks. Not inconvenient just trying to help

[Nipar]

Ubuntu wallet crashed 1450 while trying to update from a week ago.
Downloaded and installed 1451 and -reindex and it crashed again
trying now with -erasechain

Update: success with 1451 -erasechain

[Budinga]

Sorry guys but i have a really silly question.

do i use my worker name or my bbpaddress for the external miner?

Bit confused how it works.

Thanks

For Nomp, it only takes the BBP address currently.  For example here is my command line for windows:

bbpminer-x86.exe -ostratum+tcp://nomp.biblepay.org:3008 --user=BEsraanMpV3tzQ4dhJV1y9EkdEvf8MonF8

Ok so i am doing it all wrong then. I used a worker on the pool for ABN. then i just used that nickname. So i just use the same address for all miners.

It seems to be working now as i am now showing up on the pool. Will see how it goes.
I did notice though that the external miner will not run on my 32bit windows installs, only on x64.


Thanks for the help as always great work

Oh, interesting, I think Ive only been building the win64 build. 
Alright, we can potentially add one more build to the build script.

First, let me take a look at these ABN issues; we have a discussion going on in the other thread about disabling ABN in the current vote.

Ill take a look at this next.

No problem at all just thought i should point it out .

[sunk818]

https://wiki.biblepay.org/Nomp_mining

Now that you turned off ABN, do the directions above differ at all? Is there a difference between easy & hard set up now?

Why do some workers have so many invalid shares?

http://nomp.biblepay.org/workers

[bible_pay]

https://wiki.biblepay.org/Nomp_mining

Now that you turned off ABN, do the directions above differ at all? Is there a difference between easy & hard set up now?

Why do some workers have so many invalid shares?

http://nomp.biblepay.org/workers

I'll be announcing the change in ABN requirements asap.  Of course with the end of the month, there is a lot going on.

I'm looking into the invalid shares.

[bible_pay]

Oh, interesting, I think Ive only been building the win64 build. 
Alright, we can potentially add one more build to the build script.

First, let me take a look at these ABN issues; we have a discussion going on in the other thread about disabling ABN in the current vote.

Ill take a look at this next.

No problem at all just thought i should point it out .

Sorry for the delay; I added windows32 to our build process for the BiblePay CPU miner.

Please try this one on windows32:
https://github.com/biblepay/cpuminer/tree/master/binaries

bbpminer32.exe

I just tested it on windows7 and it appears to work.

[bible_pay]

*** ABN (Anti-bot-net changes) - ABN is no longer required ***



All, we have been discussing potential future growth changes for BBP: https://forum.biblepay.org/index.php?topic=461.msg6381#msg6381
and following the suggestions from the DSS model, showing that we need a positive UPD (+1 or more new user per day), and also with the complexity of requiring people to unlock wallets and support ABNs in the pool(s) is probably not worth the benefit, since we are going to be moving to a new environment soon with stronger anti-bot-net possibilities (rewards for cancer mining/aids, limiting rewards to PODC, etc).

In light of this, I have disabled ABN (the sanctuary vote is largely pointing to this).  This is primarily being done now - so the devs can finish the NOMP pool now with simplicity in mind for the new users.

So, starting now, you no longer need an ABN to mine BBP.  The NOMP pool has been updated to pay equally. 

You may now move to the easy setup, and you no longer need to send single threaded abn's to pool.biblepay.org to mine.

The easy start guide has been modified for NOMP.

Pool.biblepay.org is being modified now to make payouts equal across the board.

(I am analyzing nomp's share rejects today, and will make a post ASAP about that).

[Nipar]

NOMP pool pages are up, miners get : connection refused

15 minutes now

Update: all good now. expecting more ups and downs today