|
moocowmoo
|
|
August 21, 2015, 05:29:37 AM Last edit: August 21, 2015, 05:40:08 AM by moocowmoo |
|
There are safer ways to accomplish the same things here: cd ~/.dash wget https://github.com/MangledBlue/DASH/blob/master/dashR chmod +x dashR sudo cp dashd /usr/bin sudo cp dash-cli /usr/bin sudo cp dashR /usr/bin sudo chmod 775 /usr/bin/dashd sudo chmod 775 /usr/bin/dash-cli sudo chmod 775 /usr/bin/dashR cd dashR
can all be replaced by simply doing: # step into the .dash folder cd ~/.dash
# get a copy of the desired executable wget https://github.com/MangledBlue/DASH/blob/master/dashR
# set its permissions to be executable chmod +x dashR
# add ~/.dash to the front of the list of places to look for executables export PATH=~/.dash:$PATH
to add ~/.dash to PATH on every login, just add to ~/.bashrc export PATH=~/.dash:$PATH
Now you can run dashd or dash-cli or dashR or whatever from wherever. --- But, I don't recommend plucking files out of git repos. It removes all the goodness of versioning. Better to have people git clone your repo and just symlink into it. It also make things easier on them when you push a bugfix. They only need to do 'git pull' and they're done. --- Also, your dashR calling dashR calling dashR is a memory leak. You need to exec.
|
|
|
|
Sub-Ether
Sr. Member
Offline
Activity: 434
Merit: 250
Quantum entangled and jump drive assisted messages
|
|
August 21, 2015, 06:11:10 AM |
|
Thanks Sub-Ether. Maybe there should be a check of used keys(n) during shutdown. It adds the keypool=n+1000 in the config file to generate more keys. If backups are done on startup and each mix uses 200 keys, this should always keep a valid backup(even up to 4 or 5 mix sessions). EDIT: I added keypool=2000 in my config and it didn't changed my wallet size. I had to run keypoolrefill to get the wallet to change size. Suggestion: Set keypool as needed to keep 1000 free addresses. On shutdown run keypoolrefill and backup wallet. Thats a good idea, have a counter for the number of keys used, and when the limit is near there could be a warning to backup your wallet - useful if doing a lot of mixing.
|
Dash is 27.3 times faster with syncing and updating than Bitcoin and 93.7 times faster than Monero. Bitcoin (v0.11.0) has a Tao ratio 11.2% faster than bitcoin (v0.10.0) release. Dash (v.0.12.0.49) = Tao sync ratio = 0.15 seconds / hour of update || Dash (v.0.11.2.23) = Tao sync ratio = 0.24 seconds / hour of update. V12 versus V11 speedup = +36.5% Bitcoin (v.0.11.0) = Tao sync ratio = 4.14 seconds / hour of update || Monero (v.0.41.1) = Tao sync ratio = 14.2 seconds / hour of update
|
|
|
illodin
|
|
August 21, 2015, 06:30:24 AM |
|
Lightning nodes are probably MSBs as they are holding and transmitting other peoples' money. Whether that matters is another story, as the nodes will likely be managed by few large entities collecting the fees being their business model and can afford the license. Being an MSB brings other interesting things to the table, for example KYC/ALM requirements and such. Which means the users of the lightning network will not likely be individual citizens (unless they want to succumb to totalitarianism), but official organizations and corporations.
|
|
|
|
Sub-Ether
Sr. Member
Offline
Activity: 434
Merit: 250
Quantum entangled and jump drive assisted messages
|
|
August 21, 2015, 06:34:17 AM |
|
Lightning nodes are probably MSBs as they are holding and transmitting peoples' money. Whether that matters is another story, as the nodes will likely be managed by few large entities collecting the fees being their business model and can afford the license. Sounds pie in the sky to me, in 12 months it may not even matter so where will the incentive be?
|
Dash is 27.3 times faster with syncing and updating than Bitcoin and 93.7 times faster than Monero. Bitcoin (v0.11.0) has a Tao ratio 11.2% faster than bitcoin (v0.10.0) release. Dash (v.0.12.0.49) = Tao sync ratio = 0.15 seconds / hour of update || Dash (v.0.11.2.23) = Tao sync ratio = 0.24 seconds / hour of update. V12 versus V11 speedup = +36.5% Bitcoin (v.0.11.0) = Tao sync ratio = 4.14 seconds / hour of update || Monero (v.0.41.1) = Tao sync ratio = 14.2 seconds / hour of update
|
|
|
|
Sub-Ether
Sr. Member
Offline
Activity: 434
Merit: 250
Quantum entangled and jump drive assisted messages
|
|
August 21, 2015, 08:12:36 AM |
|
I see the masternodes like shock absorbers on a car:- when there are bumpy price movements downwards this produces a counter acting force and increased dampening factor of more buy ins for extra masternodes. when the price goes bumpity up, people empty their spare change from the masternodes, producing a counter acting (and higher dampened) force downwards on the price. Hence both reactions are equal and opposite forces against the market price trend thus evening out the larger spikes to smoother price swings.
|
Dash is 27.3 times faster with syncing and updating than Bitcoin and 93.7 times faster than Monero. Bitcoin (v0.11.0) has a Tao ratio 11.2% faster than bitcoin (v0.10.0) release. Dash (v.0.12.0.49) = Tao sync ratio = 0.15 seconds / hour of update || Dash (v.0.11.2.23) = Tao sync ratio = 0.24 seconds / hour of update. V12 versus V11 speedup = +36.5% Bitcoin (v.0.11.0) = Tao sync ratio = 4.14 seconds / hour of update || Monero (v.0.41.1) = Tao sync ratio = 14.2 seconds / hour of update
|
|
|
pille
|
|
August 21, 2015, 08:39:31 AM |
|
Thanks Sub-Ether. Maybe there should be a check of used keys(n) during shutdown. It adds the keypool=n+1000 in the config file to generate more keys. If backups are done on startup and each mix uses 200 keys, this should always keep a valid backup(even up to 4 or 5 mix sessions). EDIT: I added keypool=2000 in my config and it didn't changed my wallet size. I had to run keypoolrefill to get the wallet to change size. Suggestion: Set keypool as needed to keep 1000 free addresses. On shutdown run keypoolrefill and backup wallet. Thats a good idea, have a counter for the number of keys used, and when the limit is near there could be a warning to backup your wallet - useful if doing a lot of mixing. We had a discussion about the keypool problem here: https://dashtalk.org/threads/darksend-to-seed-or-not-to-seed.4925/#post-54501
|
|
|
|
Rux
Legendary
Offline
Activity: 1291
Merit: 1024
https://crypto.ba
|
|
August 21, 2015, 08:45:51 AM |
|
Guys im doing setup for a costumer, he has 1000 DASH i do the rest of job!
But when he try to start MN from his local wallet he said he get
"not capable masternode: Could not connect to xx.xxx.xxx.xxx:9999"
what could be the problem?
I updated 2 MN and 1 fresh install yesterday to .47 with no problems so im kinda confused :/
|
RXC Crypto.ba Decentralized solutions!
|
|
|
GhostPlayer
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
August 21, 2015, 08:50:32 AM |
|
Guys im doing setup for a costumer, he has 1000 DASH i do the rest of job!
But when he try to start MN from his local wallet he said he get
"not capable masternode: Could not connect to xx.xxx.xxx.xxx:9999"
what could be the problem?
I updated 2 MN and 1 fresh install yesterday to .47 with no problems so im kinda confused :/
Could be a couple of things. Wrong IP, or VPS doesn't have the port open. Also, double check you have listen=1
|
|
|
|
Rux
Legendary
Offline
Activity: 1291
Merit: 1024
https://crypto.ba
|
|
August 21, 2015, 09:18:57 AM Last edit: August 21, 2015, 09:40:55 AM by Rux |
|
Guys im doing setup for a costumer, he has 1000 DASH i do the rest of job!
But when he try to start MN from his local wallet he said he get
"not capable masternode: Could not connect to xx.xxx.xxx.xxx:9999"
what could be the problem?
I updated 2 MN and 1 fresh install yesterday to .47 with no problems so im kinda confused :/
Could be a couple of things. Wrong IP, or VPS doesn't have the port open. Also, double check you have listen=1 it was Listen=0 i dont know how that got there, but problem should be gone... waiting for client to come online so that he can fire up MN from his local wallet! p.s. I have 700 DASH ready for another masternode, i need 300 DASH more, so if anyone is insterested let me know! Long live DASH
|
RXC Crypto.ba Decentralized solutions!
|
|
|
Riseman
|
|
August 21, 2015, 09:32:41 AM |
|
Interesting. Previously it was the other way around. Dash price nearly mirrored BTC price.
|
|
|
|
r4vani
|
|
August 21, 2015, 10:43:02 AM |
|
Who can explain what happens if Technology to be built for mining and all Dash blocks are resolved in six months.
|
BITOKER.COM | [ | Enjoy the ultimate online play bitcoin poker Anonymous / US Player Friendly / Instant Play | [ | | ] |
|
|
|
Rux
Legendary
Offline
Activity: 1291
Merit: 1024
https://crypto.ba
|
|
August 21, 2015, 10:44:47 AM |
|
all blocks resolved ? :/ you can never resolve all blocks because there were be new transactions always and there is difficulty to bear in mind... so what are you say is probably impossible, someone correct me if im wrong
|
RXC Crypto.ba Decentralized solutions!
|
|
|
r4vani
|
|
August 21, 2015, 10:50:28 AM |
|
all blocks resolved ? :/ you can never resolve all blocks because there were be new transactions always and there is difficulty to bear in mind... so what are you say is probably impossible, someone correct me if im wrong yes ,Situation existed that all 22 million coins mined in 6 month by community.
|
BITOKER.COM | [ | Enjoy the ultimate online play bitcoin poker Anonymous / US Player Friendly / Instant Play | [ | | ] |
|
|
|
rentahash
|
|
August 21, 2015, 11:02:51 AM |
|
all blocks resolved ? :/ you can never resolve all blocks because there were be new transactions always and there is difficulty to bear in mind... so what are you say is probably impossible, someone correct me if im wrong yes ,Situation existed that all 22 million coins mined in 6 month by community. From my understanding it is theoretically possible, BUT at this very moment I dont see super mega advanced revolutionary computing power any near from now. If that scenario happen it will effect all cryptocurrency, BUT like Rux mentioned difficulty will help things out to once massive computing power is in production, we will have time to adjust algorithm of X11 in order to mitigate all blocks being mined fast... I really dont see it happening anytime soon... and yes there should be solution if that scenario comes in range of risk management.
|
|
|
|
toknormal
Legendary
Offline
Activity: 3066
Merit: 1188
|
|
August 21, 2015, 11:14:26 AM |
|
London stocks: AKA "keeping a lead balloon in the air with loose monetary policy". Now erased all gains for the year.
|
|
|
|
Rux
Legendary
Offline
Activity: 1291
Merit: 1024
https://crypto.ba
|
|
August 21, 2015, 11:19:52 AM |
|
all blocks resolved ? :/ you can never resolve all blocks because there were be new transactions always and there is difficulty to bear in mind... so what are you say is probably impossible, someone correct me if im wrong yes ,Situation existed that all 22 million coins mined in 6 month by community. From my understanding it is theoretically possible, BUT at this very moment I dont see super mega advanced revolutionary computing power any near from now. If that scenario happen it will effect all cryptocurrency, BUT like Rux mentioned difficulty will help things out to once massive computing power is in production, we will have time to adjust algorithm of X11 in order to mitigate all blocks being mined fast... I really dont see it happening anytime soon... and yes there should be solution if that scenario comes in range of risk management. but guys, you do realize that even after 22 milion coins were mined, blocks are still ongoing, new transactions need to be confirmed, and train is moving on without mining .... miners wont be miners more, even now its not miners, more like confirmators who get paid in mined coins im hope im not wrong
|
RXC Crypto.ba Decentralized solutions!
|
|
|
|
Minotaur26
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
August 21, 2015, 11:42:33 AM |
|
One exists, one doesn't. Lightning is centralized by design. It's something like a centralized ledger that is capable of pushing out finalized transaction states to the real ledger at anytime. Drawbacks: - It screws with the UTXO set, because you can't tell where the money actually is in the system - It's 100% centralized and could be prone to regulation. I've seen them talk about this and they say if the centralized node starts to whitelist addresses or something to that effect, they'll just start another one. - It's incredibly complicated and will be prone to errors for the first year or two - It's not really that useful if you're paying different people with every transaction you do. It's more useful for subscriptions or companies that are paying each other all of the time. - There's probably more, but I lost interest The masternode network is decentralized by design and can pretty much do anything a centralized system can do but in a completely decentralized and stable way, including fixing all of these issues with scalability they're having in a much more elegant way. This is very informative thanks.
|
|
|
|
|