github/vac.dev
1
1
Fork 0
mirror of https://github.com/vacp2p/vac.dev.git synced 2026-01-08 22:28:01 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update Links (#163)

Browse Source 
* Update 2022-07-22-relay-anonymity.mdx

* Update 2022-07-22-relay-anonymity.mdx

* Update 2019-07-19-p2p-data-sync-for-mobile.mdx

* Update 2019-08-02-vac-overview.mdx

* Update 2019-10-04-remote-log.mdx

* Update 2019-12-03-fixing-whisper-with-waku.mdx

* Update 2020-02-14-waku-update.mdx

* Update 2020-02-7-dns-based-discovery.mdx

* Update 2020-02-7-dns-based-discovery.mdx

* Update 2020-07-01-waku-v2-pitch.mdx

* Update 2020-09-28-waku-v2-update.mdx

* Update 2020-11-10-waku-v2-ethereum-messaging.mdx

* Update 2021-03-03-rln-relay.mdx

* Update 2021-06-04-presenting-js-waku.mdx

* Update 2021-08-06-coscup-waku-ethereum.mdx

* Update 2021-10-25-waku-v1-vs-waku-v2.mdx

* Update 2022-04-12-introducing-nwaku.mdx

* Update 2022-05-09-ambient-peer-discovery.mdx

* Update 2022-05-17-noise.mdx

* Update 2022-11-04-building-privacy-protecting-infrastructure.mdx

* Update 2022-11-08-waku-for-all-decentralize-applications.mdx

* Update 2023-04-03-waku-as-a-network.mdx

* Update 2023-04-03-waku-as-a-network.mdx

* Update 2023-04-24-device-pairing-in-js-waku-and-go-waku.mdx

* Update 2023-11-07-rln-relay.mdx

* Update 2024-05-03-rln-light-verifiers.mdx

* Update 2024-05-13-rln-v3.mdx
This commit is contained in:
Jimmy Debe
2025-03-04 14:01:14 -05:00
committed by GitHub
parent fba3a2d7c3
commit 062761386f
24 changed files with 107 additions and 106 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
rlog/2020-07-01-waku-v2-pitch.mdx
View File

@@ -108,7 +108,7 @@ Very experimental and incomplete libp2p support can be found in the nim-waku rep
### 2. 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://rfc.vac.dev/spec/6/>). Not all of it serves it purpose anymore. For example, do we still need RLP here when we have Protobuf messages? What about extremely low PoW when we have peer scoring? What about key management / encryption when have encryption at libp2p and Status protocol level?
Due to Waku's origins in Whisper, devp2p and as a standalone protocol, there are a lot of stuff that has accumulated (<https://rfc.vac.dev/waku/standards/legacy/6/waku1/>). Not all of it serves it purpose anymore. For example, do we still need RLP here when we have Protobuf messages? What about extremely low PoW when we have peer scoring? What about key management / encryption when have encryption at libp2p and Status protocol level?
Not everything has to be done in one go, but being minimalist at this stage will the protocol lean and make us more adaptable.