SunID by ZUNI - Bridging Real-Life Data and Blockchain on Tron 🌞

Project Name: SunID

Project Track: Web3

Team Name: ZUNI

Team Member(s): @vinhtran @david7

DevPost Project Link

:dart: Project Goal: To create a DeSo dApp that connects real-life data with blockchain on Tron. Think of it as a one-stop-shop where anyone can issue or receive claims about pretty much anything in life.

:gem: Project Value: SunID addresses the lack of a DeSo application in the Tron ecosystem that connects real-world data with on-chain information. It unifies and authenticates fragmented data points, ensuring trust and accessibility. By leveraging blockchain technology, SunID provides a secure, transparent, and decentralized platform for managing and verifying various claims, from credentials to financial statuses.

:information_source: Project Info

sunid_project.pdf (1.4 MB)

Project Details: SunID is your bridge between the real world and the blockchain universe! :bridge_at_night: It works with two main players: issuers and holders. Issuers dish out credentials, and holders receive them. These credentials can be stored on-chain (Tron blockchain) or off-chain (BTFS), depending on your needs.

System Design

Key Features:

  1. Flexible Storage: Credentials can be stored either on-chain (using the TRON network) or off-chain (via BTFS), giving users control over their storage preferences.:innocent:
  2. Issue and Revoke: Simple, user-friendly system for issuing and revoking credentials. Easy peasy. :v:
  3. Unique Credential ID: Each credential has a unique ID for easy revocation and verification.

The platform is open-source, so feel free to jump in with ideas and improvements! :tada:

Project Website: sunid.xyz

Project Test Instructions

Heads up! We’re working on the Shasta network. To grab some test tokens, hop over to Shasta Tron Faucet.

Main Workflows in SunID

1. Create Schema:

Schemas define the data fields and types used in credentials. Each schema gets a unique ID on-chain.

  • Step 1: Go to Schema Page and connect your wallet.
  • Step 2: Click the Create Schema button.
  • Step 3: Complete the form:
    • Name: The schema’s name.
    • Schema Definition: * Define your schema’s template to specify data types for credentials.
    • Resolver Address (Optional): The TRON address of the entity responsible for managing the schema (e.g., a contract that authorizes certain schemas).
    • Revocable: Specify whether credentials issued under this schema can be revoked.

2. Issue a Credential:

Prerequisite: You must have an existing schema to issue credentials.

  • Step 1: Select the schema you want to use.
  • Step 2: In the Schema Detail page, click the Issue Credential With This Schema button.
  • Step 3: Fill out the form:
    • Recipient: TRON address of credential recipeint.
    • Credential Data: Provide data according to the schema template.
    • Advanced options:
      • Expiration: Set an expiration date for the credential; if not set, the credential will not expire.
      • RefUID: Reference a Credential UID.
      • Revocable: Select if the schema allows revocable credentials. If set to “Yes” the issuer can later revoke the credential.
  • Step 4: Choose whether to issue the credential on-chain or off-chain:
    • On-chain credentials will be stored on Tron.
    • Off-chain credentials will be stored on BTFS.

3. Revoke a Credential:

Prerequisite: You must be a credential issuer.

  • Step 1: Select the schema you used to issue the credential you want to revoke. You can find the credential in two ways:
    • If you have the credential UID, use the search bar at the top of the page.
    • Click on the My Credentials tab to see all issued credentials.
  • Step 2: Click on Revoke button on the top right corner.
    • For offchain credentials, this submits the credential UID to chain. Verifiers can check if this Credential UID is revoked by querying the chain.

Smart Contract Deployment:

TRON Shasta Testnet

Project Milestones:

SunID is continuously evolving to provide better services and enhanced functionality. Here are the upcoming project milestones:

  1. Onchain/Offchain Storage: Support issuing credentials on Tron and BTFS :white_check_mark:
  2. Enhanced Data Indexing: Improve on-chain data indexers for more efficient and seamless data access. :soon:
  3. Service Dockerization: Dockerize APIs and Explorer services, enabling users to easily deploy personalized, custom services.
  4. Wallet Integration: Develop a plugin to add SunID credentials as assets in TronLink or a custom version of TronLink.
  5. Privacy Enhancement: Implement zero-knowledge proof technology to verify on-chain credentials, significantly improving privacy and security.

(Note: Milestones will be updated as we go, just keeping it flexible!)


Community Love:
We’re always open to contributions, feedback, or even just a chat! Feel free to reach out if you’ve got questions or ideas. Let’s build something amazing together! :bulb::tada:

6 Likes

welcome team, I am now researching about DeSo but can you tell us more? For those who will come later to know what DeSo is all about. Thank you

3 Likes

Welcome! DeSo, or Decentralized Social, is a new concept where social networks are built on blockchain, giving users control over their data and content. It removes centralized control, ensuring more transparency and freedom. It’s great for those interested in privacy, ownership, and earning from their content. Feel free to ask if you’d like to learn more!

2 Likes

I want to learn more about this please

1 Like

Welcome to S7 hackathon team SunID.
I must say your pdf is nice and looking good. I read through and it bigger for me to understand now. Your project is working on creating a platform that makes it easy for users to manage and share their credentials and documents in a secure and decentralized way?

My question is how will you accomplish this,will they be any fee or charge?


Sir one of your usecase is kyc compliance with defi? Please I don’t understand. How do you mean. Thank you

2 Likes

Welcome to Tron hackathon season 7. I just read through your project pdf and it’s quite simple and straightforward

SunID claims to bridge real-life data and blockchain. What types of credentials and licenses are you envisioning for this platform? How will it ensure security and authenticity?

3 Likes

Absolutely! When we say DeSo gives users control, it means your data is stored on the blockchain, so you get to own and manage your content. You decide how it’s shared, and you can even earn directly from it! No more relying on a platform to access your info.

2 Likes

Thank you for taking the time to go through our proposal! You’re absolutely right - SunID is focused on creating a platform where users can securely manage and share their credentials and documents in a decentralized way.

We achieve this by using the Tron blockchain and BTFS. Issuers can create credentials for holders, which can be stored either on-chain (for immutability) or off-chain (for scalability). Each credential is assigned a unique claim ID, making it easy to manage, verify, or even revoke if necessary.

Regarding fees, at this time, we don’t charge any fee for creating a credential. However, users will need to pay a gas fee for transactions involving on-chain storage. Alternatively, they can store credentials off-chain at no cost.

Great question! SunID is designed to support a wide range of credentials, including KYC, academic credentials, ID documents, financial records, and more. The platform is flexible enough to accommodate various types of credentials and licenses as needed.

To ensure authenticity, SunID introduces a trust network concept. This means you should only trust credentials issued by your trusted issuers. It’s similar to real life—when you submit your degree to a company, the company trusts your qualifications because they trust the school that issued the degree.

For sensitive data, we offer the option to store credentials off-chain using BTFS, while keeping a reference on-chain. This ensures both scalability and security, with users retaining full control over their data.

1 Like

When we talk about KYC compliance in DeFi with SunID, it means that if you have a KYC credential issued through SunID on the Tron blockchain, you can use this credential across various dApps and even directly within smart contracts.

Here’s how it works: Once you receive a KYC credential from a trusted issuer (e.g., Tron Foundation) via SunID, it’s stored on-chain. You can then present this KYC credential when interacting with our dApp or other DeFi platforms. Smart contracts on these platforms can verify the validity of your KYC credential, allowing them to accept or reject entities based on the verified KYC status.

This system enhances both security and compliance within the DeFi ecosystem, while ensuring that users retain control over their personal information.

1 Like

thank you for your time, I will come again

1 Like

Welcome to Grand hackathon S7
First and foremost I want to ask what is DeSo but after reading through I see it has been answered but it still got me confused how it works, so I want to know if it’s specifically for saving social files and data or anything else, please I would like you to elaborate in simple terms how it really works and how can a user have an advantage of it

2 Likes

Welcome to the Hackathon of season 7, I have take my time to read your project, are you doing any staking mechanism type of thing, thank you

Let me give you a simple example to explain how KYC works in a decentralized way using SunID. Imagine a trading exchange that requires KYC before you can trade to ensure you’re not located in the U.S. Now, let’s say you have a KYC credential issued by the Tron Foundation. If the exchange trusts the Tron Foundation, they will accept the KYC credential you’ve received. The exchange’s smart contract might have a requirement that only users with verified KYC can deposit funds.

Here’s how it works with SunID:

  1. The Tron Foundation uses SunID to create a KYC schema, which defines the fields and data types required for KYC, such as name, age, and country.
  2. Once the Tron Foundation verifies your identity, they issue a KYC credential confirming you’ve successfully completed the process.
  3. You now hold your KYC credential on the Tron blockchain and can present it to the exchange’s smart contract. The contract will automatically verify the KYC and grant you permission to deposit and start trading.

The key advantage here is that you don’t need to repeat the KYC process with other dapps that trust the Tron Foundation’s KYC. You KYC once and use it multiple times across different dapps.

Here are some key benefits:

  • Ownership: You control your own data, not a company.
  • Security: Your data is secure, transparent, and tamper-proof since it’s stored on the blockchain.
  • Interoperability: You can use the same KYC credential across various dapps without needing to repeat the KYC process or create separate accounts.
1 Like

We haven’t had staking mechanism yet.

Welcome buddy
SunID is a new concept on Tron that helps connect real-life data with blockchain technology. It makes it easier to verify credentials and claims in a secure and transparent way.
In general my question is

In what manner will SunID get people to use the platform, and how will it make sure the credentials are accurate and trustworthy, especially when they need to be revoked.
Thank you

Which means while verifying the kYC that gas fees would be attached right?

It depends on the type of verifier. If the verifiers are web2/offchain apps, they can simply read the data stored on the blockchain, in which case no one pays a gas fee. However, if the verifier is a smart contract and requires you to submit your KYC, you would need to pay a gas fee for that transaction.

1 Like

SunID will attract users by offering a secure, decentralized platform that allows them to manage and share their credentials across multiple dApps without needing to repeat processes like KYC.

To ensure the accuracy and trustworthiness of credentials, SunID employs a trust network. This means you should only trust credentials issued by trusted issuers, such as universities or financial institutions, similar to how you trust credentials from reputable sources in the real world.

When it comes to revoking credentials, SunID assigns a unique claim ID to each credential. If a credential needs to be revoked, the issuer can do so by revoking this specific claim ID.

Welcome to Hackathon Season 7.
Quite frankly, I see this as a promising initiative aimed at bridging real-life data with the blockchain on Tron.
Reading through your offering, I’ve concerns bordering around privacy, so how would you handle the privacy of users who don’t want their real-world credentials linked to the blockchain? Is there a consent mechanism that users can control?