Hi,
The last 3-4 weeks I am working closely with burstdev and we are integrating AT into burst platform. AT stands for Automated Transactions ( for more info visit
www.ciyam.org/at ) and what actually does is to enable smart contract functionality. In brief an Automated Transaction is a "Turing complete" set of byte code instructions which will be executed by a byte code interpreter built into in burst platform. AT programs are currently written using custom AT machine code, but in the near future we are planing to create a compiler, enabling high level languages to be used to write AT programs.
AT is also being integrating in Qora platform, which imo is a perfect opportunity to make the first atomic cross chain txs between burst and qora ( for more info visit the acct use case
http://ciyam.org/at/at_atomic.html ).
The integration is almost done and we might see it live this or next week. I am very excited seeing AT has already found a "second home".
Best Regards
-vbcs
Where physically is the AT code executed? miners?, wallets?
Is there guards against malicious AT code, like, for instance code that loops forever, or code that somehow fills up memory, or code that runs for a while, generating a denial of service attack. code that perhaps open files or other resouces and manage to leak them. I fear a little that enabling anyone to write programs that are executed inside the transaction processing computers, might open up for a lot of different kinds of attacks
There are lots of good things too of course, but i'd like to know more about how much focus is on security.
