I/O Coin (IOC) DiONS VM | Messaging | Data Storage | Chameleon | DeFi

[aleet]

Hi guys. Virustotal gave this results of the scan. Whats causes of these results? Is wallet safe?
Cylance   Unsafe   20170807
Rising   Malware.Undefined!8.C (cloud:7QWcvcZMOpE)   20170806
Symantec   ML.Attribute.HighConfidence   20170806
WhiteArmor   Malware.HighConfidence   20170731

Possibility of false positive. I've been using their wallet for a long time now. Avast pro and malwarebytes doesn't give me any warning whatsoever.

[Harpo]

Not much happening in here, when can we get some updates?
Or is there a slack?

[Flash86]

Not much happening in here, when can we get some updates?
Or is there a slack?

Join the slack channel, there is much more disscusion than here.
Link for slack invite:
http://goo.gl/Y0ppnX

[kb4scv]

https://www.tradingview.com/chart/?symbol=BITTREX:IOCBTC


Nice chart.  Thx @cercamOn in slack.

[kb4scv]

IOC is getting ready to make a move.  They are almost done with new wallet and DIONs.  First step in a much bigger plan.  Very well done and thought out.  These guys will be around for a long time.

[ECore]

Not much happening in here, when can we get some updates?
Or is there a slack?

Join the slack channel, there is much more disscusion than here.
Link for slack invite:
http://goo.gl/Y0ppnX

Love slack. Thanks for link.

[plankton643]

Do I neeed to register my name/address in the "Ions registry" in the wallet for any purpose?

[videogamer939]

Where is the wallet on the website it says coming soon? also why is the marketcap so low on a coin that's been out for so long?? i am confused??

[georgehuang]

 They are almost done with new wallet and DIONs.  First step in a much bigger plan.  Very well done and thought out.  These guys will be around for a long time.

[IO Dev Team]

Development Update August 9th 2017

Hello everyone hope your all well, we have been quite busy putting the final touches to the wallet, here is our community update.


Sorry for not having it yesterday but the upload took long time was done around 4am and just finished the upload. Doing the best I can for everyone.

CLICK BELOW

To all interested in IOC our team is constantly updating in our slack channel, reddit and or telegram.
Any questions that you may have you can find an answer quicker in telegram or slack. We can load both apps in our mobile devices and therefore it has been more effective.

Please follow our team updates


Telegram

https://t.me/joinchat/CqVqS0O3PjCTx9bfp4CwOQ


Slack

https://iocoin.slack.com



Thanks To all our friends and Community

I/O Digital Development Team

[cryptocoinnl]

to add:

Slack invite can be requested at www.iodigital.io/slack

[fuongy]

For anyone interesting in understanding the alias part of the new DIONS release there is a good explanation in slack.

There will be 2 types of Aliases a public and an encrypted (private)

registering aliases is done in 2 stages first stage is encrypted and then second stage is to make it public if you want to (but dont need to).  The second stage checks if anyone else has it to avoid 2 people with the same alias.

All aliases last for 200k blocks.

you can only send funds to other users Alias if it is a public Alias.

[fuongy]

Update (from slack)

Currently the team is working on the bootstrap

bootstrap is a mechanism for the wallet to download the chain via compressed file and unloads it for a super fast sync

Go DIONS....

[fuongy]

From ioc telegram,  exciting times ahead.

the IOC team has other plans in the future for a commercial company that needs a good Blockchain. We are not building the IOC chain just for others. We create this chain also for our own future business to use. We only trust something we know every detail about. We know is secure, stable, fast and full of features we need. Again, yes we will market more visible when DIONS is out. No need to worry guys.

[sidhujag]

I took a look at the src. Are there unit tests? I couldnt find any dions tests.. please make sure you do these they are important for when people place trust in your system with real money.

There also may be a fairly serious MITM attack possible it seems with the creation of dion aliases. You will need to seperate the creation of your alias into 2 steps. First you will need a reservation tx that will send the hash of the alias data to the chain and then use that as input for the alias/dions that represents the hash. This will remove the attack vector. Now im not sure if because you are forcing everyone to create encrypted aliases before making them public solves the issue, but the idea is that someone would be watching for alias creation txs and simply frontrun squat the alias hoping his tx reaches the miner first. Have you thought about this?

Overall good job lots of work put in. Im not familiar with your message and relay system enough to understand if its good at a code level but overall it seems fairly tightly related to an older syscoin/namecoin codebase implementation. The only attack that may be possible found was the aformentioned one. Its a pretty easy fix and isnt that bad if noone is creating the dions on a mainnet or trying to steal the names. If it is truly an issue it may become an issue if left unresolved. I believe emer has the same issue but they have ignored it for now. Gjob looking fwd on seeing it in action!

Jag

[fuongy]

While I'm not on the core team I will try to get a response, the team is so focused on security and have spent many months testing, there will also be a live video with questions and answers. Feel free to join the slack , I'm confident that DIONS will be released with no compromise on security.

I took a look at the src. Are there unit tests? I couldnt find any dions tests.. please make sure you do these they are important for when people place trust in your system with real money.

There also may be a fairly serious MITM attack possible it seems with the creation of dion aliases. You will need to seperate the creation of your alias into 2 steps. First you will need a reservation tx that will send the hash of the alias data to the chain and then use that as input for the alias/dions that represents the hash. This will remove the attack vector. Now im not sure if because you are forcing everyone to create encrypted aliases before making them public solves the issue, but the idea is that someone would be watching for alias creation txs and simply frontrun squat the alias hoping his tx reaches the miner first. Have you thought about this?

Overall good job lots of work put in. Im not familiar with your message and relay system enough to understand if its good at a code level but overall it seems fairly tightly related to an older syscoin/namecoin codebase implementation. The only attack that may be possible found was the aformentioned one. Its a pretty easy fix and isnt that bad if noone is creating the dions on a mainnet or trying to steal the names. If it is truly an issue it may become an issue if left unresolved. I believe emer has the same issue but they have ignored it for now. Gjob looking fwd on seeing it in action!

Jag

[kb4scv]

Haven't seen another project out there that I think took other people's money more seriously than IOC.   That is about the last item I am worried about here.

[IO Dev Team]

I took a look at the src. Are there unit tests? I couldnt find any dions tests.. please make sure you do these they are important for when people place trust in your system with real money.

There also may be a fairly serious MITM attack possible it seems with the creation of dion aliases. You will need to seperate the creation of your alias into 2 steps. First you will need a reservation tx that will send the hash of the alias data to the chain and then use that as input for the alias/dions that represents the hash. This will remove the attack vector. Now im not sure if because you are forcing everyone to create encrypted aliases before making them public solves the issue, but the idea is that someone would be watching for alias creation txs and simply frontrun squat the alias hoping his tx reaches the miner first. Have you thought about this?

Overall good job lots of work put in. Im not familiar with your message and relay system enough to understand if its good at a code level but overall it seems fairly tightly related to an older syscoin/namecoin codebase implementation. The only attack that may be possible found was the aformentioned one. Its a pretty easy fix and isnt that bad if noone is creating the dions on a mainnet or trying to steal the names. If it is truly an issue it may become an issue if left unresolved. I believe emer has the same issue but they have ignored it for now. Gjob looking fwd on seeing it in action!

Jag

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

[SuWide]

Is there a release date for DIONS?

[kb4scv]

Is there a release date for DIONS?

They are getting close.  Still some testing and bootstrap for wallet to go.