mirror of
https://github.com/vacp2p/vac.dev.git
synced 2026-01-08 22:28:01 -05:00
Update Links (#163)
* 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:
@@ -139,11 +139,11 @@ Waku can help:
|
||||
share transactions with other sequencers. Waku nodes can act as a neutral network to enable all sequences to access
|
||||
transactions.
|
||||
- Enable censorship-resistant wallet<>L2 communication,
|
||||
- Provide rate limiting mechanism for spam protection: Using [RLN](https://rfc.vac.dev/spec/32/) to prevent DDOS.
|
||||
- Provide rate limiting mechanism for spam protection: Using [RLN](https://rfc.vac.dev/vac/32/rln-v1) to prevent DDOS.
|
||||
|
||||
## Device pairing and communication
|
||||
|
||||
With [Waku Device Pairing](https://rfc.vac.dev/spec/43/), a user can setup a secure encrypted communication channel
|
||||
With [Waku Device Pairing](https://github.com/waku-org/specs/blob/master/standards/application/device-pairing.md), a user can setup a secure encrypted communication channel
|
||||
between their devices. As this channel would operate over Waku, it would be censorship-resistant and privacy preserving.
|
||||
These two devices could be:
|
||||
|
||||
@@ -172,8 +172,8 @@ What you can expect next:
|
||||
- [Scalability and performance studies](https://forum.vac.dev/t/waku-v2-scalability-studies/142/9) and improvement across Waku software,
|
||||
- [New websites](https://github.com/waku-org/waku.org/issues/15) to easily find documentation about Waku and its implementations,
|
||||
- New Waku protocols implemented in all code bases and cross client PoCs
|
||||
([noise](https://rfc.vac.dev/spec/35/), [noise-sessions](https://rfc.vac.dev/spec/37/),
|
||||
[waku-rln-relay](https://rfc.vac.dev/spec/17/), etc),
|
||||
([noise](https://github.com/waku-org/specs/blob/master/standards/application/noise.md), [noise-sessions](https://github.com/waku-org/specs/blob/master/standards/application/noise-sessions.md),
|
||||
[waku-rln-relay](https://rfc.vac.dev/waku/standards/core/17/rln-relay), etc),
|
||||
- Easier to [run your own waku node](https://github.com/status-im/nwaku/issues/828), more operator trials,
|
||||
- Dogfooding and Improvement of existing protocols (e.g. [Waku Filter](https://github.com/vacp2p/rfc/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc++12%2FWAKU2-FILTER)),
|
||||
- Continue our focus Waku portability: Browser,
|
||||
|
||||
Reference in New Issue
Block a user