We spent the last 2 days working on the rpc test server for the names api (later also messaging) in order to speed the wallet developments. We should have that implemented by tomorrow. We will extend the rpc unit test server with the messaging in a similar way and that should speed things along for us this week. On Tuesday our front end team (PAt & Ophie) will have access to our private DIONS bitbucket to start to work on the wallet front end lastest changes, and we will be adding the first name api codes to the wallet. While the team is fast working on this lastest calls, Sam is in conversations with Derek for the beta multiple wallet, environment
Environment build which will be comprised of:
Test Environment Basic Layout:
-VMware vSphere 5.x
-2 or 3 ESXi Hosts at version 5.1 U3
-1 vCenter Server
-Back-end storage for VMs via iSCSI with SSD Caching
-Multiple physical switches at 1Gbps(internal communication)
-Internet via fiber with 50Mbps up/down speed
-Multiple static public IP Addresses available(1-3)
-Redundant wherever possible(PSUs, NICs, etc.)
To make things clear for the new community members, we had already successfully beta tested DIONS the actual code. We were successful in registering names, updating and transferring, along with private messaging. This test was conducted months ago within the code in testnet. In this current phase we are in the wallet api code implementation and the upcoming beta will be for Full I/O DIONS Blockchain with wallet, setting us up for the release of Dions V.1. The Wallet is a new redesigned HTML5 wallet which is non QT, we did however specially coded some of the qt features like debug console, wallet lock while staking, and a few others. The wallet is a fresh environment which will allow us to expand nicely into future developments without the need of redesigning it from scratch again. The code for the wallet has be designed exclusively by our team unlike many out there which require a qt wallet.
DIONS will bring registration fees awarded to stakers. As of now they are comprised of 10 IOC per alias, .01 per KB for data and messaging. This registration fee goes to the confirming staker. It is based on stake size, large stakers have more chances of mining the winning tx. Consider your coins like hashing power to gain more ioc. As we expand and if IOC price climbs we could have a community consensus to adjust fees accordingly.
Thanks Everyone
PS, Remember the team is always available in our slack channel
I/O Digital Dev Team