The Otterspace Badge Protocol is designed for use by communities. Every badge within Otterspace is generated by a community and is associated with a community. If you want to generate badges, you first need to set up a community.
You can read how to do so here.
Your community Raft Token
When registering a community on Otterspace, a Raft Token is minted (a ‘raft’ is a group of otters). This token is a transferable ERC721 that represents your community within Otterspace and acts as the admin key to the Otterspace protocol. The token id is used as the on-chain identifier of the community.
Any Badge that is created and minted as part of your community references this token id in its metadata. This way, all Badges have an on-chain connection to the community.
[2.1: Raft Token]
The wallet holding the Raft Token is the admin of the community and is able to create new Badges and distribute Badge-claiming vouchers to members. We recommend holding the token in a new 1 of n multisig wallet so multiple core contributors are able to create and distribute Badges. Read more about that here.
To see your Raft Token in your wallet, import the contract address:
0xa6773847d3D2c8012C9cF62818b320eE278Ff722 and set the number of decimals to ‘0’. Some wallets don’t display NFTs visually so you may only see your balance instead of seeing the token itself.
Transferring a Raft Token to another wallet
A Raft Token is a regular transferable ERC721 NFT, so it can be transferred between wallets. The wallet holding the Token is able to take action on behalf of the community.
Not every Ethereum wallet supports the easy transfer of NFTs from within the wallet interface, so we recommend using Quixotic to transfer the token - this will work with any wallet that supports Wallet Connect.
- Sign in with the wallet holding the Raft Token
- Navigate to the Token’s page
- Click ‘transfer’
The Gnosis Safe web app also offers a very straightforward way to transfer NFTs in case you are holding the Token in a Safe.
Guilds/Sub-DAOs (coming soon)
We plan to add the functionality to create sub-communities that can be semi-independently managed. The wallet holding the community’s Raft Token will be able to mint another Raft Token with a new name and identifier.
fig 2.2 : Space DAO example (wallet holding $RAFT can mint other $RAFT for sub-communities)
The new Raft Token will have a metadata field called ‘parent community’, which will reference the token id of the original Raft Token.
Badges generated by the sub-community will reference the sub-community’s Raft Token id instead of the main community’s Raft Token id.
The sub-community Raft Token can be moved to a different wallet and managed separately.
Distributing permissions (coming soon)
We are working on a way for communities to customize their permissions by choosing the following:
- Any community badge holder can create Badges
- Any holder of a specific community badge can create Badges
- Only the Raft Token holder can create Badges