Yes, and I see a lot of windows10 users appear to not edit the correct biblepay.conf file.
Please navigate to:
%appdata%\biblepayevolution
Create the biblepay.conf there. Then look at it in DOS, and ensure its called "biblepay.conf" not "biblepay.conf.conf.txt" etc.
Happy mining!
Hello! Something weird is happeing on my side, after an update (I am not sure which one) I started to mine millions (which is impossible just with a laptop). I have checked now my wallet at: https://chainz.cryptoid.info/bbp/, and I am not mining there since 1st of June. But the worst is that I have two more movements 23rd of June and another one 24th of June of an average of MINUS 2500 BBPs each time. But going backwards shows to me that everything I mined, was taken out everytime I had more than a BBP (pluses followed by minus all the time). I am in shocked, as I had even bought BBPs this summer, so I could start to contribute with PoS + mining + old BOINC system. PD: I can see in the same webpage that all was moved to a 'Guesstimated Wallet', whatever that is, where my main address appears as the owner of that guess wallet. So perhaps not all is lost. But still I am mining millions without a reason. Perhaps I am in a forked wallet? How could that happend? I need some guidance now. First, have no fear that any BBP you bought or mined on the main chain is still there, as long as you have the wallet.dat file. One step at a time, we will need to ensure you upgraded to Evolution. You should be on 1.4.4.0, what version do you have? Note that Evo required us to move the wallet.dat file to the new location. You may still be mining in BiblePay Classic, which would explain how you solved so many blocks (diff is probably .0001) now. |
|
|
|
|
I remember Dave_BBP and Gilligan had a Windows10 mining crash issue, please let us know if the last release solved the problem.
|
|
|
|
windows 10(64bit) wallet 1.4.4.1(h) cant connet to the pool.. I dont have problem connecting to the pool on windows 7 (64bit)
addnode=explorer.biblepay.org
pool=http://pool.biblepay.org
poolport=80
workerid=KMIS *note (Funded worker)
genproclimit=60
minersleep=0
gen=1
----------------------------
"blocks": 131417,
"currentblocksize": 2484,
"currentblocktx": 2,
"difficulty": 3493.889791328252,
"errors": "",
"pooledtx": 2,
"chain": "main",
"genproclimit": 60,
"networkhashps": 454494.8052647252,
"hashps": 0,
"minerstarttime": "07-13-2019 09:25:23",
"hashcounter": 0,
"pooledtx": 2,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"abninfo": "Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti
Paste the full output of getnining info. Looks to me like it could not find your miner name and reverted you to solo mining or your use is not listed as funded. So grab a snapshot of your worker list also. That might be setup wromg Yes, and I see a lot of windows10 users appear to not edit the correct biblepay.conf file. Please navigate to: %appdata%\biblepayevolution Create the biblepay.conf there. Then look at it in DOS, and ensure its called "biblepay.conf" not "biblepay.conf.conf.txt" etc. Happy mining! |
|
|
|
Is it possible to use the funded ABN in the pool as a backup? Say if I have enough ABN for single block and I burn it, will I continue to mine with funded ABN? Thanks!
Sounds like a pretty good idea; could you enter an issue for it? https://github.com/biblepay/biblepay-evolution/issues |
|
|
|
|
** Funded ABN Fees are now dynamically calculated in the pool **
We have implemented a sliding scale ratio for the funded abn pool fee (HPS debit).
The fee is now the percentage of funded blocks solved over a 24 hour period.
Please see Pool | About: See the number of funded blocks and the funded block solve ratio.
|
|
|
|
|
BiblePay
1.4.4.1h-Leisure Upgrade
- Resolve windows10 mining crash and funded-abn crash
- Add funded-abn pool support
- Ensure GSC tx cannot use more than 500 inputs
- Add CameroonOne sanctuary logic
- Add exec dailysponsorshipcap (for CameroonOne), and exec
getchildbalance childid (for Cameroon One)
|
|
|
|
|
So far, Im receiving positive windows reports; please see the next version.
|
|
|
|
hi
Something weird on pool.biblepay.org
Total Balance:
28535.5744
Immature Balance:
37219.4495
Total balance is less then the immature
When trying to withdraw - impossible - amount is negative.
Regards
PM
Fixed, please try now! |
|
|
|
hi
Something weird on pool.biblepay.org
Total Balance:
28535.5744
Immature Balance:
37219.4495
Total balance is less then the immature
When trying to withdraw - impossible - amount is negative.
Regards
PM
Curious issue! My balance also shown as negative on the pool, when I went to the withdraw tab. Immature balance looks normal, however. We had some Indian letter writers trying to pull a fast one last night, so I increased the immaturity time - sorry, I believe I went a little too far there. Have no fear, the balance and underlying data is still correct. I will post as soon as its fixed. |
|
|
|
im using wallet ver. 1.4.4.1f 64bit / win7(64bit)
pool workerid KMIS funded
im receiving error
Assertion failed.
file:dbwrapper.h, Line 549
Expression: dbTx.IsClean()
wallet would run only for around 5mins.
What day did you download this, as we released a partial fix for this last night (1441f isnt supposed to be subject to dbwrapper)? Also how many funded threads are you running? |
|
|
|
** One Page startup Guide **
https://wiki.biblepay.org/Quick_StartLet me know if I forgot any great features or topics, or if I left out any required information, or if I should elaborate on any basic information. Hopefully this gives a new user the information they need to get started immediately with BiblePay.
|
|
|
|
And when you sort Announcements (Altcoins) by # of replies we are on the bottom of the first page  Hey thats positive for PR! |
|
|
|
So now biblepay has Turnkey Sanctuaries (GIN) and Turnkey mining (pool.biblepay.org) (mining without ABNs), and we already had a form staking with POG, and we have a working faucet.
Now I will work on a one-page startup guide for our most common scenarios so Grandpa can also get started.
With a one-page guide, I fail to see any barrier of entry for newbies.
I maintain the environment is not overly complicated.
And its also possible that with all the changes we've made in the last 2 years, that new users who stop by cant really understand what we are doing here, or how to mine. They might get frustrated in having to read 1,400 pages (remember our other thread is 700 pages also). So I think in this one page document (maybe it will be two or three pages now), I will also attempt to explain who we are and what we do (IE our boilerplate message) and a summary of our most important initiatives, where we are with them, etc. (I've been told by Dash that BBP is struggling to find its identity). One asset we have fortunately is our list of 5,000 e-mail addresses - containing distinct users who "tried" bbp in one shape or form. Once we peer review this document, lets send it out to our 5,000 members and see if we pick up any new users. |
|
|
|
|
So now biblepay has Turnkey Sanctuaries (GIN) and Turnkey mining (pool.biblepay.org) (mining without ABNs), and we already had a form staking with POG, and we have a working faucet.
Now I will work on a one-page startup guide for our most common scenarios so Grandpa can also get started.
With a one-page guide, I fail to see any barrier of entry for newbies.
I maintain the environment is not overly complicated.
|
|
|
|
** Pool.biblepay.org Non-ABN mining for users with no abn weight **
The following is what I have designed that appears to be technically feasible and secure, to allow turnkey mining for users with no abn weight:
1) Modify the pool Add Worker to have a dropdown that allows the user to choose : Yes for Funded ABN or No for self supplied ABN.
(This will mark the miner record with a 0 or 1 indicator indicating if they are a fundedabn, or not a funded abn. FundedABN = 1).
2) The Worker List: Show the Funded ABN column.
3) Miners mining against the pool with regular ABNs will see their full hashpower in the leaderboard.
3b) Miners mining against the pool with Funded ABNs will only receive 80% of their hashpower in the pool leaderboard (this is equal to a 20% decrease in subsidy). This hashpower excess will be given to the rest of the pool, therefore the rest of the pool will receive a 20% bonus for supplying the ABNs.
4) BiblePay core will be modified to supply an extended block template for a pool miner, with pool mining enabled, and using a workerid that is a funded ABN workerid.
5) When the miner asks for a block to work on, the pool will find an applicable ABN that is for the current best block and provide it to biblepaycore. This is the block the end miner will work on.
5b) Note that the ABN used comes from a non-predictable funded miner who is currently mining in the pool, so over time, random ABNs will be used by random non-funded miners (IE one rich miner should not lose all ABN weight as we wont iterate serially).
6) BiblePay core will be modified with security considerations so the above steps can be completed.
7) The block distribution will be modified to show : UserWhoSolvedBlock.MinerWhoSolvedBlock so we can debug the funded abn's properly and work out any issues. We will also see [FABN=1] in the block distribution drill in, so we can see funded abn's who solved blocks.
8 ) The BiblePay core miner will show a distinct message in getmininginfo when it is mining with a funded ABN vs a normal ABN.
9) If we use up too much coin-age by an influx of users, we can increase the fees.
Who would like to test non-abn pool mining? This is in beta, so I'm not going to announce a release yet until the feature is tested from the windows machine(s), then we can ask MIP to build a linux version if its successful. At this point, you can download the windows v1.4.4.1c, and verify you have the feature enabled by typing 'exec getabnweight 115000' and if the Version output equals 2.0, you have the non-abn feature. To set up the feature, go to pool.biblepay.org, add a new worker. Select "Funded" = YES for the worker id funding type. Save the record. Use this workerid in your biblepay.conf file. Start the miner. If you see "ABN=OK (Non-Funded)" from getmininginfo, and the HPS > 0, its working, otherwise please see the error message. Ready for testing (Windows 64): https://biblepay.org/biblepayevo64.exe |
|
|
|
|
** Pool.biblepay.org Non-ABN mining for users with no abn weight **
The following is what I have designed that appears to be technically feasible and secure, to allow turnkey mining for users with no abn weight:
1) Modify the pool Add Worker to have a dropdown that allows the user to choose : Yes for Funded ABN or No for self supplied ABN.
(This will mark the miner record with a 0 or 1 indicator indicating if they are a fundedabn, or not a funded abn. FundedABN = 1).
2) The Worker List: Show the Funded ABN column.
3) Miners mining against the pool with regular ABNs will see their full hashpower in the leaderboard.
3b) Miners mining against the pool with Funded ABNs will only receive 80% of their hashpower in the pool leaderboard (this is equal to a 20% decrease in subsidy). This hashpower excess will be given to the rest of the pool, therefore the rest of the pool will receive a 20% bonus for supplying the ABNs.
4) BiblePay core will be modified to supply an extended block template for a pool miner, with pool mining enabled, and using a workerid that is a funded ABN workerid.
5) When the miner asks for a block to work on, the pool will find an applicable ABN that is for the current best block and provide it to biblepaycore. This is the block the end miner will work on.
5b) Note that the ABN used comes from a non-predictable funded miner who is currently mining in the pool, so over time, random ABNs will be used by random non-funded miners (IE one rich miner should not lose all ABN weight as we wont iterate serially).
6) BiblePay core will be modified with security considerations so the above steps can be completed.
7) The block distribution will be modified to show : UserWhoSolvedBlock.MinerWhoSolvedBlock so we can debug the funded abn's properly and work out any issues. We will also see [FABN=1] in the block distribution drill in, so we can see funded abn's who solved blocks.
8 ) The BiblePay core miner will show a distinct message in getmininginfo when it is mining with a funded ABN vs a normal ABN.
9) If we use up too much coin-age by an influx of users, we can increase the fees.
|
|
|
|
Speaking of mining.. there's a miner on pool with over 1.2m hash/ps, and a growing # of physical machines. Kind of curious about it.
Thanks, I see him now. So he looks like he's about 38* bigger than me, and I solved 11 shares and he solved 418, so that looks good. The deal is that means we should solve about 15 more blocks than normal in the next 24 hours. So lets see if we solve more than 50... PS - I am making a proof of concept for funded ABNs. I think it would be nice to have turnkey mining since we need more users right now. |
|
|
|
Can someone help me figure out why I have no hashps showing up? 
{
"blocks": 130227,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 2130.164171713709,
"errors": "",
"pooledtx": 0,
"chain": "main",
"genproclimit": 2,
"networkhashps": 258953.0736721055,
"hashps": 0,
"minerstarttime": "07-07-2019 18:54:43",
"hashcounter": 0,
"pooledtx": 0,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; BALKgP9NgQqurufJJCDqN4r7y6fhUUCLcj; ",
"poolinfo2": "RMC_07-07-2019 19:03:26; RMC_07-07-2019 19:03:25; ",
"poolinfo3": "",
"abninfo": "Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.; ",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "http://pool.biblepay.org",
"required_abn_weight": 125000
}
Everything else seems fine? Not sure about the abn part as it doesn't seem like something I see needed to setup a biblepay.conf file to mine? Does this mean I cannot mine even though it says poolmining "true" and biblepay-generate "true"? poolmining=true and generate=true means your mining thread is running, and you are configured to pool mine, but you are not mining due to the error in "abninfo". Could you please paste your 'exec getabnweight 125000' and it should show the reason you are not mining. Minimum abn weight is 125,000. (Otherwise the miner fails to create a block). I see. So in layman's terms this would mean?? I have a few days to wait to be eligible to mine? Thank you in adv. 11:36:53

exec getabnweight 125000
11:36:53

{
"Command": "getabnweight",
"version": 1.2,
"weight": 54966.13539351852,
"total_required": 15012,
"weight 125000.00": 54966.13539351852,
"total_required 125000.00": 15012
}
I see you have an ABN weight of 55K (this is equal to your current wallets coin_value * age). You just need to increase this weight above 125,000 to currently mine. You could either add to your balance, or wait til it ages more. We do have a faucet at pool.biblepay.org also btw. |
|
|
|
How to multiple mine? would I simply sync my wallet.dat to new PC? (Windows platform)
Do you mean mine on multiple machines with the same wallet? If so yes.. But ABN would be burned on both if 1 finds a block. Yes, exactly, just copy your wallet.dat out to multiple miner machines to share the ABN. |
|
|
|
|
Show Posts
