We are happy and eager to announce our web client release which will be available later today with an overview guide. For most until the testnet this will not be particularly interesting but we feel it will greatly ease the difficulty of currently getting set up with the temporary chain which will help adoption and community growth.

To improve transparency with our plans going forward, we would like to take some time to give a general idea of what’s to come and what’s being worked on. Since there are two main projects, the web client and the Novusphere testnet being developed, we feel it’s best to convey the goals for each in separate roadmaps. Please note that these roadmaps are not set in stone and subject to change.

Thank you for your continued support and patience.

Web Client Development

We encourage auditing source and network traffic to ensure no private information is ever being sent to the server used for blockchain information and relaying transactions. Traffic is primarily done over WSS. No private keys or passwords are ever sent directly to the node you are connected to.

Temporary Chain

For the initial release, it covers a minimalist client interface for the temporary atmos blockchain released allowing users to quickly and securely receive/send/store atmos without requiring the hassle of setting up the qt client or managing a wallet.dat file. It will not allow staking.

Notes: A native block explorer and anything relating to exploring indexed data on the temporary chain has not been implemented. While not seamless, the cryptoID block explorer provides sufficiently for the temporary blockchain and it would not be a productive use of time. As for indexed data on the temporary chain, it would be complicated to implement backwards compatibility for both the temporary chain and the testnet so we have decided to forego this in the new client implementation.

A native block explorer and anything relating to exploring indexed data on the temporary chain has not been implemented. While not seamless, the block explorer provides sufficiently for the temporary blockchain and it would not be a productive use of time. As for indexed data on the temporary chain, it would be complicated to implement backwards compatibility for both the temporary chain and the testnet so we have decided to forego this in the new client implementation. Re-integration of 2FA (Two factor) service via Google Authentication

Testnet

Initial testnet integration (send, receive transactions)

Native block explorer capability (view address history, transaction info)

Naming/aliasing public key with a human readable string

Adding indexed content to testnet chain

Indexed content explorer (general search, think like “Google”)

Voting on content — “liking” and “disliking” to help every day users filter spam, broken and unethical content

Begin using Schnorr signature scheme in transactions

Testnet: Specialized indexed content explorers — Videos

Index a general video metadata/description (think like “IMDB”)

Add/view video mirrors (mp4, iframe, ipfs hash) referencing video metadata

Sort mirrors by voting to reduce spam/broken mirrors

We will further evaluate the community’s opinion on what other specialized content explorers they would like to see developed.

Testnet Development