GigLabs Update

It has been a good month since we started real world testing of our Alpha release of GigApps. We successfully completed a couple of projects using the application and the two development teams. We encountered a few bumps in the road through the process of running the Alpha. We are now taking the feedback and lessons we learned to plan, design, and develop the future release of GigApps.

Stay posted for announcements from GigLabs and our Alpha customers/partners about some of the projects completed on GigApps.

CryptoRome Update

As we mentioned last time, we also did an internal test project that we called CryptoRome. If you have not had a chance to check out our blog post on digital assets from our CTO, Brian Burns, you should give it a read:

CryptoRome’s big pre-sale event starts on May 17, 2018. You can think of it as a Kickstarter campaign with a fund raise goal. If the goal is reached, we will commission the game to be built using our GigApps platform — we would essentially become our own first customer.

From a Lean Startup perspective, we will learn whether or not the customer even wants CryptoRome before building it, which is great. If not, we would not burn any more time or resources having the actual game built.

If you haven’t read our previous post regarding Lean Startup, you can find it here. As a note, we’ve also been applying Design Thinking/Lean Startup principles to the presale event itself.

From a Design Thinking perspective, all we did was create the website and description of what the game will be (i.e. a mock-up of the product). We quickly introduced this to the public and are continually gaining feedback.

From a Lean Startup perspective, we identified the actual goal metrics and assumptions we would need to validate at the very beginning. We decided to try a viral engine of growth. Our assumption was that if we achieved certain social media metrics, we would have a successful sale. These social media metric goals were based on analysis of other successful blockchain game pre-sales. Whether successful or not, we will do a full analysis on all aspects of what worked and what did not.


We will be finishing up our last project using the Alpha release of GigApps next week with a SaaS service offering for protection of data from tampering. We are calling this service GigSign. This SaaS offering will accept the encrypted hash of any file and write that hash to a few public blockchains. No one in the public will be able to know anything about what the data actually is (a hash is just an encrypted representation of data). However, customers can prove irrefutably that the data or file existed on the specific day/time in question and none of the data has been tampered with or changed.

Why is this important?

GigSign is useful when it comes to intellectual property and contracts, as examples. Specifically for intellectual property, now companies will have an option to have their scientist’s and engineer’s files digitally signed with an immutable public blockchain to prove when they were created. If there is a dispute at a later date, they will have undeniable proof of being first and having prior art. This also ensures that the documents were not tampered with, red-lined, etc.

GigApps is a decentralized blockchain development platform that utilizes smart contracts and freelancer teams to work on projects as they are funded on the platform. For more about GigApps and the GigLabs team, please visit us at

Douglas Dimola