As a simple rule of thumb I'd estimate it would take the same time it took you to create such a vanity address (the OP was only talking about the initial characters - not an exact address match).

AT on its own (using the ACCT use case) will only be suitable for more person-to-person trades *but* the CIYAM project has a Token package that is designed to work with ACCT making it perhaps a very suitable "trustless exchange platform" (it isn't using a blockchain yet but that is coming - https://bitcointalk.org/index.php?topic=598860.0).

@burstcoin (or @burstdev) has also contributed quite a lot of work on AT (in particular the creation of the AT Assembler which is a fantastic tool for those wanting to create ATs).

We also did have some help from @qoradev before his recent disappearance.

But we prefer as a team just to be called the AT developers (our names are not nearly as important as the technology we have created).

The problem is whether you want to trade "crypto for crypto" or "crypto for fiat".

The former will be able to be addressed soon (the AT project has already developed an "atomic cross-chain transfer" smart contract that can do this provided both blockchains have implemented AT) but the latter is not likely to ever happen (as fiat transfers basically *require* a trusted 3rd party).

What you'll find is that unless you send it funds it will actually do nothing at all (so won't waste anyone's resources beyond the actual AT creation tx data in the blockchain).

And even if you send it say 1M BURST it won't cause the next block minter to run out of memory (or get stuck forever) as the fixed maximum steps per AT will mean it won't spend more than a fraction of a second processing that (there is also a max. number of ATs that can be processed per block limit so you can't screw things up by creating 1M such ATs).

So any such "attack" would actually be less effective than just sending millions of "normal txs".

Try creating an "infinite loop" AT - I'll even give you the machine code for that here:


Now see what damage you can do with it.

(hint - you can't do any more damage with that than any other sort of DoS type of attack on the network as ATs work like "transactions" with funds needed to run them and fixed limits as to how many steps can be run per block)

It is running now on Burst and we have so far seen no problems. What issues in particular are of concern?

Yes AT is Turing complete and is already live on Burst (the first "mainnet" to be able to offer Smart Contracts which has been made possible through its use of AT).

It is expected that AT will be included in Qora soon and that then the world's first "atomic cross-chain transfer" between two different blockchains will be able to take place (using the ACCT AT we have already written).

This should be the basis for a completely decentralised exchange for cryptos (i.e. no trusted parties or servers). Understand that this only applies for trading cryptos for cryptos (not fiat).

In regards to the UI for AT we are currently creating a new design that should mean that .html files won't need to be installed manually (the UI will be able to be automatically generated according to metadata stored in the AT creation tx).

Hmm... like maybe this one?

https://bitcointalk.org/index.php?topic=949438.0

In regards to adding a Donation button to the UI (prior to 100% funding goal reached) - unless we have that as being a general idea for all ATs (i.e. to "donate" to their creators) then it should not be done for an already published ATs (as you can't "update" an AT) - it could only thus appear in a future crowdfund.

The entire point of "consensus" is that you can't just go and change it (otherwise people would not trust ATs at all).

As we are working on a complete new design for AT UI (that will get rid of the need to download .html files) the AT team is not going to focus on such "small issues" for now (feel free to bring them up again when our new UI implementation appears).

For anyone who is keen to do some "early testing" of the CIYAM system a VM can be downloaded here: https://susestudio.com/a/kp8B3G/ciyam-server (it should be noted that this version of CIYAM is not a blockchain system so is only useful for learning about how to use the IDE and build apps via Software Manufacturing).

Once you have installed the VM you can log in as "root" with password "linux" then type: ./setup

(it will update the OS and grab the latest version of CIYAM from github and then build and install it as well as set up apache2 to work with it)

I noticed the start of "sig campaign" posts so I have deleted a few posts.

If you have a sponsored sig then don't bother posting here (without posting something of actual relevance) as I will delete your post (unlike the mods I don't care for that shit).

I am not sure where people are getting their information from but the AT team (CIYAM Developers) did not create Burst and only help consult with that project (and I have not heard anything from @burstdev about working on Qora).

As for CIYAM Developers and Qora we will help out to try and make sure AT is actually implemented in the coin (as had been promised to the Qora community) but "taking it over" is not really our desire at all (as we have a lot of other things we are doing).

Unfortunately Jan Tenner has moved on to do work for blockchain.info but luckily before he left he created our new logo (which I've put at the top of the OP).



The CIYAM Developers would like to thank him for his contribution.

To get an idea about what Software Manufacturing is: http://ciyam.org/docs/methodology.html is an introduction to the concept (which I am fairly sure is going to change the way that software is created in the future).

To find out about how Software Manufacturing came into existence: http://ciyam.org/open/?cmd=view&data=20121221010507352000_P&ident=M100V112&chksum=b3d538bf (it isn't as long as most of Gavin or Vitalik's blog entries and does have pics).

Anyone interested to understand a bit more of the "nuts and bolts" might also be interested to read this: http://ciyam.org/open/?cmd=view&data=20150210150346737000&ident=M100V120&chksum=ecd893c2 (which shows how one of the main tools used to do Software Manufacturing works).

I think you are best to wait until we are ready to actually launch (by which time we will hopefully have some video demos) and understand that CIYAM doesn't even use AT (these are two very separate projects).

What will be able to link CIYAM with blockchains that use AT is actually the ACCT use case (which has yet to be demonstrated).

Because it won't say that unless it is already 100% funded (and maybe also not until the target block - would have to check with Vasilis about that to be sure).


It *is* crowdfunding because if the target level is not reached it will return the funds (we do understand the concept completely).

We added the "donate" once 100% reached as presumably the project would like to have further funds if it can but we could easily modify the AT so that after the target date any further funds can be refunded.

I guess we could also perhaps extend the AT to always have a Donate button which would send funds immediately to the destination address (if you think that would be an improvement I'll discuss it with Vasilis).

The button should say "pledge" so it is not a "donation" (if the target is not reached you will be refunded).

When the crowdfund target is reached then the button will change to donate (as it has been fully funded).

Make sense?

Fundamentally both AT and Ethereum solve the problem of providing "Turing complete" smart contracts but they do this in quite different ways.

Ethereum have used a Java like VM whilst AT is "virtual CPU". To most users of this technology the underlying mechanism is not going to matter and whether one approach or the other is better remains to be seen.

AT does not include a "new high-level language" (which Ethereum does) so the path towards a HLL for AT would actually be to harness an existing (and extremely well tested) system such as LLVM by targeting AT as a new kind of CPU that it can work with.

Assuming we are able to get LLVM working with AT then you would be able to program ATs using C/C++ (and other "industry standard" languages).