BiblePay (BBP) | 10% Charity | POW/POS | CPU Only | Masternode | No Premine

[coinsinspect]

I know the botnet is not back, because we have a 125K abn requirement.

One other nice hack the external miner relieves us of is the issue where we copy the wallet.dat out to many machines - with one bbp running node you can mine on multiple miners without copying wallet.dat.

Do you think a higher difficulty warrants high ABN? It sounded like you want to reduce ABN so the mining would not need much BBP to stake.

Can you explain a little more about not needing to copy the wallet.dat ?

We still need to run a node (biblepay-qt or biblepayd) but a blank wallet.dat is okay as long as one BiblePay wallet is running with the required ABN stake? That is news to me and sounds like a more secure way to mine. If mining is easier, I'm thinking it'll be easier for botnets to be set up too... if you set ABN to 5k, it wouldn't take much to mine continuously. Is there some way to keep botnets away without needing to stake BBP for ABN?

1) On the one biblepay node, multiple miners, like Nipar explained you can do that - the key is in the biblepay.conf on the single running node to do the :rpcallowip=ipv4 - one entry row per mining machine.  On the ABN question, yes that single node would need to have a high enough balance to cover all the ABN activity (IE 10 mining machines might need 1.25MM etc).  That particular wallet still needs unlocked, so that it can generate ABN's for the miners.  Its the same as required now, except concentrated against one node.  The nice thing about it though is we dont tell people to copy wallet.dat out to mining machines, and, its a little more efficient as you dont run multiple biblepays just to mine (I suppose thats better for our governance data and bandwidth consumption also).

2)
"
Do you think a higher difficulty warrants high ABN? It sounded like you want to reduce ABN so the mining would not need much BBP to stake.
"
->  Well, this is a definite conundrum.  On one hand, higher difficulty would dictate a higher ABN requirement if we go the "common sense route", but, the 'cryptocurrency economy model' is starting to explain to us that in order to attract many new users/miners, we have to lower the barrier.  This means we have to choose between these dimensions:  Less users/low diff/lower investor buying activity/more profit for a few - and risk of a collapse of the coin, or  b: more users/higher diff/higher buying activity/less profit per mined block/a more stable community.  So, I also realize, we are trying to protect our miners interests by blocking the botnet also - so it sounds as if a zero ABN is not good either.  Maybe we keep thinking about it - and ideas where we block the botnet - but increase user count.  All I have so far is the idea it might be good to lower the ABN req. to 10,000 or whatever, something that is a low barrier but would still afford some protection against a person who might install biblepay in a school system etc.  

[coinsinspect]

BiblePay - External CPU Miner
1.0.0.6-Mandatory upgrade for Miners

- Prevent crash during big blocks

Binaries:

https://github.com/biblepay/cpuminer/tree/master/binaries

[coinsinspect]

** BiblePay - New NOMP Pool - Opening in BETA mode for testing **



I am proud to announce our new NOMP pool is now opening in Beta mode.

You must use the BBP external miner to mine against our NOMP pool (as nomp requires stratum).

Note, that ABN's are going to be supported, however today all the shares temporarily pay the same amount (as ABN is not configured on the server side yet).

The goal today is to ensure the shares are being accepted in prod, the miners do not crash in stratum mode, the miners continually receive new work, and that we can actually solve blocks in prod.  Also, we need to ensure payouts work correctly from the NOMP side.

Regarding payouts:  NOMP pays every 15 minutes, but does require each solved block to be fully matured; here is an example of how your payout would work:
Miner A solves block 100,000.  NOMP records this miners shares and BBP address in the database (even if you stop mining, NOMP will remember your work).
At block 100,120, NOMP will see the block has matured.  Within 30 minutes, it will distribute all of the payouts (for every share that participated in that block).
So from a high level, you will be paid about 12 hours later for shares you solved.

WEB SITE URL:

http://nomp.biblepay.org

I have added some preliminary instructions on how to mine against NOMP on the home page.  Please see the wiki.

Basic configuration from our external miner:

https://wiki.biblepay.org/Nomp_mining
(See the Easy setup section)


As soon as ABN is configured on the server, I will post and explain how you can see your ABN status and ABN payout information, etc.

[coinsinspect]

BiblePay - External Miner
1.0.0.7-Leisure Upgrade

- Fix windows crash
- Fix issue where miner discards fresh work
- Deal with block size dynamically, to avoid memory problems.


https://github.com/biblepay/cpuminer/tree/master/binaries


** The updated server side NOMP code has just been released, so please, start testing over again and let's look at the ABN shares vs. worker shares as we solve them and verify these are incrementing correctly now.

Please upgrade to the new miner before NOMP mining as the prior version(s) had a work discard bug.

[coinsinspect]

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

[coinsinspect]

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 **

[coinsinspect]

*** 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).

[coinsinspect]

BiblePay - External CPU Miner
1.0.0.8-Leisure Upgrade

- Prevent submitting duplicate shares
- Handle time encoding correctly

** Ok guys, it appears the lions share of the problem with the pool was the time encoding and submission of duplicate shares.  Please upgrade the external miner, and try again with Nomp, lets see if the valid share percentages rise now. **

[coinsinspect]

External CPU Miner
1.0.0.9-Leisure Upgrade

- Ensure time is encoded properly for both stratum & non-stratum modes

** Ok everyone, the 1008 version is really not a working release.  I believe this version actually addresses the problem; please try now. **

[coinsinspect]

i went to pog so i browse how it worked ... and found this guide
https://wiki.biblepay.org/Getting_Started_with_Evolution
but exec sendgscc is not working anymore...
update is needed

btw how can i check if my wallet is already joined to pog? i'm not sure if i not leaved or so
sendgscc not thrown any error

1)  Its now : sendgscc instead of 'exec sendgscc', so you can type for example:  sendgscc pog 100, that would send a donation of 100 bbp to the foundation.
2)  If you leave the miner running on one thread with the wallet unlocked, it will send one sendgscc out every 12 hrs.
3)  You can try to type : exec join pog,  and it will throw an error if you already joined.

[coinsinspect]

1) can we have lower difficulty? Even 3 diff is kind of high for some computers. Could you offer difficulty of 1 or lower perhaps?

2) Wrote some new articles:

I downloaded the Biblepay wallet but it doesn’t sync, why?
https://whitewalr.us/2019/biblepay-wallet-sync-issue.html

How do I mine on the BiblePay NOMP pool?
https://whitewalr.us/2019/biblepay-nomp-pool-mining.html

3) I get disconnected from pool sometimes. I just communicated with it so I am not sure why this is happening.

stratum_recv_line failed
Stratum connection interrupted

I tried temporarily from different networks (usa, europe, asia, etc). it seems to happen regardless of where my miner traffic originates from.. i wonder if pool can handle all the workers?

is anyone else seeing the disconnect?

4) i let some miners run overnight and I think invalid shares is high again. out of 1050 submitted / only 1010 accepted. So, something like 96.1% accept rate. saturday day worked very good. but saturday night maybe more people joined pool, i don't know.

[coinsinspect]

BiblePay
1.4.5.2-Leisure Upgrade

- Fix exec paycameroon feature to use current bbp price
- Fix exec price to show current bbp price

** This is the windows release.  MIP will update when linux is ready **

[coinsinspect]

By the way, the DIP3 link is not working :
https://wiki.biblepay.org/Evolution_Upgrade

Here is a working link:
https://docs.dash.org/en/0.13.0/masternodes/dip3-upgrade.html

Are these the steps to upgrade masternode to deterministic?
https://bitcointalk.org/index.php?topic=2388064.msg51695886#msg51695886
https://www.reddit.com/r/BiblePay/comments/clyxyc/upgrading_masternodes_sanctuaries_to/
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

EDIT:
This worked for me.
I noticed that you need to keep the old line, so the sanctuary will not exit:
masternodeprivkey=nnnn

[realdantreccia]

I can't get my wallet to sync pat 99.26% (10 days behind). I upgraded to the latest Windows 64-bit version from biblepay.org...

help?

[realdantreccia]

Here is what my debug says:

Code:

2019-11-04 14:34:04 init message: Loading addresses...
2019-11-04 14:34:04 Loaded 44315 addresses from peers.dat  116ms
2019-11-04 14:34:04 init message: Loading banlist...
2019-11-04 14:34:04 init message: Starting network threads...
2019-11-04 14:34:04 net thread start
2019-11-04 14:34:04 dnsseed thread start
2019-11-04 14:34:04 addcon thread start
2019-11-04 14:34:04 opencon thread start
2019-11-04 14:34:04 msghand thread start
2019-11-04 14:34:04 mncon thread start
2019-11-04 14:34:04 init message: Starting Miner...
2019-11-04 14:34:04 BibleMiner -- started thread 0.000000 
2019-11-04 14:34:04  ** Started 1.000000 BibleMiner threads. ** 

2019-11-04 14:34:04 init message: Done loading
2019-11-04 14:34:04 GUI: Platform customization: "windows"
2019-11-04 14:34:04 GUI: PaymentServer::LoadRootCAs: Loaded  68  root certificates
2019-11-04 14:34:15 Loading addresses from DNS seeds (could take a while)
2019-11-04 14:34:15 1 addresses found from DNS seeds
2019-11-04 14:34:15 dnsseed thread exit
2019-11-04 14:35:00 ERROR: AcceptBlockHeader: block 10d7b6ebc06d41a4c7b1059470af579a4cc24ff7ffefe8e10f135525fae39038 is marked invalid
2019-11-04 14:35:00 ERROR: invalid header received
2019-11-04 14:35:00 
ios_base_failure::mesg_fail::ProcessMessages(headers, 161031 bytes) FAILED peer=0
2019-11-04 14:35:00 Misbehaving: 134.209.2.19:40000 peer=0 (0 -> 1)

[coinsinspect]

Try asking in the main thread:
https://bitcointalk.org/index.php?topic=2388064.new#new

Rob, the main developer, is very helpful.

[coinsinspect]

I am using under Windows 10:

Code:

bbpminer-x86 -o stratum+tcp://nomp.biblepay.org:3032 -u MINING_WALLET -p x

Or:

Code:

bbpminer-x86 -o stratum+tcp://5.135.183.202:3032 -u MINING_WALLET -p x

Both returns rightaway:

Code:

KJV Loaded
Using bbpminer version 1009

solo mining 0
[2019-11-10 08:57:12] Starting Stratum on stratum+tcp://5.135.183.202
[2019-11-10 08:57:12] 4 miner threads started, using 'pobh' algorithm.
[2019-11-10 08:57:12] Binding thread 3 to cpu 3
[2019-11-10 08:57:31] stratum_recv_line failed
[2019-11-10 08:57:31] ...retry after 30 seconds

Last two lines in a loop (new line every 30 seconds).
Perhaps my hashrate is slow as I've been disconnected since 4th of November. But I cannot mine with the wallet client as well since then. The biblepay.conf file:

Code:

gen=1
genproclimit=3
minersleep=0
pool=tcp://5.135.183.202:3032
workerid=zupernovato1
workeridfunded=zupernovato2

But with getmining info:

Code:

...
"poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; ",
"poolmining": false
...

Do I need to register workerids on the new pools hosts?

Do I need to turn onh WCG-BOINC once again in team BiblePay? (I've read something about it in the recent pages of this thread).

1) I've tested your bbpminer-x86 external miner config and it seems OK, it works for me.  I dont think you need the "-p x" at the end, but it should not be a concern.
2) I don't think its your hashrate; it doesn't sound like you ever get to the point where the miner is showing the hashmeter.  After a couple minutes you should see 'thread 1: nn KH/S'.  You can try adding "-t1" to mine on a single core (this would put more availability to one thread) and see if anything happens, but imo I dont think its the hashrate.
3) You can take out the workerid, workeridfunded, and pool settings in the biblepay.conf as currently pool.biblepay.org is out of play in favor of nomp.  Basically the internal miner in the core wallet is not being used for mining, but we are using the external miner now.  (I do have a side project to fix that, so they are equal, but for now lets all use the external miner to be equal in speed).
4) You do not need to register any workerid now, you can just use a valid BBP receive address.  Please do verify the receive address you use is valid (you get it from the core client Receiving address, or, from 'getnewaddress' . <- I would look at this as this could be the problem, nomp may be hanging up on you if its a bad address.
5) You don't need to have boinc on *yet*, but, we are going to require users to be on team BBP for WCG very soon - IE within 30 days - to earn PODC2.0 credits.  See this thread if you want to help us:  https://forum.biblepay.org/index.php?topic=465.msg6515#msg6515

6)  If none of this helps, please try the external miner on another machine and see if it works with the same settings.  If it does, you might have a bad binary on win10, just re-download it.
7) You can also try this:  telnet nomp.biblepay.org 3032
Verify the screen clears.  This shows you have a connection to the stratum port.  There is a remote chance you have a blocked firewall in win10?

[coinsinspect]

https://i.imgur.com/27JnOUk.png

i like big blocks and i can not lie

download the miner here:
https://github.com/biblepay/cpuminer/tree/master/binaries

join the pool and earn BBP rewards here:
bbpminer-x86.exe -o stratum+tcp://5.135.183.202:3032 -u BEXTU6iVeBdoqgwbP8rmzYNoKhQgwz5BGs -p PraiseJesus

-u is your bbp address
-p password can be anything

other pools:

nomp.biblepay.org
leopool.biblepay.org

[coinsinspect]

** BiblePay Prod Quick Sync **


I'm working on a quick sync script for prod to be released during our PODC 2.0 release - so Windows quick-sync is not ready yet, but in the mean time if anyone wants to test this the linux version is ready:

For biblepayd or biblepay-qt do the following for quick-sync (this is syncing fast from block 0, an alternative to -erasechain=1):

Do this part once:
cd ~/.biblepayevolution  (Be sure to cd to where your Biblepay data directory is first)
wget biblepay.org/syncblocks_prod.sh
chmod 777 syncblocks_prod.sh

Whenever you want to sync from 0:
cd ~/.biblepayevolution
./syncblocks_prod.sh


The script automatically gracefully stops biblepay first.  We do sync the prayers, blocks, llmq & chainlocks, and governance data, so theoretically the node should be stable after this.
You do have to start biblepay manually after this is done.

[coinsinspect]

** CAMEROON-ONE WALLET ADDRESS CHANGE **


Cameroon is migrating to a new wallet (and the old key is no longer available).

Please do not use the 'paycameroon' command until the next update, and please do not send any funds to the address in 'sponsorchild'.

We will be making this an adjustable spork in the next version (our testnet version) but for now we will release a leisure upgrade to fix this in the next day or so.

The new address is:
BF6qmwBMmnmb4FbSmRGTeWQL1m3rwh5n7b