cita-sdk-java

null

License	License The Apache License, Version 2.0
Categories	Categories Tape Data Data Structures
GroupId	GroupId com.cryptape.cita
ArtifactId	ArtifactId utils
Last Version	Last Version 1.0.0
Release Date	Release Date Oct 28, 2019
Type	Type jar
Description	Description cita-sdk-java null
Project URL	Project URL https://github.com/cryptape/cita-sdk-java.git
Source Code Management	Source Code Management https://github.com/cryptape/cita-sdk-java.git

Download utils

Filename	Size
utils-1.0.0.pom
utils-1.0.0.jar	12 KB
utils-1.0.0-tests.jar	8 KB
utils-1.0.0-sources.jar	6 KB
utils-1.0.0-javadoc.jar	54 KB
Browse

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/com.cryptape.cita/utils/ -->
<dependency>
    <groupId>com.cryptape.cita</groupId>
    <artifactId>utils</artifactId>
    <version>1.0.0</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/com.cryptape.cita/utils/
implementation 'com.cryptape.cita:utils:1.0.0'

Gradle Kotlin

// https://jarcasting.com/artifacts/com.cryptape.cita/utils/
implementation ("com.cryptape.cita:utils:1.0.0")

Apache Buildr

'com.cryptape.cita:utils:jar:1.0.0'

Apache Ivy

<dependency org="com.cryptape.cita" name="utils" rev="1.0.0">
  <artifact name="utils" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='com.cryptape.cita', module='utils', version='1.0.0')
)

Scala SBT

libraryDependencies += "com.cryptape.cita" % "utils" % "1.0.0"

Leiningen

[com.cryptape.cita/utils "1.0.0"]

Dependencies

compile (1)

Group / Artifact	Type	Version
org.bouncycastle : bcprov-jdk15on	jar	1.54

test (2)

Group / Artifact	Type	Version
junit : junit	jar	4.11
org.mockito : mockito-core	jar	1.10.19

Project Modules

There are no modules declared in this project.

cita-sdk-java

English
中文

Introduction

cita-sdk-java, originally adapted from Ethereum web3j, is a Java library for working with Smart Contract and integrating with clients on CITA.

For detailed documentation, see documentation.

Features

Complete implementation of CITA JSON-RPC API over HTTP.
Auto-generation of Java smart contract wrappers to create, deploy, transact with and call smart contracts from native Java code (Solidity and Truffle definition formats supported).
Android compatible.

Getting Started

Prerequisites

Java 8
Gradle 5.0

Install

Install from repositories:
maven

<dependency>
  <groupId>com.citahub.cita</groupId>
  <artifactId>core</artifactId>
  <version>20.2.0</version>
</dependency>

Gradle

compile 'com.citahub.cita:core:20.2.0'

Install manually If you want to generate the jar and import manually.

git clone https://github.com/citahub/cita-sdk-java.git
gradle shadowJar

CITA Test net

Use CITA test net (recommended): https://testnet.citahub.com is provided as a test net.

Or build your own CITA net: Please find more information in CITA.

Get started

Deploy smart contract

Similar as Ethereum, smart contracts are deployed in CITA network by sending transactions. CITA transaction is defined in Transaction.java.
In CITA transaction, there are 3 special parameters:

nonce: generated randomly or depend on specific logic to avoid replay attack.
quota: transaction execution fee for operation, like gasPrice * gasLimit in Ethereum.
valid_until_block: timeout mechanism which should be set in (currentHeight, currentHeight + 100]. Transaction will be discarded beyond valid_until_block.

Please see the example below for a smart contract deployment.

Generate binary file for the contract by below command:

$solc example.sol --bin

Construct a transaction with generated binary code and other 3 parameters.

String contractCode = "6080604052600160005534801561001557600080fd5b5060df806100246000396000f3006080604052600436106049576000357c0100000000000000000000000000000000000000000000000000000000900463ffffffff16806360fe47b114604e5780636d4ce63c146078575b600080fd5b348015605957600080fd5b5060766004803603810190808035906020019092919050505060a0565b005b348015608357600080fd5b50608a60aa565b6040518082815260200191505060405180910390f35b8060008190555050565b600080549050905600a165627a7a723058202dd6056ea84968f05202910ca070fe13f6f46ff5507867f313d9c98bf2d2e55c0029";
CITAj service = CITAj.build(new HttpService("https://testnet.citahub.com"));
AppMetaData appMetaData;
appMetaData = service.appMetaData(DefaultBlockParameter.valueOf("latest")).send();
String chainIdHex = appMetaData.getAppMetaDataResult().getChainIdV1();
BigInteger chainId = new BigInteger(chainIdHex.substring(2), 16);
int version = appMetaData.getAppMetaDataResult().getVersion();
long currentHeight = service.appBlockNumber().send().getBlockNumber().longValue();
long validUntilBlock = currentHeight + 80;
Random random = new Random(System.currentTimeMillis());
String nonce = String.valueOf(Math.abs(random.nextLong()));
long quota = 1000000;
Transaction tx = Transaction.createContractTransaction(nonce, quota, validUntilBlock, version, chainId, "0", contractCode);

Sign the transaction with sender's private key and send it to CITA net.

String privateKey = "0x5f0258a4778057a8a7d97809bd209055b2fbafa654ce7d31ec7191066b9225e6"; // your private key
String rawTx = tx.sign(privateKey);
AppSendTransaction result = service.appSendRawTransaction(rawTx).send();

Please be attention that all transactions need to be signed since CITA only supports method sendRawTransaction rather than sendTransaction.

Call functions in smart contract

In CITA smart contract call, like contract deployment, a transaction needs to be created with 2 more parameters:

contract address: address of the deployed contract.
functionCallData: ABI of function and parameter.

After contract deployed, contract address can be fetched from TransactionReceipt. functionCallData is encoded from functionName and parameters by contract ABI. For example, functionCallData of function set() with parameter 1 is 60fe47b10000000000000000000000000000000000000000000000000000000000000001.

//get receipt and address from transaction
String txHash = result.getSendTransactionResult().getHash();
TransactionReceipt txReceipt = service.appGetTransactionReceipt(txHash).send().getTransactionReceipt();
String contractAddr = txReceipt.getContractAddress();

//sign and send the transaction
List<Type> inputParameters = Arrays.asList(new Uint(BigInteger.valueOf(4l)));
String funcData = CITASystemContract.encodeFunction("set", inputParameters);
Transaction tx = new Transaction(contractAddr, nonce, 10000000L, validUntilBlock, version, chainId, "0", funcData);
String rawTx = tx.sign(privateKey);
String txHash =  service.appSendRawTransaction(rawTx).send().getSendTransactionResult().getHash();

Please check TokenTransactionTest.java to see a complete example for smart contract deployment and function invocation.

Working with smart contract with cita-sdk-java wrapper

Besides interacting with smart contracts by sending transactions with binary code, cita-sdk-java provides a tool to help to convert solidity contract to a Java class from which smart contracts can be deployed and called.

Download cita jar file from release page or run gradle shadowJar to generate jars so that the tool can be found under build/libs. Name of the tool is cita-sdk-$version.jar.

Usage of cita-sdk-$version is shown below:

$ java -jar cita-sdk-20.2.0.jar solidity generate [--javaTypes|--solidityTypes] /path/to/{smart-contract}.bin /path/to/{smart-contract}.abi -o /path/to/src/main/java -p {package-path}

Example generate Java class from Token.sol, Token.bin and Token.abi under /tests/src/main/resources:

java -jar build/libs/cita-sdk-20.2.0.jar solidity generate tests/src/main/resources/Token.bin tests/src/main/resources/Token.abi -o tests/src/main/java/ -p com.citahub.cita.tests

Token.java will be created from commands above and class Token can be used with TransactionManager to deploy and call smart contract Token. Please be attention that TransactionManager is supposed to be used as TransactionManager for transaction creation in CITA network. Please check TokenCodegenTest.java for a complete example.

Working with smart contract with cita-sdk-java Account (Test)

cita-sdk-java provides interface Account for smart contract manipulations. With parameters of smart contract's name, address, method and method's arguments, smart contracts can be deployed and called through the interface without exposing extra java, bin or abi file to developers.

Method of smart contract deployment:

// Deploy contract in sync and async way.
public AppSendTransaction deploy(File contractFile, String nonce, BigInteger quota)

public Future<AppSendTransaction> deployAsync(File contractFile, String nonce, BigInteger quota)

Method of smart contract method call:

public Object callContract(String contractAddress, String funcName, String nonce, BigInteger quota, Object... args)

//function is a encapsulation of method including name, argument datatypes, return type and other info.
public Object callContract(String contractAddress, AbiDefinition functionAbi, String nonce, BigInteger quota, Object... args)

While contract file is required when first deploy the contract, cita-sdk-java can get the abi file according to address when call methods in deployed contract. Please find complete code in TokenAccountTest.

Contributing

Creating a Bug Report

open a new issue: https://github.com/citahub/cita-sdk-java/issues/new

with your version info

Tech Stack

Back end

Java

Version: 8
Building: gradle-v5.0

Coding style

coding style guide: Google Shell Style guide:

https://google.github.io/styleguide/javaguide.html

Installing the coding style settings in Intellij

Download the intellij-java-google-style.xml file from the http://code.google.com/p/google-styleguide/ repo.
go into Preferences -> Editor -> Code Style. Click on Manage and import the downloaded Style Setting file. Select GoogleStyle as new coding style.

Installing the coding style settings in Eclipse

Download the eclipse-java-google-style.xml file from the http://code.google.com/p/google-styleguide/ repo.
Under Window/Preferences select Java/Code Style/Formatter. Import the settings file by selecting Import.

Commit your changes

Workflow

GitHub Flow, Understanding the GitHub flow

git style guide

use git-style-guide for Branches, Commits,Messages, Merging

Versioning

vx.y.z

x.y Follow the version number of CITA
z Defined by SDK itself：changed by fixing or adding features

简介

cita-sdk-java 是对以太坊 Web3j 进行改写，适配 CITA 的一个 Java 开发包。cita-sdk-java 集成了与 CITA 客户端交互的功能，可以用来对 CITA 发送交易，系统配置，信息查询。

开发请参考详细文档。

特性

通过 HTTP 协议，实现了 CITA 所定义的所有 JSON-RPC 方法。
可以通过 Solidity 智能合约生成该合约的 Java 类。这个智能合约的 Java 类作为 java 对智能合约的包裹层，可以使开发和通过 java 方便地对智能合约进行部署和合约方法的调用（支持Solidity 和 Truffle 的格式）。
适配安卓

开始

预装组件

Java 8
Gradle 5.0

安装

通过远程仓库安装：

<dependency>
  <groupId>com.citahub.cita</groupId>
  <artifactId>core</artifactId>
  <version>20.2.0</version>
</dependency>

Gradle

compile 'com.citahub.cita:core:20.2.0'

手动安装
如果你想使用最新的 CITA，编译 CITA 生成 jar 包，并手动引入。

git clone https://github.com/citahub/cita-sdk-java.git
gradle shadowJar

CITA 测试网络

使用 CITA 测试网络（推荐）：
https://testnet.citahub.com

或者可以部署你自己的 CITA：
如果需要了解怎么部署 CITA 网络，请查阅CITA。

快速教程

部署智能合约

与以太坊类似，智能合约是通过发送交易来部署的。CITA 交易对象定义在 Transaction.java。在 CITA 交易中，有三个特殊的参数：

nonce：随机数或者通过特定的逻辑生成的随机信息，nonce是为了避免重放攻击。
quota：交易执行费用，也就是矿工费，就像以太坊中的 gasPrice * gasLimit。
valid_until_block：超时机制，valid_until_block 可以定义的范围是 (currentHeight, currentHeight + 100]。交易在valid_until_block之后会作废。

以下是一个智能合约部署的例子。

通过 solc 生成智能合约的二进制文件，命令如下：

$solc example.sol --bin

根据生成的二进制文件和其他3个参数构造一个交易，代码如下：

String contractCode = "6080604052600160005534801561001557600080fd5b5060df806100246000396000f3006080604052600436106049576000357c0100000000000000000000000000000000000000000000000000000000900463ffffffff16806360fe47b114604e5780636d4ce63c146078575b600080fd5b348015605957600080fd5b5060766004803603810190808035906020019092919050505060a0565b005b348015608357600080fd5b50608a60aa565b6040518082815260200191505060405180910390f35b8060008190555050565b600080549050905600a165627a7a723058202dd6056ea84968f05202910ca070fe13f6f46ff5507867f313d9c98bf2d2e55c0029";
CITAj service = CITAj.build(new HttpService("https://testnet.citahub.com"));
AppMetaData appMetaData;
appMetaData = service.appMetaData(DefaultBlockParameter.valueOf("latest")).send();
String chainIdHex = appMetaData.getAppMetaDataResult().getChainIdV1();
BigInteger chainId = new BigInteger(chainIdHex.substring(2), 16);
int version = appMetaData.getAppMetaDataResult().getVersion();
long currentHeight = service.appBlockNumber().send().getBlockNumber().longValue();
long validUntilBlock = currentHeight + 80;
Random random = new Random(System.currentTimeMillis());
String nonce = String.valueOf(Math.abs(random.nextLong()));
long quota = 1000000;
Transaction tx = Transaction.createContractTransaction(nonce, quota, validUntilBlock, version, chainId, "0", contractCode);

用发送者的私钥对交易进行签名然后发送到 CITA 网络，代码如下：

String privateKey = "0x5f0258a4778057a8a7d97809bd209055b2fbafa654ce7d31ec7191066b9225e6"; // your private key
String rawTx = tx.sign(privateKey);
AppSendTransaction result = service.appSendRawTransaction(rawTx).send();

请注意因为 CITA 只支持 sendRawTransaction 方法而不是 sendTransaction ，所以所有发送给 CITA 的交易都需要被签名。

调用智能合约的函数

在 CITA 中，正如智能合约的部署，智能合约中函数的调用也是通过发送交易来实现的，调用合约函数的交易是通过两个参数构造的：

合约地址：已部署合约的地址。
函数编码数据：函数以及入参的 ABI 的编码后数据。

智能合约成功部署以后，可以通过交易回执得到合约地址。以下是调用合约函数的例子，在例子中，functionCallData 通过对合约 ABI 中的函数名和入参编码得到。入参为 1 的set() 函数的编码数据 functionCallData 是 60fe47b10000000000000000000000000000000000000000000000000000000000000001.

//get receipt and address from transaction
String txHash = result.getSendTransactionResult().getHash();
TransactionReceipt txReceipt = service.appGetTransactionReceipt(txHash).send().getTransactionReceipt();
String contractAddr = txReceipt.getContractAddress();

//sign and send the transaction
List<Type> inputParameters = Arrays.asList(new Uint(BigInteger.valueOf(4l)));
String funcData = CITASystemContract.encodeFunction("set", inputParameters);
Transaction tx = new Transaction(contractAddr, nonce, 10000000L, validUntilBlock, version, chainId, "0", funcData);
String rawTx = tx.sign(privateKey);
String txHash =  service.appSendRawTransaction(rawTx).send().getSendTransactionResult().getHash();

请在 TokenTransactionTest.java 中查看完整代码。

通过 cita-sdk-java 中的 wrapper 与智能合约交互

以上例子展示了直接通过合约二进制码和函数的编码构造交易，并且发送与链上合约进行交互。除此方法以外，cita-sdk-java 提供了 codeGen 工具可以通过 solidity 合约生成 java 类。通过 cita-sdk-java 生成的 java 类，可以方便对合约进行部署和函数调用。

在 release 页面下载 cita-sdk-java 的 jar 包，或者在源项目中运行 gradle shadowJar 生成 jar 包，jar包会在 build/libs 中生成，名字是 cita-sdk-$version.jar。

solidity 合约转化为 java 类操作如下：

$ java -jar cita-sdk-20.2.0.jar solidity generate [--javaTypes|--solidityTypes] /path/to/{smart-contract}.bin /path/to/{smart-contract}.abi -o /path/to/src/main/java -p {package-path}

这个例子通过 Token.sol, Token.bin and Token.abi 这三个文件在 tests/src/main/resources 生成对应的 java 类，命令如下：

java -jar build/libs/cita-sdk-20.2.0.jar solidity generate tests/src/main/resources/Token.bin tests/src/main/resources/Token.abi -o tests/src/main/java/ -p com.citahub.cita.tests

Token.java 会通过以上命令生成， Token 可以与 TransactionManager 一起使用来和 Token 合约交互。请注意在 CITA 中应该使用 TransactionManager 而不是 TransactionManager。请在 TokenCodegenTest.java 查看完整代码.

通过 CITAj 中的 Account 与智能合约交互（测试阶段）

cita-sdk-java 还提供了接口 Account 与智能合约交互。通过智能合约的名字，地址，函数名和函数入参，Account 可以进行合约的部署和合约函数的调用。通过 Account 这个方式，开发者无需进行合约二进制文件和 abi 细节处理。

合约部署示例代码：

// Deploy contract in sync and async way.
public AppSendTransaction deploy(File contractFile, String nonce, BigInteger quota)

public Future<AppSendTransaction> deployAsync(File contractFile, String nonce, BigInteger quota)

合约函数调用示例代码：

public Object callContract(String contractAddress, String funcName, String nonce, BigInteger quota, Object... args)

//function is a encapsulation of method including name, argument datatypes, return type and other info.
public Object callContract(String contractAddress, AbiDefinition functionAbi, String nonce, BigInteger quota, Object... args)

虽然在第一次部署合约的时候需要提供合约文件，但是在以后调用合约函数的时候 cita-sdk-java 通过 CITA 提供的 getAbi 接口根据合约地址得到对应的 abi。
请在 TokenAccountTest 中查看完整代码。

参与贡献

报告Bug

提交 issue: https://github.com/citahub/cita-sdk-java/issues/new 记得声明所使用软件的版本信息

技术栈

Back end

Java

Version: 8
Building: gradle-v5.0

编码规范

使用《Google java编程规范》作为我们的编码规范:

英文版: https://google.github.io/styleguide/javaguide.html
中文版: https://jervyshi.gitbooks.io/google-java-styleguide-zh/content/

Installing the coding style settings in Intellij

Download the intellij-java-google-style.xml file from the http://code.google.com/p/google-styleguide/ repo.
go into Preferences -> Editor -> Code Style. Click on Manage and import the downloaded Style Setting file. Select GoogleStyle as new coding style.

Installing the coding style settings in Eclipse

Download the eclipse-java-google-style.xml file from the http://code.google.com/p/google-styleguide/ repo.
Under Window/Preferences select Java/Code Style/Formatter. Import the settings file by selecting Import.

代码提交规范

代码提交流程

GitHub Flow, Understanding the GitHub flow

git style guide

我们要求遵守 git-style-guide 中的规则来进行分支创建、提交以及合并操作。

版本规则

vx.y.z

x.y 跟随 CITA 的版本号；
z 由 SDK 自己定义：修复或增加feature 则变化

Cryptape

We build trust.

Versions

Version
1.0.0 Oct 28, 2019
0.25.0 Oct 16, 2019
0.24.1 Aug 15, 2019
0.24.0 May 30, 2019
0.23.0 May 5, 2019
0.22.3 Apr 10, 2019
0.22.1 Apr 1, 2019
0.21 Feb 18, 2019
0.20.3.1 Jan 18, 2019

cita-sdk-java

License

Categories

GroupId

ArtifactId

Last Version

Release Date

Type

Description

Project URL

Source Code Management

Download utils

How to add to project

Dependencies

compile (1)

test (2)

Project Modules

cita-sdk-java

Introduction

Features

Getting Started

Prerequisites

Install

CITA Test net

Get started

Deploy smart contract

Call functions in smart contract

Working with smart contract with cita-sdk-java wrapper

Working with smart contract with cita-sdk-java Account (Test)

Contributing

Creating a Bug Report

Tech Stack

Back end

Coding style

Installing the coding style settings in Intellij

Installing the coding style settings in Eclipse

Commit your changes

Workflow

git style guide

Versioning

简介

特性

开始

预装组件

安装

CITA 测试网络

快速教程

部署智能合约

调用智能合约的函数

通过 cita-sdk-java 中的 wrapper 与智能合约交互

通过 CITAj 中的 Account 与智能合约交互（测试阶段）

参与贡献

报告Bug

技术栈

Back end

编码规范

Installing the coding style settings in Intellij

Installing the coding style settings in Eclipse

代码提交规范

代码提交流程

git style guide

版本规则

Cryptape

Versions