* New! Latest stable version of OK wallet v7-SpaceMonkey *


Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - rmd73

Romana (Romanian) / Bine aţi venit!
December 06, 2016, 05:14:17 PM
Mă bucur să văd români interesaţi de cripto-monezi alternative.
Această secţiune este dedicată vorbitorilor limbii române, iar în acest topic ne putem prezenta şi/sau (re)cunoaşte  :P
Quote from: jamesdelelio on November 27, 2016, 09:12:24 AM
problem is two fold.
1st you can not start/initiate the Bitcoin wallet for the first time from a remote computer; keyboard and monitor must be connected to the Pi directly.

2nd. permission must be set for media/pi/mounted volume fot the user to acces. I used sudo chmod -R -v 777 * and that worked (not sure if it is the best security setting...)

So now I have 248Gb Volume created from 2 tiny 128Gb Sandisk Ultra Fit usb 3.0 flash drives, nice, neat and small package  8)
Tip:  Format USB sticks to Flash Friendly File System (f2fs) instead of the Linux ext4 file system to avoid errors
Re: 1st. I think bitcoind can be started for the first time from a remote computer (via ssh) and I can't see why it wouldn't run if started for the first time using a VNC connection... but I never tried any of those scenarios.
Re: 2nd. I would have used chown -R pi /media/pi/mounted_volume

I wouldn't use software defined RAID on any "production" machine (unless forced), especially RAID 0... the risk of data loss is staggering.
Disregarding my an**l-retentive comment above, congrats :D
Quote from: okheymos on December 03, 2016, 02:12:02 AM
Quote from: chrispop on December 02, 2016, 08:20:05 AM
Greetings from Romania! I have joined this forum after I've seen the okcash awareness promotion on the discord app. You can also find me on burstforums and bitcointalk.  :P

here's my OK address: PGawGGD9ehedcJAYRwVX2ygFzin93yhe4s

Greetings, welcome to your forums! OK Sent  :P
Salut, concetăţene! :D
Nice! That finally made me to get a github account :D
OKcash address: PNFzUL1bUD91nAfP3W3kAzjsHiDqewLFdx
If one is using Windows 7 or newer and doesn't shut down properly the computer (or power failures are occurring), the file system might be the culprit (along a few other compounding factors to be mentioned a bit later).
Also, if the "hibernate" or "suspend" features are used, the "peers.dat" can end up containing peers that banned one's host on grounds of misbehavior (i.e. they initiated a request, one's host started to respond then went silent for the rest of the communication).
On top of those two major reasons (largely ignored by users and, hopefully, less ignored by devs), there lies another monster reason for apparently inexplicable behaviors: leveldb 4.8, the most used database in crypto-currencies wallets and daemons. Just read about leveldb on Wikipedia:
QuoteLevelDB is widely noted for being unreliable and databases it manages are prone to corruption.[13][14][15][16][17][18][19][20] Academic studies of past versions of LevelDB[21][22] have found that, under some file systems, the data stored in those versions of LevelDB might become inconsistent after a system crash or power failure. LevelDB corruption is so commonplace that corruption detection has to be built in to applications that use it.[23]
Even the mighty Bitcoin is prone to database corruption, but with code managed by an entire foundation... I bet their code includes checks and repairs that other devs are just not noticing... and even so, BTC core wallet might give a bit of tachycardia to a quite large userbase from time to time.
Lesson to learn: back up your "wallet.dat" AND your private keys in as many (secure) ways you can imagine. Then, in case of a malfunction, use your brain to figure out what might have happened, then try to solve the problem by yourself in a consistent and rational way. If that doesn't work (you reached the limits of your current knowledge), then ask politely for help.
Usually, when troubles occur, reinstalling and resync-ing (either from scratch, from a bootstrap.dat or from a database snapshot) solves the problem. But, if the problem is user's behavior... there's not much to be done.
With One-Way Light Time (OWLT) ranging from a minimum of about 4 minutes to a maximum of about 24 minutes, I think synchronization of the block-chain would be at least problematic... considering the average block time of 72 seconds.
Pretty old in OKcash, greetings from Romania :)
OKcash is a gem... can't pass the opportunity  8)