控制台2.6+版本¶
标签：控制台2.6
重要
控制台是FISCO BCOS 2.0重要的交互式客户端工具，它通过Java SDK与区块链节点建立连接，实现对区块链节点数据的读写访问请求。控制台拥有丰富的命令，包括查询区块链状态、管理区块链节点、部署并调用合约等。此外，控制台提供一个合约编译工具，用户可以方便快捷的将Solidity合约文件编译为Java合约文件。
控制台配置与运行¶
重要
前置条件：搭建FISCO BCOS区块链，请参考 搭建第一个区块链网络 建链工具参考：开发部署工具 或 运维部署工具。
获取控制台¶
cd ~ && mkdir -p fisco && cd fisco
# 获取控制台
curl -#LO https://github.com/FISCO-BCOS/console/releases/download/v2.9.2/download_console.sh && bash download_console.sh
注解
如果因为网络问题导致长时间无法下载，请尝试 curl -#LO https://gitee.com/FISCO-BCOS/console/raw/master-2.0/tools/download_console.sh && bash download_console.sh
目录结构如下：
|-- apps # 控制台jar包目录
| -- console.jar
|-- lib # 相关依赖的jar包目录
├── conf
│ ├── config-example.toml # 配置文件
│ ├── group-generate-config.toml # 创建群组的配置文件，具体可参考命令genrateGroupFromFile
│ └── log4j.properties # 日志配置文件
|-- contracts # 合约所在目录
| -- solidity # solidity合约存放目录
| -- HelloWorld.sol # 普通合约：HelloWorld合约，可部署和调用
| -- TableTest.sol # 使用CRUD接口的合约：TableTest合约，可部署和调用
| -- Table.sol # 提供CRUD操作的接口合约
| -- console # 控制台部署合约时编译的合约abi, bin，java文件目录
| -- sdk # sol2java.sh脚本编译的合约abi, bin，java文件目录
|-- start.sh # 控制台启动脚本
|-- get_account.sh # 账户生成脚本
|-- get_gm_account.sh # 账户生成脚本，国密版
|-- sol2java.sh # solidity合约文件编译为java合约文件的开发工具脚本
注意：默认下载的控制台内置0.4.25版本的solidity编译器，用户需要编译0.5或者0.6版本的合约时，可以通过下列命令获取内置对应编译器版本的控制台
# 0.5
curl -#LO https://github.com/FISCO-BCOS/console/releases/download/v2.9.2/download_console.sh && bash download_console.sh -v 0.5
# 0.6
curl -#LO https://github.com/FISCO-BCOS/console/releases/download/v2.9.2/download_console.sh && bash download_console.sh -v 0.6
注解
如果因为网络问题导致长时间无法下载，0.5版本请尝试命令： https://osp-1257653870.cos.ap-guangzhou.myqcloud.com/FISCO-BCOS/console/releases/v2.9.2/download_console.sh && bash download_console.sh -v 0.5
0.6版本请尝试命令： https://osp-1257653870.cos.ap-guangzhou.myqcloud.com/FISCO-BCOS/console/releases/v2.9.2/download_console.sh && bash download_console.sh -v 0.6
配置控制台¶
区块链节点和证书的配置：
将节点sdk目录下的
ca.crt、sdk.crt和sdk.key文件拷贝到conf目录下。将
conf目录下的config-example.toml文件重命名为config.toml文件。配置config.toml文件，其中添加注释的内容根据区块链节点配置做相应修改。提示：如果搭链时设置的channel_listen_ip(若节点版本小于v2.3.0，查看配置项listen_ip)为127.0.0.1或者0.0.0.0，channel_port为20200， 则config.toml配置不用修改。FISCO-BCOS 2.5及之后的版本，添加了SDK只能连本机构节点的限制，操作时需确认拷贝证书的路径，否则建联报错。
配置示例文件如下：
[cryptoMaterial]
certPath = "conf" # The certification path
# The following configurations take the certPath by default if commented
# caCert = "conf/ca.crt" # CA cert file path
# If connect to the GM node, default CA cert path is ${certPath}/gm/gmca.crt
# sslCert = "conf/sdk.crt" # SSL cert file path
# If connect to the GM node, the default SDK cert path is ${certPath}/gm/gmsdk.crt
# sslKey = "conf/sdk.key" # SSL key file path
# If connect to the GM node, the default SDK privateKey path is ${certPath}/gm/gmsdk.key
# enSslCert = "conf/gm/gmensdk.crt" # GM encryption cert file path
# default load the GM SSL encryption cert from ${certPath}/gm/gmensdk.crt
# enSslKey = "conf/gm/gmensdk.key" # GM ssl cert file path
# default load the GM SSL encryption privateKey from ${certPath}/gm/gmensdk.key
[network]
peers=["127.0.0.1:20200", "127.0.0.1:20201"] # The peer list to connect
# Configure a private topic as a topic message sender.
# [[amop]]
# topicName = "PrivateTopic1"
# publicKeys = [ "conf/amop/consumer_public_key_1.pem" ] # Public keys of the nodes that you want to send AMOP message of this topic to.
# Configure a private topic as a topic subscriber.
# [[amop]]
# topicName = "PrivateTopic2"
# privateKey = "conf/amop/consumer_private_key.p12" # Your private key that used to subscriber verification.
# password = "123456"
[account]
keyStoreDir = "account" # The directory to load/store the account file, default is "account"
# accountFilePath = "" # The account file path (default load from the path specified by the keyStoreDir)
accountFileFormat = "pem" # The storage format of account file (Default is "pem", "p12" as an option)
# accountAddress = "" # The transactions sending account address
# Default is a randomly generated account
# The randomly generated account is stored in the path specified by the keyStoreDir
# password = "" # The password used to load the account file
[threadPool]
# channelProcessorThreadSize = "16" # The size of the thread pool to process channel callback
# Default is the number of cpu cores
# receiptProcessorThreadSize = "16" # The size of the thread pool to process transaction receipt notification
# Default is the number of cpu cores
maxBlockingQueueSize = "102400" # The max blocking queue size of the thread pool
配置项详细说明参考这里。
重要
控制台说明
当控制台配置文件在一个群组内配置多个节点连接时，由于群组内的某些节点在操作过程中可能退出群组，因此控制台轮询节点查询时，其返回信息可能不一致，属于正常现象。建议使用控制台时，配置一个节点或者保证配置的节点始终在群组中，这样在同步时间内查询的群组内信息保持一致。
合约编译工具¶
控制台提供一个专门的编译合约工具，方便开发者将solidity合约文件编译为java合约文件。
# 若控制台版本小于v2.8.0，脚本sol2java.sh的使用方法如下：
$ bash sol2java.sh -h
# Compile Solidity Tool
./sol2java.sh [packageName] [solidityFilePath] [javaCodeOutputDir]
packageName:
the package name of the generated Java class file
solidityFilePath:
(optional) the solidity file path or the directory where solidity files located, default: contracts/solidity
javaCodeOutputDir:
(optional) the directory where the generated Java files located, default: contracts/sdk/java
# 若控制台版本大于等于v2.8.0，脚本sol2java.sh的使用方法如下：
$ bash sol2java.sh -h
usage: Compile Solidity Tool:
-h,--help
-l,--libraries <arg> [Optional] Set library address information built
into the solidity contract
eg:
--libraries lib1:lib1_address lib2:lib2_address
-o,--output <arg> [Optional] The file path of the generated java
code, default is contracts/sdk/java/
-p,--package <arg> [Optional] The package name of the generated java
code, default is com
-s,--sol <arg> [Optional] The solidity file path or the solidity
directory path, default is contracts/solidity/
参数
packageName: 生成Java文件的包名solidityFilePath: (可选)solidity文件的路径，支持文件路径和目录路径两种方式，参数为目录时将目录下所有的solidity文件进行编译转换。默认目录为contracts/solidity。javaCodeOutputDir: (可选)生成Java文件的目录，默认生成在contracts/sdk/java目录。
使用
$ cd ~/fisco/console
# 若控制台版本小于2.8.0
$ ./sol2java.sh org.com.fisco # 指定java包名
# 若控制台版本大于等于2.8.0
$ bash sol2java.sh -p org.com.fisco
运行成功之后，将会在console/contracts/sdk目录生成java、abi和bin目录，如下所示。
|-- abi # 编译生成的abi目录，存放solidity合约编译的abi文件
| |-- HelloWorld.abi
| |-- Table.abi
| |-- TableTest.abi
|-- bin # 编译生成的bin目录，存放solidity合约编译的bin文件
| |-- HelloWorld.bin
| |-- Table.bin
| |-- TableTest.bin
|-- java # 存放编译的包路径及Java合约文件
| |-- org
| |-- com
| |-- fisco
| |-- HelloWorld.java # 编译的HelloWorld Java文件
| |-- Table.java # 编译的CRUD接口合约 Java文件
| |-- TableTest.java # 编译的TableTest Java文件
java目录下生成了org/com/fisco/包路径目录。包路径目录下将会生成java合约文件HelloWorld.java、TableTest.java和Table.java。其中HelloWorld.java和TableTest.java是java应用所需要的java合约文件。
重要
Java合约文件说明
控制台自1.1.0版本起，生成的Java合约文件国密、非国密环境均可以运行，国密与非国密环境生成一份合约代码即可
启动控制台¶
在节点正在运行的情况下，启动控制台：
$ ./start.sh
# 输出下述信息表明启动成功
=====================================================================================
Welcome to FISCO BCOS console(2.6.0)!
Type 'help' or 'h' for help. Type 'quit' or 'q' to quit console.
________ ______ ______ ______ ______ _______ ______ ______ ______
| | \/ \ / \ / \ | \ / \ / \ / \
| $$$$$$$$\$$$$$| $$$$$$| $$$$$$| $$$$$$\ | $$$$$$$| $$$$$$| $$$$$$| $$$$$$\
| $$__ | $$ | $$___\$| $$ \$| $$ | $$ | $$__/ $| $$ \$| $$ | $| $$___\$$
| $$ \ | $$ \$$ \| $$ | $$ | $$ | $$ $| $$ | $$ | $$\$$ \
| $$$$$ | $$ _\$$$$$$| $$ __| $$ | $$ | $$$$$$$| $$ __| $$ | $$_\$$$$$$\
| $$ _| $$_| \__| $| $$__/ | $$__/ $$ | $$__/ $| $$__/ | $$__/ $| \__| $$
| $$ | $$ \\$$ $$\$$ $$\$$ $$ | $$ $$\$$ $$\$$ $$\$$ $$
\$$ \$$$$$$ \$$$$$$ \$$$$$$ \$$$$$$ \$$$$$$$ \$$$$$$ \$$$$$$ \$$$$$$
=====================================================================================
启动脚本说明¶
查看当前控制台版本：¶
./start.sh --version
console version: 2.6.0
账户使用方式¶
控制台加载私钥¶
控制台提供账户生成脚本get_account.sh(脚本用法请参考账户管理文档，生成的的账户文件在accounts目录下，控制台加载的账户文件必须放置在该目录下。 控制台启动方式有如下几种：
./start.sh
./start.sh groupID
./start.sh groupID -pem pemName
./start.sh groupID -p12 p12Name
默认启动¶
使用控制台配置文件指定的默认群组号启动。
./start.sh
注意: 控制台启动未指定私钥账户时，会尝试从accounts目录下加载一个可用的私钥账户用于发送交易，加载失败则会创建一个新的PEM格式的账户文件，将其保存在accounts目录下。
使用PEM格式私钥文件启动¶
使用指定的pem文件的账户启动，输入参数：群组号、-pem、pem文件路径
./start.sh 1 -pem accounts/0xebb824a1122e587b17701ed2e512d8638dfb9c88.pem
使用PKCS12格式私钥文件启动¶
使用指定的p12文件的账户，需要输入密码，输入参数：群组号、-p12、p12文件路径
./start.sh 1 -p12 accounts/0x5ef4df1b156bc9f077ee992a283c2dbb0bf045c0.p12
Enter Export Password:
注意： 控制台启动时加载p12文件出现下面报错：
exception unwrapping private key - java.security.InvalidKeyException: Illegal key size
可能是Java版本的原因，参考解决方案：https://stackoverflow.com/questions/3862800/invalidkeyexception-illegal-key-size
控制台命令结构¶
控制台命令由两部分组成，即指令和指令相关的参数：
指令: 指令是执行的操作命令，包括查询区块链相关信息，部署合约和调用合约的指令等，其中部分指令调用JSON-RPC接口，因此与JSON-RPC接口同名。 使用提示： 指令可以使用tab键补全，并且支持按上下键显示历史输入指令。
指令相关的参数: 指令调用接口需要的参数，指令与参数以及参数与参数之间均用空格分隔，与JSON-RPC接口同名命令的输入参数和获取信息字段的详细解释参考JSON-RPC API。
常用命令¶
合约相关命令¶
其他命令¶
查询区块高度：getBlockNumber
查询共识节点列表：getSealerList
查询交易回执信息: getTransactionReceipt
切换群组: switch
快捷键¶
Ctrl+A：光标移动到行首Ctrl+D：退出控制台Ctrl+E：光标移动到行尾Ctrl+R：搜索输入的历史命令↑：向前浏览历史命令
↓：向后浏览历史命令
控制台命令列表¶
help¶
输入help或者h，查看控制台所有的命令。
[group:1]> help
* help([-h, -help, --h, --H, --help, -H, h]) Provide help information
* addObserver Add an observer node
* addSealer Add a sealer node
* call Call a contract by a function and parameters
* callByCNS Call a contract by a function and parameters by CNS
* create Create table by sql
* delete Remove records by sql
* deploy Deploy a contract on blockchain
* deployByCNS Deploy a contract on blockchain by CNS
* desc Description table information
* quit([quit, q, exit]) Quit console
* freezeAccount Freeze the account
* freezeContract Freeze the contract
* generateGroup Generate a group for the specified node
* generateGroupFromFile Generate group according to the specified file
* getAccountStatus GetAccountStatus of the account
* getAvailableConnections Get the connection information of the nodes connected with the sdk
* getBatchReceiptsByBlockHashAndRange Get batched transaction receipts according to block hash and the transaction range
* getBatchReceiptsByBlockNumberAndRange Get batched transaction receipts according to block number and the transaction range
* getBlockByHash Query information about a block by hash
* getBlockByNumber Query information about a block by number
* getBlockHashByNumber Query block hash by block number
* getBlockHeaderByHash Query information about a block header by hash
* getBlockHeaderByNumber Query information about a block header by block number
* getBlockNumber Query the number of most recent block
* getCode Query code at a given address
* getConsensusStatus Query consensus status
* getContractStatus Get the status of the contract
* getCryptoType Get the current crypto type
* getCurrentAccount Get the current account info
* getDeployLog Query the log of deployed contracts
* getGroupConnections Get the node information of the group connected to the SDK
* getGroupList Query group list
* getGroupPeers Query nodeId list for sealer and observer nodes
* getNodeIDList Query nodeId list for all connected nodes
* getNodeInfo Query the specified node information.
* getNodeVersion Query the current node version
* getObserverList Query nodeId list for observer nodes.
* getPbftView Query the pbft view of node
* getPeers Query peers currently connected to the client
* getPendingTransactions Query pending transactions
* getPendingTxSize Query pending transactions size
* getSealerList Query nodeId list for sealer nodes
* getSyncStatus Query sync status
* getSystemConfigByKey Query a system config value by key
* getTotalTransactionCount Query total transaction count
* getTransactionByBlockHashAndIndex Query information about a transaction by block hash and transaction index position
* getTransactionByBlockNumberAndIndex Query information about a transaction by block number and transaction index position
* getTransactionByHash Query information about a transaction requested by transaction hash
* getTransactionByHashWithProof Query the transaction and transaction proof by transaction hash
* getTransactionReceipt Query the receipt of a transaction by transaction hash
* getTransactionReceiptByHashWithProof Query the receipt and transaction receipt proof by transaction hash
* grantCNSManager Grant permission for CNS by address
* grantCommitteeMember Grant the account committee member
* grantContractStatusManager Grant contract authorization to the user
* grantContractWritePermission Grant the account the contract write permission.
* grantDeployAndCreateManager Grant permission for deploy contract and create user table by address
* grantNodeManager Grant permission for node configuration by address
* grantOperator Grant the account operator
* grantSysConfigManager Grant permission for system configuration by address
* grantUserTableManager Grant permission for user table by table name and address
* insert Insert records by sql
* listAbi List functions and events info of the contract.
* listAccount List the current saved account list
* listCNSManager Query permission information for CNS
* listCommitteeMembers List all committee members
* listContractStatusManager List the authorization of the contract
* listContractWritePermission Query the account list which have write permission of the contract.
* listDeployAndCreateManager Query permission information for deploy contract and create user table
* listDeployContractAddress List the contractAddress for the specified contract
* listNodeManager Query permission information for node configuration
* listOperators List all operators
* listSysConfigManager Query permission information for system configuration
* listUserTableManager Query permission for user table information
* loadAccount Load account for the transaction signature
* newAccount Create account
* queryCNS Query CNS information by contract name and contract version
* queryCommitteeMemberWeight Query the committee member weight
* queryGroupStatus Query the status of the specified group of the specified node
* queryThreshold Query the threshold
* queryVotesOfMember Query votes of a committee member.
* queryVotesOfThreshold Query votes of updateThreshold operation
* recoverGroup Recover the specified group of the specified node
* registerCNS RegisterCNS information for the given contract
* removeGroup Remove the specified group of the specified node
* removeNode Remove a node
* revokeCNSManager Revoke permission for CNS by address
* revokeCommitteeMember Revoke the account from committee member
* revokeContractStatusManager Revoke contract authorization to the user
* revokeContractWritePermission Revoke the account the contract write permission
* revokeDeployAndCreateManager Revoke permission for deploy contract and create user table by address
* revokeNodeManager Revoke permission for node configuration by address
* revokeOperator Revoke the operator
* revokeSysConfigManager Revoke permission for system configuration by address
* revokeUserTableManager Revoke permission for user table by table name and address
* switch([s]) Switch to a specific group by group ID
* select Select records by sql
* setSystemConfigByKey Set a system config value by key
* startGroup Start the specified group of the specified node
* stopGroup Stop the specified group of the specified node
* unfreezeAccount Unfreeze the account
* unfreezeContract Unfreeze the contract
* update Update records by sql
* updateCommitteeMemberWeight Update the committee member weight
* updateThreshold Update the threshold
---------------------------------------------------------------------------------------------
注：
help显示每条命令的含义是：命令 命令功能描述
查看具体命令的使用介绍说明，输入命令 -h或--help查看。例如：
[group:1]> getBlockByNumber -h
Query information about a block by block number.
Usage:
getBlockByNumber blockNumber [boolean]
* blockNumber -- Integer of a block number, from 0 to 2147483647.
* boolean -- (optional) If true it returns the full transaction objects, if false only the hashes of the transactions.
newAccount¶
创建新的发送交易的账户，默认会以PEM格式将账户保存在account目录下。
# 控制台连接非国密区块链时，账户文件自动保存在`account/ecdsa`目录
# 控制台连接国密区块链时，账户文件自动保存在`accout/gm`目录下
[group:1]> newAccount
AccountPath: account/ecdsa/0x6fad87071f790c3234108f41b76bb99874a6d813.pem
newAccount: 0x6fad87071f790c3234108f41b76bb99874a6d813
AccountType: ecdsa
$ ls -al account/ecdsa/0x6fad87071f790c3234108f41b76bb99874a6d813.pem
$ -rw-r--r-- 1 octopus staff 258 9 30 16:34 account/ecdsa/0x6fad87071f790c3234108f41b76bb99874a6d813.pem
loadAccount¶
加载PEM或者P12格式的私钥文件，加载的私钥可以用于发送交易签名。
参数：
私钥文件路径: 支持相对路径、绝对路径和默认路径三种方式。用户账户地址时，默认从
config.toml的账户配置选项keyStoreDir加载账户，keyStoreDir配置项请参考这里。账户格式: 可选，加载的账户文件类型，支持
pem与p12，默认为pem。
[group:1]> loadAccount 0x6fad87071f790c3234108f41b76bb99874a6d813
Load account 0x6fad87071f790c3234108f41b76bb99874a6d813 success!
listAccount¶
查看当前加载的所有账户信息
[group:1]> listAccount
0x6fad87071f790c3234108f41b76bb99874a6d813(current account) <=
0x726d9f31cf44debf80b08a7e759fa98b360b0736
注意：带有<=后缀标记的为当前用于发送交易的私钥账户，可以使用loadAccount进行切换
getSealerList¶
运行getSealerList，查看共识节点列表。
[group:1]> getSealerList
[
0c0bbd25152d40969d3d3cee3431fa28287e07cff2330df3258782d3008b876d146ddab97eab42796495bfbb281591febc2a0069dcc7dfe88c8831801c5b5801,
10b3a2d4b775ec7f3c2c9e8dc97fa52beb8caab9c34d026db9b95a72ac1d1c1ad551c67c2b7fdc34177857eada75836e69016d1f356c676a6e8b15c45fc9bc34,
622af37b2bd29c60ae8f15d467b67c0a7fe5eb3e5c63fdc27a0ee8066707a25afa3aa0eb5a3b802d3a8e5e26de9d5af33806664554241a3de9385d3b448bcd73
]
getObserverList¶
运行getObserverList，查看观察节点列表。
[group:1]> getObserverList
[
037c255c06161711b6234b8c0960a6979ef039374ccc8b723afea2107cba3432dbbc837a714b7da20111f74d5a24e91925c773a72158fa066f586055379a1772
]
getNodeIDList¶
运行getNodeIDList，查看节点及连接p2p节点的nodeId列表。
[group:1]> getNodeIDList
[
41285429582cbfe6eed501806391d2825894b3696f801e945176c7eb2379a1ecf03b36b027d72f480e89d15bacd43462d87efd09fb0549e0897f850f9eca82ba,
87774114e4a496c68f2482b30d221fa2f7b5278876da72f3d0a75695b81e2591c1939fc0d3fadb15cc359c997bafc9ea6fc37345346acaf40b6042b5831c97e1,
29c34347a190c1ec0c4507c6eed6a5bcd4d7a8f9f54ef26da616e81185c0af11a8cea4eacb74cf6f61820292b24bc5d9e426af24beda06fbd71c217960c0dff0,
d5b3a9782c6aca271c9642aea391415d8b258e3a6d92082e59cc5b813ca123745440792ae0b29f4962df568f8ad58b75fc7cea495684988e26803c9c5198f3f8
]
getConsensusStatus¶
运行getConsensusStatus，查看共识状态。
[group:1]> getConsensusStatus
ConsensusInfo{
baseConsensusInfo=BasicConsensusInfo{
nodeNum='4',
nodeIndex='3',
maxFaultyNodeNum='1',
sealerList=[
11e1be251ca08bb44f36fdeedfaeca40894ff80dfd80084607a75509edeaf2a9c6fee914f1e9efda571611cf4575a1577957edfd2baa9386bd63eb034868625f,
78a313b426c3de3267d72b53c044fa9fe70c2a27a00af7fea4a549a7d65210ed90512fc92b6194c14766366d434235c794289d66deff0796f15228e0e14a9191,
95b7ff064f91de76598f90bc059bec1834f0d9eeb0d05e1086d49af1f9c2f321062d011ee8b0df7644bd54c4f9ca3d8515a3129bbb9d0df8287c9fa69552887e,
b8acb51b9fe84f88d670646be36f31c52e67544ce56faf3dc8ea4cf1b0ebff0864c6b218fdcd9cf9891ebd414a995847911bd26a770f429300085f37e1131f36
],
consensusedBlockNumber='1',
highestblockNumber='0',
groupId='1',
protocolId='65544',
accountType='1',
cfgErr='false',
omitEmptyBlock='true',
nodeId='b8acb51b9fe84f88d670646be36f31c52e67544ce56faf3dc8ea4cf1b0ebff0864c6b218fdcd9cf9891ebd414a995847911bd26a770f429300085f37e1131f36',
allowFutureBlocks='true',
connectedNodes='3',
currentView='1735',
toView='1735',
leaderFailed='false',
highestblockHash='0x4f6394763c33c1709e5a72b202ad4d7a3b8152de3dc698cef6f675ecdaf20a3b'
},
viewInfos=[
ViewInfo{
nodeId='11e1be251ca08bb44f36fdeedfaeca40894ff80dfd80084607a75509edeaf2a9c6fee914f1e9efda571611cf4575a1577957edfd2baa9386bd63eb034868625f',
view='1732'
},
ViewInfo{
nodeId='78a313b426c3de3267d72b53c044fa9fe70c2a27a00af7fea4a549a7d65210ed90512fc92b6194c14766366d434235c794289d66deff0796f15228e0e14a9191',
view='1733'
},
ViewInfo{
nodeId='95b7ff064f91de76598f90bc059bec1834f0d9eeb0d05e1086d49af1f9c2f321062d011ee8b0df7644bd54c4f9ca3d8515a3129bbb9d0df8287c9fa69552887e',
view='1734'
},
ViewInfo{
nodeId='b8acb51b9fe84f88d670646be36f31c52e67544ce56faf3dc8ea4cf1b0ebff0864c6b218fdcd9cf9891ebd414a995847911bd26a770f429300085f37e1131f36',
view='1735'
}
]
}
getSyncStatus¶
运行getSyncStatus，查看同步状态。
[group:1]> getSyncStatus
{
"blockNumber":5,
"genesisHash":"0xeccad5274949b9d25996f7a96b89c0ac5c099eb9b72cc00d65bc6ef09f7bd10b",
"isSyncing":false,
"latestHash":"0xb99703130e24702d3b580111b0cf4e39ff60ac530561dd9eb0678d03d7acce1d",
"nodeId":"cf93054cf524f51c9fe4e9a76a50218aaa7a2ca6e58f6f5634f9c2884d2e972486c7fe1d244d4b49c6148c1cb524bcc1c99ee838bb9dd77eb42f557687310ebd",
"peers":[
{
"blockNumber":5,
"genesisHash":"0xeccad5274949b9d25996f7a96b89c0ac5c099eb9b72cc00d65bc6ef09f7bd10b",
"latestHash":"0xb99703130e24702d3b580111b0cf4e39ff60ac530561dd9eb0678d03d7acce1d",
"nodeId":"0471101bcf033cd9e0cbd6eef76c144e6eff90a7a0b1847b5976f8ba32b2516c0528338060a4599fc5e3bafee188bca8ccc529fbd92a760ef57ec9a14e9e4278"
},
{
"blockNumber":5,
"genesisHash":"0xeccad5274949b9d25996f7a96b89c0ac5c099eb9b72cc00d65bc6ef09f7bd10b",
"latestHash":"0xb99703130e24702d3b580111b0cf4e39ff60ac530561dd9eb0678d03d7acce1d",
"nodeId":"2b08375e6f876241b2a1d495cd560bd8e43265f57dc9ed07254616ea88e371dfa6d40d9a702eadfd5e025180f9d966a67f861da214dd36237b58d72aaec2e108"
},
{
"blockNumber":5,
"genesisHash":"0xeccad5274949b9d25996f7a96b89c0ac5c099eb9b72cc00d65bc6ef09f7bd10b",
"latestHash":"0xb99703130e24702d3b580111b0cf4e39ff60ac530561dd9eb0678d03d7acce1d",
"nodeId":"ed1c85b815164b31e895d3f4fc0b6e3f0a0622561ec58a10cc8f3757a73621292d88072bf853ac52f0a9a9bbb10a54bdeef03c3a8a42885fe2467b9d13da9dec"
}
],
"protocolId":265,
"txPoolSize":"0"
}
getNodeVersion¶
运行getNodeVersion，查看节点的版本。
[group:1]> getNodeVersion
{
"Build Time":"20190107 10:15:23",
"Build Type":"Linux/g++/RelWithDebInfo",
"FISCO-BCOS Version":"2.0.0",
"Git Branch":"master-2.0",
"Git Commit Hash":"be95a6e3e85b621860b101c3baeee8be68f5f450"
}
getPeers¶
运行getPeers，查看节点的peers。
[group:1]> getPeers
[
PeerInfo{
nodeID='78a313b426c3de3267d72b53c044fa9fe70c2a27a00af7fea4a549a7d65210ed90512fc92b6194c14766366d434235c794289d66deff0796f15228e0e14a9191',
ipAndPort='127.0.0.1:54647',
agency='agency',
topic=[
],
node='node2'
},
PeerInfo{
nodeID='95b7ff064f91de76598f90bc059bec1834f0d9eeb0d05e1086d49af1f9c2f321062d011ee8b0df7644bd54c4f9ca3d8515a3129bbb9d0df8287c9fa69552887e',
ipAndPort='127.0.0.1:30303',
agency='agency',
topic=[
],
node='node3'
},
PeerInfo{
nodeID='b8acb51b9fe84f88d670646be36f31c52e67544ce56faf3dc8ea4cf1b0ebff0864c6b218fdcd9cf9891ebd414a995847911bd26a770f429300085f37e1131f36',
ipAndPort='127.0.0.1:30300',
agency='agency',
topic=[
_block_notify_1
],
node='node0'
}
]
getGroupPeers¶
运行getGroupPeers，查看节点所在group的共识节点和观察节点列表。
[group:1]> getGroupPeers
[
cf93054cf524f51c9fe4e9a76a50218aaa7a2ca6e58f6f5634f9c2884d2e972486c7fe1d244d4b49c6148c1cb524bcc1c99ee838bb9dd77eb42f557687310ebd,
ed1c85b815164b31e895d3f4fc0b6e3f0a0622561ec58a10cc8f3757a73621292d88072bf853ac52f0a9a9bbb10a54bdeef03c3a8a42885fe2467b9d13da9dec,
0471101bcf033cd9e0cbd6eef76c144e6eff90a7a0b1847b5976f8ba32b2516c0528338060a4599fc5e3bafee188bca8ccc529fbd92a760ef57ec9a14e9e4278,
2b08375e6f876241b2a1d495cd560bd8e43265f57dc9ed07254616ea88e371dfa6d40d9a702eadfd5e025180f9d966a67f861da214dd36237b58d72aaec2e108
]
getBlockHeaderByHash¶
运行getBlockHeaderByHash，根据区块哈希查询区块头信息。 参数：
区块哈希：0x开头的区块哈希值
签名列表标志：默认为false，即：区块头信息中不显示区块签名列表信息，设置为true，则显示区块签名列表。
[group:1]> getBlockHeaderByHash 0x99576e7567d258bd6426ddaf953ec0c953778b2f09a078423103c6555aa4362d
{
"dbHash":"0x0000000000000000000000000000000000000000000000000000000000000000",
"extraData":[
],
"gasLimit":"0x0",
"gasUsed":"0x0",
"hash":"0x99576e7567d258bd6426ddaf953ec0c953778b2f09a078423103c6555aa4362d",
"logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
"number":1,
"parentHash":"0x4f6394763c33c1709e5a72b202ad4d7a3b8152de3dc698cef6f675ecdaf20a3b",
"receiptsRoot":"0x69a04fa6073e4fc0947bac7ee6990e788d1e2c5ec0fe6c2436d0892e7f3c09d2",
"sealer":"0x2",
"sealerList":[
"11e1be251ca08bb44f36fdeedfaeca40894ff80dfd80084607a75509edeaf2a9c6fee914f1e9efda571611cf4575a1577957edfd2baa9386bd63eb034868625f",
"78a313b426c3de3267d72b53c044fa9fe70c2a27a00af7fea4a549a7d65210ed90512fc92b6194c14766366d434235c794289d66deff0796f15228e0e14a9191",
"95b7ff064f91de76598f90bc059bec1834f0d9eeb0d05e1086d49af1f9c2f321062d011ee8b0df7644bd54c4f9ca3d8515a3129bbb9d0df8287c9fa69552887e",
"b8acb51b9fe84f88d670646be36f31c52e67544ce56faf3dc8ea4cf1b0ebff0864c6b218fdcd9cf9891ebd414a995847911bd26a770f429300085f37e1131f36"
],
"stateRoot":"0x0000000000000000000000000000000000000000000000000000000000000000",
"timestamp":"0x173ad8703d6",
"transactionsRoot":"0xb563f70188512a085b5607cac0c35480336a566de736c83410a062c9acc785ad"
}
getBlockHeaderByNumber¶
运行getBlockHeaderByNumber，根据区块高度查询区块头信息。 参数：
区块高度
签名列表标志：默认为false，即：区块头信息中不显示区块签名列表信息，设置为true，则显示区块签名列表。
[group:1]> getBlockHeaderByNumber 1 true
{
"dbHash":"0x0000000000000000000000000000000000000000000000000000000000000000",
"extraData":[
],
"gasLimit":"0x0",
"gasUsed":"0x0",
"hash":"0x99576e7567d258bd6426ddaf953ec0c953778b2f09a078423103c6555aa4362d",
"logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
"number":1,
"parentHash":"0x4f6394763c33c1709e5a72b202ad4d7a3b8152de3dc698cef6f675ecdaf20a3b",
"receiptsRoot":"0x69a04fa6073e4fc0947bac7ee6990e788d1e2c5ec0fe6c2436d0892e7f3c09d2",
"sealer":"0x2",
"sealerList":[
"11e1be251ca08bb44f36fdeedfaeca40894ff80dfd80084607a75509edeaf2a9c6fee914f1e9efda571611cf4575a1577957edfd2baa9386bd63eb034868625f",
"78a313b426c3de3267d72b53c044fa9fe70c2a27a00af7fea4a549a7d65210ed90512fc92b6194c14766366d434235c794289d66deff0796f15228e0e14a9191",
"95b7ff064f91de76598f90bc059bec1834f0d9eeb0d05e1086d49af1f9c2f321062d011ee8b0df7644bd54c4f9ca3d8515a3129bbb9d0df8287c9fa69552887e",
"b8acb51b9fe84f88d670646be36f31c52e67544ce56faf3dc8ea4cf1b0ebff0864c6b218fdcd9cf9891ebd414a995847911bd26a770f429300085f37e1131f36"
],
"signatureList":[
{
"index":"0x3",
"signature":"0xb5b41e49c0b2bf758322ecb5c86dc3a3a0f9b98891b5bbf50c8613a241f05f595ce40d0bb212b6faa32e98546754835b057b9be0b29b9d0c8ae8b38f7487b8d001"
},
{
"index":"0x0",
"signature":"0x411cb93f816549eba82c3bf8c03fa637036dcdee65667b541d0da06a6eaea80d16e6ca52bf1b08f77b59a834bffbc124c492ea7a1601d0c4fb257d97dc97cea600"
},
{
"index":"0x1",
"signature":"0xea3c27c2a1486c7942c41c4dc8f15fbf9a668aff2ca40f00701d73fa659a14317d45d74372d69d43ced8e81f789e48140e7fa0c61997fa7cde514c654ef9f26d00"
}
],
"stateRoot":"0x0000000000000000000000000000000000000000000000000000000000000000",
"timestamp":"0x173ad8703d6",
"transactionsRoot":"0xb563f70188512a085b5607cac0c35480336a566de736c83410a062c9acc785ad"
}
getBlockByHash¶
运行getBlockByHash，根据区块哈希查询区块信息。 参数：
区块哈希：0x开头的区块哈希值。
交易标志：默认false，区块中的交易只显示交易哈希，设置为true，显示交易具体信息。
[group:1]> getBlockByHash 0xf6afbcc3ec9eb4ac2c2829c2607e95ea0fa1be914ca1157436b2d3c5f1842855
{
"extraData":[
],
"gasLimit":"0x0",
"gasUsed":"0x0",
"hash":"0xf6afbcc3ec9eb4ac2c2829c2607e95ea0fa1be914ca1157436b2d3c5f1842855",
"logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
"number":"0x1",
"parentHash":"0xeccad5274949b9d25996f7a96b89c0ac5c099eb9b72cc00d65bc6ef09f7bd10b",
"sealer":"0x0",
"sealerList":[
"0471101bcf033cd9e0cbd6eef76c144e6eff90a7a0b1847b5976f8ba32b2516c0528338060a4599fc5e3bafee188bca8ccc529fbd92a760ef57ec9a14e9e4278",
"2b08375e6f876241b2a1d495cd560bd8e43265f57dc9ed07254616ea88e371dfa6d40d9a702eadfd5e025180f9d966a67f861da214dd36237b58d72aaec2e108",
"cf93054cf524f51c9fe4e9a76a50218aaa7a2ca6e58f6f5634f9c2884d2e972486c7fe1d244d4b49c6148c1cb524bcc1c99ee838bb9dd77eb42f557687310ebd",
"ed1c85b815164b31e895d3f4fc0b6e3f0a0622561ec58a10cc8f3757a73621292d88072bf853ac52f0a9a9bbb10a54bdeef03c3a8a42885fe2467b9d13da9dec"
],
"stateRoot":"0x9711819153f7397ec66a78b02624f70a343b49c60bc2f21a77b977b0ed91cef9",
"timestamp":"0x1692f119c84",
"transactions":[
"0xa14638d47cc679cf6eeb7f36a6d2a30ea56cb8dcf0938719ff45023a7a8edb5d"
],
"transactionsRoot":"0x516787f85980a86fd04b0e9ce82a1a75950db866e8cdf543c2cae3e4a51d91b7"
}
[group:1]> getBlockByHash 0xf6afbcc3ec9eb4ac2c2829c2607e95ea0fa1be914ca1157436b2d3c5f1842855 true
{
"extraData":[
],
"gasLimit":"0x0",
"gasUsed":"0x0",
"hash":"0xf6afbcc3ec9eb4ac2c2829c2607e95ea0fa1be914ca1157436b2d3c5f1842855",
"logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
"number":"0x1",
"parentHash":"0xeccad5274949b9d25996f7a96b89c0ac5c099eb9b72cc00d65bc6ef09f7bd10b",
"sealer":"0x0",
"sealerList":[
"0471101bcf033cd9e0cbd6eef76c144e6eff90a7a0b1847b5976f8ba32b2516c0528338060a4599fc5e3bafee188bca8ccc529fbd92a760ef57ec9a14e9e4278",
"2b08375e6f876241b2a1d495cd560bd8e43265f57dc9ed07254616ea88e371dfa6d40d9a702eadfd5e025180f9d966a67f861da214dd36237b58d72aaec2e108",
"cf93054cf524f51c9fe4e9a76a50218aaa7a2ca6e58f6f5634f9c2884d2e972486c7fe1d244d4b49c6148c1cb524bcc1c99ee838bb9dd77eb42f557687310ebd",
"ed1c85b815164b31e895d3f4fc0b6e3f0a0622561ec58a10cc8f3757a73621292d88072bf853ac52f0a9a9bbb10a54bdeef03c3a8a42885fe2467b9d13da9dec"
],
"stateRoot":"0x9711819153f7397ec66a78b02624f70a343b49c60bc2f21a77b977b0ed91cef9",
"timestamp":"0x1692f119c84",
"transactions":[
{
"blockHash":"0xf6afbcc3ec9eb4ac2c2829c2607e95ea0fa1be914ca1157436b2d3c5f1842855",
"blockNumber":"0x1",
"from":"0x7234c32327795e4e612164e3442cfae0d445b9ad",
"gas":"0x1c9c380",
"gasPrice":"0x1",
"hash":"0xa14638d47cc679cf6eeb7f36a6d2a30ea56cb8dcf0938719ff45023a7a8edb5d",
"input":"0x608060405234801561001057600080fd5b506040805190810160405280600d81526020017f48656c6c6f2c20576f726c6421000000000000000000000000000000000000008152506000908051906020019061005c929190610062565b50610107565b828054600181600116156101000203166002900490600052602060002090601f016020900481019282601f106100a357805160ff19168380011785556100d1565b828001600101855582156100d1579182015b828111156100d05782518255916020019190600101906100b5565b5b5090506100de91906100e2565b5090565b61010491905b808211156101005760008160009055506001016100e8565b5090565b90565b6102d7806101166000396000f30060806040526004361061004c576000357c0100000000000000000000000000000000000000000000000000000000900463ffffffff1680634ed3885e146100515780636d4ce63c146100ba575b600080fd5b34801561005d57600080fd5b506100b8600480360381019080803590602001908201803590602001908080601f016020809104026020016040519081016040528093929190818152602001838380828437820191505050505050919291929050505061014a565b005b3480156100c657600080fd5b506100cf610164565b6040518080602001828103825283818151815260200191508051906020019080838360005b8381101561010f5780820151818401526020810190506100f4565b50505050905090810190601f16801561013c5780820380516001836020036101000a031916815260200191505b509250505060405180910390f35b8060009080519060200190610160929190610206565b5050565b606060008054600181600116156101000203166002900480601f0160208091040260200160405190810160405280929190818152602001828054600181600116156101000203166002900480156101fc5780601f106101d1576101008083540402835291602001916101fc565b820191906000526020600020905b8154815290600101906020018083116101df57829003601f168201915b5050505050905090565b828054600181600116156101000203166002900490600052602060002090601f016020900481019282601f1061024757805160ff1916838001178555610275565b82800160010185558215610275579182015b82811115610274578251825591602001919060010190610259565b5b5090506102829190610286565b5090565b6102a891905b808211156102a457600081600090555060010161028c565b5090565b905600a165627a7a72305820fd74886bedbe51a7f3d834162de4d9af7f276c70133e04fd6776b5fbdd3653000029",
"nonce":"0x3443a1391c9c29f751e8350304efb310850b8afbaa7738f5e89ddfce79b1d6",
"to":null,
"transactionIndex":"0x0",
"value":"0x0"
}
],
"transactionsRoot":"0x516787f85980a86fd04b0e9ce82a1a75950db866e8cdf543c2cae3e4a51d91b7"
}
getBlockByNumber¶
运行getBlockByNumber，根据区块高度查询区块信息。 参数：
区块高度：十进制整数。
交易标志：默认false，区块中的交易只显示交易哈希，设置为true，显示交易具体信息。
[group:1]> getBlockByNumber 1
{
"extraData":[
],
"gasLimit":"0x0",
"gasUsed":"0x0",
"hash":"0xf6afbcc3ec9eb4ac2c2829c2607e95ea0fa1be914ca1157436b2d3c5f1842855",
"logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
"number":"0x1",
"parentHash":"0xeccad5274949b9d25996f7a96b89c0ac5c099eb9b72cc00d65bc6ef09f7bd10b",
"sealer":"0x0",
"sealerList":[
"0471101bcf033cd9e0cbd6eef76c144e6eff90a7a0b1847b5976f8ba32b2516c0528338060a4599fc5e3bafee188bca8ccc529fbd92a760ef57ec9a14e9e4278",
"2b08375e6f876241b2a1d495cd560bd8e43265f57dc9ed07254616ea88e371dfa6d40d9a702eadfd5e025180f9d966a67f861da214dd36237b58d72aaec2e108",
"cf93054cf524f51c9fe4e9a76a50218aaa7a2ca6e58f6f5634f9c2884d2e972486c7fe1d244d4b49c6148c1cb524bcc1c99ee838bb9dd77eb42f557687310ebd",
"ed1c85b815164b31e895d3f4fc0b6e3f0a0622561ec58a10cc8f3757a73621292d88072bf853ac52f0a9a9bbb10a54bdeef03c3a8a42885fe2467b9d13da9dec"
],
"stateRoot":"0x9711819153f7397ec66a78b02624f70a343b49c60bc2f21a77b977b0ed91cef9",
"timestamp":"0x1692f119c84",
"transactions":[
"0xa14638d47cc679cf6eeb7f36a6d2a30ea56cb8dcf0938719ff45023a7a8edb5d"
],
"transactionsRoot":"0x516787f85980a86fd04b0e9ce82a1a75950db866e8cdf543c2cae3e4a51d91b7"
}
getBlockHashByNumber¶
运行getBlockHashByNumber，通过区块高度获得区块哈希。 参数：
区块高度：十进制整数。
[group:1]> getBlockHashByNumber 1
0xf6afbcc3ec9eb4ac2c2829c2607e95ea0fa1be914ca1157436b2d3c5f1842855
getTransactionByHash¶
运行getTransactionByHash，通过交易哈希查询交易信息。 参数：
交易哈希：0x开头的交易哈希值。
[group:1]> getTransactionByHash 0x1dfc67c51f5cc93b033fc80e5e9feb049c575a58b863483aa4d04f530a2c87d5
{
"blockHash":"0xe4e1293837013f547ad7f443a8ff20a4e32a060b9cac56c41462255603548b7b",
"blockNumber":"0x8",
"from":"0xf0d2115e52b0533e367447f700bfbf2ed35ff6fc",
"gas":"0x11e1a300",
"gasPrice":"0x11e1a300",
"hash":"0x1dfc67c51f5cc93b033fc80e5e9feb049c575a58b863483aa4d04f530a2c87d5",
"input":"0xebf3b24f0000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000005667275697400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000056170706c65000000000000000000000000000000000000000000000000000000",
"nonce":"0x1aec6e447da49b9a140bf39a91a4d75fd19ea77f7dc38ccf940d8d510d78bd0",
"to":"0x42fc572759fd568bd590f46011784be2a2d53f0c",
"transactionIndex":"0x0",
"value":"0x0"
}
getTransactionByBlockHashAndIndex¶
运行getTransactionByBlockHashAndIndex，通过区块哈希和交易索引查询交易信息。 参数：
区块哈希：0x开头的区块哈希值。
交易索引：十进制整数。
[group:1]> getTransactionByBlockHashAndIndex 0xe4e1293837013f547ad7f443a8ff20a4e32a060b9cac56c41462255603548b7b 0
{
"blockHash":"0xe4e1293837013f547ad7f443a8ff20a4e32a060b9cac56c41462255603548b7b",
"blockNumber":"0x8",
"from":"0xf0d2115e52b0533e367447f700bfbf2ed35ff6fc",
"gas":"0x11e1a300",
"gasPrice":"0x11e1a300",
"hash":"0x1dfc67c51f5cc93b033fc80e5e9feb049c575a58b863483aa4d04f530a2c87d5",
"input":"0xebf3b24f0000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000005667275697400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000056170706c65000000000000000000000000000000000000000000000000000000",
"nonce":"0x1aec6e447da49b9a140bf39a91a4d75fd19ea77f7dc38ccf940d8d510d78bd0",
"to":"0x42fc572759fd568bd590f46011784be2a2d53f0c",
"transactionIndex":"0x0",
"value":"0x0"
}
getTransactionByBlockNumberAndIndex¶
运行getTransactionByBlockNumberAndIndex，通过区块高度和交易索引查询交易信息。 参数：
区块高度：十进制整数。
交易索引：十进制整数。
[group:1]> getTransactionByBlockNumberAndIndex 8 0
{
"blockHash":"0xe4e1293837013f547ad7f443a8ff20a4e32a060b9cac56c41462255603548b7b",
"blockNumber":"0x8",
"from":"0xf0d2115e52b0533e367447f700bfbf2ed35ff6fc",
"gas":"0x11e1a300",
"gasPrice":"0x11e1a300",
"hash":"0x1dfc67c51f5cc93b033fc80e5e9feb049c575a58b863483aa4d04f530a2c87d5",
"input":"0xebf3b24f0000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000005667275697400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000056170706c65000000000000000000000000000000000000000000000000000000",
"nonce":"0x1aec6e447da49b9a140bf39a91a4d75fd19ea77f7dc38ccf940d8d510d78bd0",
"to":"0x42fc572759fd568bd590f46011784be2a2d53f0c",
"transactionIndex":"0x0",
"value":"0x0"
}
getTransactionReceipt¶
运行getTransactionReceipt，通过交易哈希查询交易回执。 参数：
交易哈希：0x开头的交易哈希值。
[group:1]> getTransactionReceipt 0x1dfc67c51f5cc93b033fc80e5e9feb049c575a58b863483aa4d04f530a2c87d5
{
"blockHash":"0xe4e1293837013f547ad7f443a8ff20a4e32a060b9cac56c41462255603548b7b",
"blockNumber":"0x8",
"contractAddress":"0x0000000000000000000000000000000000000000",
"from":"0xf0d2115e52b0533e367447f700bfbf2ed35ff6fc",
"gasUsed":"0x94f5",
"input":"0xebf3b24f0000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000005667275697400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000056170706c65000000000000000000000000000000000000000000000000000000",
"logs":[
{
"address":"0x42fc572759fd568bd590f46011784be2a2d53f0c",
"data":"0x0000000000000000000000000000000000000000000000000000000000000001",
"topics":[
"0xc57b01fa77f41df77eaab79a0e2623fab2e7ae3e9530d9b1cab225ad65f2b7ce"
]
}
],
"logsBloom":"0x00000000000000800000000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000800000000000000000000000000000000002000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
"output":"0x0000000000000000000000000000000000000000000000000000000000000001",
"status":"0x0",
"to":"0x42fc572759fd568bd590f46011784be2a2d53f0c",
"transactionHash":"0x1dfc67c51f5cc93b033fc80e5e9feb049c575a58b863483aa4d04f530a2c87d5",
"transactionIndex":"0x0"
}
getCode¶
运行getCode，根据合约地址查询合约二进制代码。 参数：
合约地址：0x的合约地址(部署合约可以获得合约地址)。
[group:1]> getCode 0x97b8c19598fd781aaeb53a1957ef9c8acc59f705
0x60606040526000357c0100000000000000000000000000000000000000000000000000000000900463ffffffff16806366c99139146100465780636d4ce63c14610066575bfe5b341561004e57fe5b610064600480803590602001909190505061008c565b005b341561006e57fe5b61007661028c565b6040518082815260200191505060405180910390f35b8060006001015410806100aa57506002600101548160026001015401105b156100b457610289565b806000600101540360006001018190555080600260010160008282540192505081905550600480548060010182816100ec919061029a565b916000526020600020906004020160005b608060405190810160405280604060405190810160405280600881526020017f32303137303431330000000000000000000000000000000000000000000000008152508152602001600060000160009054906101000a900473ffffffffffffffffffffffffffffffffffffffff1673ffffffffffffffffffffffffffffffffffffffff168152602001600260000160009054906101000a900473ffffffffffffffffffffffffffffffffffffffff1673ffffffffffffffffffffffffffffffffffffffff16815260200185815250909190915060008201518160000190805190602001906101ec9291906102cc565b5060208201518160010160006101000a81548173ffffffffffffffffffffffffffffffffffffffff021916908373ffffffffffffffffffffffffffffffffffffffff16021790555060408201518160020160006101000a81548173ffffffffffffffffffffffffffffffffffffffff021916908373ffffffffffffffffffffffffffffffffffffffff160217905550606082015181600301555050505b50565b600060026001015490505b90565b8154818355818115116102c7576004028160040283600052602060002091820191016102c6919061034c565b5b505050565b828054600181600116156101000203166002900490600052602060002090601f016020900481019282601f1061030d57805160ff191683800117855561033b565b8280016001018555821561033b579182015b8281111561033a57825182559160200191906001019061031f565b5b50905061034891906103d2565b5090565b6103cf91905b808211156103cb57600060008201600061036c91906103f7565b6001820160006101000a81549073ffffffffffffffffffffffffffffffffffffffff02191690556002820160006101000a81549073ffffffffffffffffffffffffffffffffffffffff0219169055600382016000905550600401610352565b5090565b90565b6103f491905b808211156103f05760008160009055506001016103d8565b5090565b90565b50805460018160011615610100020316600290046000825580601f1061041d575061043c565b601f01602090049060005260206000209081019061043b91906103d2565b5b505600a165627a7a723058203c1f95b4a803493db0120df571d9f5155734152548a532412f2f9fa2dbe1ac730029
getTotalTransactionCount¶
运行getTotalTransactionCount，查询当前块高和累计交易数（从块高为0开始）。
[group:1]> getTotalTransactionCount
{
"blockNumber":1,
"txSum":1,
"failedTxSum":0
}
deploy¶
部署合约。(默认提供HelloWorld合约和TableTest.sol进行示例使用) 参数：
合约路径：合约文件的路径，支持相对路径、绝对路径和默认路径三种方式。用户输入为文件名时，从默认目录获取文件，默认目录为:
contracts/solidity，比如：HelloWorld。
# 部署HelloWorld合约，默认路径
[group:1]> deploy HelloWorld
contract address:0xc0ce097a5757e2b6e189aa70c7d55770ace47767
# 部署HelloWorld合约，相对路径
[group:1]> deploy contracts/solidity/HelloWorld.sol
contract address:0xd653139b9abffc3fe07573e7bacdfd35210b5576
# 部署HelloWorld合约，绝对路径
[group:1]> deploy ~/fisco/console/contracts/solidity/HelloWorld.sol
contract address:0x85517d3070309a89357c829e4b9e2d23ee01d881
注：
部署用户编写的合约，可以将solidity合约文件放到控制台根目录的
contracts/solidity/目录下，然后进行部署即可。按tab键可以搜索contracts/solidity/目录下的合约名称。若需要部署的合约引用了其他合约或library库，引用格式为
import "./XXX.sol";。其相关引入的合约和library库均放在contracts/solidity/目录。如果合约引用了library库，library库文件的名称必须以
Lib字符串开始，以便于区分是普通合约与library库文件。library库文件不能单独部署和调用。
listAbi¶
显示合约接口和Event列表 参数：
合约路径：合约文件的路径，支持相对路径、绝对路径和默认路径三种方式。用户输入为文件名时，从默认目录获取文件，默认目录为:
contracts/solidity，比如：TableTest。合约名：(可选)合约名称，默认情况下使用合约文件名作为合约名参数
[group:1]> listAbi TableTest
Method list:
name | constant | methodId | signature
--------------------------------------------------------------
remove | false | 0x0fe1160f | remove(string,int256)
update | false | 0x49cc36b5 | update(string,int256,string)
select | true | 0x5b325d78 | select(string)
insert | false | 0xe020d464 | insert(string,int256,string)
Event list:
name | topic signature
--------------------------------------------------------------
remove | 0x0fe1160f9655e87c29e76aca1cab34fb2a644d375da7a900c7076bad17cad26b | remove(string,int256)
update | 0x49cc36b56a9320d20b2d9a1938a972c849191bceb97500bfd38fa8a590dac73a | update(string,int256,string)
select | 0x5b325d7821528d3b52d0cc7a83e1ecef0438f763796770201020ac8b8813ac0a | select(string)
insert | 0xe020d464e502c11b54a7e37e568c78f0fcd360213eb5f4ac0a25a17733fc19f7 | insert(string,int256,string)
getDeployLog¶
运行getDeployLog，查询群组内由当前控制台部署合约的日志信息。日志信息包括部署合约的时间，群组ID，合约名称和合约地址。参数：
日志行数，可选，根据输入的期望值返回最新的日志信息，当实际条数少于期望值时，按照实际数量返回。当期望值未给出时，默认按照20条返回最新的日志信息。
[group:1]> getDeployLog 2
2019-05-26 08:37:03 [group:1] HelloWorld 0xc0ce097a5757e2b6e189aa70c7d55770ace47767
2019-05-26 08:37:45 [group:1] TableTest 0xd653139b9abffc3fe07573e7bacdfd35210b5576
[group:1]> getDeployLog 1
2019-05-26 08:37:45 [group:1] TableTest 0xd653139b9abffc3fe07573e7bacdfd35210b5576
注： 如果要查看所有的部署合约日志信息，请查看console目录下的deploylog.txt文件。该文件只存储最近10000条部署合约的日志记录。
call¶
运行call，调用合约。 参数：
合约路径：合约文件的路径，支持相对路径、绝对路径和默认路径三种方式。用户输入为文件名时，从默认目录获取文件，默认目录为:
contracts/solidity。合约地址: 部署合约获取的地址。
合约接口名：调用的合约接口名。
参数：由合约接口参数决定。参数由空格分隔；数组参数需要加上中括号，比如[1,2,3]，数组中是字符串或字节类型，加双引号，例如[“alice”,”bob”]，注意数组参数中不要有空格；布尔类型为true或者false。
# 调用HelloWorld的get接口获取name字符串
[group:1]> call HelloWorld 0x175b16a1299c7af3e2e49b97e68a44734257a35e get
---------------------------------------------------------------------------------------------
Return code: 0
description: transaction executed successfully
Return message: Success
---------------------------------------------------------------------------------------------
Return values:
[
"Hello,World!"
]
---------------------------------------------------------------------------------------------
# 调用HelloWorld的set接口设置name字符串
[group:1]> call HelloWorld 0x175b16a1299c7af3e2e49b97e68a44734257a35e set "Hello, FISCO BCOS"
transaction hash: 0x54b7bc73e3b57f684a6b49d2fad41bd8decac55ce021d24a1f298269e56f1ce1
---------------------------------------------------------------------------------------------
transaction status: 0x0
description: transaction executed successfully
---------------------------------------------------------------------------------------------
Output
Receipt message: Success
Return message: Success
---------------------------------------------------------------------------------------------
Event logs
Event: {}
# 调用HelloWorld的get接口获取name字符串，检查设置是否生效
[group:1]> call HelloWorld 0x175b16a1299c7af3e2e49b97e68a44734257a35e get
---------------------------------------------------------------------------------------------
Return code: 0
description: transaction executed successfully
Return message: Success
---------------------------------------------------------------------------------------------
Return values:
[
"Hello,FISCO BCOS"
]
---------------------------------------------------------------------------------------------
# 调用TableTest的insert接口插入记录，字段为name, item_id, item_name
[group:1]> call TableTest 0x5f248ad7e917cddc5a4d408cf18169d19c0990e5 insert "fruit" 1 "apple"
transaction hash: 0x64bfab495dc1f50c58d219b331df5a47577aa8afc16be926260238a9b0ec0fbb
---------------------------------------------------------------------------------------------
transaction status: 0x0
description: transaction executed successfully
---------------------------------------------------------------------------------------------
Output
Receipt message: Success
Return message: Success
---------------------------------------------------------------------------------------------
Event logs
Event: {"InsertResult":[1]}
# 调用TableTest的select接口查询记录
[group:1]> [group:1]> call TableTest 0x5f248ad7e917cddc5a4d408cf18169d19c0990e5 select "fruit"
---------------------------------------------------------------------------------------------
Return code: 0
description: transaction executed successfully
Return message: Success
---------------------------------------------------------------------------------------------
Return values:
[
[
"fruit"
],
[
1
],
[
"apple"
]
]
---------------------------------------------------------------------------------------------
注： TableTest.sol合约代码参考这里。
deployByCNS¶
运行deployByCNS，采用CNS部署合约。用CNS部署的合约，可用合约名直接调用。 参数：
合约路径：合约文件的路径，支持相对路径、绝对路径和默认路径三种方式。用户输入为文件名时，从默认目录获取文件，默认目录为:
contracts/solidity。合约版本号：部署的合约版本号。
# 部署HelloWorld合约1.0版
[group:1]> deployByCNS HelloWorld 1.0
transaction hash: 0xb994d8e510f147815bdf9838fda542e553c2fe981177ee7a97a0686b9619cfbb
contract address: 0xf485b9ccfffa668f4d7fac37c81c0cd63408188c
{
"code":1,
"msg":"Success"
}
# 部署HelloWorld合约2.0版
[group:1]> deployByCNS HelloWorld 2.0
transaction hash: 0x3132f73e5af72fce44c2e07185a04f554ac06ddd94119dcf798980695b0890a0
contract address: 0xf68a1aabfad336847e109c33ca471b192c93c0a9
{
"code":1,
"msg":"Success"
}
# 部署TableTest合约
[group:1]> deployByCNS TableTest 1.0
transaction hash: 0x288ccc6e166e43f5cd3bd563e00af48988e641196aaea57a59f0ab256e23c84e
contract address: 0x0fe221339e50c39aaefddfc3a9a26b4aeff23c63
{
"code":1,
"msg":"Success"
}
注：
部署用户编写的合约，可以将solidity合约文件放到控制台根目录的
contracts/solidity/目录下，然后进行部署即可。按tab键可以搜索contracts/solidity/目录下的合约名称。若需要部署的合约引用了其他合约或library库，引用格式为
import "./XXX.sol";。其相关引入的合约和library库均放在contracts/solidity/目录。如果合约引用了library库，library库文件的名称必须以
Lib字符串开始，以便于区分是普通合约与library库文件。library库文件不能单独部署和调用。
queryCNS¶
运行queryCNS，根据合约名称和合约版本号（可选参数）查询CNS表记录信息（合约名和合约地址的映射）。 参数：
合约名称：部署的合约名称。
合约版本号：(可选)部署的合约版本号。
[group:1]> queryCNS HelloWorld
---------------------------------------------------------------------------------------------
| version | address |
| 1.0 | 0xf485b9ccfffa668f4d7fac37c81c0cd63408188c |
| 2.0 | 0xf68a1aabfad336847e109c33ca471b192c93c0a9 |
---------------------------------------------------------------------------------------------
[group:1]> queryCNS HelloWorld 1.0
---------------------------------------------------------------------------------------------
| version | address |
| 1.0 | 0xf485b9ccfffa668f4d7fac37c81c0cd63408188c |
---------------------------------------------------------------------------------------------
callByCNS¶
运行callByCNS，采用CNS调用合约，即用合约名直接调用合约。 参数：
合约名称与合约版本号：合约名称与版本号用英文冒号分隔，例如
HelloWorld:1.0。当省略合约版本号时，例如HelloWorld，则调用最新版本的合约。合约接口名：调用的合约接口名。
参数：由合约接口参数决定。参数由空格分隔，其中字符串、字节类型参数需要加上双引号；数组参数需要加上中括号，比如[1,2,3]，数组中是字符串或字节类型，加双引号，例如[“alice”,”bob”]；布尔类型为true或者false。
# 调用HelloWorld合约1.0版，通过set接口设置name字符串
[group:1]> callByCNS HelloWorld:1.0 set "Hello,CNS"
transaction hash: 0x7ad2f34a13bbc2272d2d52fa46915e6f03136a6960d84a23478bee3c37e76ad6
---------------------------------------------------------------------------------------------
transaction status: 0x0
description: transaction executed successfully
---------------------------------------------------------------------------------------------
Output
Receipt message: Success
Return message: Success
---------------------------------------------------------------------------------------------
Event logs
Event: {}
# 调用HelloWorld合约2.0版，通过set接口设置name字符串
[group:1]> callByCNS HelloWorld:2.0 set "Hello,CNS2"
transaction hash: 0x41f8decbe137905824321da6c28a19d957e902cfad1e8078d797bc649c078d3e
---------------------------------------------------------------------------------------------
transaction status: 0x0
description: transaction executed successfully
---------------------------------------------------------------------------------------------
Output
Receipt message: Success
Return message: Success
---------------------------------------------------------------------------------------------
Event logs
Event: {}
# 调用HelloWorld合约1.0版，通过get接口获取name字符串
[group:1]> callByCNS HelloWorld:1.0 get
---------------------------------------------------------------------------------------------
Return code: 0
description: transaction executed successfully
Return message: Success
---------------------------------------------------------------------------------------------
Return values:
[
"Hello,CNS"
]
---------------------------------------------------------------------------------------------
# 调用HelloWorld合约最新版(即2.0版)，通过get接口获取name字符串
[group:1]> callByCNS HelloWorld get
---------------------------------------------------------------------------------------------
Return code: 0
description: transaction executed successfully
Return message: Success
---------------------------------------------------------------------------------------------
Return values:
[
"Hello,CNS2"
]
---------------------------------------------------------------------------------------------
registerCNS¶
注册合约至CNS。
参数：
合约路径: 合约文件的路径，支持相对路径、绝对路径和默认路径三种方式。用户输入为文件名时，从默认目录获取文件，默认目录为:
contracts/solidity。合约地址: 注册合约地址
合约版本号: 注册合约版本号
[group:1]> registerCNS HelloWorld 0xf19a7ec01f0b1adb16a033f0a30fb321ec6edcbf v1.0.0
{
"code":1,
"msg":"success"
}
addSealer¶
运行addSealer，将节点添加为共识节点。 参数：
节点nodeId
[group:1]> addSealer ea2ca519148cafc3e92c8d9a8572b41ea2f62d0d19e99273ee18cccd34ab50079b4ec82fe5f4ae51bd95dd788811c97153ece8c05eac7a5ae34c96454c4d3123
{
"code":1,
"msg":"success"
}
addObserver¶
运行addObserver，将节点添加为观察节点。 参数：
节点nodeId
[group:1]> addObserver ea2ca519148cafc3e92c8d9a8572b41ea2f62d0d19e99273ee18cccd34ab50079b4ec82fe5f4ae51bd95dd788811c97153ece8c05eac7a5ae34c96454c4d3123
{
"code":1,
"msg":"success"
}
removeNode¶
运行removeNode，节点退出。通过addSealer命令可以将退出的节点添加为共识节点，通过addObserver命令将节点添加为观察节点。 参数：
节点nodeId
[group:1]> removeNode ea2ca519148cafc3e92c8d9a8572b41ea2f62d0d19e99273ee18cccd34ab50079b4ec82fe5f4ae51bd95dd788811c97153ece8c05eac7a5ae34c96454c4d3123
{
"code":1,
"msg":"success"
}
setSystemConfigByKey¶
运行setSystemConfigByKey，以键值对方式设置系统参数。目前设置的系统参数支持tx_count_limit,tx_gas_limit, rpbft_epoch_sealer_num、rpbft_epoch_block_num和consensus_timeout。这些系统参数的键名可以通过tab键补全：
tx_count_limit：区块最大打包交易数
tx_gas_limit：交易执行允许消耗的最大gas数
rpbft_epoch_sealer_num: rPBFT系统配置，一个共识周期内选取的共识节点数目
rpbft_epoch_block_num: rPBFT系统配置，一个共识周期出块数目
consensus_timeout：PBFT共识过程中，每个区块执行的超时时间，默认为3s，单位为秒
参数：
key
value
[group:1]> setSystemConfigByKey tx_count_limit 100
{
"code":1,
"msg":"success"
}
getSystemConfigByKey¶
运行getSystemConfigByKey，根据键查询系统参数的值。 参数：
key
[group:1]> getSystemConfigByKey tx_count_limit
100
grantUserTableManager¶
运行grantUserTableManager，授权账户对用户表的写权限。 参数：
表名
账户地址
[group:1]> grantUserTableManager t_test 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
listUserTableManager¶
运行listUserTableManager，查询拥有对用户表写权限的账号列表。 参数：
表名
[group:1]> listUserTableManager t_test
---------------------------------------------------------------------------------------------
| address | enable_num |
| 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d | 2 |
---------------------------------------------------------------------------------------------
revokeUserTableManager¶
运行revokeUserTableManager，撤销账户对用户表的写权限。 参数：
表名
账户地址
[group:1]> revokeUserTableManager t_test 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
grantDeployAndCreateManager¶
运行grantDeployAndCreateManager，授权账户的部署合约和创建用户表权限。
参数：
账户地址
[group:1]> grantDeployAndCreateManager 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
listDeployAndCreateManager¶
运行listDeployAndCreateManager，查询拥有部署合约和创建用户表权限的账户列表。
[group:1]> listDeployAndCreateManager
---------------------------------------------------------------------------------------------
| address | enable_num |
| 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d | 2 |
---------------------------------------------------------------------------------------------
revokeDeployAndCreateManager¶
运行revokeDeployAndCreateManager，撤销账户的部署合约和创建用户表权限。 参数：
账户地址
[group:1]> revokeDeployAndCreateManager 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
grantNodeManager¶
运行grantNodeManager，授权账户的节点管理权限。参数：
账户地址
[group:1]> grantNodeManager 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
listNodeManager¶
运行listNodeManager，查询拥有节点管理的账户列表。
[group:1]> listNodeManager
---------------------------------------------------------------------------------------------
| address | enable_num |
| 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d | 2 |
---------------------------------------------------------------------------------------------
revokeNodeManager¶
运行revokeNodeManager，撤销账户的节点管理权限。 参数：
账户地址
[group:1]> revokeNodeManager 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
grantCNSManager¶
运行grantCNSManager，授权账户的使用CNS权限。参数：
账户地址
[group:1]> grantCNSManager 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
listCNSManager¶
运行listCNSManager，查询拥有使用CNS的账户列表。
[group:1]> listCNSManager
---------------------------------------------------------------------------------------------
| address | enable_num |
| 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d | 2 |
---------------------------------------------------------------------------------------------
revokeCNSManager¶
运行revokeCNSManager，撤销账户的使用CNS权限。参数：
账户地址
[group:1]> revokeCNSManager 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
grantSysConfigManager¶
运行grantSysConfigManager，授权账户的修改系统参数权限。参数：
账户地址
[group:1]> grantSysConfigManager 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
listSysConfigManager¶
运行listSysConfigManager，查询拥有修改系统参数的账户列表。
[group:1]> listSysConfigManager
---------------------------------------------------------------------------------------------
| address | enable_num |
| 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d | 2 |
---------------------------------------------------------------------------------------------
revokeSysConfigManager¶
运行revokeSysConfigManager，撤销账户的修改系统参数权限。参数：
账户地址
[group:1]> revokeSysConfigManager 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
grantContractWritePermission¶
运行grantContractWritePermission，添加账户对合约写接口的调用权限。参数：
合约地址
账户地址
[group:1]> grantContractWritePermission 0xc0ce097a5757e2b6e189aa70c7d55770ace47767 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
listContractWritePermission¶
运行listContractWritePermission，显示对某个合约的写接口有调用权限的账户。参数：
合约地址
[group:1]> listContractWritePermission 0xc0ce097a5757e2b6e189aa70c7d55770ace47767
---------------------------------------------------------------------------------------------
| address | enable_num |
| 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d | 11 |
---------------------------------------------------------------------------------------------
revokeContractWritePermission¶
运行revokeContractWritePermission，撤销账户对合约的写接口调用权限。参数：
合约地址
账户地址
[group:1]> revokeContractWritePermission 0xc0ce097a5757e2b6e189aa70c7d55770ace47767 0xc0d0e6ccc0b44c12196266548bec4a3616160e7d
{
"code":1,
"msg":"success"
}
[create sql]¶
运行create sql语句创建用户表，使用mysql语句形式。
# 创建用户表t_demo，其主键为name，其他字段为item_id和item_name
[group:1]> create table t_demo(name varchar, item_id varchar, item_name varchar, primary key(name))
Create 't_demo' Ok.
注意：
创建表的字段类型均为字符串类型，即使提供数据库其他字段类型，也按照字符串类型设置。
必须指定主键字段。例如创建t_demo表，主键字段为name。
表的主键与关系型数据库中的主键不是相同概念，这里主键取值不唯一，区块链底层处理记录时需要传入主键值。
可以指定字段为主键，但设置的字段自增，非空，索引等修饰关键字不起作用。
desc¶
运行desc语句查询表的字段信息，使用mysql语句形式。
# 查询t_demo表的字段信息，可以查看表的主键名和其他字段名
[group:1]> desc t_demo
{
"key":"name",
"valueFields":"item_id,item_name"
}
[insert sql]¶
运行insert sql语句插入记录，使用mysql语句形式。
[group:1]> insert into t_demo (name, item_id, item_name) values (fruit, 1, apple1)
Insert OK, 1 row affected.
注意：
插入记录sql语句必须插入表的主键字段值。
输入的值带标点符号、空格或者以数字开头的包含字母的字符串，需要加上双引号，双引号中不允许再用双引号。
[select sql]¶
运行select sql语句查询记录，使用mysql语句形式。
# 查询包含所有字段的记录
select * from t_demo where name = fruit
{item_id=1, item_name=apple1, name=fruit}
1 row in set.
# 查询包含指定字段的记录
[group:1]> select name, item_id, item_name from t_demo where name = fruit
{name=fruit, item_id=1, item_name=apple1}
1 row in set.
# 插入一条新记录
[group:1]> insert into t_demo values (fruit, 2, apple2)
Insert OK, 1 row affected.
# 使用and关键字连接多个查询条件
[group:1]> select * from t_demo where name = fruit and item_name = apple2
{item_id=2, item_name=apple2, name=fruit}
1 row in set.
# 使用limit字段，查询第1行记录，没有提供偏移量默认为0
[group:1]> select * from t_demo where name = fruit limit 1
{item_id=1, item_name=apple1, name=fruit}
1 row in set.
# 使用limit字段，查询第2行记录，偏移量为1
[group:1]> select * from t_demo where name = fruit limit 1,1
{item_id=2, item_name=apple2, name=fruit}
1 rows in set.
注意：
查询记录sql语句必须在where子句中提供表的主键字段值。
关系型数据库中的limit字段可以使用，提供两个参数，分别offset(偏移量)和记录数(count)。
where条件子句只支持and关键字，其他or、in、like、inner、join，union以及子查询、多表联合查询等均不支持。
输入的值带标点符号、空格或者以数字开头的包含字母的字符串，需要加上双引号，双引号中不允许再用双引号。
[update sql]¶
运行update sql语句更新记录，使用mysql语句形式。
[group:1]> update t_demo set item_name = orange where name = fruit and item_id = 1
Update OK, 1 row affected.
注意：
更新记录sql语句的where子句必须提供表的主键字段值。
输入的值带标点符号、空格或者以数字开头的包含字母的字符串，需要加上双引号，双引号中不允许再用双引号。
[delete sql]¶
运行delete sql语句删除记录，使用mysql语句形式。
[group:1]> delete from t_demo where name = fruit and item_id = 1
Remove OK, 1 row affected.
注意：
删除记录sql语句的where子句必须提供表的主键字段值。
输入的值带标点符号、空格或者以数字开头的包含字母的字符串，需要加上双引号，双引号中不允许再用双引号。
重要
执行`freezeContract`、`unfreezeContract`和`grantContractStatusManager`三个合约管理的控制台命令，需指定私钥启动控制台，用于进行操作权限判断。该私钥为部署指定合约时所用的账号私钥，即部署合约时也是指定私钥启动控制台。
freezeContract¶
运行freezeContract，对指定合约进行冻结操作。参数：
合约地址：部署合约可以获得合约地址，其中0x前缀非必须。
[group:1]> freezeContract 0xcc5fc5abe347b7f81d9833f4d84a356e34488845
{
"code":1,
"msg":"success"
}
unfreezeContract¶
运行unfreezeContract，对指定合约进行解冻操作。参数：
合约地址：部署合约可以获得合约地址，其中0x前缀非必须。
[group:1]> unfreezeContract 0xcc5fc5abe347b7f81d9833f4d84a356e34488845
{
"code":1,
"msg":"success"
}
grantContractStatusManager¶
运行grantContractStatusManager，用于已有权限账号给其他账号授予指定合约的合约管理权限。参数：
合约地址：部署合约可以获得合约地址，其中0x前缀非必须。
账号地址：tx.origin，其中0x前缀非必须。
[group:1]> grantContractStatusManager 0x30d2a17b6819f0d77f26dd3a9711ae75c291f7f1 0x965ebffc38b309fa706b809017f360d4f6de909a
{
"code":1,
"msg":"success"
}
revokeContractStatusManager¶
运行revokeContractStatusManager，用于撤销指定权限账号对指定合约的合约管理权限。参数：
合约地址：部署合约可以获得合约地址，其中0x前缀非必须。
账号地址：tx.origin，其中0x前缀非必须。
[group:1]> revokeContractStatusManager 0x30d2a17b6819f0d77f26dd3a9711ae75c291f7f1 0x965ebffc38b309fa706b809017f360d4f6de909a
{
"code":1,
"msg":"success"
}
getContractStatus¶
运行getContractStatus，查询指定合约的状态。参数：
合约地址：部署合约可以获得合约地址，其中0x前缀非必须。
[group:1]> getContractStatus 0xcc5fc5abe347b7f81d9833f4d84a356e34488845
The contract is available.
listContractStatusManager¶
运行listContractStatusManager，查询能管理指定合约的权限账号列表。参数：
合约地址：部署合约可以获得合约地址，其中0x前缀非必须。
[group:1]> listContractStatusManager 0x30d2a17b6819f0d77f26dd3a9711ae75c291f7f1
[
"0x0cc9b73b960323816ac5f52806257184c08b5ac0",
"0x965ebffc38b309fa706b809017f360d4f6de909a"
]
grantCommitteeMember¶
添加治理委员会委员，如果当前没有委员，则直接添加成功，否则判断投票账号是否有权限投票，如有则记录投票并检查投票是否生效。委员账号可以添加运维、管理链系统配置、节点增删等，详情参考这里。参数：
账号地址：投票添加该账号为委员
[group:1]> grantCommitteeMember 0x61d88abf7ce4a7f8479cff9cc1422bef2dac9b9a
{
"code":1,
"msg":"success"
}
revokeCommitteeMember¶
撤销治理委员会委员判断投票账号是否有权限投票，如有则记录投票并检查投票是否生效。参数：
账号地址：投票撤销该账号的委员权限
[group:1]> revokeCommitteeMember 0x61d88abf7ce4a7f8479cff9cc1422bef2dac9b9a
{
"code":1,
"msg":"success"
}
listCommitteeMembers¶
查询所有治理委员会委员。
[group:1]> listCommitteeMembers
---------------------------------------------------------------------------------------------
| address | enable_num |
| 0x61d88abf7ce4a7f8479cff9cc1422bef2dac9b9a | 1 |
| 0x85961172229aec21694d742a5bd577bedffcfec3 | 2 |
---------------------------------------------------------------------------------------------
updateThreshold¶
投票更新生效阈值，判断投票账号是否是委员，是则计票并判断是否生效。参数：
生效阈值：取值范围[0,99]
[group:1]> updateThreshold 75
{
"code":1,
"msg":"success"
}
queryCommitteeMemberWeight¶
查询治理委员会委员的票数。
[group:1]> queryCommitteeMemberWeight 0x61d88abf7ce4a7f8479cff9cc1422bef2dac9b9a
Account: 0x61d88abf7ce4a7f8479cff9cc1422bef2dac9b9a Weight: 1
updateCommitteeMemberWeight¶
投票更新委员账号的票数，检查投票账号是否有权限，有则计票并检查是否生效，生效后该委员账号投票操作相当于设置的票数。参数：
委员账号：被投票修改票数的委员账号
投票权重：希望修改的权重
[group:1]> updateCommitteeMemberWeight 0x61d88abf7ce4a7f8479cff9cc1422bef2dac9b9a 2
{
"code":1,
"msg":"success"
}
grantOperator¶
添加运维账号，运维角色拥有部署合约、创建用户表和管理CNS的权限，治理委员会委员可以添加运维，如果当前没有委员，则不限制。参数：
账号地址：添加该账号为运维
[group:1]> grantOperator 0x283f5b859e34f7fd2cf136c07579dcc72423b1b2
{
"code":1,
"msg":"success"
}
revokeOperator¶
撤销账号的运维权限，委员可以操作，如果当前没有委员，则不限制。参数：
账号地址：撤销该账号的运维权限
[group:1]> revokeOperator 0x283f5b859e34f7fd2cf136c07579dcc72423b1b2
{
"code":1,
"msg":"success"
}
listOperators¶
查询有运维权限的账号。
[group:1]> listOperators
---------------------------------------------------------------------------------------------
| address | enable_num |
| 0x283f5b859e34f7fd2cf136c07579dcc72423b1b2 | 1 |
---------------------------------------------------------------------------------------------
queryVotesOfThreshold¶
查询updateThreshold的投票情况:
[group:1]> queryVotesOfThreshold
The votes of the updateThreshold operation : {"0.100000":[{"block_limit":"10002","origin":"0x2eb1be0f52c0d00f9594a021240ea7fb027d7485"}]}
queryVotesOfMember¶
查询指定账户被选举为委员的投票情况，若没有任何委员投票，则返回null:
账户地址: 被查询的账户地址
[group:1]> queryVotesOfMember 0xc398d318662aa19487c405a45267ecd60115adec
queried account: 0xc398d318662aa19487c405a45267ecd60115adec
votes:{"grant":[{"block_limit":"10003","origin":"0x2eb1be0f52c0d00f9594a021240ea7fb027d7485"}]}
freezeAccount¶
运行freezeAccount，对指定账号进行冻结操作。对没有发送过交易的账号，冻结操作将提示该账号地址不存在。参数：
账号地址：tx.origin，其中0x前缀必须。
[group:1]> freezeAccount 0xcc5fc5abe347b7f81d9833f4d84a356e34488845
{
"code":1,
"msg":"success"
}
unfreezeAccount¶
运行unfreezeAccount，对指定账号进行解冻操作。对没有发送过交易的账号，解冻操作将提示该账号地址不存在。参数：
账号地址：tx.origin，其中0x前缀必须。
[group:1]> unfreezeAccount 0xcc5fc5abe347b7f81d9833f4d84a356e34488845
{
"code":1,
"msg":"success"
}
getAccountStatus¶
运行getAccountStatus，查询指定账号的状态。对没有发送过交易的账号，查询操作将提示该账号地址不存在。参数：
账号地址：tx.origin，其中0x前缀必须。
[group:1]> getAccountStatus 0xcc5fc5abe347b7f81d9833f4d84a356e34488845
The account is available.
listDeployContractAddress¶
列出指定合约名部署的所有合约地址， 列出部署指定合约产生的合约地址列表，参数：
contractNameOrPath: 合约名或合约绝对路径，用于指定合约;
recordNumber: 显示的合约地址列表长度，默认为20
# 获取部署HelloWorld合约产生的合约地址列表
[group:1]> listDeployContractAddress HelloWorld
0xe157185434183b276b9e5af7d0315a9829171281 2020-10-13 15:35:29
0x136b042e1fc480b03e1e5b075cbdfa52f5851a23 2020-10-13 15:35:22
0xd7d0b221bc984a20aa6b0fc098dad89888378e3a 2020-10-13 15:34:14
0x0fe221339e50c39aaefddfc3a9a26b4aeff23c63 2020-10-13 15:16:20
0x5f248ad7e917cddc5a4d408cf18169d19c0990e5 2020-10-13 12:28:23
0xf027fd91a51bd4844f17600c01e943058fc27482 2020-10-12 18:28:50
0x682b51f3c7f9a605fa2026b09fd2635a6fa562d9 2020-10-11 23:22:28
0xf68a1aabfad336847e109c33ca471b192c93c0a9 2020-10-11 22:53:07
0xf485b9ccfffa668f4d7fac37c81c0cd63408188c 2020-10-11 22:52:26
0x175b16a1299c7af3e2e49b97e68a44734257a35e 2020-10-11 22:49:25
0x7c6dc94e4e146cb13eb03dc98d2b96ac79ef5e67 2020-10-11 22:46:35
# 限制显示的合约地址列表长度为2
[group:1]> listDeployContractAddress HelloWorld 2
0xe157185434183b276b9e5af7d0315a9829171281 2020-10-13 15:35:29
0x136b042e1fc480b03e1e5b075cbdfa52f5851a23 2020-10-13 15:35:22
getCurrentAccount¶
获取当前账户地址。
[group:1]> getCurrentAccount
0x6fad87071f790c3234108f41b76bb99874a6d813
getCryptoType¶
获取当前控制台所连接的节点账本类型、SSL协议类型。
注解
非国密账本类型为
ECDSA，国密类型账本类型为SMOpenSSL协议类型为
ECDSA，国密SSL协议类型为SM
[group:1]> getCryptoType
ledger crypto type: ECDSA
ssl crypto type: ECDSA
getAvailableConnections¶
获取SDK连接的节点连接信息。
[group:1]> getAvailableConnections
[
127.0.0.1:20200,
127.0.0.1:20201
]
getGroupConnections¶
从SDK连接的节点列表中，筛选出启动控制台当前登录群组的节点列表信息。
[group:1]> getGroupConnections
[
127.0.0.1:20200,
127.0.0.1:20201
]
generateGroup¶
为指定节点动态创建一个新群组，参数：
endPoint: 接收创建新群组请求的区块链节点IP:Port信息，SDK连接的所有节点IP:Port信息可通过命令getAvailableConnections获取；groupId: 新创建的群组ID；timestamp: 新创建群组的创世块时间戳，可通过命令echo $(($(date '+%s')*1000))获取时间戳；sealerList: 新创建群组的共识节点列表，多个共识节点ID之间用空格分割。
为监听在本机20200端口的区块链节点创建新群组2的示例如下：
# 获取时间戳
$ echo $(($(date '+%s')*1000))
1590586645000
[group:1]> generateGroup 127.0.0.1:20200 2 1590586645000 b8acb51b9fe84f88d670646be36f31c52e67544ce56faf3dc8ea4cf1b0ebff0864c6b218fdcd9cf9891ebd414a995847911bd26a770f429300085f37e1131f36
GroupStatus{
code='0x1',
message='Group 2 generated successfully',
status='null'
}
generateGroupFromFile¶
通过新群组配置文件为指定节点列表创建新群组，配置文件指定了需要创建群组节点列表、新群组的共识列表以及创世块时间戳，群组配置示例group-generate-config.toml如下：
# The peers to generate the group
[groupPeers]
peers=["127.0.0.1:20200", "127.0.0.1:20201"]
# The consensus configuration of the generated group
[consensus]
# The sealerList
sealerList=["b8acb51b9fe84f88d670646be36f31c52e67544ce56faf3dc8ea4cf1b0ebff0864c6b218fdcd9cf9891ebd414a995847911bd26a770f429300085f37e1131f36","11e1be251ca08bb44f36fdeedfaeca40894ff80dfd80084607a75509edeaf2a9c6fee914f1e9efda571611cf4575a1577957edfd2baa9386bd63eb034868625f"]
[genesis]
# The genesis timestamp, It is recommended to set to the current utcTime, which must be greater than 0
timestamp = "1590586645000"
generateGroupFromFile命令的参数包括：
groupConfigFilePath: 群组配置文件路径，控制台conf/group-generate-config.toml是提供的群组配置文件模板，用户可根据实际场景拷贝、修改该配置模板，并加载修改后的群组配置文件；groupId: 新创建的群组ID。
[group:1]> generateGroupFromFile conf/group-generate-config.toml 3
* Result of 127.0.0.1:20200:
GroupStatus{
code='0x0',
message='Group 3 generated successfully',
status='null'
}
* Result of 127.0.0.1:20201:
GroupStatus{
code='0x0',
message='Group 3 generated successfully',
status='null'
}
startGroup¶
为指定节点启动群组，参数：
endPoint: 接收启动群组请求的区块链节点IP:Port信息，SDK连接的所有节点IP:Port信息可通过命令getAvailableConnections获取；groupId：启动的群组ID。
启动群组2的控制台命令示例如下：
# 获取127.0.0.1:20200当前群组列表
[group:1]> getGroupList 127.0.0.1:20200
[1]
[group:1]> startGroup 127.0.0.1:20200 2
GroupStatus{
code='0x0',
message='Group 2 started successfully',
status='null'
}
# 127.0.0.1:20200的群组2启动成功后，群组列表中新增群组2
[group:1]> getGroupList 127.0.0.1:20200
[1, 2]
stopGroup¶
为指定节点停止群组，参数：
endPoint: 接收停止群组请求的区块链节点IP:Port信息，SDK连接的所有节点IP:Port信息可通过命令getAvailableConnections获取；groupId：停止的群组ID。
停止群组2的控制台命令示例如下：
# 获取127.0.0.1:20200当前群组列表
[group:1]> getGroupList 127.0.0.1:20200
[1, 2]
[group:1]> stopGroup 127.0.0.1:20200 2
GroupStatus{
code='0x0',
message='Group 2 stopped successfully',
status='null'
}
# 127.0.0.1:20200的群组2停止成功后，群组列表中群组2被移出
[group:1]> getGroupList 127.0.0.1:20200
[1]
removeGroup¶
为指定节点删除群组，参数：
endPoint: 接收删除群组请求的区块链节点IP:Port信息，SDK连接的所有节点IP:Port信息可通过命令getAvailableConnections获取；groupId：删除的群组ID。
删除群组2的控制台命令示例如下：
# 删除127.0.0.1:20200的群组2
[group:1]> removeGroup 127.0.0.1:20200 2
GroupStatus{
code='0x0',
message='Group 2 deleted successfully',
status='null'
}
# 删除127.0.0.1:20200的群组2后，尝试启动被删除的群组，启动失败
[group:1]> startGroup 127.0.0.1:20200 2
GroupStatus{
code='0x5',
message='Group 2 has been deleted',
status='null'
}
[group:1]> getGroupList 127.0.0.1:20200
[1]
recoverGroup¶
为指定节点恢复指定群组，参数：
endPoint: 接收群组恢复请求的区块链节点IP:Port信息，SDK连接的所有节点IP:Port信息可通过命令getAvailableConnections获取；groupId：恢复的群组ID。
# 获取127.0.0.1:20200的当前群组列表
[group:1]> getGroupList 127.0.0.1:20200
[1]
# 恢复127.0.0.1:20200的群组2
[group:1]> recoverGroup 127.0.0.1:20200 2
GroupStatus{
code='0x0',
message='Group 2 recovered successfully',
status='null'
}
# 启动127.0.0.1:20200的群组2
[group:1]> startGroup 127.0.0.1:20200 2
GroupStatus{
code='0x0',
message='Group 2 started successfully',
status='null'
}
# 获取127.0.0.1:20200的当前群组列表, 新增了群组2
[group:1]> getGroupList 127.0.0.1:20200
[1, 2]
getBatchReceiptsByBlockNumberAndRange¶
指定块高和交易回执范围，获取指定区块高度、指定范围的交易回执:
blockNumber: 请求获取的交易回执所在的区块高度from: 请求的批量回执的起始索引，可不填，默认值为0count: 请求的批量回执数目，可不填，默认值为-1，设置为-1时，返回区块内所有交易回执
[group:1]> getBatchReceiptsByBlockNumberAndRange 1
TransactionReceiptsInfo{
blockInfo=BlockInfo{
receiptRoot='0x67182babfe1500a8ec442a8b9548e7d0d912af4943c3d549bdf9ed0c76fe8c11',
blockNumber='0x1',
blockHash='0x5eb495f6fa457dbcaf6323630a257a65a7085e01087421b7191d8efec69da0c0',
receiptsCount='0x1'
},
transactionReceipts=[
TransactionReceipt{
transactionHash='0xa3ce50e3f03d3282e21248172efd1345b9eb15b281791b499f2e6c7bbe464667',
transactionIndex='0x0',
root='null',
blockNumber='null',
blockHash='null',
from='0x2eb1be0f52c0d00f9594a021240ea7fb027d7485',
to='0x0000000000000000000000000000000000001008',
gasUsed='0x589b',
contractAddress='0x0000000000000000000000000000000000000000',
logs=[
],
logsBloom='null',
status='0x0',
statusMsg='null',
input='null',
output='0x0000000000000000000000000000000000000000000000000000000000000001',
txProof=null,
receiptProof=null
}
]
}
getBatchReceiptsByBlockHashAndRange¶
指定区块哈希和交易回执范围，获取指定区块哈希、指定范围的交易回执:
blockHash: 请求获取的交易回执所在的区块哈希from: 请求的批量回执的起始索引，可不填，默认值为0count: 请求的批量回执数目，可不填，默认值为-1，设置为-1时，返回区块内所有交易回执
[group:1]> getBatchReceiptsByBlockHashAndRange 0x5eb495f6fa457dbcaf6323630a257a65a7085e01087421b7191d8efec69da0c0
TransactionReceiptsInfo{
blockInfo=BlockInfo{
receiptRoot='0x67182babfe1500a8ec442a8b9548e7d0d912af4943c3d549bdf9ed0c76fe8c11',
blockNumber='0x1',
blockHash='0x5eb495f6fa457dbcaf6323630a257a65a7085e01087421b7191d8efec69da0c0',
receiptsCount='0x1'
},
transactionReceipts=[
TransactionReceipt{
transactionHash='0xa3ce50e3f03d3282e21248172efd1345b9eb15b281791b499f2e6c7bbe464667',
transactionIndex='0x0',
root='null',
blockNumber='null',
blockHash='null',
from='0x2eb1be0f52c0d00f9594a021240ea7fb027d7485',
to='0x0000000000000000000000000000000000001008',
gasUsed='0x589b',
contractAddress='0x0000000000000000000000000000000000000000',
logs=[
],
logsBloom='null',
status='0x0',
statusMsg='null',
input='null',
output='0x0000000000000000000000000000000000000000000000000000000000000001',
txProof=null,
receiptProof=null
}
]
}
附录：合约参数输入规则¶
控制台在部署、调用合约时，涉及参数输入：
包含多个参数时，各参数使用空格分开。 注意:不同参数之间使用空格分离，复杂参数内部不要出现空格，否则会被控制台分割，当做不同参数处理
另外对于一些复杂特殊的参数，有一些特殊的规则:
二进制类型:
bytes、bytes1、…、bytes32控制台的输入都会当做文本处理，无法直接接收二进制数据，可以将二进制数据转换为
hex字符串，或者Base64格式，格式如下:hex://xxxxxxxxxxxxxxxxxbase64://xxxxxxxxxxxxxxxxx
数组类型:
数组按照
[元素1,元素2,...,元素N]的格式，[]作为数组标记，中间的元素使用逗号分割注意:数组整体作为一个参数，不要在中间包含空格
例如:
int256[]: [1,2,3,4]string[3]: [“a”,”b”,”c”]
结构体
struct类型:结构体类型参数支持两种格式:
数组方式
依次将结构体每个成员的值组成一个数组，例如:
struct Person { string name; string address; int age; }
假如Person对象:
{name: "XiaoWang", address: "ShenZhen", age: 18}，控制台输入Person对象格式:["XiaoWang","ShenZhen",18]键值对字符串 构造结构体对应的键值对
JSON字符串, 同样以上面的Person对象为例，按照JSON方式输入:{"name":"XiaoWang","address":"ShenZhen","age":111}
复杂数据类型
更复杂的数据类型由普通类型嵌套生成，同样遵循之前的规则，按照对应的规则对参数进行嵌套即可