You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The nim-waku repo and project has recently been renamed to nwaku.
However, the binaries compiled from the repo still use a naming scheme where nwaku is never mentioned.
Examples of binaries compiled from the nwaku repo:
wakunode1
wakunode2
chat2
wakubridge
sim2
etc.
This may be confusing, e.g. when:
any of the binaries are published as a standalone
a binary is embedded as a service node in another application
from a marketing perspective
Proposal
This issue proposes that we rethink the binary naming scheme, preferably adopting a scheme similar to nimbus-eth2 for organisational consistency.
The text was updated successfully, but these errors were encountered:
Problem
The
nim-waku
repo and project has recently been renamed tonwaku
.However, the binaries compiled from the repo still use a naming scheme where
nwaku
is never mentioned.Examples of binaries compiled from the
nwaku
repo:wakunode1
wakunode2
chat2
wakubridge
sim2
etc.
This may be confusing, e.g. when:
Proposal
This issue proposes that we rethink the binary naming scheme, preferably adopting a scheme similar to nimbus-eth2 for organisational consistency.
The text was updated successfully, but these errors were encountered: