This is a really thoughtful question! Privacy is one of the main concerns with on-chain data, and we’ve made sure to address that in SunID.
For the first version we’re presenting at this hackathon, we’ve implemented an option for off-chain storage using BTFS. This allows users to store their data off-chain, while maintaining full control over which credentials they share and with whom.
However, as you pointed out, BTFS data is still technically public. In future versions, we plan to introduce local storage, where the credential will be sent directly to the user after issuance and won’t be indexed or displayed on the SunID platform.
For on-chain verification of these private credentials, we’ll implement zk-proof technology, allowing users to selectively disclose only the specific data required, ensuring greater privacy while still meeting verification needs.
Thank you for explaining this to my understanding that you don’t charge fees for creating credentials, but there might be some gas fee for transaction on the blockchain. That’s okay, because it’s like paying for a safe deposit box at a bank. and also offer free off-chain storage, which is great for people who don’t want to pay extra.
Sir,my question is what if i Iose my password or access to my SunID account?
We don’t use passwords like traditional Web2 platforms. Instead, SunID is integrated with your TronLink wallet. To access your SunID account, you simply connect using your wallet.
Thanks for taking the time to not only reply but break it down in comprehensible format, and it is indeed noteworthy your commitment to privacy through the use of BTFS for off-chain storage and the planned implementation of zero-knowledge proofs (zk-proofs). Moving forward, zk-proofs are computationally intensive. Have you assessed how this might impact the user experience or the performance of the SunID platform as the number of credentials or users scales up? What strategies will you employ to optimize this?
After having several reads on your project to understand its usefulness, I am now convinced that it serves very important purpose of revolutionizing how we can authenticate and share information online thus opening more doors for transparency, trust and verification in a decentralized space. But aside the many benefits of a decentralized method of authenticating information, lies the concern on how these information/data will be verified before being added to the blockchain. How do you plan to address this, to ensure the legitimacy of the information provided by the users?
You can easily obtain SunID by visiting sunid.xyz, where you can create schemas and credentials. We’ve already provided a guide on how to use SunID on the post , and these instructions will be updated continuously to ensure a smooth experience.
We’ve already implemented a simple version of zk-proof, and based on our testing, the time to generate a proof is around 8-10 seconds. However, we believe there’s room for optimization, and we plan to dedicate more time to refining it in the future, which should help reduce this time further. It’s important to note that proof generation happens entirely on the client side (user side), so it won’t affect the scalability of the SunID platform itself.
You’re right! It’s challenging to verify data before it’s added to the blockchain. That’s why we’ve implemented the trust network concept, where you should only trust credentials issued by a verified and trusted party.
While anyone can create credentials on SunID, we plan to develop a more effective reputation mechanism in the future to further enhance trust and credibility.
It’s great to hear that you’ve already implemented a simple version of zk-proof and are working on optimizing the proof generation time.
Have you considered offering a lite mode or optimized pathway for low-end or older devices that might struggle with proof generation?
SunID is amazing connecting the real world to blockchain and also making verification easy and secure.
Great job buddy but how will it handle complex verification situations in terms of university degrees and professional accreditation.
In complex verification situations like university degrees and professional accreditations, the verifier should check who issued the credential. The verifier should only trust credentials from issuers they recognize, such as known universities or professional organizations. This is part of the trust network SunID builds, where only trusted issuers ensure credibility.
, and these instructions will be updated continuously to ensure a smooth experience.