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.

Messages - rmd73

Pages: [1]
ROKOS Dev and Tech Discussion / Re: Suggestions
« on: Today at 01:46:22 AM »

I think wondershaper was good at the beginning of the 2000s (2002 - 2006), but it is not a viable solution when modern equipments and bandwidths are in use (I found a better explanation than I intended to reply with at ).
I am not very sure about db cache, but it seems that it might allow devices with lower RAM specs to run the daemon(s) without too much swapping... it's an interesting suggestion if it turns out to be possible, but one must take into account the size of the blockchain and the way buffers are allocated by the OS... Anyway. it seems that there is work done to replace BerkeleyDB in Bitcoin (and possibly other relevant alts), so it might be less than optimal to address this now.
The LCD support depends on device and the graphics driver's quality/configurability. AFAIK Pine64 already has a LCD display for sale. Not sure about RasPi. I admit I've fallen a bit behind the news ;)

Romana (Romanian) / Bine aţi venit!
« on: 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

ROKOS Tech Support / Re: Raspberry Pi raid array with USB HDDs
« on: December 06, 2016, 05:02:18 PM »
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

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

Service Discussion / NoblePay
« on: November 11, 2016, 05:01:39 PM »
First evaluation of NoblePay (app for Android):
211 ERC * 0.00005295 BTC/ERC (bid on bittrex) = 0.01117245 BTC
0.01117245 BTC * 715 USD/BTC (bittrex) = 7.98830175 USD
1 USD = 0,921879897 EUR
0.01117245 BTC = 7.98830175 USD * 0.921879897 EUR/USD = 7.364254794 EUR

Noblepay asks 210.94089236 ERC for 10 EUR in SEPA transfer (European bank transfer).
That's a 2.635745206 EUR markup for the service. Not too bad for a start, considering the fact that NoblePay is operated by a business from Australia.
I haven't tried the actual transfer yet... but I might do it towards the end of the month...

It works well. The "auto-sync" feature ("./" in terminal) is awesome.
If proper power supply is used (5V, min. 2A) the lil' gem is stable.
One might want to "mod" the Pine64 by mounting a heat-sink on the ARM processor, as this might get a bit warm (towards "hot" ~ 45-50 degC) in certain circumstances, but that is not required.

I didn't like the poswallet from the beginning, hence I didn't even bothered to open an account on their site... The first red flag was rised by the (almost) complete lack of company info. I admit the bias of a previous unpleasant experience with staisybit, but at least there were a couple of RL identifiable guys that could pull a few strings around the staisybit's dev/operator (and thanks to them for that!).
The second red flag was the absence of a "terms and conditions" page and the absence of a "privacy policy"... let alone a FAQ.
All in all, you better get an inexpensive piece of hardware like a Raspberry/Banana Pi or a Pine64, a 16GB SDcard (class 6 would be just fine and less costly than a cheap class 10), install ROKOS and stake like a champ. For those in Microsoft's leash, a second-hand laptop under $150 would be much better...
I wish that poswallet will prove me wrong, but I doubt it. In the long term, greed overcomes even the best of intentions, more so when no enforceable contract is involved.

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:
LevelDB 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.

Staking & Technical Support / Re: OKCash Wallet in Space?
« on: October 10, 2016, 04:21:34 PM »
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)

Pages: [1]