-
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
Submit DigiTrust proposal #2219
Conversation
CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. Please submit the following text as a separate comment: I have read and hereby sign the Contributor License Agreement. phamdat seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. |
I have read and hereby sign the Contributor License Agreement.
Phạm Quốc Đạt
Mobile phone: 0977705810
Vào Th 5, 15 thg 2, 2024 vào lúc 09:19 github-actions[bot] <
***@***.***> đã viết:
… *CLA Assistant Lite bot:* Thank you for your submission, we really
appreciate it. Like many open source projects, we ask that you sign our Contributor
License Agreement
<https://github.com/w3f/Grants-Program/blob/master/docs/Support%20Docs/T%26Cs.md>
before we can accept your contribution. Please submit the following text as
a separate comment:
------------------------------
I have read and hereby sign the Contributor License Agreement.
------------------------------
*phamdat* seems not to be a GitHub user. You need a GitHub account to be
able to sign the CLA. If you have already a GitHub account, please add
the email address used for this commit to your account
<https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/#commits-are-not-linked-to-any-user>
.
You can retrigger this bot by commenting *recheck* in this Pull Request
—
Reply to this email directly, view it on GitHub
<#2219 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH37MBJSDPDL5V7UMHEGJE3YTVWDJAVCNFSM6AAAAABDJOTRZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBVGI3DCMRVGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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.
Hi @phamdat721101 thanks for the application. I have the following initial comments:
- Milestone 2 is missing delivery tables. Could you add these in?
- We typically only focus on the PoC and therefore aren't able to fund gathering feedback or beta testing. Could you remove deliverable 5?
- We don't support Solidity development, would you be willing to write them in ink! instead?
Hi Keegan,
Thanks for your comments
I already updated my proposal, and opened a pull request. Please help me to
check it again
Thank you so much.
Phạm Quốc Đạt
Mobile phone: 0977705810
Vào Th 7, 17 thg 2, 2024 vào lúc 00:32 Keegan | W3F <
***@***.***> đã viết:
… ***@***.**** requested changes on this pull request.
Hi @phamdat721101 <https://github.com/phamdat721101> thanks for the
application. I have the following initial comments:
- Milestone 2 is missing delivery tables. Could you add these in?
- We typically only focus on the PoC and therefore aren't able to fund
gathering feedback or beta testing. Could you remove deliverable 5?
- We don't support Solidity development, would you be willing to write
them in ink! instead?
—
Reply to this email directly, view it on GitHub
<#2219 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH37MBK5LPHWZ722EYABXXLYT6J4RAVCNFSM6AAAAABDJOTRZ6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQOBVGY3DAMJRGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks @phamdat721101 we usually require mandatory deliverables for all milestones, could you also add those in for M2 as well? |
Sure I did it
Phạm Quốc Đạt
Mobile phone: 0977705810
Vào Th 7, 17 thg 2, 2024 vào lúc 09:09 Keegan | W3F <
***@***.***> đã viết:
… Thanks @phamdat721101 <https://github.com/phamdat721101> we usually
require mandatory deliverables for all milestones, could you also add those
in for M2 as well?
—
Reply to this email directly, view it on GitHub
<#2219 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH37MBIPQDV46T2H4AGWP73YUAGOVAVCNFSM6AAAAABDJOTRZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBZGYYDEOJQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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.
Thanks @phamdat721101 however I'm still not seeing deliverables 0a. - 0e. present in M2.
-
Can you add these in? You can skip the Docker deliverable if it doesn't apply; also just one article for M2 is fine.
-
We usually ask for mockups to be provided upfront for UI focused milestones, even if they are rough.
-
For M2, its not clear to me how the notifications are being built.
-
Curious why you want to use traditional email/password login? Seems like a wallet login would be sufficient seeing as its dealing with assets.
Hi @keeganquigley,
I already updated the proposal:
1 - I updated the Docker deliverable in M1 and M2
2 - I already attached link to our mockups website, and you can check our
figma design (wireframe link) in project details
3 - I updated more detail about how to build automatic funding
allocation and notification in milestone 2
4 - In the first-version, we target to convert web2 users to web3
industry, so we want to use traditional login firstly, then we will update
to zk-login after having good traffic.
Please help me to check it.
Thank you.
Phạm Quốc Đạt
Mobile phone: 0977705810
Vào Th 2, 19 thg 2, 2024 vào lúc 23:38 Keegan | W3F <
***@***.***> đã viết:
… ***@***.**** requested changes on this pull request.
Thanks @phamdat721101 <https://github.com/phamdat721101> however I'm
still not seeing deliverables 0a. - 0e. present in M2.
1.
Can you add these in? You can skip the Docker deliverable if it
doesn't apply; also just one article for M2 is fine.
2.
We usually ask for mockups to be provided upfront for UI focused
milestones, even if they are rough.
3.
For M2, its not clear to me how the notifications are being built.
4.
Curious why you want to use traditional email/password login? Seems
like a wallet login would be sufficient seeing as its dealing with assets.
—
Reply to this email directly, view it on GitHub
<#2219 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH37MBPTDIYAONYWHPPVLYDYUN5W7AVCNFSM6AAAAABDJOTRZ6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQOBYHA2DQMBXGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for the changes @phamdat721101 I'm still not seeing that the M2 Market News section has been elaborated upon. That being said, I will go ahead and mark your application as ready for review. But I'm personally not convinced about it seeing as you list only EVM DeFi protocols in the tech stack and your team doesn't have much Rust/ink! expertise. Also this is a DeFi focused app that could be more appropriately funded via a VC or one of the DeFi parachain grant programs or even a community treasury, given the social aspect of it. Therefore I won't personally approve it but I will open it up for other committee members to comment. |
Thank you so much @keegan
Phạm Quốc Đạt
Mobile phone: 0977705810
Vào Th 5, 22 thg 2, 2024 vào lúc 03:55 Keegan | W3F <
***@***.***> đã viết:
… Thanks for the changes @phamdat721101 <https://github.com/phamdat721101>
I'm still not seeing that the M2 Market News section has been elaborated
upon. That being said, I will go ahead and mark your application as ready
for review.
But I'm personally not convinced about it seeing as you list only EVM DeFi
protocols in the tech stack and your team doesn't have much Rust/ink!
expertise. Also this is a DeFi focused app that could be more appropriately
funded via a VC or one of the DeFi parachain grant programs
<https://github.com/w3f/Grants-Program?tab=readme-ov-file#other-grant-or-bounty-programs>
or even a community treasury, given the social aspect of it.
Therefore I won't personally approve it but I will open it up for other
committee members to comment.
—
Reply to this email directly, view it on GitHub
<#2219 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH37MBMOWLBG35YWPOSO5R3YUZNLZAVCNFSM6AAAAABDJOTRZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJXHEYDAMJVG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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.
Thank you for your application, @phamdat721101. I agree with @keeganquigley that it's missing some technical details. See the questions below. That being said, it might make more sense to focus on a few of these deliverables, as this is a technical grants program and many of the deliverables you list are not reusable or useful to the ecosystem by themselves.
- What parachains are you planning to deploy this on?
- Do you have experience with ink! and Substrate?
- "Connect with relevant APIs", "Notifications can be sent to users", "Implement real-time communication" - these are too vague to be useful or properly evaluated.
|
||
Key Achievements: | ||
|
||
**Blockchain Integration:** Smart contracts have been deployed to testnet, providing users with transparent and tamper-resistant asset management. |
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.
Which testnet is this? Can you share the addresses?
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.
1 - DigiTrust targets to deploy on Statemint parachain
2 - We are starting to work with Ink! and Substrate now, and we will migrate system from solidity base
3 - These are extra features in the second milestone, and we will explain more detail after having traffic from first-version for building portfolio management
4 - DigiTrust is deployed in Klaytn-testnet : 0xa39c2b7957496d28cd6b3fd005b4a1584abe0c30
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.
Thanks for the application. But why do you need to "Integrate blockchain technology" to track portfolio data? For this kind of solution no smart contract or anything similar should be needed, at least if the portfolio is based on digital assets. What kind of smart contracts have you deployed as part of your MVP?
pinging @phamdat721101 |
|
Hi, DigiTrust target to track portfolio data as the post content for decentralized social network feature, which can support investors or managers to share their performance, |
Hi @phamdat721101 thank you for all the time and effort you put into the application and for your communication during the process. Unfortunately, the committee unanimously decided today not to move forward with the application. This is mainly due to the concerns listed above. Since you already have all the smart contracts built and it is meant to integrate with popular EVM DeFi apps, it might make more sense to migrate the contracts to an EVM-compatible chain like Moonbeam or Astar instead of re-writing them all. Either way, I appreciate your interest in the W3F grants program and wish you the best of luck in finding funding. |
No worries, thanks for the update!
Phạm Quốc Đạt
Mobile phone: 0977705810
Vào Th 5, 7 thg 3, 2024 vào lúc 07:22 Keegan | W3F <
***@***.***> đã viết:
… Hi @phamdat721101 <https://github.com/phamdat721101> thank you for all
the time and effort you put into the application and for your communication
during the process.
Unfortunately, the committee unanimously decided today not to move forward
with the application. This is mainly due to the concerns listed above.
Since you already have all the smart contracts built and it is meant to
integrate with popular EVM DeFi apps, it might make more sense to migrate
the contracts to an EVM-compatible chain like Moonbeam or Astar instead of
re-writing them all.
Either way, I appreciate your interest in the W3F grants program and wish
you the best of luck in finding funding.
—
Reply to this email directly, view it on GitHub
<#2219 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH37MBJACAWRHQD54WA7Q4LYW6XMTAVCNFSM6AAAAABDJOTRZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBSGA4TSNJRGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Project Abstract
Grant level
Application Checklist
project_name.md
).@_______:matrix.org
(change the homeserver if you use a different one)