How did you move from Win8 to Win10? Did you update your operating system?


It's quite possible that Bitcoin Core just didn't get to processing the blocks where your transactions occurred... thus it cannot "see" your transactions and therefore hasn't displayed them in the transaction history.


This is could be somewhat problematic. You need to find your wallet.dat... then make a backup copy or two just in case.

It is highly likely (as you mentioned Windows 10), that your wallet.dat resides in a folder that is hidden by the Operating System by default. You would need to modify the windows settings to show hidden files/folders first. Refer: https://support.microsoft.com/en-us/help/4028316/windows-view-hidden-files-and-folders-in-windows-10

The file path should be: C:\Users\{YOUR-USER-NAME}\AppData\Roaming\Bitcoin

But you should be able to confirm this inside Bitcoin Core, by looking for the "datadir" value displayed on the following Menu option: "Window -> Information":

Then you might want to revisit the Ledger store and check current pricing... the Nano S is considerably cheaper: https://shop.ledger.com/products/ledger-nano-s

The Nano X is certainly a lot more expensive than the S. Nano S is currently selling for CAD$89, Nano X is CAD$159... that includes free shipping.

Reserved.


Hopefully someone gets the joke...

Is it possible that you accidentally "clicked twice" to create two transactions and/or you copy-pasted the wrong address (possibly clipboard jacking?)?

So basically... it *should* be good for at least 25 years from a data retention point of view.

The trick is finding a way of keeping it safe to prevent accidental loss, that also ensures that it is secure. Just like you need to with paper wallets, seed backups etc.

I'm sorry... but I don't really understand the strategy as you have explained it.
As I understand it, you're min-betting with 50% chance (low) until you get 3 losses in a row? Then you divide your balance in half 10 times... effectively (balance / 2^10) => (balance / 1024)... and make that your bet amount... while still betting "low" (< 50)?


But then I get very lost here:
What do you mean "it drops out> 50"?


As far as I can understand here... you're saying we bet "low" until we win (increasing by *2)... If win then continue to bet at the higher amount? then reset to 0.00000001 once we lose?... then wait for another 3 losses in a row... then repeat the entire process?

Unfortunately, this is very confusing and I really don't understand how the strategy works at this point.



And here you're just randomly betting hi/low?

I know it is difficult to try to put into words how the strategy works... but perhaps you could list a series of bets (amount + hi/low) and results to demonstrate how it works in the various examples.

I assume you mean 'import the private key for the address that has "3" prefix'... the private key itself should most likely start with a "T"

Theoretically... the SegWit private key that you generated, should be able to be imported as "p2wpkh-p2sh"... it will create an address that starts with "M", but it should be the "same" as the address that starts with a "3"... You can check this by using the Litecoin P2SH address converter here: https://litecoin-project.github.io/p2sh-convert/

Litecoin switched to using "M" prefix to try and prevent people from accidentally sending Litecoin to Bitcoin addresses

That error is caused because you do not have Bitcoin Core installed or have not configured Armory to look in the correct location for the Bitcoin Core datadir.

I assume you have setup Bitcoin Core to store it's data in a "custom" location... If so, you need to refer to the Armory docs on seeing up the "pathing": https://btcarmory.com/docs/pathing

For those who are interested... blackxsx12 has raised the flag against Strikke106 here

Based on the evidence I've seen, I've added my support to this flag.

Send them a PM telling them they have been accepted into the HoweyCoin SigCampaign and provide them with the signature BBCode

Just to clarify,

There were TWO parts to your query.The fee rate "discrepancy" is "a segwit thing" (as explained by bob123) due to the concept of weight units and virtual bytes... but the fact that there are 2 outputs created is simply "a Bitcoin thing". It is is not specific to SegWit transactions.

Believe it or not, but "Self-plagiarism" is actually a thing... refer: http://en.writecheck.com/self-plagiarism

Although it is probably of more relevance in the realms of academia, research and journalism... as others have stated, Rule #12 is probably more relevant on this forum.

Who "controls" the address: 3AHzNcaXcWBQc93kMCr26az2PthFXYaBzc?

You? Or is it a deposit address that is part of an exchange, marketplace or some other site?

As expected, it was simply a "pathing" issue... Armory was looking for your Bitcoin data in the "default" location... and failing:



It's just a "text" file with a .conf file extension... so you should be able to open it with notepad (or another texteditor) and just put the text there... or download the .conf files that PhoenixFire has created for you

Well... we got well and truly hosed didn't we? LOL... C'est la vie... Easy come... easy go!

I'll happy chip in another 0.01 if someone is going to run another round.

You should be able to use Litecoin Core or Electrum-LTC to import the private key

Electrum-LTC also has the advantage of not requiring that you sync the entire blockchain.

You seems a little confused about what a wallet actually is. A wallet is essentially a container for holding one or more private keys (and therefore, one or more addresses).

Even non-deterministic wallets (for instance, the old MultiBit "classic" wallet) can hold multiple private keys and therefore contain multiple addresses. The advantage of a "deterministic" wallet is that all the private keys are generated in a chain from a single starting point (aka "the seed") in a repeatable way... such that if you have the seed, you can completely rebuild the wallet.

Non-deterministic wallets just generated private keys randomly... so if you lost the wallet, there was no way to be able to rebuild it.

To answer you question regarding multiple addresses, if a wallet contains multiple private keys and therefore multiple addresses... you can send coins to any of the addresses that are controlled by that wallet and they will be displayed in the wallet balance... and will be able to be spent by that wallet.

I would agree that from a raw processing power point of view, the hardware in most modern phones is quite capable of acting as a Bitcoin Node... the issue is really that the package as a whole is not well suited to the task.

Surely, the thermal throttling that would likely occur during the CPU intensive initial sync, combined with relatively small batteries and often fairly limited storage capacity (which in a number of cases is non-upgradeable) make them a poor choice. And, yeah, you can get around the storage issue by running a "pruned" node... but then that is going to limit what you can actually do with it.

Personally, I think, as with a lot of things... just because you can, doesn't mean you should

#stopExcelAbuse

I believe the source code for the Electrum fork is here: https://github.com/eveybcd/electrum
The Electrum-BCD Releases are here: https://github.com/eveybcd/electrum/releases

Note that this is the same github account that holds the diamond "core" wallet as linked from the bitcoindiamond.org download page: https://github.com/eveybcd/BitcoinDiamond/releases/download/v1.2.0/bitcoindiamond-1.2.0-win64-setup-unsigned.exe

As for the "trustworthiness" of this... I'm not going to tell you that it's "safe". Take adequate precautions (run it in a VM or on a liveboot Linux USB, empty the BTC addresses first etc) and you should be "OK"... but "Use at your own risk" etc

Meanwhile, in the cheap seats waaaay up in the nosebleed section...