Closed serhanwbahar closed 3 years ago
oskarth
commented
3 years ago Thanks for the thorough issue! The spec links should be updated to rfc.vac.dev/ links. Going forward this should be less of an issue, because the spec URL is more consistent and future-proof.
oskarth
commented
3 years ago I think I got them all, plus a few other ones. Please take a look here: https://github.com/vacp2p/vacp2p.github.io/pull/37
@D4nte can you please address 10 above in a separate PR in a similar fashion? You know better what to do with those links.
Going forward, this should hopefully be less of an issue as we have a more consistent/immutable spec/RFC format with unique numbers that don't change.
serhanwbahar
commented
3 years ago @oskarth thanks for the quick fix! Just checked it against for double-check and just waiting @D4nte for 10th. Excellent!
D4nte
commented
3 years ago serhanwbahar
commented
3 years ago Thanks!
I was looking at the articles about Vac to understand more clearly and be ready for my specification task. However, I've realized some of the links are not available anymore in the articles.
I created a list for that and talked with @oskarth about what we should do about it. Also, I'm not sure the correct links (for most of them) to fix broken links; that's why I'm not sending a PR for the issue.
You may see the all broken links below:
In the section of "MVDS - a minimium viable version":
The first minimum viable version is in an alpha stage, and it has a specification...
In the section of "Protocol Stack":
What does this stack look like? We take inspiration from core internet architecture, existing survey work...
On the other hand, we've mentioned using "whisper" in this article. I've talked with @staheri14 about the replacing Waku v2 instead of whisper. Does this need to be updated?
In the section of "Progress so far":
In short, we have a Waku version 0 spec up as well as a PoC for backwards compatibility. In the coming weeks, we are going to solidify the specs, get a more fully featured PoC for Waku mode. See rough roadmap, project board...
In the section of "Current State":
We released Waku spec v0.3 this week! You can see the full changelog here...
Also,
There are currently two clients that implement Waku v0.3, these are Nimbus...
We have a simulation...
In the section of "Next steps and future plans":
For the third bottleneck, a likely candidate for fixing this is Kademlia routing. This is similar to what is done in Swarm's...
On the other hand, there is a Trello board here in the article: https://trello.com/b/DkxQd1ww/status-app-roadmap That board is outdated.
In the last sentence of the second paragraph:
In most applications, including Status right now, this is done with a static list of nodes...
In the section of "Simplify the protocol":
Due to Waku's origins in Whisper, devp2p and as a standalone protocol, there are a lot of stuff that has accumulated (https://specs.vac.dev/specs/waku/waku.html)...
In the section of "Specs":
In the section of “Things that are missing”:
Core integration was mentioned in scope for track 1 initially. This work has stalled a bit, largely due to organizational bandwidth and priorities. While there is a Nim Node API that in theory is ready to be used, having it be used in e.g. Status desktop or mobile app is a different matter. The team responsible for this at Status (status-nim)...
In the section of “4. Waku v2 - Breakdown”:
You can read more about the breakdown in this update though some progress has been made since then, as well was in the main Waku v2 spec...
In the section of "References":
1 RLN-Relay specifications: https://github.com/vacp2p/specs/blob/master/specs/waku/v2/waku-rln-relay.md ↩ 4 Waku v2: https://github.com/vacp2p/specs/blob/master/specs/waku/v2/waku-v2.md ↩ 6 Waku Relay: https://github.com/vacp2p/specs/blob/master/specs/waku/v2/waku-relay.md ↩ 8 Whisper: https://eips.ethereum.org/EIPS/eip-627 ↩
In the section of "Achievements so far":
We have also put a bounty at 0xHack for using JS-Waku and running a workshop...
In the section of "What's next?":
Whether you are a developer, you can come chat with us using WakuJS Web Chat or chat2. You can get support on Discord #waku-support (dev support)...