Create Interstellar M1.md (1) #394
Conversation
* Create Interstellar M1.md * Update Interstellar M1.md * Update Interstellar M1.md * Update Interstellar M1.md * Update Interstellar M1.md * u * update * update * update * Delete settings.json * update * update * u * u * u * u * u * u * u * u * update Co-authored-by: Nathan Prat <nathan.prat@gmail.com>
semuelle
changed the title
|
Thank you for the delivery, @nashjl. We will look into it as soon as possible. |
|
Hi @nashjl, thank you for your milestone 1 submission! My name is Ashley and I'm working on your milestone 1 evaluation here at the W3F. I've learned a lot from reading about your project and excited to test it. I believe I've carefully installed all the prerequisites on my machine, but I keep getting this error and not able to get the ID. Any suggestions? Thanks!
|
|
Additional information: I did get the two docker images running, but unable to compile the OCW demo: Could you please see if those errors are on your end or otherwise hopefully provide me a bit of help to resolve the errors on my end? Thank you! |
|
Hi Ashley, |
|
For If yes, what kind of machine are you using? Maybe you are hitting : rust-lang/rust#95267 I am using: |
|
Hi @nathanprat. That was very helpful, thank you. I was on the wrong branch and was not using your toolchain, so that solved some errors already. But, let me go back to the prerequisites and take it step-by-step again and first test with Docker before trying to compile from source. I believe I may be stuck on this instruction in your prerequisites:
Sorry, I'm relatively new here at W3F and wondering if you could please explain a bit more. Does this mean that before I launch the IPFS daemon I need to have the docker images running already? I believe I have the docker images running: This is how my daemon looks: This is how my ports look: Does it look like I have the proper addresses/ports? Should there be these Thanks so much for your patience, quick response, & providing step-by-step instructions! |
|
You need to have the IPFS running when you end up calling the API routes. Your IPFS daemon says What you may need to change is the If you are stuck you may try to compile from source and run |
|
Hi, I just saw your new comment, and I plan to get to work with those tips!! By the way, looking ahead, so I can run your I believe we can get through this together! 😄 By the way, fyi, I also ran these commands: which yielded a That solved a bunch of errors, but I still have some errors: So I'm wondering, perhaps I have the wrong directory organization? Or perhaps this is a Thanks for your help! |
|
The last error For CMake yes it is not the cleanest; you basically need to DL the pre-compiled binaries and add them into your PATH. |
|
Thank you. Planning to fix the missing submodules next. Thanks for the dockerfile with additional cmake commands too. Btw, I checked with |
|
That is weird. |
|
I tried deleting and re-cloning to try to build from source. I am getting this error: Are you familiar with these error messages? I am so sorry for all the trouble. I believe this is because I've ssh'd into my Ubuntu VM and from there, I don't have ssh to GitHub set up and I clone repos with HTTPS. It seems this is an issue? Working through this best I can on my end. Perhaps if I can't get this working on my remote Ubuntu server, you could provide instructions so I could build from source on my MacBook Pro 2019 (Intel chip)? Again, I really appreciate your help. |
|
Ah yes, I had never checked the submodules. I guess you indeed need to have git SSH configured. All the repos are public so that should be working, assuming PS: you should avoid |
|
@nathanprat Makes sense! I'm just barely setting up my new Ubuntu server and see that I need to spend some more time configuring git. I'm wrapping up for the day, and thanks for all the great help! I plan to continue tomorrow. |
|
Hi @nathanprat, I'm planning to continue this evaluation on Monday. Hope you have a nice weekend! |
|
Good day @nathanprat! I set up ssh to github on my machine and was able to clone those repos recursively via ssh, thank you. I'm still having issues with cmake. I'm getting I've also tried many ways I could find online to update this. I feel quite blocked and might have to discuss this with my team to see how we can proceed. I am not able to In the meantime, do you happen to have testing instructions for Mac? Do you think it's possible to test with Mac? |
|
Hi,
For CMake this is probably just because you need to add /opt/cmake/bin to
your PATH.
To check: "which cmake" and if it says something like /usr/bin/cmake it
means you are using the system one.
If you are still blocked you can ignore compiling from source and just use
docker.
We can go back to compiling once you have a version running.
I honestly do not know if compiling on Mac is possible. I am curious to
know, but I can not give you instructions on how to install the system
dependencies.
For sure CMake, Ninja, boost are installable on Mac but beyond that...
Le lun. 28 mars 2022 à 23:19, ashley grevelink ***@***.***> a
écrit :
… Good day @nathanprat <https://github.com/nathanprat>!
I set up ssh to github on my machine and was able to clone those repos
recursively via ssh, thank you.
I'm still having issues with cmake. I'm getting Unpacking finished
successfully but when querying for the version, I still get 3.16.3. (see
terminal output) Very sorry about this.
***@***.***:~$ sudo ./cmake-3.22.3-linux-x86_64.sh --skip-license --prefix=/opt/cmake/
CMake Installer Version: 3.22.3, Copyright (c) Kitware
This is a self-extracting archive.
The archive will be extracted to: /opt/cmake/
Using target directory: /opt/cmake/
Extracting, please wait...
Unpacking finished successfully
***@***.***:~$ cmake -version
cmake version 3.16.3
CMake suite maintained and supported by Kitware (kitware.com/cmake).
I've also tried many ways I could find online to update this. I feel quite
blocked and might have to discuss this with my team to see how we can
proceed. I am not able to cargo build and I get cmake compilation errors.
In the meantime, do you happen to have testing instructions for Mac? Do
you think it's possible to test with Mac?
—
Reply to this email directly, view it on GitHub
<#394 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALPGR5XYDRERDDGE2SN4ATVCIO4NANCNFSM5QP6GFYA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
You're correct. I ran Sorry I'm relatively new to using Linux/GNU again. I tried the command |
|
I am able to run the ipfs daemon, your two docker nodes and then able to run your substrate chain! It's nice to see it producing blocks here locally on my ubuntu VM. I need to set up port forwarding properly via VSCode to my mac so I can run a substrate frontend at http://localhost:5001/ -- unless you know, I think I need to check with my team tomorrow. Thanks again for your help! |
|
The When you have the frontend + OCW running you should see "Nothing to do" messages in the OCW's console for both the OCW pallets. |
|
I got the ports properly forwarded and the substrate template running locally and I can interact with your
I am now stuck on step 1 of your demo. I know I'm relatively new to Linux and Polkadot ecosystem, but still I find your testing guide assumes a lot of steps and it's made it extremely time intensive to evaluate your project. What I did for step 1 was first try just creating the At this point, I've already had to ask for so many clarifications, I'm really sorry, but for both our time, I'm going to have to ask you to take some time and make your testing guide truly step-by-step per our grant requirements, perhaps with a video or screenshots or more text, whatever is easiest for you. Your testing guide is already very in-depth and very detailed, which I very much appreciate, it's just not quite enough details for me to effectively follow. I'm so sorry about this once again and really hoping you understand. I appreciate the opportunity to test your very interesting technology, and I only wish to understand how it works. Thanks for all the massive time, effort and heart you've put into this project and this ecosystem. I'm looking forward to continue testing and finish your evaluation asap! |
|
There was a little typo Beyond that https://book.interstellar.gg/M1_demo_tutorial.html#step-1-add-the-masterconfig-verilogfilev-in-ipfs should work. |
I am sorry to here that, but the docker version of the evaluation should not take much time at all. Overview of the "Docker testing"Global PrerequisitesNOTE: outside the scope of evaluating our own milestone; this is general
PrerequisitesTestingI will grant you than setting up what is needed to compile from sources is a bit of a pain, but that is not required for the Docker part |
|
@nathanprat thanks for updating the curl command! I still have remaining questions: In general, it would be helpful if you would follow the testing guide yourself to double-check for bugs beforehand, or you could perhaps give a screenshot of what the expected outcome is after each step so I could verify I did each step correctly. There are two OCW pallets, but could you show a video or screenshot of the terminal of how it's supposed to look? Looking at step 2, I wish there was a lot more explanation because I don't really know what to actually put in the terminal, which terminal window (because I have so many running), which directory I should be in, etc. It seems there are so many steps in between the steps you have in the tutorial. Maybe you could slow things down for me and take it step by step? A screencast video of you going through the tutorial would maybe be really nice! Thank you! |
We have tested only with and you have to copy-paste
There are already screenshots for the OCW steps(2,3)
I will grant you that is not necessarily obvious what is an input and what is an output in the demo guide.
It was missing a branch for |
|
Quick pass done. Launch a generic Substrate Fromt-end-> directly link to https://github.com/substrate-developer-hub/substrate-front-end-template#using-the-template instead Launch substrate demo chain with OCWMissing Step 1: add the master/config verilogfile.v in IPFSClarify: |
|
@nathanprat Thanks for reviewing! Resuming testing now. |
|
Hi @nathanprat, I was happy to successfully POST the On step 2, (specifically 2.1), you didn't include instructions on whether to submit the transaction 'signed', 'unsigned', or 'sudo', which was troubling, since we require step-by-step instructions, but I decided to try first unsigned (which failed), then sudo resulting in this:
Then you say
so I assume the I found it in my OCW log here: But this doesn't match the output of your step 2.2, and once again I'm blocked and had to spend a lot of time guessing how to set up a demo. Once again, your instructions do not seem to be accurate or thorough for my level of understanding. I'm really sorry, but I plan to work on other evaluations at this time instead. Please update your testing guide so you can teach how to use your technology, specifically how to set up a development/testing environment and go step by step instead of skipping steps/assuming prior knowledge. I find myself very lost and just trying to execute steps without understanding what the purpose of the technology is or why I'm doing what I'm doing. I'm humbly asking again, please go slowly, step by step. Please be clear and thorough. Please teach what's going on. Please make your technology accessible to people other than only experts in your specific technology. I'm really sorry I'm not an expert in your specific tech stack, I wish I was, but I really need help understanding what's going on. I really wish to understand your technology because I find it very interesting, I loved learning logic circuits in school and I am a seasoned developer, just not in your technologies specifically. I think your concepts about cryptography, TEE, OCWs and wallet are fascinating. Thank you and sorry for the trouble. |
|
Hi Asley, Sorry we did not mention explicitly in the tutorial that we need a signed extrinsic/transaction, but this information is in the API documentation https://book.interstellar.gg/GCF_API.html#flowchart-and--substrate-gcf-pallets The purpose of the demo is to show that our APIs are working properly and as expected with:
I understand that you are a bit frustrated because you are not familiar with both our technology and substrate framework. Anyway, thanks a lot for your interest and your kind words about our technology. Really appreciated. We designed it with love & passion to have an impact on both the wallet's security and ease of use (yes, not kidding 😉). |
|
@nashjl Thank you!! Big sigh of relief reading your nice comment and thanks for all the help so far 😅 Working on it ASAP. |
|
Hi Ashley (@cruikshankss) Hope you are doing well. Could you please let us know when you plan to validate M1 and if you need any help. Kind regards |
|
Hello @nashjl, Thanks for the update. I'm very happy to hear you are close to delivering M2. I plan to finish your evaluation in the next 24 hours. I will let you know if I need any help, thanks! |
|
Hi Asley, Thanks a lot for your message. Hope, you will keep in mind that M1 target audience for this demo are mostly developers familiar with VHDL, C/C++, Rust, and Substrate. Mostly people already familiar with cryptography, garbled circuits, multi-party computation that aim at adapting this low-level layer for their own purpose or potential contributors. Later. (Start with M3) we will target a larger audience of Rust/Substrate developers that aim at using our Transaction Validation Protocol. Thanks to our future friendly TVP APIs that will hidden the low-level complexity of GCF and GC production. |
|
@nashjl Still working on it this evening. Thanks for the additional info! |
|
@nashjl, I've just accepted your milestone 1 and here is my evaluation. I've forwarded your invoice to the invoices team. Thank you again! |
|
Hi Asley (@cruikshankss), Thanks a lot!!! |
|
Awesome! Thanks for your time! |
|
@nashjl, yes, I saw there were two M1 invoice submissions. I looked at them both and forwarded the most recent one with your VAT ID and made note of this to the invoices team as well. Thanks for double-checking! |
|
Congratulations on completing the first milestone of this grant! As part of the Grants Program, we want to help grant recipients acknowledge their grants publicly. To that end, we’ve created a badge for projects that successfully deliver their first milestone. Note that it must only be used within the context of the delivered work, so please do not display it on your team or project's homepage unless accompanied by a short description of the grant. |
|
Thank you very much for all Ashley ! |
|
For the record, additional invoicing discussion occurred here on the M1 evaluation conversation thread: #417 |
Milestone Delivery Checklist
Link to the application pull request: w3f/Grants-Program#734 please fill this in with the PR number of your application.