Topic: 🆗[ANN][OK] Okcash | ⚡Fast | LTSSposv3hybrid | Easy to use | Reliable | ROKOS ✅ - page 102. (Read 459151 times)

I have been running OKcash wallet for almost 2 years now (before and after rebrand). Never had any corruption problems on windows. I do have UPS, so i have enough time to shutdown my system if i loose electricity. Considering you're holding virtual money in your wallet i would suggest to invest money in UPS protection to protect your virtual money!

I don't mean to be rude either. My reaction came after I saw that user galixxx "solved" his problem by "starting over"... and not mentioned the system restarts (a thing that most users "forget" to mention and/or do). Also, my point about windows operating systems being very forgiving with filesystem errors still stands, even in the case of NTFS (which is a very robust filesystem, btw).
User vagos mentioned very clearly he encountered that problem once, after a power failure and he solved it by reinstalling the wallet and the blockchain and restarting the machine.
Your claim that OKcash is the only coin whose wallet gave you grief after the power failures made me check your post history... and, lo' and behold, some pattern emerged...
https://bitcointalksearch.org/topic/m.15844688
https://bitcointalksearch.org/topic/m.15450613
Well, I see that your enthusiasm is great, but your patience might be lacking sometimes, as you seem to be prone to "burn through the details". Trust me, the devil we're looking for is in those details... Mounting filesystems is similar in both worlds, windoze and *nix/linux, filesystems errors are treated in similar ways... it's just the user-observable effects that make a difference.
I uphold my previous statement: it is not the OKcash wallet/daemon's fault, it is the filesystem corruption.
Engineering is cool, but it takes a lot of science and patience.

Sorry to hear, very strange, not sure i've seen this one happen yet before.  We are live most of the time on discord.okcash.co come stop by and we can work through it.

Straight up this don't happen with any other coin, so don't blame hardware, just not going to put up with that .... it's the one and only coin I have ever had do it, on top of which it happens on all platforms, again, don't blame hardware. Don't mean to be rude, I am asking for a fix to this, not to have my hardware be blamed for something no other coin has ever had the problem of.... thanks for your input

For windoze: read the nice article at HowToGeek http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/
or
- restart in "Safe mode with command prompt only" and run
Answer with "Y" (for "Yes") at the prompt of scheduling scan at the next reboot,
- then reboot with

For Linux: read the nice article at MakeTechEasyer https://www.maketecheasier.com/check-repair-filesystem-fsck-linux/
and follow your frontal cortex's lead

It would be best not to get your filesystem(s) corrupted in the first place. That can be achieved by eliminating as many causes of forced restarts and/or shutdowns: power failures, inappropriate user action, "bad" software executed with administrative privileges... and so on.
Another major cause for filesystem corruption is the media itself. Low cost HDDs can cost you more than their price tag if you store significant informations on them and forget to backup... Low cost SSDs might have bugs in controller's firmware and/or much less write cycles than regular or premium models...
Bottom line is: devs can't really do much in that regard if the user doesn't protect it's filesystem(s) properly, they can perform time-consuming checks and/or reindexing, they can force an even more time-consuming sync either from scratch or by a bootstrap (big question of trust here), but that's about all I can think of.
As far as I am concerned, this problem is PEBCAK. Oh, well, we all should use more resilient hardware and filesystems and pay only fractions of cents (if ever), right?

Happen to me once, I fixed it by just using the installer and reinstall OK, restarted my comp and all was working again. (yes happened during power failure too)

There is a bunch of times I have opened my wallet (on win 7, 10 and my Pi) and found my wallet file has become corrupted, at least I think it is, only copying over a new wallet file seems to fix the error, I have found this to be a consistent problem during power failures of my devices. Is there a way I can stop this from happening or is there a Fix devs can do that will stop this, I have never had this problem with any other coin wallet before dispite having run thus far at least 20-30 wallets of different coins at times over the last 3-4 years... thanks guys.

We added your cryptocurrency.
With respect, the development team of Crypto-trade.
Crypto-Trade – Official Announcement https://bitcointalksearch.org/topic/crypto-trade-official-announcement-10-fiat-365-crypto-5300-pairs-1604225

I'm glad to know it worked out well.
I didn't encounter those issues on my OKcash wallet(s) under Linux, regardless of wallet version, so I assumed something Internet/network related.
Now, after your post, I can think of file and/or file system corruption as a possible cause, being well known that windoze is too eager to push that kind of issues "under the carpet" in order to keep the user happy...

Quick update on my synching issue.
I was able to fully sync my wallet. Solution was to wipe out roaming/OKCash and start from the beginning. I downloaded bootstrap file from http://cryptochainer.com/dir/?page_id=365. Deletion of just the peer.dat didn't help! Firewall port setting was also not the solution in my case.
Thanks everyone for your support! Much appreciated.

from: http://okcashtalk.org/index.php/topic,1881.0.html


The Arch User Repository (AUR) is a community-driven repository for Arch users.
It contains package descriptions (PKGBUILDs) that allow you to compile a package from source with makepkg and then install it via pacman.

AUR Okcash-git (Graphical wallet) - https://aur.archlinux.org/packages/okcash-git/
AUR Okcashd-git (daemon) - https://aur.archlinux.org/packages/okcashd-git/

By Maintainer Dev: greenbigfrog


A good number of new packages that enter the official repositories start in the AUR.
In the AUR, users are able to contribute their own package builds (PKGBUILD and related files).
The AUR community has the ability to vote for or against packages in the AUR.
If a package becomes popular enough — provided it has a compatible license and good packaging technique — it may be entered into the community repository (directly accessible by pacman or abs).

My current promo ends 9/19 sometime later in the day.. I'll make a final post, after that it won't count.  IF you don't know what i'm talking about, you are missing out on free okcash.

Check your firewall(s). https://www.grc.com/shieldsup is a good place to start. Look for ports 696 and 6970 (they must be open).
As MagicStyle said, you might have been "peer blocked" and you'll have to delete the "peer.dat" file (with the wallet turned off).
If you're on windoze... well... check your antivirus firewall (if any), then your windows firewall, then your router firewall (and settings).

Thank you MagicStyle and OKorator I will check when I'm back home. I let you know of the outcome :-)

Stop by our discord for live support

discord.okcash.co

maybe getting peer blocked, go to /appdata/roaming/okcash and with your wallet off, delete the peers.data file and turn on your wallet,
give it a bit of time and should get fixed

Hi,
My wallet is not synching properly since 23 hours.
I am stuck on block 878240.
Any advise what I can do?
I am using newest wallet version 4.0.0.0-g
Thanks!

Be sure to check out livecoin... okcash is up for voting on there.  Looks like we'll need to do paid votes to take the lead.. not a priority, but lets get a start!

https://www.livecoin.net/voting/index?lang=en

Hahaha @ Okorator, I cant stop watching those cats waiting for OK to be on polo as well. I hope it will be soon. Then it will be great

I can't stop watching this  

Glad you are back!