|
1 | | -BOP Community Bitcoin Server |
2 | | -============================ |
| 1 | +BOP Enterprise Server API |
| 2 | +========================= |
3 | 3 |
|
4 | | -This software enables your application to send/receive Bitcoin payments. |
| 4 | +API to Bits of Proof's BOP Enterprise Bitcoin Server. |
5 | 5 |
|
6 | | -You may run it stand-alone utilizing its own validation engine or as a slave behind the Satoshi client so it accepts exactly what the 'reference client' does. In either case it builds a fully indexed block chain of transactions stored in LevelDB. |
7 | | - |
8 | | -The server process handles peer-to-peer communication with the network and serves clients connected to it through a message bus. Wallet(s) are implemented by the client library and transactions are also signed at the client side. Private keys, that is the control of Bitcoins always remain at the client side. |
9 | | - |
10 | | -The BOP Community Bitcoin Server is a fully functional demonstration of BOP technology, that we use to build commercial applications such as wallets and exchanges. |
11 | | - |
12 | | -The BOP Enterprise Bitcoin Server supports the same API but has significantly improved performance e.g. in processing wallets using a large number of addresses. BOP offers professionally hosted Enterprise Bitcoin Servers, access to its latest Enterprise Server source code and support contracts. Please contact sales@bitsofproof.com for an offer. |
13 | | - |
14 | | -Build the Community Server |
15 | | --------------------------- |
16 | | -Make sure you have Maven3, JDK 7 (with JCE Unlimited Strength Policy Jurisdiction) and Google protobuf compiler 2.4.1 installed. |
17 | | - |
18 | | - git clone https://github.com/bitsofproof/supernode |
19 | | - |
20 | | - cd supernode |
21 | | - |
22 | | - mvn assembly:assembly |
23 | | - |
24 | | -The build will create a zip file in the target directory. |
25 | | - |
26 | | -Run |
27 | | ---- |
28 | | - |
29 | | - copy and unzip the distribution zip created in the previous step and cd to it. |
30 | | - |
31 | | - java -Xmx4g -jar bitsofproof-server-version-shaded.jar testnet3 memdb |
32 | | - |
33 | | -The final two parameters of the above example command line identify configuration contexts you copied under *-profile.xml. You have to choose one of the networks by specifying either testnet3 or production or slave, and a database layer, that could be (examples): |
34 | | - |
35 | | - * memdb - in memory database for tests |
36 | | - * leveldb - LevelDB |
37 | | - |
38 | | -To use the API of your local server you need to run a message broker process providing the infrastructure. Since the message bus offers authentication and a wide selection of transports, your installation will likely be unique and need to be reflected in BCSAPI-profile.xml. You find example configurations for the message Active MQ there. The complete command line for a production environment might be (assuming you run it as a slave behind a satoshi): |
39 | | - |
40 | | - java -server -Xmx4g -jar bitsofproof-server-version-shaded.jar slave leveldb BCSAPI activemq |
| 6 | +BOP offers access to latest BOP Enterprise Server source code and support contracts. |
| 7 | +Please contact sales@bitsofproof.com for an offer. |
41 | 8 |
|
42 | 9 | License |
43 | 10 | ------- |
44 | 11 | Apache License, Version 2.0. See LICENSE file. |
45 | | - |
46 | | -Donations |
47 | | ---------- |
48 | | -Please honor Bits of Proof's contribution to the Bitcoin community, and donate to: |
49 | | - |
50 | | -1EuamejAs2Lcz1ZPNrEhLsFTLnEY29BYKU |
51 | | - |
0 commit comments