Interconnected Identity Chains Part 1

ID, Genesis, Bevy, Passenger, and Republic all from the open protocol of ID
Part 1: ID

Three Things

1____I'm writing this in hopes of getting feedback from those of you who understand better than I do the intricacies of the blockchain and how to program a password protected interface that could import data into blocks in that chain.

2____This is going to be lengthy, and even if you don't read it all just comment the minute I say something crazy or impossible and tell me why.

3____I'm thinking the languages I'll have to learn to build this are Python or Ruby, and javascript, please tell me if you have a different opinion and explain why as best you can.

Thanks in advance for your time in at least looking this over.

The Flow Charts
I have created these flow charts to better depict my thoughts on the exact functionality of these applications and the network

The ID Interface, designed to create and secure identity chains (identity chain: a blockchain belonging to an individual person containing any data type in each block)

To initiate a new account with a unique blockchain, the fingerprint is scanned as the username and the ear canal is scanned as the password.

The ear canal is scanned to write data to the blockchain, any type of data is accepted onto the blockchain but the filename can never be changed.

A Block in the identity chain
can only be written after scanning the password
contains a unique key that will serve in the future as a link to the data block
contains the key to the previous block of data
contains the filename
contains a timestamp created by ID in UTC
contains the file data

The key, filename, and time are searchable in ID's database for every unique user.
Every block of data can be tagged with an editable structured database
Comments can be added to every structured data tag

The structured data, comments, filename, and time can all act as separate​ filters when searching for data
For every block, the key is required to access the data and an ear scan is required to authenticate access to the key

ID will contain a time-zone converter for the convenience of converting one's timezone to UTC when searching via the timestamp

ID can also generate the following types of files: text, video, camera, audio import
Before a new file is saved to the blockchain it is named by the user and authenticated
After a block is saved the user is immediately presented with structured data tags to tag and comment on the new file
A user can browse their files in their blockchain and edit the structured data tags and comments

The user's identity chain is hosted on a server where the user owns space for it

Contacts : The links between identity Chains

The more contacts you make the more secure your identity chain becomes. For this, ID will utilize a special kind of contact data that builds mirrored data blocks​ between two different identity chains.

Afterthoughts

However,
filenames can never be changed
files can never be deleted​
contacts can never be removed

Unless ID has a way to re-write a block in the data chain​ without changing the keys.

In order for ID to be a feasible means of storing data and maintaining a network, this ability is vital.
Because ID requires a username and password to access a specific identity chain for writing and using the application at all, nobody can abuse the application and tamper with an ID account from the ID application.

The Uses for ID are derived from users always having authentication control and ownership of their own data while still being able to share that data, selectively, through other applications written to complement ID's open protocol.

It's not foolproof, I know, but how risky is it?