Safe Haven Inheritance Platform (SHIP) v1.0 — Complete

The Safe Haven team is proud to announce that the initial form of our flagship product, the Safe Haven Inheritance Platform (SHIP), has been completed. After many long months of hard work, the SHIP, as explained in our ICO Whitepaper, is ready for action and, our team has several potential partnerships lined up for near-term integration. Like many great ideas, there are always improvements that can be made — and this is the norm for Safe Haven, we are already hard at work creating an enhanced version of the SHIP that will pave the way towards rapid mass adoption as we speak.

So, what does this all mean? It means that the programmed architecture (behind the great idea that originally attracted you to Safe Haven) has been established in a way that creates the necessary backbone of the SHIP. This means it can be integrated as originally intended as of today. It also means that in the time we have been bringing the platform to life, an important upgrade has been conceived. This upgrade will make the use case scenarios and platform integrations work more seamlessly.

Not only are we ready to begin initial testing of APIs and begin a closed beta program with some of our most trusted future partners, but we also have decided to keep our developer team hard at work in completing an upgraded version to be released within a few months. For ease of discussion, we will be labeling these two versions of the Inheritance Platform as SHIP v1.0 and SHIP v1.1, and will get into their specifics following a few important development milestones that lead to the completion of our initial product version.

Q1 Details: Critical Development Milestones

Before we get into the distinctions between the two versions of the SHIP, there are a few items that we should mention. These were the final points on our internal itemized roadmap which officially designated the completion of SHIP v1.0.

First, the contract system. SHIP’s contract system is a complex series of shares that are housed within each dedicated smart-contract. Two significant aspects of such are the storage of shares within the dedicated smart-contract and the deployment of the contracts themselves. These two aspects of the platform architecture are what make the Inheritance Platform “work.”

From here we finalized the addition of the notification system, which is the part of the platform that communicates with the trustees, benefactors and executors (amongst others), indicating which steps need to be taken and in what order they are to be followed. This process is initiated via the inheritance (or continuity) plan’s validator (generally a lawyer) — who logs into the account once the estate conditions have been met. His validation sends out an automated series of chronological instructions to all parties, which is what makes the platform intuitive and easy to use.

Next, the share authority model was completed and integrated. This key aspect of the platform’s code supports one of the crucial nuances of estate and continuity plans: shareholder weighting factors. This is similar to the concept of preferred stock, in that it allows for certain shareholders to have greater rights in regards to voting and/or the appropriation of funds. Bridging these types of in-depth legal understandings and smart contract architecture is what makes the Safe Haven team and products stand alone in Blockchain.

Finally, in order to begin the closed beta testing phase of SHIP v1.0 (more on that below) we needed to link the inheritance platform with a VeChain wallet system so that transactions could be tested. For this, we decided to integrate support for the Comet Wallet along with our custom client side key management system in our initial construct. As we continue to work on SHIP v1.1, other wallet integrations will be made creating a more robust and inclusive product.

The Inheritance Platform of Today — SHIP v1.0

If, like the majority of our community, you have read and reread our ICO Whitepaper line-by-line, then you will recall that the initial concept for the Inheritance Platform stated that “the software used for [the Inheritance Platform] will not keep any data in memory or in centralized databases” (p. 9). The purpose of this decision was simple: in order for this sensitive data to be as secure as possible, it should not be kept in a database that could be compromised, or in a centralized or cloud-based location where prying eyes may gain access to it.

Safety is most certainly our first priority at Safe Haven; however, far be it from our team to lose sight of the key factors that will enable our platforms and products to be comprehensive in every way — especially when it comes to:

  1. Ease of use
  2. Mass adoption

Needless to say, these two factors go hand in hand. In fact, most would posit that mass adoption cannot take place (quickly, if at all) without ease of use, especially when it comes to B2C product releases. The problem with our initial concept is that, without storing any data anywhere, the product is safe, but not easy to use — it requires that all consumers maintain and keep safe a printed paper version of their sensitive data to plug into the SHIP when the time is right.

So we found ourselves at a crossroads, where it seemed as though on one hand we had the maximum in security and, on the other hand, we had a product/platform that was easy to use. So, like any responsive company with a problem, we came up with an even better solution: the SafeKey 2FA Device.

When we started out with SafeKey, the idea was to have it work as a simple encrypted 2FA hardware solution that would integrate with our platforms and others. As the ease-of-use problem clearly demanded a stronger solution, we opted to enhance the SafeKey from the ground up in a way that endows it with an internal memory system capable of privately storing the essential data required of our community and customers. No centralization, no cloud, no security issues.

This brings us to the purpose behind enhancing our current iteration of the Inheritance Platform to the more robust and easy-to-use SHIP v1.1.

The Inheritance Platform of Tomorrow — SHIP v1.1

Ok, maybe not tomorrow, but soon. As we are a company that prides itself on completing our roadmap objectives on time, we decided to push forward with the initial construct of the SHIP and have it completed and ready to test as of the end of Q1, 2019: a feat that we are excited to have accomplished! This will allow us to conduct our closed beta test and work out any outstanding UX/UI obstacles and take the next steps with some potential partners that we are courting.

As part of our team works on testing the existing platform, another subset of our developers is already working on writing and integrating the necessary code needed to allow for our SHIP v1.0 to interface with the enhanced, memory enabled SafeKey system and thereby create the SHIP v1.1.

It is premature to give an exact date for the completion of these upgrades, since testing is an interactive process. However, at this time, we can say that within a few short months there will be a platform available to our exchange and business partners, and consumer customers alike, that will make digital asset inheritance both easy-to-use and perfectly safe. This combination is what will allow for mass adoption of this platform and the ensuing rise of Safe Haven technologies and protocols within the crypto-sphere and beyond.

Where do we go from here?

Our initial beta testing is being conducted between our internal team and carefully selected partners. Phase two of the testing will include a select group of our community members who show interest in helping us make the platform ready for public launch. If you are someone who would like to be considered for this aspect of the project, please let our moderators know within the Safe Haven Telegram channel and we will get back to you over the next month or two with instructions for participation.

We look forward to sharing more information about our partnerships and the progress we make in regards to the upgrades to our platform as we enter into Q2 — and if you have questions about how the new SafeKey will work, or how the platform functions, we will do our best to answer those in the proper channels as well.

Thank you for continuing to support our projects and for being a part of our mission.