N-Hub
{"title": "N-Hub", "logoImg": "bafkreihe6fpj7n32iapoyb2ddzefillkd4i5vjqfqe6rnivzt7ksdxhfyi", "website": "https://nhub.vercel.app/", "bannerImg": "bafkreiagj5awv7d5j3dnha3xwc677nbvjq5ywaodo7g5qvdwbrbxmfatq4", "createdAt": 1713215360145, "userGithub": "", "credentials": {"twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..m2r2svaS-JUA7le2FUcAJU_aWs2feEYUMY4CtlshiXKanK8SUZqm5H-7c75gbdL8ZdcL8a-yZMy06BOFEvINAg", "type": "Ed25519Signature2018", "created": "2024-04-15T21:23:08.722Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-04-15T21:23:08.722Z", "expirationDate": "2024-07-14T21:23:08.722Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xf66c00759467c6524B0C86af132bb52786b37382", "hash": "v0.0.0:FoBTlCQw8j627x4MCuzbzOGpre7QiYbGWf3p7qRkmfs=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#nhubweb3"}}}, "description": "EAS has established itself as one of the reference standards for creating on-chain attestations. Its simple, efficient, and flexible structure has allowed it to surpass the most widely adopted solution in the recent past, NFTs. Whether the standard used was ERC721 or ERC1155, there were mainly two issues with the use of NFTs:\n  - the need to create a new smart contract to use a new attestation\n  - the impossibility to create a true on-chain schema for attestations to ensure homogeneity and standardisation\n\nEAS manages to solve these two problems thanks to its infrastructure composed of a smart contract dedicated to attestations and another dedicated to schemas.\n\nRegarding the minting/redeeming logic of a particular attestation, in NFTs, they could be written anywhere within the smart contract, while EAS involves the use of Resolver (a smart contract containing two callbacks) to implement such logic.\n\nTo date, many real world scenarios involve the use of Resolver, but this affects the simplicity of using EAS as previously described. In practice, this process necessitates the involvement of a developer, just like in the creation of an NFT.\n\nN-HUB aims to address this shortcoming by proposing a marketplace of ready-to-use Resolvers to be implemented in one's attestations with JUST one click. It will no longer be necessary to be a developer to have elaborate logic in one's attestations.", "logoImgData": {}, "bannerImgData": {}, "projectGithub": "NHUB-web3", "projectTwitter": "nhubweb3"}