So you must be careful in choosing whom to add as a cosigner and not to create a 2-of-2 multisig address with a party who could potentially not sign your transaction. Otherwise, you will loose your coins send to that address. For example, you used 2-of-2 multisig when trading and you had an argument with the buyer/seller, he could decide not to sign transaction and you will loose your Bitcoin. Vice versa, you can do the same too! For trading, it's better to include one or more trusted third party depending on the trade as a cosigner, creating a 2-of-3 multisig address or m-of-n multisig address, n>=3 & m<n.


Multisig addresses are no different than normal address when it comes to transaction other than 2 or more signatures are required to send Bitcoin in it. Therefore, if there is a hardfork, you can broadcast your transaction into both chains or you can use a client which supports the chain you want. Usually, wallets choose a chain which is technically better/correct or widely accepted.

---

There is no "coins" in blockchain, only outputs. When a hardfork happens, blockchain will be split into. A chain on top of the blockchain without new rules and a blockchain with new rules. Outputs after hardfork in a chain will be invalid in the other blockchain. When choosing a chain, you must be careful not to chose a chain which nobody or very few people use because you can not broadcast a transaction which includes an output in a blockchain, to other chain.

If you don't understand, consider the current blockchain as a "path", say main_path. What happens when hardforking is, like the path being split into two different paths, say path 1(chain 1) & path 2(chain 2). You can choose which one to walk on  -- choose chain.

• Now, consider you are walking on main_path and you or someone stored something, say money, in a place along the way -- a transaction in current blockchain.
• You go on main_path and at the end, you are met with two paths, path 1 & path 2  -- hardfork
• You choose path 1  -- chain 1.
  
• You or someone else deposited money in a place on path 1  -- sending/receiving transaction in chain 1
• Let's say, after sometime, you want to take all the money you stored along the way. -- sending output
• Regardless of the path(path 1 & path 2) you want to walk to, you *will* have to go through main_path  -- current blockchain.
• You can take money deposited in main_path regardless of which path you want to go *to* because to get to path 1 or path 2, you have to go through main_path  --  using output in main chain in a transaction and broadcasting it to either of the chains - chain 1 & chain 2.

Now, consider these questions:

Q) Will you be able to get your deposit(output) in path 1(chain 1), if you go through path 2(chain 2)?
A) No.

Q) Doesn't that mean that if you send Bitcoin in chain 1, then that transaction won't be shown in chain 2?
A) Yes.

Q) If so, doesn't that mean we can spend double-spend?
A) Yes. But do note that, outputs in only *one* chain will be valuable.

Q) But, how do I know which chain to follow?
A) You can follow a chain which is followed by most.

Q) I followed a chain and there were many who used that blockchain. My transactions are all in blocks belonging to that chain. What do I do if no one uses that chain anymore? Can I recover my Bitcoin?
A) Your Bitcoin in main_chain will be there in the other blockchain even if you have already used it in the "wrong" chain. All the Bitcoin you received after hardfork, that is, when you used "wrong" chain, will be lost. You have to tell senders to resend Bitcoin to new address and this time, broadcast transaction to the "current/accepted" chain.

Did I miss anything or can't you understand someting? Feel free to ask in *another thread*.

Don't understand you understand anything at all? Ask your questions/doubts in a new thread and someone will answer you.

*  Word "output" here refers to UTXO(unspent transaction output).

---

I am not sure how ChipMixer does it. But, there is already a wallet which use nLocktime. You may have heard about it. It is called GreenAddress.

https://greenaddress.it/

When you become Jr. Member, i.e. activity reaches 30. It isn't far for you!

https://bitcointalk.org/index.php?topic=178608.0

Yes. You can keep one for yourself and one to whomever you want.

* Don't send your private key to someone you don't trust.

P.S. Main point in ChipMixer's post in Reddit  is timelock [1] transaction, not multisig.

[1] https://en.bitcoin.it/wiki/Timelock

Post here -> https://bitcointalk.org/index.php?topic=28402.0.

If you are afraid others will see your password while you type, take your notebook with you to bathroom. I highly doubt anyone would barge into bathroom while you "use".

I don't mean seed or xPrv, but xPub. It can be exported, right? If even xPub can't be exported, I will be disappointed in this wallet. No offence. I have used it before and I really liked it. Don't want to see it going downhill.

You will get it if you are Jr. Member and below or if you don't have any successful deals and you ask a loan of high amount with no collateral. If you got negative trust feedback for loan with no collateral as a Newbie, over time, it can be removed or at least, changed to neutral.

Enter redeemScript you got in http://coinb.in/#verify and check if the address you got is the same as the address in your wallet.

Doesn't Android Bitcoin wallet support exporting xPub? If yes, isn't that enough to generate new addresses? I haven't used android wallet for a long time now. So I don't know what all new features it have.


For receiving payments to new addresses each time. You may need to do it for privacy, for example, if you have a shop or if you are a seller.

Don't do anything to get negative trust feedback. Scamming, spamming, excessive trolling are plagiarism are some of them. As to which deserve negative trust and which don't vary from person to person. But users in DT trust list won't do anything "excessive". Else, they will be removed.


Be honest, contribute to forum and successful transaction. Point it out if I missed any!

After you enter xPrv in "BIP32 Root Key", don't click "BIP32" in derivation path. By default it will use BIP44 default derivation path and see if addresses you are looking for are generated.

If you are using command line, then it maybe more difficult than you image to set it up in Linux for those who are unfamiliar with Linux. But, Electrum has a GUI app which you could use. So it is as easy as setting up a normal wallet, just more time consuming.

17MxKujaf2sFtGzX36tSkVFXwkJCDsSS8J can be found in http://www.allprivatekeys.com/1157920892373161954235709850086879078528375642790749043826051631415181614942

You should upload to different servers so your backup won't be lost in case one is down and a few paper backups, in case all servers are gone (unlikely) or if you forgot your password. IMO, an encrypted backup is good, but you should use a password which you won't forget and not some "hard-to-crack password which is hard to remember. Forgetting your password is the last thing you want to happen when backing up an important file.

Sorry if I made a confusion by writing "sig" there. I was asking if such posts are spam and if they are deleted.


Me too!


Everything he said has already been said by others or is wrong and even the wrong statement he made has been posted one by another user and I already posted it is wrong. It can be said there is "nothing" in his post.


Already stated by another user before him and corrected by me.

I believe everything there is to be discussed about this proposal is already discussed. Is there any reason to continue this discussion?


When did that happen? Can someone give me a link to a detailed thread(if any)?

As we are talking about spam here, I want to know if this is considered as(sig) spam or not and if they are deleted by mods/staffs. Please read the whole thread(only 1 page) before answering.


*Edited

Quoted and verified.

1N9TBCcrwqrk7ZC4PWiuU1nUf8qkt7eEXR - https://bitcointalk.org/index.php?topic=996318.msg14039362#msg14039362

* Quoting it from shorena's thread in begginers & help board.