PR #774 corrects a wiring bug that prevented cors_allow_origins from being applied to the router, ensuring cross-origin policies are enforced as configured. PR #775 builds on the gateway auth layer by adding bearer token revocation triggered on principal deletion, closing a credential-lifetime gap where tokens could outlive their owning principal. Together these two fixes harden the gateway's security posture around identity lifecycle and origin control.

PR #768 introduces a dedicated HTTP admin API surface alongside invite token primitives in the gateway. This gives operators a structured programmatic interface for administrative operations rather than relying on out-of-band tooling. The invite token primitives lay the groundwork for controlled onboarding flows, allowing the gateway to gate new principal creation behind issued tokens.

PR #317 pins OpLog blocks, requests persistent browser storage, and emits a critical-block-evicted event to signal data-loss risk before it occurs. PR #316 adds an OpLog epoch-reset primitive with a permanent walkback floor, enabling controlled log compaction without losing the authoritative history baseline. PR #331 replaces the previous blockstore with an IDBBlockstore-backed implementation, adds a pointer-publish gate, and includes a token fallback path to ensure profile data survives browser cache eviction. PR #309 adds identity-key fallback storage and tolerates LoadBlockFailedError so that transient block-fetch failures no longer surface as hard identity failures. Collectively these changes make the profile subsystem significantly more durable under adverse browser storage conditions.

PR #315 introduces a sphere.connectivity surface that exposes network reachability state and gates the offline send-path, preventing operations that would silently fail when infrastructure is unreachable. PR #327 softens the connectivity gate from a hard block to an advisory, allowing the application to proceed with degraded UX rather than a full stop when connectivity is uncertain. PR #320 adds logic to auto-clear the BLOCKED profile state on a successful pointer poll, resolving the case where transient connectivity blips left profiles permanently stuck. These changes give the SDK a coherent, recoverable model for partial and intermittent connectivity.

PR #314 implements lazy loading of the local profile from a snapshot blob on startup, deferring the full remote sync to the background. This decouples perceived load time from network latency, letting the UI become interactive immediately while the SDK reconciles with the remote state asynchronously. The approach also provides a fallback baseline if remote sync fails, improving robustness in offline-first scenarios.

PRs #317 through #320 in sphere build out a service-status banner that probes aggregator, IPFS, Nostr, and Markets API endpoints and surfaces their health in the UI, with PR #318 correcting the banner truth logic and PR #319 adding a direct IPFS gateway probe that bypasses the SDK IpfsPinger for more accurate results. PRs #321 and #322 extend developer tooling to allow runtime override of Nostr, IPFS, Faucet, Market, and aggregator endpoints via console commands or localStorage, with PR #322 exposing these overrides through a Settings modal GUI. PR #323 fixes a z-index stacking issue where BaseModal was rendered beneath MobileBottomNav, and sphere-sdk PR #322 wraps local-infra images for relay, faucet, and aggregator in the ssl-manager, enabling HTTPS in local development. These changes significantly accelerate developer iteration and make infrastructure health visible to end users.

PR #3 introduces BFT snapshot support to the unicity-node, enabling the consensus layer to periodically checkpoint its state. Snapshots reduce the cost of node recovery and bootstrapping by allowing new or restarting nodes to sync from a recent snapshot rather than replaying the full chain history. This is a foundational addition to the network node's operational robustness and sets the stage for faster node onboarding as the network grows.