Shipping Update

Here are the latest shipping updates on your order. Your security is our main priority and we will never jeopardize this by shipping too early. We understand delays are not ideal, but in the end it will all be for the better. Designing and producing a hard-core security device is something that needs full attention during every little step of the way. Hardware takes time. Security takes time. 
That said, know that for any open orders, we accept cancellations and refunds at all times. No questions asked. Note though that we have a limited supply only for 2021 and that cancelling a pre-order pushes you back to the end of the queue and we cannot guarantee that you'll be able to place a new order as it all depends on our available stock (of course, all pre-orders have guaranteed shipping).

Sweat more in practice, bleed less in war- Spartan Warrior -

Overall Status (detailed updates lower)

🚧 Perform a complete production test run with v1.0🚧 If good for shipping, release firmware v1.0 πŸš§ Test 0.9, including business tests. Decide Go/No-go for shipping.βœ… Create a secured release (0.9)  βœ… Liquid app approved by iOS and Android stores (will be launched right before shipping)βœ… Coin testing: BTC, ETH, ERC20, BNB, LTC, NEO,         EOS, ZEC, TRX, DGB, DASH, DOGE & GRSβœ… Verified Bootβœ… Secure EAL7 OS integrationβœ… ZERO hardware assemblyβœ… Fulfilment flow ready to go

## Progress update 10/9 ## 

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


Summary

Version v0.9 has completed functional testing. The previously mentioned issue with the transaction flow has been solved.


We are now preparing the production test run. There is still an issue with the secure activation of the communication layer between the secure element and the main chip. However, if debugging proceeds well, we expect to be ready for a test run by late next week.


Meanwhile we are using the time to perform more business tests with new users. This allows us to catch any remaining and mostly cosmetic issues. 


Once both remaining tasks listed above are done, we can release 1.0 and proceed to a 100% complete production test run, putting us very close to a final shipping date. 


What's next: 

βœ…  Finish testing release 0.8 and review testing results

βœ…  Confirm and apply the fix allowing upgrade over USB over Mac computers 

βœ…  Release firmware v0.9 containing the fixes for firmware upgrade as discovered in 0.8

βœ…  Solve transaction flow issue

βœ…  Functional testing of v0.9

🚧  If good for shipping, release firmware v1.0 

🚧  Finish preparation for production test run 

🚧  Perform a complete production test run with v1.0

## Progress update 26/8 ## 

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


Summary


Version 0.9 has been released. This version contains the firmware as frozen earlier this month, and is now being thoroughly tested to remove all remaining bugs preventing us from shipping. 


We have not yet been able to give a GO for shipping, as there is still an issue with the transaction flow. It is a relatively straightforward bug, expected to be fixed this week. 


The good news is that upgrades work as expected. We also used the time last week to perform an additional security review of the device. 


Production Test 

Flashing production units at the factory requires us to prepare reliable and secure tools and processes. We can't go into much detail here, but we can mention that all development work has been completed. 


Once we have released the firmware 1.0 we will be able to complete a 100% complete production test run. 


What's next: 

βœ…Finish testing release 0.8 and review testing results

βœ…Confirm and apply the fix allowing upgrade over USB over Mac computers 

βœ…Release firmware v0.9 containing the fixes for firmware upgrade as discovered in 0.8

🚧Test 0.9, including business tests. Decide Go/No-go for shipping.

🚧If good for shipping, release firmware v1.0 

🚧Perform a complete production test run with v1.0

## Progress update 12/8 ## 

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


Summary

With this update, we can start with the good news that all known issues have been solved. 


However, the required modifications represent a meaningful change in the firmware which we shall combine and test in release 0.9. This release will be ready in the coming days. 


As before, this release introduces no new features. We will again perform complete tests over the weekend, including business tests which will allow us to decide whether or not we are ready for shipping. 


Next week we will send an update with our testing results and whether it’s a Go/No-Go for shipping


As we are still testing the final version of the firmware, all development is frozen for new features. We only make changes for critical bugs. In the last update, we had released and were testing v0.8. During testing last week, we discovered an issue that caused upgrades to fail. As upgrades have to be 100% reliable, we spent last week debugging this. We are happy to have found the cause, and have meanwhile written the patch, applied it, tested it. All seems to be working correctly now. We have also tested and confirmed the fix for the bug preventing upgrades with Mac computers, which was still uncertain at the time of the last update.  


Production Test 

Flashing production units at the factory requires us to prepare reliable and secure tools and processes. We can’t go into much detail here, but we can mention that all development work has been completed. 


Once we have released the firmware 1.0 we will be able to complete a 100% complete production test run. 


What’s next: 

βœ…Finish testing release 0.8 and review testing results

βœ…Confirm and apply the fix allowing upgrade over USB over Mac computers 

🚧Release firmware v0.9 containing the fixes for firmware upgrade as discovered in 0.8

🚧Test 0.9, including business tests. Decide Go/No-go for shipping.

🚧If good for shipping, release firmware v1.0 

🚧Perform a complete production test run with v1.0

## Progress update 30/7 ## 

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


Summary

Last week we decided to freeze the firmware. This led to release 0.8, which we have been testing this week. We are now reviewing the testing results and will decide whether to go for 1.0 or if any issue remains for which we need to update the firmware. 


The most recent activity has been focused on firmware upgrades. This has to be 100% stable before we decide to release 1.0. As mentioned in the last update, there was an issue when trying to upgrade using Mac computers. We have investigated this issue last week and suspect we have found the issue. The fix is going to be tested in the next few days.


If testing keeps going well, we expect to proceed to release 1.0 very soon, hopefully next week. With this version we will be able to do a complete production test run. 


Secure Boot

βœ… SECURE OS: The secure OS is confirmed to be release-ready.

βœ… LINUX: We have secured the linux kernel, it is ready for production. 

βœ… GUI: We have integrated the audited user application firmware 

βœ… GUI: Full test of the newly integrated, audited application firmware.

βœ… Obtain final approval of all involved security experts.


Code is frozen and being tested. Next update will mention whether testing was successful and or if changes were required. 


Coin Operations 

βœ… The design issues have been solved for those operations requiring an extra PIN code input. 

βœ… Patch to the coin application running in the Secure OS

🚧 Test, validate the above patch. 


A new patch for Ed25519 coins is ready. As we do not want to delay shipping even more, we have decided to already freeze the firmware without this patch. If not, we would have had to wait for a new testing round to finish. We can be certain that those coins will be added in the next firmware upgrade. The bulk of the work has been done, we just need to test and bugfix so an update with this patch which will include the remaining coins will follow shortly


As shipping is our highest priority, we will test this patch only after the release of firmware version 1.0. 


Production Test 

Flashing production units at the factory requires us to prepare reliable and secure tools and processes. We can’t go into much detail here, but we can mention that all development work has been completed. 


Since the end of last week we are testing the tools, incrementally activating all security protocols. Once we have released the firmware 1.0-beta we will be able to complete a 100% complete production test run. 


What’s next: 

- Finish testing release 0.8 and review testing results

- Confirm and apply the fix allowing upgrade over USB over Mac computers 

- Release firmware v1.0-beta 

- Perform a complete production test run with v1.0

## Progress update 19/7 ## 

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


Summary

Since the last update, the user application has been fully tested. No issues were found. We are now preparing a full code β€˜freeze’, meaning that no further changes will be allowed. The firmware will then remain unchanged, ready for release, while we are finalizing the preparation work on the production tools. 


The production tools have been developed, and we are now testing their use with a process of signing and securing a gradually more complete version of our device, until we are ready for 1.0-beta. The difference between the releases so far and 1.0-beta will be that it is fully secured, using the production keys, and made with our production tooling, which is a 100% complete production test run. 


The final step will be to test firmware upgrades. We do not expect any issues, but it is paramount that we can rely on this functionality 100%. We have a firmware upgrade tool that works reliably on Windows and Linux. We are now testing the Mac version, on which we are still experiencing some issues. Our main priority is to ensure any issue is unrelated to the ZERO as we only want to ship a device that can be upgraded from any computer.  


Secure Boot

βœ…  SECURE OS: The secure OS is confirmed to be release-ready.

βœ…  LINUX: We have secured the linux kernel, it is ready for production. 

βœ…  GUI: We have integrated the audited user application firmware 

βœ…  GUI: Full test of the newly integrated, audited application firmware.

🚧  Obtain final approval of all involved security experts.


Testing is completed, we are holding feedback rounds with all stakeholders as the code is being prepared to be frozen and production tooling is being tested.


Coin Operations 

βœ…  The design issues have been solved for those operations requiring an extra PIN code input. 

βœ…  Patch to the coin application running in the Secure OS

🚧  Test, validate the above patch. 


A new patch for Ed25519 coins is ready. As we do not want to delay shipping even more, we have decided to already freeze the firmware without this patch. If not, we would have had to wait for a new testing round to finish. We can be certain that those coins will be added in the next firmware upgrade


Production Test 

Flashing production units at the factory requires us to prepare reliable and secure tools and processes. We can’t go into much detail here, but we can mention that all development work has been completed


Since the end of last week we are testing the tools, incrementally activating all security protocols. Once we have securely flashed the firmware 1.0-beta we will have completed a 100% complete production test run. 


What’s next: 

- Obtain final approval of all involved security experts

- Freeze the firmware version and prepare release 1.0-beta

- Finish the firmware upgrade tool for Mac computers 

- Incrementally test the secure flashing procedure until we have flashed a feature-complete, secure release 1.0-beta with the production tools.

## Progress update 9/7 ## 

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


Summary


We made good progress on securing the device. However, we had to delay the acceptance of the newly integrated GUI. There were some complications with the patch for coins using Ed25519 cryptography. These coins are eGLD, XLM, AE, XTZ. We will now continue with the production test run. 


Below you can find the relevant sections from the previous post with updates. 


Secure Boot

βœ… SECURE OS: The secure OS is confirmed to be release-ready.

βœ… LINUX: We have secured the linux kernel, it is ready for production. 

βœ… GUI: We have integrated the audited user application firmware 

🚧 GUI: Full test of the newly integrated, audited application firmware.

🚧 Obtain final approval of all involved security experts.


As mentioned in the previous update, the firmware responsible for the actual user interface on the device has been put through a thorough audit and review. Since the last update, we have integrated these changes together with the below mentioned patch for Ed25519 coins. During testing, we discovered that the coin operations patch was not yet sufficient, which caused some delay in the testing of the GUI. We expect to make good progress on the final acceptance testing in the coming days.


Coin Operations 

βœ… The design issues have been solved for those operations requiring an extra PIN code input. 

🚧 Patch to the coin application running in the Secure OS

🚧 Test, validate the above patch. 


In the last update, we mentioned we had patched the Secure OS with a fix to enable coins using the Ed25519 elliptic curve. These coins are eGLD, XLM, AE, XTZ. We have tested this patch but it is not yet fully ready for production. Instead of delaying shipping, we shall continue support for those coins on a separate track. 


Note: This task is not blocking us from shipping, as the secure upgrade has been tested and validated. 


Production Test 

For a full test run we had to first completely finish securing the release version of the firmware. As this is now complete, we expect to make significant progress on this over the next few days.


Keep in mind that it’s only about preparing the software tools here, everything related to hardware - assembly, testing, inventory - has been ready for some weeks now.


What’s next: 


- Complete the full acceptance testing of the final GUI. 

- Obtain final approval of all involved security experts

- Finish the firmware upgrade tool for Mac computers (it already works for Windows and Linux)

- Set up the tooling for the production test run. 


We are always open for any feedback or questions. As always, we highly value your continued support.

## Progress update 28/06 ## 

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


As mentioned in the previous update, in order to start shipping your ZERO, three last tasks need to be completed and stable: Secure Boot, Coin Operations and Production Test. We have progressed well on each of these and you can find the latest status update per remaining task here below. You can find both a high level status and a bit more technical one in italics.


Secure Boot

To start shipping, we need to have the firmware on the ZERO to be audited, secured and locked. This means that we remove all features that are useful for development, but are a security risk if left enabled in the final product. 


βœ… SECURE OS: Since the last update, the secure OS is now confirmed to be release-ready.

🚧 LINUX: There remains some work related to managing both a development and release version. (1)

🚧 GUI: Integration of audited user application firmware. (2)


(1) The non-secure OS runs a custom Linux kernel. We are disabling features in the kernel that are invaluable for development purposes. To prevent a horrible debugging experience during development, we had to find a way to load both kernels. This allows us to load only the one we want, while maintaining the ability to easily switch between versions if we have to debug. We expect to have finished this task in 1-2 days. 


(2) The firmware responsible for the actual user interface on the device has been put through a thorough audit and review over the last few weeks. This resulted in some changes in the application firmware which makes it faster, more stable and better maintainable. It also eased the process of securing it. Last week and during the weekend we started integrating the changes. We have one bugfix remaining before we can test it, which should again not take more than a couple of days. As mentioned in the previous update, this was not to add features but to solidify the existing functionality.


Coin Operations

βœ… The design issues have been solved for those operations requiring an extra PIN code input. 

βœ… Patch to the coin application running in the Secure OS

🚧 Test, validate the above patch.


In the last status update we mentioned that we still needed to change the designs of the user interface for coins using Ed25519, since those require us to enter the PIN code more often. After further testing, it has been decided that the application running in the secure OS needed some updates as well. These have now been applied, and need to be tested. Before we can do this, however, we need to have finished the integration of the rework of the application responsible for the user interface as mentioned above (2).  


Note: This task is not blocking us from shipping, as the secure upgrade has been tested and validated. 


Production Test 

For a full test run we have to first completely finish securing the release version of the firmware, as mentioned above (2). Keep in mind that it’s only about preparing the software tools here, everything related to hardware - assembly, testing, inventory - has been ready for some weeks now.


What’s next: 

- Complete the work for the closed Linux release version 

- Finish integrating and test the refactored application for the user interface. 

- Test the patch allowing us to test and integrate Ed25519 coins. 

- Set up the tooling for the production test run, while awaiting the closed Linux release.



Your patience and continued support are very much appreciated. We also reiterate that completing a qualitative and secure product is our absolute priority, and backers who don’t want to wait any longer can request a refund.

## Weekly progress update (17/06) ## 

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


 Latest achievements


βœ…   Firmware version 0.6 has successfully been delivered and tested. 


In our last update we mentioned how the last issue with the firmware upgrade had been resolved. Since then, we have prepared the release and tested it on several devices that were previously running version 0.5. No new issues have been found, and upgrades work reliably. This is the first release to enable a fully verified bootchain, effectively guaranteeing that the ZERO will only run our firmware. The few roadblocks we encountered have been documented in the last 2 updates, and we are proud that they have now all been overcome.


There remain 3 tasks before we can start shipping, all of which have been started and are currently 

being done in parallel: 


🚧   Secure Boot: With our boot verification, we can be sure that the ZERO runs our firmware. We are now preparing the release version of the firmware, meaning that we are disabling all communication channels and are putting our code through a thorough review to ensure all security requirements are correctly implemented. This is not about adding new features, but rather, removing them. 


🚧   Coin Operations: Most coins have been tested & are functional, with the exception of coins using a different cryptographic algorithm (Ed25519). Those coins are XLM, AE, eGLD and XTZ. Due to a cryptographical difference in this algorithm, it is not possible to create new addresses without having to enter the PIN again. This is not according to our current designs, but we are experimenting with a design iteration to solve this. However, we don’t want shipping to be delayed because of this. 


 πŸš§   Production Test: Test run with secure keys. This is a test run of our operational setup. We can’t go into too much detail here, but it is important to realize that we have already assembled and tested a large number of devices that are now only awaiting our final firmware. We want to be able to fulfill orders at a fast pace once shipping starts. The production setup has to be capable of flashing multiple devices without impacting security. 


Your patience and continued support are very much appreciated. We also reiterate that backers who don’t want to wait any longer can request a refund.


We remain 1000X committed to making you proud of having joined us from the start.

## Quick update about the progress (10/06) ## 

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


Here is the progress we made over the last week, including more clarity for the remaining tasks before shipping. 


Latest achievements


We experienced some bumps in the road, but are back on track to prepare, release and test our latest release candidate.


Details: As mentioned in the previous update (June 3), our nearest target was delivering version 0.6, a feature complete release candidate. Our requirements for it were that it should contain all coins & have all features activated to verify the device during each boot (verified boot). We reached both goals last Friday. However, over the weekend we discovered that the device couldn’t boot anymore when attempting a firmware upgrade.


The cause for the firmware upgrade boot failure has been identified, and has now been solved. This was the cause: in the previous update we mentioned how we modified the memory layout to make our device more future proof - allow more space to accept firmware upgrades of larger size. This change impacted the work we had prepared for the boot verification task, causing issues to verify the integrity of the firmware upgrade boot partition. The positive takeaway is that the secure boot alerts worked as they were supposed to. The fix has been committed,tested and validated.


We are again on track for testing of the release candidate. The time has not been lost, as everyone has been extremely busy testing all aspects of the device not related to verified boot. Any testing we do now makes the need for a new release less likely.



Milestones until shipping


βœ…   Device Firmware: All aspects of device behavior excluding issues related to coins (see further). For example power management, secure operations, communicating with secure OS and much more. This work has been thoroughly tested, validated and is practically complete.


🚧   Coin Operations: We are now continuously performing integration tests for each coin, so that we can guarantee their correct behavior. Bug-fixing effort here is by now reduced to specific tasks per coin, mostly on the mobile app. Following coins have already been tested and validated: BTC, ETH, ERC20, BNB, LTC, NEO, EOS, ZEC, TRX, DGB, DASH, DOGE & GRS.  


βœ…   Verified Boot = ZERO will only boot software that has been signed by NGRAVE. This task can only be done as one of the last steps, as it makes debugging issues related to the device firmware much harder. We worked on this the last 2 weeks, and it is now practically complete.


🚧   Secure Boot: Once we guarantee that the firmware on our device can only be ours, we have to remove all possible sources of communication with it except via firmware upgrade. This is the step following the release 0.6. It has been prepared is now a matter of activating & testing. At best it will take a couple of days, but we can’t exclude that it might take longer.


🚧   Production Test: Test run with secure keys. This will be done in parallel with the Secure Boot task. 


We know that you prefer to have clear deadlines. And we remain optimistic that the first devices will be shipped this month. The reality is that we did not take the easy road and have developed all firmware for the device from scratch for maximum security. This comes with its challenges.


We also reiterate that backers who don’t want to wait any longer can request a refund. We know we have shared optimistic timelines, but we will never put speed to deliver in front of security.

## Quick update about the progress (03/06) ## 

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


Since the last update, there remained 2 major tasks to be done before we could proceed to v0.6:

  - Have all remaining (non-xpub based) coins pass automated tests

  - Activate all security features, to simulate a fully secured release


* Over the weekend, we were able to finish the full integration and activation of all security features. This was a big milestone for us. We had prepared this as good as we could, but there is always the risk of new and unforeseen issues if you bring it all together. No new issues were discovered, which was great news.


* After activating the security features, it was important that we could confirm that every step in our security design was correctly implemented (verifying the correct authentication of all pieces in our system). We experienced some frustration here, as some parts of the code used in the signature verification tools provided by the chip vendor had been modified and were not correctly documented anymore before the integration. This caused several days of delay before we could fully confirm the correct workings of the secured boot chain of the ZERO.


* As I write this, we managed to solve this last task only a few hours ago. We are now able to finish the tasks related to security and move on to actually preparing release v0.6, which will be deployed on our testing units tomorrow


* In v0.5, we deployed an automated testing script to validate the proper working of the deployed coins. This helped us to identify and resolve issues much faster before starting the manual test cases


* Meanwhile, the preparation of the non-xpub coins was delivered yesterday, and we have already begun manual testing of each coin. This way we will have more confidence when we make release v0.6. While we are still encountering some issues, we are noticing that the frequency of encountering those which can be considered as blocking has dramatically decreased. At this point, it often takes more effort to find them and report them, than to fix them. 


* Tomorrow we will start preparing release v0.6 and if all goes well we should be able to release it by the end of the day. Meanwhile we will keep testing all coins on v0.5 for 1/ manual coin tests and 2/ test the firmware upgrade again once v0.6 is released.


* We have high hopes for v0.6, as this could potentially be the release candidate. In order to not give false hopes, we want to stress the fact that if an important issue is found that requires more research, we could see a v0.7 as release candidate. We will communicate accordingly.

## Quick update about the progress (28/05) ##

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


- Progress on testing v0.5: Functionality for all xpub coins and ERC-20 has been thoroughly tested, and we’re satisfied with the results. We also tested all other features not related to coin management, such as fingerprint, power management, camera etc and found no issue, except for some instances of firmware upgrade.   


- In some cases, going from v0.4 to v0.5 failed. Firmware upgrade needs to be rock solid, but is also difficult to debug due to all security measures in place. As we suspected, the issue was due to the same difference in compilation environment that was solved last week, but it took some time to confirm.


- Progress on v0.6: Resolving the issue with firmware upgrade took a bit longer than expected, and we now expect the new release to be ready early next week, instead of already this weekend. The reason is that progress on having all coins pass automated tests was halted while we were debugging the firmware upgrade issue.

 

- In parallel, we are also enabling all remaining security features that we had to postpone until the final release candidate, to not hinder development too much. For example: encryption keys will be configured, anti-tamper always enabled. Other features will also be enabled, but we prefer to no to go into too much detail here.

 

- For this part. the progress has been going well, and since yesterday the whole configuration was working in at least one development environment. We now make it ready to be integrated in release 0.6.

## Quick update about the progress (25/05) ##

β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”


- We have started testing release 0.5 over the weekend: Testing is not yet finished, but no blocking issues have been identified which is very good news.


- Version 0.6 is being prepared: All remaining coins are being added as we speak, each one has to pass an extensive array of automated tests before 0.6 can be released.


- Release 0.6 will also add some other remaining features: LED operation during normal operation and during upgrade process, a button press configuration that allows us to activate a recovery mode.

It will also enable some settings that were tested separately, but were disabled during previous tests, related to security; anti-tamper detection, locking the device with one-time programmable encryption keys, disabling firmware downgrades.


In a best-case scenario, we will have 0.6 ready by the end of this week, which we will test over the weekend. 

With no new issues & all tests passing, we will be ready to start flashing units for shipping. If there are blocking issues, we will communicate it here.