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, so this is largely uncharted territory.
The current plan is to provide technical requirements and a basic wallet for key management of standard coin accounts sufficient for the launch of public mainnet. Unlike the rest of Geeq’s protocol, wallet providers may configure wallets to appeal to users as they see fit, as long as they meet Geeq’s technical requirements.
The plan is similar for a Geeq micropayments wallet as a browser extension. Again, Geeq will provide technical requirements for other providers to adopt, develop plug-ins, and tailor for their own use.
Geeq’s micropayment transactions are not held to the same secure standard as regular coin accounts because the values of micro-coins are low and convenience may be the most desirable characteristic. For example, users may want to whitelist particular websites or streaming services without confirming signatures every time.
An important implication is that users must be provided a way to have some kind of “firewall” between standard coin accounts and micro-coin accounts. For more discussion of security, please see the roadmap entry for the hardware wallet.