Casper BLOCKCHAIN component

Since Camel 3.14.2

Both producer and consumer are supported.

Producer performs RPC calls to Casper blockchaine like querying blocks, deploys, accounts.

Consumer polls Casper Event Stream Server (port 9999).

The Casper blockchain component uses the Casper SDK API and allows you to interact with Casper Network nodes

Maven users will need to add the following dependency to their pom.xml for this component:

<dependency>
    <groupId>io.caspercommunity</groupId>
    <artifactId>camel-casper</artifactId>
    	<version>3.14.2</version>
    <!-- use the same version as your Camel core version -->
</dependency>

URI FORMAT

casper://<local/remote host:port or local IPC path>[?options]

CONFIGURING OPTIONS

Camel components are configured on two separate levels:

• component level
• endpoint level

CONFIGURING COMPONENT OPTIONS

The component level is the highest level which holds general and common configurations that are inherited by the endpoints. For example a component may have security settings, credentials for authentication, urls for network connection and so forth.

Some components only have a few options, and others may have many. Because components typically have pre configured defaults that are commonly used, then you may often only need to configure a few options on a component; or none at all.

Configuring components can be done with the Component DSL, in a configuration file (application.properties|yaml), or directly with Java code.

CONFIGURING ENDPOINT OPTIONS

Where you find yourself configuring the most is on endpoints, as endpoints often have many options, which allows you to configure what you need the endpoint to do. The options are also categorized into whether the endpoint is used as consumer (from) or as a producer (to), or used for both.

Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL as a type safe way of configuring endpoints.

A good practice when configuring options is to use Property Placeholders, which allows to not hardcode urls, port numbers, sensitive information, and other settings. In other words placeholders allows to externalize the configuration from your code, and gives more flexibility and reuse.

The following two sections lists all the options, firstly for the component followed by the endpoint.

COMPONENT OPTIONS

The Casper Blockchain component supports 11 options, which are listed below.

Name	Description	Default	Type
configuration (producer)	Default configuration.		CasperConfiguration
operation (producer)	RPC operation to use.
event (consumer)	sse event to track.
casperService (common)	Casper RPC API		CasperService
deployHash (producer)	Hash of a deploy in the blockchain		String
blockHash (producer)	Hash of a block in the blockchain		String
blockHeight (producer)	Height of a block in the blockchain		String
publicKey (producer)	Account publick key		String
key (producer)	casper_types::Key as formatted string		String
path (producer)	Path components starting from the key as base		String
stateRootHash (producer)	state_Root_Hash : an identifier of the current network state		String
purseUref (producer)	purseUref : URef of an account main purse		String
dictionaryItemKey (producer)	dictionaryItemKey : dictionary item key formatted as a string		String
seedUref (producer)	seedUref : dictionary's seed URef formatted as string		String

ENDPOINT OPTIONS

The Casper Blockchain endpoint is configured using URI syntax:

casper:nodeUrl

with the following path and query parameters:

Name	Description	Default	Type
nodeUrl (common)	Required, sets the node url.		String

QUERY PARAMETERS (11 PARAMETERS)

Name	Description	Default	Type
configuration (producer)	Default configuration.		CasperConfiguration
operation (producer)	Rpc operation to use.
event (consumer)	sse event to track.
casperService (common)	Casper RPC API		CasperService
deployHash (producer)	Hash of a deploy in the blockchain		String
blockHash (producer)	Hash of a block in the blockchain		String
blockHeight (producer)	Height of a block in the blockchain		String
publicKey (producer)	Account publick key		String
key (producer)	casper_types::Key as formatted string		String
path (producer)	Path components starting from the key as base		String
stateRootHash (producer)	state_Root_Hash : an identifier of the current network state		String
purseUref (producer)	purseUref : URef of an account main purse		String
dictionaryItemKey (producer)	dictionaryItemKey : dictionary item key formatted as a string		String
seedUref (producer)	seedUref : dictionary's seed URef formatted as string		String

Producer

Camel Producer component performs RPC calls to Casper blockchain. It supports the following operations (as per node version 1.4)

Operation	Description
NETWORK_PEERS	returns a list of casper network connected pairs
NODE_STATUS	returns the status of a given node in casper network
DEPLOY	returns a deploy
LAST_BLOCK	returns the last minted block from the blockchain
BLOCK	returns a block from the blockchain
LAST_BLOCK_TRANSFERS	returns the list of transfers within the last minted block from the blockchain
BLOCK_TRANSFERS	returns the list of transfers within a given block
STATE_ROOT_HASH	returns the current state root hash
ACCOUNT_INFO	returns the current state root hash
AUCTION_INFO	returns an AuctionState object that contains the bids and validators
ERA_INFO	returns an EraSummary object
STATE_ITEM	returns StoredValue object by state root hash, key and path
ACCOUNT_BALANCE	returns the balance (in motes) of an account
PUT_DEPLOY	sends a deploy to the network
DICTIONARY_ITEM	returns an item from a Dictionary (StoredValue object) by a given state root hash, dictionary item key and seed URef
GLOBAL_STATE	Sends a query to global state using either a Block hash or state root hash, returns a StoredValue object

Consumer

Consumer polls Casper Event Stream Server for the following events :

DEPLOY_PROCESSED : raised after a deploy was executed

DEPLOY_ACCEPTED : raised after a deploy is received by the node

DEPLOY_EXPIRED : raised when a deploy expired 

BLOCK_ADDED : raised when a block was added 

FINALITY_SIGNATURE :  raised after a validator approves a block

FAULT  : raised after a network error like equivocation

STEP  : raised when the auction where validators are selected finishes

SAMPLES

Consume BLOCK_ADDED events from Casper SSE and send block hashes to a jms queue :

from("casper://127.0.0.1:9999/events/main?event=BLOCK_ADDED")
.jsonpath("$blockAdded.block_hash", false, String.class, "block")
.to("jms:queue:new_blocks");

Use the block hashes to retrieve the block transfers:

from("jms:queue:new_blocks")
.setHeader(BLOCK_HASH, body())
.to("casper://127.0.0.1:7777?operation=BLOCK_TRANSFERS");

SPRING BOOT AUTO-CONFIGURATION

TODO

How to install

In your maven pom file add :

<dependency>
    <groupId>io.caspercommunity</groupId>
    <artifactId>camel-casper</artifactId>
   	<version>3.14.2</version>
</dependency>

Running unit tests

Requirements:

JAVA

Make sure you have the Java 8 JDK (also known as 1.8). If you don’t have version 1.8 or higher, install the JDK

Maven

Install maven (version 3.3.9 or higher). Guide : https://maven.apache.org/install.html.

Clone the project

git clone https://github.com/caspercommunityio/camel-casper

Run the unit tests :

cd camel-casper
mvn test

Usage examples

• configure routes using RouteBuilder

import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.component.casper.CasperConstants;
/**
 * A Camel Java DSL Router
 */
public class CasperRouteBuilder extends RouteBuilder {
/**
 * Let's configure the Camel routing rules using Java code...
 */
   public void configure()
   {
	   //this route  queries the node for latest block every 10 seconds and print the block object (using to string method)
	   from("timer://simpleTimer?period=10000")
	      .to("casper:http://65.21.227.180:7777/?operation="+CasperConstants.LAST_BLOCK)
	      .log("This call gives - ${body}");

	  
	  //this route reads a uref_purse from a file, use it to query an account balance and send the result via email
	  from("file://temp/input.txt")
                .convertBodyTo(String.class)
                .setHeader(PURSE_UREF, body())
                .to("casper:http://65.21.227.180:7777/?operation="+CasperConstants.ACCOUNT_BALANCE&stateRootHash=30cE5146268305AeeFdCC05a5f7bE7aa6dAF187937Eed9BB55Af90e1D49B7956)
                .to("smtp://user@mailserver?password=&[email protected]")
}

• Run the routes :

import org.apache.camel.main.Main;

/**
* A Camel Application
  */
  public class MainApp {
  /**
    * A main() so we can easily run these routing rules in our IDE
      */
      public static void main(String...args) throws Exception
      {
        Main main = new Main();
        main.configure().addRoutesBuilder(new CasperRouteBuilder());
         main.run(args);
      }
  }

Demo Project

You can find a demo project here : https://github.com/caspercommunityio/camel-example-casper

To build and run the project :

git clone https://github.com/caspercommunityio/camel-example-casper
cd camel-example-casper
mvn compile
mvn exec:java

The project contains 4 routes :

• Make a RPC request to get the state root hash
• Read a block hash stored in a file and make a RPC Request to get the block info from that hash
• Read a block height stored in a file and make a RPC Request to get the auction info from that specific block height and Then saves the validator slot of the auction to a json file
• Make a RPC request to get the state root hash then query an account using the state root hash and an account