feat: console wallet use dns seeds

[SWvheerden]

Description

Console wallet use dns seeds

Motivation and Context

The console wallet should use the DNS seed, and not just the seeds in the config file

How Has This Been Tested?

Manual

[github-actions]

Test Results (CI)

1 264 tests   1 264 ✔️  12m 2s ⏱️
     39 suites         0 💤
       1 files           0 ❌

Results for commit 0f035ab.

♻️ This comment has been updated with latest results.

[github-actions]

Test Results (Integration tests)

28 tests   28 ✔️  11m 52s ⏱️
11 suites    0 💤
  2 files      0 ❌

Results for commit 0f035ab.

♻️ This comment has been updated with latest results.

[stringhandler]

Nice find

[brianp]

I think I want to test this.

but a clarification if you will:

should use the DNS seed, and not just the seeds in the config file

and not just

So it should use both? Because the change swings the pendulum, to ignore the config seeds, and use whatever the PeerDB already has.
At what point did it fetch DNS seeds?

[SWvheerden]

ld use the DNS seed, and not just the seeds in the config file

and not just

it should use both:

tari/base_layer/p2p/src/initialization.rs

Line 583 in 851cb00

let peers = Self::try_parse_seed_peers(&self.seed_config.peer_seeds)?;

[brianp]

LGTM

Thanks for the response.

Tested locally:
Created new wallet on esme network. Removed the peers from the config. Deleted the dht, and peer db. Restarted the wallet and it started finding peers instantly, found and connected to a base node, and carried on.

👍🏻

Ack (sans ut)