Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • H hive-io
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • hivehive
  • hive-io
  • Issues
  • #2
Closed
Open
Issue created Mar 17, 2020 by Scott jarvie@JarvieReporter0 of 2 checklist items completed0/2 checklist items

How to handle @hiveio account

  • We need a way to determine access to @hiveio chain account
  • We need a way to have trustless safe keeping of the more sensitive keys

Also are there other accounts we will need to do this with that should be considered community owned? Maybe witness consensus directed?

Assignee
Assign to
Time tracking