dappconnect-sdks/apps/website/docs/status-communities/transfer-your-community-s-o...

42 lines
2.4 KiB
Markdown
Raw Normal View History

[website] Add documentation (#403) * setup md/mdx * add test page * setup mdx provider * Add breadcrumbs * links -> routes * add information box * add more remark plugins * text InformationBox * setup contentlayer * add testing docs folder * setup docs static generation * add ssg to blog too * add Shortcut component * add SearchButton * add hook for keyboard shortcuts * update main docs page * update main learn page content * side-bar -> sidebar-menu * rename docs pages * add heading anchors, use new components * add table of contents to docs * move styling to breadcrumbs * cleanup markdown examples * change slugify fn * update getting-started.md * add highlight matches component * update learn pages * rename website InformationBox to Admonition * ?enable user-select * add static helpers to epics * simplify components structure * update insights layout * add link tree utils * add search engine * update docs import * update contenlayer * add docs indexer * support code block highlighting * search index * fix types * remove supporting files * update tree builder * make build work * update docs * update label * update toc * add config.json * update menu * search index import * learn -> help * fix md file * update toc * fix code snippets * add help index route * remove testing files * add original docs * migrate getting started * migrate messaging-and-web3-browser docs * migrate network-nodes-and-statistics docs * handle empty content * add navigation config * wip * migrate status-wallet docs * migrate to new admonitions format * migrate your-profile-and-preferences docs * migrate part of status-communities docs * mv * rm log * index * fix lint * fix warn * fix title * fix docs layout * udpate next.config * use lowercase lang * generate contentlayer types before typechecking * update docs images * update help routes --------- Co-authored-by: Felicio Mununga <felicio@users.noreply.github.com>
2023-06-27 20:30:11 +00:00
---
id: 496
revision: '0'
language: en
title: Transfer your community's ownership
---
:octicons-beaker-24: Beta
If you can't manage your Status Community anymore, you can transfer the ownership to someone else. To transfer your community's ownership, you need a [backup of the community's private key][back-up-your-community-s-private-key].
When you transfer the ownership, the new owner's computer becomes a community node with full control of the community, including its settings, permissions and membership approvals.
:::tip
If you need help managing your community, consider adding others as admins. For more information, check out [Delegate admin functions to community members][delegate-admin-functions-to-community-members].
:::
## Current security issues you should consider
The current system for transferring ownership of Status Communities has two important security issues:
- The community owner has to share the community's private key with the new owner. Manually transferring the private key from one owner to another is an insecure method of handling a private key.
- There is no way to be certain that the community is fully transferred. After handing it over to the new owner, the previous owner may still have a copy of the private key. This means that an old owner with malicious intentions could potentially regain access to the community at any time.
We're working on implementing a token-based ownership model to solve these problems. In the meantime, be extra cautious when handling your community key and keep it safe. For example, don't save your community's private key in an online storage service or screenshot.
:::warn
Read and consider the security implications before you transfer the ownership of your community or become the new owner of someone else's community.
:::
## How to transfer your community ownership
Here's how to transfer your community:
- [x] [Back up your community's private key][back-up-your-community-s-private-key].
- [x] Handle over the private key to the new community owner.
- [x] Ask the new owner to [restore the community][restore-your-status-community] using the private key.
- [x] [Leave the community][leave-a-status-community]. If you wish, join the community again as a member.
- [x] Delete or destroy any copy you own of the private key.
\*[Beta]: This software feature is currently incomplete or in beta, and is subject to change at any time.