That's pretty much all you need to know about this to know how stupid it would be to use one. It's so so easy to think that you've remembered a phrase and then you forget it one day.

I wish there was less fluctuation in the price so that people could focus more on developing technical advancements. It's hard to focus on that kind of stuff when there's drastic changes in the price.

I would increase the contrast on the items in your navbar. They're pretty hard to distinguish against the background, especially those buttons on the very top right corner.

Wouldn't that limit most people without large amounts of reputation to only a single open trade? I suppose that may be beneficial. Just trying to think of blocks in the user experience.

If you're using Windows and you'd rather not have to install any additional software, there's a certutil command available to calculate hashes (among other things).

To calculate a hash, do  certutil -hashfile filename algorithm

For example, certutil -hashfile image.png SHA256

The available hash algorithms are MD2, MD4, MD5, SHA1, SHA256, SHA384, and SHA512.

Blockchain will never, ever, ever made traditional databases obsolete. Blockchains cannot even come close to rivaling the speed and footprint of a standard database, SQL or No-SQL based. That's never been the point of a blockchain. What if I want to store a database of sensitive information? Why would I send it out all over the world? And yes, you could encrypt it but that's just additional overhead then.^[1] Blockchains are for having a decentralized, immutable, auditable database. Many people don't need that and don't want that. Say you have a traditional DB and someone changes their email address. All you have to do is change that value. But with a blockchain, you'd have to create another entry, taking up more space.

Blockchains solve a very niche solution, one that happened to greatly benefit Bitcoin but is not nearly as applicable in every situation as people like you make it out to be.


[1]: Actual sensitive data in a database should always be encrypted at rest. That's a big part of stopping would-be hackers from taking everything.

So basically the Golem network, but you don't have any actual software yet

I've seen plenty of people wanting to know how they can make money by routing payments. But a lot of them seem to not understand the scale required of both the whole network and the number of channels their node will have to maintain in order to make any amount of money they can recognize

I think it's going to take a lot more time to see people making money off of routing fees than it's going to take to see it being used by people. The usability is more than half there now. But it's still difficult to make money running a node.

So...I am to believe that the well experienced team behind BandZ are incapable of putting together a functioning website, something that anybody with $5 and an internet browser can do on a number of sites? But they're still somehow capable of running an ICO and taking people's money and promising to make...a VPN? Why try to solve a problem that nobody has? We already have VPNs. Free VPNs, paid VPNs, self-hosted VPNs, and then there's Tor and company if you're looking for something decentralized. I don't see the point of this at all.

If A and B are using the same wallet file, it doesn't matter if either of them encrypts it or when. They're already sharing the same master seed which is used to derive all of their addresses. Encryption only protects against people getting access to your computer and attempting to get to your private keys (master seed) but in this scenario you've let A and B share the same seed. They would both be able to spend the other's money.

Agreed. This totally destroys the purpose of hardware wallets, increased security. Carrying it around on your person all the time would be a horrible idea. Anybody seen with one (and you would be seen because it'd be on your phone) would be a prime target for robbery. The fact of the matter is if you're being held at gunpoint, it doesn't matter how secure the wallet you're holding is.

I believe they generate up to a certain amount by default, that can be configured to be larger if it's not generating all the addresses that you've used.

The xpub is the extended public key from which all of the addresses in the wallet are generated. It leaves the device so that the wallet can display your addresses and retrieve balances. It does not give control of your coins to anybody that has it, but it does reveal all current and future addresses.

As much as I hate Chrome, I don't really think it's as much of a privacy risk as some people might make it out to be. Sure, when you install the app, Google knows that you searched for and installed the ledger chrome app. But they're not stealing your xpub from the app, nothing like that.

That said, I am happy to not have to rely on Chrome because with that said, I don't want Google having a big list of ledger owners.

The thing is, because of the security model of the ledger devices, you don't have to worry about the platform you use it on, as long as you actually use the device to verify everything.

The first three wouldn't be something to add to AM because they're things that are easy to find just on the site.

The last couple won't be added because I don't run a LTC node on my machine and don't have any plans to.

The last ones are fine ideas though, just not something I'm going to add.

AM has been stable for a while now. While I'm not actively developing it anymore, if anybody has any feature requests, I'll gladly take a look at them.

Preferably you would use a computer/laptop that's never been online, something like a fresh linux install.

For instructions on how to do this using Electrum, click here.

Other wallets have similar instruction manuals you can find just by using Google.

I suggest allowing the user to scroll through the list no matter where their mouse is on the screen. Having the tip helps but I didn't even see it until I figured out that my mouse had to be over the center left panel. It's the only thing on the screen, there's no reason to restrict where you can scroll through the list. It looks very nice though.