|ANN| DAS - Decentralized and Secure. Private Send. Masternodes.

[bitcoinbulk]

DAS price is definitely tumbling but it can easily bounce back. As someone else has mentioned, can't the community take over development? Probably better than having 1 developer anyways.

[redditarco]

DAS price is definitely tumbling but it can easily bounce back. As someone else has mentioned, can't the community take over development? Probably better than having 1 developer anyways.

there u go now u are talking and thinking ahead, protocol for these types of issues have backup devs just in case.
let me know if someone wants to join me in getting a new dev for das, lets make this coin awesome! it already has a lot in place.

[todualex]

can i setup a masternode on my windows laptop?


p.s.  specs are okey, i dont use this laptop anymore, i have static ip.

[redditarco]

can i setup a masternode on my windows laptop?


p.s.  specs are okey, i dont use this laptop anymore, i have static ip.

do a search on youtube for steps.
pathfinder das masternode setup on windows

[jota17]

How could a new dev run DAS?

[redditarco]

How could a new dev run DAS?

old dev not responding, trying to move forward.

[lemanruss]

Hi Guys

has anyone run more the 1 DAS node on the Windows wallet. I tried setting it up but the 2nd Masternode keeps getting missing.

[szfinx]

Hi Guys

has anyone run more the 1 DAS node on the Windows wallet. I tried setting it up but the 2nd Masternode keeps getting missing.

Yes, I am running more than 2 masternodes controlled by 1 windows wallet.

What is your setup?
Is the masternode gone missing on the VPS as well, or only in the Windows wallet?
Do you run both masternodes on the same VPS?
Do they have separate static IPs?

[uf2458058zenq]

I have the same  but my balance is showing fine.

[szfinx]

The status of the masternodes are gone missing all the time in the Windows wallet. This is a known issue, but as we don't have a developer, no way of fixing it.
Luckily it is only the status info from the Windows wallet, the actual status of the masternodes on the VPS's are solid and haven't gone missing for several weeks now.

[coind0g]

How could a new dev run DAS?

old dev not responding, trying to move forward.

I'm a developer and I have invested in several DAS masternodes. I am stepping up to help continue development because I think it would be a shame to see this coin go to waste.

Here is a PR (code submission) I just opened for some fixes to get DAS to compile with newer versions of OpenSSL:

https://github.com/Truckman83/DAS-source/pull/6


It is unlikely we will see this merged as it appears Truckman has gone AWOL.

If we need to, we can make my account the primary account and simply continue development on there.

I think my next step will be seeing how we can disable INSTANTSEND until DASH fixes the potential exploit with it. See this link for more information:

https://www.dash.org/forum/threads/temporary-disabling-of-instandsend-due-to-potential-quorum-exploit-method.16492/

[szfinx]

How could a new dev run DAS?

old dev not responding, trying to move forward.

I'm a developer and I have invested in several DAS masternodes. I am stepping up to help continue development because I think it would be a shame to see this coin go to waste.

Here is a PR (code submission) I just opened for some fixes to get DAS to compile with newer versions of OpenSSL:

https://github.com/Truckman83/DAS-source/pull/6


It is unlikely we will see this merged as it appears Truckman has gone AWOL.

If we need to, we can make my account the primary account and simply continue development on there.

I think my next step will be seeing how we can disable INSTANTSEND until DASH fixes the potential exploit with it. See this link for more information:

https://www.dash.org/forum/threads/temporary-disabling-of-instandsend-due-to-potential-quorum-exploit-method.16492/

Hi Coind0g and welcome aboard.

I am happy to have someone who has the knowledge and willingness to make the DAS bigger.
I am too invested in masternodes... How can the community help your effort?

[coind0g]

Hi Coind0g and welcome aboard.

I am happy to have someone who has the knowledge and willingness to make the DAS bigger.
I am too invested in masternodes... How can the community help your effort?

Thanks, glad to be here.

First and foremost, we need more devs. I can do a lot to assist with porting in patches and eventually developing new features, but all the more help, the better. I see a few other people trying to submit pull requests on github. I could try reaching out to them.

Once we establish which repository will be the new official DAS repository (my fork could easily serve as this), we may want to make a new ANN thread titled something like "|ANN| DAS Revival". This is similar from what I've seen happen with Crave. See links below for example:

(old, original Crave thread):
https://bitcointalk.org/index.php?topic=997356.0

(new, revival Crave thread):
https://bitcointalk.org/index.php?topic=1964765.0

If/when the movement to a new repository happens and a revival thread is created, we will need your support and anyone else who cares about DAS to promote the new forum revival thread and repository.

As part of the revival thread, we will probably want to establish a better looking website that we can update as a community. Github pages can host it for free. We should also establish some goals and eventually build some kind of road map for where we'd like to take DAS.

[redditarco]

Hi Coind0g and welcome aboard.

I am happy to have someone who has the knowledge and willingness to make the DAS bigger.
I am too invested in masternodes... How can the community help your effort?

Thanks, glad to be here.

First and foremost, we need more devs. I can do a lot to assist with porting in patches and eventually developing new features, but all the more help, the better. I see a few other people trying to submit pull requests on github. I could try reaching out to them.

Once we establish which repository will be the new official DAS repository (my fork could easily serve as this), we may want to make a new ANN thread titled something like "|ANN| DAS Revival". This is similar from what I've seen happen with Crave. See links below for example:

(old, original Crave thread):
https://bitcointalk.org/index.php?topic=997356.0

(new, revival Crave thread):
https://bitcointalk.org/index.php?topic=1964765.0

If/when the movement to a new repository happens and a revival thread is created, we will need your support and anyone else who cares about DAS to promote the new forum revival thread and repository.

As part of the revival thread, we will probably want to establish a better looking website that we can update as a community. Github pages can host it for free. We should also establish some goals and eventually build some kind of road map for where we'd like to take DAS.

Hi Coind0g welcome aboard!
I can promote on youtube etc to get word out, so we are doing a fork of das cool stuff! :-)
let me know how I can help out in any other way, glad to see progress on this masternode coin :-)

[jhannlenris]

DAS Masternodes must use port 9399, other ports for the masternode are not allowed.

That wold go against the currently issue with another local port, with the multiple masternodes as they require another port...
As they have to be the same i think 9399 local 9399 vps, 9400 local 9400 vps, etc..

Try this to run multiple masternodes on the same linux vps.

Review under /home/yourusername/.das the das.conf file

I have the following config in it:

server=1
daemon=1
listen=1
rpcuser=dasuser01 >>> your RPC user
rpcpassword=asdfuh2q3r98zasFHBas90dfh213AHdfkajg234 >>>your RPC password
rpcport=9398 >>> some RPC port
rpcallowip=127.0.0.1
masternode=1
masternodeprivkey=<<< your Masternode genkey >>>
masternodeaddr=13.284.238.21 >>> your linux VPS WAN/external IP address
externalip=13.284.238.21 >>> your linux VPS WAN/external IP address
bind=10.0.1.4:9399  >>> your internal linux vps IP address with the DAS port - which is bound to the 1st WAN IP

Then start your masternode with: dasd --datadir=/home/yourusername/.das

For your second masternode on the same machine:
- Requirement: You need a second WAN IP / external IP address for your 2nd Masternode.

- Make a second das folder: mkdir /home/yourusername/.das1
- create a empty das.conf with nano das.conf in it.

Config for the second masternode:

server=1
daemon=1
listen=1
rpcuser=dasuser02 >>> your 2nd RPC user
rpcpassword=aSf92hAGHBf29o83hzgaökdfabdf >>>your 2nd RPC password
rpcport=9397 >>> your 2nd RPC port
rpcallowip=127.0.0.1
masternode=1
masternodeprivkey=<<< your 2nd Masternode genkey >>>
masternodeaddr=93.293.23.235>>> your 2nd linux VPS WAN/external IP address
externalip=93.293.23.235 >>> your 2nd linux VPS WAN/external IP address
bind=10.0.1.5:9399  >>> your 2nd internal linux vps IP address with the DAS port - which is bound to the 2nd WAN IP

Then start your 2nd masternode with: dasd --datadir=/home/yourusername/.das1
Report to moderator 

[bitcoinbulk]

Hi Coind0g and welcome aboard.

I am happy to have someone who has the knowledge and willingness to make the DAS bigger.
I am too invested in masternodes... How can the community help your effort?

Thanks, glad to be here.

First and foremost, we need more devs. I can do a lot to assist with porting in patches and eventually developing new features, but all the more help, the better. I see a few other people trying to submit pull requests on github. I could try reaching out to them.

Once we establish which repository will be the new official DAS repository (my fork could easily serve as this), we may want to make a new ANN thread titled something like "|ANN| DAS Revival". This is similar from what I've seen happen with Crave. See links below for example:

(old, original Crave thread):
https://bitcointalk.org/index.php?topic=997356.0

(new, revival Crave thread):
https://bitcointalk.org/index.php?topic=1964765.0

If/when the movement to a new repository happens and a revival thread is created, we will need your support and anyone else who cares about DAS to promote the new forum revival thread and repository.

As part of the revival thread, we will probably want to establish a better looking website that we can update as a community. Github pages can host it for free. We should also establish some goals and eventually build some kind of road map for where we'd like to take DAS.

Agreed that we need & want more than 1 developer. On top of that should we try to establish some other roles? Marketing and promotion people?

Also, if we can get the ball rolling in the right direction it might not be a bad idea to set up a donation address for the developers working on the project. Thoughts?



On a totally separate note:

I'm running 2 MN on a windows VPS but the wallets both keep locking. Any idea what's going on?

[bakra]

Hi Coind0g,

Welcome. Will you also join the Telegram chat?

[chaosfourever]

How do we get coins back from our masternodes? When you try to send the coins somewhere it is 1000 short since those were sent to your masternode, so how do you get those back to send them somewhere else if needed?

If you have a controlling windows wallet, they you can click on 'send' then input. Select the grayed out 1000 balance and right click and unlock it.
If you have a hot masternode, change the masternode=1 to 0 in the das.conf file.

Sweet thanks for this. I am not messing with my node at all right now. Just in case in the distant future if I want to pull out my coins.

[todualex]

is it too late for mining on nvidia gpu? i could not find working pool

[coind0g]

DAS Masternodes must use port 9399, other ports for the masternode are not allowed.

That wold go against the currently issue with another local port, with the multiple masternodes as they require another port...
As they have to be the same i think 9399 local 9399 vps, 9400 local 9400 vps, etc..

Try this to run multiple masternodes on the same linux vps.

Review under /home/yourusername/.das the das.conf file

I have the following config in it:

server=1
daemon=1
listen=1
rpcuser=dasuser01 >>> your RPC user
rpcpassword=asdfuh2q3r98zasFHBas90dfh213AHdfkajg234 >>>your RPC password
rpcport=9398 >>> some RPC port
rpcallowip=127.0.0.1
masternode=1
masternodeprivkey=<<< your Masternode genkey >>>
masternodeaddr=13.284.238.21 >>> your linux VPS WAN/external IP address
externalip=13.284.238.21 >>> your linux VPS WAN/external IP address
bind=10.0.1.4:9399  >>> your internal linux vps IP address with the DAS port - which is bound to the 1st WAN IP

Then start your masternode with: dasd --datadir=/home/yourusername/.das

For your second masternode on the same machine:
- Requirement: You need a second WAN IP / external IP address for your 2nd Masternode.

- Make a second das folder: mkdir /home/yourusername/.das1
- create a empty das.conf with nano das.conf in it.

Config for the second masternode:

server=1
daemon=1
listen=1
rpcuser=dasuser02 >>> your 2nd RPC user
rpcpassword=aSf92hAGHBf29o83hzgaökdfabdf >>>your 2nd RPC password
rpcport=9397 >>> your 2nd RPC port
rpcallowip=127.0.0.1
masternode=1
masternodeprivkey=<<< your 2nd Masternode genkey >>>
masternodeaddr=93.293.23.235>>> your 2nd linux VPS WAN/external IP address
externalip=93.293.23.235 >>> your 2nd linux VPS WAN/external IP address
bind=10.0.1.5:9399  >>> your 2nd internal linux vps IP address with the DAS port - which is bound to the 2nd WAN IP

Then start your 2nd masternode with: dasd --datadir=/home/yourusername/.das1
Report to moderator 

You actually do not need to have a 2nd IP. You can host multiple masternodes on a single IP. I can post a guide about doing this.