BitBadges Integration #118
Replies: 3 comments 6 replies
-
|
I think this would be a great idea especially if it can adopt some of the other proposals here #59 at the same time. Implementing it on chain would also remove the need for IPFS/ETH dependencies i think right? Aspects to consider:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the suggestion @trevormil. If you weren't aware, the solution the core devs would like to build is covered in the FAQ.
I think this data is important enough to store on chain rather than a third party service. |
Beta Was this translation helpful? Give feedback.
-
|
Good Morning Trevor. My nodes are pretty much kind of up. I definitely want to continue the implementation of your project. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The last CIP regarding BitBadges didn't gain much traction: #105
So, I wanted to resurrect it here in a new one. I would like to integrate BitBadges into bitclout.com's frontend and potentially into the main chain itself.
BitBadges is a solution where user's can issue NFT badges to any other users. Think of them like boy scout or military badges. You can issue badges to any other user and they will live permanently on the blockchain. So once you earn a badge, no one can take it away from you because it is linked with your public key. You then start to build a collection of badges for your BitClout profile and you can display all your best badges somewhere on your profile page. This will 1) aid people in investment decisions as it assigns a better reputation score than just creator coin price which can be manipulated and 2) offer a crypto software solution to many of BitClout's existings problems like scammers, verification, etc and 3) offer a new cool way of interaction between creator and audience.
What problems does this solve for BitClout currently?
Verification - Accounts like @VerifiedProfile can issue verification badges and then all you need to do to check if someone is verified is check if they have the badge issued from them. If in the future, you don't like @VerfiedProfile anymore, you can just choose to recognize someone else as the official verifier. Different users can even choose to recognize different official verifiers. There doesn't have to be one unique one. Much better solution than the current solutions.
Scammers - Same thing as with verification for scammers. Right now, if someone is new to BitClout there is really no way to tell if someone has a history of scams. With a scammer badge, new people can directly see who is a scammer by a scammer badge.
Along with these two main problems, there are infinitely many use cases for BitBadges because each badge is unique. So many interesting use cases will pop up.
Examples:
Implementation:
We are fully open source. We offer a public API that gives access to all badge data to whoever wishes. So if we ever act untruthfully in the future and you don't trust BitBadges anymore, you can just fork us and create a new BitBadges.
To issue a badge, all you need to provide is jwt verification with BitClout Identity. Then, you can issue a badge to anyone.
The only time we charge money is for over 25 recipients on a single badge which is just to reduce API spam limit which we don't plan to offer that feature on bitclout.com. We are already implemented on CloutFeed and we would like to do a similar integration on bitclout.com as well.
We would love to discuss if you have any ideas for more transparency.
There is nothing to lose with integrating BitBadges. It is a cool feature that solves many of BitClout's problems and there will be absolutely no creator coins/money involved.
Would love to answer any questions.
See https://www.bitbadges.github.io for more details as well.
Beta Was this translation helpful? Give feedback.
All reactions