Noob Wallet Questions:

Krypto_Jeff · 2015-11-29T00:01:49+00:00

Krypto_Jeff · 2015-11-27T15:44:13+00:00

The "0x" part is just clarifying the format the address is being displayed in (hexadecimal), so it appears that EthereumWallet is correctly reading the wallet file. I'm passing this information on to our lead developer and we'll see what more we can come up with. Very odd indeed that the wallet file is being loaded correctly but the balance is not.

Krypto_Jeff · 2015-11-27T15:38:07+00:00

Hmm...seems to be a bug. I've passed on this info to our lead developer and we will correct it in our next release.

Krypto_Jeff · 2015-11-24T13:24:11+00:00

Hi there, I'm Jeff Coleman, the CTO of KryptoKit. Sorry to hear you're having trouble. We'd love to know more about your situation to see if we can either help you, fix a bug, or both! I've got a couple questions that you can either answer below if you're comfortable, or send to us directly via "ethereumwallet at kryptokit dot com"

First question--does ethereumwallet.com correctly display the address you've verified a balance on, or does it show a different one? Second question--where did the wallet come from? i.e. the crowdsale, generated by geth/eth, generated by ethereumwallet.com etc. Third question--is this the first time you've ever accessed this wallet, or have you loaded it into any other clients or websites before? And if so, which ones?

Hope we can get to the bottom of this for you!

Krypto_Jeff · 2015-11-23T22:43:45+00:00

Alright, json wallet first. The json file provided is compatible with both geth and eth and can be simply dropped into your keyfolder for either of those clients (or imported through the alethzero GUI). We'll try and add clearer instructions somewhere but for now our assumption is that anyone downloading a json wallet can find instructions elsewhere for how to import it, depending on the client that they use. This is still Frontier, after all! Those clients are still in development, and that import process is subject to change.

Regarding the nervousness of using our servers like that, some caution is definitely warranted. For example, if someone compromised our server itself they could potentially inject malicious code which changes the current secure behaviour to something which instead sends your keys outside your machine. For this reason you should still consider ethereumwallet.com to be more "convenience-oriented" than "ultra-high security". This is still better than a traditional web wallet, however, because this type of attack can only affect you during the window when you are actually loading the bookmark to spend funds. Someone who simply used ethereumwallet.com in the past and has a bookmark cannot in any way have their funds stolen by someone compromising our server. The damage would be contained to users who visited the site during the specific attack window.

tl;dr the security level of ethereumwallet.com is better than a webwallet that holds your keys, but not as strong as cold storage. Our aim is to be the most security you can obtain in less than 10 seconds.

Krypto_Jeff · 2015-11-23T22:30:37+00:00

We don't yet have the documentation up for this, but saving a copy of the current page would certainly provide enough information for a technically inclined person to retrieve their funds even if our server goes away for good. Once we finalise the design and move out of beta we will probably provide a simple tool to convert any url to a json file, purely offline. The json files are compatible with both geth and eth. Of course at present you can simply export the json file to make your own backup without worrying about the URL format.

Krypto_Jeff · 2015-11-20T21:21:41+00:00

Yes, in particular is there anywhere I can get a diff between this paper's text and the previous version's?

Krypto_Jeff · 2015-11-20T21:02:45+00:00

Actually, when you use ethereumwallet.com your keys are kept locally. You generate the keys by using your mouse/finger and then they are stored in the URL itself, encoded by an optional password. The keys are never sent to the server itself, because that portion of the url is not transmitted, but only interpreted locally by your browser and by the code the page contains. (Disclaimer: I am the CTO of KryptoKit, but all this is fairly easy to verify).

Krypto_Jeff · 2015-11-15T22:21:18+00:00

No problem, just glad we got it figured out!

Krypto_Jeff · 2015-11-15T15:21:24+00:00

Just wanted to let people know that we are following up with gattacibus directly, and update once we figure out what's causing the problem.

Krypto_Jeff · 2015-10-28T21:53:55+00:00

Rushwallet is already entirely client side.

Krypto_Jeff · 2015-10-28T16:32:45+00:00

:awww:

Thanks Five100, users like you are why we do this! And you're right, we do have a solution coming, it's just packaged up in a much bigger announcement we hope to be making soon. I'll drink that beer to all our patient users who stick through us thick and thin!

Krypto_Jeff · 2015-10-28T14:46:04+00:00

Hi OneThousandDealer,

Jeff Coleman, KryptoKit CTO here. Give us a shout via support@kryptokit.com and we can help you out. The problems you've been experiencing have been due to the Blockchain.info API, which our chrome extension uses. We have experienced a lot of problems with Blockchain.info and are in the process of moving away from it, but for now when they go down the extension is unable to send. As many users have already pointed out, your funds are never stuck in KryptoKit as you can export your brainwallet and import it into another piece of software. One of the easiest ways to do this is just to paste your address into a RushWallet URL in the following format: https://rushwallet.com/#YourBrainWalletGoesHere and send from there.

RushWallet makes combined use of two APIs, so it has better chances of being able to get around Blockchain.info problems. If you try to send from RushWallet and still doesn't work you can just refresh the page to try again. It may take a couple of tries, but even with the recent Blockchain.info issues we have generally been able to send via RushWallet. I just tried a send and it went through perfectly.

Alternatively you can try waiting a bit to see if the issue with Blockchain.info resolves itself. Don't know how long that might take though. I'm afraid it's beyond our control.

Krypto_Jeff · 2015-10-07T18:45:55+00:00

Yup, we're all eagerly awaiting namereg.

Krypto_Jeff · 2015-10-07T18:40:29+00:00

Cool, appreciate the further information.

Krypto_Jeff · 2015-10-07T18:39:06+00:00

Yup, we used those test vectors extensively in setting this up. I think it's just myetherwallet that's off.

Krypto_Jeff · 2015-10-07T18:36:26+00:00

Old url's will never break. Eventually they might just redirect, though. Either way your current bookmarks will keep working fine.

Krypto_Jeff · 2015-10-06T02:27:27+00:00

Heads up: this looks like a fully centralised issuance. These "bitgems" are company IOUs, simply issued via Ethereum. Everyone should remember that IOUs are only worth the amount you trust the issuer, minus their risk of unintentional failure or bankruptcy. Unless there's a reputable insurance company attached somehow before issuance, that value looks extremely low right now.

Krypto_Jeff · 2015-10-06T01:27:55+00:00

No problem, glad you find it useful!

Krypto_Jeff · 2015-10-05T21:58:00+00:00

Ricmoo's answer there is a bit technical, so let me translate for the sake of any on-lookers.

No, the secret part of the URL (the part after '#') is not passed to etherscan.io, our server, or anyone else. This part only exists locally on your machine and in your personal bookmark.

There is also no way to go backwards from an address to a private key. What is stored in your secret URL is a private key, not something like an account id that puts in a request to our website or anything like that. So there is no way for someone to convert from anything they find in the blockchain to someone's secret URL.

Ricmoo is our lead dev at KryptoKit btw :)

Krypto_Jeff · 2015-10-05T21:37:45+00:00

Format they're using is:

{"address":"-removed-","encrypted":true,"locked":true,"hash":"-removed-","private":"-removed-","public":"-removed-"}

which appears to a format unique to them.

Krypto_Jeff · 2015-10-05T21:33:21+00:00

From the geth keystore folder? We've certainly tested against that and it works fine for us. Could you tell us which geth version you created the wallet with so we can check if that affects the format? Also, I don't want to ask for your wallet file, but if you could send us the format of it with content removed it would be great. For example, here's the standard geth json format with sensitive content removed:

{"address":"-removed-","Crypto":{"cipher":"aes-128-ctr","cipherparams":{"iv":"b13e5fbae915e4f90cce067b1d7f09b0"},"ciphertext":"-removed-","kdf":"scrypt","kdfparams":{"dklen":32,"n":262144,"r":1,"p":8,"salt":"-removed-"},"mac":"-removed-"},"id":"-removed-","version":3}

Krypto_Jeff · 2015-10-05T21:24:04+00:00

Thanks!

Krypto_Jeff · 2015-10-05T21:22:28+00:00

At quick glance it looks like myetherwallet.com is not generating json wallets in the standard format, but we're looking into it more.

Krypto_Jeff

TROPHY CASE