User:Lapp0/Best Practices - Revision history

Lapp0: /* Development Risks */

2015-01-23T20:50:29Z

Development Risks

← Older revision		Revision as of 20:50, 23 January 2015
Line 65:		Line 65:
	Using the [[Testnet]] is recommended. The Bitcoins on this network are designed to be valueless and there is no risk of monetary loss if your software has unexpected behavior while testing. If none of the faucets are working you can ask for testnetcoins on Freenodes #bitcoin-dev.		Using the [[Testnet]] is recommended. The Bitcoins on this network are designed to be valueless and there is no risk of monetary loss if your software has unexpected behavior while testing. If none of the faucets are working you can ask for testnetcoins on Freenodes #bitcoin-dev.

	Your software should NOT use the gettransaction [[Original_Bitcoin_client/API_Calls_list\|API call]] to verify that payments are in the blockchain ~~because of~~ [[Transaction malleability]]. Instead you can use listsinceblock.		Your software should NOT use the gettransaction [[Original_Bitcoin_client/API_Calls_list\|API call]] to verify that payments are in the blockchain due to [[Transaction Malleability\|transaction malleability]]. Instead you can use listsinceblock.

	Your businesses software should not handle others money in most cases. If you are planning on handling others bitcoins, the system should be developed by a professional developer with a strong understanding of cryptography and bitcoin.		Your businesses software should not handle others money in most cases. If you are planning on handling others bitcoins, the system should be developed by a professional developer with a strong understanding of cryptography and bitcoin.

Lapp0: /* Development Risks */

2015-01-23T20:49:46Z

Development Risks

← Older revision		Revision as of 20:49, 23 January 2015
Line 63:		Line 63:
	=Development Risks=		=Development Risks=

	Using the [[Testnet]] is recommended. The Bitcoins on this network are designed to be valueless and there is no risk of monetary loss if your software has unexpected behavior while testing.		Using the [[Testnet]] is recommended. The Bitcoins on this network are designed to be valueless and there is no risk of monetary loss if your software has unexpected behavior while testing. If none of the faucets are working you can ask for testnetcoins on Freenodes #bitcoin-dev.

	Your software should NOT use the gettransaction [[Original_Bitcoin_client/API_Calls_list\|API call]] to verify that payments are in the blockchain because of [[Transaction malleability]]. Instead you can use listsinceblock.		Your software should NOT use the gettransaction [[Original_Bitcoin_client/API_Calls_list\|API call]] to verify that payments are in the blockchain because of [[Transaction malleability]]. Instead you can use listsinceblock.

Lapp0: /* Centralized services */

2015-01-23T20:48:35Z

Centralized services

← Older revision		Revision as of 20:48, 23 January 2015
Line 39:		Line 39:
	* withhold your private keys and extort you		* withhold your private keys and extort you
	* send you malicious code that steals your money		* send you malicious code that steals your money
	* lie about a payment to you ~~for free~~		* lie about a payment to you costlessly
	* correlate your IP address with your transaction		* correlate your IP address with your transaction
	* have broken Javascript cryptography unintentionally		* have broken Javascript cryptography unintentionally

Lapp0: /* Centralized services */

2015-01-23T20:46:12Z

Centralized services

← Older revision		Revision as of 20:46, 23 January 2015
Line 41:		Line 41:
	* lie about a payment to you for free		* lie about a payment to you for free
	* correlate your IP address with your transaction		* correlate your IP address with your transaction
	* have broken Javascript unintentionally		* have broken Javascript cryptography unintentionally

	Blockchain.info is particularly bad in terms of security and ethics. It is strongly recommended that individuals and businesses don't use them. They have had large thefts<ref>[https://www.cryptocoinsnews.com/gentleman-hacker-returns-stolen-bitcoins-blockchain-info/ GENTLEMAN HACKER RETURNS STOLEN BITCOINS TO BLOCKCHAIN.INFO]</ref> and vulnerabilities that allow attackers to lie about payments.<ref>[https://www.cryptocoinsnews.com/blockchain-info-bug-one-month-fix/ Blockchain.info Bug Took One Month to Fix]</ref>		Blockchain.info is particularly bad in terms of security and ethics. It is strongly recommended that individuals and businesses don't use them. They have had large thefts<ref>[https://www.cryptocoinsnews.com/gentleman-hacker-returns-stolen-bitcoins-blockchain-info/ GENTLEMAN HACKER RETURNS STOLEN BITCOINS TO BLOCKCHAIN.INFO]</ref> and vulnerabilities that allow attackers to lie about payments.<ref>[https://www.cryptocoinsnews.com/blockchain-info-bug-one-month-fix/ Blockchain.info Bug Took One Month to Fix]</ref>

Lapp0: /* Wallet Types */

2015-01-23T20:44:10Z

Wallet Types

← Older revision		Revision as of 20:44, 23 January 2015
Line 43:		Line 43:
	* have broken Javascript unintentionally		* have broken Javascript unintentionally

	Blockchain.info is particularly bad in terms of security and ethics. It is strongly recommended that individuals and businesses don't use them. They have had large thefts<ref>[https://www.cryptocoinsnews.com/gentleman-hacker-returns-stolen-bitcoins-blockchain-info/ GENTLEMAN HACKER RETURNS STOLEN BITCOINS TO BLOCKCHAIN.INFO]</ref> and vulnerabilities that allow ~~users~~ to lie about payments.<ref>[https://www.cryptocoinsnews.com/blockchain-info-bug-one-month-fix/ Blockchain.info Bug Took One Month to Fix]</ref>		Blockchain.info is particularly bad in terms of security and ethics. It is strongly recommended that individuals and businesses don't use them. They have had large thefts<ref>[https://www.cryptocoinsnews.com/gentleman-hacker-returns-stolen-bitcoins-blockchain-info/ GENTLEMAN HACKER RETURNS STOLEN BITCOINS TO BLOCKCHAIN.INFO]</ref> and vulnerabilities that allow attackers to lie about payments.<ref>[https://www.cryptocoinsnews.com/blockchain-info-bug-one-month-fix/ Blockchain.info Bug Took One Month to Fix]</ref>

	===Local Wallets===		===Local Wallets===

Lapp0: /* Improper Handling Of Money */

2015-01-23T20:43:04Z

Improper Handling Of Money

← Older revision		Revision as of 20:43, 23 January 2015
Line 55:		Line 55:
	==Improper Handling Of Money==		==Improper Handling Of Money==

	[[Address reuse]] should be avoided, addresses should be used as invoices. [[From address\|From addresses]] cause confusion, there is no guarantee that a payer controls this address and paying back to it may cause loss of funds.		[[Address reuse]] should be avoided, addresses should be used as invoices. The use of "[[From address\|From addresses]]" (which don't actually exist<ref>[https://iwilcox.me.uk/2014/no-from-address There Is No 'From' Address]</ref>) cause confusion, there is no guarantee that a payer controls this address and paying back to it may cause loss of funds.

	==Anonymity==		==Anonymity==

Lapp0: /* Development Risks */

2015-01-23T20:40:02Z

Development Risks

← Older revision		Revision as of 20:40, 23 January 2015
Line 63:		Line 63:
	=Development Risks=		=Development Risks=

	Using the [[Testnet]] is recommended. The Bitcoins on this network are designed to be ~~free~~ and there is no risk of monetary loss if your software has unexpected behavior while testing.		Using the [[Testnet]] is recommended. The Bitcoins on this network are designed to be valueless and there is no risk of monetary loss if your software has unexpected behavior while testing.

	Your software should NOT use the gettransaction [[Original_Bitcoin_client/API_Calls_list\|API call]] to verify that payments are in the blockchain because of [[Transaction malleability]]. Instead you can use listsinceblock.		Your software should NOT use the gettransaction [[Original_Bitcoin_client/API_Calls_list\|API call]] to verify that payments are in the blockchain because of [[Transaction malleability]]. Instead you can use listsinceblock.

Lapp0: /* Improper Handling Of Money */

2015-01-23T20:25:38Z

Improper Handling Of Money

← Older revision		Revision as of 20:25, 23 January 2015
Line 55:		Line 55:
	==Improper Handling Of Money==		==Improper Handling Of Money==

	[[Address reuse]] should be avoided. [[From address\|From addresses]] cause confusion, there is no guarantee that a payer controls this address and paying back to it may cause loss of funds.		[[Address reuse]] should be avoided, addresses should be used as invoices. [[From address\|From addresses]] cause confusion, there is no guarantee that a payer controls this address and paying back to it may cause loss of funds.

	==Anonymity==		==Anonymity==

Lapp0: /* Anonymity */

2015-01-23T20:25:01Z

Anonymity

← Older revision		Revision as of 20:25, 23 January 2015
Line 59:		Line 59:
	==Anonymity==		==Anonymity==

	Bitcoin is not anonymous, it is pseudonymous. If you reuse addresses you will link your ~~pseudonyms/addresses~~ together.		Bitcoin is not anonymous, it is pseudonymous. If you reuse addresses you will link your private payments together.

	=Development Risks=		=Development Risks=

Lapp0: Created page with "Bitcoin is a trustless consensus system with no central authority. When you make a payment and it is confirmed into the blockchain, it is not feasible to have a "chargeback" u..."

2015-01-23T20:24:01Z

Created page with "Bitcoin is a trustless consensus system with no central authority. When you make a payment and it is confirmed into the blockchain, it is not feasible to have a "chargeback" u..."

New page

Bitcoin is a trustless consensus system with no central authority. When you make a payment and it is confirmed into the blockchain, it is not feasible to have a "chargeback" unless the person you paid pays you back themselves. Over the years there have been many losses of money through hacks, scams, software failures and other incidents.<ref>[https://bitcointalk.org/index.php?topic=83794.0#post_toc_11 List of events by BTC value lost]</ref> It is important that Bitcoin investors, users and developers understand these risks so they can be mitigated.

=Investing Risks=

==Bitcoin==

Bitcoin is a volatile asset. There is no promise that you won't lose all of your money when you buy bitcoin. In general, it is a good idea to understand something before you invest in it. In short, Bitcoin is a deflationary internet currency that requires a consensus system to work. This consensus system only works if a sufficient number of miners have the proper incentives to be honest. This means before buying bitcoins you should answer the following questions for yourself:
* Is deflation [http://krugman.blogs.nytimes.com/2010/08/02/why-is-deflation-bad/ problematic] or [https://mises.org/library/deflating-deflation-myth not]? Is it problematic to the point that it will cause Bitcoin to fail?
* How does the Bitcoin consensus system [https://bitcoin.org/bitcoin.pdf work]?
* Are the [https://github.com/kanzure/bitcoin-incentives/blob/master/bitcoin-incentives.tex incentives] of Bitcoin miners and other users in the system sufficient for consensus?
* Can Bitcoin gain sufficient merchants and users to sustain itself?
* Is there some other reason Bitcoin might fail?

When buying bitcoin, one should be aware of the risks that come with someone else holding their money. To reduce risk, your bitcoins or dollars should be traded on an exchange that you have researched and trust. Ideally, fiat and bitcoin should be on the exchange for as little time as possible.

==Bitcoin Related Investments==

Being a pseudonymous currency where users have little recourse if their money is stolen, Bitcoin attracts attracts scammers. There have been many scams and thefts involving Bitcoin. Before giving someone else your money consider whether the offer is to good to be true, whether you can trust the potential bitcoin recipient and what your counterparty risk is.

Some common scams or ripoffs includes cloud mining, which usually only returns a fraction of what you pay them, and altcoins which often advertise themselves as being the "next big thing" and claim to solve some problem in Bitcoin, by breaking the security model.<ref>[https://download.wpsoftware.net/bitcoin/alts.pdf A Treatise On Altcoins]</ref>

=Use Risks=

Once you have bought or earned Bitcoins, keeping them requires that no malicious party can spend the bitcoins in your wallet. If your computer is infected with malware then any time you decrypt your wallet the malware could potentially steal from you.

==Wallet Types==

Once you have chosen a wallet to use, you must [[Securing_your_wallet|create and use it securely]]. [https://bitcoin.org/en/choose-your-wallet Bitcoin.org] has a tool to view the security problems and benefits of many wallets.

===Paper Wallets===

A properly created [[Paper wallet]] removes the risk of theft-by-malware.

===Centralized services===

One of the main advantages of Bitcoin over traditional currencies is the lack of a requirement to trust someone else to own currency (trustlessness). When you give your money to a web wallet such as Coinbase, you are at risk of theft or some other form of loss.<ref>[https://bitcointalk.org/index.php?topic=83794.0#post_toc_11 List of events by BTC value lost]</ref> Services like Coinbase own your bitcoins and display a balance for you, but you aren't guaranteed to be able to spend that balance, you are trusting them.

There are web wallets that don't store your private keys such as [[blockchain.info]]. However there are still many risks involved, the service could
* withhold your private keys and extort you
* send you malicious code that steals your money
* lie about a payment to you for free
* correlate your IP address with your transaction
* have broken Javascript unintentionally

Blockchain.info is particularly bad in terms of security and ethics. It is strongly recommended that individuals and businesses don't use them. They have had large thefts<ref>[https://www.cryptocoinsnews.com/gentleman-hacker-returns-stolen-bitcoins-blockchain-info/ GENTLEMAN HACKER RETURNS STOLEN BITCOINS TO BLOCKCHAIN.INFO]</ref> and vulnerabilities that allow users to lie about payments.<ref>[https://www.cryptocoinsnews.com/blockchain-info-bug-one-month-fix/ Blockchain.info Bug Took One Month to Fix]</ref>

===Local Wallets===

[[Thin_Client_Security#Simplified_Payment_Verification_.28SPV.29|SPV thin clients]] allow you to have a secure wallet with the assumption that the majority of the mining power isn't malicious. These clients verify that a block exists and there was sufficient work done on it, but not that it was valid. Not verifying a block takes orders of magnitude less disk space, band width and processing power, however if a miner has 51% of the network hashrate, they can send you an invalid blockchain that has had more work done on it than the valid mainchain. This invalid blockchain might contain an invalid transaction that pays you money that doesn't exist. It is expensive to obtain 51% of the network hashrate, so SPV clients have a "good enough" level of security for small payments.

If you are storing and handling a large amount of money, you should use a full-node client that verifies every block such as Bitcoin Core. When a payment is made to you, it can be reversed with some probability by an attacking miner. As you receive more [[Confirmation|Confirmations]] it becomes exponentially more expensive for an attacker to doublespend a payment to you. Unconfirmed transactions have no guarantee and can be doublespent.

If you use a full node with a consensus reimplementation such as btcd, there is a risk you will lose consensus with the rest of the network.

==Improper Handling Of Money==

[[Address reuse]] should be avoided. [[From address|From addresses]] cause confusion, there is no guarantee that a payer controls this address and paying back to it may cause loss of funds.

==Anonymity==

Bitcoin is not anonymous, it is pseudonymous. If you reuse addresses you will link your pseudonyms/addresses together.

=Development Risks=

Using the [[Testnet]] is recommended. The Bitcoins on this network are designed to be free and there is no risk of monetary loss if your software has unexpected behavior while testing.

Your software should NOT use the gettransaction [[Original_Bitcoin_client/API_Calls_list|API call]] to verify that payments are in the blockchain because of [[Transaction malleability]]. Instead you can use listsinceblock.

Your businesses software should not handle others money in most cases. If you are planning on handling others bitcoins, the system should be developed by a professional developer with a strong understanding of cryptography and bitcoin.

==References==

<references/>