Alright folks, sorry for the delay but as promised here is what we’ve basically scheduled our focuses on for the better part of Q3-2016 through Q4-2017. I’ll be going into detail below the timeline in an effort to break down anything that might not make sense to those not in our development pipeline or those that may not be as technical as some others. This is the bulk of what the underlying foundation for the most part will require moving forward to support some undisclosed features (we like surprises, and learned the hard way not to disclose everything you’re working on as some will copy and release feeble attempts just to be first to market) and some additional alliances which would play a supporting role in overall operations.
The new website is in progress and likely will be ready long-before the projected timeline.
Poloniex and Bleutrade in-wallet trading
In addition to being able to trade on Bittrex through the wallet, we’ll be adding both of these exchanges in as well.
Rather than the news coming from a 3rd party, such as a website (single point of failure), it will be stored, managed, and archived on the blockchain itself. The bytes used for said data is nominal even over the course of time for long-term operation. Archives will be pruned as well after certain thresholds.
Reported bugs thus far
- While within the masternode list tab, clicking on columns to sort by field data produces unwanted results with random data being excluded post-sort.
- If the Bittrex API is down, the Neos market is frozen, or strings are returned as a result of the query, it causes a crash.
- Stake rewards are showing in the transaction list in the headless client as 0.0 reward value when they are in fact 0.5
Bugs are annoying; everyone hates bugs. We’ll be squashing these.
The major upcoming changes and features
Account Registration - within the coming network you’ll be able to access different data made available by the Neos team and community via realms. You’ll use your Neos ID and passphrase to access these. Registration allows for unique reference and access by alias. You’ll also be able to send Neos to one another using these account aliases rather than needing to remember wallet addresses.
Two-factor authentication - Just as Neos v2 had two-factor authentication, so will the upcoming version. The difference being - this will be chain-based rather than our original method of using a 3rd party server. Currently were considering Google, Authy, and MobilePass as potential options.
While accessing content within the new Neos network, you’ll have the ability to filter out content you don’t wish to see and through a learning algorithm if enabled - prevent any similar content from being displayed.
ACL (Access Control List) for content restrictions
You’ll be able to control what access specific users or groups have within your realm to content.
Everyone seems to enjoy the click-to-tip model and it’s something we definitely believe is conducive to a more productive and bountiful experience. If quality content creators are earning for their time and works, they’re bound to keep providing that same quality.
Content voting system
You’ll be able to rate content created by others.
Realm creation and management
Consider your realm your home. You’ll be able to oversee everything from users, ACL’s, scheduled content, news and more. You’ll be able to create as many realms of your own as your Neos balance can support.
Masternode Data Sharding/Storage
As briefly hinted at the relevance and importance of masternode operation and maintenance - we’re working on employing masternodes as data nodes (hence the reason we ourselves run a group of them and will continue to expand them). What we’re experimenting with is akin to ceph. If you’re familiar with ceph - you’re already aware of the capabilities and what a paramount role it can play in big data storage and access. While we’re not using ceph directly, information on the data storage structure/model can be read over at http://ceph.com/ceph-storage/file-system/. Allowing for seamless expansion based on capacity and node health/responsiveness will provide long-term sustainability while alleviating the need for every node running to keep full copies of data ready. With our approach, nodes can be added or removed without any network noise or service interruption.
This is something experimental and not 100% guaranteed. The idea behind our approach to what could be seen as an alternative to “smart contracts” for handling p2p payments for services rendered - is to use masternodes as overseers, work logs and escrow. Once we determine through development and testing that this is a feasible approach we’ll be providing more information.
The new skin and interface
With all of the new functionality being built, the existing interface will be going through a major overhaul in design. Our goal is to have everything contained within the client and make it as portable as possible and supported on multiple platforms.
What’s been outlined today is a taste of what’s coming. I’ve personally worked with all of the technologies listed above throughout the years and have witnessed attempts at combining them with blockchain technology. If executed properly this can provide a truly sustainable secure presence with many benefits. If anyone has any questions, please don’t hesitate to ask. We’re also in the process of seeking an additional developer to join the team. If you feel you’re a good fit - please contact me. These timelines are just estimates and combined with a QA period with rigorous testing - can be drastically reduced.