That does depend upon whether you change the setting for the address pool size but 100 is the default (as most users are probably not even aware about when new addresses are used they are probably best advised to back up at least once every 100 txs).

Welcome to send me a PM if you like (although if it is a "get rich quick" idea then it would be better to not bother).

You might be surprised.

I can command over 1000 RMB per hour here in China (over 150 USD at current rates) and with more effort (I am a bit lazy) I am sure that could be easily doubled.

Actually that really isn't an issue of where people come from but instead *how they are employed* which is why I created CIYAM Open (to try and work out a completely new way to do this).

Unfortunately so far I've found that the vast majority of people are simply not up to the level of being able to do a task for a fixed fee (instead they always prefer to be paid for "time").

Although I come from Australia I can tell you that is a terrible idea.

Having lived in China for now over 8 years I can tell you it is virtually impossible to find any software engineers that have the same sort of creative skills that are available in most western countries (to understand why is to understand the Chinese education system and in particular the Chinese written language which is its core).

As software engineering usually requires quite a lot of creativity if you decide to employ people with very little of that then your business won't do very well at all (how well other "cheap contractors" compare is something perhaps others can comment upon).

Just noticed from the screen snapshot in the above post that it says "Automatic Transactions" in the UI - this should be changed to "Automated Transactions".

If that is the case then I think there should be no issues.

Yes - I think that currently you can't do more than 2 out of 3 and still be a standard tx (and I have no idea when if ever that might change).

I understand it is very near release but @qoradev seems to be on holidays still.

A sneak preview of the CIYAM OS can be found here: https://susestudio.com/a/kp8B3G/ciyam-server

There is work underway to create a "tinycore" version of the OS (that will only require 256 MB of RAM) and some new scripts have been added to make it quite simple to set up the VM so that you can work on creating CIYAM apps.

We will soon have a "trustless lottery" running for Burst (a world's first I think).

Although no-one managed to claim the possible 40 BTC bounty to get AT on a Bitcoin clone before the new year there is still 20 BTC available for those that are interested.

I wouldn't recommend using a brainwallet for website passwords but instead a password manager (as you mention re-using patterns could be a very bad idea).

In the future I would hope we could sign in to websites via QR code - one neat method I have thought about would be that when initially signing up you'd provide the equivalent of a Bitcoin "address". When you next go to sign in you would be presented with a service id and "nonce" in a QR code which you'd scan with an offline device.

It would look up the service id to find the public key (matching the address the service knows about) then sign a message containing the "nonce" and a new address which it would then display as a QR code for the service to scan to authenticate.

For those paranoid about security there is also the CIYAM Safe (https://susestudio.com/a/kp8B3G/ciyam-safe) which combines various tools (including bitcoind, vanitygen, scrypt and GPG) so that you can use QR codes to do 100% air-gapped tx signing and also safely keep encrypted backups of your keys online.

I seriously doubt that I would fall into either category - the idea stands on its own and some others have taken an interest in AT - not because of me but because it makes sense as a good idea.

Also I firmly believe that an idea is actually the easy part - turning an idea into reality is the far harder part and where far more credit is due (without the help of others AT would not have progressed as far as it has already).

The real heroes are @vbcs and @burstdev for working hard to turn this idea a reality (there are others including @qoradev who are also joining the ranks).

It would be great to see various blockchains implement AT so we can start harnessing many smart developers to go up against something like Ethereum without having any VC funding at all (like a "grass roots" sort of development).

I hope (and am fairly confident) that you'll find things will progress quite a bit faster than that (expect to see useful ATs available in weeks and months rather than years).

A lot of effort (months) had actually already gone into the development of AT before it was even introduced to Burst.

That is indeed something that should be considered and yes the CA component of HTTPS is IMO the biggest part of the problem with it.

To be clearer the reason that I am envisioning something quite different to HTTPS is that I see blockchains (note not singular) and P2P as being the two key core technologies of the internet of the future (and HTTPS was really designed for a traditional client/server model).

That project has mostly failed because it just replaced one name squatting system with another (I don't like the idea of anything like DNS).

Any suggestion for a better title?

Unfortunately one of the killer use cases will actually not be usable until AT appears upon another blockchain (although this is expected to happen soon). This is "atomic cross-chain transfer" which will let users of two blockchains exchange "coins" from each blockchain in a trustless manner without a 3rd party (thus no need for a crypto to crypto exchange that takes commissions and has to be trusted).

Another use case that will be appearing soon will be a lottery you can enter and then things like auctions and crowd-funding (all trustless and without 3rd parties).

It will take some time for these things to appear but it won't be that long until most people who are familiar with blockchains will be able to see the benefits of what AT can bring to them.

I think perhaps the title of this topic has confused people as I didn't intend it to mean creating things like the lowest level algos but instead the idea of replacing conventional implementations such as HTTPS in particular.

The comparison with the other topic is more to do with challenging "conventional wisdom" (i.e. that you *can't create a replacement for securely encrypting data* for something like HTTPS) so it is the system implementation rather than its low level algorithmic parts that are key.

The main interest I have is in how we create a new secure internet that doesn't use DNS or HTTPS (this topic being about the latter of these two things).