Search results

Can you retrieve the wallet.dat file from the old wallet or a backup? That file contains your private keys, it's stored in C:\Users\<YOUR-WINDOWS-USERNAME>\AppData\Roaming\Dash

I think it's fine if the contractor, e.g. core team, is willing to obey the signal like your dev team is UdjinM6 :) I'm thinking more generally in the commercial world contracts aren't enforcable without joint agreement around a consideration, i.e. if a client commissions a developer to build...

OK registered charities - I take your point. Unsung is pretty well known in Dash circles though via TheCryptoShow and the Network is sponsoring them: https://www.dash.org/forum/threads/sponsorship-for-the-crypto-show-and-unsung-hacking-hunger.10565/

Here's one :) http://www.unsung.org/donate

Hey Splawik :) It would be possible to do that with Sentinel, yes. But in the Evo revision it can be done more elegantly, so our strategy is to press on with the Evo alpha (within which Sentinel is upgrading to DashDrive essentially) and release everything together. Andy

Hi there. Can you provide as much info as possible - for example what machines are the old / new wallets on. What is the exact steps you are following and what are you seeing on the screen (e.g. double click dash wallet, what you are seeing in the wallet etc) thanks Andy

Hi Acedian I won't comment on the actual fee I think we should have right now. But just to point out, these proposals that just ask a question aren't always going to get results because proposals only work when they pay someone to do something (this is the fundamental incentive modal of the...

It's still a bit centralized though :) decentralized version would be the Network could appoint designated charities dynamically or something similar. Which should be possible in Evolution. Mixing in proposals with charity donations though might be 2 things to keep separate because part of it...

Interesting idea. I think the issue would be that this requires designation of the recipient charities (by payment address) using a centralized authority at the protocol level. Unless some dynamic solution could be devised.

Incident report and how to harden your Masternode: https://www.dash.org/2017/03/08/DDoSReport.html

Hey - please make sure to set the recommended IP tables too, that might be the cause and not the HW if you're on the recommended spec already: https://gist.github.com/chaeplin/5dabcef736f599f3bc64bdce7b62b817

The attack was against all MNs as far as we know, from 2,000 individual IPs mostly in Asia, i.e. a botnet

I would guess yes

Yes DDOS protection, the IP tables/hardening that @UdjinM6 posted above and making sure your node is high enough spec / on decent infrastructure is the best protection. This kind of attack can be done on any Crypto p2p network and it's clearly not very effective against Dash considering only...

Source: @chaeplin :) You can see the MNs that dropped off center of the top row, at the attacks peak (t+5 hrs) the # of nodes offline was 114 or ~2.8% of the network, probably the nodes with the least performance / provision / cost. Now in hour 6 and the nodes are recovering, 2.1% are still down.

When you first run the QT wallet it creates a file on your system called wallet.dat. Inside there is a bunch of private keys that generate your addresses in the wallet and control of those lets you spend. So the wallet.dat file is basically your 'wallet', you can go to another computer and...

well, someone with a 1 week account isn't going to have access to dash.org/contact - chat agents has at least you with 1 week old account planning to be at least an agent on there, so that's the first difference. Second, talking a non-technical noob who doesn't know first thing about crypto...

If the account holder was someone known and the admins/agents were as tightly controlled as the dash.org/contact recipients then I wouldn't be worried about it as an attack vector. That would need to be managed going forward though and I bet most known people don't have the time required to...

Ok let me rephrase it: you say - you made the proposal because devs didn't want to do it but Evans text suggest the devs do want to do it which makes no sense. initially you wanted to have control of the account that gives you access to all Dash.org users, their IPs, browser, OS, and also...