Search results

yes italx It's on the mental roadmap. next few updates are going to be: ipv6 support system lib (/usr/bin /usr/local/bin) support notification when protocol is updated (to resend masternode starts) testnet support (which will probably require arbitrary directory location support first) If...

https://github.com/moocowmoo/dashman *now with voting goodness! (beta) dashman DASH wallet/daemon management utilities - version 0.1.9 This script installs, updates, and manages single-user dash daemons and wallets It is currently only compatible with 32/64 bit linux. Multi-user (system...

No need to apologize. I apologize for being curt. Rest assured I'll keep your information confidential. Please email me at [email protected] so I can notify you when *needed*. It's part of the service you're paying for. :)

you are way over thinking this. Send me your email and get notified when action is required on your part, or don't and keep up with dash's development releases and changing requirements. I recommend the first option.

You're welcome. I do my best to keep things secure. Yes, so please do send an email so I can get in touch if need be. As far as twitter goes, with two-factor auth and using a vpn it's secure enough for direct messages. The message contents aren't anything that would require high...

I use zerobin.net for anything confidential. the "burn after reading" setting guarantees either: only you have access to the message, or you know it was compromised (because the message isn't there to read) I intend to automate the renewal process eventually, but having a way to contact users...

hi nemo, thanks for signing up! when your subscription nears expiration I'll email you a reminder with the payment address and amount. email me at [email protected] also follow me on Twitter for occasional direct message updates: @masternode_me feel free to ask any questions you may...

This is a normal phase of startup. The node is waiting to see it's start signal /from the network/. removing cache files is a good practice in my experience. on upgrades, dashman does: rm -f budget.dat debug.log fee_estimates.dat mncache.dat mnpayments.dat peers.dat

something like that, but I'd do the right hand side in a separate script. dashman does: dash-cli stop 2>&1 >/dev/null sleep 10 killall -9 dashd dash-shutoff 2>/dev/null note: on slower systems, ten seconds is sometimes not enough time for dashd to complete it's cleanup.

It *prompts* to install if missing. And, yes/no -- talking directly to dashd just leaves one less thing to sit and hang -- curl will timeout after ten seconds (latest commit). dash-cli [command] can hang indefinately.

here's a script/cron component that should help you guys out: https://github.com/moocowmoo/dash-rpctest

Don't keep spawning dashd. You're wasting cpu, log space, and time. You could probe rpc for a response using curl. curl -v --user rpcusername:rpcpassword --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;'...

I can't help you without specifics. Is the process still running? Is rpc not responding?

You're welcome. The backticks `` are a bash-style command substitution. Using $() is more portable, but I still have the backtick habit too.

MangledBlue, Sub-Ether Specifically HOW does dashd crash?

That's incorrect, that's now how pidof works.

The crash issues you are having aren't very common. I run dashd on a vps with 256M of ram (with 1G of swap) and have no crashes whatsoever, so the issue isn't your ram. It may be environmental too, radio noise from neighboring electronics could cause trouble, it's an unshielded board. Are there...

I think this is a huge con. If the system were to deterministically select one of the previous n-blocks of mixing transactions for payment, chances are high people would try to game the choice by mixing with multiple wallets to create more 'tickets'. I don't see how this could be detected using...

wif is 'wallet import format' and is one form of a private key. It starts with X Try the instructions online (one computer, no usb key) with a throwaway/temp key and see how the process works to get the hang of it. And, don't forget, once you have a paper wallet: print two copies, keep them...

That will work fine, but qt doesn't import bip38 keys. You'll have to use your wif for qt. So you'll have to generate a paper wallet, copy the wif, bip38 encrypt it, print it. Then import your copied wif into qt.