Non-transferable tokens used to mark a user's reputation and trust level.
Facebook, Twitter, LinkedIn and the rest are closed gardens; gardens where all the plants you sow are hidden behind a gate, and all the crops you harvest are owned by a publicly traded Corporation. It’s time we throw open the gates and declare rightful ownership to our identities on the internet. The Ether XP is the first step in a long process of giving user's ownership of their digital identity. The Ether is a social platform that allows users to debate about Ethereum and answer questions related to our ecosystem. Whenever users writing compelling arguments or insightful answers, they are rewarded with The Ether's native reputation, XP. Our XP system is a representation of a user's Ethereum ecosystem insights. For our hackathon project, we turned The Ether's XP into a non-transferrable NFT. In this way, user's can not only own their reputation that stems from their The Ether XP, but they can also take it with them to any Web 3.0 application. Just like reputation in real life, this tokenized reputation can not be transferred and will always be associated with the user through the NFT that lives in their wallet. Want to have a conference that is only for insightful Ethereans? Require entrants to that party to prove their insightfulness by displaying their eXP (The Ether XP for short) badge. Eventually, we will have eXP for each community on The Ether (i.e. Core Dev, DeFi, Research, etc.), and then move beyond Ethereum based reputation. We are calling the larger reputation project TREP (tokenized reputation). But what if a user loses their private keys to a nefarious actor? Or what if that user does something terrible on The Ether that causes them to lose reputation? In these scenarios, a user will be sent an untrusted miscreant badge. This "bad" badge will show other users and Web 3.0 apps that this user's XP NFT has lost its integrity.
How it's made
The token is built on ERC721 standards modified to prevent transfer of tokens. Tokens are initially minted from the smart-contract address and are inextricably bound to the address called in the initial mint function. We prevented calls to transfer and safetransfer functions. However lowlevel calldata functions may still be susceptbile to token transfers. We welcome bug and QA testers. We are continuing to add additional restrictions and security into our smart-contract to ensure the token is permanent and "npn-transferable"." The contract used for compilation is theetherxp_flattened.sol, this contract contains all solidity imports and flattened using solidity flattener, the contract was compiled with solidity 0.6.2 and deployed using remix.ethereum.org IDE Git Tree ├── metadata │ ├── images │ │ ├── 01.png │ │ ├── ...truncated-list... │ │ └── bbt.png │ └── json │ ├── 01.json │ ├── ...truncated-list... │ └── 11.json ├── README.md └── solidity ├── build │ └── contracts │ ├── Address.json │ ├── Context.json │ ├── Counters.json │ ├── EnumerableMap.json │ ├── EnumerableSet.json │ ├── ERC165.json │ ├── ERC721.json │ ├── ethxp.json │ ├── IERC165.json │ ├── IERC721Enumerable.json │ ├── IERC721.json │ ├── IERC721Metadata.json │ ├── IERC721Receiver.json │ ├── Migrations.json │ ├── SafeMath.json │ └── Strings.json ├── contracts │ └── ethxp.sol ├── theetherxp_flattened.sol └── truffle-config.js We are using the following technologies/ protocols: NFT standards IPFS Web3Technologies used