im tested over 70+ coins with mining for last 8-9 years= no problems with this coins,, BIBLEPAY? nonstop problems, im ran this wallet for my friend, no mine 24hours  21:40:48  exec getabnweight 125000 1 21:40:48  { "Command": "getabnweight", "version": 2.7, "weight": 6499.35, "total_required": 259975, "coin_age_data_pre_select": "25997.7751(0.03)=[649.93] depth=7, <ROW>233977.4686(0.03)=[5849.43] depth=7, <ROW><TOTALREQ>259975.24</TOTALREQ><TOTALAGE>6499</TOTALAGE>", "weight 125000.00": 6499.35, "total_required 125000.00": 259975 } Share your biblepay.conf file please as well as a print out of your worker list. Your ABN is LOW as is clear from weight of 6499.35 which is less than 125000 Ask him to clear up his language on our forum or he will be re-banned. Slovakia, if you continue to bash us you will be gone again - as you are in every other forum and system. We don't deserve your foul and negative posts while you sit back in your armchair and you never contribute anything except complaints. |
|
|
|
now crashed mining in pool . where is problem? 21:30:58  getmininginfo 21:30:59  { "blocks": 148740, "currentblocksize": 130157, "currentblocktx": 68, "difficulty": 3274.255937859833, "errors": "", "pooledtx": 67, "chain": "main", "genproclimit": 40, "networkhashps": 421280.8584988303, "hashps": 367381.002477927, "minerstarttime": "10-02-2019 14:42:51", "hashcounter": 5379221294, "pooledtx": 67, "chain": "main", "biblepay-generate": true, "poolinfo1": "Pool mining with slovakia; 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; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ", "poolinfo2": "RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:25; RMC_10-02-2019 19:30:26; RMC_10-02-2019 19:30:25; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:26; RMC_10-02-2019 19:30:25; RMC_10-02-2019 19:30:39; RMC_10-02-2019 19:30:26; RMC_10-02-2019 19:30:25; RMC_10-02-2019 19:30:39; RMC_10-02-2019 19:30:40; RMC_10-02-2019 19:30:26; RMC_10-02-2019 19:30:39; RMC_10-02-2019 19:30:34; RMC_10-02-2019 19:30:31; RMC_10-02-2019 19:30:39; RMC_10-02-2019 19:30:42; RMC_10-02-2019 19:30:39; RMC_10-02-2019 19:30:40; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:39; RMC_10-02-2019 19:30:40; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:40; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:40; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:42; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:42; RMC_10-02-2019 19:30:40; RMC_10-02-2019 19:30:40; RMC_10-02-2019 19:30:41; RMC_10-02-2019 19:30:39; RMC_10-02-2019 19:30:42; ", "poolinfo3": "", "poolinfo5": "Internal ABN: Invalid 1570044641; ", "abninfo": "No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044655; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044655; No block to mine... Please wait... 1570044655; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044655; No block to mine... Please wait... 1570044665; No block to mine... Please wait... 1570044662; No block to mine... Please wait... 1570044655; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044655; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044655; No block to mine... Please wait... 1570044655; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044655; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044657; No block to mine... Please wait... 1570044655; No block to mine... Please wait... 1570044657; ", "gsc_errors": "low abn weight 0", "poolmining": true, "pool_url": " https://pool.biblepay.org", "required_abn_weight": 125000 } It says right on the page you have an invalid ABN Slovakia. What does 'exec getabnweight 125000 1' say now? |
|
|
|
now crashed mining in pool . where is problem?
Incorrect - please don't post misleading information on the forum. To clarify: Uptime of the biblepaypool has been very good for the last 2 years, considering that we only have one active pool left. I think I brought it down twice in a year for about an hour. |
|
|
|
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. |
|
|
|
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. |
|
|
|
22:06:28  exec sendgscc 22:06:28  { "Command": "sendgscc", "Error": "Command not found" }  til now worked stable The newest version no longer requires 'exec' for that command (and a few others now). |
|
|
|
Hello MIP. I'm reaching out this way as this seems to be a re-occurring issue. My BBP client was happy until this last mandatory upgrade. After upgrading, it will not connect to any peers. I have gone as far as completely removing BBP off of my system and deleting the residual files/folders and then re-installing as if I were a new user. Even without my wallet.dat and config file, it will not connect to any peers. I have attempted disabling Windows Defender firewall (Win10) and have also added the two IP addresses in my config file for the nodes you mentioned the last time I had connection issues. Any ideas what to try next? Thank you for you time and consideration on this matter.
Have you ensured the system time and timezone is correct within 10 seconds also? After doing that - *If* its still not working, try this from the rpc type: addnode 95.216.127.254 onetry Please post the log if it still does not work. EDIT: Please confirm the BBP Version is 1.4.4.8+ in the about page? Pre 1448 will get rejected by the network. |
|
|
|
A user on Twitter outside of the USA is having trouble using the pool faucet: "pool.biblepay.org has a faucet for which one needs to verify their mobile by providing their carrier information, but what about people not based in usa, i have a carrier not available in the options could i get some help!?" https://twitter.com/hellboi697/status/1178536740551675904Please tell him to email me his CPK and his receive address from his official email address and Ill manually enter it. |
|
|
|
BBP offline in Southxchange..., Any info about that?
They are upgrading now; they took it down to move to 1.4.4.8. Thanks!, That's what I thought but I wanted to confirm it. SX is open again for deposits. There was a technical issue that needed worked out. |
|
|
|
BBP offline in Southxchange..., Any info about that?
They are upgrading now; they took it down to move to 1.4.4.8. |
|
|
|
|
*** HOW To: Cameroon One additional Payment option directly from the core wallet ***
We already have about 12 children being sponsored in POOM.
Now you can pay in BBP using a dedicated command!
From the rpc type:
exec paycameroon childid USD_AMOUNT test
(Note: To find your childid, type listchildren).
Specify the amount in USD, for example:
exec paycameroon 123aaa 40 test
The console will show you the amount in BBP (at the midpoint of our current market rate) that will be sent to Cameroon.
If you authorize it, re-execute the command with "authorize" at the end:
exec paycameroon 123aaa 40 authorize
Cameroon will be able to run a report that shows the TXID and the ChildID and amount - this way it will be easy for them to match up the childid-payments for BBP.
|
|
|
|
1.4.4.8-Mandatory Upgrade for Entire Network Please upgrade before block 148,000
https://github.com/biblepay/biblepay-evolution/releases/tag/1.4.4.8- Increment Sanc protocol version to enforce upgrade, Enforce protocol version and peer version at block 148000, Enforce 1447 immediately Add network monitor for use by devs to diagnose excessive bandwidth by message type - Add CheckGSCHealth - this lets the node check its GSC health once every 4 hours - if it fails it calls out for a gobject resync. It also reassesses the chain (IE unwinds any forks) once every 4 hours. You can disable this with 'disablereassesschains=1' in the biblepay.conf. (This is only necessary if you believe your node is down, optional. Type exec gschealth to see the output). Our primary tool is still 'exec health' under normal circumstances; this shows the health of the GSC system. - Allow non-standard Sanctuary port numbers (based on outcome of sanctuary vote). This will allow us to create Sancs with nonstandard port numbers, and allow Apollon to use this if approved. - Added 'exec paycameroon childid amount dry'. This allows you to pay cameroon one for a sponsored child. It automatically converts the USD rate for you and includes the ChildID-CPK-TXID on the cameroon payment information. Once you run it, then re-run it with 'authorize' to complete the transaction. Cameroon will see this payment on their reports. - Add ddos for non compliant nodes sending strange messages Change syncing timeout for gobjects to 60 seconds Delete old GSC data in the delete thread (once every 5 mins); this removes approx 75% of old orphaned votes and decreases ram usage and gobject file size - Add dedicated RPC command for readverse: readverse book_name chapter language verse_number. - Ensure 'exec readverse' defaults to English. (We plan on honoring the wallet language setting in the future). - Add dedicated RPC command for 'sins'. This shows the 39 mortal sins that could send a person to Hell. - Added dedicated RPC command: versionreport: Shows the software version running on the network by users ranked by percentage (over the last 205 blocks). - Added dedicated RPC command for 'bookname short_book_name' (Shows the long name corresponding to the book abbreviation). - Added dedicated RPC command for 'books' (Shows the books of the bible). - Create dedicated command for 'datalist'. Type 'datalist objtype' for the list (IE datalist prayer 7) to receive the last 7 days of prayers. Added 'leaderboard (nickname || all) height'. This allows a user to see the exact reward breakdown per superblock height. It also allows anyone else to audit a breakdown per nickname. - Add Chinese Language Translations for BiblePay QT Bible Reader (Allows the user to read the CNV from the Read Bible Menu) Enhance 'exec readverse' to support both Chinese and English Fix OneClickMining initial crlf issue (Meaning that biblepay.conf will not be corrupted if user starts with one-click-mining config). - Add Payment Option 4 for Cameroon-One, and fix BIO URL Apollon Integration for Deterministic Sancs: Add 'exec blscommand mnppriv blsprivkey'. This allows the user to set the deterministic masternodeblsprivkey in the sanc biblepay.conf file. NOTE: The EncryptAES256 and DecryptAES256 were added to support this feature (this is so no other node can discover your mnprivkey or your mnblsprivkey during transmission or initialization). - Update Health feature for Sanctuaries only: Set healthupdate=1 to enable, healthupdate=0 to disable, default is Enabled on Sanctuaries only. If this is enabled, you will see your Sanctuaries health status (IE Best Block Hash, GSC voting level) in the pool. This will be valuable when we host with Apollon. - Fix governance.dat bloated file size, on boot. Reindex governance.dat on boot if > 35 megs. Note: Although most users will see an improvement in RAM and network usage in 1448, the full impact for gobject propagation will appear at block 148,000. At this height, this version will become mandatory and all old nodes will drop off, thereby creating an environment that only shares the official gobjects (increasing qos). Theoretically our network utilization should drop by 70% after this height as nodes will not continually ask for objects repeatedly. ** All binaries have been deployed **
|
|
|
|
|
If anyone wants to set up a Sanc in MainNet (Prod) on a non-standard port, it's OK to do so now, since we pushed this feature in the new mandatory and the vote has won.
To do this:
On the Sanctuary, pick a nonstandard port # (IE like 10000).
Set "port=10000" (or your chosen #) in the biblepay.conf.
On the controller, change the ":40000" in the masternode.conf file to the correct port # chosen above.
Everything else should work as previously described.
|
|
|
|
|
** Orphan Letters - Outbound **
Help: We have 7 letters written in the pool and they have no votes, please vote.
|
|
|
|
Everyone, I'd like to announce my intended release schedule and expectation of real world usefulness for Christian Spaces and give an overview of what we are trying to accomplish: First, you can get acclimated with what Christian Spaces is here: https://wiki.biblepay.org/Christian_Spaces_Functional_DesignNext, you can start by listening to some of the technical explainer videos at the bottom of the wiki (there are over 10). Feel free to ask any questions about what the idea is, or why we are doing this, etc. So first I plan on creating a "New Feature" thread in bitcointalk for Christian Spaces (and its constituent features like DSQL). What I'd like to accomplish is turning it into a testnet thread, bringing seasoned users and devs into the discussion, running 5-10 nodes of BMS, using it from a user perspective, refining it to become something useful (for approximately 3-4 months - then probably for 5 years as we need to add more to it). Then I plan on enabling some of the useful features *by* the end of the year in prod Biblepay. As I feel a few are valuable now, and can be enabled towards November/December. Some of the enhancements I really want to release for BiblePay before the end of the year include these features: - A decentralized prayer blog. The idea here, is to have a full page to be able to type a longer prayer, and then when you post it, it appears in blog format sorted by votes ascending. This will allow us to pray more effectively as a group, if we can see important prayers get upvoted, and also, more personal prayers (for example if someone has a relative in need etc). The 'novelty' of the feature however will be that we store the blog as a table in our decentralized sql server across many nodes (DSQL), and serve the blog from our BWS (BiblePay decentralized Web server). - An accounting system. Id like to see a page for debits/credits per user CPK, so we can see the DSQL balance, and see accounting entries affecting the user. - Our gospel links table, ported to be decentralized with voting. This will allow people to post new Gospel Links and let these get upvoted/downvoted etc. - All of our DR (disaster recovery) tables be ported to DSQL and be browsable. - Ability for the core wallet to sign transactions and browse the decentralized web. This basically means easy to use interface for the user, who just wants to see a prayer blog and vote on a prayer, etc. Without knowing anything technical. - The Christian Treasure Trove (IE saving data at risk of being scrubbed on the web that should be available/valuable for all humans). - Ability to host an HTML5 site in a decentralized way, from BBP. - BBP Leasing/freshening of documents. - A true GDPR/RIAA/Inappropriate takedown request process. We have most of this solution (with the above features) very close to being ready for testnet (its very close to checking in, and compiling for use by testers). I believe we can start testing by October 1st. |
|
|
|
That looks pretty awesome! If I think of anything else I will post. DSQL is too big of an animal to add to it at this moment, but I'm starting to work on the info for Bitcointalk now and I suppose we can handle that separately. |
|
|
|
If BiblePay wants to expand into China with exchanges, the next logical step is to support Christian orphanages in China. I saw many links on GlobalGiving for Chinese orphanages, but not sure if they are Christian based as religion is not recognized by the Communist Party. https://www.globalgiving.org/companies/china/CameroonOne is the Boston branch that focuses on the Cameroon-Africa children (where Hilary and Todd works), but they are owned by OneTrack Intl. From what I understand when we ask for a new child to be sponsored, Todd reaches out to One Track and they provide the new child. I'm currently searching for children in Israel. God says in Genesis 12:3, I will bless those that bless you, and curse those that curse you (to Abraham). I feel like if we start blessing Israel, we can see our project be blessed. Hi Rob, I live in Israel, I love that you are willing to support us. I think it will be a mistake, in this stage, to move funds from Africa. Israel has relative strong economy: https://tradingeconomics.com/israel/ratingBiblePay, relatively small charity, will have much more big effect on kids life in Africa. With regards, Yaron I'm not against China of course, but our budget is relatively full right now (we have 115 existing children) and this month we were primarily sustained by our existing credit. I'm referring to Israel for the reason above - for POOM - and also for blessing the apple of God's eye first, so we may open the floodgates for more to flow in to our project - and then we can help other children in the world with a greater magnitude, if God blesses us. We have to be a Holy and peculiar people, living by his word, and bearing Christian Fruit. Then the blessings will follow because his word does not return void. EDIT: But I'll ask Todd at Cameroon, for POOM, if a user may specify China. He *might* have an option with OneTrack (or they might not be associated with China). (Global Giving btw is not Cameroon or one-track or compassion - its a different company). |
|
|
|
CameroonOne is the Boston branch that focuses on the Cameroon-Africa children (where Hilary and Todd works), but they are owned by OneTrack Intl. From what I understand when we ask for a new child to be sponsored, Todd reaches out to One Track and they provide the new child. I'm currently searching for children in Israel. God says in Genesis 12:3, I will bless those that bless you, and curse those that curse you (to Abraham). I feel like if we start blessing Israel, we can see our project be blessed. Hi Rob, I live in Israel, I love that you are willing to support us. I think it will be a mistake, in this stage, to move funds from Africa. Israel has relative strong economy: https://tradingeconomics.com/israel/ratingBiblePay, relatively small charity, will have much more big effect on kids life in Africa. With regards, Yaron Thank you, that's good too. I'm not intending to move funds from Africa though. I'm working with Cameroon-One on trying to make additional children available from Israel (or Cameroon) for POOM - at the miner's discretion (for new sponsorships). In my case I'd like to sponsor some children in Israel to help bring blessings to this project. I believe those who help God's chosen people open up the floodgates of blessings on the entire project. EDIT: And also to clarify, this would not be for the rich of Israel. There are a few pockets in Israel in destitute need of help. One might be Druze, Im not exactly sure. But these would be orphans in really bad shape, if we find them. |
|
|
|
|
Show Posts
