The Bulleon Exchange Development Summary 1

The Bulleon Exchange Development Update 1

Back-End Development status

We’re done with the development of the back-end. At the same time, we’re processing various tests where we examine the security and centricity of the exchange. As regards the front-end development, we have initiated a more functionality-focused approach, as opposed to focusing on aesthetics. We will open the opportunity to test the product and work on its design when the product becomes functional. We will also be focusing on the user experience and basing it on your opinion. Rest assured that we’ll be considering your feedback.

Bulleon Exchange Modules running on back-end

As you know, Bulleon is community driven-project. This means that everybody can build it to meet their specification and serve their needs. If you’ll love to participate in the development and testing of the product, feel free to contact us via Telegram.

Front-End Development status

Front-end development is also in good shape. We’ve achieved proper interactions with both front-end and back-end, and everything seems to be working according to plan.

Screenshot of front-end interface which is now under construction.

At the moment, we’re at a good stage with the construction of an interface’s design. After the Bulleon Exchange’s launch, we’ll be implementing it into our existing Bulleon MVP wallet software, which is currently released under pre-alpha version.

The Bulleon MVP wallet adds simplicity to the ecosystem, as users are able to effortlessly manage their digital assets locally on a single platform. You can also make use of Bulleon MVP as a Wallet to store your BUL tokens and Ethereum without going through tedious and time-consuming processes.

The Bulleon Exchange Server is a high-performance trading platform that was designed for cryptocurrency exchange operations. It is capable of supporting up to 10,000 trades per second, and it enables real-time user/market notifications via Websocket.

System Architecture

Used systems

MySQL: For saving operation logs, user balance histories, order histories and trade histories.

Redis: A Redis sentinel group is used to save market data.

Kafka: A message system.

Bulleon Exchange System Architecture.

Base library

Network: An event base and high-performance network programming library, which is capable of supporting 1000K TCP connections. It also includes TCP/UDP/UNIX SOCKET server and client implementation, a simple timer, state machine, and a thread pool.

Utils: Some basic library, including log, config parse, some data structure and http/websocket/rpc server implementation.


matchengine: This is the most important part, as it records user balance and executes user order. It is stored in the memory database, and it saves operation logs in MySQL and redoes the operation logs when started. It also writes user history into MySQL, push balance, orders and deals message to Kafka.

marketprice: Reads message(s) from Kafka, and generates k line data.

readhistory: Reads history data from MySQL.

accesshttp: Supports a simple HTTP interface and hides complexity for upper layer.

accwssws: A Websocket server that supports queries and pushes for user and market data.

alertcenter: A simple server that writes FATAL level log to redis list, so we can send alert emails.

As you can see, we are closer to the launch of the first Bulleon product now. This product will help generate revenue and operating profit for the company, with a share of these profits going to BUL holders. Development has gone according to our laid-out plans, and we are on schedule.

Stay tuned!

Learn more about Bulleon: