b88f7e73da
* 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>
1.7 KiB
| id | revision | language | title |
|---|---|---|---|
| 490 | 0 | en | Understand token requirements in communities |
In Status, there are two kinds of communities: public and private. If you want to [join a private community][join-a-status-community], you need to meet the token requirements set by the community owner. To maintain access to a private community, hold the necessary tokens at all times.
For example, a community owner can set up owning 10 SNT as a requirement to join their community. In that case, you need a minimum of 10 SNT in your [Status Wallet][status-wallet-your-quick-start-guide] to join that community.
There are three kinds of tokens in the Status app: assets, collectibles and ENS (Ethereum Name Service) names. Community owners can set up any combination of these tokens as a requirement to join their communities.
:::info When you join a private community, the token or tokens required to join are not transferred to anyone. They are used for verification purposes only, and they remain in your possession and wallet. :::
If you meet the requirements
Before you join a private community, the Status app automatically checks if you meet the community requirements. If you meet the requirements, the option to join the community is available.
:::info If the community owner has set [manual approval][manage-community-join-requests] option for their community, you still need the owner's approval to join. :::
If you don't meet the token requirements
If the request button is greyed out and unavailable, it means that you don't meet the token requirements to join a community in the Status app. To apply to join the community, you need to have the required amount of tokens. To buy the required tokens, read [Buy crypto][buy-crypto].