IMO people do care way too much about the short term price.

If you are using bitcoin as a speculative investment or tools for trading, you might care about the price.. but that's not the intention of bitcoin.

If you are holding bitcoin because of the value you think it has, and if nothing fundamental changes.. what is then the reason to panic because of a decline in price ?
In the long term bitcoin will establish as a means of payment. Especially with all changes happening (schnorr, LN, .. ).

A decline in price would be just short term. The long term outlook is still very positive.

You obviously don't have any experience at all.
The hash needs to be LOWER or EQUAL TO the target. This has been discussed in this thread and should be clear if you have completely read it.

The difficulty also does NOT increase each 2016 blocks. This depends on time it took to mine these blocks.
Overall, the difficulty rises. But there also were shorter streaks where the difficulty and hashrate was dropping over multiple periods.

You can get it from github (https://github.com/jackjack-jj/pywallet).

On linux install the following dependencies:


Then run the .py file according to the readme file.


If you are running into trouble installing/using it, read the first 2 pages of this thread.

With only this information, you can't.

Since you have found the file in the electrum directory, you most probably have used electrum ?
Do you remember installing it ?

Also.. did you do what nc50lc suggested ?

• Quote from: nc50lc on August 29, 2018, 07:10:53 AM
  Since you're using Electrum on Windows, try to look for the wallet files inside the electrum data folder:
  C:\Users\(Your Username)\AppData\Roaming\Electrum\wallets [Hidden by default]
  

This is the directory of electrum's wallet files (which contain all of your private keys).




You can not 'miss' a transaction.
Transactions are broadcasted into the network. Once they are included in a block, they are confirmed.

You don't need this information to access your btc. You only need the corresponding private keys.

With a big user base who is transacting daily on the LN, there will be enough on-chain transactions.
And if not, the fees for the on-chain transactions will be low enough for users to be attracted by on-chain tx's again.
I believe this will find an equilibrium.

The price does only have to grow exponentially if the miner do want to keep increasing the hashrate.
If mining gets unprofitable, the miner with the highest costs and lowest capital will stop mining and vice versa. This should also find an equilibrium.
 

That's not necessarily true.
These transactions do still exist inside of orphaned  blocks.

They are not part of the main chain, but these blocks do exist. And they are indexed and searchable.




You can view the block info of orphaned blocks here: https://www.blockchain.com/en/btc/orphaned-blocks
The orphaned blocks are valid blocks which are not part of the main chain, but contain valid transactions.

The average amount of blocks per day and the average time per block are calculated using the same 2 variables: Time and Number of blocks.

You can accomplish this by comparing the height each 24 hours.

You can use this command to get the current height:


The first time measuring, you just write down the number.
24 hours later you can again execute the command and subtract this number from the old one. What you get are the number of blocks in the last 24 hours.

This information is enough to calculate all data you want.

This file seems to contain transaction information. But it is not a 'transaction you can redeem'.
To gain access to the BTC, you need access to the private keys associated to the address.




You might start off with explaining what happened.

Which OS are you using ?
Which wallet are/were you using ?
How did you lose access to your coins / What happened ?
Do you have any backup (e.g. 12 word mnemonic phrase, xprv.. , QR codes..  ) ?

SegWit introduced a maximum block weight of 4.000.000 units (compared to 1.000.000 bytes).

A 'typical' (non-segwit) byte in a transaction has a weight of 4 units.A witness byte weighs 1 unit.

So, theoretically if all transactions would be segwit we'd have 4 times more transactions inside the blocks than pre-segwit.
But the block size itself (for the non-witness part of the transactions still is at 1 MB.

Did you run npm install inside the correct directory ?


Try installing the missing module (async) via this command:



If you are further running into trouble, copy the output of your terminal and paste it between code-tags ([ code] and [ /code] omitting the spaces)

Using windows as a privacy orientated user is generally quite a big problem.
The leakage of information is tremendous.

But only switching the OS won't protect you that much. The user habits have to be changed. And the proper OS can help you with that.




Tor is not anonymous by default.
There are a lot of tracing techniques (which are being applied by law enforcement agencies).

It is not impossible to stay anonymous. But it takes more than simply just using tor.

It is extremely important to note that the (only) official electrum is a BTC wallet. And the only official URL is https://electrum.org/.
Since electrum is open source (https://github.com/spesmilo/electrum), a lot of people forked the code and modified it to support different currencies.

However, this forks should NOT be regarded as safe. Without code reviewing/auditing, bad surprises may happen.
This does not mean that all forks are malicious. But there are malicious / buggy forks around under the name 'electrum'.

Yes. One way would be as bitfocus has suggested which will give you the 'mobile' bridge to your nano s.

The other way would be to setup a GNU/Linux environment [1] on your android tablet and install ledger live on it.
This will give you the desktop version of the UI (ledger live) for your nano s.


[1] https://www.xda-developers.com/guide-installing-and-running-a-gnulinux-environment-on-any-android-device/

A cold wallet is simply a wallet which is not connected to the internet in any way. And a wallet is a piece of software which manages your private- and public- keys.
Whether a transactions went trough only depends on whether it has been included into a block. It doesn't matter whether the private key to access these funds is stored offline or online.

Is it a completely 'fresh' wallet ?
Or do the addresses inside this wallet have a transaction history ?

You might want to uninstall jaxx, delete (or better: just rename) the jaxx folder inside the 'AppData' folder and reinstall it.
If its a synchronization issue, this should fix it.

But, Jaxx is known to be buggy and vulnerable. It is NOT recommended to use this wallet.
As soon as you are able to access your coins again, please move them to a safer wallet.

The only way would be to use the backup of your GA codes (which have to be done when scanning the QR / entering the code).
Without a backup, unfortunately not.




You either need the seed (which contains 2 of 3 keys) to access your coins OR help from TrustedCoin (they have 1 key and your current wallet file contains 1 key).

@OP: Note that after this step, your seed should be assumed to be compromised.
In order to keep the seed of a hardware wallet truly offline and isolated, you need to create a new seed with your trezor.

Encrypting the file asymmetrically would require a way larger key compared to encrypting it symmetrically.
The advantage of asymmetric encryption is the solution of the key exchange. It doesn't need one. But if you are only encrypting it as a backup for your own, using symmetric encryption is favorable.
Asymmetric keys have to be 10 (or more!) times larger than symmetric keys to have an equal bit strength.

Theoretically, a proper encrypted file with a key which is long enough to be considered safe should be absolutely fine. Even stored offline.
But the devil is in the detail. You have to rely on the software you use to encrypt the data to be correctly implemented (e.g. entropy).

In case of a data leak (on the cloud provider side) AND an incorrectly implemented algorithm, your keys are at risk. This scenario is pretty unlikely. But it should be considered nevertheless.

Bruteforcing the private key with 1 misstyped character can be done within one or two seconds. Thats 58*52 (= 3016) combinations.
Bruteforcing 2 characters does need to check the space of ( (52 choose 2) * 47 * 47 =) 4.308.174 combinations. This also can be done at home easily.
With 3, thats ( (52 choose 3) * 47 * 47 * 47 = ) 4.092.765.300 private keys to check. It starts to get rough here.

Basically, for N missing characters: (52 choose N ) * 47^N


If you have misstyped 1 or 2 characters the time it takes to bruteforce the private key is very low. Definitely worth a try.
But with a higher number of chars, it pretty much gets impossible.

You just need tool to check all possibilities for valid private keys. Because of the checksum the majority of these keys won't be valid.

Did you set the path manually ?


The slashes (/) seem to be wrong. Windows does use backslashes (\).