Topic: IOTA - page 734. (Read 1473405 times)

The Turing paradox has been confirmed in an experiment.

http://news.cornell.edu/stories/2015/10/zeno-effect-verified-atoms-wont-move-while-you-watch

...

Very interesting reading. There are indeed breakthroughs in quantum computation almost weekly. Now of course 'breakthrough' is a laden word, but it's not really a controversial thing in academia. Big steps towards practical quantum computers are published wekly. Not too long ago there was still die-hard skeptics that claimed that decoherence made quantum computers IMPOSSIBLE, now of course we know that is bogus. Given that accelerating technology and research it should really be a no-brainer for anyone inventing the future to include protection against this.

163 chars without splitting. That string was split because of small screen width I think.

^ CfB probably wrote blockchain.info wallet because it's message functionality will be used.
See https://blockchain.info/de/wallet/features "Custom Send - Advanced Send form with coin control. With ability to embed messages in the blockchain."

I believe BCNext also used this.

Now I'm confused :-).

Which string do I have to put in during the ICO? I guess the 163 chars? Do I have to split them in two parts like in your example?

But...


Now I'm confused :-).

Which string do I have to put in during the ICO? I guess the 163 chars? Do I have to split them in two parts like in your example?

Quote from: martismartis on November 11, 2015, 11:07:42 PM
Maybe it is possible to separate then somehow, indicating which is which? will be a lot of confusion and questions about it in future Smiley

No need, users will use only the secret seed. That string will be published only once during the sale.

Quote from: Come-from-Beyond on November 09, 2015, 11:44:49 AM
These keys need to be published during the sale via https://blockchain.info/wallet.

during the sale? I thought it was just for test. What is the purpose of this?

These keys need to be published during the sale via https://blockchain.info/wallet.

Maybe it is possible to separate then somehow, indicating which is which? will be a lot of confusion and questions about it in future

There must be one string of 163 chars.

Hi,
when I run the above with FireFox Browser, I get one string without a break. Is it correct to split two characters before the "_" to get pub key and checkpoint key?

Use any of the files below:

For Windows 32-bit - http[Suspicious link removed]


Run the app and open http://localhost:9999/9abcdefghijklmnopqrstuvwxyz9abcdefghijklmnopqrstuvwxyz9abcdefghijklmnopqrstuvwxyz (it will take 5-10 seconds). You will see something like
Quote
GIETRWDKTJWJVAJDKZQHZAWGGKNCEONKJOUUCWCWLSSVTBUCATOIZTPLYVDDOISPZWBNHZMWRSDMQWE IN_IIBACWXHBCDIEJZSX9SUQAKI9XQNFJIQUASNMJLJZEHDZAOAQZJGMUQDHRRQYGOGSJRAJ99TKHGY DVPQE
The first part is your public key, the second part is your checkpointing key.

Hi,
could you explain what is "random entropy", please?

...

I think there will be definitely some other wallets available with great random entropy and easy for use, say wallet file similar to Bitcoin.

Yes. But the seed will be forced to 81 latin letters and '9'. Nothing stops other devs from using another approach, of course.

Seed must be exactly 81 characters long or it can be shorter?

I'm going to read a bit between the lines here but IOTA is built to work efficiently with a ternary (as opposed to ye traditional binary) processor that CfB is working on.  I would assume that since there are 26 letters in the English alphabet, adding an additional character to the list would make a well rounded 27 (3^3) available characters.  So 3 trits (think base-3 bits) can easily represent one character in the pubkey.  By adding one more character to the usable alphabet you don't have to filter out or validate that one, unusable value. All possible 3-trit values can be used for an 81-character pubkey.

But why 9?  Since 0 and 1 tend to be thrown out of specialty character sets that may need to be read by humans, this would leave digits 2-9 as possible numeric candidates for the 27th letter of the alphabet. 

Being that this is for a ternary system, we could narrow down the numeric character subset to values "2", "3", "6" and "9" as best possibly choices for stylistic reasons.

Since 9 = 3^2 and as CfB mentioned is the position of the Iota in the Greek alphabet, it makes sense to use the character "9" as the final letter in the IOTA pubkey alphabet.

Again, I'm reading between the lines but this is likely the logic I would have followed if I needed to create a ternary-friendly alphabet consisting of a minimal subset of characters for pubkeys.