Update and news roundup for those of you who haven't subscribed to the mailing list
although I assume most have as the number is getting up there.
*Last call for alpha testers, we will be beginning alpha testing of our API,
ledger process, and POG in just a few days and although we do have enough testers
this is the final call for anyone else who would like to be included before we
move on to the beta stage.
This is who I have approved so far for testing, I'm only
approving about 1/4 of the people who have asked for the
alpha but the beta is going to be open to everyone:
CryptAxe
Tigew (mobile dev team)
Skitter (mobile dev team)
eureka
criptix (community manager)
visual111
nine009
mamamae
Here is what the ATOMIC desktop wallet looks like right now for the alpha testers:
As you can see, transactions arrive in a queue very similar to bitcoin, however you can
see that the transactions show the source, and destination coin (if applicable) as well
as what type of transaction occurred. Double clicking any of these transactions will bring
you to our blockchain explorer which has been modified to suit our needs and display data
appended via the Proof Of Exchange process.
*Information for developers and future customers of the ATOMIC DAC:
note this is all trimmed down so it will fit on the forum, full contents
as well as examples of calling from different languages available soon
at atomicdac.org
API CALLS (examples shown in c++):
/*
* Check the status of the ATOMIC
* network, the API of the exchange
* selected, and the ATOMIC API
*
* Any result other than 0 indicates
* that there is an issue
*
* CODES:
* 0: Good
* 1: Connection issues
* 2: Overloaded
* ..... etc
*/
unsigned int status();
Example:
AtomicAPI api;
if (api.status > 0) {
std::cout << "The network cannot handle a request right now\n";
}
/*
* Overloaded exchange function
* will be passed an atomic
* object directly instead of
* having to create one from params
* or data from socket
*/
unsigned int atomicExchange(AtomObject *aObject);
This will be the main way that customers and developers will communicate with the
ATOMIC network. The wallet generates atomobjects for every transaction, but developers
are able to actually generate them without the wallet, so that they can be sent over
an sslsocket, or via an http request to the ATOMIC network without the developer of
software which should make use of the ATOMIC ledger having to install or configure
their own nodes or wallet.
/*
* Check the transaction
* at the ID specified.
*
* Return -1 if does not
* exist
*
* Return 0 for exist but
* no confirms
*
* Anything returned above
* 0 will be additional
* confirmations.
*
* ex: -1 = does not exist
* 0 = exists with 0 confirms
* 10 = exists with 10 confirmations
*
* *Stops counting at your systems limit
*/
int checkTX(string txid);
/*
* return total amount spent
* in transaction ID
*/
float checkTXAmount(string txid);
checkTX and checkTXAmount are self explanitory.
You may be wondering how it is that we are going to do everything that we have talked
about with such a simple API. The reason for the simplicity is that the API calls
themselves have been designed in a way which we hope will allow for minimal changes
in the future to the API itself (good for compatibility) and instead make changes
to the atomobjects which are passed.
Okay that's too much of a wall of text already, go ahead and sign up for the mailing list
for more info and you should be seeing a sneak peak of the mobile wallet as well some time
soon from the mobile dev team who are wrapping up the mobile app (Android only for now)
