---
# System prepended metadata

title: Community SBT EthDenver release
tags: [NDC, i-am-human]

---

# Community SBT EthDenver release
###### tags: `NDC`, `i-am-human`


We want to start rolling out parts of the i-am-human particles. The upcoming EthDenver & NEAR House will be a perfect moment for that.

Community SBT is part of the i-am-human system and provides community verification of humanity.

Projects we want to release:
* SBT registry
* Community SBT v1.0 (first public release):
    * Community SBT is issued by community and for community
    * Goal: verify if a person is part of community.
    * 2 SBT collections:
        * Trustees / OGs: well known persons (NEAR contributors)
        * Community: SBT that certifies that someone is part of the community.
    * Trustee Verification: 
        To get a Trustee SBT, it's required to have at least 3 other Trustees to approve you.
    * Community Verification: 
        * any Trustee can add issues Community SBT to any account.
        * any 5 other members can add any other account: meet other parts of the community and ask to be verified. We will prepare recommendation how anyone can verify that an account holder is part of the community.
    * expire: 9 months: you need to recursively ask community to verify you.
    * NOTE: Community SBT is not going to be proof of unique humanity, but a fact that an account is associated with an alive person active in the community.
        * That being said, gaming the system to hundreds of accounts per person will be challenging.
* NEAR House SBT:
    * SBT rewarded to accounts participating during the NEAR House, in live
    * verification is by person (proof of authority): set of admins will be defined to verify that an individual registered and is part of the NEAR House.

## Discussion

Noak proposed to already go full ahead and build Community SBT as a verification protocol for i-am-human.
Original plan for Community SBT was to be a unique human verified account by the community. Something similar to BrightID. However this will require more work:
* we will need to collect user private data
* obey GDPR regulations
* think how to correctly encrypt and link data

I think it will be better to focus on the _"OG SBT"_ (Trustee) and use it for the future `i-am-human` community verification. This way we will grow the community seed of verified (in person at the conference) users, while deliver community "badge" as well.


## TODO:
- [ ] document eligibility for Trustee (OG) - a guideline for all trustees about who should be part of it, some examples, counter examples and how should the verification process look like.