Skip to content

Commit e23befd

Browse files
author
Will Binns
committed
index: Drop additional text for now
Context: #73
1 parent 82f5825 commit e23befd

File tree

1 file changed

+1
-52
lines changed

1 file changed

+1
-52
lines changed

index.rst

Lines changed: 1 addition & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -8,59 +8,8 @@ this documentation, `make sure you're running a node`_.
88
For technical support, we recommend `Bitcoin Stack Exchange`_. For errors or
99
suggestions related to this documentation, please open an issue on `GitHub`_.
1010

11-
A simple payment system
12-
-----------------------
13-
14-
Unless a payment needs to be associated with automatic invoices, accepting money
15-
is as simple as sending some bitcoin - just display an address or QR code. This
16-
simple setup is within reach of almost all users and can fulfill the needs of
17-
many clients. From an accounting perspective, it's especially suitable for
18-
reducing overhead and adding transparency.
19-
20-
Many third-party APIs
21-
---------------------
22-
23-
There are many third party payment processing services that provide APIs; you
24-
don't need to store bitcoins on your server and handle the security that this
25-
implies. Additionally, most of these APIs allow you to process invoices and
26-
exchange your bitcoins into your local currency at competitive costs.
27-
28-
Be your own bank
29-
----------------
30-
31-
If you don't use any third party APIs, you can integrate a Bitcoin node directly
32-
into your applications allowing you to become your own bank and payment
33-
processor. With all the responsibilities that this implies, you can build
34-
amazing systems that process Bitcoin transactions however you would like.
35-
36-
Bitcoin addresses to track invoices
37-
-----------------------------------
38-
39-
Bitcoin creates a unique address for each transaction. If you were to build a
40-
payment system associated with an invoice, all you would need to do is generate
41-
and monitor a Bitcoin address for each payment (you should never use the same
42-
address for more than one transaction).
43-
44-
Client side security
45-
--------------------
46-
47-
Most security is handled by the protocol, eliminating the need for PCI
48-
compliance. Fraud prevention can be simplified down to monitoring a single
49-
variable: the confirmation score. Beyond that, keeping your bitcoins secure is
50-
mainly a matter of securing your wallet and using HTTPS or other secure
51-
protocols to send payment requests to customers.
52-
53-
A new world of possibilities
54-
----------------------------
55-
56-
Bitcoin allows you to design new and creative online services that couldn't
57-
exist before due to financial limitations. This includes tipping systems,
58-
automated payment solutions, distributed crowdfunding services, time locked
59-
payment management, public asset tracking, low-trust escrow services,
60-
micropayment channels and more.
61-
6211
Acknowledgments
63-
========
12+
---------------
6413

6514
This documentation would not be possible without the many contributions to the
6615
Bitcoin project over the years from core developers and other people. A very

0 commit comments

Comments
 (0)