-
Notifications
You must be signed in to change notification settings - Fork 5
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
Client Allocation Request for: John McLaughlin #162
Comments
Thanks for your request!
|
Hey @georgemac510 - thanks for your request. Can you kindly add more information / context here on:
Thanks |
Hi @philippbanhardt, Please see my responses to your inquiries below:
Thank you for your attention to this request. Please let me know, if I can offer any additional information. Best, John McLaughlin |
Hi Philipp,
I know that you are super busy, but I wanted to check on the status of my
verified deals application. I had updated my application to include the
suggested info that was needed. My username is @georgemac510.
Thanks very much.
Best,
John McLaughlin
…On Wed, Dec 30, 2020 at 12:21 PM Philipp Banhardt ***@***.***> wrote:
Hey @georgemac510 <https://github.com/georgemac510> - thanks for your
request. Can you kindly add more information / context here on:
- yourself , e.g. include links to social media / news mentions etc
- your history working on IPFS / Filecoin, e.g. notable contributions
to the community, type of engagement shown over time etc
- type, size, source and your relationship with the data you (and by
extension other Discover participants) are looking to store on Filecoin,
e.g. public data vs private data, who owns the data / license, etc
- how you intend to store the data on Filecoin, e.g. redundancy,
location / miner preferences, etc
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#162 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH32A2CVKPDFX43PXAQEXRLSXNORTANCNFSM4VMF5LPA>
.
|
Client Allocation Questions
Core Information
The text was updated successfully, but these errors were encountered: