Skip to content

Peer-Reviewed Academic Journal Article and Dissemination - Digital Inheritance in Web3: A Case Study of Soulbound Tokens and Social Recovery Pallets within the Polkadot and Kusama Ecosystems#1183

Merged
Noc2 merged 41 commits intow3f:masterfrom
jgophd:master
Oct 25, 2022

Conversation

@jgophd
Copy link
Copy Markdown
Contributor

@jgophd jgophd commented Sep 24, 2022

Project Abstract

This proposal is to create a peer-reviewed academic case study for applying soulbound tokens within the Polkadot and Kusama ecosystems by leveraging the Social Recovery pallet and soulbound token use cases developed by the Phala Network and RMRK for digital inheritance. This will be a qualitative case study where we will conduct a literature review of soulbound tokens and interview team members and developers of the Phala Network, as well as team members from RMRK. In addition to the research on soulbound tokens, we will also interview Parity Technologies members who are familiar with the development of the Social Recovery pallet to investigate how it can be applied to digital inheritance.

Grant level

  • Level 1: Up to $10,000, 2 approvals
  • Level 2: Up to $30,000, 3 approvals
  • Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

  • The application template has been copied and aptly renamed (project_name.md).
  • I have read the application guidelines.
  • A BTC, Ethereum (USDT/USDC/DAI) or Polkadot/Kusama (aUSD) address for the payment of the milestones is provided inside the application.
  • The software delivered for this grant will be released under an open-source license specified in the application.
  • The initial PR contains only one commit (squash and force-push if needed).
  • The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
  • I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

Noc2
Noc2 previously approved these changes Oct 17, 2022
Copy link
Copy Markdown
Contributor

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay here. I’m still happy to go ahead with it and will share it again with the rest of the team.

@jgophd
Copy link
Copy Markdown
Contributor Author

jgophd commented Oct 17, 2022

@semuelle, per your last message, please see the changes from 'developed materials' to 'raw data'.

@jgophd
Copy link
Copy Markdown
Contributor Author

jgophd commented Oct 17, 2022

Thanks for this application. I have renamed some of your deliverables to make them more expressive and left two questions. Other than that, I am happy to support this.

@semuelle, I have now responded to these questions. Thanks again for your review and assistance on this.

@semuelle
Copy link
Copy Markdown
Contributor

Thanks for the quick reply, @jgophd, but my questions were how you would make them accessible, and if it would be also the raw data. It would be nice if you could phrase the specification accordingly.

@jgophd
Copy link
Copy Markdown
Contributor Author

jgophd commented Oct 17, 2022

Thanks for the quick reply, @jgophd, but my questions were how you would make them accessible, and if it would be also the raw data. It would be nice if you could phrase the specification accordingly.

@semuelle Thank you for this. I updated each section with the following comment. "All developed materials and raw data will be publicly accessible and public domain via a GitHub repository."

Copy link
Copy Markdown
Contributor

@alxs alxs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jgophd thanks a lot for your application. This looks great and we're generally interested in supporting more research projects. However, please note that as a rule of thumb we only fund the development/research work itself, not any related costs such as infrastructure or, in your case, in-person presentations and travel costs. See our FAQ in this regard. The treasury is a much better-suited source of funds for such activities. I suggest you remove deliverable 1a. from milestone 3 and apply for Treasury funding to promote the article when you're ready.

Feel free to redistribute the costs among all milestones, since I think deliverable 1 currently also accounts for the actual writing of the article but only covers the submission costs.

@jgophd jgophd requested review from alxs and removed request for semuelle October 24, 2022 02:34
@jgophd
Copy link
Copy Markdown
Contributor Author

jgophd commented Oct 24, 2022

@jgophd thanks a lot for your application. This looks great and we're generally interested in supporting more research projects. However, please note that as a rule of thumb we only fund the development/research work itself, not any related costs such as infrastructure or, in your case, in-person presentations and travel costs. See our FAQ in this regard. The treasury is a much better-suited source of funds for such activities. I suggest you remove deliverable 1a. from milestone 3 and apply for Treasury funding to promote the article when you're ready.

Feel free to redistribute the costs among all milestones, since I think deliverable 1 currently also accounts for the actual writing of the article but only covers the submission costs.

@alxs Thank you for your feedback. I have redistributed the costs for more researchers, which will provide a more well-rounded study. Please let me know if this is what you are looking for.

@jgophd
Copy link
Copy Markdown
Contributor Author

jgophd commented Oct 24, 2022

Thanks for the quick reply, @jgophd, but my questions were how you would make them accessible, and if it would be also the raw data. It would be nice if you could phrase the specification accordingly.

@semuelle Thank you for this. I updated each section with the following comment. "All developed materials and raw data will be publicly accessible and public domain via a GitHub repository."

@semuelle, are the revisions what you were looking for?

Copy link
Copy Markdown
Contributor

@semuelle semuelle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update. Happy to proceed.

@alxs
Copy link
Copy Markdown
Contributor

alxs commented Oct 25, 2022

Thanks @jgophd. Could you please fill in your first comment, which I've replaced with our PR comment template?

@jgophd
Copy link
Copy Markdown
Contributor Author

jgophd commented Oct 25, 2022

Thanks @jgophd. Could you please fill in your first comment, which I've replaced with our PR comment template?

@alxs, thank you for your quick response. I have populated the first comment per your request.

@rrtti rrtti self-requested a review October 25, 2022 13:12
@Noc2 Noc2 merged commit 7dbe974 into w3f:master Oct 25, 2022
@Noc2
Copy link
Copy Markdown
Contributor

Noc2 commented Oct 25, 2022

Congratulations! Your application has been accepted, but the bot didn’t post the welcome message here, because it was merged into the wrong folder. I updated it. And here is the official text:

Congratulations and welcome to the Web3 Foundation Grants Program! Please refer to our Milestone Delivery repository for instructions on how to submit milestones and invoices, our FAQ for frequently asked questions and the support section of our README for more ways to find answers to your questions.

Before you start, take a moment to read through our announcement guidelines for all communications related to the grant or make them known to the right person in your organisation. In particular, please don't announce the grant publicly before at least the first milestone of your project has been approved. At that point or shortly before, you can get in touch with us at grantsPR@web3.foundation and we'll be happy to collaborate on an announcement about the work you’re doing.

Lastly, please remember to let us know in case you run into any delays or deviate from the deliverables in your application. You can either leave a comment here or directly request to amend your application via PR. We wish you luck with your project! 🚀

@keeganquigley
Copy link
Copy Markdown
Contributor

Hi @jgophd just checking in to see how milestone 3 is coming along?

@jgophd
Copy link
Copy Markdown
Contributor Author

jgophd commented Apr 22, 2023

Hi @jgophd just checking in to see how milestone 3 is coming along?

@keeganquigley, I hope all is well. The team is waiting to hear back from IEEE, and the submission is under manuscript ID Access-2023-06036. Per direction in Milestone 2, the pre-print of article was uploaded to arXiv - arXiv preprint arXiv:2301.11074 - and can be found at Google Scholar - https://bit.ly/3oDJLxt - and at university libraries just as Penn State University - https://bit.ly/3LofgEZ.

After discussing this research with projects from other ecosystems, the team has been working with Safe Haven in the VeChain ecosystem to integrate some of the findings from this study into their base product. The overall goal is to hopefully introduce a solution on Kusama in the future. Please see more about that collaboration here - https://bit.ly/3N53Erv.

Finally, for the dissemination of the research, I will be discussing this study at Coin Bureau Live on June 10th https://live.coinbureau.com/. The Coin Bureau has 2.25 million subscribers on YouTube - https://www.youtube.com/@CoinBureau - many of which will be reviewing the livestream of the event, as well as in-person. This is the first of many engagements where I will be discussing the research as well at academic conferences in the Fall of 2023.

I will keep you updated on IEEE as I assumed you all wanted a report once the study was published in IEEE instead of arXiv.

@keeganquigley
Copy link
Copy Markdown
Contributor

Hi @jgophd just circling back on this to see if you ever heard back from the IEEE. Also, I think I found the correct video stream of the Coin Bureau conference but it is 8 hours long. Are you able to point to where your panel/presentation was? Just curious to watch it.

Regarding milestone 3, after talking internally with the grants team, I think you can probably go ahead and submit the delivery as is, since the arXiv version is published. That way we can finish up the grant, as waiting for IEEE could still take a long time. Let me know your thoughts. Thanks!

@jgophd
Copy link
Copy Markdown
Contributor Author

jgophd commented Aug 22, 2023

Hi @jgophd just circling back on this to see if you ever heard back from the IEEE. Also, I think I found the correct video stream of the Coin Bureau conference but it is 8 hours long. Are you able to point to where your panel/presentation was? Just curious to watch it.

Regarding milestone 3, after talking internally with the grants team, I think you can probably go ahead and submit the delivery as is, since the arXiv version is published. That way we can finish up the grant, as waiting for IEEE could still take a long time. Let me know your thoughts. Thanks!

@keeganquigley, sorry for the delayed response. The Coin Bureau video above is on the main stage. I discussed the digital inheritance session in another session. Also, I make revisions to the IEEE article and am waiting to hear back after those revisions. I will submit the final milestone now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready for review The project is ready to be reviewed by the committee members.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants