Search results

Nah, it's unlikely to get flamed to any degree, maybe some harsh criticism at worst but even that is likely to be constructive. We likes these kind of discussions around these parts :) Here's an interesting one along quite different lines from a while back, the PDF is a bit hard to understand...

Fancy getting one started? I've been thinking along the same lines and have been waiting for 12.1 to see how a DAO for something like that could be established. It's kind of inevitable Bitcoin mining will end up primarily as a renewable energy provider with mining as a secondary business soaking...

Welcome fellow hillbilly :) I'm interested in hearing it too, it's one I've turned over many times as well and always interested in hearing different takes on it.

I'm not familiar with Dash-Qt.conf but as far as I know it's only for the gui, ie. it's a Qt configuration file and not a dash client configuration file. The one you need should be ~/.dash/dash.conf

On a newly started masternode? That message comes up on the first run and should change as soon as Sentinel runs (to pre-enabled iirc), not really a bug but apparently it'll be changed to something less confusing before release.

Ouch, sad to hear. The client now does automated backups (in the .dash/backups folder) so there's some protection from that happening but was that in the client back in 2014? Saddly it's likely those coins are gone @starkast unless you have a more recent backup :/

Sry, edited my post after I sent it, the -70.001 transaction looks like (edit) a regular transaction sent to yourself but hasn't registered as coming back to you for some reason, could you check the details of that one? A block explorer will show what happened to it after that transaction...

I'm guessing your wallet is safely backed up, it would be worth trying some of the repair options in the tools menu, Tools>Wallet Repair. The 2 "Recover transactions" options or the "Rescan blockchain files" will probably fix it. EDIT: That bottom transaction doesn't look right, the -70.001...

I'd kind of agree but you end up with an insiders and outsiders situation and that causes it's own tensions, we already see a bit of that kind of situation with both the core development Slack and the high barrier to entry in the governance process (masternode ownership) and imho furthering it...

Any contributions would be very welcome :) I wouldn't really read the Evo paper as a rigid outline and schedule, large open source projects don't really work that way and imho Evolution is more like it's name suggests, a constant process of improvement rather than a specific set of features...

Maybe, maybe not but the wider online community has been in a real shitstorm for the last few days and attempts to break apart the community are more or less inevitable at some stage. Make no mistake, Dash is one of the most dangerous projects in the world today. Cryptocurrencies are a real...

This post of Evans back on the first page: "Committees" sets alarm bells ringing for me but otherwise a big thumbs up, being able to delegate decision making is an essential step imho.

That's actually quite a thought provoking question. I'm practically certain it will because it was decided some time ago to keep the first tier in sync with Bitcoins codebase to both benefit from Bitcoins development and allow Bitcoin based projects to be easily ported to Dash. Simple enough so...

Jeysus, you made me look through the code again and it weirds me out for a while, nothing wrong with it but it's a bit like it's been written in feet and inches and I'm thinking in metric, needs a mental gearchange. The relevant line is here if you're interested...

No prob and it's not at all pedantic, coming up with potential attacks is very important.

Have you had a look at the code? The annotation is probably the best place to look to understand what's going on at that kind of level: https://github.com/dashpay/dash/blob/master/src/instantx.h https://github.com/dashpay/dash/blob/master/src/instantx.cpp If you're not familiar with c++ but...

...+4. Inputs must have at least 6 confirmations so the proof of work hash (providing the entropy) will be from the block -2 or lower from the current height. It's more than a year since I went over any of this and I'd forgotten how complicated it was, you could only really attack if you know...

There's more on the wiki: https://dashpay.atlassian.net/wiki/display/DOC/Quorum+Selection

Got to say, I was very impressed when a "Bitcoin" news alert I have running linked a Dash Times article. It was a really good one too, lots of original thinking on crypto with just a hint of Dash and it's come up with quite a few more since, very impressive but some have been very specifically...

6+ hours a day? A breath of fresh air would be no harm, you'll be back ;) Swarmwise... definitely a good call proposing that, it even allows opposing views with the same common goal to pull together in the same direction. Catch you later, have a good one.