So, first you claim running a pruned node is not secure because it can be 'tricked'.

Then your whole statement is based on "bla bla bla.. if all mining pools are on a fork 550 blocks are not enough.. bla bla bla"

I hope you don't really believe the shit you are talking.


So.. i'll ask again.. HOW do you believe pruned nodes (not every pruned node is storing 550 blocks) can be 'tricked' ?
I know that they can't. The majority of experienced bitcoin user know that this is not possible.

Now i am asking you.. how do you think they can be tricked ? You, as an completely unexperienced user, should be able to explain it with real proofs.. or not ?

There are examples. At least examples of everything you need:


If your blockchain is stored in D:/Blockchain, then put this into the config file:


Pasting this one line into the config file is everything you need to do.


Another option would be to start armory with the startup parameter --satoshi-datadir
So it would look like this when stating from command line:

Oh, i have assumed you want to use exodus because you have said something about sweeping into exodus.

Usually it should work with every wallet.. Not sure why it doesn't work with the atomic wallet 




No, because you have received more than 1 transaction.
Most wallets do generate a new address (which also means a new private key) for each receiving transaction.

This is done for privacy reasons. Someone from outside can't link your two addresses together (if you don't use both of them in one transaction).




If you had all of your BTC 'on' one address prior to the fork, then yes.
If you had your BTC spread between 2 addresses, you need to import those 2 corresponding private keys to see all of your BCC.

Basically, each address which contained BTC at the forkdate results in one address containing BCC.
And each address needs one private key.

You might want to start with the actual problem you are facing.

It is hard for us to guess what went wrong.

You need an electrum server running to be able to connect to it with electrum.


If you only want to verify whether you have received the transaction yourself, but don't explicitly want to have the luxury of simply opening electrum, i'd suggest to simply run the core CLI and enter:


You will get all necessary information about the transaction id (sender/receiver/confirmations/..).

This takes less work and configuration than setting up an electrum server, but isn't that convenient for daily usage.

Yes, these are your private keys.




The private key which belongs to the address which had BTC stored prior to the forkdate 'contains' your BCC.
But it shouldn't say 'invalid key' at all.

Even if there are no funds there, importing shouldn't be a problem.
In fact, usually you can import all private keys and the wallet shows which address contains a balance.


Just to make sure.. your private keys start with 5.. and are 51 characters long, correct ?

---

Edit:
How did you actually try to import the private key ?

Exodus seems to not support importing private keys, but sweeping them (which means that exodus will take your private key and generate a transaction to an address from your exodus wallet). Effectively this is the same (difference: costs transaction fee + can be recovered using exodus mnemonic code).

To sweep a private key in exodus: Select Developer > Assets > Bitcoin Cash > Move Funds

Is this what you have tried ?

Where do you get all these wrong information from ?

Do they come up in your dreams about how unfair BTC is because you didn't invest when it was at 10$ / or being mad buying it at 20k$ ?
Or did you read them on some kind of anti-everything forum ?


Your statement is rubbish. You are completely delusional.

Pruned nodes are validating full nodes - by definition. They just discard the old blocks which they don't need anymore (because they already have verified them).

Please explain how they can be tricked. I love hearing fantasy stories. 

All of your questions already has been answered (multiple times).

Please read the thread carefully again if you still have questions/doubts. It can't be explained in more different ways and more easier than already done.




No. When he says private key, he means private key (click here).
A seed is NOT a private key. A seed is used to derive all private keys.

Generally, VirtualBox is good. But i wouldn't recommend it currently.

A new vulnerability has been found which allows to execute code on the host computer. [1]


Currently, it is definitely NOT recommended to use virtualbox on a system with sensitive information.

Especially since it has been published publicly without first contacting oracle. Including the code to actively exploit this vulnerability.
It will definitely take some time until oracle has a fix for it (as always).

In the meantime it might be better to use VMWare or any other virtualization software.


[1] Vulnerability + Exploit: https://github.com/MorteNoir1/virtualbox_e1000_0day/blob/master/README.md

Because a wallet is a software which manages your private-/public- keypairs.
Each address has its own private key.

That's how bitcoin works. I'd suggest you read a bit into how BTC works. A lot of people assume wrong things and make mistakes which leads to a loss of funds.




All which contained a balance prior to the fork date.




Did you properly copy the private keys and did you tick 'Private Key (Plain Base 58)' ?
You don't need to include the address or unused addresses. Only the private keys.

It is not about popularity, but about security.

AFAIK, bitcoin was the first project to use secp256k1 as the curve for calculations.




secp256k1 is not a technology. It is a curve used for elliptic-curve cryptography (ECC).
It doesn't make sense to say that this specific curve is going to be replaced.

It also doesn't make sense to say that ECC will be replaced as a technology. Do you have anything to back up your claims ? If not, your opinion will be considered worthless.

There are several guides available online on how to accept payments (either via core or electrum).
Electrum probably is a bit easier.

If you don't explicitly want to have a validating full node (but still want to use it trustless and with being in full control over your funds), i'd choose electrum to accept payments.

---

The hate is real 

OP, don't listen to this moron. He is a known flamer on this forum, trying to speak the word of god btrash.




That's a retarded statement.

Full node means that you have full control over the funds and can verify everything yourself (how BTC is intended to be).
Using a 'service' to accept payments means you do NOT have control over your funds and that you are trusting a 3rd party to give you correct information.




Same as the rise from 1k to 20k within a year.. +1900% compared to -66%.
But hey.. everyone is free to decide it for himself.

The idea would be that your offline-wallet (which holds the private keys) won't be vulnerable to attacks.
A wallet on an online server does always create a risk. With a watch-only wallet, you'll be able to generate receiving addresses but won't be able to send funds (since no private keys are stored).

If you then want to move funds, you'll need to do that from your offline-wallet (which is the only wallet holding the private keys).


You can't modify the watch-only wallet so that it will be able to send funds (if that's what your question was). This would be an oxymoron.

Generally this 2-wallet-setup is the best approach. Storing private keys on an online server is never a good idea. But in some cases it is required (e.g. hot wallet of an exchange).

As HCP has mentioned, to properly use armory you'll need to have core downloaded and fully synced.


But you don't need core if you only want to access/move your coins. You can simply open armory, export the private keys and import them into another wallet (e.g. a ligtweight client: electrum).

To export the private keys, start armory -> click 'Backup this wallet' -> 'Export key list' -> Then tick 'Private key (Plain Base 58)'.

In electrum: Create a new wallet -> 'Import Bitcoin addresses or private keys' -> Paste the private keys.

Did they really offer a malicious wallet to download ?

I remember them hosting a site to 'claim (or check) bitcoin gold' by entering private keys / seeds.
Any user who had entered their private keys / seeds got his funds stolen within seconds.

I wasn't aware of a malicious wallet.

Even if all miner would stop mining and start bruteforcing private keys, they wouln't be able to search trough a fraction of the keyspace in their lifetime.

The current hashrate is at about 50TH/s. That's 50*10^12 hashes per second.

Now, lets assume they can try private keys in the same speed (which the never can, since you'd need to calculate the public key out of the private key, then hash it to get the address and then check if it cointains balance while mining simply is double-hashing).

They (all miner) would need ~ 1.15^63 seconds to check half of the keyspace. That's 1.34 * 10^58 days.
That's 1340000000000000000000000000000000000000000000000000000000000 days if ALL miner could search at the same speed as hashing works (in fact that's MUUUCH slower).


As you see, this would be completely wasted energy. It's simply not possible. The keyspace is waaaaay too big.

Did you verify the signature ?

Even if you download it from the official source, a Man-in-the-middle attack could replace the original client with a malicious one.
Verifying the signature is the only way to make sure you are using the correct version.

If you are too lazy to verify the signature, at least check the hash of the file.

To check the hash, please do the following (assuming you are on windows):

• Open the command promt (WIN-key + R  -> then enter 'cmd')
• Enter: certUtil -hashfile C:/path/to/your/electrum/file.exe sha256

Then please post the output here and tell us which version of electrum you are using. I am then going to download the correct file and verify that the hash is the same.
If this is the case, your client was non-malicious and we have to look further how your coins got stolen.

What approach do you want to choose ?

1)
To enable pruning simply navigate into the bitcoin data directory (default path: ~/Library/Application Support/Bitcoin/) and edit the bitcoin.conf file.
If it doesn't exist, simply create one with this content:

Replace N with the size (in MB) you want to have stored on your hard drive. 550 MB is the minimum possible.
So, for example, if you want to have 5 GB stored, choose 5120 MB.


2)
If you want to keep the whole blockchain, move the bitcoin folder to an external drive (again, standard path: ~/Library/Application Support/ to an external drive).
Only do this while bitcoin core is NOT running. Then start up core and it will ask for a data directory path. Point it to your new path.

Not necessary.

All private keys are publicly available online.

This site (https://allprivatekeys.com/random.php) has ALL private keys stored 


P.S. Obviously it does really have all private keys, but the chances of finding a private key whose corresponding address does contain funds is almost 0 

You weren't able to reply to this topic because it has been locked.

Probably by the OP because the question already has been answered.


User starmyc has posted a link to such a dump:

Correct me if i'm wrong, but this should be completely unrelated to the seed used.
The only difference between a completely 'fresh' wallet and his old one is the seed.

In both case he is trying to connect with the same client and a 'new wallet' (at least a new wallet file, with the seed being the only difference).


@OP:
When were you able to properly connect using electrum the last time ?
May i ask from which country you are ? As far as i know, people from russia often do have problem using electrum because of restricted internet traffic.