-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Alma.md #2432
Create Alma.md #2432
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
20a8660
to
550677d
Compare
I have read and hereby sign the Contributor License Agreement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MizukiSonoko thanks for applying to our grants program.
I've studied your proposal and got a couple of questions.
- The proposal is rather abstract, and I didn't fully understand which business problem ALMA is solving. Is this mainly a protocol that aims to enable projects to use DIDs in some way, or is there a deeper or more nieche problem being addressed by ALMA?
- Staying at the topic of DIDs, how does the value proposition of your project differ from Kilt? They are a parachain on Polkadot and provide DIDs, so while I understand that the architecture is completely different (you mention your project is not a blockchain), I'm still curious to see what difference your solution makes to potential customers.
- I was curious to learn more about the project Taisei won the JP Hacks at University of Tokyo with.
- By "Solamitsu" I assume you mean "Soramitsu", the Polkadot parachain, is that correct?
- Regarding the deliverables, we usually don't support deployment activities through this program. Hence, I recommend to merge M2 with M1 or M3.
- Please note that the DOT % should be at least 50%, as per our guidelines.
- Could you elaborate on the relevance for the Polkadot ecosystem (if any), and also add more details to the deliverables, incl. the technologies you're planning to use (e.g. Polkadot SDK)?
@takahser
Regards. |
550677d
to
a4c183b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@takahser Thanks for replying! I will answer for your questions.
The proposal is rather abstract, and I didn't fully understand which business problem ALMA is solving. Is this mainly a protocol that aims to enable projects to use DIDs in some way, or is there a deeper or more nieche problem being addressed by ALMA?
- This time, Alma seeks to provide a solution to an essential identity challenge rather than a business challenge. there are various problems with the systems surrounding IDs:
- There is a cost of guaranteeing compatibility between services due to the proliferation of proprietary ID standards.
- There is a risk that the data associated with IDs may be subject to changes inevitable for users. For example, an ID can be suspended by compulsion due to the circumstances of the ID providers or global conditions.
- Web services including blockchain solve the above issues to some extent, but they are not user-friendly because it is difficult for many users to manage their information, passwords, and private keys.
I have some follow-up questions:
- When you talk about "compatibility between services due to the proliferation of proprietary ID standards", are you referring to web2 or web3 standards?
- I'm not sure what is meant by "suspended by compulsion due to the circumstances of the ID providers or global conditions"; would you mind making an example?
Staying at the topic of DIDs, how does the value proposition of your project differ from Kilt? They are a parachain on Polkadot and provide DIDs, so while I understand that the architecture is completely different (you mention your project is not a blockchain), I'm still curious to see what difference your solution makes to potential customers.
- We believe that DID/VC is just one of the easy-to-understand UseCases of Alma, and that the essential value lies in distributed storage.
We believe that only “Alma”, which stores property related to IDs in a decentralized, has the significance (speed, dispersion) that only a transaction-specific architecture such as “blockchain” can provide. We believe that there are significant advantages (e.g., speed, decentralized )
We will also make the architecture more people-friendly with regard to private key management using MPC and ZK.
I'm not knowledgable about VC (verifiable credentials) - would you mind explaining the difference to VC and Kilt's Verification feature? In general, it would be good to understand the difference between your solution and Kilt, and what the ramifications of that design choice are (advantages and disadvantages).
I was curious to learn more about the project Taisei won the JP Hacks at University of Tokyo with.
By "Solamitsu" I assume you mean "Soramitsu", the Polkadot parachain, is that correct?
- At the time, I created a gadget that allowed business cards to be exchanged with a handshake.
( Sorry for the Japanese article.
https://japan.zdnet.com/article/35058222/ )
Interesting idea. 👍
Yes, that Soramitsu. I was making Hyperledger/Iroha architecture with Takemiya-san.
Ah, yes Soramitsu is correct, https://soramitsu.co.jp
👍
Regarding the deliverables, we usually don't support deployment activities through this program. Hence, I recommend to merge M2 with M1 or M3.
- Understood. How do I update my PR?
Please note that the DOT % should be at least 50%, as per our guidelines.
- Ok
This has still not been updated.
Could you elaborate on the relevance for the Polkadot ecosystem (if any), and also add more details to the deliverables, incl. the technologies you're planning to use (e.g. Polkadot SDK)?
- By utilizing Polkadot's smart contract capabilities (such as Ink!), you can build a system that ties data generated through secret sharing to a token economy. For instance, fragments of a secret can be managed in a decentralized manner and only assembled under certain conditions, such as completing a specific action or achievement. This enables the setup of conditional incentives, where tokens are awarded as a reward when those criteria are met.
Regards.
Likewise, this is still not specified in the deliverables. Could you update them accordingly?
pinging @MizukiSonoko |
@MizukiSonoko, there are still some unanswered questions in the comment above. Please note that if we don't hear from you within the next week, we will close this application. |
Sorry for I'm late reply. I will answer in this weekend. |
- **Total Estimated Duration:** 10 month | ||
- **Full-Time Equivalent (FTE):** 8 | ||
- **Total Costs:** 8,000USD | ||
- **DOT %:** None |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MizukiSonoko to answer your question, you would basically just update this section to say 50% instead of "none". Total costs can remain the same. Also be sure to include both your USDC Asset Hub address (currently it is an ETH address) and DOT address if it is different than the USDC one. Let us know if you have questions about this.
Closing due to inactivity. Please reach out if you would like to continue the conversation, @MizukiSonoko. |
Project Abstract
ALMA is a software and also a protocol for managements parameters like DID/VC.
ALMA has two goals to realize:
Grant level
Application Checklist
project_name.md
).@_______:matrix.org
(change the homeserver if you use a different one)