Skip to content
HFT meets Blockchain in Java platform
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
api
docgen
examples
exchange
net
platform
platform2
rfc
server
util
.gitignore
LICENSE.adoc
README.adoc
pom.xml

README.adoc

Chronicle-Accelerate

badge

Chronicle-Accelerate (XCL)

XCL is a new cryptocurrency project that, learning from the previous Blockchain implementations, aims to solve the issues limiting adoption by building an entirely new protocol that can scale to millions of transactions per second, delivering consistent sub-second latency. Our platform will leverage AI to control volatility and liquidity, require low energy and simplify compliance with integrated KYC and AML support.

The XCL platform combines low latencies (single digit millisecond), IoT transaction rates (millions/s), open source AI volatility controls and blockchain for transfer of value and exchange of value for virtual fiat and crypto currencies. This system could be extended to other asset classes such as securities and fixed income. It uses a federated services model and regionalized payment systems making it more scalable than a blockchain which requires global consensus.

Use cases

The main use cases we support are

  • distributed transaction ledger

  • settlement of payment

  • matching and settlement of exchange of value e.g. fiat or digital currencies.

The platform uses

The platform makes use of Chronicle-Salt for encryption and Chronicle-Bytes. Chronicle Bytes contains all the low level memory access wrappers. It is built on Chronicle Core’s direct memory and OS system call access.

Chronicle Bytes has a similar purpose to Java NIO’s ByteBuffer with some extensions.

Region Codes

Each service is designated to a region or a set of regions. Region codes are based on ISO-3166 region codes with some additional services.

XCLBase32 Specification

XCLBase32 is an extension of hexa-decimal for encoding a string of bytes.

There are Base32 specifications such as IETF - RFC4648 for encoding a string of bytes which starts at the highest bits and includes the length of bytes; the byte length of any training zeros is not important. As such encoding is aligned to the highest bits.

One of the aims is to produce numbers which can also be used to form words.

You can’t perform that action at this time.