KPrasch

After deliberation, usage, and reconsideration embedded emitters have become the norm. If there is still emitter injection into the python API, it can be removed.

Yes - I think so. We see 'em working everyday in worker consoles.

> Proposed solution: replace the emitter with logging, make the address and the balance accessible from the Ursula object, and emit them from CLI where it is created. This isn't...

Reopening this issue after this pattern continues to propagate in #2701.

Not yet done since it cannot be handled from worker configs.

Thanks for the report! We're looking into the cause.

Related to https://github.com/nucypher/nucypher/issues/1714

Hmm looking at this again - "Verifying key swapped out" is pretty vague language IMO.

Guess I better roll up my sleeves! I'd like to work on this Issue this week since I anticipate it will need several iterations for a minimum viable solution.

This is normal and expected behavior when contacting a peer that is offline. If your node continues to run, carry on!