You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

566 lines
17 KiB

  1. <!---
  2. order: 1
  3. --->
  4. # Creating an application in Go
  5. ## Guide Assumptions
  6. This guide is designed for beginners who want to get started with a Tendermint
  7. Core application from scratch. It does not assume that you have any prior
  8. experience with Tendermint Core.
  9. Tendermint Core is Byzantine Fault Tolerant (BFT) middleware that takes a state
  10. transition machine - written in any programming language - and securely
  11. replicates it on many machines.
  12. Although Tendermint Core is written in the Golang programming language, prior
  13. knowledge of it is not required for this guide. You can learn it as we go due
  14. to it's simplicity. However, you may want to go through [Learn X in Y minutes
  15. Where X=Go](https://learnxinyminutes.com/docs/go/) first to familiarize
  16. yourself with the syntax.
  17. By following along with this guide, you'll create a Tendermint Core project
  18. called kvstore, a (very) simple distributed BFT key-value store.
  19. ## Built-in app vs external app
  20. To get maximum performance it is better to run your application alongside
  21. Tendermint Core. [Cosmos SDK](https://github.com/cosmos/cosmos-sdk) is written
  22. this way. Please refer to [Writing a built-in Tendermint Core application in
  23. Go](./go-built-in.md) guide for details.
  24. Having a separate application might give you better security guarantees as two
  25. processes would be communicating via established binary protocol. Tendermint
  26. Core will not have access to application's state.
  27. ## 1.1 Installing Go
  28. Please refer to [the official guide for installing
  29. Go](https://golang.org/doc/install).
  30. Verify that you have the latest version of Go installed:
  31. ```bash
  32. $ go version
  33. go version go1.16.x darwin/amd64
  34. ```
  35. ## 1.2 Creating a new Go project
  36. We'll start by creating a new Go project.
  37. ```bash
  38. mkdir kvstore
  39. cd kvstore
  40. ```
  41. Inside the example directory create a `main.go` file with the following content:
  42. ```go
  43. package main
  44. import (
  45. "fmt"
  46. )
  47. func main() {
  48. fmt.Println("Hello, Tendermint Core")
  49. }
  50. ```
  51. When run, this should print "Hello, Tendermint Core" to the standard output.
  52. ```bash
  53. go run main.go
  54. Hello, Tendermint Core
  55. ```
  56. ## 1.3 Writing a Tendermint Core application
  57. Tendermint Core communicates with the application through the Application
  58. BlockChain Interface (ABCI). All message types are defined in the [protobuf
  59. file](https://github.com/tendermint/tendermint/blob/master/proto/tendermint/abci/types.proto).
  60. This allows Tendermint Core to run applications written in any programming
  61. language.
  62. Create a file called `app.go` with the following content:
  63. ```go
  64. package main
  65. import (
  66. abcitypes "github.com/tendermint/tendermint/abci/types"
  67. )
  68. type KVStoreApplication struct {}
  69. var _ abcitypes.Application = (*KVStoreApplication)(nil)
  70. func NewKVStoreApplication() *KVStoreApplication {
  71. return &KVStoreApplication{}
  72. }
  73. func (KVStoreApplication) Info(req abcitypes.RequestInfo) abcitypes.ResponseInfo {
  74. return abcitypes.ResponseInfo{}
  75. }
  76. func (KVStoreApplication) DeliverTx(req abcitypes.RequestDeliverTx) abcitypes.ResponseDeliverTx {
  77. return abcitypes.ResponseDeliverTx{Code: 0}
  78. }
  79. func (KVStoreApplication) CheckTx(req abcitypes.RequestCheckTx) abcitypes.ResponseCheckTx {
  80. return abcitypes.ResponseCheckTx{Code: 0}
  81. }
  82. func (KVStoreApplication) Commit() abcitypes.ResponseCommit {
  83. return abcitypes.ResponseCommit{}
  84. }
  85. func (KVStoreApplication) Query(req abcitypes.RequestQuery) abcitypes.ResponseQuery {
  86. return abcitypes.ResponseQuery{Code: 0}
  87. }
  88. func (KVStoreApplication) InitChain(req abcitypes.RequestInitChain) abcitypes.ResponseInitChain {
  89. return abcitypes.ResponseInitChain{}
  90. }
  91. func (KVStoreApplication) BeginBlock(req abcitypes.RequestBeginBlock) abcitypes.ResponseBeginBlock {
  92. return abcitypes.ResponseBeginBlock{}
  93. }
  94. func (KVStoreApplication) EndBlock(req abcitypes.RequestEndBlock) abcitypes.ResponseEndBlock {
  95. return abcitypes.ResponseEndBlock{}
  96. }
  97. func (KVStoreApplication) ListSnapshots(abcitypes.RequestListSnapshots) abcitypes.ResponseListSnapshots {
  98. return abcitypes.ResponseListSnapshots{}
  99. }
  100. func (KVStoreApplication) OfferSnapshot(abcitypes.RequestOfferSnapshot) abcitypes.ResponseOfferSnapshot {
  101. return abcitypes.ResponseOfferSnapshot{}
  102. }
  103. func (KVStoreApplication) LoadSnapshotChunk(abcitypes.RequestLoadSnapshotChunk) abcitypes.ResponseLoadSnapshotChunk {
  104. return abcitypes.ResponseLoadSnapshotChunk{}
  105. }
  106. func (KVStoreApplication) ApplySnapshotChunk(abcitypes.RequestApplySnapshotChunk) abcitypes.ResponseApplySnapshotChunk {
  107. return abcitypes.ResponseApplySnapshotChunk{}
  108. }
  109. ```
  110. Now I will go through each method explaining when it's called and adding
  111. required business logic.
  112. ### 1.3.1 CheckTx
  113. When a new transaction is added to the Tendermint Core, it will ask the
  114. application to check it (validate the format, signatures, etc.).
  115. ```go
  116. import "bytes"
  117. func (app *KVStoreApplication) isValid(tx []byte) (code uint32) {
  118. // check format
  119. parts := bytes.Split(tx, []byte("="))
  120. if len(parts) != 2 {
  121. return 1
  122. }
  123. key, value := parts[0], parts[1]
  124. // check if the same key=value already exists
  125. err := app.db.View(func(txn *badger.Txn) error {
  126. item, err := txn.Get(key)
  127. if err != nil && err != badger.ErrKeyNotFound {
  128. return err
  129. }
  130. if err == nil {
  131. return item.Value(func(val []byte) error {
  132. if bytes.Equal(val, value) {
  133. code = 2
  134. }
  135. return nil
  136. })
  137. }
  138. return nil
  139. })
  140. if err != nil {
  141. panic(err)
  142. }
  143. return code
  144. }
  145. func (app *KVStoreApplication) CheckTx(req abcitypes.RequestCheckTx) abcitypes.ResponseCheckTx {
  146. code := app.isValid(req.Tx)
  147. return abcitypes.ResponseCheckTx{Code: code, GasWanted: 1}
  148. }
  149. ```
  150. Don't worry if this does not compile yet.
  151. If the transaction does not have a form of `{bytes}={bytes}`, we return `1`
  152. code. When the same key=value already exist (same key and value), we return `2`
  153. code. For others, we return a zero code indicating that they are valid.
  154. Note that anything with non-zero code will be considered invalid (`-1`, `100`,
  155. etc.) by Tendermint Core.
  156. Valid transactions will eventually be committed given they are not too big and
  157. have enough gas. To learn more about gas, check out ["the
  158. specification"](https://docs.tendermint.com/master/spec/abci/apps.html#gas).
  159. For the underlying key-value store we'll use
  160. [badger](https://github.com/dgraph-io/badger), which is an embeddable,
  161. persistent and fast key-value (KV) database.
  162. ```go
  163. import "github.com/dgraph-io/badger"
  164. type KVStoreApplication struct {
  165. db *badger.DB
  166. currentBatch *badger.Txn
  167. }
  168. func NewKVStoreApplication(db *badger.DB) *KVStoreApplication {
  169. return &KVStoreApplication{
  170. db: db,
  171. }
  172. }
  173. ```
  174. ### 1.3.2 BeginBlock -> DeliverTx -> EndBlock -> Commit
  175. When Tendermint Core has decided on the block, it's transferred to the
  176. application in 3 parts: `BeginBlock`, one `DeliverTx` per transaction and
  177. `EndBlock` in the end. DeliverTx are being transferred asynchronously, but the
  178. responses are expected to come in order.
  179. ```go
  180. func (app *KVStoreApplication) BeginBlock(req abcitypes.RequestBeginBlock) abcitypes.ResponseBeginBlock {
  181. app.currentBatch = app.db.NewTransaction(true)
  182. return abcitypes.ResponseBeginBlock{}
  183. }
  184. ```
  185. Here we create a batch, which will store block's transactions.
  186. ```go
  187. func (app *KVStoreApplication) DeliverTx(req abcitypes.RequestDeliverTx) abcitypes.ResponseDeliverTx {
  188. code := app.isValid(req.Tx)
  189. if code != 0 {
  190. return abcitypes.ResponseDeliverTx{Code: code}
  191. }
  192. parts := bytes.Split(req.Tx, []byte("="))
  193. key, value := parts[0], parts[1]
  194. err := app.currentBatch.Set(key, value)
  195. if err != nil {
  196. panic(err)
  197. }
  198. return abcitypes.ResponseDeliverTx{Code: 0}
  199. }
  200. ```
  201. If the transaction is badly formatted or the same key=value already exist, we
  202. again return the non-zero code. Otherwise, we add it to the current batch.
  203. In the current design, a block can include incorrect transactions (those who
  204. passed CheckTx, but failed DeliverTx or transactions included by the proposer
  205. directly). This is done for performance reasons.
  206. Note we can't commit transactions inside the `DeliverTx` because in such case
  207. `Query`, which may be called in parallel, will return inconsistent data (i.e.
  208. it will report that some value already exist even when the actual block was not
  209. yet committed).
  210. `Commit` instructs the application to persist the new state.
  211. ```go
  212. func (app *KVStoreApplication) Commit() abcitypes.ResponseCommit {
  213. app.currentBatch.Commit()
  214. return abcitypes.ResponseCommit{Data: []byte{}}
  215. }
  216. ```
  217. ### 1.3.3 Query
  218. Now, when the client wants to know whenever a particular key/value exist, it
  219. will call Tendermint Core RPC `/abci_query` endpoint, which in turn will call
  220. the application's `Query` method.
  221. Applications are free to provide their own APIs. But by using Tendermint Core
  222. as a proxy, clients (including [light client
  223. package](https://godoc.org/github.com/tendermint/tendermint/light)) can leverage
  224. the unified API across different applications. Plus they won't have to call the
  225. otherwise separate Tendermint Core API for additional proofs.
  226. Note we don't include a proof here.
  227. ```go
  228. func (app *KVStoreApplication) Query(reqQuery abcitypes.RequestQuery) (resQuery abcitypes.ResponseQuery) {
  229. resQuery.Key = reqQuery.Data
  230. err := app.db.View(func(txn *badger.Txn) error {
  231. item, err := txn.Get(reqQuery.Data)
  232. if err != nil && err != badger.ErrKeyNotFound {
  233. return err
  234. }
  235. if err == badger.ErrKeyNotFound {
  236. resQuery.Log = "does not exist"
  237. } else {
  238. return item.Value(func(val []byte) error {
  239. resQuery.Log = "exists"
  240. resQuery.Value = val
  241. return nil
  242. })
  243. }
  244. return nil
  245. })
  246. if err != nil {
  247. panic(err)
  248. }
  249. return
  250. }
  251. ```
  252. The complete specification can be found
  253. [here](https://docs.tendermint.com/master/spec/abci/).
  254. ## 1.4 Starting an application and a Tendermint Core instances
  255. Put the following code into the "main.go" file:
  256. ```go
  257. package main
  258. import (
  259. "flag"
  260. "fmt"
  261. "os"
  262. "os/signal"
  263. "syscall"
  264. "github.com/dgraph-io/badger"
  265. abciserver "github.com/tendermint/tendermint/abci/server"
  266. "github.com/tendermint/tendermint/libs/log"
  267. )
  268. var socketAddr string
  269. func init() {
  270. flag.StringVar(&socketAddr, "socket-addr", "unix://example.sock", "Unix domain socket address")
  271. }
  272. func main() {
  273. db, err := badger.Open(badger.DefaultOptions("/tmp/badger"))
  274. if err != nil {
  275. fmt.Fprintf(os.Stderr, "failed to open badger db: %v", err)
  276. os.Exit(1)
  277. }
  278. defer db.Close()
  279. app := NewKVStoreApplication(db)
  280. flag.Parse()
  281. logger := log.NewTMLogger(log.NewSyncWriter(os.Stdout))
  282. server := abciserver.NewSocketServer(socketAddr, app)
  283. server.SetLogger(logger)
  284. if err := server.Start(); err != nil {
  285. fmt.Fprintf(os.Stderr, "error starting socket server: %v", err)
  286. os.Exit(1)
  287. }
  288. defer server.Stop()
  289. c := make(chan os.Signal, 1)
  290. signal.Notify(c, os.Interrupt, syscall.SIGTERM)
  291. <-c
  292. os.Exit(0)
  293. }
  294. ```
  295. This is a huge blob of code, so let's break it down into pieces.
  296. First, we initialize the Badger database and create an app instance:
  297. ```go
  298. db, err := badger.Open(badger.DefaultOptions("/tmp/badger"))
  299. if err != nil {
  300. fmt.Fprintf(os.Stderr, "failed to open badger db: %v", err)
  301. os.Exit(1)
  302. }
  303. defer db.Close()
  304. app := NewKVStoreApplication(db)
  305. ```
  306. For **Windows** users, restarting this app will make badger throw an error as it requires value log to be truncated. For more information on this, visit [here](https://github.com/dgraph-io/badger/issues/744).
  307. This can be avoided by setting the truncate option to true, like this:
  308. ```go
  309. db, err := badger.Open(badger.DefaultOptions("/tmp/badger").WithTruncate(true))
  310. ```
  311. Then we start the ABCI server and add some signal handling to gracefully stop
  312. it upon receiving SIGTERM or Ctrl-C. Tendermint Core will act as a client,
  313. which connects to our server and send us transactions and other messages.
  314. ```go
  315. server := abciserver.NewSocketServer(socketAddr, app)
  316. server.SetLogger(logger)
  317. if err := server.Start(); err != nil {
  318. fmt.Fprintf(os.Stderr, "error starting socket server: %v", err)
  319. os.Exit(1)
  320. }
  321. defer server.Stop()
  322. c := make(chan os.Signal, 1)
  323. signal.Notify(c, os.Interrupt, syscall.SIGTERM)
  324. <-c
  325. os.Exit(0)
  326. ```
  327. ## 1.5 Getting Up and Running
  328. We are going to use [Go modules](https://github.com/golang/go/wiki/Modules) for
  329. dependency management.
  330. ```bash
  331. export GO111MODULE=on
  332. go mod init github.com/me/example
  333. ```
  334. This should create a `go.mod` file. The current tutorial only works with
  335. the master branch of Tendermint, so let's make sure we're using the latest version:
  336. ```sh
  337. go get github.com/tendermint/tendermint@master
  338. ```
  339. This will populate the `go.mod` with a release number followed by a hash for Tendermint.
  340. ```go
  341. module github.com/me/example
  342. go 1.16
  343. require (
  344. github.com/dgraph-io/badger v1.6.2
  345. github.com/tendermint/tendermint <vX>
  346. )
  347. ```
  348. Now we can build the binary:
  349. ```bash
  350. go build
  351. ```
  352. To create a default configuration, nodeKey and private validator files, let's
  353. execute `tendermint init validator`. But before we do that, we will need to install
  354. Tendermint Core. Please refer to [the official
  355. guide](https://docs.tendermint.com/master/introduction/install.html). If you're
  356. installing from source, don't forget to checkout the latest release (`git
  357. checkout vX.Y.Z`). Don't forget to check that the application uses the same
  358. major version.
  359. ```bash
  360. rm -rf /tmp/example
  361. TMHOME="/tmp/example" tendermint init validator
  362. I[2019-07-16|18:20:36.480] Generated private validator module=main keyFile=/tmp/example/config/priv_validator_key.json stateFile=/tmp/example2/data/priv_validator_state.json
  363. I[2019-07-16|18:20:36.481] Generated node key module=main path=/tmp/example/config/node_key.json
  364. I[2019-07-16|18:20:36.482] Generated genesis file module=main path=/tmp/example/config/genesis.json
  365. I[2019-07-16|18:20:36.483] Generated config module=main mode=validator
  366. ```
  367. Feel free to explore the generated files, which can be found at
  368. `/tmp/example/config` directory. Documentation on the config can be found
  369. [here](https://docs.tendermint.com/master/tendermint-core/configuration.html).
  370. We are ready to start our application:
  371. ```bash
  372. rm example.sock
  373. ./example
  374. badger 2019/07/16 18:25:11 INFO: All 0 tables opened in 0s
  375. badger 2019/07/16 18:25:11 INFO: Replaying file id: 0 at offset: 0
  376. badger 2019/07/16 18:25:11 INFO: Replay took: 300.4s
  377. I[2019-07-16|18:25:11.523] Starting ABCIServer impl=ABCIServ
  378. ```
  379. Then we need to start Tendermint Core and point it to our application. Staying
  380. within the application directory execute:
  381. ```bash
  382. TMHOME="/tmp/example" tendermint node --proxy-app=unix://example.sock
  383. I[2019-07-16|18:26:20.362] Version info module=main software=0.32.1 block=10 p2p=7
  384. I[2019-07-16|18:26:20.383] Starting Node module=main impl=Node
  385. E[2019-07-16|18:26:20.392] Couldn't connect to any seeds module=p2p
  386. I[2019-07-16|18:26:20.394] Started node module=main nodeInfo="{ProtocolVersion:{P2P:7 Block:10 App:0} ID_:8dab80770ae8e295d4ce905d86af78c4ff634b79 ListenAddr:tcp://0.0.0.0:26656 Network:test-chain-nIO96P Version:0.32.1 Channels:4020212223303800 Moniker:app48.fun-box.ru Other:{TxIndex:on RPCAddress:tcp://127.0.0.1:26657}}"
  387. I[2019-07-16|18:26:21.440] Executed block module=state height=1 validTxs=0 invalidTxs=0
  388. I[2019-07-16|18:26:21.446] Committed state module=state height=1 txs=0 appHash=
  389. ```
  390. This should start the full node and connect to our ABCI application.
  391. ```sh
  392. I[2019-07-16|18:25:11.525] Waiting for new connection...
  393. I[2019-07-16|18:26:20.329] Accepted a new connection
  394. I[2019-07-16|18:26:20.329] Waiting for new connection...
  395. I[2019-07-16|18:26:20.330] Accepted a new connection
  396. I[2019-07-16|18:26:20.330] Waiting for new connection...
  397. I[2019-07-16|18:26:20.330] Accepted a new connection
  398. ```
  399. Now open another tab in your terminal and try sending a transaction:
  400. ```json
  401. curl -s 'localhost:26657/broadcast_tx_commit?tx="tendermint=rocks"'
  402. {
  403. "jsonrpc": "2.0",
  404. "id": "",
  405. "result": {
  406. "check_tx": {
  407. "gasWanted": "1"
  408. },
  409. "deliver_tx": {},
  410. "hash": "CDD3C6DFA0A08CAEDF546F9938A2EEC232209C24AA0E4201194E0AFB78A2C2BB",
  411. "height": "33"
  412. }
  413. ```
  414. Response should contain the height where this transaction was committed.
  415. Now let's check if the given key now exists and its value:
  416. ```json
  417. curl -s 'localhost:26657/abci_query?data="tendermint"'
  418. {
  419. "jsonrpc": "2.0",
  420. "id": "",
  421. "result": {
  422. "response": {
  423. "log": "exists",
  424. "key": "dGVuZGVybWludA==",
  425. "value": "cm9ja3My"
  426. }
  427. }
  428. }
  429. ```
  430. "dGVuZGVybWludA==" and "cm9ja3M=" are the base64-encoding of the ASCII of
  431. "tendermint" and "rocks" accordingly.
  432. ## Outro
  433. I hope everything went smoothly and your first, but hopefully not the last,
  434. Tendermint Core application is up and running. If not, please [open an issue on
  435. Github](https://github.com/tendermint/tendermint/issues/new/choose). To dig
  436. deeper, read [the docs](https://docs.tendermint.com/master/).