mirror of
https://github.com/logos-messaging/js-waku.git
synced 2026-04-02 01:33:28 +00:00
0dfe35281c
Nodes returned by DNS Discovery are not guaranteed to be reachable. Hence, setting an upfront limit based on sought capability does not provide any guarantees that such capability should be reached. The discovery's mechanism role is to find Waku 2 nodes. As many as possible. It is then the role of the peer manager to decide: - whether to attempt connecting to the node based on advertised capabilities - retain connection to the node based on actual mounted protocols. We still want to prevent infinite loops, hence the `maxGet` parameter. Also, there was a dichotomy between code tested, and code actually used by libp2p peer discovery, now resolved. # Conflicts: # packages/discovery/src/dns/constants.ts
16 lines
544 B
TypeScript
16 lines
544 B
TypeScript
import { Tags } from "@waku/interfaces";
|
|
|
|
/**
|
|
* The ENR tree for the different fleets.
|
|
* SANDBOX and TEST fleets are for The Waku Network.
|
|
*/
|
|
export const enrTree = {
|
|
SANDBOX:
|
|
"enrtree://AIRVQ5DDA4FFWLRBCHJWUWOO6X6S4ZTZ5B667LQ6AJU6PEYDLRD5O@sandbox.waku.nodes.status.im",
|
|
TEST: "enrtree://AOGYWMBYOUIMOENHXCHILPKY3ZRFEULMFI4DOM442QSZ73TT2A7VI@test.waku.nodes.status.im"
|
|
};
|
|
|
|
export const DEFAULT_BOOTSTRAP_TAG_NAME = Tags.BOOTSTRAP;
|
|
export const DEFAULT_BOOTSTRAP_TAG_VALUE = 50;
|
|
export const DEFAULT_BOOTSTRAP_TAG_TTL = 100_000_000;
|