Skip to content

Sync the ProConfig to swarms rather than extra data#80

Merged
jagerman merged 5 commits intosession-foundation:devfrom
Doy-lee:doyle-sync-pro-config-to-swarms
Mar 3, 2026
Merged

Sync the ProConfig to swarms rather than extra data#80
jagerman merged 5 commits intosession-foundation:devfrom
Doy-lee:doyle-sync-pro-config-to-swarms

Conversation

@Doy-lee
Copy link
Contributor

@Doy-lee Doy-lee commented Feb 25, 2026

Restore syncing to the swarms so that multi-device Session accounts agree and unify and use the same Session Pro proof. Having every device use the same proof is important to prevent observers from identifying devices based on their attached proof.

This removes the std::optional from the user profile and instead it's loaded from the internal .data dict and follows the same pattern as the rest of the code. Caching the value is additional state that can go out of sync.

Restore syncing to the swarms so that multi-device Session accounts agree and
unify and use the same Session Pro proof. Having every device use the same proof
is important to prevent observers from identifying devices based on their
attached proof.

This removes the std::optional<ProConfig> from the user profile and instead it's
loaded from the internal `.data` dict and follows the same pattern as the rest
of the code. Caching the value is additional state that can go out of sync.
`pro_proof` is just as long as `pro.proof` so no need to pull it into
a reference.
Re-derive the private key and public key into the runtime structures
from the seed saving 64b on the wire.
@jagerman jagerman enabled auto-merge February 25, 2026 02:01
auto-merge was automatically disabled February 25, 2026 03:16

Head branch was pushed to by a user without write access

@jagerman jagerman merged commit 16e440c into session-foundation:dev Mar 3, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants