Payments from minermore.com are also strange. I received 5 small payments today. The first 3 of them are still unconfirmed, the next one was confirmed immediately, the last one is unconfirmed again. No idea what's going on, since the unconfirmed also don't have any "counter" how many confimations are done/missing.  |
|
|
|
Now a small problem remains in my wallet: it shows the correct transactions in the "transactions" tab, but on the overview under "recent transactions" there are only a handfull of old ones (the latest from more than a week ago). Is there a quick way to fix this? Restarting the wallet didn't help. Otherwise I would make a reindex, which should solve the problem.
Try -zapwallettxes Thank you, but that didn't help. I also tried every other repair option (zap2, rescan, reindex..) and even started from a clean core folder (only with wallet.dat), but no success. Since it's only a "cosmetic" error I'll just leave it for now and maybe wait for another QT-wallet update. Maybe it will somehow miracilously resolve itself.  |
|
|
|
Woah we got to PODC block 55555 solved it
and then jumped through 55556 to 55612 super fast! like 5-6 minutes!
...however that was even possible.  Nice, so it seems to have sorted itself out again. I even got the PODC payment, so it seems like the 25 hour window between the PODC updates was no problem this time because it was way more than 25 hours between those 2 superblocks. Now a small problem remains in my wallet: it shows the correct transactions in the "transactions" tab, but on the overview under "recent transactions" there are only a handfull of old ones (the latest from more than a week ago). Is there a quick way to fix this? Restarting the wallet didn't help. Otherwise I would make a reindex, which should solve the problem. |
|
|
|
I never added any nodes and my wallet synced just fine yesterday after the update (and the blockchain download). Just leave it open for a couple of hours and it should be ok. I'm missing " minermore.com" from the pool list, they currently have 3 GH/s. btw: I also tried the bsod pool over the last couple of hours and indeed it seems to be severely underperforming. No idea why... |
|
|
|
|
So obviously the whole chain is again complete bollocks right now due to the superblock collision. My Win10-Wallet (1.1.3.6) is constantly crashing, which is why I had to leave it closed and I hoped that the next superblock would be here sooner.
Now it appears that my lasts PODC update is approx. 25hours old. Does this automatically mean I will also miss the NEXT superblock payout?
Right now I managed to open the wallet with gen=0 and quickly force a PODCupdate. But this is too late, right?
|
|
|
|
|
Just 2 quick questions:
1. Since there was no major upgrade until now I assume there won't be a PODC payout tonight (due to superblock collision), right?
2. What is the current status with BBP under Ubuntu 18? A friend of mine tried to heat-mine on Ubuntu 18 and since there is no PPA version as of yet he tried to build it from source. After some minor tweaks (I think mostly regarding libssl) it worked, but the POW seems to suffer from a memory leak (approx. 10-15 MiB per minute). Has anyone tried to run the BBP client under this operating system? Any hints?
|
|
|
|
Hey guys. I just discovered this project yesterday and started to mine some with my GTX 1063 ( ). What confused me was that there seems to be a market for VTL/BTC on YoBit ( https://yobit.net/en/trade/VTL/BTC#1M) which looks really strange with hundereds of millions of VTL for sale and no buy order. This has nothing to do with your coin, right? Otherwise this would look like a huge scam given the fact that your ANN post states a max supply of 35 mio VTL. nope this is vitalair (an old coin, now it seems swapped to token... don't know if still alive) Nothing to do with verticalcoin. Listed only: https://graviex.net/markets/vtlbtchttps://wallet.crypto-bridge.org/market/BRIDGE.VTL_BRIDGE.BTCAh, thanks alot; that clears things up.  Nice work so far, looking forward to the new algo! |
|
|
|
Hey guys. I just discovered this project yesterday and started to mine some with my GTX 1063 ( ). What confused me was that there seems to be a market for VTL/BTC on YoBit ( https://yobit.net/en/trade/VTL/BTC#1M) which looks really strange with hundereds of millions of VTL for sale and no buy order. This has nothing to do with your coin, right? Otherwise this would look like a huge scam given the fact that your ANN post states a max supply of 35 mio VTL. |
|
|
|
Well...it says activating best chain. Still stuck. So you mean i need to just download the wallet again? ? I don't know how to cleanup or whatever.My campus coin wallet is acting fine. Edit: I downloaded the wallet again and it still is stuck on this activating best chain screen. Is my computer just too slow for this new wallet???IT opened up just fine yesterday before it synced. No, of course it's not enough to just install it again. What do you mean you don't know how to cleanup? You posted the link yourself! https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/Windows: File Explorer: %appdata%/BiblePayCore Delete blocks and chainstate folders, delete banlist, fee_estimates, governance, mncache, netfulfiled and peers If that doesn't help: In Wallet do Tools >> Wallet Repair >> Rebuild index |
|
|
|
I downloaded the bible pay wallet about 7 months ago and went overseas.
I recently returned and tried to open my wallet today but it won't connect to the network.
Do I need to download a new wallet and replace the old one with it?
Yes you will need to download new version of BiblePay, there have been a couple mandatory upgrades since then, You should be able to download and install new version on top of old version without any issues. How to Update & Clean Wallet https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/NOTE: Your "wallet.dat" file is your most important file, it has all of the keys to all of your funds. Make sure to have one or more backups of it. Backup Wallet.dat: https://www.reddit.com/r/BiblePay/comments/7lksp4/backup_walletdat/Ok,I downloaded the new wallet and let it sync last night....i woke up and it was synced but my computer was frozen saying i needed to delete some files to free space and now it just gets stuck on the block loading index screen when i try to open my new wallet. What gives? My old QT file won't open now either. I deleted other files on my computer to free up space, so that's not the problem. Should i download it again? I think the moment your disk was full the daemon corrupted some of your blockchain files. Easiest way to resolve this is to make sure you have enough disk space (the biblepaycore folder right now needs about 1.2 GiB), then do the cleanup again (as described above) and let it sync from scratch. Just remember to backup your wallet.dat and maybe your biblepay.conf and you should be good to go. |
|
|
|
WFT is up with the wallet you guys need to get a fucking grip on your updates  WTF ist up with your generalized complaining? So are you annoyed that they update too often? Is your wallet not working? No one can provide any help on your senseless rants. Newest wallet can be found here: https://github.com/stellitecoin/StelliteGUI/releasesWorks like a charm and instantly syncs with the external node. |
|
|
|
I just found I missed last POBH payment for block 53505. Is there a way to know why? Nothing changed since block 53300 and I have several PODC updates.
From the pool website, the rosseta leaderboard only has the lastest block. Is there a way to check the block 53505?
Easiest way is to check on biblepay-central.org. There is a history of PODC payments, PODC updates etc. The payments are not quite accurate, but give a good idea. |
|
|
|
At current situation on crypto, even if intense release the browser extension, it will be very hard to attract traders and investors to come immediately to intense project. Especially at this bear season. But once clients will be able to one by one try the browser extension and vn tunnel thru intense network. Then, every one will be investing lots of money into it.
I do not agree. If ITNS becomes the first FUNCTIONING, decentralized VPN and actually starts accepting tunnels, payments and so on, it will become not just a blocks of numbers, but an actual working product. Then it can compete with the centralized VPNs. If it is better, the prices will rise by itself as more people start using it. It is that simple. If we can take Storj as an example, at first the people will swarm to offer tunnel exit points, hoping to become rich. Then they will withdraw because of the low demand until the product becomes popular, which will rise it's price automatically. Also dVPN has another positive trait - the people who need it and the people who offer it live in different countries. So from it's start it will have a very large group of users from both types. I made a quick research and all other VPN projects are at the same development level, or behind. The only thing that bothers me is the infinite supply of coins.It would be interesting to hear your toughts. Well, although technically you are correct, I wouldn't call ITNS an "infinite supply coin". It has a max supply of approx. 1 billion coins with a planned tail-mining of 15 million per year (equivalent to a 1.5% annually inflation ratio). That sounds quite reasonable to me. Very excited for this project, this is one of the few coins where I actually see some kind of purpose in. |
|
|
|
For anyone interested: I just tried mining with 1063 cards under Win10 and it works! EWBF miner doesn't show errors, shares are accepted. Memory usage: card 0: 2.2 GiB card 1: 2.85 GiB (3 screens connected) Awesome work everyone! P.S.: Amazing how many bot-postings there are accumulating here the last couple of days. |
|
|
|
Hi Dave...
Thx for the reply. Here is what was in effect last night before the overnight issue showed up: I am running wallets, identical, for heat mining. On the second wallet I already have the utxooverride=-1 as the last line in the bible.conf file. As far as I can tell the second machine is not sending out PoDC updates, but I'm not completely sure. Since the wallets are the same, would I be able to actually tell on the second machine if it sent out an update versus an update going out from the primary machine? When an update goes out from the primary, does that update also show up in the transaction history on the second machine? I would think it would since they are copies of each other.
Yes, the transactions are completely mirrored. I'm not sure if you could tell which one came from which machine, but you would recognize the problem by looking at the timestamps. If your second machine also sent out the updates, there should be at least 1 occurence where 2 updates are very close together. THIS is the problem (not the multiple updates themselves...) since a podcupdate leaves you with an extremely low balance in your wallet for at least 1 block (hence the "stakebalance" step above). Then the other machine gives out the podcupdate with the extremely low balance and overrides the old one. But, I will go ahead and turn off the second machine for now and only run the primary. You seem to be implying that the problem with the auto-staking should correct itself reasonably soon?? I don't HAVE to run the second wallet, however, adding it gives me quite a boost in my hashrate which puts me up almost always in the top 10 on the leaderboard. Many times I'm number 3 behind the other 2 really big guys. If you have further thoughts please let me know. Otherwise, I will come back and update again in the next day or so when the problem resolves. I just wish there was a way to recover my superblock payment from today!  >>Edit>>>right after posting this I went back and double-checked the .conf file of the second wallet and discovered the override=-1 line was NOT there!! I know what happened. A few nights ago when the multiple updates came out and there were other problems trying to run more than one wallet, I copied the entire appdata folder for bible pay from the primary machine over to the secondary. I never went back in to add the override line. Ughh! Also, right after posting this I also found out that the auto-staking was back to normal and my utxoweight was my full balance once again. So, other than missing out on today's payments, I should be back receiving them beginning tomorrow. If something else pops up I will let you know. I hate it when it's little mistakes like this that are MY fault! (Not that I was ever blaming Rob for faulty code...lol) So let's hope that this fixes everything for you. You can always check the getboincinfo in a couple of hours, just to be extra sure. It's past midnight here, I'm gonna get some shut-eye. |
|
|
|
Hello All...
This is eyedoctrader1 writing to you asking for help with a recurring wallet problem...
I'm sorry if this is the wrong place to post something like this. I'm not sure how to navigate my way through this forum and within the BBP sub- forum.
I'm having a recurring problem with the auto-staking feature of the wallet. This problem has appeared several times in 1.1.2.4 back to 1.1.2.1. I thought with 1.1.2.7 it was gone for good until I checked in to the pool this morning and saw that I was missing from today's superblock. I've got nearly 30,000 RAC and over 661K BBP with over 3.5 Magnitude. I don't understand why this should ever be an issue. When I check the distributed computing tab it shows my UTXOWeight = 2983. This is the number is always goes to when it isn't showing the correct wallet total balance. There are no errors in either getboincinfo or getmininghash. When this problem occurs it leads to two things. I lose my superblock reward for that particular day (I didn't get today's that came out about an hour ago), and, it shuts me out of heat mining for the duration of the next superblock period (25 hours). So, I'm being penalized on both sides when I am fully qualified to receive the heat-mined coins and the superblock. If I wasn't earning over 4K per day on the superblock I might not care so much about this, but $10 USD/day is nothing to sneeze at.
If someone in the know could look into this and help me correct the problem I would appreciate it immensely. By the way, I am not the only one this is happening to. When I look at the superblock list I see the usernames of others, like "lichtsucher" who have been sent into the mining dungeon.
Thanks so much for your assistance, and Lord Bless!
---Stephen
Hello and welcome to the forum. This looks alot like a problem I had several weeks ago and the solution was very simple: I had copied my wallet to other machines for heat mining and on one of them I forgot to put "utxooverride=-1" in the config. The result was that this wallet too sent podcupdates and those rivaled with the other ones from the "controller wallet". So if this is the case with you it would be a fast solution. In case you checked all your heat miners and they all have utxooverride=-1 then to be extra sure you could do the following: Stop all heat miner wallets and only leave your main (controller wallet) running for a couple of days. Regularly check the podcupdates (in "transactions" tab and with "exec getboincinfo"). If there are still strange utxoweights ocurring, then perform the podcupdate manually. For that you have to: 1. "exec stakebalance" --> only proceed if this shows your full wallet balance! 2. "exec podcupdate true" --> should give " performed .... over 1 CPIDs successfully". Good luck and God bless! |
|
|
|
Anyone who was testing 1.1.2.6 and had mining problems, please upgrade to 1.1.2.7.
The race condition should be fixed now...
Note in 1.1.2.7 getmininginfo will show something to the effect of "Loading CPIDs" until the wallet is warmed up.
Sorry about the inconvenience.
Yep, starts and runs smoothly now with gen=1 in the config. Running getmininginfo directly after startup gives the new info "Please wait for CPIDs to be memorized..." (besides "Submitting Solution..") which is resolved after a minute or so. Nice work! @Lichtsucher: I'd love to have this version in the Ubuntu PPA to use it on my Raspberries. |
|
|
|
So your CPID is in the chain and it cant send a podcupdate, interesting. Alright please see if downgrading actually solves it; I only have 1.1.1.9, which should be OK for this, here is the link: https://pool.biblepay.org/downloads/biblepaycore-1.1.1-win64.exeI'll check further into the problem. Before you downgrade please try this and tell me if it solves it so we know the problem: Boot wallet Wait 5 mins Type exec getboincinfo (Verify the CPID is present) Type exec podcupdate (Verify you dont see the error that no cpids exist that you saw before) Then do: (This means you start the miner *after* exec getboincinfo was called) setgenerate true 5 (or whatever number) getmininginfo Tell me if it mines. I think the problem is that 'exec getboincinfo' has to be run before 'setgenerate true X'. If that is the case its a race condition that needs a line of code during boot to fix 1.1.2.6. Yep, that's exactly it! What I did: 1. Stop wallet. 2. Change to "gen=0" in config 3. Start wallet, wait shortly. 4. exec getboincinfo was successful 5. exec podcupdate was successful (!) 6. setgenerate true 4 7. getmininginfo showed no errors (!) Nice troubleshooting. btw: it's almost midnight, I'm going to bed now. |
|
|
|
I don't see a problem with 1.1.2.6, this looks to be on your end.
Classic IT response.. I'll sit back and watch if others encounter issues. edit2: Same message on testnet with a "clean" install and associated cpid. ... Let me check into this... I dont see a problem with 1.1.2.6, Im still mining after 24 hours. To diagnose this in prod, first type: exec datalist dcc;YYYY 365 Where YYYY equals the first 4 chars of your CPID. Paste the results here. Step 2: Type 'exec podcupdate' and paste the results here. I'm sure the other person who had the problem resolved itself after the prayers were memorized. The high cpu usage during 15 seconds after the GUI loads is just the prayers being memorized in the background. You should leave the machine on for at least 10 minutes of mining to see if the errors clear. Wallet has been running for hours, but no POBh possible. {
"DataList": "DCC;7C92",
"4559FEF3C1C689EE9FC3FF42494 (03-07-2018 20:01:05)": "7c9264559fef3c1c689ee9fc3ff42494;BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh;BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh;1981794;IIN5nTV5xxNV9tflryvwAcWzvf9WyxKPUx1XxpKGl1tgOZQ3uXzDIxPgjxxTtUIyZXHa1TMzDuTFcPDS7cl/U10=;0"
}{
"Command": "podcupdate",
"PODCUpdate": "Unable to find any CPIDS. Please try exec getboincinfo."
}Thx for looking into this. In the meantime: is there an archive with the old 1.1.2.4 win64-install? I'd like to go back to that for the time being... Edit: now, after approx. 5 hours, it seems to have sorted itself out again. PODCUpdate also works again. The datalist output remains the same. |
|
|
|
So I tested 1.1.2.6 on my two Windows machines (old Thinkpad Win7, newer Xeon Win10). Here's what I see so far: 1. The startup is indeed much faster without the "memorizing prayers" step. Nice work there. 2. After the wallet opened there is a longer period of time with huge CPU utilization. This is the "memorizing prayers" step I suppose? 3. I immediately got the CPID errors mentioned by thesnat. 4. The self-payment Rob suggested helped this error for approx. 1 minute, then it returned. 5. The errors are independent of OS and occur on both pools (main pool and purepool) alike. Hope this helps a bit. Edit: Well, that's strange. On my Win10-Xeon it seems to have sorted itself out after maybe 10 minutes and is now submitting solutions as usual. On the Win7-Thinkpad getmininginfo is still full of CPID errors. Thanks Dave, Glad i'm not crazy I realized that actually it also sorted itself out on my Win7 laptop, just much later. So it seems to be a problem of time (or rather of number of submitted shares?). I then tried closing the wallet and starting it again and - lo and behold - the errors were back. Also without the "bug-fixing" self-payment they persist over hours. I now made the transaction again but for 20 minutes it hasn't solved the errors yet... |
|
|
|
|
Show Posts
