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

feat: upgrade docusaurus version to v3

Browse Source
This commit is contained in:
jinhojang6
2025-04-23 01:40:37 +09:00
committed by Jinho Jang
parent 94c2339e04
commit 77b1a2988b
47 changed files with 6824 additions and 9702 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
rlog/2020-09-28-waku-v2-update.mdx
View File

@@ -12,7 +12,7 @@ discuss: https://forum.vac.dev/t/discussion-waku-v2-update/56
A research log. Read on to find out what is going on with Waku v2, a messaging protocol. What has been happening? What is coming up next?
<!--truncate-->
{/* truncate */}
It has been a while since the last post. It is time for an update on Waku v2. Aside from getting more familiar with libp2p (specifically nim-libp2p) and some vacation, what have we been up to? In this post we'll talk about what we've gotten done since last time, and briefly talk about immediate next steps and future. But first, a recap.
@@ -24,7 +24,7 @@ In the last post ([Waku v2 plan](https://vac.dev/waku-v2-plan)) we explained the
2. Track 2 - Better routing
3. Track 3 - Accounting and user-run nodes
As well as various rough components for each track. The primary initial focus is track 1. This means things like: moving to FloodSub, simplify the protocol, core integration, topic interest behavior, historical message caching, and Waku v1<\>v2 bridge.
As well as various rough components for each track. The primary initial focus is track 1. This means things like: moving to FloodSub, simplify the protocol, core integration, topic interest behavior, historical message caching, and Waku v1`<\>`v2 bridge.
## Current state