Hand off control without handing us your secret.

The ceremony creates a new Rally address from the group’s shared public key — not by importing an existing wallet. That address is the on-chain account whose Owner permission is what you hand off. Rekey’s cloud service never holds a Rally private key for the threshold products.

Optional. Leave it off to seal the new Rally address without touching the chain (you can fund later). Turn it on only if the organizer’s machine can pay network fees from an operator funder wallet: Wrap then activates Rally on Shasta, tops it up with a fee reserve (about 100 TRX for a later ownership update), and finishes threshold on-chain setup. You can also optionally leave extra TRX on Rally, or reserve about 2 TRX so B′ can be activated later from Rally instead of a separate funder→B′ transfer. That does not import an old account — each ceremony still derives a fresh Rally.

B′ is a fresh TRON key created at delivery (usually on the receiving group’s combiner machine). Appoint is a single on-chain permission update: Rally’s Owner becomes B′. That costs about 100 TRX from Rally’s balance (the reserve funded earlier). After appoint, control of Rally is the B′ private key — not the ceremony’s shared signing group. The private key stays sealed on the machine that ran appoint; it cannot be rebuilt from the address alone.

No. Activating B′ only gives B′ itself an on-chain presence. Rally can already receive TRX and, after appoint, be spent with the B′ key even if B′ was never funded. Anyone can add TRX to an active Rally; spending Rally’s balance requires the current Owner key (B′ after appoint). Activating B′ is separate from moving or spending Rally funds.

Ceremony participants (organizer and seats) know Group B’s contact identities by design. The wider world should not learn those people’s names or emails from the chain, and should not be able to prove “this Rally is controlled by that group.” After appoint, explorers show Rally’s Owner as a TRON address (B′). Privacy here means unlinkability: that Owner is a fresh key, not a known wallet belonging to a named person — not that ownership is invisible on-chain.

Leave B′ inactive (preferred for privacy). B′ never receives TRX, so it often does not appear as its own funded account on explorers. Rally still works as a transfer account: it can be topped up and spent with the B′ key. Outsiders who look up Rally may see an Owner address, but B′ itself stays quiet — no separate B′ balance history, and no “B′ was funded from X” trail. This is the stealthed controller pattern.

Activate B′. B′ becomes a visible on-chain account (explorer presence, its own balance). That helps public validation and using B′ as a normal wallet, but it increases visibility. Funding B′ from a known operator wallet can also create a linkable chain trail to B′. Use activation when you want B′ obvious; skip it when you want the final controller to stay as quiet as the chain allows.

The unload machine (usually the Group B combiner) creates and holds the B′ private key. Ceremony participants may learn the B′ address at delivery. Rekey’s service must never hold that private key. Control of Rally after appoint is whoever has the B′ key — not whoever merely sees the address. A later ownership change is another permission update signed by the current Owner (again needing Rally fee balance), still without requiring B′ to have been activated.