AMO testnet has two main purposes:
For the first purpose, AMO testnet shall be periodically purged and restarted (about once a week).
To see the internals of the AMO blockchain, visit our github.com page.
To see how to connect to the AMO testnet, visit this page.
To see blocks the AMO testnet creates, visit AMO blockchain explorer.
It's getting deeper into the summer, and it's time to release AMO software version 1.0 (AMO blockchain node software). According to the original plan, the software v1.0 should be feature-complete, and it's supposed to be polished and optimized until the end of this year. Although there is much room for change in the underlying data structures and internal architecture, the current version(v1.0-beta1) is feature-complete in view of the AMO blockchain protocol spec and AMO storage service spec. We're planning to release v1.0 on 24th July, this week, and another testnet will be launched on the same day.
It's been a while since the testnet-190617 with the storage service launched silently. Yes, without any notice. We were waiting for the faucet server to be working properly, and now it IS up and running now. Along with the faucet server, new demo page has been setup. With the faucet feature, now you can try some operations with actual test money. And the demo page and parcel page can handle encryption keys. Try out on the AMO blockchain explorer site now.
After days of inconsistency and downtime, the testnet has been fully recovered. It was not a problem in the blockchain node software. Rather it was an operational problem in running master seed node. The seed node has been freshly started. After all, this is a blockchain, and all the necessary blockchain data had been copied in other nodes.
Anyway, we are preparing to release ABCI software
Along the process, we will restart the testnet several times without
notification. This is for testing the crash recovery feature in the blockchain
node software. So, the data may or may not be retained.
The new strategy for storage service has been set. We are not sticked to
PAUST-DB, and new AMO storage service adapter will be introduced. In this
strategy, any storage service can be incorporated in AMO infrastructure. With
v1.0-beta1 software, we will launch a testing storage service.
New testnet launched with the ABCI software
we have new Demo Page in
AMO blockchain explorer. In order to
test data parcel trade and see the flow of payment, you need some AMO coins for
test purpose. There is a Ask for coin button in the demo account view,
but this faucet link is not working right now. It will be working shortly.
We are undergoing an import discussion about the native storage service of AMO blockchain. Our original plan was to use PAUST-DB, but there is an opinion gaining popularity, which insists that we must use a long-lived and well-tested distributed storage software such as Ceph.
Regarding the ongoing discussion, the data upload feature shall be delayed to come, which had been planned to come last week. Until the discussion is resolved, we will provide a demo page showing basic trading feature set, which of course uses generic Data parcel IDs, rather than associated with the actual storage service.
In addition, there is a change in digital signature format. So, new testnet will be launched on Friday this week, or Tuesday next week.
New testnet launched. This time, with paust-db as a default storage service. Paust-db supports basic functions including upload, download and delete. According to AMO Storage Service Requirements, any AMO-compliant storage service should implement an access control feature, but there is no user authentication or access control feature yet. Access control will be applied in the next testnet, coming in about two weeks from now.
Client features regarding data transfer will be provided next week with the current testnet.
Testnet-190509 will be launched on 2019-05-09 13:00 KST. This testnet will implement data upload feature, but with limited size. Users will be able to upload any data, but the upload feature is not tightly bound with the encryption feature. We are currenty finalizing AMO storage service specification, and this document will specify the data parcel format and requirements to support data encryption and key custody handling. Note that data upload feature is not part of AMO blockchain protocol. It shall be handled by clients and AMO storage services, not the blockchain nodes themselves. So, more precisely, this testnet will come along with the default storage service (PAUST-DB).
The launch was delayed about 3 hours in order to fix a bug in validator update mechanism. Now it's online (15:00 KST). Unfortunately, there wasn't enough time to setup a faucet site. It will come soon.
The second testnet will open on 2019-04-23 13:00 KST, using software version
v1.0-alpha4. The genesis file can be retrieved from
this location. It will come along with a simple faucet site.
Raindrop script is a low-profile transaction generator. Due to the fix introduced on Apr. 16, blocks are not generated when there is no transactions to process. To stir up some activities in the testnet blockchain and nodes, we are planning to launch a transaction generator. This transaction generator has two P256 private keys† associated with two test accounts. These acounts were given some AMO coins to spend. The transaction generator will occasionally transfer small amount of AMO coins from one account to the other. These transfer transactions are scheduled to be generated once in several tens of minutes. Since this is not a heavy load, we do not call this a load generator. Rather we call this a raindrop generator.
† To figure out why we used P256 keys, see this note.
The press release has been postponed until the weekend and there is no
serious traffic to this testnet yet. So, there is a chance to update the
software before public notice. One noticeable change is that blocks will be
created only if there is any transaction to include. Currently a block is
created every second even if there is no transaction to process. Technically,
this is due to the block reward mechanism and the
in the tendermint layer. Original configuration was that validators shall
receive a reward even for an empty block. Since the tendermint layer records
the ABCI app's state change in the NEXT block, not the CURRENT
block, a state change coming from the block reward for the block
must be recorded in the next block
n+1. This NEXT block
n+1 may contain no transactions, but even if the block is empty
there shall be a state change due to the reward for the block
And, this state change must be recorded in the block
And, another block. And another state change, and another block, and so on...
To remedy this problem, block reward for an empty block will be changed to be ZERO. And the block progression will stop if there is no transaction to process.
The first testnet will open on 2019-04-15 12:00 KST, using software version
v1.0-alpha2. The genesis file can be retrieved
from this location.
Thank you for your interest.