Additional Features

Administrative users may extend or revoke permissions for users to send transactions to a private blockchain.

Additional Features

The dev team upgraded the encryption algorithm to Ed25519. Ed25519 is efficient which is important for blockchain performance where each chain is expected to process large volumes of transactions.

The exercise of upgrading the encryption had independent value. It demonstrated the code is being written such that changing the encryption algorithm leaves the logic of all the validation checks intact. Put another way, the protocol works regardless of the encryption algorithm used.

As envisioned in Geeq’s White Paper, the dev team has shown that Geeq’s upgrade path is feasible.

Additional Features

Geeq’s standard merkle trees provide an efficient and novel way to encode a merkle path all the way to the transaction level in any node’s block. If a user has exact data on a transaction, it is straightforward to dive quickly into the Merkle trees.

The schema for the merkle trees was finalized for each transaction in the Validation Layer Block, the Validation Layer Ledger, the Application Layer Block, and the Application Layer Ledger.

The same merkle schema apply to every Geeq chain, private or public, regardless of the features included in the chain.

For an introduction to Geeq’s merkle trees, please see the June 2023 Technical Update.

Additional Features

The merkle roots for the Validation Layer Block (VLB), Validation Layer Ledger (VLL), and Application Layer Block (ALB or app block) were computed for Geeq’s Data app.

Additional Features

Geeq’s protocol is different from other protocols because it is a leaderless protocol. At Geeq, each independent node receives the same set of transactions and builds its own block. Each individual node is responsible for following the validation protocol exactly.

The protocol requires each node to sign (attest) to a content statement that contains their own Chain State View, based on their own computed merkle roots. By protocol, nodes determine whether or not other nodes share the same view and automatically audit those with a different chain state view.

For more details, please read the May 2023 Technical Update.

Additional Features

Private blockchain users may not wish to allow public or anonymous nodes in their chain’s validation network. Permissions were added to drop nodes from a network.

Geeq’s no-consensus protocol still holds each individual node accountable for following its strict validation criteria. In other words, Geeq’s private blockchain users are still protected, by protocol, from malicious individual nodes or from collusion of a group of nodes even if they do not delete such nodes.

The permissions exist primarily for privacy, changes in enterprise collaboration, or to make other changes in the active network list.

Additional Features

Private blockchain users may wish to authorize specific nodes to join their chain’s validation network. Permissions were added to add nodes to a network.

Adding nodes to a validation network allows private blockchain users to increase access and convenience to blockchain services, multiply network effects, selectively increase transparency, improve compliance, and seamlessly work with regulators.

Additional Features

Geeq-native NFTs and fungible tokens were added to Geeq’s original roadmap. As a result, two new asset categories were added to the schema for the original coin asset records.

A user’s coin asset account will include coins, NFTs, and fungible tokens.

Additional Features

Geeq Data established Geeq’s software product development cycle. As transactions were validated and written to a block, their data payloads were separated and written to a corresponding app block. Thus, the attestations were captured in time in the application blockchain. Pure data does not require the creation of an application ledger record.

An NFT does require the creation of an application ledger record. The record is written into the ledger when it is minted. The characteristics of the NFT are signed when the mint transaction is submitted, ensuring its provenance and description are fixed when the mint transaction is validated. For more details, please see the November 2023 Technical Update.

Additional Features

Ordinary user accounts are coin asset accounts controlled by its public-private key (PPK) pair. When a coin asset account is created, a coin asset account record is created in the validation layer ledger. These user accounts may contain coins, NFTs, and fungible tokens. A user may send and receive any of those assets using (the same) standard transactions. When those transactions are validated and written in the validation layer block, balances are updated in the validation layer ledger.

Proxy accounts are user accounts that require additional validation criteria. Conceptually, it is helpful to distinguish them from ordinary user accounts by imagining their functions. An individual controls their own coin asset accounts and may wish to assume anonymity. In contrast, an administrator may control a proxy account and wish to separate the proxy account’s PPK from their personal PPK.

A proxy account must be created in order to mint NFTs.

Additional Features

One of Geeq’s strengths is the ease with which it integrates Web2 or SaaS style apps with blockchain. The dev team prepared a NFT minting app for the community for the holidays. This was the first of many apps that can use Geeq’s NFTs!

For more details, please see the write-up in the December 2023 Technical Update.

Additional Features

Non-fungible tokens (NFTs) build logically on Geeq’s secure validation of transactions with application payloads and metadata. The issuer fixes the characteristics and terms of the NFT. An NFT is minted by sending an application layer transaction. When the mint transaction is validated, a permanent record is created in the application layer. No smart contracts are required.

Geeq NFTs are controlled by coin accounts, so transactions that involve existing NFTs interact only with the validation blockchain. The minting coin account is controlled by the introduction of a coin account subgroup called “proxy account”.

Additional Features

Merkle proofs for NFT transactions are available via API.

Additional Features

Administrative privileges were created to add and delete nodes in the validation network for a private blockchain.