Well, instead of entering your seed into a website (download it onto an offline pc first!!) and just importing 1 or 2 private keys, you might as well import the seed directly into electrum.
You can check the BIP39 Seed option and enter the derivation path (Ledger legacy: m/44/0/0, segwit: m/49/0/0)

You should be able to see your whole balance inside electrum.

But note, that once you have entered your seed anywhere else (e.g. electrum or website), it should be considered as compromised.
It is advised to create a new seed with your ledger afterwards if you want to use this hardware device to store your coins.

Well, the name pretty much tells it already.
Proof of Work relies on work to be done in order to secure the network (an attacker needs lots of work to attack the network).
Proof of Stake relies on money/value to be staked in order to secure the network (an attacker needs to stake a lot of money/value to attack the network).

IMO Artificial Intelligence is overhyped a lot. In the end all is build upon if-statements.

The goal should be to combine AI and the human mind so that the mind will profit from the AI.
You can't simply implement an AI into a blockchain.

You can use mechanism to check the security of a system or to simulate the outcome of a specific scenario in the future. But a direct connection between an AI and a blockchain probably won't exist in the near future.
At least i am not seeing a specific use case with this.


An AI is mostly only helpful when supporting humans (e.g. detection of cancer). Sure, you can build this upon a blockchain since it theoretically doesn't matter which kind of database you are accessing. But there aren't real benefits of blockchains compared to local databases in this case.

Accepting ANY coin will lead to a high volatility of your earnings.
People may place a small buy order for a shitcoin to pump the price by 200-300%. Then after paying you, they simply start selling their shitcoins again.

You effectively won't ever be able to sell your shitcoins for btc/USD because there is no liquidity.

I'd suggest you focus on the top 50 coins to accept. The easiest solution probably would be to find a payment processor, however creating a program to generate private keys, addresses and to query an API or check the blockchain shouldn't be too difficult to implement too, and would truly be decentralized as you wouldn't need to trust someone (e.g. payment processor).

Just to make sure, you did rename the file to <>.zip, right?
Because in case you did, the chances are high that your file is corrupted.

Which recovery software has been used? And do you still have an untouched copy/image of your old drive?
If you are simply formatting a drive most of the data will stay intact. The probability of a small .zip file to be corrupted are relatively small. It might have been the recovery software which didn't recover the file as it should (maybe uses different techniques for .jpg).
Another image of the drive could be useful for analysis with other (better) tools.

If you do not have such an image left, you probably have to follow NeuroticFish's advise and try out a zip-recovery tool.

Without being sure which of your addresses do hold your (complete) balance and without being very tech-savvy, you definitely shouldn't mess around with your wallet if waiting for core to sync is a viable option.
But you may should do at least one thing - backing up your wallet.

You can find your wallet file (named wallet.dat) inside the data directory of core.
If you have installed it as proposed by the installer, your data directory (windows) can be found under C:\Users\USERNAME\Appdata\Roaming\Bitcoin (note: USERNAME has to be replaced with your actual username).

You can also open this directory by pressing your WIN-key and R. Then enter %APPDATA%\Bitcoin into the field.


Just make one copy (or two) of the wallet.dat into another directory (e.g. your desktop) and you will be fine if you accidentally mess up with your wallet file later on.

Since you can see all the past transactions, you can check the receiving address of your latest transactions and enter this into a blockexplorer (e.g. https://www.blockchain.com/explorer).
If you can see the correct balance, you are fine.

Anyway it is still advised to move all of your funds to a new wallet.
You can either dump the private keys for each address inside the core console with this command:

Or let core sync and then send all your funds via core to your new wallet.

Did you download and use the *.AppImage file?
You need to open it with root rights for the wallet to be able to sync the nano s for the first time.

You always need to sign  transaction with the corresponding private key(s).
There is NO other way to send BTC's from one address to another.



You ALWAYS have control over the fees.
In cases where you don't have control over the fees, the user interface doesn't let you choose the fee. But the system/program/wallet itself has to set a fee.
To be more precise, the fee is determined by the difference of the inputs and the outputs (fee = sum of inputs - sum of outputs).

If you somehow cant set the fee, switch to a desktop-/mobile-/hardware- wallet. Those almost always do allow to set a specific fee.

You don't HAVE to generate/use a new address each time. It does NOT decrease the security of your coins in any way.

Anyway, as TryNinja has mentioned, it does harm your privacy (and the privacy of the people you are transacting with). Anyone transacting with you will be able to check your address and see (1) the amount of coins you hold, (2) the amount of transactions you are doing (3) the addresses you are transacting with.

You are free to choose whether you are using only one address for your lifetime, or whether you use an address as a one-time-transaction-identifier (which is recommended).

As far as i remember they told the first step was to implement the coins which were supported by their chrome applications (since chrome is shutting down all chrome applications + google is gathering massive amounts of user data).
Ledger told they are going to increase the number of supported coins gradually. In the end we will (hopefully) be able to access all coins storable on the nano s via ledger live.

But coins which were accessable via chrome applications needed to be implemented first -> then bug fixes -> UI/UX improvements -> adding erc20 -> adding more coins is the plan according to ledger.

Please, in the future, do not create a duplicate of your thread.

Use your first thread [1] to ask further question regarding the same topic. This won't just help keeping the board more clean, but will also help newcomers to faster find answers to their similar questions.
If you feel like people are kind of ignoring your thread, you are allowed to bump it once every 24 hours so it will appear back on top of the board.


[1] https://bitcointalk.org/index.php?topic=4744436.0

How do you come to the conclusion?

OP was asking for sources to understand PoS. And the ethereum wiki is one of the best places where PoS is explained pretty detailed.
Calling it 'not worth the time' is just overstated.




OP was asking for PoS, not for any shitcoin utilizing a PoW/PoS hybrid.

The problem is that Open Dime isn't a real 'wallet'.
It is a small device which holds one private key.

It either shows you the receiving address, or the private key (if you 'break' it).

The nano s is a hardware wallet based on your seed. It is not possible to import private keys into it (and thats good so, it would completely destroy the purpose since the seed HAS to be created in a secured offline environment, in nanos case: the device itself).
If you would be able to import a private key into the nano s, it might be compromised, compromising the overall security of your device.

Therefore you first have to import the private key into a wallet (e.g. electrum) and then afterwards create a transaction from this private key to your receiving address from the nano s.

Were you already able to import the private keys into electrum?

You will have to export them from armory (Wallet Properties > Backup This Wallet > Export Key Lists).
Then open electrum and create a wallet by importing the private key (of the address which holds your funds).

Afterwards you will be able to easily access/send your funds.

Since segwit got introduced the capacity of a block is measured in weight units, not bytes (4.000.000 weight units = 1 MB).
Theoretically if each transaction would be a segwit tx, the block size would be about 4MB. Currently it is at about 2.3 MB.

This, by the way, is also the reason why blockchain.info is calculating the fee wrong. If you are sending a transaction with effectively 1 sat/B, blockchain.info will show a fee of less than 1 sat/B (which practically is not possible since standard nodes do not relay transactions with a fee < 1 sat/B).

Yes, most merchants accepting bitcoin do use such a payment gateway.
They get paid in BTC -> the payment processor converts the BTC to fiat -> pays the merchant in fiat.

While you are right with the fact that it creates selling pressure since these coins are directly sold on an exchange, it is the first step towards BTC adoption.

The goal is not to always convert the BTC into fiat when paying a merchant, but it does reduce the inhibition level of a merchant accepting bitcoin.
Imagine how many merchants would accept BTC if they had to mannually sell them at the end of the day/week/month on an exchange, without knowing how much they actually will get. Since they often only have a small margin, this could completel destroy their business (especially if it is a smaller business).

The more accepted bitcoin as a mean of payment gets and the lower the volatility will be, the more merchants will start to accept direct bitcoin payments (at least if they actually can use these btc to pay their costs).

It is a bumpy road until BTC is seen as THE mean of payment, but it has to start with BTC->Fiat procesors.

Do you have set core to accept incoming connections?
Armory won't be able to get the necessary information if you don't allow incoming connections, since armory does not use RPC calls, but connects to core as a node (via loopback).

If you didn't allow incoming connections yet, do the following in core:
Click on 'Settings' -> 'Options' -> 'Network'-tab -> enable 'Allow incoming connections'

This may fix your problem. If not, you'll have to check whether your firewall is blocking something.
Additionally, do you use a VPN ?

Please answer these questions:

• Are you running the latest version of armory (0.96.4) ?
• Do you have the latest version of core installed (0.16.1) ?
• Is core running and synced ?
• Do you have incoming connections accepted in the bitcoin.conf (inside the core data directory) ?

If at least one answer is no, this point probably is causing the issue.
If you can answer all of these questions with yes it seems like it is a network issue. Maybe your firewall? Or are you connecting through a VPN?

Where can the source code be found? I didn't find any links on your website.
Is it even open source yet? Or do you plan on keeping it closed source?

I don't think issuing a closed source wallet is a good idea. I, personally, would never use such a wallet.

There are actually 0 benefits of a closed source project inside the crypto eco system.


Cons of this wallet:

• No security audits
• Maybe backdoored/malicious
• Eventually buggy
• Security by obscurity always was a bad design

Pros:

• Nice UI