[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 814.

Lebubar

legendary

Activity: 1288

Merit: 1000

Quote from: JGCMiner on February 25, 2017, 02:20:24 PM

Quote from: Quartz-Team on February 25, 2017, 02:15:42 PM

Re. Dashman, can someone please help:

I follow the instructions in the GitHub repo and get this:

Code:

root@mn01:~# sudo apt-get install git
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. 
root@mn01:~# sudo dpkg --configure -a
root@mn01:~# sudo apt-get install git
Reading package lists... Done
Building dependency tree       
Reading state information... Done
git is already the newest version.
The following packages were automatically installed and are no longer required:
  linux-headers-3.13.0-101 linux-headers-3.13.0-101-generic
  linux-headers-3.13.0-108 linux-headers-3.13.0-108-generic
  linux-headers-3.13.0-91 linux-headers-3.13.0-91-generic
  linux-headers-3.13.0-92 linux-headers-3.13.0-92-generic
  linux-headers-3.13.0-93 linux-headers-3.13.0-93-generic
  linux-headers-3.13.0-95 linux-headers-3.13.0-95-generic
  linux-headers-3.13.0-96 linux-headers-3.13.0-96-generic
  linux-headers-3.13.0-98 linux-headers-3.13.0-98-generic
  linux-image-3.13.0-101-generic linux-image-3.13.0-108-generic
  linux-image-3.13.0-110-generic linux-image-3.13.0-91-generic
  linux-image-3.13.0-92-generic linux-image-3.13.0-93-generic
  linux-image-3.13.0-95-generic linux-image-3.13.0-96-generic
  linux-image-3.13.0-98-generic linux-image-extra-3.13.0-101-generic
  linux-image-extra-3.13.0-108-generic linux-image-extra-3.13.0-91-generic
  linux-image-extra-3.13.0-92-generic linux-image-extra-3.13.0-93-generic
  linux-image-extra-3.13.0-95-generic linux-image-extra-3.13.0-96-generic
  linux-image-extra-3.13.0-98-generic
Use 'apt-get autoremove' to remove them.
Suggested packages:
  fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools
  linux-headers-3.13.0-110-generic
The following packages will be upgraded:
  linux-image-3.13.0-110-generic
1 upgraded, 0 newly installed, 0 to remove and 57 not upgraded.
1 not fully installed or removed.
Need to get 0 B/15.3 MB of archives.
After this operation, 43.3 MB of additional disk space will be used.
(Reading database ... 320122 files and directories currently installed.)
Preparing to unpack .../linux-image-3.13.0-110-generic_3.13.0-110.157_amd64.deb ...
E: Sub-process /usr/bin/dpkg returned an error code (2)

and:

Code:

root@mn01:~# cd dashman
root@mn01:~/dashman# ./dashman update
missing dependency:  unzip
 --> sudo apt-get install  unzip

This is not the best place to get speedy support... I would head over to the Dash nation slack. Plenty will help you there (often times moocowmoo himself)

https://dash-nation-invite.herokuapp.com

You need to install unzip:

Code:

sudo apt-get install  unzip

or

Code:

apt-get install  unzip (as root)

EDIT: Don't run dashman as root but as user with which you installed/run dashd.

JGCMiner

hero member

Activity: 611

Merit: 500

Quote from: Quartz-Team on February 25, 2017, 02:15:42 PM

Re. Dashman, can someone please help:

I follow the instructions in the GitHub repo and get this:

Code:

root@mn01:~# sudo apt-get install git
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. 
root@mn01:~# sudo dpkg --configure -a
root@mn01:~# sudo apt-get install git
Reading package lists... Done
Building dependency tree       
Reading state information... Done
git is already the newest version.
The following packages were automatically installed and are no longer required:
  linux-headers-3.13.0-101 linux-headers-3.13.0-101-generic
  linux-headers-3.13.0-108 linux-headers-3.13.0-108-generic
  linux-headers-3.13.0-91 linux-headers-3.13.0-91-generic
  linux-headers-3.13.0-92 linux-headers-3.13.0-92-generic
  linux-headers-3.13.0-93 linux-headers-3.13.0-93-generic
  linux-headers-3.13.0-95 linux-headers-3.13.0-95-generic
  linux-headers-3.13.0-96 linux-headers-3.13.0-96-generic
  linux-headers-3.13.0-98 linux-headers-3.13.0-98-generic
  linux-image-3.13.0-101-generic linux-image-3.13.0-108-generic
  linux-image-3.13.0-110-generic linux-image-3.13.0-91-generic
  linux-image-3.13.0-92-generic linux-image-3.13.0-93-generic
  linux-image-3.13.0-95-generic linux-image-3.13.0-96-generic
  linux-image-3.13.0-98-generic linux-image-extra-3.13.0-101-generic
  linux-image-extra-3.13.0-108-generic linux-image-extra-3.13.0-91-generic
  linux-image-extra-3.13.0-92-generic linux-image-extra-3.13.0-93-generic
  linux-image-extra-3.13.0-95-generic linux-image-extra-3.13.0-96-generic
  linux-image-extra-3.13.0-98-generic
Use 'apt-get autoremove' to remove them.
Suggested packages:
  fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools
  linux-headers-3.13.0-110-generic
The following packages will be upgraded:
  linux-image-3.13.0-110-generic
1 upgraded, 0 newly installed, 0 to remove and 57 not upgraded.
1 not fully installed or removed.
Need to get 0 B/15.3 MB of archives.
After this operation, 43.3 MB of additional disk space will be used.
(Reading database ... 320122 files and directories currently installed.)
Preparing to unpack .../linux-image-3.13.0-110-generic_3.13.0-110.157_amd64.deb ...
E: Sub-process /usr/bin/dpkg returned an error code (2)

and:

Code:

root@mn01:~# cd dashman
root@mn01:~/dashman# ./dashman update
missing dependency:  unzip
 --> sudo apt-get install  unzip

This is not the best place to get speedy support... I would head over to the Dash nation slack. Plenty will help you there (often times moocowmoo himself)

https://dash-nation-invite.herokuapp.com

Quartz-Team

newbie

Activity: 24

Merit: 0

Re. Dashman, can someone please help:

I follow the instructions in the GitHub repo and get this:

Code:

root@mn01:~# sudo apt-get install git
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. 
root@mn01:~# sudo dpkg --configure -a
root@mn01:~# sudo apt-get install git
Reading package lists... Done
Building dependency tree       
Reading state information... Done
git is already the newest version.
The following packages were automatically installed and are no longer required:
  linux-headers-3.13.0-101 linux-headers-3.13.0-101-generic
  linux-headers-3.13.0-108 linux-headers-3.13.0-108-generic
  linux-headers-3.13.0-91 linux-headers-3.13.0-91-generic
  linux-headers-3.13.0-92 linux-headers-3.13.0-92-generic
  linux-headers-3.13.0-93 linux-headers-3.13.0-93-generic
  linux-headers-3.13.0-95 linux-headers-3.13.0-95-generic
  linux-headers-3.13.0-96 linux-headers-3.13.0-96-generic
  linux-headers-3.13.0-98 linux-headers-3.13.0-98-generic
  linux-image-3.13.0-101-generic linux-image-3.13.0-108-generic
  linux-image-3.13.0-110-generic linux-image-3.13.0-91-generic
  linux-image-3.13.0-92-generic linux-image-3.13.0-93-generic
  linux-image-3.13.0-95-generic linux-image-3.13.0-96-generic
  linux-image-3.13.0-98-generic linux-image-extra-3.13.0-101-generic
  linux-image-extra-3.13.0-108-generic linux-image-extra-3.13.0-91-generic
  linux-image-extra-3.13.0-92-generic linux-image-extra-3.13.0-93-generic
  linux-image-extra-3.13.0-95-generic linux-image-extra-3.13.0-96-generic
  linux-image-extra-3.13.0-98-generic
Use 'apt-get autoremove' to remove them.
Suggested packages:
  fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools
  linux-headers-3.13.0-110-generic
The following packages will be upgraded:
  linux-image-3.13.0-110-generic
1 upgraded, 0 newly installed, 0 to remove and 57 not upgraded.
1 not fully installed or removed.
Need to get 0 B/15.3 MB of archives.
After this operation, 43.3 MB of additional disk space will be used.
(Reading database ... 320122 files and directories currently installed.)
Preparing to unpack .../linux-image-3.13.0-110-generic_3.13.0-110.157_amd64.deb ...
E: Sub-process /usr/bin/dpkg returned an error code (2)

and:

Code:

root@mn01:~# cd dashman
root@mn01:~/dashman# ./dashman update
missing dependency:  unzip
 --> sudo apt-get install  unzip

Taylor05

sr. member

Activity: 265

Merit: 250

Proposal: Business Development - BlockCypher Maintenance

https://www.dash.org/forum/threads/proposal-bus-dev-blockcypher-maint.13286/

This proposal funds the maintenance portion of the BlockCypher contract, which is already passing.

qwizzie

legendary

Activity: 2548

Merit: 1245

http://www.coindesk.com/who-broke-the-sha1-algorithm-and-what-does-it-mean-for-bitcoin/

Quote

It's important to stress that the cryptography underpinning the bitcoin network, which makes use of the more secure SHA256 algorithm,
is not directly affected by the discovery,

But, besides enriching the mystery bounty recipient, the SHA1 collision vulnerability does pose a concern for the bitcoin development community,
since its Git version control system uses SHA1 to generate the hash digest for commits.

"The consequences aren't that we have to stop using Git immediately," Todd said, "but it will make it more important to review other people's work,
because a third party could try to push a malicious commit in."

The vulnerability here is that an attacker could theoretically create two different versions of a code commit that would appear to be the same when
hash values were compared – though for now, given the vast number of computations still needed to find a collision, it's highly unlikely that could happen.

I assume Dash does not rely on sha1 in any way ? Not even in Github ? (Dash is using X11 algorithme after all). I do wonder if this kind of advanced method of generating hash
collision can also be used on alternative cryptocurrencies like Dash, Euthereum, Ripple, Litecoin ?

The article shows us something we should never forget : that the whole cryptoscene is involved in a technological battle between those that want to break encryption and those that want to have encryption.

bizzyb

legendary

Activity: 1652

Merit: 1001

Don't look at my signature!

Dear DASH community we are accepting DASH on our Forex trading platform with 100% bonus on initial deposits

https://muex.io/Forex

qwizzie

legendary

Activity: 2548

Merit: 1245

Quote from: UdjinM6 on February 25, 2017, 12:11:04 PM

Quote from: JGCMiner on February 25, 2017, 11:09:11 AM

It is strongly recommended that everybody update to the latest version 12.0.2 as well as the latest sentinel. Moocowmoo's Dashman makes this very quick and easy. The sooner most of the network is on 12.0.2 the earlier enforcement can be reenabled. It will be nice to get InstantSend back and not have to worry about the off-chance of a greedy miner not paying one of my nodes. Wink

https://github.com/moocowmoo/dashman

12.1.2

0.12.1.2

UdjinM6

legendary

Activity: 1318

Merit: 1040

Quote from: JGCMiner on February 25, 2017, 11:09:11 AM

It is strongly recommended that everybody update to the latest version 12.0.2 as well as the latest sentinel. Moocowmoo's Dashman makes this very quick and easy. The sooner most of the network is on 12.0.2 the earlier enforcement can be reenabled. It will be nice to get InstantSend back and not have to worry about the off-chance of a greedy miner not paying one of my nodes. Wink

https://github.com/moocowmoo/dashman

12.1.2

BagHolder010

sr. member

Activity: 283

Merit: 250

Best IoT Platform Based on Blockchain

Quote from: JGCMiner on February 25, 2017, 11:39:01 AM

Quote from: BagHolder010 on February 25, 2017, 11:30:27 AM

Hello, can anyone here tell me when did RC3 come? I know it's somewhere in 2014. "Trying to Submit my claim to Cryptsy settlement"

You will have to dig around in this thread, but RC4 was around August 2014 so RC3 was probably sometime between May - July. Probably not before May since I am pretty sure RC3 was after the introduction of MNs (which was in early May).

Ok thank you

JGCMiner

hero member

Activity: 611

Merit: 500

Quote from: BagHolder010 on February 25, 2017, 11:30:27 AM

Hello, can anyone here tell me when did RC3 come? I know it's somewhere in 2014. "Trying to Submit my claim to Cryptsy settlement"

You will have to dig around in this thread, but RC4 was around August 2014 so RC3 was probably sometime between May - July. Probably not before May since I am pretty sure RC3 was after the introduction of MNs (which was in early May).

BagHolder010

sr. member

Activity: 283

Merit: 250

Best IoT Platform Based on Blockchain

Hello, can anyone here tell me when did RC3 come? I know it's somewhere in 2014. "Trying to Submit my claim to Cryptsy settlement"

qwizzie

legendary

Activity: 2548

Merit: 1245

Quote from: g4q34g4qg47ww on February 25, 2017, 11:06:51 AM

Anyone know what happened to user 'g4q34g4qg47ww'? He was the last speck of honesty, an honest genuine guy. He was the last user out of the old-school drk cult.

I have no idea, he somehow changed into .. this.

Taylor05

sr. member

Activity: 265

Merit: 250

Proposal: Infrastructure - Datacenter (March)

https://www.dash.org/forum/threads/proposal-infrastructure-datacenter-march.13285/

This proposal funds the ongoing infrastructure costs of the project.

TanteStefana2

legendary

Activity: 1260

Merit: 1001

Quote from: JGCMiner on February 25, 2017, 11:09:11 AM

It is strongly recommended that everybody update to the latest version 12.0.2 as well as the latest sentinel. Moocowmoo's Dashman makes this very quick and easy. The sooner most of the network is on 12.0.2 the earlier enforcement can be reenabled. It will be nice to get InstantSend back and not have to worry about the off-chance of a greedy miner not paying one of my nodes. Wink

https://github.com/moocowmoo/dashman

For those of you that are hands on, like me, all I had to do was update dashd and dash-cli by the usual method you use, and as for sentinel, it's very simple. cd into your sentinel folder, wherever it is, and issue the command: git pull

It should download and merge everything you need into your sentinel. You are finished. Just restart dashd, no reindex required.

JGCMiner

hero member

Activity: 611

Merit: 500

It is strongly recommended that everybody update to the latest version v0.12.1.2 as well as the latest sentinel. Moocowmoo's Dashman makes this very quick and easy. The sooner most of the network is on v0.12.1.2 the earlier enforcement can be reenabled. It will be nice to get InstantSend back and not have to worry about the off-chance of a greedy miner not paying one of my nodes. Wink

https://github.com/moocowmoo/dashman

EDIT: Fixed the version numbering gaffe Tongue

g4q34g4qg47ww

sr. member

Activity: 478

Merit: 250

Anyone know what happened to user 'fernando'? He was the last speck of honesty left in this project and imho was an honest genuine guy. I reached out to him when i started smelling what was going around, he was upset but was going to stick around to fight the good fight. All my messages with him are now gone and it appears his username is also nowhere to be found? Is GhostPlayer still on board? He was the last user out of the old-school drk cult that I tried to save, just wondering if he ever got de-programmed.

110110101

legendary

Activity: 1382

Merit: 1002

Quote from: Quartz-Team on February 25, 2017, 08:57:32 AM

I get this now with my MN:

Warning: Your masternode version (120100) is behind the official version (120102). This is from DASHcentral.

I am running 12.1 so do I need to upgrade again. I just updated last week...??

and go through the update procedure and reset my time and loose rewards etc.

I get them a lot too, but eventually Dashcentral gets things right and reports my node properly. Just leave it alone, seems to be the best advice I have received and tested.

BrainShutdown

legendary

Activity: 1052

Merit: 1004

Quote from: maxpowerzz92 on February 25, 2017, 09:27:03 AM

Quote from: BrainShutdown on February 25, 2017, 09:23:22 AM

Quote from: maxpowerzz92 on February 25, 2017, 09:21:04 AM

Quote from: Quartz-Team on February 25, 2017, 09:10:43 AM

No, I run my own on a VPS, I just use Dashcentral to monitor the MN. So, is it just a matter of replacing the dashd on the server? what about sentinel?

Dashman upgrades Sentinel also. It took about 5 minutes to upgrade my masternodes to the latest version.

5 minutes?!? You must have a lot of masternodes. Good for you Grin

Haha yes! I have a few. Grin

The longest part is waiting for the blockchain to resync after it restarts dashd. I always run "dashman status" to verify that everything is green before moving on to the next MN.

Yep the reindex is a bit painfull but one every 18 months it's not that bad Wink

qwizzie

legendary

Activity: 2548

Merit: 1245

Quote from: Quartz-Team on February 25, 2017, 09:10:43 AM

Quote from: Lukas_Jackson on February 25, 2017, 09:09:20 AM

Quote from: Quartz-Team on February 25, 2017, 08:57:32 AM

I get this now with my MN:

Warning: Your masternode version (120100) is behind the official version (120102). This is from DASHcentral.

I am running 12.1 so do I need to upgrade again. I just updated last week...??

and go through the update procedure and reset my time and loose rewards etc.

I don't run any on dashcentral. Do you run your remote node (vps) there? It should be taken care of by them. You don't have to start-alias your mn from local. It's simple update and you won't lose your rewards.

No, I run my own on a VPS, I just use Dashcentral to monitor the MN. So, is it just a matter of replacing the dashd on the server? what about sentinel?

Sentinel needs to be updated as well, for those not using Dashman you can use following command : cd .dashcore/sentinel && git pull
cronjob for Sentinel needs to be set to 1 minute, you can use the following cron :

* * * * * cd /home/YOURUSERNAME/.dashcore/sentinel && ./venv/bin/python bin/sentinel.py >/dev/null 2>&1

Warning : there is currently some discussion going on if sentinel is placed inside the .dashcore folder (atlassian guide) or directly in your home folder (github guide).
This could effect both your cronjob and the sentinel update itself. To be continued ...

Quartz-Team

newbie

Activity: 24

Merit: 0

Ok, cool, I will try Dashman

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 814. (Read 9723733 times)