I got it.  I like it so far.  I've only read the first ~20%, but it's thoroughly researched, and kind of interesting.  From what I've read, I'd say it's worth while.

No, paying for media you can already get for free will not be the killer app.

The private and public keys, and addresses, in Litecoin are exactly the same as they are in Bitcoin.  The address just starts with a different prefix byte.  But under the hood, it's exactly the same.  It's only the mining that's different -- using scrypt instead of sha256, and having blocks come 4x faster.  The public/private keys, and if Litecoin is using P2SH now too, all work exactly the same.

Not that it's of any particular use, but here's the squatter faggot's info, taken from another poker domain he's squatting.  And here's the mansion that such lucrative money can buy.  Squatters can go fuck themselves.

They just keep checking address down the tree until they get like 100 in a row with no transactions and then they assume they've reached the end and stop checking.

OP, no you cannot recover it.  :-(  The new "change" address was only in your Bitcoin-QT wallet, and not in the Blockchain.info wallet.  For now, you should probably stick to Blockchain.info or if you want a desktop wallet, something like Electrum.  Electrum in particular gives you a set of words you can write down that will always ensure you can recover your money (as long as you use only the addresses it provides you!)

Even if clients didn't check the genesis block, you'd still have to make a chain with more proof of work than bitcoin

No but I trust everybody else less.  (I answered "Yes 100%" to the survey because that was the closest.)

That was another address in your own wallet.  That's called a "change address".  When you spend bitcoin, you MUST spend all of an "input", which is money you received elsewhere.

All Bitcoin is is a chain of transactions going from A to B to C all the way back to when the coins were first minted.  So when you want to send 0.3 to somebody, what you do is you say to the network "hey look I got 0.47 from this transaction before, and I'd like to use it now".  And since you must spend all of it (that's how the protocol works), it sends 0.3 to the person you're sending it to, and the rest back to you (at a different address but one which you still control).  Then later, when you want to send 0.1 to somebody, the tx will use that 0.17 and send 0.1 to somebody, and 0.07 back to a new address of yours.

If you still have the file wallet.dat and haven't deleted it, you can recover your 0.17.  It's in there.

I would sell them if it was proven that P=NP

.... and not before then.

https://brainwallet.github.io/#converter

Source encoding is Base58Check.

It has an error though in that it cuts off the first byte.  So choose Base58 (no check) and it will show the first byte as well as 4 bytes at the end (which are a checksum, which is how your client knows if you've mis-typed something).

So if you want an accurate hex, just choose Base58 and delete the last 4 bytes and that's your hex.

Nevermind, that's just a god awful converter with a ton of errors.  Don't use it.  Download this, extract everything and run BtcAddress.exe and choose "Base58 Calculator" from the Tools menu.

no and if they did we wouldn't care and use it anyway

Probably put 20% of my bitcoin into nubits or bitusd.  I don't love bitcoin's variance, but it's still a waaaay good investment (just swingy), and I can't bring myself to keep my money in a form that somebody else can control and confiscate.

Or I may not-- the whole point of Bitcoin is to break away from the banking system, so even using USD and thinking in USD goes against that.  The few bitcoin businesses I've started have always had fixed btc prices (for at least a few months at a time anyway) for that exact reason.

I took that Stanford crypto class (and just barely passed it, dear god it was difficult), and the main thing I took away from it was "ZOMG DONT MAKE YOUR OWN CRYPTO."  Just use standard libraries and time-tested algorithms.  The best minds in the world came up with those and if they've been around a while, they're probably as good as you're gonna get.  Anything you come up with yourself is probably wrong, and you won't know it until you get hacked, because it hasn't been in the wild being tested and attacked.  Don't roll your own crypto!  Don't roll your own implementation!  Use the standard libraries.  That's what they're there for!!!

The JRSS isn't for the signature itself, it's for deriving dealer-less shares of a random k value among the t-of-n participants without revealing k.  (And can also be used to create shares of a new random private key without a dealer and hence without anybody ever knowing the private key.)

Excellent, thank you!  I consider myself pretty decent with my google-fu but I could not get it.  I will have to learn to navigate google scholar.  Thank you!!

NO, no no!!!  I did NOT mean the md5.  That can be written on the forged website.

I meant the PGP signature.  The PGP signature *HAD* to have come from the actual Electrum developers.  THAT'S what you need to verify.

To the right of the link to download, you'll see another link that says "sig" or "signature", which will lead you to either a .asc file or a .sig  file.

You then use PGP software (usually in the form of GPG) to verify that the signature is correct and from either the key:

9914864DFC33499C6CA2BEEA22453004695506FD

or the key

6694D8DE7BE8EE5631BED9502BD5824B7F9470E6

You need to learn how to use GPG for that.  It's a pain in the ass to learn, but once you learn it, it is extremely useful.  It's that same software people use to encrypt their e-mail.  Google and find Youtube videos about setting it up.  It takes time to learn, and that sucks, but you'll be glad you know it once you do.

The PGP signature, unlike a hash, can only be created by the developers.  So even if the website is hacked and the hackers put up new md5's for their evil files, they still can't make fake PGP signatures.

I read the paper on threshold signatures and I thought it would be a fun project -- and immense challenge, since I'm not an expert programmer or cryptographer! -- to try to write a Python module to implement it.

However, one aspect required is deriving shares of a random number (the K value, and also the initial private key) without ever having or revealing the fully constructed value.  They mention this is possible but don't show the protocol for it.

Instead, they reference the paper "A robust threshold elliptic curve digital signature providing a new verifiable secret sharing scheme" by the authors M.H. Ibrahim, I. Ali, I. Ibrahim, and A. El-sawi.  This paper supposedly includes the protocol for JRSS

I cannot find a copy of that paper online, and I was hoping somebody else might be able to find it, or already have it, or simply know the protocol for generating shares of a random value without anybody knowing the random value (aka JRSS).

Verify PGP sigs!!!

OP would you like us to inform Huobi that you are using your deposit address with them to run scams?