This is the I/O Coin Protocol 60021, Dions-html5 Linux Debian Wallet 105-8


Please remember this is a mandatory update, if you send coins to bittrex or anyone from the old protocol wallets 60015, 60016, 60017, 60018, 60019, 60020 after the fork on block 1625000 u could lose coins since bittrex wallets were disabled and the coins won't hit the new chain. Always send 1 ioc as test to ensure proper receive during upgrade times.

****Make sure to Always Backup all files and folders before upgrading

https://github.com/IOCoin/DIONS/releases/download/Dions-html5wallet-Windows10-OSX-1058-1108-setup/dions-105-8-normal-debian-run.sh

This is the I/O Coin Protocol 60021, Dions-html5 Windows 10 & OSX Sierra 64Bit Wallet-105-8 & D-110-8

For a Guide and How to for the wallet install please check our website https://www.iodigital.io/tutorial

**This is Mandatory Update internal synchronisation mechanism added to prevent Dions aliases being submitted for decryption when same valid Dions is already active, protocol updated to 60021 .. 60020 lower protocols are now banned

Version D-110-8 Is a decentric version for systems that are low in resources.

Please remember this is a mandatory update, if you send coins to bittrex or anyone from the old protocol wallets 60015, 60016, 60017, 60018, 60019, 60020 after the fork on block 1625000 u could lose coins since bittrex wallets were disabled and the coins won't hit the new chain. Always send 1 ioc as test to ensure proper receive during upgrade times.

****Make sure to Always Backup all files and folders before upgrading

**We have blockchain files to help you speed up the blockchain sync


https://github.com/IOCoin/DIONS/releases/tag/Dions-html5wallet-Windows10-OSX-1058-1108-setup

This is the I/O Coin Protocol 60021, Dions-html5 Windows 10 & OSX Sierra 64Bit Wallet-105-6 & D-110-6

For a Guide and How to for the wallet install please check our website https://www.iodigital.io/tutorial

**This is Mandatory Update internal synchronisation mechanism added to prevent Dions aliases being submitted for decryption when same valid Dions is already active, protocol updated to 60021 .. 60020 lower protocols are now banned

Version D-110-6 Is a decentric version for systems that are low in resources.

Please remember this is a mandatory update, if you send coins to bittrex or anyone from the old protocol wallets 60015, 60016, 60017, 60018, 60019, 60020 after the fork on block 1625000 u could lose coins since bittrex wallets were disabled and the coins won't hit the new chain. Always send 1 ioc as test to ensure proper receive during upgrade times.

****Make sure to Always Backup all files and folders before upgrading

https://github.com/IOCoin/DIONS/releases

Today we observed multiple wallets failing to sync and on further investigation it appears that the issue was the result of a bad block that occurred on Nov 2nd.
Unfortunately we had a user who clicked to create a dion on the new wallet that shouldn’t have been ‘enabled’. This action created a bad block since the feature has not been enabled until the fork at 1625000. Some wallets were able bypass the bad block with chain automatic reorganize & others got stuck.  We have taken action and resolved this matter.

We took the decision to suspend the market and err on the side of caution. The matter is now resolved.

New wallets are up



Please ensure to be on the lookout for more wallet patches and updates until the block 1625000. We are updating regularly and adding patches as they are needed. Make sure to always backup the entire iocoin folder in 2 different locations to ensure you have good backups before your proceed with upgrades. If you need wallet support with upgrade go to our telegram channel. If you Move, Send or Receive coins for the next couple weeks please do a small 1 IOC test send and receive first to ensure all good.


https://t.me/joinchat/CqVqS0YP0QgLnfhNKGJ4pA


Market should resume as soon as Bittrex Has Updated


Latest wallets are ready to download on Github wallet version 1.0.4 /Satoshi:15.0.0/ protocol 60017

https://github.com/IOCoin/DIONS/releases



I/O Digital Dev Team

Gas is an expression of what people are calling fees (IOC Fraction) rebrand marketing they did

Fixed it so it would not confuse

Thanks

Note to all our I/O Coin holders.


I/O Coin was fair launched blockchain, this was not an ICO. We are not a company, when you buy IOC your buying from other holders that bought IOC and are selling them. The project is completely decentralized  and once anyone buys an IOC they have a voice and your part of our decentralized community. So far Funds to develop came from private funds and lots of hard work in 8-5pm Jobs. The dev team has been working now full time for over 2 years. Businesses were sold, private jobs were put aside and savings were put in to fund our work.  We bought coins, just like you, from the markets. Im personally staking my coins since few weeks after the genesis block and Ive been buying ioc when I've had the extra funds. Staking is extremely important for ioc, Yes it takes a bit of time to download and setup, but this is how we can truly secure our blockchain. Going forward with DIONS upgrade it will be even more important to have more nodes. All our stakers will be incentivized through transfer fees, staking fees, registration fees, document storage fees, messaging fees. These fees will be spread to all stakers. Unlike other projects where they have marketing gimmicks like “Master Nodes” here anyone that has weight gets more chances to make extra IOC (More Coins). As our network grows and more transactions are happening, our stakers will be greatly taken care off.  We are pushing forward a great decentralized platform that will allow for the liberty of expression and document storage. Now in these days we should not only think about monetary benefits, but also help push platforms for independent developers and companies to have a chance to do Proof Of Concept on our blockchain and  build some great dapps. If you have a computer that's in a corner dead doing nothing,  dust it off, you could use that computer to stake and help us grow in nodes. Price is important but the more nodes we have the more stronger we become. We have a stakers channel and you're welcome to join and ask questions #stakers-channel.

Please be careful in the markets don’t buy more than what you can afford, prices fluctuate. The dev team doesn’t control markets push up or down. This is a tradable currency. As we grow in market cap more developer will show interest and give ideas on how to add features, improve security and further enhance the I/O Digital blockchain.  With the DIONS upgrade we will provide a platform for IOC to be used for alias creation (In V.2 DNS) data (document storage) transfer of documents, identity storage, encrypted messaging, we will have more to come on V.2. We are very long term project, you can check our roadmap at www.iocoin.io The team will be meeting on friday (tomorrow) to go over some educational infographics and press release so we can spread the news of IOC once we call the block. Lastly we have a foundation that we put together to help spread the word on IOC, which supports the development team. The foundation is a non for profit. Just because the foundation is here it doesn’t stop people from helping on starting their own marketing ideas, promotion or maybe help in development. Please feel free to reach out to the team if you have any question. Try to get involved in any possible way and help us grow our community. We need more people to answer questions, help people installing wallets or correcting any misleading information that could come as it always happens when the price goes on rise.

Lastly for the ones that are asking, we had a bucket list to complete DIONS, two items have already been done. We are still coding the bootstrap, we have a chromium fix and box for enc doc. When we release DIONS remember it will be V.1, we will later on upgrade to V.2 and further enhance as we go along. Chameleon whitepaper will be announce after DIONS along with DIONS V.2 please follow us on facebook, twitter, telegram all our links are on the website.  Thank You All, and welcome to the I/O Digital Community


Joel
I/O Digital Dev Team

We are Not sure what to say about this message, please make sure to understand the code before making comments. We are not even using a qt as a wallet that should tell you allot about our work ethics. We are extremely busy and would appreciate you refrain from making baseless claims and guesses that scare our holders. We don't go into syscoin forum and scare your holders or fud. If you have legitimate concerns after you truly understand our code, use the proper channels to communicate with us.

Thank You

Hello everyone, we want to thank everyone that's been with us since the beginning or if you are new to our community thank you for stopping bye.


The Dev team has been hard at work in the final beta testing stages of our DIONS upgrade. During this beta phase almost 95% of the bugs found were related to the UI (Wallet Front end) and other minor enhancements to our daemon. We implemented a blockchain crawler for both the aliases and RSA key to alias messaging invite. Now messaging will work by inviting your friends and family by simple name invite.  Continuing forward, we are currently working on the Rsa Key generation to Alias testing, Private alias, download, transfer and dns testing. We will also be completing some testing on the messaging section and adding the last touches to the wallet (Super bootstrap + installers).

We have found great support by our beta testers and we are confident that if everything goes as planned, we should be able to release DIONS on around 45 days. We are estimating this time, because we really don't have much to do, but tweaks to the UI and minor enhancements. We also have to commission a brand new block explorer for DIONS, to be ready for release. Here is our latest look to our DIONS section with private and public alias display running in our "ioclab". You may also watch our test net demo on the link below. Lastly for the ones asking about our github not being updated, we are working DIONS in a private github account and the code will be open source soon after release. The code will be reviewed by open source devs.


As a reminder users have until May 2nd to move coins out of poloniex exchange and over to your wallets or Bittrex Exchange. We have also been informed that Coinigy will be going live with an exchange and we look forward for them to have IOC listed on their exchange. On Dions release the dev team will be in contact with all other major exchanges to have IOC listed and expand our reach to other markets.

DIONS wallet Preview https://youtu.be/NR9e1gYvUqw
Blocktalk with Founder Joel Bosh https://www.youtube.com/watch?v=Lcu6oC5AlqA

So far for release DIONS will be available for Windows 10, OSX El capitan and Linux. We are also working on Sierra

Thank You Everyone.

Hardware upgrades to our data lab testnet are done. We are now setting up clients and will be doing roll call for our Final DIONS Beta Stress Test, to our Managers & Beta testers next. Once we commence this important test, we will update once again. This stress test will be the last test we run before Dion's is formally released. As we have previously said all these measures are precautionary in order to ensure a smooth release for V.1. We are updating on a regular basis in our slack, so please feel free to join us there.


Thanks

I/O Dev Team

Our lead dev Derek has passed the baton to Sam to commence shutdown of our data center in preparation for our hardware upgrade. The hardware upgrade will be conducted through today and tomorrow. This will allow us to host 15 to 20 desktop clients with Dions wallets and begin our last leg of our Dions Beta, The Stress Test. This test is very important not only to isolate front end bugs but to also test the chain under heavy load and or real life push. In the years we have been around, we have never seen a project go as far as we are going to ensure a solid release to such important platform.

These tests are run under a very controlled environment to allow us to monitor cpu and or resource usage.  Because our wallet is one of a kind, in its code and interaction with the backend, we have been extra careful as to making sure we dont overlook any important detail on release. So the people that are coming in are vital to our collective success to be able to have an awesome roll out. Im very proud to hit another huge milestone.

We will be working on a video wallet demo to be ready close to release to have new users get a feel and understanding of how to manage our new wallet. We will update again once our hardware upgrade is done.


Thanks Everyone

I/O Digital Dev Team

  It was an amazing 2016, we started at around market cap $50k and today Jan 2017, we hover around $5 to $6 Million dollars. It was a year filled with awards and lots of progress made with DIONS, running up to our current initial beta with our new HTML5 wallet.  The I/O Digital Blockchain has been going strong with 0 downtime, 0 forks or any major setbacks and we are looking strong to keep that stellar accomplishment. As with any other blockchain project, if any unforeseen issues were to come, they will be handled swiftly by our team.  

The team is back at it today. We will be uploading images as we go along finalizing things, but all major parts of our DIONS HTML5 wallet are in and have passed initial beta. Our next steps are now to get the wallet ready for our testers so we can run stress test of the entire blockchain, code, wallet to clean out any unseen bugs, that we haven't already gotten too. We have conferences coming up from Miami to England and we have the Fintech awards voting that's also coming up.

Mr Antonioni (former IBM mexico president) is currently conducting a study on our entire project, looking over Foundation paper work gearing up for our first board meeting along with Marco Houweling (Finance from TomTom). Mr Antonioni has some ideas in mind and propositions for us to follow. He has been in touch with some industry tech leaders that also have been given him feedback. We are always going to share as much info as we can since some people for the time being are not in a position to announce that they are in talks with our project, but rest assure that as we move along if we get green we will share. As everyone knows from our roadmap, we have Chameleon that will follow Dions. So all hands are to get Dions out first asap, following thorough stress tests to the entire chain with our beta testers. Please remember that after main release of Dions, there will be more versions to it along with the wallet. Ophie is currently working on a new I/O Coin website which will be updated on Dions release. There has been progress with project sunrise (which is a side project not part of the foundation) and we are working out strategies for a provisional patent as we concluded our first round of vetting and research. Project sunrise will be announced along with chameleon in due time.

It will be an extremely busy 2017 and we are looking forward to hit the ground running for that Top 10 spot. If you or anyone has any questions please field them to Richard our community manager and we will answer them asap. Please spread our infographics. This project is for everyone to also think of things to do with the chain as we go along. Remember that with Dions, the more coins you stake the more staking power you have, it will help secure more rewards from fees as users chat, create aliases, upload data and more. The fees stand at .01 IOC per KB.


Happy New Year to everyone.

I/O Digital Dev Team



If you want to read more about our project, you can visit the resource pages mentioned below;

I/O Digital website: http://www.iodigital.io

I/O Digital roadmap: http://www.iodigital.io/roadmap

I/O Coin website: http://www.iocoin.io

I/O Digital community website: http://www.iocoinhub.io

Join us in Slack!
Be sure to connect to us on our Slack chat channel.
Team members and community members are there to chat about the project and ideas we have.
Subscribe here: goo.gl/Y0ppnX  (invites sent immediately)

If you want to buy I/O Coins;
Poloniex: https://poloniex.com/exchange#btc_ioc
Bittrex: bittrex.com/Market/Index?MarketName=BTC-IOC
How to buy I/O Coin: www.iodigital.io/how-to-buy-io-coin/

Thanks for your interest.

FOR IMMEDIATE RELEASE


Mr. Nadal Antonioni former IBM Mexico President/Chairman & Director of Operations for Latin America, joins the I/O Digital Foundation Board of Advisors

Antonioni has a long professional history within IBM. Antonioni started his career as a Systems Engineer in Argentina, holding several senior management, operations and  executive positions. Antonioni served for over 25 years within the company.
Antonioni, was also a member of the IBM/AFE Board of Directors, participated in developing strategic directions and approving policy for the IBM/AFE corporation in 56 countries including Canada, India, Japan, China and Latin America, representing the Latin America point of view in key business issues. Later in his career, he was Systems Software Associates General Manager for Latin America. Antonioni was also General Manager for Latin America of Lexmark international when IBM sold their printer and supplies business.  Antonioni also established Lexmark HQ in Coral Cables, Florida and implemented the Latin America channels.
In 1997, Antonioni founded his own company,  Southern Cone Advisors Inc. The company specialized in advising USA Companies and individuals on Latin America business opportunities, as well as in possible associations with the 200 USA Most Successful Small Co’s.

Antonioni will be actively advising the I/O Digital Team on strategic partnerships and global expansion of the I/O Digital Foundation.
The Advisory Board

Nadal Antonioni joins Marco Houweling, senior vice president finance TomTom, at the Advisory Board of the I/O Digital Foundation. The Advisory Board consists of top industry experts who advise the Foundation in their field of experience and contribute to the future stability and growth of the Foundation. We welcome Nadal Antonioni to our Foundation and are proud of Mr. Antonioni joining this amazing project. We are looking forward in working together.
Media Contact

Contact Name: Richard Groen
Contact Designation: COO
Company Name: I/O Digital Foundation
Contact Email: marketing@iodigital.io
Location: Amsterdam, Netherlands
I/O Digital Foundation is the source of this content. Virtual currency is not legal tender, is not backed by the government, and accounts and value balances are not subject to consumer protections. This press release is for informational purposes only. The information does not constitute investment advice or an offer to invest.

Hello I/O Coiners, some good news today we uploaded 90K binary via UI to our tesnet blockchain, we had done this prior via backend but this was our first test via UI. We are finishing up now with the download side to complete (the upload download) DIONS section.

With that said our official date to release the DIONS infographics and a very important Board Advisory announcement, is Tuesday 27th, 2016 as we now have full approval to inform the entire blockchain space of this very important advisory board member.


Have a Merry Christmas and Happy Holidays to everyone

I/O DEV TEAM

Answers for sidhujag,

1.

Question: How does data sharing work?

Answer: Data is attached to transactions in base64 encoded form (maximum 1MB). These transactions are then sent to wallets/addresses/aliases via the Blockchain.

2.

Question: Are you building blockchain services to use your aliases? (if so how would transfer work in conjunction with things that those aliases "own")

Answer: The aliases can be arbitrary not just ours, transfer work by sending the alias from one user's wallet to another. If you are referring to the purchase/sale of an existing aliases in DIONS V.1. The two parties would make an agreement on the sale and would have to either trust each other or use some form of escrow for payment and transfer of the alias.

3.

Question: What are stealth aliases all about? Zero-knowledge transactions or something else?

Answer: All aliases are initially encrypted for a fixed number of blocks when created as measure to protect against attempts by malicious users to copy the aliases. Therefore the aliases are encrypted by default for (at least 12 blocks) before being 'activated' (decrypted and made public) by the user.

In our original code, a user had to 'activate' as above his aliases before he could attach files or transfer them. We decided for our beta release to extend this by allowing users to keep their aliases encrypted while still operating on them as normal (attach data, transfer, update associated data). This way aliases e.g  brand names or whatever, can be established in encrypted form with the option to "publicize" the name later for example revealing brand ownership, at will when the time is considered appropriate by user, if ever.

So the “Private Aliases” for us means the possibility to encrypt using RSA the data or alias information that a user chooses. Private Aliases in terms stealth or of zero knowledge transactions has not been our aim at least for our initial release though we may include work in this direction later if their is community consensus on this direction, but again it's not our priority right now.

4.

Question: How do GPG file checks happen, is it part of consensus code?

Answer: We use RSA encryption for our messaging system. Signature verification is not an automated feature for our early beta releases but is planned for early on in our beta release cycle. File associated signatures can of course still be uploaded checked and verified manually, little clunky for initial beta, but the automation of this is not planned for our initial beta test release.

5.

Question: Are you using opreturn for your data(good) or a custom TX data field (bad), The data "field" is fixed and verified by consensus.

Answer: What do mean by custom?

What is essential is that the script structure is fixed so that the consensus checks can be applied.

6.

Question: How do you handle bloat with 1mb data fields?
          
Answer: The size is 1MB, not 1mb. For our initial DIONS release we decided to allow for relatively small data sizes. i.e. to keep it light weight; think twitter like messaging, avatars, copyright info. In a project following closely on the heels of DIONS, we plan to address the bloat issue, R&D work has already been carried out on this over the past year.

7.

Question: You obviously increased the max tx and block size because of this?
          
Answer: No.

8.

Question: if not how do you handle scalability if mass user acceptance happens?          

Answer: Our future plans of using side-chains connected via Chameleon to prevent bloat on the main chain.

9.

Question: Do aliases expire?

Answer: Yes aliases expire after a fixed set of blocks. For our initial release this is fixed so that expiry can be expected after approximately 12 months given the prevailing block generation rate.

10.

Question: Can they be extended?
          
Answer: Yes aliases can be extended even after expiry for another period with preference given to the current owner before becoming publicly available.

11.

Question: In section 6 of your DIONS white paper you go into a.b.c and how a can control b or c and b can control c ? Is this correct? How would that work?

Answer: Since that white paper we've decided to take the approach of * not * constraining the alias field to any particular format the fields are arbitrary.

12.

Question: Is that standard public key encryption messaging using the same curve used to sign transactions?
      
Answer: No, we use RSA encryption for sending encrypted messages as a built in feature.



PS. If we dont get to anyones questions in time, please be advised that we are currently extremely busy and pressed for time, as we are about to launch DIONS beta. We will do our best to answer questions as we get a break in.

Thanks Everyone

I/O Digital Dev Team