In 2014, BURST was born with features that other blockchains are still looking to build.

Encrypted Messaging, Asset Exchange, Crowdfunding and the Marketplace loaded the BURST-chain with important features since Day One. However, Proof-of-Capacity (PoC), with its eco-friendly mining algorithm, has always been what truly sets BURST apart.

BURST has always been a community-driven coin with different committed teams.A lot of improvements have been made since inception, like increased transactions per block, new and optimized miner & pool-software, extended explorer, and new wallets.

Until now, the true potential of BURST is yet to be unleashed…

Smart Contracts by Automated Transactions (AT)

BURST is currently ready to be a global payment gate, but even more interesting is that BURST is shipped with a smart contract implemented as Automated Transactions (AT). This AT system was developed by CIYAM and is turing-complete, thus having potentially infinite number of use cases.

The concept of this virtual machine is time-tested and already proven on-chain with some complex examples; like the BURST-lottery: which was written with only 37 steps in CIYAM bytecode

However, the creation and deployment of smart contracts on-chain requires writing bytecode and extensive testing, thus is not user-friendly at the moment.

(example of API Call for creating an AT)

We all know that smart-contracts will be the next big thing for the crypto-world and BURST has the best basis technology already in its DNA.

Currently, BURST ATs support three built-in transaction types:

  • Receiving/sending BURST
  • Receiving/sending BURST with message
  • Receiving/sending message

These options provide a good amount of flexibility in building ATs. However, deployment of ATs on-chain poses another significant hurdle.

BURST AT extended framework “BlockTalk”

What would you think if you just write a code in a simple and concise language and the code gets deployed as an AT on the BURST-chain immediately?! Furthermore you can use tools and code-snipes to develop within your own development-setup and deployment will be supported by several helper tools? Finally, what if the fees to deploy your AT and run it on BURST blockchain are very small?

Gotcha!
You would start using it!

And here the good news come
BlockTalk is an extended BURST AT framework which aids in the creation and deployment of ATs via a simple and concise language, and a simple interface for deploying to the blockchain. It includes tools and code snippets to assist in the process, and helps manage the minimal fees involved with running ATs. BlockTalk is being developed free of charge by a group of bytecode and AT specialists. Here’s a peek at the current system design:

To shed some light upon this visualisation of the future deployment of BURST ATs, a short description of each component:

LANG
This will be a new programming language, specifically designed for future creation of AT

ANTLR (Another Tool for Language Recognition)
This is a powerful tool for reading and translating structured text into binary files. That involves:

  • A Lexer – to read LANG sourcecode and turn that into tokens
  • A parser – to parse and turn the tokens into a structured representation (AST)
  • AST – with an associated walker to walk the AST and turn that into a new extended script language (ESA) for Burst blockchain

ESA
The extended script assembly (ESA) will create and handle the new types, dynamic memory and extension of SA.

SA
The script assembly is creating the first maschinencode.
It includes and handles logical branches, declarations of vars, labels to jump to, named API funcs as opposed to hex numbered functions.

Mcode
This module make the preparation for the Step5-1 processing.
Mainy labels will be swapped out with addrs, named funs swapped with hex numbered func, named vars swapped with their physical addrs.

Step5-1
The steps are part of the compiling process.
The steps compile mcode into bcode and breaks that task into clearly defined steps of 5. Each step, involves having input from step above and providing output to step below. Syntax and semantics are thoroughly checked on both input and output at each step. In case of any error at a given step, the input is rejected and an error message to the above step is submitted. Step3 is the most human readable (big-endian), Step2 and Step1 are on form little-endian.

Bcode
Final transformation to bytecode.
Each instr on separate lines, as op-funcno-arg , literal


CIYAM Bytecode
In this last step some checks will be performed with the bytecode and CIYAM Bytecode will be created. This code can then be released to the BURST-Chain as a new smart AT.

Conclusion

The benefit of this concept will be that the first  7 components are outside the BURST chain and could be formed according to the needs of the developers and users – running locally or as services in a cloud-environment. Also each component will run as a microservice and communicate via JSON, making the further development easy.

We like to hear you!
Starting with the architectural setup right now and building the first service components  which will open the CIYAM bytecode with even more flexibility, we would like to invite the community to give us feedback about our development plans.

We also want to involve you to try out the infinite possibilities of future BURST ATs by publishing ideas or requirements of your AT that you always wanted to do but never were able to do.

As we are working right now on the first setup we will give you continuous updates via the Weekly Burst Reports. Anyone who feels attracted by building this new framework may contact frank_the_tank via discord or just write a comment under this article.

We are looking forward to receiving your ideas and new smart ATs on the BURST-chain!




Together, let’s build a strong and smart BURST network

Total
17
Shares

Subscribe

Subscribe now to our newsletter

6 comments

Leave a Reply

Your email address will not be published. Required fields are marked *

*
*