mirror of https://github.com/acid-info/vac.dev.git
Merge pull request #10 from vacp2p/enhancement/discuss
enhancement/discuss
This commit is contained in:
commit
4da5e8a04e
|
@ -9,6 +9,10 @@ layout: default
|
|||
<div class="meta">{{ page.date | date_to_string }} • {{ page.author }}</div>
|
||||
<div class="editor-content">
|
||||
{{ content }}
|
||||
|
||||
{% if page.discuss %}
|
||||
<p>Discuss this post on our <a href="{{ page.discuss }}">forum</a>. </p>
|
||||
{% endif %}
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
@ -9,6 +9,7 @@ permalink: /feasibility-semaphore-rate-limiting-zksnarks
|
|||
categories: research
|
||||
summary: A research log. Zero knowledge signaling as a rate limiting mechanism to prevent spam in p2p networks.
|
||||
image: /assets/img/peacock-signaling.jpg
|
||||
discuss: https://forum.vac.dev/t/discussion-feasibility-study-semaphore-rate-limiting-through-zksnarks/21
|
||||
---
|
||||
|
||||
**tldr: Moon math promising for solving spam in Whisper, but to get there we need to invest more in performance work and technical upskilling.**
|
||||
|
@ -149,5 +150,3 @@ For example, this might also include leveraging largely ready made solutions suc
|
|||
Thanks to Barry Whitehat for patient explanation and pointers. Thanks to WJ for helping with runtime issues.
|
||||
|
||||
*Peacock header image from [Tonos](https://en.wikipedia.org/wiki/File:Flickr_-_lo.tangelini_-_Tonos_(1).jpg).*
|
||||
|
||||
Discuss this post on our [forum](https://forum.vac.dev/t/discussion-feasibility-study-semaphore-rate-limiting-through-zksnarks/21).
|
||||
|
|
|
@ -9,6 +9,7 @@ permalink: /fixing-whisper-with-waku
|
|||
categories: research
|
||||
summary: A research log. Why Whisper doesn't scale and how to fix it.
|
||||
image: /assets/img/whisper_scalability.png
|
||||
discuss: https://forum.vac.dev/t/discussion-fixing-whisper-with-waku/27
|
||||
---
|
||||
|
||||
This post will introduce Waku. Waku is a fork of Whisper that attempts to
|
||||
|
@ -291,5 +292,3 @@ In short, we have a [Waku version 0 spec up](https://specs.vac.dev/waku.html) as
|
|||
The spec has been rewrittten for clarity, with ABNF grammar and less ambiguous language. The spec also incorporates several previously [ad hoc implemented features](https://specs.vac.dev/waku.html#additional-capabilities), such as light nodes and mailserver/client support. This has already caught a few incompatibilities between the `geth` (Go), `status/whisper` (Go) and `nim-eth` (Nim) versions, specifically around light node usage and the handshake.
|
||||
|
||||
If you are interested in this effort, please check out [our forum](https://forum.vac.dev/) for questions, comments and proposals. We already have some discussion for better [spam protection](https://forum.vac.dev/t/stake-priority-based-queuing/26) (see [previous post](https://vac.dev/feasibility-semaphore-rate-limiting-zksnarks) for a more complex but privacy-preserving proposal), something that is likely going to be addressed in future versions of Waku, along with many other fixes and enhancement.
|
||||
|
||||
Discuss this post [here](https://forum.vac.dev/t/discussion-fixing-whisper-with-waku/27).
|
||||
|
|
Loading…
Reference in New Issue