Search results

I'll be open sourcing a python library I developed for the soda machine InstantX demo in Miami soon. Today, it takes watching the p2p traffic and keeping track of the received messages. There are plans to make this easier to use, but I'm hoping the library will act as a roadmap for developers...

it couldn't get the version from github. notice how it said "latest version is :" but had no version? I'll push a patch for a better error message later tonight. I agree that's confusing. in this instance, it's good it didn't let you continue. if you can't contact github, you can't vote...

I've built another python script for tracking the current budget status. It's new, but I'm pretty sure I've squashed all the big bugs. As always, let me know if you run into trouble. (If you're seeing old proposals, stop your wallet, delete budget.dat, and restart it. It will pull in an...

Hello everybody, I've found that different pi os' behave better than others, but don't have a solid production-worthy recommendation (yet!) For the dash soda machine, we're using the latest osmc build. Its kernel seems to have played the nicest with dashd. (I put dashd on my home osmc/kodi...

Hi Greensheep, Sorry for the delay, been busy preparing for Miami. Here's some answers to your questions: That whitepaper can be found here: https://dashpay.atlassian.net/wiki/display/DOC/Whitepaper The last x11 hash, current blockchain tip, is the entropy for the deterministic selection of...

hehe, thanks camosoul Yeah studioz, right now the code is prototype quality -- I'm going to refactor everything, document it, and release it on github sometime after Miami.

you're welcome -- vagrant makes it easy. And thanks! --- nope, not your masternode.conf -- needed another compatibility patch. python3 compat is turning out to be a pain. python2 is a dependency for now. git pull the arch branch -- should work now!

nightowl -- pushed a temporary patch onto the arch branch. git remote update ; git checkout arch ; ./dashman status The issues were a) not recognizing your package manager and b) gnu netcat has different switches. I've got a pure python implementation in the works, but this branch should work...

Glad to hear it! You're welcome. Get the github version if you haven't already, it shows the queue position too. Thanks! The more I write, the faster I can. I love discrete projects like this.

This should work for you Bridgewater just change the paths at the top to point to your dash-cli and masternode.conf locations. Enjoy! https://github.com/moocowmoo/masternode_conf_check

dashman status only works on a local instance in version 0.1. version 0.2 will be complete in a few months and will be able to give you remote statuses. (you'll run an instance of dashman on each masternode and you'll be able to query them remotely)

I recommend using a different linux distribution for now. There are too many little differences to patch out. The pure-python version I'm working on will not have most of these dependencies.

happy new year! I'll spin up a fedora20 today and see if I can find a quick workaround for you. edit: turns out fedora uses a different netcat https://www.redhat.com/archives/fedora-list/2009-January/msg01114.html i'm looking to see if I can make it work now.

Excellent news! Voted! to vote with (linux only) dashvote, have your dash-cli and masternode.conf in ~/.dash and do: git clone https://github.com/moocowmoo/dashman.git dashman/dashman vote You'll be prompted to install any missing dependencies if needed.

fixed. ;) Thanks for the notify! added to all ssl sites on the server SSLProtocol ALL -SSLv2 -SSLv3 SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH

You're fighting against the way the internet works is why. They're called third level domain's and are pretty standard. There is no ssl certificate for dash.org, only a wildcard cert for *.dash.org. This wildcard allows use across a variety of hosts such as: (examples only) ftp.dash.org...

Like Solarminer said, a pi isn't the ideal platform for some of the more advanced things an evolution node will eventually be tasked to do. But, I think building some images for people to plug-and-play wouldn't be a bad idea. In the same vein as NOOBS, images that can be burned, plugged-in...

We'll need to support password changes in case of system compromise, so directly generating some of this key material from the password isn't an option. I'm drafting up something that will address this and will post it later.

Regarding sorting, never assume when you can enforce. Especially if your using diff to detect changes. Name, url, and budget are fixed. They can't change within a given budget. Considering the rpc call 'mnbudget getinfo' uses the name to pull the info (it probably should be using the hash)...

a slightly more robust version for you to vet: #!/bin/bash notify_email="[email protected]" BUDGET_NAMES=$(dash-cli mnbudget show | grep Name | awk '{print $3}' | sed -e 's/[",]//g' | sort) echo "$BUDGET_NAMES" > /tmp/current_budgets if [ -e /tmp/previous_budgets ]; then...