Struct RekeyFollow 

pub struct RekeyFollow {
    pub updated: Option<CommunityV2>,
    pub self_removed: bool,
    pub dissolved: bool,
    pub wedged: bool,
}

The outcome of a rekey-follow pass.

Fields

updated: Option<CommunityV2>

The community after adopting every rotation it could catch up on, or None if nothing advanced.

self_removed: bool

A base rotation removed us — the caller tears the local hold down (the updated community is not persisted in that case).

dissolved: bool

An owner tombstone sits on the dissolved plane (CORD-02 §9) — the local flag is already set; the caller surfaces the death and stops following.

wedged: bool

A complete authorized rotation carried a blob AT OUR LOCATOR that would not open (a width this build predates, a rotator bug, or a deliberately undecryptable blob planted to pass an admissibility check while severing us). Never a removal (CORD-06 §2: removal is the ABSENCE of a blob), so the walk parks — but the park is otherwise indistinguishable from “no rotation happened”, which is exactly what makes it abusable. Surfaced so the user learns their key delivery is broken while the prior root still reaches everyone.