You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 26, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+18-15Lines changed: 18 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ use scenarios such as MAM and [TangleID](https://tangleid.github.io/).
19
19
20
20
At the moment, it is not feasible to host fully-functioned full nodes on Raspberry Pi class
21
21
Arm devices, but Raspberry Pi 3 is known to be capable to execute `Tangle-accelerator`
22
-
without problems. Since it is written in C/C++ with [entangled](https://github.com/iotaledger/entangled),
22
+
without problems. Since it is written in C/C++ with [iota.c](https://github.com/iotaledger/iota.c),
23
23
both footprint and startup time are behaved pretty well.
24
24
25
25
## Architecture
@@ -90,27 +90,30 @@ Tangle-accelerator is built and launched through Bazel, it also requires Redis t
90
90
91
91
## Build from Source
92
92
93
-
Before running tangle-accelerator, please edit binding address/port of accelerator instance, IRI, and redis server in `accelerator/config.h` unless they are all localhost and/or you don't want to provide external connection. With dependency of [entangled](https://github.com/iotaledger/entangled), IRI address doesn't support https at the moment. Here are some configurations and command you might need to change and use:
93
+
Before running tangle-accelerator, please edit binding address/port of accelerator instance, IOTA full node, and redis server in `accelerator/config.h` unless they are all localhost and/or you don't want to provide external connection. With dependency of [iota.c](https://github.com/iotaledger/iota.c), IOTA full node address doesn't support https at the moment. Here are some configurations and command you might need to change and use:
94
94
95
-
*`TA_HOST`: binding address of accelerator instance
96
-
*`TA_PORT`: port of accelerator instance
97
-
*`IRI_HOST`: binding address of IRI
98
-
*`IRI_PORT`: port of IRI
99
-
*`HTTP_THREADS`: Determine thread pool size to process HTTP connections.
100
-
*`quiet`: Turn off logging message
95
+
*`ta_host`: Binding address of accelerator instance.
96
+
*`ta_port`: Port of accelerator instance.
97
+
*`node_host`: Binding address of IOTA full node which includes IRI and Hornet or other community implementation.
98
+
*`node_port`: Port of IOTA full node.
99
+
*`http_threads`: Determine thread pool size to process HTTP connections.
100
+
*`quiet`: Turn off logging message.
101
101
102
102
```
103
103
$ make && bazel run //accelerator
104
104
```
105
+
105
106
### Building Options
107
+
106
108
Tangle-accelerator supports several different build time options.
107
109
108
110
* Docker images
109
111
* MQTT connectivity
110
112
* External database
111
113
* Debug Mode
112
114
113
-
Debug mode enables tangle-accelerator to display extra `debug` logs.
115
+
Debug mode enables tangle-accelerator to display extra `debug` logs.
116
+
114
117
```
115
118
bazel run --define build_type=debug //accelerator
116
119
```
@@ -160,13 +163,13 @@ clang-format can be installed by command:
160
163
## Usage
161
164
`Tangle-accelerator` currently supports two categories of APIs
162
165
* Direct API: check [wiki page](https://github.com/DLTcollab/tangle-accelerator/wiki) for details.
163
-
* Proxy API to IRI core functionalities
166
+
* Proxy API to IOTA core functionalities
164
167
165
-
### IRI Proxy API
166
-
`tangle-accelerator` allows the use of IRI core APIs. The calling process does not have to be aware of the destination machine running IRI. With the exactly same format of IRI API, `tangle-accelerator` would help users forward the request to IRI and forward the response back to users.
167
-
We support two way to forward Proxy APIs to IRI:
168
-
1. Bypass Proxy APIs directly to IRI.
169
-
2. Process the Proxy APIs, then transmit them to IRI.
168
+
### Full Node Proxy API
169
+
`tangle-accelerator` allows the use of IOTA core APIs. The calling process does not have to be aware of the destination machine running IOTA full node. With the exactly same format of IOTA core APIs, `tangle-accelerator` would help users forward the request to IOTA full node and forward the response back to users.
170
+
We support two way to forward Proxy APIs to IOTA full node:
171
+
1. Bypass Proxy APIs directly to IOTA full node.
172
+
2. Process the Proxy APIs, then transmit them to IOTA full node.
170
173
171
174
The user can choose which way they want with CLI argument `--proxy_passthrough`.
172
175
All the Proxy APIs are supported with the first way.
0 commit comments