Skip to content
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

Add open problems page #72

Merged
merged 5 commits into from
Aug 17, 2022
Merged

Add open problems page #72

merged 5 commits into from
Aug 17, 2022

Conversation

kaiserd
Copy link
Contributor

@kaiserd kaiserd commented Jul 14, 2022

Add open problems page


(Below description a bit out of date)

This PR adds a research collaboration page.

My suggestion for funded positions is to have a JD for each of them and link the JD in the respective section of this research collaboration page.

Also, I'd not put in the "Research Proposal" section because it seems not very attractive for applicants. I just mentioned it for the sake of discussion during the offsite. We could make it more attractive by offering jointly writing the proposal. Still, I'd probably not list that.
Maybe we could write:
" We also offer jointly writing research proposals to relevant funding agencies in the listed research areas."
My opinion: I'd not list this at all and keep that as an unlisted option in case we find an opportunity.

@kaiserd kaiserd force-pushed the staging branch 2 times, most recently from 73ee562 to 39f0c52 Compare July 22, 2022 15:52
@oskarth
Copy link
Contributor

oskarth commented Jul 29, 2022

I suggest we take this PR and update it a bit to be in line with #82

Probably best to merge it after #79

@kaiserd kaiserd mentioned this pull request Jul 29, 2022
2 tasks
@kaiserd kaiserd force-pushed the add/research-collaboration-page branch from fe49aae to a8b592c Compare August 2, 2022 14:55
@kaiserd
Copy link
Contributor Author

kaiserd commented Aug 2, 2022

I reworked the open research problems page. It now simply lists open research topics.

  • removed the "funded positions" as we currently do not have any
  • removed the anonymity analysis
    • Imo, only tasks we are not actively working, and that can be outsourced make sense here
    • during working on the anonymity analysis, such more contained topics might emerge and be added to the list

I'd suggest merging this soon and let other team members open their PR's to add more topics.

@kaiserd kaiserd requested a review from D4nte August 2, 2022 15:00
@kaiserd
Copy link
Contributor Author

kaiserd commented Aug 2, 2022

NAT traversal might be an interesting topic to list here, too.
It does not have a high priority, but could be easily outsourced.

@kaiserd kaiserd mentioned this pull request Aug 2, 2022
6 tasks
Copy link
Contributor

@s1fr0 s1fr0 left a comment

Choose a reason for hiding this comment

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

LGTM! Left some comments

We are seeking to collaborate with academia in the following topic areas.
Feel free to join our [Discord](https://discord.gg/DXHGzzGX) for discussion.

### DHT (distributed hash table) security / privacy / anonymity
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
### DHT (distributed hash table) security / privacy / anonymity
## Privacy/Anonymity:
### DHT (Distributed Hash Table)

I think makes sense to organize topics by tracks/research area

Copy link
Contributor Author

@kaiserd kaiserd Aug 2, 2022

Choose a reason for hiding this comment

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

I'd leave that just as a list of topics. The DHT topic, in specific, would be part of the discovery track, too.
No strong opinion here. Does anyone else have an opinion on this?

Copy link
Contributor

Choose a reason for hiding this comment

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

A list of topics makes sense to me, we can have research areas in () maybe.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ideally we then have a list of up to 10 somewhat discrete problems. Basically this should be a live and updated version of https://vac.dev/vac-overview#problems-and-rough-priorities (and more detailed probably)

open-problems.md Outdated
### DHT (distributed hash table) security / privacy / anonymity

Compared to unstructured P2P overlay networks, DHTs offer efficient and (theoretically) reliable discovery.
However, they are prone to eclipse attacks and typically offer weak privacy properties.
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe worth to point "ecplise attacks" to some reference (also on why DHTs provide weak privacy properties)

I think it is good if for each open research area, we provide 3-4 references to give better context and attract interest in the problem.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added some pointers f45405e

open-problems.md Outdated

For now, please take a look at our open issues. For example in the [vacp2p/research repo](https://github.com/vacp2p/research/issues).
We are seeking to collaborate with academia in the following topic areas.
Copy link
Contributor

Choose a reason for hiding this comment

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

Not only academia, also independent researchers - most people in the web3 space are more independent

The phrasing sounds a a bit too... dreary? Maybe say we have a lot of research areas and some specific open problems, and are excited to see contributions from people (affiliated or not)

@oskarth oskarth changed the title add: research collaboration page Add open problems page Aug 3, 2022
@oskarth
Copy link
Contributor

oskarth commented Aug 3, 2022

Can we add more problems to this page? It feels a bit lacking. Perhaps going over with Sanaz (#81 (comment) per offsite) to make sure we capture a reasonable selection of problems that we've discussed previously, both in previous write-ups as well as things that have come up as we've been working on this research (MT optimization, node reputation, etc..)

@fryorcraken fryorcraken requested review from fryorcraken and removed request for D4nte August 15, 2022 03:40
@kaiserd kaiserd force-pushed the add/research-collaboration-page branch from a8b592c to 531e81e Compare August 16, 2022 13:59
@kaiserd
Copy link
Contributor Author

kaiserd commented Aug 16, 2022

I added additional pointers to the information on the DHT topic f45405e .

Imo, it would make sense to merge this into staging now and let others open PRs adding their respective topics.
Wdyt?

@kaiserd kaiserd requested a review from oskarth August 16, 2022 14:09
Copy link
Contributor

@staheri14 staheri14 left a comment

Choose a reason for hiding this comment

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

Looks good as the start.

open-problems.md Outdated

For now, please take a look at our open issues. For example in the [vacp2p/research repo](https://github.com/vacp2p/research/issues).
We are seeking to collaborate with researchers in the following topic areas.
Feel free to join our [Discord](https://discord.gg/DXHGzzGX) for discussion.
Copy link
Contributor

Choose a reason for hiding this comment

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

The Discord link does not seem to work.

Copy link
Contributor Author

@kaiserd kaiserd Aug 17, 2022

Choose a reason for hiding this comment

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

fixed in f45405e

@staheri14
Copy link
Contributor

Can we add more problems to this page? It feels a bit lacking. Perhaps going over with Sanaz (#81 (comment) per offsite) to make sure we capture a reasonable selection of problems that we've discussed previously, both in previous write-ups as well as things that have come up as we've been working on this research (MT optimization, node reputation, etc..)

I have a couple of topics in mind, let me compile their description and add to this page (if ok in a separate PR so that this one does not get blocked)
Some topics headlines:

  • Privacy-Preserving Incentivizations of waku protocols
  • Devising applications using Waku protocol stack e.g., a p2p social network, evoting system, etc.

Copy link
Contributor

@oskarth oskarth left a comment

Choose a reason for hiding this comment

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

We can merge this as partial progress if this makes things simpler, but we need more work on this page before we can close issue (including on research front)

@oskarth
Copy link
Contributor

oskarth commented Aug 17, 2022

Can we add more problems to this page? It feels a bit lacking. Perhaps going over with Sanaz (#81 (comment) per offsite) to make sure we capture a reasonable selection of problems that we've discussed previously, both in previous write-ups as well as things that have come up as we've been working on this research (MT optimization, node reputation, etc..)

and let others open PRs adding their respective topics.

Can you @kaiserd and @staheri14 please do a sweep over e.g. previous write-ups and offsite discussion and add problems that we've already identified? Instead of it being "let others do it" :P

Doesn't have to be fancy, just that we capture various dimensions we've alluded to in various places.

@kaiserd
Copy link
Contributor Author

kaiserd commented Aug 17, 2022

Can you @kaiserd and @staheri14 please do a sweep over e.g. previous write-ups and offsite discussion and add problems that we've already identified? Instead of it being "let others do it" :P

@oskarth I added the topic list discussed during the offsite in 74aa8f1
Not trying to escape the work ;); Imo, it is more efficient if the person that came up with the topic, has more background knowledge, and is responsible for the respective track writes the respective description; they will know best what we need.

We can merge this as partial progress if this makes things simpler, but we need more work on this page before we can close issue (including on research front)

Ill add a NAT traversal topic in this PR and then close this PR

Ill add a new PR for the NAT topic as it is a new topic and somebody might have objections. This PR already got the accepted.

@kaiserd kaiserd merged commit 0de2ab0 into staging Aug 17, 2022
@kaiserd kaiserd deleted the add/research-collaboration-page branch August 17, 2022 08:59
@kaiserd kaiserd restored the add/research-collaboration-page branch August 17, 2022 10:06
@kaiserd kaiserd deleted the add/research-collaboration-page branch August 17, 2022 10:07
@oskarth
Copy link
Contributor

oskarth commented Aug 17, 2022

Not trying to escape the work ;); Imo, it is more efficient if the person that came up with the topic, has more background knowledge, and is responsible for the respective track writes the respective description; they will know best what we need.

Right, I guess part of the point is that not everything is well-formulated, and what we want to capture on open problem space are especially things that might not be well-specified enough. I believe between you and Sanaz there's enough knowledge and understand that you should be able to cover most relevant areas, obv with other people reviewing + adding thoughts.

@kaiserd
Copy link
Contributor Author

kaiserd commented Aug 17, 2022

@oskarth Maybe there is a doc that I am not aware of? I added the captions based on our offsite doc which only lists headings with no content:
(I did not find any formulation regarding these topics.)

  • DHT security
  • Incentivise relay
  • Waku simulator
  • Halo2 in a browser
  • RFPs?: Finding applications for Waku and publishing as a paper.
  • Meshnet transports and libp2p
  • Applied ZK

I added a description for the first item, and just added NAT traversal as a new topic in #86 (already merged).


edit

Clarified in Discord.
More info and continuation in: "Discussion: Should Open Problems Page Contain our Roadmaps" section in #81

(I assumed, the open problms page should only contain separate / stand-alone research problems and not our roadmaps.)


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants