OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Wallets

Goki

Goki is a suite of Solana programs for key management and security, including a timelock-capable multisignature smart wallet and a token signer that authorizes transactions through NFT or token ownership. It also provides a TypeScript client SDK.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Goki — OpenViST project profile in Wallets.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Consider Goki when building Solana key-management flows that need multisig, timelocks or token-based signing, particularly when control is expected to move among a team, hardware wallet and DAO.

Who it is for

  • Solana teams that need shared wallet control with timelocked transaction execution.
  • Protocol developers who want to assign different permissions to NFT- or token-based credentials.
  • Projects planning to shift control from a local wallet toward hardware-wallet, multisig or DAO ownership.

Documented uses

  • Coordinate transaction signing through a multisignature Solana wallet.
  • Add timelock capabilities to smart-wallet transactions.
  • Authorize transactions based on possession of an NFT or token.
  • Represent distinct protocol roles—such as contract upgrades and fee setting—with separate credentials.
Before you choose

Requirements & limits

  • The smart wallet supports multisig and timelock capabilities; the token signer uses NFT or token ownership as a signing credential.
  • The README describes the code as unaudited and says APIs are subject to change during active development.
  • The repository states that the project is licensed under AGPL v3.0 and describes source-sharing obligations for changes, including private use.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Plan a staged transition of Goki signing control

Organize the intended progression from a local NFT-key wallet toward hardware-wallet, multisig, and DAO control.

Before you start

  • A local wallet for development using the NFT key.
  • A Ledger or other hardware wallet for the later NFT-key stage.
  • A Goki multisig wallet for the mainnet/production stage.
  • A DAO for the later governance stage.

Steps

  1. Use a local wallet for development with the NFT key.

  2. When the project becomes more serious, send the NFT to a Ledger or other hardware wallet.

  3. For mainnet or production, use the multisig wallet.

  4. After sufficient traction is established, send the NFTs to the DAO.

Expected outcome

A staged ownership progression is outlined, moving from local development control toward DAO-held NFTs.

Guide limitations

  • The README describes this as an intended use case and does not provide implementation, deployment, or transaction instructions.
  • Hardware-wallet models and specific DAO integrations are not specified.
  • Goki is in active development, APIs may change, and the code is unaudited.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
18 October 2026
Original website title
GokiProtocol/goki · Official homepage title · retained in its source language
How we review sourcesSuggest a correction