MIP wallet.dat and biblepay.conf....my explorer setup PPA still crashed.....all deleted and gave up with explorer of BBP forever
never found coin where explorer shows shits!!!!! only BBP
That doesn't mean much without knowing further details. I have mounted quite a few too, including BBP ones, without issues, and that doesn't mean anything either. For example I have mounted quickly this BBP Explorer in 25 minutes with a $10/month Vultr machine (no GUI customized) and now it's working and indexing the blocks http://207.246.112.230:3001/And it's not crashing at the moment. You can check it for a while for you to see and I will switch it down in 2 hours. To be constructive, if you need more details we can discuss in Discord and try to solve your problems, if you want. all infos is posted here.......what you want, debug is here.......when i tried 50times run PPA --daemon and still crashed its not my problem..... before upgrade to 1185 all worked..... new upgrade to 1185 fucked up all .... check how many ppl got problem with PODC rewards....... this is mistake of main DEV...... MIP i deleted explorer and all with BBP..... BLE (CPU idle mining coin) explorer ran in same time like BBP= working till now without my hand, BBP? nonstop problems .... nonstop upgrade,nonstop updates, nonstop change rules, nonstop rpoblems,nonstop angries,nonstop crashing,nonstop facepalms!!!!!! yes VULTR for 10$ and for few weeks you can delete it=cos your df space will be fully  I think the most constructive thing we can do in this case Slovakia is to isolate the problem by breaking it down. We know multiple things happened this week - we had a fork, we had a problem with getdifficulty, the explorer sync slowly etc. I recommend deleting the database in the explorer (wherever the mysql data is stored). Run biblepay first without the explorer on the node and sync it to the top. Verify biblepay 'getdifficulty' works. Then add the explorer on in a layer. This way we can see exactly what introduces the problem. I'll look at your logs. I'll also look to see what happened with PODC last night. It could be that the sancs did not come to a consensus - as MIPs log shows they didnt read all the data (but this has not been confirmed yet). |
|
|
|
Hey,... Texas cowboy.
Instead of deleting my posts you should really start to solving problems that people have with your coin.
It's not my coin, it's our coin and we have multiple devs- I can't babysit you 24 hours per day. Its 9AM here and I'm coming on to help everyone out - but it is a community effort. (I'm not sure what post you are referring to but please do not violate the OP rules). |
|
|
|
few questions:
for tithing, do i need gen=1 with tithe=1? or just tithe=1?
how much it will be tithing with tithe=1, one bbp? so if i want tithe 100, then i set tithe=100? i think then 100 wil be max and if diff allows only 50, then it will tithe 50, right?
if diff is low and max tithe is for example 100, then is it same if i tithe 10x 10 bbp or 1x 100bbp?
how can i set tithe frequency? because if i will not be tithing max, then tithing every 4hrs is wasting coins with age
if i counting properly, then diff 60000 means, that i will need coin age 54 days, so at least 54 adresses, but x6 when autotithing... 22.5k amount on them so in total 7.29m bbp to be able tithing in loop (of course i will need somehow add back spent coins)
1. Technically you just need tithe=1. As gen=1 is the default. 2. With tithe=1 you tithe once every 4 hours, at the difficulty level tithe amount (automatically). 3. If you want to tithe a custom amount, please shut off tithe=1 (with tithe=0) and manually tithe. 4. If diff is 32000, it will only tithe just below the diff level (150 bbp). 5. Please rephrase the question, is it the same if i tithe 10x. 6. Tithe frequency is in minutes. tithe=10 means tithe once every 10 mins. 7. On diff of 60,000 you need coin age of 54 days, but not 54 addresses. You only need 1 address. See 'exec bankroll'. |
|
|
|
before mandantory worked....after all crashed,forks,POG dumping-price tool,classic
Stability `by ROB`... Praise the Lord! |
|
|
|
its excellent: when i made my 2 explorers for BBP and BLE
BBP=nonstop still problems
BLE=working nonstop from start
What kind of problems to run an explorer? read slowly, i posted here my problems..... PPA crashed.......nvm....forgot about explorer, i reinstalled machine and using for p2p/warez and mining stable BLE == next CPU mining coin= idle mining COIN OF FUTURE .... So basically you got a bad taste in your mouth when you tried to run an explorer node and it crashed because we had a bad build (that has subsequently been fixed). Ok, it sounds like you have nerves of steel, but thats no reason to leave BBP. |
|
|
|
There is something wrong with numbers. Sowers are getting 100K bbp although 400*205 is 82K. Other thing is about blocks vs time. I find it confusing that there is many times said 24 hours and right after it some explanation that 205 block are 24 hours. I know that 205 blocks is around 24 hours, but I would rather see consistently 205 blocks used instead of 24 hours. Maximum daily tithe cannot be both 50K and 100K. I think it should be maximum tithe for 205 blocks is 50K. Otoh is a slang word. Thanks, I adjusted these things, please check again. |
|
|
|
Keep meaning to ask about the change (I think in 1.1.6.4) to goobject vote-many.
Are the new parameters ([sanctuary_name_wildcard] [sleep_ms]) the result of a change in DASH or something you added? If the later, hows it working out? What positive use do you see from this?
Thats actually a biblepay feature that supposedly lets you vote-many but only on sancs that match the wildcard pattern, but for some reason it didn't work out. I'll try to look into the reason why soon. It basically has no effect (if you had west1 through west20, you should have been able to add 'west' as a parameter) and vote on all nodes beginning with west, but it votes with all still. Ill look at it when time permits. (It passed test because it was not tested properly). |
|
|
|
|
On my windows wallet, I set tithe=10 and restarted and it tithed properly 3 times.
I don't see any problems.
I'm disabling this until go live.
Most likely, whoever had the issue had a message in the debug log with a wallet unlock error or something (maybe NSF, etc).
NOTE: If you test your miner now before go live, and you don't auto tithe, grep the debug.log for this: BiblePayMiner::SendTithe:: (All the send tithe errors contain this prefix).
|
|
|
|
MIP just mentioned to me that people in Discord are confused about POG because the docs are outdated. I'm going to go through these now and create a more concise version. Then if someone wants to take it and make it look nicer as a PDF for the web site etc they can- I will work on this now. |
|
|
|
its excellent: when i made my 2 explorers for BBP and BLE
BBP=nonstop still problems
BLE=working nonstop from start
What kind of problems to run an explorer? |
|
|
|
We integrated the pool with the Walmart API.
46k BBP for $15 Subway Gift card delivered by fedex very quickly.  Thank you for confirming! Thanks for ordering. I ordered one myself and saw on the back of the card that it's reloadable. Its something cool for us to keep in mind if we ever want to reload our users Subway cards. Also, I did take a look at e-mailing gift certificates and made some progress on that, but I need to update everyone later as there are higher priority things going on right now. But I will persistently get back to that project asap as I found one solid and concrete way for BiblePay to e-mail a gift card from the pool with WalMart gift cards. Great! when can we see BBP Gift Cards for non-US residents ? Maybe Ebay / GOOGLE PLAY / Amazon ? So far, we have an agreement with Walmart, and I have confirmed that we will be able to offer e-mailed walmart gift cards soon that work in physical stores. I can't promise that the card will work in other Countries yet. But this appears to be a great addition for us to add as some people will want to spend biblepay without revealing their home address. |
|
|
|
Hi!, I have wallets in diferent block height. Wich one is the right one? How do I find out the correct block the chain is in?
Just verify this hash matches: getblockhash 99435 20:32:25 1f0d42e4696112cd70b57cce11d323012641e33cd81e6db4800b358b92148dd4 If it does not, rm files and restart. If you lose any solo mining rewards its because they were mined on a fork. |
|
|
|
Great to have you back! Yes pool.biblepay.org is on the 1f0d* chain and all my nodes on the 1f0d* chain also. (This is the one with 1.1.8.5 > 98%). Capulo, the reason the other chain is getting rewards is because all transactions and mining still occur on both chains. The one with more work ultimately wins. |
|
|
|
1.1.8.5b is already in Ubuntu Launchpad. (PPA repository)
Remember that it just adresses a crash in a RPC (console) command , so it doesn't make any difference to 1.1.8.5 in terms of chain consensus .
after upgrade,still crashed I just checked the windows version ( www.biblepay.org) works and does not crash, maybe its the PPA version? It would be nice to know the OS+version used, and how it was installed. Also what kind of "crash" is the user experiencing (if there is a message to be seen on console, a segfault line, or nothing). Unfortunately, "still crashed" is not enough information to narrow down the problem. ubuntu 16.04 ubuntu 18.04 installed by your steps on wiki after updated and upgraded to 1185 and started biblepayd --daemon crashed after starting.... tried deleted all things like before togos wrote tried start with reindex still crashed after syncing blocks via PM i can to send to you root access and you can check it crashed,that you see nothing... tried getinfo and thanks  If this crash is unrelated to executing 'getdifficulty' then its probably not the PPA issue (maybe), in this case I would try: rm blocks -r rm chainstate -r rm gov* rm mnp* rm mnc* Then restart. Sometimes the governance object cache being out of sync with 0 blocks makes the wallet do all kinds of unexpected things. tried deleted 3 times all in folder except .conf and wallet.dat .... started wallet...... when im started npm start,then crashed Togo=can you to check it via putty/kitty where can be problem? thanks Whats the tail of the debug.log look like? Any idea how high the height was and what it did last? As a last resort, you can copy wallet.dat to wallet.bak, then restore an old wallet from the \backups folder, just to see if its the wallet file is corrupted. If you do this ensure you get your entire balance back. (If you don't you have to salvage the old wallet file). You probably will get it all back. |
|
|
|
1.1.8.5b is already in Ubuntu Launchpad. (PPA repository)
Remember that it just adresses a crash in a RPC (console) command , so it doesn't make any difference to 1.1.8.5 in terms of chain consensus .
after upgrade,still crashed I just checked the windows version ( www.biblepay.org) works and does not crash, maybe its the PPA version? It would be nice to know the OS+version used, and how it was installed. Also what kind of "crash" is the user experiencing (if there is a message to be seen on console, a segfault line, or nothing). Unfortunately, "still crashed" is not enough information to narrow down the problem. ubuntu 16.04 ubuntu 18.04 installed by your steps on wiki after updated and upgraded to 1185 and started biblepayd --daemon crashed after starting.... tried deleted all things like before togos wrote tried start with reindex still crashed after syncing blocks via PM i can to send to you root access and you can check it crashed,that you see nothing... tried getinfo and thanks If this crash is unrelated to executing 'getdifficulty' then its probably not the PPA issue (maybe), in this case I would try: rm blocks -r rm chainstate -r rm gov* rm mnp* rm mnc* Then restart. Sometimes the governance object cache being out of sync with 0 blocks makes the wallet do all kinds of unexpected things. tried deleted 3 times all in folder except .conf and wallet.dat .... started wallet...... when im started npm start,then crashed Togo=can you to check it via putty/kitty where can be problem? thanks Whats the tail of the debug.log look like? Any idea how high the height was and what it did last? |
|
|
|
Can PoDC updates take from Tithe balance if there aren't other any balances to take from. For example, your RAC goes up, so you need to stake more in the PoDC update transaction.
If the coins were created with 'exec bankroll' denominations, the PODC won't spend those coins; otherwise it will try to. Speaking of that I think its time to create some bankroll denominations for testing in prod. |
|
|
|
1.1.8.5b is already in Ubuntu Launchpad. (PPA repository)
Remember that it just adresses a crash in a RPC (console) command , so it doesn't make any difference to 1.1.8.5 in terms of chain consensus .
after upgrade,still crashed I just checked the windows version ( www.biblepay.org) works and does not crash, maybe its the PPA version? It would be nice to know the OS+version used, and how it was installed. Also what kind of "crash" is the user experiencing (if there is a message to be seen on console, a segfault line, or nothing). Unfortunately, "still crashed" is not enough information to narrow down the problem. ubuntu 16.04 ubuntu 18.04 installed by your steps on wiki after updated and upgraded to 1185 and started biblepayd --daemon crashed after starting.... tried deleted all things like before togos wrote tried start with reindex still crashed after syncing blocks via PM i can to send to you root access and you can check it crashed,that you see nothing... tried getinfo and thanks If this crash is unrelated to executing 'getdifficulty' then its probably not the PPA issue (maybe), in this case I would try: rm blocks -r rm chainstate -r rm gov* rm mnp* rm mnc* Then restart. Sometimes the governance object cache being out of sync with 0 blocks makes the wallet do all kinds of unexpected things. |
|
|
|
1.1.8.5b is already in Ubuntu Launchpad. (PPA repository)
Remember that it just adresses a crash in a RPC (console) command , so it doesn't make any difference to 1.1.8.5 in terms of chain consensus .
after upgrade,still crashed I just checked the windows version ( www.biblepay.org) works and does not crash, maybe its the PPA version? It would be nice to know the OS+version used, and how it was installed. Also what kind of "crash" is the user experiencing (if there is a message to be seen on console, a segfault line, or nothing). Unfortunately, "still crashed" is not enough information to narrow down the problem. If anyone is running the new PPA version, please do a 'getdifficulty' and tell us it does not crash  . |
|
|
|
|
Show Posts
