NOMP pool pages are up, miners get : connection refused 15 minutes now Update: all good now. expecting more ups and downs today It's getting there now finally; looks like we did have a couple issues...
|
|
|
*** 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#msg6381and 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).
|
|
|
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/binariesbbpminer32.exe I just tested it on windows7 and it appears to work.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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 **
|
|
|
Chainz has been updated.
They are purring like a kitten again, as usual.
EDIT: Thanks Togo!
|
|
|
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.
|
|
|
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.
|
|
|
@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.
|
|
|
@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.
|
|
|
@Togo block explorer seems to be stuck at 153102 @chainz they also seem to be stuck at 153102
I have 153107 on my own wallet.
Did anyone notice these two transactions 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
I am about to propose that we disable ABNs based on the DSS thread winning, and, the complexity its causing in the pool reqs and for the sake of onboarding new users. So I just temporarily disabled ABN reqs while I put this code test together in nomp without abns; I will make a post for this today. EDIT: Ill make sure I add my vote first, but its clearly looking like it will be approved.
|
|
|
Let's get it to be stable and working properly first, and be an appropriate replacement for pool.biblepay.
Then, I will enable the github "issues" on that branch also - the branch is already checked in, but its not ready for github issues quite yet.
EDIT: Nomp does have a configuration for recouping costs; we should expose that under the home page. Ill look at doing that also.
Ill also look at MH/KH.
Great work as always! I've never ran a pool before but I have a kimsufi dedicated servers I got for 3.99€/mo so maybe I can convert one of those to run a pool. Having multiple pools will indicate there's interest in the community and adds to the decentralization effort. It really saddened me to see Licht retire purepool after some time. When Licht gets wind of this stratum pool I think purepool will likely be back. Status: 0/unconfirmed, in memory pool Date: 10/23/2019 11:52 From: unknown To: BSMeRjiLxEm2CurJ4ZnQgJio58RSgdfNi6 (own address, label: NOMP Pool 121) Credit: 315.47545186 BBP Net amount: +315.47545186 BBP Transaction ID: 00bbb4c6a0c957426bf55623b547b1cc312d3fd01ab9c689676e61d3c6aa3427 Output index: 3 Transaction total size: 480 bytes
Credit: 315.47545186 BBP To: BSMeRjiLxEm2CurJ4ZnQgJio58RSgdfNi6 315.0000 BBP Got my first proper NOMP pool payment just now. Thank you !! No idea though for what period of time, what blocks the shares came from or any other pertinent information. That will come later I hope. I have run a NOMP pool before but getting miners was tough. Maybe for fun I try again, family pool or something Great! Yeah, I see how opaque the payment system is. We probably need to dump the data out of redis into something we can understand and make at least a running transaction log. If we had the miner address, the payout amount and height in a running log we could at least expose that on the web and make sense of whats happening. First let me switch over to the new wallet.
|
|
|
Let's get it to be stable and working properly first, and be an appropriate replacement for pool.biblepay.
Then, I will enable the github "issues" on that branch also - the branch is already checked in, but its not ready for github issues quite yet.
EDIT: Nomp does have a configuration for recouping costs; we should expose that under the home page. Ill look at doing that also.
Ill also look at MH/KH.
Great work as always! I've never ran a pool before but I have a kimsufi dedicated servers I got for 3.99€/mo so maybe I can convert one of those to run a pool. Having multiple pools will indicate there's interest in the community and adds to the decentralization effort. It really saddened me to see Licht retire purepool after some time. You will be in for a pleasant surprise when installing this one. Compared to pool.biblepay.org. This one can be installed on a linux box with only a couple paragraphs. Ill be sure to update the build instructions as it was pain free on both boxes. The entire headache Ive had this week had to do with ABNs.
|
|
|
for nomp, under hashrate per pool, it is showing gigahash after kilohash. probably should be megahash too I assume.
is there a github to submit pool issues?
do you plan to offer vardiff so pool adjusts difficulty automatically based on the worker hash rate?
Let's get it to be stable and working properly first, and be an appropriate replacement for pool.biblepay. Then, I will enable the github "issues" on that branch also - the branch is already checked in, but its not ready for github issues quite yet. EDIT: Nomp does have a configuration for recouping costs; we should expose that under the home page. Ill look at doing that also. Ill also look at MH/KH.
|
|
|
Here's a look at what happened overnight: Pool Algo Workers Valid Shares Valid ABN Shares Invalid Shares Total Blocks Pending Confirmed Orphaned Hashrate biblepay x11 3 10617 8197 0 24 5 3 2 572.66 KH I doubt we solved 14 blocks over night but if we did, wow. lol Hopefully we solved a couple and provided enough data to sort something out. Thanks, I am looking at making a dedicated wallet for the pool next (in contrast to sharing the wallet with the other pool). One thing I have to do first however is check to see if ABNs are actually preventing us from mining. Im working on this next.
|
|
|
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.
|
|
|
hi to all,
where i can to find problem with 1007 version, still crashed after any time win 10
thx
No crashes have occurred in 1007 for any of the win boxes. If you crashed, please take a screenshot of 'bbpminer -x1', then one of the crash, then one of the command line, and the events that led up to the crash.
|
|
|
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
|
|
|
|