How it works

The identity is defined as the public master key of any node in a bip32 tree. This pub key can be shared, published at will, for instance on social networks.

Every signature can be traced to the corresponding public master key without ever exposing the corresponding private master key.

A demo

To test, you may download , then verify it on , and hopefully

.

Further reading

The post Â鶹´«Ã½É«ÇéƬ Deploys Bitcoin BIP32 Self Sovereign Identity appeared first on Â鶹´«Ã½É«ÇéƬ - The Standard of Verifiable files.

We are extremely proud to accompany the launch of their new bug bounty platform.

Note that Â鶹´«Ã½É«ÇéƬ offers ultimate confidentiality by encrypting using totally anonymized containers (that neither disclose any hint of who are the sender and receivers nor of what is the data), that may further be exchanged using your own cloud or disk.

The post Â鶹´«Ã½É«ÇéƬ launches a Bug Bounty program to crack our encrypted container appeared first on Â鶹´«Ã½É«ÇéƬ - The Standard of Verifiable files.

Further protecting your Â鶹´«Ã½É«ÇéƬ account means protecting an amazing range of your unique serverless collaboration : messaging, chats, ECM (document and content management, versions, classification…), processes, search, integrity.

The post Â鶹´«Ã½É«ÇéƬ Now Supports FIDO U2F authentication appeared first on Â鶹´«Ã½É«ÇéƬ - The Standard of Verifiable files.

One is . Git is the most widely used version control system. The emphasis of Git on data integrity builds upon an underlying scheme called “” and .

Content addressable storage may operate like this: given a file, one computes a unique hash from its contents, then manages to store and retrieve the data from the hash alone, henceforth being immune to renaming, moving and of course modification.

Merkle trees work like this: every node in the tree may contain the hashes of its subnodes. The hash of the node itself accounts for these subnodes hence locks the entire structure. Merkel trees are useful to Git, because for various storage efficiency reasons files are chunked into pieces and versions are stored by difference. Hence every file will be converted to a tree of content addressed blocks.

In Git, every data block or node is immutable, because the contents are addressed from the hash, and can then further be verified as genuine. The whole node structure is also connected.

Another innovation is the (also on wikipedia, on bitcoin.org). In a block chain (many abound besides Bitcoin), every block has a hash, and contains the hash of the previous block in the chain. [Computing this hash is difficult and called mining because the protocol requires blocks to be generated every 10 minutes on average by introducing competition among miners.]

In Bitcoin, every block  is immutable, and is linked to the chain of previous blocks down to block #0 called . It is also timestamped by the network. Internally, the block also contains a Merkle tree of the transactions that were included.

From there on, a question arises:

are documents more useful and/or valuable when they are mutable, or when they can be proved as unmodified?

Being immutable, it appears that document gains a wealth of useful properties. An immutable file may be :

• addressed by its content hash, hence becoming immune to renaming or moving
• verified for integrity, hence becoming immune to unwanted modifications
• be timestamped for inclusion in (smart) contracting processes
• be included in complex chains or trees of documents (versions, references…)
• …

So, can we benefit from these advantages within our own document organization?

Â鶹´«Ã½É«ÇéƬ generalizes immutability and connectivity to the whole set of your documents. But it does a lot more. Â鶹´«Ã½É«ÇéƬ not only computes an integrity identifier (idx) for every file but it also:

• encodes this idx so that it is usable as a name by humans (including on the phone)
• injects this idx in the file itself so it can be found or indexed by search engines, on a computer or on the web. It does not require a specific software or infrastructure to discover the files!
• injects into your very own documents references to other documents. However, in so doing Â鶹´«Ã½É«ÇéƬ ensures that searches for these references do not collide with searches for the document itself
• automatically chains versions of your files, also allowing when required multiple parallel versions
• injects the public key of your digital identity, so your contribution is locked in forever
• injects a signature of the idx with your private key, so that nobody can counterfeit you. Such a signature can also be verified without Â鶹´«Ã½É«ÇéƬ.
• injects more metadata allowing the statement of copyright, confidentiality statements, instructions to collaborators or any meaningful information (up to 4K)
• injects a specific hash compatible with (for example, search for 2HzFzM99P59PV4ssMhkC9bcZuzzjMdRNiYaqDTC at the bottom of this link)
• promotes your folder structure to a global tag system
• …

So using Â鶹´«Ã½É«ÇéƬ, one builds on his very own disks and without any infrastructure a provably immutable network of documents that can altogether be:

• trusted for their integrity and authorship : never wonder or reread
• fully interconnected for a variety of needs such as semantic tags, process marks, links to original files or versions or references : search, organize at blazing speed
• further connected to the bitcoin blockchain or any other : prepare for ultimate dematerialization and notarization scenarios
• addressed by their content at machine or web scale : instant and exact search with artificial words that generate zero collisions
• involved into arbitrarily complex automation schemes : build your digital heritage, for a future where semantics and trust will break data silos and allow for continuous process improvement

Start using Â鶹´«Ã½É«ÇéƬ and invest in your very own digital heritage.

The post The Future of Data : Immutable and Connected, like a Blockchain appeared first on Â鶹´«Ã½É«ÇéƬ - The Standard of Verifiable files.

Â鶹´«Ã½É«ÇéƬ lets users define per recipient sharing means (over weblinks, dropbox, google drive, even nfs or webdav) and encryption settings.

Then sharing targets can be selected in a single click: no groups, no access rights, extreme simplicity.

Â鶹´«Ã½É«ÇéƬ is a unique no infrastructure, #nosaas solution.

The post How One to One Sharing Enforces Secure Collaboration appeared first on Â鶹´«Ã½É«ÇéƬ - The Standard of Verifiable files.

Â鶹´«Ã½É«ÇéƬ lets users define their own identity settings using a social certificates: people who know you ensure that you are the one you pretend, in the absence of a certificate authority.

Social certificates can be renewed, published, revoked at any time, at no cost.

Â鶹´«Ã½É«ÇéƬ won an award at World Smart Week in the category e-Id and Cybersecurity.

Â鶹´«Ã½É«ÇéƬ is a unique no infrastructure, #nosaas solution.

The post How Social Certificates may help build Decentralized Trust appeared first on Â鶹´«Ã½É«ÇéƬ - The Standard of Verifiable files.

• Your files stay on Your machine (you may easily monitor the exchanges with our servers)
• You see your encrypted files (of course naturally if you choose your favorite cloud sync to share)
• We can allocate a dedicated private server for a company – even though the perspective of exchanging outside the limits of the company renders this choice questionable.
• Verifying a keeexed file (that uses SHA256) is possible using a public script (hence remains feasible should the Â鶹´«Ã½É«ÇéƬ company default)
• The Â鶹´«Ã½É«ÇéƬ digital signature (uses the elliptic curve Sekp256k1) can be verified qithout Â鶹´«Ã½É«ÇéƬ (for instance on ) (hence remains feasible should the Â鶹´«Ã½É«ÇéƬ company default)
• The format of encrypted files (that use AES CBC 256 IV and user accessible secrets) is made available by contract (hence remains feasible should the Â鶹´«Ã½É«ÇéƬ company default)
• As a last resort, Â鶹´«Ã½É«ÇéƬ writes ASCII Metadata in files, hence is fully compatible with the Unix system commands  GREP, FIND, LS… (hence allows for any automation should the Â鶹´«Ã½É«ÇéƬ company default)
• The information sent by the Â鶹´«Ã½É«ÇéƬ app to our servers to allow for notifications are not inversible (they are hashes).

Henceforth, the cryptographic features of Â鶹´«Ã½É«ÇéƬ are verifiable and accessible, even without Â鶹´«Ã½É«ÇéƬ. To date:

• Sha256 is known as immune to collision and pre-image attacks: it is thus impossible to create two documents having the same Â鶹´«Ã½É«ÇéƬ identifier, or a second document having the same idx as the first one,
• Sekp256k1 is known as inviolate : it is the elliptic curve used by the Bitcoin protocol: any flaw would destroy Bitcoin entirely.
• AES CBC 256 IV (with unguessable initialisation vector) is known as inviolate

We continuously improve the quality of our eexcution

The post Why Â鶹´«Ã½É«ÇéƬ is not the next ‘Bad Guy’ appeared first on Â鶹´«Ã½É«ÇéƬ - The Standard of Verifiable files.

And they are instantly received, and automatically moved next to their previous version if any.

They are also ultimately protected from prying eyes by automatic client side AES 256 encryption, and automatic receiver side decryption. No stress, no risk in the confidentiality of your industrial of intellectual property.

You pick a shared secret with a collaborator. Â鶹´«Ã½É«ÇéƬ recalls it, as long as you need.

The post Â鶹´«Ã½É«ÇéƬ now encrypts and sends in 1 click, according to per user settings appeared first on Â鶹´«Ã½É«ÇéƬ - The Standard of Verifiable files.