Safe Haven: July 2019 Development Update
Despite the holiday period and the fact that we were not in full force, our team did not sit still. We continued our efforts in order to maintain our development targets and due dates.
Safe Haven Inheritance Platform
SHIP documents are being encoded and processed in order to create a comprehensive collection of dynamic web pages that will give an in depth overview of Safe Haven’s Inheritance Platform. These libraries are covering the following topics:SHIP Introduction Pager — Refurbished whitepaper SHIP User Guide — Step-2-Step/how-to guides, including some best practices SHIP LLD — Low level design of the platform SHIP SK Design Docs — SafeKey design including in-depth protocol description and firmware API SHIP SK Software Docs — SafeKey SDK description, including server and client library examples SHIP Intellectual Property — Safe Haven’s overview for patent, licensing and copyrights
The documentation will be made available through the https://docs.safehaven.io url (currently password protected) and a public Github repo in which users will be able to send PR and comments/questions in order to make the docs more accurate and understandable.
We all know that in SHIP, our TAN is an important asset of the ecosystem as a user/initiator can add a verified legal entity into several protection plans, nevertheless our inheritance platform can work completely automated by the usage of, what we call, dead man switches (DMS). This means that the release of the smart contracts (through a decryption process which are explained in the SHIP-docs in detail) are triggered after a pre-selected period of time. A few predefined death man switches are:Login; CONDITION — last platform login Mail; CONDITION — mail link click SMS; CONDITION — reply by SMS Phone call; CONDITION — answer by phone
These trigger conditions can be an ‘and’ or an ‘or’ operator based on the configuration chosen b...