moved to new thread

[Videlicet]

Looks like some noble effort here guys, keep up the good work. I know how long it can take to build something and do it right. 

Best of Luck,
Viz.

[Qarterd]

Looks like some noble effort here guys, keep up the good work.

Thanks, yeah we're really trying to innovate on every front here to create a true crypto 2.0, not only fully programmable, but also cryptographically future-proofed and scalable to the whole web.

[Videlicet]

You've got the right idea 

Curious though, how do you calculate the security to a Quantum Computer; are you just assuming multiplicity of the power from the available quantum states; then dividing hash security by this number?
I ask by your claims of 128 bit quantum security, curious as to how this is implemented.

Thank You,
Viz.

[Qarterd]

I ask by your claims of 128 bit quantum security, curious as to how this is implemented.

There is some mathematical evidence that the encryption system we're using is in fact quantum-resistant, so we only need enough bits in the key to thwart a quantum search (Grover's algorithm). Also, we use merkle hash trees for signatures, and although there is no proof yet, there are no known quantum algorithms that can attack hashes other than a quantum search. To brute force a 256-bit hash would usually take 2²⁵⁶ operations, but Grover's algorithm only takes O(√N) time, so that's 2^256/2 = 2¹²⁸ quantum operations = 128-bit level quantum security.

[Videlicet]

Good to see Developers that know what they are doing 

Thanks for the Information,
Viz.

[Qarterd]

why did you choose Python for the contracts

The reason why we chose Python is right on the front page, and also there is a section dedicated to it in the design document.

Transaqoins and qointracts are simply turing machines, there are many pre-existing languages that are adaptable to our needs and are already adept at interfacing humans with turing machines.

We must restrict our language choices to those that provide a ready-made embeddable virtual machine to ensure determinism. All nodes must be able execute the same sequence of transactions and result in the same state. The virtual machine must be able to hide device-specific state from programmers. Python, with a bit of tinkering, can meet these requirements.

Qointum is leveraging Python’s significant network effect – according to the TIOBE Index Python is in the top 5 virtual-machine languages and there are an estimated millions of Python developers world-wide. Qointum is also leveraging millions of man-hours of labour on the core Python language and third-party libraries, allowing us to focus on just developing a cryptocurrency, not a language.

[mistercoin]

For some reason I highly doubt you can guarantee that a quantum pc would not be able to crack this. I hope you will prove me wrong though.

[Qarterd]

For some reason I highly doubt you can guarantee that a quantum pc would not be able to crack this. I hope you will prove me wrong though.

Quantum computers are well understood, their capabilities have been studied for the past 20 years and yet no one has figured out a method to attack Merkle signatures or McEliece encryption which have been known for even longer, and now we even have mathematical evidence of quantum resistance (mentioned in my post above).

Over the last 10 years cryptographers have worked to reduce key sizes and improve efficiency to the point that these quantum-secure crypto schemes are now ready for practical use.

[Videlicet]

I hope to see you guys recognized for your hard work and innovation.

Good Luck,
Viz.

[grahvity]

Qointracts

[Qarterd]

Qointracts

Yeah it was too tempting of a pun.

[gjhiggins]

Qointracts

Yeah it was too tempting of a pun.

As a pun, it's rather twee and I predict that you will regret deeply the expense of the indulgence. Successfully expressing complex concepts clearly and concisely is difficult enough as it is without gratuitous distractions, however humorously intended.

Cheers

Graham

[Qarterd]

As a pun, it's rather twee and I predict that you will regret deeply the expense of the indulgence.

For marketable high-level concepts I believe it's more important to focus on branding to differentiate our ideas from those of our competitors. The puns are of course part of the branding -- Qoinapps (Blockchain Applications), Qointracts (Smart Contracts), Transaqoins (Smart Transactions?), Entangled Chains (Multi-Chains). These are things users and developers will be using on a daily basis, so a developer can search for say "qointracts" instead of "smart contracts" and find a relevant answer pertaining to Qointum.

We have more sensible names for technical concepts -- Maximally Vetted Delegate Chain, etc.

[grahvity]

As a pun, it's rather twee and I predict that you will regret deeply the expense of the indulgence.

For marketable high-level concepts I believe it's more important to focus on branding to differentiate our ideas from those of our competitors. The puns are of course part of the branding -- Qoinapps (Blockchain Applications), Qointracts (Smart Contracts), Transaqoins (Smart Transactions?), Entangled Chains (Multi-Chains).

We have more sensible names for technical concepts -- Maximally Vetted Delegate Chain, etc.

You're killing me.

[gjhiggins]

As a pun, it's rather twee and I predict that you will regret deeply the expense of the indulgence.

For marketable high-level concepts I believe it's more important to focus on branding to differentiate our ideas from those of our competitors.

The puns are of course part of the branding -- Qoinapps (Blockchain Applications), Qointracts (Smart Contracts), Transaqoins (Smart Transactions?), Entangled Chains (Multi-Chains). These are things users and developers will be using on a daily basis, so a developer can search for say "qointracts" instead of "smart contracts" and find a relevant answer pertaining to Qointum.

We have more sensible names for technical concepts -- Maximally Vetted Delegate Chain, etc.

Thanks for responding, I'm keen to see how you get on with developing a brand identity, values, story, etc.

My main objection is that you're replacing reasonably straightforwardly recognisable labels with labels that must first be decoded as puns. This adds to the mental load rather than reducing it.

Just for clarity, I'm not questioning the approach (of attending to branding) but the implementation. Unless you've got support from either desk research or quantitative work, then you're merely guessing at the effectiveness of the linguistic differentiation that you're proposing will somehow play into your branding. How will it translate across languages? (Hint: not at all).

Also, (largely because I think you've actually got something substantial and could with real support to keep you on the straight and narrow), I'm going to call your bluff on “... using on a daily basis, so a developer can search ...” I reckon that's just a guess on your part because you have no evidence for its pertinence to this context. Sounds as if there's little to no current MR support to drive this aspect of the development of a brand identity.

You're not the first person to have had the notion; all previous attempts to rope in punning linguistic markers to promote brand identity have basically sunk without trace because the proponents ignored the fact that what's humorously quirky to one is pretty much guaranteed to be irritatingly unfunny to another. It's not as effective a tactic as you seem to believe and its inability to cross alphabets is likely to prove a major disadvantage in a global market.

It also has the penalty that if the project is in any way successful, the IP in the brand naming will need to be protected proactively --- which means enforcing “Qointract™” (or whatever) in every usage.

From a branding perspective, it promises to be way more trouble that it's demonstrably worth.

Cheers

Graham

[gjhiggins]

From a branding perspective, it promises to be way more trouble that it's demonstrably worth.

Ach, never mind.

I'd failed to spot the design document's note: “This document describes inventions by NewGamePlus Inc. that are patent-pending with the USPTO.”


Cheers

Graham

[Qarterd]

*bump* still in development =)

[Corleone1918]

*bump* still in development =)

wow

[delulo]

I'm interested in this project. A few questions:
How will the ICO be structured: More "coins" if one invests at the start compared to an investment at the end of the ICO period?
Did you do your research on whether you violate any security laws by doing the ICO?
Do you develope all of the software form scratch? If not what project did you make use of?
Did you develope everything by yourself or do you have a team?
Will you publish information about your identity and the identities of your team before the ICO (a must for me if you want any money)?
Thanks for taking the time!

[Qarterd]

Do you develope all of the software form scratch? If not what project did you make use of?

There is some code taken from Bitcoin, code from Python as an interpreter is embedded, and code from existing implementations of our post-quantum cryptography which we'll reveal later.

Did you develope everything by yourself or do you have a team?

It's just myself right now.

Will you publish information about your identity and the identities of your team before the ICO (a must for me if you want any money)?

Take a look at our SSL certificate, it's from StartSSL.com which requires proof of personal identity. Also our company is federally incorporated in Canada which also requires proof of personal identity.