By: Geeq  on Apr 10, 2024

March highlights:

• Append-only NFTs are code complete and moving on to QA
• Minimum block interval parameter is code complete and being tested by the dev team
• Work began on adding Validation Layer Ledger records to the Block Explorer
• The dev team is working to integrate NFTs with variable metadata fields and the append-only function with the notary app, wallet POC, and QA testing tool/automated script.

Append-only NFTs: A new function allows owners to add notes to the descriptions of their NFTs. It is code complete. The original description of the NFT is already preserved in the ledger record; every addition signed by the current owner becomes a part of the NFT’s historical record on-chain.

Geeq’s protocol is data agnostic, i.e. the owner may append any new data, including hashes of official documentation from other sources and pointers to other on-chain records. The append function includes Geeq’s metadata fields.

Examples of Append-only NFTs

A frequently cited use case: An accredited institution may issue a graduate an official, cryptographically signed certificate as a NFT. Using the append-only function, the graduate may add documentation for continuing education credits, thus building a permanent record of experience extending from the original certificate.

Different applications may be written to suggest different flows. For example, a job site may provide tags for letters of recommendation, publications, and sharing with other institutions. Other applications may create more personal experiences by providing the user a habit-tracker format or an initial NFT at the beginning of an experience.

To the protocol, the rules are identical. For users and app-developers, there is freedom to define which data to put on-chain and how. No smart contracts are required.

Minimum block interval: Different chains may receive transactions in different traffic patterns. A potential problem occurs when a blockchain writes too many empty blocks. Empty blocks add needlessly to storage requirements. Loading and searching a block explorer becomes slower and less convenient also.

The minimum block interval parameter helps tune the blockchain for its applications. Some blockchains may be used continuously because rapid, secure synchronization and feedback is required. A different use case is to share provably validated data with a regulator.

While the data is preserved in audit-ready format whenever blocks are written at Geeq, the use case of constant trading is different from regulatory compliance. Compliance may define regularly scheduled intervals, such as once per hour or day. Setting minimum block interval to a hour would write 24 blocks in a day compared to 8,640 blocks at 10 second intervals(6 blocks/minute * 60 minutes/ hour * 24 hours/day).

3. Updating the app ecosystem: As we mentioned last month, enhanced functionality requires testing the updated private blockchain with the application environment before releasing the next versions to the community.

A highlight this month was to begin work on Validation Layer Ledger (VLL) records for the Block Explorer (BE). These records contain updated balances of all assets in an account and the team is working to display coins and NFTs. Fungible tokens are on the roadmap.

We are excited about the progress on Geeq NFTs and hope users are inspired to use and/or build intuitive applications, while knowing on-chain assets are secure on Geeq. The possibilities are endless!

As always, thank you for reading and for your continued support.
– The Geeq Team