Topic: I/O Coin - Ticker: IOC - Stealth Blockchain Ecosystem - Dions - Chameleon - page 116. (Read 719184 times)

Hey Folks, hope everyone is doing well. I wanted to share with you guys something that happened to me with my Galaxy S6 phone. So long story short my phone would not recognize my fingerprint, the backup password failed to be recognized and even the google password was not working. The phone was inaccessible, So I tried locking the phone to then unlock it remotely and that also failed. With no more options available I was forced to do a factory reset but before I did that I tried changing my google password.  After changing my google password the phone was still locked out as it also failed to recognize the new password. I had no choice and proceeded to reset my phone. Once the phone was reset, I was surprised to find that Google and Samsung have a feature called FRP which would leave me phone less for 72hrs.

At this point I was so appalled by the entire thing that I sprung into a full on research. I found so many people facing the same issue, but the sad part was a few people were offering boot loader to remove the FRP. I looked into one of these loaders and as I had suspected they were infected with malicious code. So here are Samsung and Google trying to protect customers, but Hackers found an opening with desperate users and pushed them these bootloaders. The users in some forums were ecstatic, but they had no clue that they were also injecting malicious code into their phones.

I proceeded to do what I do best and I was back in my phone by the morning so no issues with me. I bring this up because this is a perfect scenario as to why BlockChain technology is so important in our lives. In the near future, it would be a possibility that the imei of a user's phone, identity and or fingerprint will be registered against your private key [in our case your Aliases] for purposes of securing your gadgets. The phone or gadget would ask for a passphrase, do a query to the I/O Blockchain and unlock that said phone, gadget, home, car etc upon confirmation. This scenario is one of many of the things that will be possible, if implemented, by a company using our blockchain as part of  the internet of things.

As we proceed to complete these api calls to the wallet, It is also imperative that our Blockchain It's also capable and at the ready to handle millions of transactions for the near future.  Once Dions is out, Im sure private and public entities will come in and do aggressive stress testing to ensure that we meet the requirements for them to adopt our Blockchain.


With this in mind,  I don't want people to think that DIONS is a walk in the park, it has been challenging and aside from the core capabilities we are also looking ahead and discussing these scaling scenarios. Everyday you hear folks coming up with all sorts of new ideas of what the blockchain can do and the requirements that will be needed for the long term success of them. I'm excited for the times ahead, but at the same time I'm cautiously optimistic, and want to be very clear with the community once again. We are not here to make features just to have the price pump. Our dev team is a very serious team and we are committing ourselves to do the best work that we could possibly do. Now is the time to make these changes before we grow to big, in the future, forking would be almost impossible if  we were to scale to fast. Therefor we are not in any kind of hurry to release crap code just to satisfy short term holders. To the team and I, security is always at the forefront. When we release DIONS we will have an open source chain, but some features will have to be protected for a period of time to ensure we are not copied on release. We have plans to further our development as explained in our roadmap to chameleon and we hope for continued support from the community and blockchain enthusiast. As the project manager I've given 200% to our project and I personally continue to invest heavily in our project because as I've said before, I believe that in time we will have our spot in this space, but this will only come with a long term commitment, hard work and dedication. Rest assure that I always have everyone's best interest in mind and will continue to do so as we move along.

I want to take the time to thank the entire team for their continued hard work and dedication. To the community thanks for the support, continue to stake and keep on rocking.


Big Hug to Everyone


Joel

Thanks for the dump, IN again @3k it's a nice price to be in, the coin is really active, hope to see it back over 15k

update: 3:49

Ok Folks  bittrex ioc wallet is back online they had a block reorganize  

Working again

Checking For you guys why is disabled.

Thanks


Update: 3:27pm

No News from Bittrex, we are waiting on a reply from them stand by

Bittrex "disabled" now. What has this to say? Hmm

Just checked Bittrex and i can see the top waller #0 has dropped around 20k coins, this is really great, combine this with now only 662k IOC for sale, from a previous 1million, really great to see coins are going to long term holders.

I said I will write something about Raspberry Pi and also how to connect it to a PC. If tings are still unclear you can let me know. This post is still at a higher level as detailed instructions of each step can take up volumes on their own.

First of all it is important to know that a Pi is just another computer working pretty much the same way as other computers. The main advantage is that it uses a small form factor with parts that consume little electricity like the ARM7 processor. It provides connectivity options so that you can add several types of add-ons that you might want to use for different types of projects. You can run the Pi2 with a 5V 1A adapter.  This makes the Pi ideal to run wallets that need to run for long periods e.g. staking wallets.  There are several operating systems (OS) available for the Pi including Linux types as well as Windows 10. In essence if you understand the PC counterparts of the OSes then the Pi will be a breeze because they are very similar.

Loading the Pi:

When you get a Pi you also need storage space to install and run the OS. The Pi does not have a built-in hard drive like a PC and therefore you need to add a micro-SD card for storage (SD for the older models). The card you get will be blank that does not help much. You have to prepare the card by putting an OS on the card. Typically this can be achieved by downloading a Pi compatible OS from https://www.raspberrypi.org/ in the form of an image file (.img). This file is then "burned" to the card by putting the micro-SD into an SD adapter, inserting that into your PC and then using a tool to do the work for you. Popular tools include Apple Pi Baker on the Mac and win32diskimager on Windows. For the purpose of compiling/running wallets I recommend Raspbian Jessie. Raspbian is a Debian Linux on Pi and is currently at version 8 (Jessie). There are basically 2 options for your OS - downloading n00bs or downloading Raspbian Jessie straight. n00bs is an installation image that helps you with the installation process and gives you the option to choose which OS you want to install. You can download any of these and both will eventually get you to the same point. There are also installation instructions available for both.

Eventually both options will take you through a series of steps to get to a command prompt. At one stage or another you need to get to an app called raspi-config which is the tool you use to configure the installation. In raspi-config you will typically configure a password, name for the pi, if it must boot to the command prompt or directly into the graphical desktop, resizing the card partition (important step if you download the Jessie image), updating raspi-config, setting up SSH and many others. If you get to the command prompt which is a black screen with a prompt something like pi@mypi:~ $. This means you are in your home folder and ready to type in commands to the operating system. the "~" character is another way to write your home folder and is similar to /home/pi. If something refers to a folder called ~/opt it is the same as saying /home/pi/opt. ~/opt is just the folder I like to create and put stuff in but you can actually put the binary any place. Another important thing to know is that if you want to execute something as "root" which is the name of the superuser in Linux, your account needs to be in the sudo group and you can put sudo in front of your command to execute it as root. If you want to execute something on a Pi you have to put sudo in front of the command if you want it to execute with higher privileges.

If you get to the command prompt and it stops there it means that your Pi boots to the command prompt. In order to show the graphical desktop you need to type in "startx" and execute and it will load the desktop. If you are in the desktop and want to execute at the command prompt, you can open a terminal window. Commands in Raspbian is similar to commands in Debian for PC and includes commands like "sudo apt-get update", "sudo apt-get dist-upgrade" and "sudo apt-get upgrade". These commands will update your OS and installed packages to the latest version. "sudo apt-cache search partlofnameofdependencyyouarelookingfor" is a nice command to use if you are search for which dependencies you need to install, because there are differences in the names of some of these between Pi and PC. Another command you will use a lot is "ls -la" which gives a detailed listing of files and folders in a location.

From this point on it is similar to Debian on PC and lots of Raspberry docs exist with detail commands etc.

Linking a Pi to your PC:

The best way to do this is to install VNC server on your Pi (currently 5.3) and then install the viewer on your PC. There is clear instructions on the realVNC website of how to do this. When you install the server on the Pi, there is a series of steps you have to follow including choosing a password and getting a license key for the free version. Make a note of your ipaddress of the Pi by executing "ifconfig" at the command prompt. Enter this in the viewer screen on your PC and it will connect, presenting you with a Pi desktop on your PC. You can get VNC for Pi at https://www.realvnc.com/download/vnc/latest/ The instructions is very clear.

Firewall:

Whatever you do, it is always a good idea to enable the firewall on Pi. The easiest firewall to use is the uncomplicated firewall (ufw). You should always enable this when you prep a Pi and needs to be done once unless you turn it off again. "sudo ufw enable".  The default setup is that all incoming connections are blocked but all outgoing connections are allowed. If you want to connect to your Pi with VNC or SSH, you have to enable that on the firewall. If you know your PC IP address, you can just enable communications from your PC. If your router is configured to automatically assign IP addresses through dynamic host control protocol (DHCP) and you think that your IPs might change from time to time, then you can allow communications from the whole subnet in your firewall rule then it will always work. The examples I use is just there for availability and can be secured much more by configuring more granular rules by IP, port etc. You can also configure a firewall rule for the port that the coin uses to allow incoming connections if you want that.

SSH:

SSH is a tool to remotely connect to your Pi from Linux/Unix/Mac. SSH is a beast on its own and has a rich manual for how it works. I will give a few rudimentary options for using it. In order to allow SSH you need to go onto your Pi and type in "sudo ufw limit 22". This will open up port 22 for SSH from anywhere with the added advantage of slowing down the time for the next password guess if someone tries to guess your password. If you do not want to use passwords you can use a long cryptographic key which is more secure and configure the key on the Pi and your PC, but for that you can read up in the manuals. The basic configuration is to use the password of the account you want to connect to on the Pi. If you have enabled the firewall rule and you are on a Mac/Linux, you can open a command prompt on your PC and type in ssh yourpiusername@yourpiipaddress and it will ask you for a password. The first time it will complain about the host being unknown but you can just say that it must add the host IP and key fingerprint to your local PC. I know it is not the most secure but this post is just to get things working. It is your own task to read up on how to SSH securely. If you enter the password correctly you will be presented with a command prompt on your Pi but on your PC. Lest assume your Pi has an ip address of 192.168.0.10 and you want to connect as the pi user, then you would execute "ssh [email protected]". If you want to copy files to and from your Pi you can use the secure copy command (scp) that also works through port 22. The syntax for this command is you copy something from somewhere to somewhere. You must first prepare the folders on the Pi where you want to copy something to or on your PC if you want to copy something to your PC. You must also make a note of the paths on both sides becuase you have to tell scp exactly where to find a file and where to put it. In its most basic form you can use the commands as follows:

Copy a file from your PC Downloads folder to the Pi. In this case we will copy a bootstrap.dat file for iocoin using the parameters assumed above. Remember it is scp from to.
Type into your PC terminal window "scp ~/Downloads/bootstrap.dat [email protected]:/home/pi/.iocoin" when you execute it will ask you for a password and copy the file from your PC to the Pi.

Copy the same file from your Pi to your PC.
Type into your PC terminal window "scp [email protected]:/home/pi/.iocoin/bootstrap.dat ~/Downloads" when you execute it will ask you for a password and copy the file from the Pi to the PC.

When you are done with SSH and scp then close the firewall port by executing on the Pi "sudo ufw deny 22". To confirm that port 22 is closed execute "sudo ufw status verbose".

Putty:

Windows does not have SSH built-in as standard. You have to use a tool for that and many people use "putty". I dont really use putty but the principles are similar. There is a tool called "metro putty" in the Windows store that works nice. There is also "Bitvise SSH client" that has some nice graphical file transfer capabilities.

This is it for now. There is much more to the above especially on security, but this post was ment to be a rudimentary intro to what you need to get going on the Pi.

Hello Community......


We started to work on the implementation of the api codes into the wallet and build of the environment. We ran into some build errors with
regards to the Dions wallet prototype on OSX. After some debugging we decided to build a server to set up gitlab & gitian, as we are sure it was a compiler problem but with gitlab & gitian it will add continuous integration and help us make our builds automatically from now on. In the meantime we switched to linux as my main dev platform just until the prototype progresses reasonably. After that will take care of windows and OSX testing of the Dions V.1 wallet prototype, with the integrated api calls. Once we get the first few calls in the wallet, then things should progress faster.


I/O Digital Dev Team

Fantastic update, thank you.   DIONS is a big developments and important step along the I/OCoin digital road, as you say, once DIONS is realised, people can see and use the product, then this will lead to a influx of investment from VC's, it is going to be a smart and profitable choice for the VC that takes on IOC first.

I really lie the idea of the app also, sounds great, i can see this being a big plus point in the future for companies accepting payments. If i could buy items 10% cheaper and all i had to do (this is how i imagine it will work) was buy £xxx of their own digital currencyto use on the website, deal done!


And as stated once one company joins many will follow.  I hope we can see DIONS in the next few months, but understand these important developments take a lot of time to finish.

Keep up the great work IOC Team!

Thanks a lot for the update! Sounds very good, exciting times ahead. You guys are doing an awesome job, holding strong!

Hi,

yes good volume. I catched 50k yesterday so thats off the market ;-)

About VC: when things come to that we have to be very careful what to say. Every letter we type can be seen as a "yes there is a VC" or "no VC ever". I can say that we are in contact with a few VC's and one actually received our investment proposal. They are screening it as we speak and watching us closely. A director of KPMG is helping us to create the best document there is. The chances are small that we get the investment short term though. This is mainly because the VC's want to have a working prototype to show for.

Thats why we are pushing for the delivery on DIONS. When we deliver DIONS (yes we will), then we have a few services / companies waiting to jump in on connecting. One of them is www.spinnit.nl (not yet a fully working website - and in Dutch) They will launch an app soon where people can sell and buy stuff in their social network. It can also be integrated into webshops (thats the easy explanation). They want to have their own Digital Currency and want to use our chain for that. Also possibly store extra data in it.

So, after we connect the first service, then its an easy sell for us as you can imagine. The talks will continue and we are very sure they will jump in when they see the time is right. We are also looking to registering I/O Digital as a company soon.

Next to this we are having a lot of attention in the FinTech media. Like the European Fintech awards and the Benzinga Fintech awards. Also getting interviews for magazines these days.

So a lot going on behind the scenes! I am very proud on what we have achieved so far and are confident I/O Digital will get the investment needed and the place in the top 5 Blockchain companies in the world. This is what we aim for!

Joel will update you on the development soon.

Cheers
Richard

Good volume today

How is the contact with the VC firms going team? Can you give an update ?

Cheers

Ill make another post in n00b speek covering the items your post including connecting the Pi to your PC.

the code is:  wget https://bitbucket.org/jc12345/iocoin/downloads/ioc_installation_pi_j.sh && chmod +x ioc_installation_pi_j.sh && ./ioc_installation_pi_j.sh && rm -f ioc_installation_pi*   (including the trailing * - all the bold text)

yes you need to get online. UTP connection much better though

Ho Richard,

ah ha! Your explanation is much easier to understand, thank you. But what is the exact "code" please

"execute the installer url that has been provided"    i cant see anything here.

Also, i need the pi online first, quite a task when i am trying to do it with the wifi dongle. Been at it all day since the morning... and i am cursed by the fact i wont stop until it works.... going to be no sleep for me.

So for now.

What is the command "text" i need to write to instal the QT wallet please, thank you.

Simon,

A PI always tries to login with the default login pi/raspberry. Thats why it immediately logs you in.

You can change the credentials in the configuration (click the 'start' menu) and then look for pi configuration. If you have done that it will prompt you a password when you startup the next time.

Don't do that immediately, but first install the wallet / config (its just a matter of opening the command prompt on the pi and execute the installer url that has been provided).

a PI with a wallet is nice, but it is not best suitable for PI newbies. You have to know a bit PI and Linux maybe to config it.
It is a whole new world. I have it up and running. The basics i did myself but the iptables (firewall) and remote desktop i had help from a sysadmin.

=edit=
yes, you need to be connected to the internet
no, you cant (easy) connect it to your laptop screen, you need a screen attached to your PI

with "executing the installer" is meant to copy paste the link below ON THE PI in the command window (that is also present at the top menu in the pi)


Just copy / paste press ENTER and (if you are connected to the internet) everything is installed for you.
If you have an "disk space error" be sure to check previous post to expand the full file system

Good luck
Richard

Sorry i should of mentioned the following.

I am using a Raspberry pi2 with the latest Jessie OS update.

Notes:
The new OS does not use a command prompt to get to the desktop, it does this automatically.
The new OS does not ask for a password or username.


Please write in non coder speak, its hard to understand for a newbie like me

"execute the installation script in my post"

Problems. I am not connected to the internet. Do i have to be connected to the internet?
What Script?
What do you mean by execute?
How can the QT be installed automatically if i am not online?

"The Qt wallet is installed in ~/opt "

Where do i find ~/opt  ?

Where do i find the bootstrap file?

2 and 3.  i will go with option 1, it seems the best.

There are steps here, that presume other things are set up on the Pi. i have a new pi. not set up for internet or nothing.

Hope that makes sense.  many thanks Simon.

Note for other people. You really need a big screen, if you do not have a monitor, buy one, it will save a ton of hassle. I am trying to figure out how to connect my pi to my laptop screen, thats a day or two job on its own, easy to find ip addreesses and such, but then you have to figure out how to connect the pi, even with putty installed and such it will not work.

Let me clarify a few things around your post:

There are a few ways to install and use the wallets:

1. Prepare an 8GB+ Raspbian Jessie card in your Pi2 and execute the installation script in my post. This will install the dependencies and install a dynamically linked Qt and headless wallet on your Pi automatically. The Qt wallet is installed in ~/opt and there is an icon on the desktop that you can execute. Remember that to get to the desktop you have to execute startx at the command prompt. You will need to download and install the blockchain separately. This is the option that I described in my instructions.

2. Get a blank 8GB card with nothing on it. Download the 8GB IOC prepared .img file to your PC and burn the image to your card with a tool like Apple Pi Baker or Win32Diskimager. You can then insert the card into your Pi, boot, change any potential settings with raspi-config and run the wallet. This option will have the Qt and headless wallets, the dependencies and blockchain already installed and loaded on the card. This option does not exist yet but is what you have requested me to do - to create the .img file.

3. Prepare a card like in option 1, but instead of executing the script download a statically linked wallet and run that. You then still need to download the blockchain manually and install. I dont like static wallets in Linux and therefore I wont choose this option.