Quote from: jsheets1970 on October 02, 2019, 09:01:20 PM

Quote from: bible_pay on October 02, 2019, 08:31:05 PM

Quote from: jsheets1970 on October 02, 2019, 06:57:38 PM

Quote from: bible_pay on October 02, 2019, 06:15:50 PM

Quote from: jsheets1970 on October 02, 2019, 03:04:56 PM

Quote from: bible_pay on October 02, 2019, 01:12:51 PM

Quote from: slovakia on October 02, 2019, 06:45:16 AM

08:41:46

{
  "blocks": 148626,
  "currentblocksize": 1193,
  "currentblocktx": 1,
  "difficulty": 3089.850267970606,
  "errors": "",
  "pooledtx": 1,
  "chain": "main",
  "genproclimit": 30,
  "networkhashps": 422039.041587423,
  "hashps": 0,
  "minerstarttime": "10-02-2019 05:52:50",
  "hashcounter": 0,
  "pooledtx": 1,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "Pool mining with canopus; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
  "poolinfo2": "RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:49; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; RMC_10-02-2019 06:40:48; ",
  "poolinfo3": "",
  "poolinfo5": "Internal ABN: Invalid 1569998449; ",
  "abninfo": "No block to mine... Please wait... 1569998512; No block to mine... Please wait... 1569998511; No block to mine... Please wait... 1569998511; No block to mine... Please wait... 1569998512; No block to mine... Please wait... 1569998511; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998511; No block to mine... Please wait... 1569998511; No block to mine... Please wait... 1569998512; No block to mine... Please wait... 1569998512; No block to mine... Please wait... 1569998511; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998511; No block to mine... Please wait... 1569998511; No block to mine... Please wait... 1569998512; No block to mine... Please wait... 1569998511; No block to mine... Please wait... 1569998511; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; No block to mine... Please wait... 1569998510; ",
  "gsc_errors": "low abn weight 0",
  "poolmining": true,
  "pool_url": "https://pool.biblepay.org",
  "required_abn_weight": 125000
}

im sent 250k bbp to friends wallet yesterday, wallet is unlocked. We must wait for coinage?

Yes, if you sent 250K, you would need to wait about 12 hours to have 125K coin-age.

Just keep typed 'exec getabnweight 125000' until the ABN says OK.

This right here is a perfect example of one of the things that is holding back this project from achieving the success that it should be seeing. This exact scenario has been discussed a lot but I am not sure if the documentation is hard to find or hard to understand. Slovakia, I believe the issue here is in the configuration of your friends machine. Yes they have been sent 250K but it has not aged enough to mine with their own funding. So, what needs to happen in my mind is not to wait for it to age, but rather modify the miner configuration. This user is mining on the pool but is mining with a worker that is setup with a Funded value of 0.. In that case it is a self funded miner. What needs to happen is create a second user that has a funded value of 1 in the worker list and then modify the conf file to look like this

workerid=Worker name with value of 0 in worker list
workeridfunded=Worker name with value of 1 in worker list

I call this configuration the hybrid configuration as it allows the user to bounce automatically back and forth between self funded and pool funded mining. This user should be mining right now with the workeridfunded user id and getting a percentage of their hash based on the pools dynamic calculations and then when ABN reaches the required 125000 it will automnatically switch to workerid and use self funding. IM me directly if you have any questions.

Yes, I agree with you. I've been looking at some of the elements of this project that make it hard on newbies:

- Being unable to mine with encrypted wallets - unless they know how to set the unlock phrase (maybe we should 'escrow' the ABN in a specific purse, so the wallet does not need unlocked - by the miner ever) <- This is a little nauseating/embarassing anyway I think
- Not understanding the nature of the ABN requirements
- Maybe we are becoming too "clubby". You have to be in the exclusive club to mine BBP (since we require funded ABNs). Maybe we vote to turn off ABNs.
- Nonstandard pool. I'm taking a look at the official dash pool (p2pool) now; I may take a look at the work effort in porting POBHs requirements into P2Pool. The advantage here would be the people that complained about not understanding how to deploy a pool could them deploy p2pool for POBH.
- Should we go back to the most simple environment possible, where we can mine out of the box.

I'm sure there are more things like this in our other areas, but this "feels" like the extent of the barrier on the POBH (heat mining side).

As far as GSC's go, I still like how veterans can earn a reward for latent BBP - its similar to earning interest - and right now the only ones who get it are those who tithe something (and with QT on, thats important because we need to pay compassion every month). The POOM project is still in its infancy. So far, I feel thats relatively good and successful although it does emit a lot of selling pressure, but we are making a big impact with POOM. So I feel the GSC side is pretty positive for BBP - regardless of the learning curve of what a CPK is and how to join a project.

I've discovered a couple large bugs in DSQL, so please hold off on testing in that thread until we fix these.

All interesting ideas for sure and things to think about.. I am not sure I would eliminate ABN but perhaps lower the amount. The feature is a nice to have for sure and think it keeps away some elements. Perhaps what we need to do on some of these things is have a more structured repository with Configuration files and examples. Better documents to explain setup.. And possibly remove the 1 click mining feature as it seems to cause more harm then good. Also a way to not have to resync from the beginning of the block chain for when people get some strange behaviors. The project is good and the features implemented are good, but I feel like we are trying to put in too many new features without first ensuring the community and new people know how to use the existing features.. Just my 2 cents

I think we consider lowering ABN for a little while until we have > 100 active miners in the pool.

10-4 on the other points.

I'll look into p2pool next to see if helps us "standardize" our pools. It might be a big boon to have a dash-evo compatible codebase - just in case all the devs get raptured and BBP is forced to bring on a new set of devs during the Great Tribulation.

When time permits we can also look into removing the need to unlock the wallet - I think thats a hindrance also (for mining) - by storing the ABN funds in a separate wallet.dat. Maybe we make a keypair for ABNs, and ask the user to pre-fund the keypair etc.

Perhaps think about making ABN requirement something like say 54 or 10K right now.. Then there is still some ABN protection.. Thought?

Whatever you guys think is best; I could open a poll?