Gosh, you're fast. You replied before I could edit the tone to be less pejorative, apologies for that.

Cheers

Graham

Very cerebral, lot of planning and careful thought.

Less thought here.

A one-off effort from someone not necessarily even a coin-holder is valued at an extremely generous 1 BTC whereas sustained commitment and engagement from a community manager over a(n unspecified) period of time is valued at a niggardly 0.25 BTC.


Cheers

Graham
Edit - toned down

I'd be grateful if you could you add a bit more detail to this assertion, in particular what determines the “child” / “parent” relationship.

I ask because my understanding of AuxPoW seems to be adrift, I managed to get a completely different impression from reading the Dogecoin statement.


Cheers

Graham

Could they be botnet machines? The two 24-hour period graphs of connected worker activity are almost identical, that's most unlikely unless there's a mechanism at work.

Cheers


Graham
 

I believe OS X 10.7 is Lion which is why I drew your attention to the macdeploy support in case you wanted a go at following the instructions and trying to get a build for yourself.

If you can get just one successful build under your belt, you'll be in good shape for others, might allow you to circumvent tiresome holdups.

I'd expect a Mac app compiled on 10.5 or 10.6 to run happily on 10.7 and later. That's one of the benefits of a relatively coherent single-vendor platform, a 10.6 compilation supports users of all subsequent OS versions too.

For a given value of “support”, ofc

Cheers

Graham

It's an elderly MacBook running OS X 10.6 plus the sdk for 10.5 (which is as far back as it goes) and an app compiled on 10.6 should run without problems on later versions.

If you're interested in exploring other options, the contrib directory includes a “macdeploy” folder which looks promising:

https://github.com/cassubian/detkcoin/blob/master/contrib/macdeploy/notes.txt

“macdeployqtplus works best on OS X Lion, for Snow Leopard you'd need to install Python 2.7 and make it your default Python installation.”

Cheers

Graham

Thank you for that.

I've not had time to investigate yet but the notion is: in order to function at all, the GUI wallet needs to recruit functionality from third-party (i.e. non-Apple) libraries which are unlikely to be available on the user's machine, so one strategy is to compile the library code into the app, thus avoiding the issue.

So, the fact that it's looking for a library on your machine is a primary fail - it shouldn't be looking for anything if the compilation was appropriately configured. In a triumph of hope over experience, I assumed that when XCode offered to compile a "Release", it would do the obvious and necessary thing and compile in the static code. Not so, it appears - and if it can't find libminiupnpc then it almost certainly won't be able find any of the other libraries that I so naively thought would be bundled in with the app.

I just need to mug up on XCode, find out what switches to press to get the desired output.

Of course, I have all the required libraries (in order to compile the app), so it never complains when I test it. But the total file size of the app should be a reasonable guide and if one library's statically compiled, they're all statically compiled (in principle, natch).

Cheers

Graham

See prior post to this thread: https://bitcointalk.org/index.php?topic=22785.msg8083116#msg8083116

Cheers

Graham

I tend not to mess about with default values set by the upstream folk, not unless I have compelling reasons such as working in a different context. Is libminiupnpc a known issue with OS X?


Cheers

Graham

Sorry about that.


That's useful, thank you.

I'll ensure it works before reposting.

Cheers

Graham

It's suffering the same fate as is likely to befall all the other algo-themed coins eventually, interest has dwindled to near zero.

Time and technology moves on; what was algorithmically hot in early 2014 is simply tepid four months later. At some point in the future, there may be a renaissance but I can't see a compelling reason for that happening any time soon, even with the current high level of dissatisfaction with new coin launches.

3 exchanges? I can only find it on one.

But, I'd be grateful for a copy of getpeerinfo results, I can't find anything to sync to.

For comparison, Grøstlcoin made a much better job of the marketing and what we're seeing here are basically the consequences of that crucial difference.

Nevertheless, one of the stronger points of this particular altcoin is that it is a “single malt” coin amidst a raft of “blended” (multi-algo) offerings (e.g. sifcoin, quark, qubit, nist5, twe, x11/12/13/14).

I need to explain my analogy ...

One source of my enlightenment (on the topic of “single vs blended”) is the SiFcoin dev's rationale for the design decision to adopt a multi-algo approach (google translated): “Complication chain to the length of 6 different hash functions and increase bit depth to intermediate 512 - attempt to protect from further development of extremely efficient Mh / s gpu-algorithms and theory, "simple" Gh / s devices”.  No mention of security, just a possibility of limiting GPU advantage.

The other source of my enlightenment is the posts made to the stackexchange discussion Guarding against cryptanalytic breakthroughs: combining multiple hash functions. Zooko's and Thomas' posts in particular bring a realistic appreciation of the issues.

Somehow, a simple and straightforward tactic to limit GPU advantage has mutated into security theatre: “super secure hashing” (Quark), “X15 adds 2 extra layers of hashing to the popular and already very secure X13 hashing Algorithm” (Maiacoin).

When it's boiled down to the essence: for an altcoin, a tactic of chaining hash algos can't be proven to increase security nor can the tactic be proven not to reduce security, the latter weakness being a default FAIL according to accepted best cryptographic practice.

This fact will be appreciated by altcoin engineering connoisseurs in a fashion I can only feebly analogise to the “single malt” vs “blended” dimension, hence my description of Fuguecoin as a “single malt” altcoin.

Cheers

Graham

Thanks for that transclusion, I found it most useful.

Cheers

Graham

Yes I can, it's clear from the rest of the semantics what the semantics of the word in question should be. The semantics of English is very robust in the face of syntactic raggedness.


I'm very familiar with the term “usability” but thank you for assuming ignorance on my part and providing a wikipedia definition, that was most considerate. I'm not sure why you went to the trouble though, it is a technical term from the domain of cognitive ergonomics and is an inappropriate choice in the given semantic context of providing a non-technical explanation of possible causes of variation in the coin's price on currency exchanges.

This is a statement from the coin developers to citizens of the UK and the choice of wording should convey the semantics as intended, not some serendipitous meaning that has to be stretched beyond all plausibility in order to fit.

Cheers

Graham

Whatever, a spelling-checker would have prevented the error. Feel free to apply that same correction to the misspelling where it appears in the javascript “slide” presentation and above, in the OP.

You have a fair amount of text wrangling to do in order to e.g., address nonsensical statements such as “The Cryptocurrency of the UK & British Isles” by narrowing the scope of the referenced geopolitical boundaries to what's actually covered by Google's API.

Perhaps another example might help get across my point about support from a copywriter: “The price of Sterlingcoin is determined by supply & demand, usability, trading and mining” - that should be either “usage” or just “use”, not “usability”.

Cheers

Graham

That's exactly as I expected but it needs to be clearly communicated on the web site.

Apart from the missing contact info and privacy statements expected of UK web sites, more attention to the wording is required. A moment's reflection will inform you that “UK” is inadequate unless you do actually intend to exclude residents of Northern Ireland.

Statements that are usefully accurate must somewhere use the mouthful: "United Kingdom of Great Britain and Northern Ireland".

Elsewhere, the statement “UK citizens receive fifty Sterlingcoin” is incorrect, the checks are for residence not citizenship.

There’s two of us here, we can manage a phone number each but only one postcode - do we get 50 each or will one application be rejected? This information should be readily available and easy to comprehend.

Minors are also citizens of the UK, if there's a lower age limit for this offer, that should be clearly communicated.

“Sterlingcoin is a completely fair, transaparant and a highly secure form of currency for all needs.” Provide some support for your claim of fairness. Use a spelling checker.

The OP advertises “575,000 Sterlingcoin (90% of Instamine) for the Spacedrop”. At 50 per application that's a grand total of 11500 applications. This  limit should be very clearly advertised.

Will applications from UK residents receive priority over applications from people outside the UK?

Cheers

Graham

The airdrop website laconically advises that “Emails submitted will not be sold/shared for promotion/marketing purposes.” Can I recommend that you make it clear that also holds true for telephone numbers?

Also, I couldn't seem to find the clear statements about terms & conditions, rights and privacy that I'd expect to see, given the claims made.

Cheers

Graham

Password-protecting the zip sources doesn't conceal the fact that the codebase of this coin is so old that it pre-dates the upgrade to leveldb (there's no /src/leveldb folder, a dead giveaway).

It's certainly not an implementation vehicle that I would have chosen for a long-term, fixed-PoW-then-PoS solution, looks more like the product of a particularly cheap altcoin cloning service.

Make sure you know the rules of this particular coin-game before devoting resources to mining --- i.e. if you don't intend to dump immediately, do make sure that you are satisfied with the projections of how the network is to be maintained after PoW finishes.

Compare with similarly-pitched fixed-PoW-then-PoS Bounty https://bitcointalk.org/index.php?topic=656663.0, launched 18th June, premine dumped on Bittrex 4 days later, ejected from Bittrex 14 days after that, wallets stopped syncing a few weeks after that. Total lifespan of the coin was around six/seven weeks.

That's how this coin-game goes.

Cheers

Graham

I think you're missing a step in the logic chain:

then just got burned ... and as I wasn't able to acquire cheaply a satisfying amount of coins ... I have decided to make a coin

Or am I doing you a disservice?

You don't need to go to all the effort of creating a new coin, launching it and providing long-term support for it, just to be able make long term investments with some degree of confidence.

There's a huge range of existing altcoins (nearly 1400 launched so far, see them all on one page: http://minkiz.co/coin/).

Those that have survived for longer than a quarter-year are most unlikely to be scams and they've got a much more extensive track record on which you can base your risk assessment.

Cheers

Graham

(Minki's coin metadata is publicly available, published as RDF: https://github.com/DOACC - update due this w/e.)

And forgot to delete the .git directory:


The developer of recently-deceased Godcoin admitted earlier today that it was a coingen coin.

So, Achilles is a gussied-up used coingen coin (yech).

Doesn't look too good for the promised EDI apps.

Cheers

Graham

Just for clarity, ~ is a short cut to /Users/your_account_username, you'll also encounter $HOME, same thing [1].


We saw the same error on our OS X 10.6 MacBook.

Here's a freshly-compiled OS X wallet, works on 10.6, should work for you on 10.7 - http://minkiz.co/noodlings/cdt/Detkoin-Qt-OSX.zip (referenced on http://minkiz.co/noodle)

Don't worry about creating directories. Fire up the app, it will create the directory: ~/Library/Application Support/Detkcoin. As soon as the wallet appears, that's it for this stage, you can shut it down.

Now fire up a text editor, paste the contents of the detkcoin.conf as listed in the OP and save that as ~/Library/Application Support/Detkcoin/detkcoin.conf and then restart the wallet, should start syncing, doesn't take long to get up date, just a few minutes.

To try mining, select Menubar->Help->debug window

debug window shows two tabs: tab1 is info,  tab2 is rpc terminal. In the commandline window at the bottom of tab2 enter setgenerate true -1 for all-in, chuck everything at the hashing. Or use positive integers to limit processing to use that number of threads/cores, e.g. setgenerate true 2.

Stop mining with setgenerate false.

HTH.

Graham

[1] there’s no place like $HOME

Edit: corrected config filename, added stop mining info