Developer Support

Specifications for wallets

First, wallets for Geeq are separate projects from the core development of the Geeq protocols. Nonetheless, the topic has been revisited often internally. At present, wallet projects are not allocated many resources, primarily because findings on user requirements will emerge as transactions and applications are launched on private chains.

Wallets for tokens are notoriously difficult to use and there is no model for a platform with native applications. Geeq prioritizes ease of use as well as security,

 » Read more about: Specifications for wallets  »

Hardware wallet

Geeq will launch public mainnet with support for a well-defined set of transactions and features to support an open platform of applications. Even though every standard coin account (with the exception of coin_micro accounts) will be able to control $Geeq and multiples of NFTs and fungible tokens, future users may decide to make accounts on multiple Geeq chains and for multiple applications.

Geeq also will employ an encryption algorithm to provide more quantum resistance than older blockchain platforms provide currently.

 » Read more about: Hardware wallet  »

Code libraries

Testing and research existing code libraries is part of the development process, as needed. Geeq foresees the need to provide new code libraries to supplement existing ones.

 » Read more about: Code libraries  »

Documentation

Ongoing, internal documentation for developers are updated as new versions and features are released. Specifications for the Multi-chain architecture, including the additional features, is complete: through $Geeq cross-chain interoperability.

Strategic partners and clients will make requests for additional documentation as well, which will guide final documentation to be released with public mainnet.

 » Read more about: Documentation  »