Why don't you post from your original account, coinhunter?

Similar in what way?

Bittorrent uses a decentralized DHT to find peers for a torrent. It also download files in "blocks" from different peers. That is somewhat similar, but the two are very different. One is a decentralized currency, one is a way of sharing files which can use centralized trackers or a decentralized DHT.

It doesn't necessarily need segwit, rather it needs a fix for transaction malleability, which segwit includes. LN uses advanced smart contracts which don't work well when the transactions can be malleated. There are other proposed fixes for malleability other than segwit, however segwit is the most tested solution, though segwit is not the absolute cleanest solution, in particular the fee discount makes spam a bit easier, but in exchange gives a softfork blocksize increase.

I agree (though I would say economy rather than companies to be more specific). However it is clear that after the hard fork the existing Bitcoin token will still have people wanting to trade it, miners wanting to mine it, and developers wanting to develop on it. Even when a majority of sha256 hashpower is mining another token the original token can stay secure by either changing the POW, allowing merge mining or some messy difficulty adjustment algorithm if thats what people want.



I don't think the likes of coinbase employ developers knowledgeable in maintaining a distributed consensus system. Maintaining a project like Bitcoin is vastly different to a normal software project. The best c++ developer in the world is useless at maintaining Bitcoin if he does not have a deep understanding in a vast array of other skills needed, and the people who have those skills are likely able to earn much more money working outside the Bitcoinsphere in less stressful and hostile environments.

Just look at the background of many of the people who have worked on Bitcoin. Mike Hearn was one of the most known senior Google engineers prior to his involvement in Bitcoin (I would occasionally read his blog for SEO tips, it was very popular), and also worked for a GCHQ contractor as a SIGINT operative (according to his google+ profile) before he went to on work on Bitcoin. Greg Maxwell worked for Juniper networks and worked on the BGP protocol, a decentralized protocol used by ISP's to exchange routing information for IP addresses, a critical part of the internet itself. Adam Back has been working on e-cash systems for decades, invented Bitcoin's POW implementation (as we have all heard a million times by now) and worked for David Chaum's company DigiCash back in the 90's. Finding people with the level of skill some of these people have who would most likely have to be willing to work for less money in a high stress environment would be difficult, it's not impossible, just not something that could easily be done.

In Bulgaria, extorting people on the internet is considered a rather nice way to spend a rainy day, part of the culture. If you are caught you just need to pay the government man $10 to stamp your paperwork that says your innocent. If he's only been there for several months that implies he wasn't born there, so chances are he has left now and nobody spends more than a few months in that shithole.

Best thing to do is to go to the marketplace section and hire a hacker to hack back the account. This will only work if the hacker you hire is more skillful than the one who stole your account however. If the hacker you hired steals your account, simply hire another.

I don't believe you!

Answer this question, how do Bulgarian's shake their head to say yes? No Googling!

I have solid evidence that Lauda lives in either Liberland, Rojava, Sealand or North Sudan. It is also a hermaphrodite.

They are still in use, but not nearly as prevalent as they were once. New technology is used, as you said. You can pick up numbers stations on shortwave radios in certain areas.

Numbers stations work really well, they are the tried and tested option. Why fix something that isn't broken.

This one is easy to explain. It is not good for security purposes to reuse addresses. Once you spend coins from an address, the public key will be revealed, so you should always move the rest of your coins to a new address.

Most of these addresses are probably long-term storage. The owners likely have other wallets that they use for day-to-day transactions.

If you go to profile > Forum Profile Information, and check "Show untrusted feedback by default:" the untrusted feedback will show up without needing to click.

But it is important to note that it is untrusted. It could be fake, as feedback is not moderated.

It's not hard to find theymos' email address. Try Google, awesome website you can use to find things. Or you could just check his website http://theymos.com

Makes it better, but doesn't fix it. It still doesn't scale linearly.

It was my understanding the EU already had directives that introduced the "right to be forgotten".

https://en.wikipedia.org/wiki/Right_to_be_forgotten#European_Union

Seems like this new legislation supersedes the current one, but I'm not sure what the differences are.

I know that you can issue takedowns to Google under the right to be forgotten if you are an EU citizen. Typically it applies to personal information. Does the new legislation allow for takedowns of other information?

It's because nullc criticized Gavin's new private key inspector service:
https://www.randomsanity.org/

Right, but the advice given by Google to website owners looking to implement TOTP is that they should provide a way to authenticate the user if they have lost their 2FA device.

Two ways to do this: first is to have the user write down a code that they can enter if they lose their 2FA device.

Another way which is what Google suggests is to: ask the user to open the website from a browser & IP they used before, ask them for the password, ask them to verify their email, ask them their account details and about some recent activity they did in their account, for bitcoin websites - ask the user to sign from Bitcoin addresses known to them, and then send the user an email and/or text message telling them their 2FA will be reset in 7 days unless they click a link to cancel the request. This is close to what Google does if you need to reset 2FA on your Gmail account for example.

The security of TOTP 2FA is overstated anyway. It really only protects you from password reuse and a crappy password. If your PC is infected, malware can just hijack your session. You can still get phished too.

A better 2FA system would be one that asks you to confirm whatever action you are doing on the 2FA device, then you'd be protected from an infected PC and phishing.


I really wouldn't recommend that as your ISP could change your IP range at any time. Also you could get locked out if you forget to pay your bill, or are away from home. IP authentication is weak anyway as a hacker only needs to find a way to use any device on your network to proxy requests. Depdning on how the website is set up, in some cases this can be done by you visiting a website with malicious javascript that allows the hacker to use your browser as a proxy while you have the page open.

That only works for Gmail, not BTC websites, unfortunately.

I'd recommend you take the photo on your phone, and if at all possible print it from your phone. Transferring the photo to your PC somewhat defeats the purpose of 2FA (even though 2FA can't protect you if your PC is hacked).

You can also scan the QR code with a QR scanner that will show you the text (it looks like a URL with a secret key at the end), and keep that (the entire URL). Then when you want to restore, encode this text back into a QR code and scan it.

I wrote a program that lets you store 2FA codes on an offline PC, and lets you do some cool stuff like encrypt them, copy them to another device or make backups. Perhaps I should release it, it's only command line though and I'm no good at making GUI's.

CoinJoin and joinmarket are cool. Will be interesting when joinmarket is more mature.

Any wallet that isn't a full node.