tie-core

README

Get started

Installation

Install Go

Download

wget https://go.dev/dl/go1.17.10.linux-amd64.tar.gz
rm -rf /usr/local/go
tar zxvf go1.17.10.linux-amd64.tar.gz -C /usr/local/go

Environment variable

vim /etc/profile

export GOROOT=/usr/local/go
export GOPATH=/home/golang
export GOBIN=/home/golang/bin
export PATH=$PATH:$GOROOT/bin:$GOBIN

source /etc/profile

Generate

Building tie from source

git clone git@github.com:TIE-Tech/tie-core.git
cd tie-core/
go build -o tie
mv tie /usr/local/bin

Initialize data folders and generate validator keys

tie secrets init --data-dir chain-data-1
tie secrets init --data-dir chain-data-2
tie secrets init --data-dir chain-data-3
tie secrets init --data-dir chain-data-4

Generate genesis.json

tie genesis --consensus ibft --pos --chainid 99 \
--ibft-validator 0xEC5e0Eb4eceDbB59022db98632b91243EeA742f9 \
--ibft-validator 0xaECf74F9Aa6d1d79a2fa540af968Db788Ecb19e0 \
--ibft-validator 0x9EbEdCe6eb4B6fC7f18521E135324883ba093b17 \
--ibft-validator 0x104Af911E6CBb54533C78954aea505b2Db4d4b82 \
--bootnode /ip4/192.168.10.1/tcp/5525/p2p/16Uiu2HAmLGnKBqBSh8ZabRRJuyXHcQ195T827MmhzxPFnjyBipJg \
--bootnode /ip4/192.168.10.2/tcp/5525/p2p/16Uiu2HAmVh13FGoGyYb5csECTEqCEwvdtqQrPeskqAPnfcmoT2s6 \
--bootnode /ip4/192.168.10.3/tcp/5525/p2p/16Uiu2HAmHexGQUcFspid6bkEAdFvxcj4DCc5xG9XsX2R58fXx132 \
--bootnode /ip4/192.168.10.4/tcp/5525/p2p/16Uiu2HAkvaa9wAU1Xz76TkWe7x8QH53UmnVMiVfsabKHfoKJXnGh \
--premine 0x5573143eBA235545BE5548E1107dD7B92713EF18:100000000000000000000000

Deploy with docker

Building tie images

git clone git@github.com:TIE-Tech/tie-core.git
cd tie-core/
docker build . -t tie:v1.0

Building node images

• start.sh

mkdir images && cd images
vim bin/start.sh

#!/bin/bash
tie server --data-dir ./chain-data --chain genesis.json --network=host --seal

• Dockerfile

FROM tie:v1.0

RUN apk update && apk add bash curl

ADD bin /root/bin

RUN chmod a+x /root/bin/*

ENTRYPOINT /root/bin/start.sh

• building

docker build . -t node:v1.0

• mount directory

mkdir -p project/test-chain project/logs

Run Server

docker run --name chain -v project/:/data --netword=host -d node1:v1.0
docker logs -f chain

CLI Commands

tie command

• secrets
  Top level SecretsManager command for interacting with secrets functionality.

• genesis
  Generates the genesis.json file, with passed in parameters.

• server
  The default command that starts the Tie client, by bootstrapping all modules together.

• status
  Returns the status of the Tie client.

• txpool
  Top level command for interacting with the transaction pool.

• peers
  Top level command for interacting with the network peers.

• monitor
  Starts logging block add / remove events on the blockchain.

• version
  Returns the current version.

genesis command

• --consensus
  Sets consensus protocol. Default: pvbft.

• --bootnode
  Multiaddr URL for p2p discovery bootstrap. This flag can be used multiple times.

• --ibft-validator
  Sets passed in addresses as BFT validators. Needs to be present if ibft-validators-prefix-path is omitted.

• --epoch-size
  Sets the epoch size for the chain. Default 129600

• --pos
  Sets the flag indicating that the client should use Proof of Stake IBFT.

• --dir
  Sets the directory for the TIE genesis data. Default: ./genesis.json.

• --name
  Sets the name for the chain. Default: tie.

• --ibft-validators-prefix-path
  Prefix path for validator folder directory. Needs to be present if ibft-validator is omitted.

• --block-gas-limit
  Set block gas limit

• --premine
  Sets the premined accounts and balances. Default premined balance: 0x4546c07635c1fc494600000

• --chainid
  Sets the ID of the chain. Default: 100

server command

• --log-path LOG_PATH
  Sets the log path for console output. Default: logs/tiechain.log.

• ---grpc GRPC_ADDRESS
  Sets the address and port for the gRPC service (address:port). Default: :7749.

• --libp2p LIBP2P_ADDRESS
  Sets the address and port for the libp2p service (address:port). Default: 6636.

• --jsonrpc JSONRPC_ADDRESS
  Sets the address and port for the JSON-RPC service (address:port). Default: 8545.

• --no-discover NO_DISCOVER
  Prevents the client from discovering other peers. Default: false.

• --price-limit PRICE_LIMIT
  Sets minimum gas price limit to enforce for acceptance into the pool. Default: 0.

• --prometheus PROMETHEUS_ADDRESS
  Sets the address and port for the prometheus instrumentation service (address:port).

• --data-dir DATA_DIRECTORY
  Specifies the data directory used for storing TIE client data. Default: ./test-chain.

• --log-level LOG_LEVEL
  Sets the log level for console output. Default: INFO.

• --seal SHOULD_SEAL
  Sets the flag indicating that the client should seal blocks. Default: false.

• --config CLI_CONFIG_PATH
  Specifies the path to the CLI config. Supports .json and .hcl.

• --chain GENESIS_FILE
  Specifies the genesis file used for starting the chain. Default: test.

• --secrets-config SECRETS_CONFIG
  Sets the path to the SecretsManager config file. Used for Hashicorp Vault. If omitted, the local FS secrets manager is used.

• --block-time BLOCK_TIME
  Sets block time in seconds. Default: 2s.

• --block-gas-target BLOCK_GAS_TARGET
  Sets the target block gas limit for the chain. If omitted, the value of the parent block is used.

• --max-peers PEER_COUNT
  Sets the client's max no.of peers allowded. Default: 21.

• --max-slots MAX_SLOTS
  Sets maximum slots in the pool. Default: 4096.

• --es-open ES_OPEN
  Set elastic log switch

• --es-addr ES_ADDR
  Set elastic connection address, No "/" at the end

• --es-index ES_INDEX
  Set elastic index

• --es-owner ES_OWNER
  Set elastic log service name

JSON RPC Commands

• Hash List
• JSON-RPC support
• HEX value encoding
• The default block parameter
• Curl Examples Explained
• JSON-RPC methods

Hash List

| 类型 | 长度 | 描述 | |-------|:------------:|:-----------:|:-----------:| | blockHash | String | 0x+64位 | 区块的哈希 | | blockNumber | Number | | 区块的块号 | | transactionHash | String | 0x+64位 | 交易的哈希值 | | transactionIndex | Number | | 交易在区块里面的序号，整数 | | client addresses | String | 0x+40位 | 账户地址 | | gas | Number | | 工作量单位 | | contractAddress | String | 0x+40位 | 合约地址 |

HEX value encoding

At present there are two key datatypes that are passed over JSON: unformatted byte arrays and quantities. Both are passed with a hex encoding, however with different requirements to formatting:

When encoding QUANTITIES (integers, numbers): encode as hex, prefix with "0x", the most compact representation (slight exception: zero should be represented as "0x0"). Examples:

• 0x41 (65 in decimal)
• 0x400 (1024 in decimal)
• WRONG: 0x (should always have at least one digit - zero is "0x0")
• WRONG: 0x0400 (no leading zeroes allowed)
• WRONG: ff (must be prefixed 0x)

When encoding UNFORMATTED DATA (byte arrays, account addresses, hashes, bytecode arrays): encode as hex, prefix with "0x", two hex digits per byte. Examples:

• 0x41 (size 1, "A")
• 0x004200 (size 3, "\0B\0")
• 0x (size 0, "")
• WRONG: 0xf0f0f (must be even number of digits)
• WRONG: 004200 (must be prefixed 0x)

The default block parameter

The following methods have an extra default block parameter:

• eth_getBalance
• eth_getCode
• eth_getTransactionCount
• eth_getStorageAt
• eth_call

When requests are made that act on the state of ethereum, the last default block parameter determines the height of the block.

The following options are possible for the defaultBlock parameter:

• HEX String - an integer block number
• String "earliest" for the earliest/genesis block
• String "latest" - for the latest mined block
• String "pending" - for the pending state/transactions

Curl Examples Explained

The curl options below might return a response where the node complains about the content type, this is because the --data option sets the content type to application/x-www-form-urlencoded . If your node does complain, manually set the header by placing -H "Content-Type: application/json" at the start of the call.

The examples also do not include the URL/IP & port combination which must be the last argument given to curl e.x. 127.0.0.1:8545

JSON-RPC methods

• web3_clientVersion 当前客户端版本
• web3_sha3 给定字符串的sha3结果
• net_version 当前的网络ID
• net_peerCount 客户端数量
• net_listening 客户端连接状态
• eth_syncing 当前同步情况
• eth_hashrate 每秒节点挖掘数量
• eth_gasPrice 当前gas价格
• eth_blockNumber 客户端当前区块号
• eth_getBalance 当前余额
• eth_getStorageAt 存储位置的值
• eth_getTransactionCount 账户地址的交易数量
• eth_getBlockTransactionCountByHash 区块哈希值的交易数量
• eth_getBlockTransactionCountByNumber 区块号的交易数量
• eth_getUncleCountByBlockHash 通过区块哈希值获取叔块
• eth_getUncleCountByBlockNumber 通过区块号获取叔块
• eth_getCode 获取链上指定地址的代码
• eth_sign 账户数据加签
• eth_sendTransaction 发送一个交易到合约
• eth_sendRawTransaction 发送加签的交易
• eth_call
• eth_estimateGas 合约部署所花费的gas
• eth_getBlockByHash 区块哈希值所对应的区块
• eth_getBlockByNumber 区块号所对应的区块
• eth_getTransactionByHash 交易哈希值查交易信息
• eth_getTransactionByBlockHashAndIndex 区块哈希值的指定序号的交易
• eth_getTransactionByBlockNumberAndIndex 区块号的指定序号的交易
• eth_getTransactionReceipt 智能合约记录查询
• eth_getUncleByBlockHashAndIndex 区块哈希值返回叔块
• eth_getUncleByBlockNumberAndIndex 区块号返回叔块
• eth_getCompilers 可用合约编译器
• eth_compileLLL 编译LLL源代码
• eth_compileSolidity 编译智能合约
• eth_compileSerpent 编译serpent源代码
• eth_newFilter 创建一个filter对象监听区块或交易的变化
• eth_newBlockFilter 创建一个filter监听新区块的创建
• eth_newPendingTransactionFilter 创建一个filter监听发起一个交易
• eth_uninstallFilter 取消指定filter
• eth_getFilterChanges 获取filter的变化日志
• eth_getFilterLogs 获取指定filter日志
• eth_getLogs 返回所有日志
• eth_getWork 挖矿应用程序
• eth_submitWork 守护进程通信
• eth_submitHashrate 提交挖矿率哈希值
• db_putString 写入字符串到数据库
• db_getString 在数据库读取字符串
• db_putHex 写入十六进制到数据库
• db_getHex 在数据库读取十六进制
• shh_post
• shh_version
• shh_newIdentity
• shh_hasIdentity
• shh_newGroup
• shh_addToGroup
• shh_newFilter
• shh_uninstallFilter
• shh_getFilterChanges
• shh_getMessages

JSON RPC API Reference

---

web3_clientVersion

Returns the current client version.

Parameters

none

Returns

String - The current client version

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"web3_clientVersion","params":[],"id":67}'

// Result
{
  "id":67,
  "jsonrpc":"2.0",
  "result": "tie [v1.0.0]"
}

---

web3_sha3

Returns Keccak-256 (not the standardized SHA3-256) of the given data.

Parameters

1. DATA - the data to convert into a SHA3 hash

params: [
  "0xbF7EB735d14d241Bd82133074Bbcc983Ef838792"
]

Returns

DATA - The SHA3 result of the given string.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"web3_sha3","params":["0xbF7EB735d14d241Bd82133074Bbcc983Ef838792"],"id":64}'

// Result
{
  "id":64,
  "jsonrpc": "2.0",
  "result": "0x47173285a8d7341e5e972fc677286384f802f8ef42a5ec5f03bbfa254cb01fad"
}

---

net_version

Returns the current network id.

Parameters

none

Returns

String - The current network id.

• "1": Ethereum Mainnet
• "2": Morden Testnet (deprecated)
• "3": Ropsten Testnet
• "4": Rinkeby Testnet
• "42": Kovan Testnet

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":67}'

// Result
{
  "id":67,
  "jsonrpc": "2.0",
  "result": "200"
}

---

net_listening

Returns true if client is actively listening for network connections.

Parameters

none

Returns

Boolean - true when listening, otherwise false.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"net_listening","params":[],"id":67}'

// Result
{
  "id":67,
  "jsonrpc":"2.0",
  "result":true
}

---

net_peerCount

Returns number of peers currently connected to the client.

Parameters

none

Returns

QUANTITY - integer of the number of connected peers.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"net_peerCount","params":[],"id":74}'

// Result
{
  "id":74,
  "jsonrpc": "2.0",
  "result": "2"
}

---

eth_syncing

Returns an object with data about the sync status or false.

Parameters

none

Returns

Object|Boolean, An object with sync status data or FALSE, when not syncing:

• startingBlock: QUANTITY - The block at which the import started (will only be reset, after the sync reached his head)
• currentBlock: QUANTITY - The current block, same as eth_blockNumber
• highestBlock: QUANTITY - The estimated highest block

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": {
    startingBlock: '0x384',
    currentBlock: '0x386',
    highestBlock: '0x454'
  }
}
// Or when not syncing
{
  "id":1,
  "jsonrpc": "2.0",
  "result": false
}

---

eth_gasPrice

Returns the current price per gas in wei.

Parameters

none

Returns

QUANTITY - integer of the current gas price in wei.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_gasPrice","params":[],"id":73}'

// Result
{
  "id":73,
  "jsonrpc": "2.0",
  "result": "0x09184e72a000" // 10000000000000
}

---

eth_blockNumber

Returns the number of most recent block.

Parameters

none

Returns

QUANTITY - integer of the current block number the client is on.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":83}'

// Result
{
  "id":83,
  "jsonrpc": "2.0",
  "result": "0x4b7" // 1207
}

---

eth_getBalance

Returns the balance of the account of given address.

Parameters

1. DATA, 20 Bytes - address to check for balance.
2. QUANTITY|TAG - integer block number, or the string "latest", "earliest" or "pending", see the default block parameter

params: [
   '0x407d73d8a49eeb85d32cf465507dd71d507100c1',
   'latest'
]

Returns

QUANTITY - integer of the current balance in wei.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBalance","params":["0x407d73d8a49eeb85d32cf465507dd71d507100c1", "latest"],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x0234c8a3397aab58" // 158972490234375000
}

---

eth_getStorageAt

Returns the value from a storage position at a given address.

Parameters

1. DATA, 20 Bytes - address of the storage.
2. QUANTITY - integer of the position in the storage.
3. QUANTITY|TAG - integer block number, or the string "latest", "earliest" or "pending", see the default block parameter

Returns

DATA - the value at this storage position.

Example

Calculating the correct position depends on the storage to retrieve. Consider the following contract deployed at 0x295a70b2de5e3953354a6a8344e616ed314d7251 by address 0x391694e7e0b0cce554cb130d723a9d27458f9298.

contract Storage {
    uint pos0;
    mapping(address => uint) pos1;
    
    function Storage() {
        pos0 = 1234;
        pos1[msg.sender] = 5678;
    }
}

Retrieving the value of pos0 is straight forward:

curl -X POST --data '{"jsonrpc":"2.0", "method": "eth_getStorageAt", "params": ["0x295a70b2de5e3953354a6a8344e616ed314d7251", "0x0", "latest"], "id": 1}' localhost:8545

{"jsonrpc":"2.0","id":1,"result":"0x00000000000000000000000000000000000000000000000000000000000004d2"}

Retrieving an element of the map is harder. The position of an element in the map is calculated with:

keccack(LeftPad32(key, 0), LeftPad32(map position, 0))

This means to retrieve the storage on pos1["0x391694e7e0b0cce554cb130d723a9d27458f9298"] we need to calculate the position with:

keccak(decodeHex("000000000000000000000000391694e7e0b0cce554cb130d723a9d27458f9298" + "0000000000000000000000000000000000000000000000000000000000000001"))

The geth console which comes with the web3 library can be used to make the calculation:

> var key = "000000000000000000000000391694e7e0b0cce554cb130d723a9d27458f9298" + "0000000000000000000000000000000000000000000000000000000000000001"
undefined
> web3.sha3(key, {"encoding": "hex"})
"0x6661e9d6d8b923d5bbaab1b96e1dd51ff6ea2a93520fdc9eb75d059238b8c5e9"

Now to fetch the storage:

curl -X POST --data '{"jsonrpc":"2.0", "method": "eth_getStorageAt", "params": ["0x295a70b2de5e3953354a6a8344e616ed314d7251", "0x6661e9d6d8b923d5bbaab1b96e1dd51ff6ea2a93520fdc9eb75d059238b8c5e9", "latest"], "id": 1}' localhost:8545

{"jsonrpc":"2.0","id":1,"result":"0x000000000000000000000000000000000000000000000000000000000000162e"}

---

eth_getTransactionCount

Returns the number of transactions sent from an address.

Parameters

1. DATA, 20 Bytes - address.
2. QUANTITY|TAG - integer block number, or the string "latest", "earliest" or "pending", see the default block parameter

params: [
   '0x407d73d8a49eeb85d32cf465507dd71d507100c1',
   'latest' // state at the latest block
]

Returns

QUANTITY - integer of the number of transactions send from this address.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionCount","params":["0x407d73d8a49eeb85d32cf465507dd71d507100c1","latest"],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x1" // 1
}

---

eth_getBlockTransactionCountByHash

Returns the number of transactions in a block from a block matching the given block hash.

Parameters

1. DATA, 32 Bytes - hash of a block

params: [
   '0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238'
]

Returns

QUANTITY - integer of the number of transactions in this block.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockTransactionCountByHash","params":["0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0xb" // 11
}

---

eth_getBlockTransactionCountByNumber

Returns the number of transactions in a block matching the given block number.

Parameters

1. QUANTITY|TAG - integer of a block number, or the string "earliest", "latest" or "pending", as in the default block parameter.

params: [
   '0xe8', // 232
]

Returns

QUANTITY - integer of the number of transactions in this block.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockTransactionCountByNumber","params":["0xe8"],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0xa" // 10
}

---

eth_getUncleCountByBlockHash

Returns the number of uncles in a block from a block matching the given block hash.

Parameters

1. DATA, 32 Bytes - hash of a block

params: [
   '0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238'
]

Returns

QUANTITY - integer of the number of uncles in this block.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getUncleCountByBlockHash","params":["0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x1" // 1
}

---

eth_getUncleCountByBlockNumber

Returns the number of uncles in a block from a block matching the given block number.

Parameters

1. QUANTITY|TAG - integer of a block number, or the string "latest", "earliest" or "pending", see the default block parameter

params: [
   '0xe8', // 232
]

Returns

QUANTITY - integer of the number of uncles in this block.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getUncleCountByBlockNumber","params":["0xe8"],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x1" // 1
}

---

eth_getCode

Returns code at a given address.

Parameters

1. DATA, 20 Bytes - address
2. QUANTITY|TAG - integer block number, or the string "latest", "earliest" or "pending", see the default block parameter

params: [
   '0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b',
   '0x2'  // 2
]

Returns

DATA - the code from the given address.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getCode","params":["0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b", "0x2"],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x600160008035811a818181146012578301005b601b6001356025565b8060005260206000f25b600060078202905091905056"
}

---

eth_sign

The sign method calculates an Ethereum specific signature with: sign(keccak256("\x19Ethereum Signed Message:\n" + len(message) + message))).

By adding a prefix to the message makes the calculated signature recognisable as an Ethereum specific signature. This prevents misuse where a malicious DApp can sign arbitrary data (e.g. transaction) and use the signature to impersonate the victim.

Note the address to sign with must be unlocked.

Parameters

account, message

1. DATA, 20 Bytes - address
2. DATA, N Bytes - message to sign

Returns

DATA: Signature

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sign","params":["0x9b2055d370f73ec7d8a03e965129118dc8f5bf83", "0xdeadbeaf"],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0xa3f20717a250c2b0b729b7e5becbff67fdaef7e0699da4de7ca5895b02a170a12d887fd3b17bfdce3481f10bea41f45ba9f709d39ce8325427b57afcfc994cee1b"
}

An example how to use solidity ecrecover to verify the signature calculated with eth_sign can be found here. The contract is deployed on the testnet Ropsten and Rinkeby.

---

eth_sendTransaction

Creates new message call transaction or a contract creation, if the data field contains code.

Parameters

1. Object - The transaction object

• from: DATA, 20 Bytes - The address the transaction is send from.
• to: DATA, 20 Bytes - (optional when creating new contract) The address the transaction is directed to.
• gas: QUANTITY - (optional, default: 90000) Integer of the gas provided for the transaction execution. It will return unused gas.
• gasPrice: QUANTITY - (optional, default: To-Be-Determined) Integer of the gasPrice used for each paid gas
• value: QUANTITY - (optional) Integer of the value sent with this transaction
• data: DATA - The compiled code of a contract OR the hash of the invoked method signature and encoded parameters. For details see Ethereum Contract ABI
• nonce: QUANTITY - (optional) Integer of a nonce. This allows to overwrite your own pending transactions that use the same nonce.

params: [{
  "from": "0xb60e8dd61c5d32be8058bb8eb970870f07233155",
  "to": "0xd46e8dd67c5d32be8058bb8eb970870f07244567",
  "gas": "0x76c0", // 30400
  "gasPrice": "0x9184e72a000", // 10000000000000
  "value": "0x9184e72a", // 2441406250
  "data": "0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f072445675"
}]

Returns

DATA, 32 Bytes - the transaction hash, or the zero hash if the transaction is not yet available.

Use eth_getTransactionReceipt to get the contract address, after the transaction was mined, when you created a contract.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sendTransaction","params":[{see above}],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"
}

---

eth_sendRawTransaction

Creates new message call transaction or a contract creation for signed transactions.

Parameters

1. DATA, The signed transaction data.

params: ["0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f072445675"]

Returns

DATA, 32 Bytes - the transaction hash, or the zero hash if the transaction is not yet available.

Use eth_getTransactionReceipt to get the contract address, after the transaction was mined, when you created a contract.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sendRawTransaction","params":[{see above}],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"
}

---

eth_call

Executes a new message call immediately without creating a transaction on the block chain.

Parameters

1. Object - The transaction call object

• from: DATA, 20 Bytes - (optional) The address the transaction is sent from.
• to: DATA, 20 Bytes - The address the transaction is directed to.
• gas: QUANTITY - (optional) Integer of the gas provided for the transaction execution. eth_call consumes zero gas, but this parameter may be needed by some executions.
• gasPrice: QUANTITY - (optional) Integer of the gasPrice used for each paid gas
• value: QUANTITY - (optional) Integer of the value sent with this transaction
• data: DATA - (optional) Hash of the method signature and encoded parameters. For details see Ethereum Contract ABI

1. QUANTITY|TAG - integer block number, or the string "latest", "earliest" or "pending", see the default block parameter

Returns

DATA - the return value of executed contract.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_call","params":[{see above}],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x"
}

---

eth_estimateGas

Generates and returns an estimate of how much gas is necessary to allow the transaction to complete. The transaction will not be added to the blockchain. Note that the estimate may be significantly more than the amount of gas actually used by the transaction, for a variety of reasons including EVM mechanics and node performance.

Parameters

See eth_call parameters, expect that all properties are optional. If no gas limit is specified geth uses the block gas limit from the pending block as an upper bound. As a result the returned estimate might not be enough to executed the call/transaction when the amount of gas is higher than the pending block gas limit.

Returns

QUANTITY - the amount of gas used.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_estimateGas","params":[{see above}],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x5208" // 21000
}

---

eth_getBlockByHash

Returns information about a block by hash.

Parameters

1. DATA, 32 Bytes - Hash of a block.
2. Boolean - If true it returns the full transaction objects, if false only the hashes of the transactions.

params: [
   '0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331',
   true
]

Returns

Object - A block object, or null when no block was found:

• number: QUANTITY - the block number. null when its pending block.
• hash: DATA, 32 Bytes - hash of the block. null when its pending block.
• parentHash: DATA, 32 Bytes - hash of the parent block.
• nonce: DATA, 8 Bytes - hash of the generated proof-of-work. null when its pending block.
• sha3Uncles: DATA, 32 Bytes - SHA3 of the uncles data in the block.
• logsBloom: DATA, 256 Bytes - the bloom filter for the logs of the block. null when its pending block.
• transactionsRoot: DATA, 32 Bytes - the root of the transaction trie of the block.
• stateRoot: DATA, 32 Bytes - the root of the final state trie of the block.
• receiptsRoot: DATA, 32 Bytes - the root of the receipts trie of the block.
• miner: DATA, 20 Bytes - the address of the beneficiary to whom the mining rewards were given.
• difficulty: QUANTITY - integer of the difficulty for this block.
• totalDifficulty: QUANTITY - integer of the total difficulty of the chain until this block.
• extraData: DATA - the "extra data" field of this block.
• size: QUANTITY - integer the size of this block in bytes.
• gasLimit: QUANTITY - the maximum gas allowed in this block.
• gasUsed: QUANTITY - the total used gas by all transactions in this block.
• timestamp: QUANTITY - the unix timestamp for when the block was collated.
• transactions: Array - Array of transaction objects, or 32 Bytes transaction hashes depending on the last given parameter.
• uncles: Array - Array of uncle hashes.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockByHash","params":["0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331", true],"id":1}'

// Result
{
"id":1,
"jsonrpc":"2.0",
"result": {
    "number": "0x1b4", // 436
    "hash": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331",
    "parentHash": "0x9646252be9520f6e71339a8df9c55e4d7619deeb018d2a3f2d21fc165dde5eb5",
    "nonce": "0xe04d296d2460cfb8472af2c5fd05b5a214109c25688d3704aed5484f9a7792f2",
    "sha3Uncles": "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",
    "logsBloom": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331",
    "transactionsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
    "stateRoot": "0xd5855eb08b3387c0af375e9cdb6acfc05eb8f519e419b874b6ff2ffda7ed1dff",
    "miner": "0x4e65fda2159562a496f9f3522f89122a3088497a",
    "difficulty": "0x027f07", // 163591
    "totalDifficulty":  "0x027f07", // 163591
    "extraData": "0x0000000000000000000000000000000000000000000000000000000000000000",
    "size":  "0x027f07", // 163591
    "gasLimit": "0x9f759", // 653145
    "gasUsed": "0x9f759", // 653145
    "timestamp": "0x54e34e8e" // 1424182926
    "transactions": [{...},{ ... }] 
    "uncles": ["0x1606e5...", "0xd5145a9..."]
  }
}

---

eth_getBlockByNumber

Returns information about a block by block number.

Parameters

1. QUANTITY|TAG - integer of a block number, or the string "earliest", "latest" or "pending", as in the default block parameter.
2. Boolean - If true it returns the full transaction objects, if false only the hashes of the transactions.

params: [
   '0x1b4', // 436
   true
]

Returns

See eth_getBlockByHash

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["0x1b4", true],"id":1}'

Result see eth_getBlockByHash

---

eth_getTransactionByHash

Returns the information about a transaction requested by transaction hash.

Parameters

1. DATA, 32 Bytes - hash of a transaction

params: [
   "0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"
]

Returns

Object - A transaction object, or null when no transaction was found:

• hash: DATA, 32 Bytes - hash of the transaction.
• nonce: QUANTITY - the number of transactions made by the sender prior to this one.
• blockHash: DATA, 32 Bytes - hash of the block where this transaction was in. null when its pending.
• blockNumber: QUANTITY - block number where this transaction was in. null when its pending.
• transactionIndex: QUANTITY - integer of the transactions index position in the block. null when its pending.
• from: DATA, 20 Bytes - address of the sender.
• to: DATA, 20 Bytes - address of the receiver. null when its a contract creation transaction.
• value: QUANTITY - value transferred in Wei.
• gasPrice: QUANTITY - gas price provided by the sender in Wei.
• gas: QUANTITY - gas provided by the sender.
• input: DATA - the data send along with the transaction.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionByHash","params":["0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"],"id":1}'

// Result
{
"id":1,
"jsonrpc":"2.0",
"result": {
    "hash":"0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b",
    "nonce":"0x",
    "blockHash": "0xbeab0aa2411b7ab17f30a99d3cb9c6ef2fc5426d6ad6fd9e2a26a6aed1d1055b",
    "blockNumber": "0x15df", // 5599
    "transactionIndex":  "0x1", // 1
    "from":"0x407d73d8a49eeb85d32cf465507dd71d507100c1",
    "to":"0x85h43d8a49eeb85d32cf465507dd71d507100c1",
    "value":"0x7f110", // 520464
    "gas": "0x7f110", // 520464
    "gasPrice":"0x09184e72a000",
    "input":"0x603880600c6000396000f300603880600c6000396000f3603880600c6000396000f360",
  }
}

---

eth_getTransactionByBlockHashAndIndex

Returns information about a transaction by block hash and transaction index position.

Parameters

1. DATA, 32 Bytes - hash of a block.
2. QUANTITY - integer of the transaction index position.

params: [
   '0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331',
   '0x0' // 0
]

Returns

See eth_getTransactionByHash

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionByBlockHashAndIndex","params":["0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b", "0x0"],"id":1}'

Result see eth_getTransactionByHash

---

eth_getTransactionByBlockNumberAndIndex

Returns information about a transaction by block number and transaction index position.

Parameters

1. QUANTITY|TAG - a block number, or the string "earliest", "latest" or "pending", as in the default block parameter.
2. QUANTITY - the transaction index position.

params: [
   '0x29c', // 668
   '0x0' // 0
]

Returns

See eth_getTransactionByHash

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionByBlockNumberAndIndex","params":["0x29c", "0x0"],"id":1}'

Result see eth_getTransactionByHash

---

eth_getTransactionReceipt

Returns the receipt of a transaction by transaction hash.

Note That the receipt is not available for pending transactions.

Parameters

1. DATA, 32 Bytes - hash of a transaction

params: [
   '0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238'
]

Returns

Object - A transaction receipt object, or null when no receipt was found:

• transactionHash : DATA, 32 Bytes - hash of the transaction.
• transactionIndex: QUANTITY - integer of the transactions index position in the block.
• blockHash: DATA, 32 Bytes - hash of the block where this transaction was in.
• blockNumber: QUANTITY - block number where this transaction was in.
• from: DATA, 20 Bytes - address of the sender.
• to: DATA, 20 Bytes - address of the receiver. null when its a contract creation transaction.
• cumulativeGasUsed : QUANTITY - The total amount of gas used when this transaction was executed in the block.
• gasUsed : QUANTITY - The amount of gas used by this specific transaction alone.
• contractAddress : DATA, 20 Bytes - The contract address created, if the transaction was a contract creation, otherwise null.
• logs: Array - Array of log objects, which this transaction generated.
• logsBloom: DATA, 256 Bytes - Bloom filter for light clients to quickly retrieve related logs.

It also returns either :

• root : DATA 32 bytes of post-transaction stateroot (pre Byzantium)
• status: QUANTITY either 1 (success) or 0 (failure)

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionReceipt","params":["0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238"],"id":1}'

// Result
{
"id":1,
"jsonrpc":"2.0",
"result": {
     transactionHash: '0xb903239f8543d04b5dc1ba6579132b143087c68db1b2168786408fcbce568238',
     transactionIndex:  '0x1', // 1
     blockNumber: '0xb', // 11
     blockHash: '0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b',
     cumulativeGasUsed: '0x33bc', // 13244
     gasUsed: '0x4dc', // 1244
     contractAddress: '0xb60e8dd61c5d32be8058bb8eb970870f07233155', // or null, if none was created
     logs: [{
         // logs as returned by getFilterLogs, etc.
     }, ...],
     logsBloom: "0x00...0", // 256 byte bloom filter
     status: '0x1'
  }
}

---

eth_getUncleByBlockHashAndIndex

Returns information about a uncle of a block by hash and uncle index position.

Parameters

1. DATA, 32 Bytes - hash a block.
2. QUANTITY - the uncle's index position.

params: [
   '0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b',
   '0x0' // 0
]

Returns

See eth_getBlockByHash

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getUncleByBlockHashAndIndex","params":["0xc6ef2fc5426d6ad6fd9e2a26abeab0aa2411b7ab17f30a99d3cb96aed1d1055b", "0x0"],"id":1}'

Result see eth_getBlockByHash

Note: An uncle doesn't contain individual transactions.

---

eth_getUncleByBlockNumberAndIndex

Returns information about a uncle of a block by number and uncle index position.

Parameters

1. QUANTITY|TAG - a block number, or the string "earliest", "latest" or "pending", as in the default block parameter.
2. QUANTITY - the uncle's index position.

params: [
   '0x29c', // 668
   '0x0' // 0
]

Returns

See eth_getBlockByHash

Note: An uncle doesn't contain individual transactions.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getUncleByBlockNumberAndIndex","params":["0x29c", "0x0"],"id":1}'

Result see eth_getBlockByHash

---

eth_getCompilers

Returns a list of available compilers in the client.

Parameters

none

Returns

Array - Array of available compilers.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getCompilers","params":[],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": ["solidity", "lll", "serpent"]
}

---

eth_compileSolidity

Returns compiled solidity code.

Parameters

1. String - The source code.

params: [
   "contract test { function multiply(uint a) returns(uint d) {   return a * 7;   } }",
]

Returns

DATA - The compiled source code.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_compileSolidity","params":["contract test { function multiply(uint a) returns(uint d) {   return a * 7;   } }"],"id":1}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": {
      "code": "0x605880600c6000396000f3006000357c010000000000000000000000000000000000000000000000000000000090048063c6888fa114602e57005b603d6004803590602001506047565b8060005260206000f35b60006007820290506053565b91905056",
      "info": {
        "source": "contract test {\n   function multiply(uint a) constant returns(uint d) {\n       return a * 7;\n   }\n}\n",
        "language": "Solidity",
        "languageVersion": "0",
        "compilerVersion": "0.9.19",
        "abiDefinition": [
          {
            "constant": true,
            "inputs": [
              {
                "name": "a",
                "type": "uint256"
              }
            ],
            "name": "multiply",
            "outputs": [
              {
                "name": "d",
                "type": "uint256"
              }
            ],
            "type": "function"
          }
        ],
        "userDoc": {
          "methods": {}
        },
        "developerDoc": {
          "methods": {}
        }
      }

}

---

eth_newFilter

Creates a filter object, based on filter options, to notify when the state changes (logs). To check if the state has changed, call eth_getFilterChanges.

A note on specifying topic filters:

Topics are order-dependent. A transaction with a log with topics [A, B] will be matched by the following topic filters:

• [] "anything"
• [A] "A in first position (and anything after)"
• [null, B] "anything in first position AND B in second position (and anything after)"
• [A, B] "A in first position AND B in second position (and anything after)"
• [[A, B], [A, B]] "(A OR B) in first position AND (A OR B) in second position (and anything after)"

Parameters

1. Object - The filter options:

• fromBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.
• toBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.
• address: DATA|Array, 20 Bytes - (optional) Contract address or a list of addresses from which logs should originate.
• topics: Array of DATA, - (optional) Array of 32 Bytes DATA topics. Topics are order-dependent. Each topic can also be an array of DATA with "or" options.

params: [{
  "fromBlock": "0x1",
  "toBlock": "0x2",
  "address": "0x8888f1f195afa192cfee860698584c030f4c9db1",
  "topics": ["0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b", null, ["0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b", "0x0000000000000000000000000aff3454fce5edbc8cca8697c15331677e6ebccc"]]
}]

Returns

QUANTITY - A filter id.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_newFilter","params":[{"topics":["0x12341234"]}],"id":73}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x1" // 1
}

---

eth_newBlockFilter

Creates a filter in the node, to notify when a new block arrives. To check if the state has changed, call eth_getFilterChanges.

Parameters

None

Returns

QUANTITY - A filter id.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_newBlockFilter","params":[],"id":73}'

// Result
{
  "id":1,
  "jsonrpc":  "2.0",
  "result": "0x1" // 1
}

---

eth_newPendingTransactionFilter

Creates a filter in the node, to notify when new pending transactions arrive. To check if the state has changed, call eth_getFilterChanges.

Parameters

None

Returns

QUANTITY - A filter id.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_newPendingTransactionFilter","params":[],"id":73}'

// Result
{
  "id":1,
  "jsonrpc":  "2.0",
  "result": "0x1" // 1
}

---

eth_uninstallFilter

Uninstalls a filter with given id. Should always be called when watch is no longer needed. Additonally Filters timeout when they aren't requested with eth_getFilterChanges for a period of time.

Parameters

1. QUANTITY - The filter id.

params: [
  "0xb" // 11
]

Returns

Boolean - true if the filter was successfully uninstalled, otherwise false.

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_uninstallFilter","params":["0xb"],"id":73}'

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": true
}

---

eth_getFilterChanges

Polling method for a filter, which returns an array of logs which occurred since last poll.

Parameters

1. QUANTITY - the filter id.

params: [
  "0x16" // 22
]

Returns

Array - Array of log objects, or an empty array if nothing has changed since last poll.

• For filters created with eth_newBlockFilter the return are block hashes (DATA, 32 Bytes), e.g. ["0x3454645634534..."].

• For filters created with eth_newPendingTransactionFilter the return are transaction hashes (DATA, 32 Bytes), e.g. ["0x6345343454645..."].

• For filters created with eth_newFilter logs are objects with following params:

  • removed: TAG - true when the log was removed, due to a chain reorganization. false if its a valid log.
  • logIndex: QUANTITY - integer of the log index position in the block. null when its pending log.
  • transactionIndex: QUANTITY - integer of the transactions index position log was created from. null when its pending log.
  • transactionHash: DATA, 32 Bytes - hash of the transactions this log was created from. null when its pending log.
  • blockHash: DATA, 32 Bytes - hash of the block where this log was in. null when its pending. null when its pending log.
  • blockNumber: QUANTITY - the block number where this log was in. null when its pending. null when its pending log.
  • address: DATA, 20 Bytes - address from which this log originated.
  • data: DATA - contains one or more 32 Bytes non-indexed arguments of the log.
  • topics: Array of DATA - Array of 0 to 4 32 Bytes DATA of indexed log arguments. (In solidity: The first topic is the hash of the signature of the event (e.g. Deposit(address,bytes32,uint256)), except you declared the event with the anonymous specifier.)

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getFilterChanges","params":["0x16"],"id":73}'

// Result
{
  "id":1,
  "jsonrpc":"2.0",
  "result": [{
    "logIndex": "0x1", // 1
    "blockNumber":"0x1b4", // 436
    "blockHash": "0x8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcfdf829c5a142f1fccd7d",
    "transactionHash":  "0xdf829c5a142f1fccd7d8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcf",
    "transactionIndex": "0x0", // 0
    "address": "0x16c5785ac562ff41e2dcfdf829c5a142f1fccd7d",
    "data":"0x0000000000000000000000000000000000000000000000000000000000000000",
    "topics": ["0x59ebeb90bc63057b6515673c3ecf9438e5058bca0f92585014eced636878c9a5"]
    },{
      ...
    }]
}

---

eth_getFilterLogs

Returns an array of all logs matching filter with given id.

Parameters

1. QUANTITY - The filter id.

params: [
  "0x16" // 22
]

Returns

See eth_getFilterChanges

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getFilterLogs","params":["0x16"],"id":74}'

Result see eth_getFilterChanges

---

eth_getLogs

Returns an array of all logs matching a given filter object.

Parameters

1. Object - The filter options:

• fromBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.
• toBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.
• address: DATA|Array, 20 Bytes - (optional) Contract address or a list of addresses from which logs should originate.
• topics: Array of DATA, - (optional) Array of 32 Bytes DATA topics. Topics are order-dependent. Each topic can also be an array of DATA with "or" options.
• blockhash: DATA, 32 Bytes - (optional, future) With the addition of EIP-234, there will be an additional optional field of params named blockHash. This restricts the logs returned to the single block with the 32-byte hash blockHash. Using blockHash is equivalent to fromBlock = toBlock = the block number with hash blockHash. If blockHash is present in params, then neither fromBlock nor toBlock are allowed.

params: [{
  "topics": ["0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b"]
}]

Returns

See eth_getFilterChanges

Example

// Request
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getLogs","params":[{"topics":["0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b"]}],"id":74}'

Result see eth_getFilterChanges

Consensus

PVBFT

Overview

PVBFT（POS+VRF+BFT）混合型共识算法，即拜占庭类POS(BFT style Proof of Stake)。

POS

POS（Proof of Stake），权益证明，通过Staking机制成为验证者。

VRF

	VRF是可验证随机函数(verifiable random function)，一方面具有伪随机性，另一方面它还具有可验证性(输出包括一个非交互零知识证明)。

	TIE节点选择基于VRF可验证随机函数实现，使出块节点具有不可预测随机性，增加安全保护措施，TIE董事会提出给验证者提供固定区块奖励，基于VRF因素，区块生产者随机产生，因此固定奖励随机分配，分配额按周期结算比率基于平均。

BFT

	BFT算法是对PBFT算法进行的改进，除执行共识之外还具备较高的容错机制，设置了状态转换(State Transfer)服务可对发生错误的节点进行修复,重新放入系统,并允许修复完成的节点访问其他节点的状态来获取最新的复制状态。
	同时为避免f个节点同时发生错误,状态转换服务将各节点已执行的操作日志存储在其他磁盘,保证系统出现这样的情况时可稳定地恢复,有效提高了系统的性能效率。
	BFT共识算法将节点分为领导节点(Leader)和副本节点(Backup)两种类型。其摄政(Regency)机制与PBFT算法的视图(View)机制相同。BFTGSmart算法的共识过程分为：
	1.提议(Propose)
	2.写入(Write)
	3.接受(Accept)

Epochs

Epochs 是一个特殊的时间周期，在POS共识中具有重要作用，以区块为单位，TIE决定每EOCH更换一次验证者列表，验证者产生于Staking，并决定每EPOCH进行一次交易手续费奖励结算，奖励额度按Staking比例发放。TIE设定默认EPOCH按72小时一周期，即每129600个区块高度一个周期。
EPOCH值可在创世配置中设定。

Staking

用户可以通过调用质押合约的stake方法进行指定金额质押，并参与到验证者列表，并在下个EPOCH参与到区块生产过程中，调用方式如下：

const StakingContractFactory = await ethers.getContractFactory("Staking");
let stakingContract = await StakingContractFactory.attach(STAKING_CONTRACT_ADDRESS) as Staking;
stakingContract = stakingContract.connect(account);
const tx = await stakingContract.stake({value: STAKE_AMOUNT});

Unstaking

用户可随时对Staking金额进行自主释放，释放后从下一EPOCH开始不在参与区块生产过程。调用方式如下：

const StakingContractFactory = await ethers.getContractFactory("Staking");
let stakingContract = await StakingContractFactory.attach(STAKING_CONTRACT_ADDRESS) as Staking;
stakingContract = stakingContract.connect(account);

const tx = await stakingContract.unstake();