By: Geeq  on Aug 15, 2023

• Improved feedback to Geeq client: Geeq now sends enhanced feedback to client applications
• Expanded logging possibilities with CloudWatch: logging system can now be accessed via AWS CloudWatch
• Merkle proofs can now be requested through the Geeq API

Last month, we announced that key aspects of Geeq’s validation layer — including Merkle root computation and proof generation — are code complete. Since then, we have made improvements to client-side feedback in the event of transaction failures, enabled Geeq chain logs to be monitored on AWS CloudWatch, and made Merkle proofs accessible through the Geeq API. Collectively, these new features will make it easier for DApp developers and script writers to integrate Geeq data into their existing data systems and workflows.

Geeq client feedback improvements

The Geeq API allows developers to certify and verify the reliability of data from any source linked to a Geeq chain. This month, we have made improvements to our feedback system to make it easier for developers to bug test software that uses our API.

In the event a transaction fails, there could be a number of causes and outcomes. One possibility is that the transaction is “non-sane”. This could occur if a transaction is incorrectly signed, for example, or as mentioned in our May update, if a transaction is targeted to the incorrect chain. A non-sane transaction will be immediately rejected by the receiving node, will not be forwarded to the other nodes, and will not appear on chain in the invalid list.

Another possibility is that the transaction is signed correctly and forwarded by the receiving node, but is then rejected by the other nodes. This might occur if two duplicate transactions with the same nonce are submitted to different receiving nodes, for example. In this case, the transactions will fail the joint check and will appear on the invalid list.

It makes sense not to submit every transaction from the receiving node to the other nodes. Indeed this is one of the reasons why Geeq is efficient: there is no point wasting time and network resources on a transaction that fails a sanity test, especially when transactions should be directed to a different chain. However, it could be challenging for developers to bug test their software without having more information about why a transaction failed. 

The latest enhancement to our feedback system will inform the client what type of transaction failure occurred, even in the case of non-sane transactions. These improvements will make it easier for script writers and DApp developers alike who use the Geeq API to bug test, handle exceptions and improve the user experience. 

Geeq can now send technical logs to AWS CloudWatch

We are committed to helping enterprises adopt blockchain gradually. This is why we want Geeq to be as easy as possible to integrate with existing enterprise software, data systems and logging tools. The reality is that AWS commands an estimated 32% share of the cloud infrastructure market and is one of the most widely used monitoring tools by DevOps teams. In particular, AWS includes a service called CloudWatch that enables devs to track metrics, logs, and events related to online resources and applications.

This month, we have added a feature that enables logs from a Geeq chain to be sent to CloudWatch. It is important to note this would be solely used for technical logging purposes and that no application or on-chain data would touch the cloud server. This would give enterprise clients and/or DApp developers the option to consolidate all their logs from various online projects and Geeq chains in one place, thereby streamlining their workflow. 

Merkle proofs now accessible via Geeq API

In our June update, we reported that Merkle root computation and proof generation was code complete. In July, we updated the Geeq API to make these proofs accessible from the client side. It is now possible for a client to request a proof that a specific transaction is included on a Geeq chain — for example, a notary transaction that includes the hash of a certain document. The proof can be stored offline, is roughly 1KB in size, and can be traced to the Merkle root. This promises to be a key feature for recordkeeping, compliance and auditing purposes.

Summary

Geeq’s validation layer and portable proofs of inclusion make it a highly reliable way for enterprises to track their data and verify its authenticity. However, no matter how technically sophisticated a blockchain network is, it must also be easy to adopt for end users. This month, we have been working on features which will make it easier for developers and enterprise clients to adopt Geeq and tailor it to their existing workflow. 

We hope you enjoyed reading and, as always, thank you for your support!

– The Geeq Team