> For the complete documentation index, see [llms.txt](https://docs.pixeljourney.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixeljourney.xyz/pxlabs-innovation-lab/pxlabs/px-packages/shared-state-and-cross-portal-communication.md).

# Shared State & Cross-Portal Communication

> **⚠️ DEVELOPMENT STATUS (June 2026)**\
> The shared state and cross-portal communication layer is in foundational design. Core principles for secure state synchronization, context sharing, and orchestration between portals are being established. Many implementation details remain under active development.\
> **We welcome high-level feedback** on desired cross-portal behaviors and state sharing priorities. Join our Discord to share your thoughts.

One of the most powerful aspects of **Px Packages & Px Portals** is the ability for different experiences to intelligently share context and state. Instead of each portal operating in complete isolation, Px Portals enables secure, user-controlled sharing of relevant information across the ecosystem.

## 🎯 Why Shared State Matters

When users move between PxLanding, PxLearn, PxWallet, PxStaking, PxHot, PxMarket, and future experiences, they should not have to start from scratch every time. Shared state allows the ecosystem to feel cohesive and intelligent:

* Your current staking positions, Arena Power, and learning progress can influence what you see and what options are available in other portals.
* Achievements and badges earned in one place can be recognized across the suite.
* Resource and token balances can be referenced without forcing manual refreshes or redundant actions.
* Automation settings configured in PxVault can apply intelligently across relevant experiences.

This creates a much more powerful and seamless user experience than a collection of disconnected tools.

## 🔗 Types of Shared Information

Px Portals is designed to handle several categories of shared state:

* **Identity & Profile** — Consistent user identity, preferences, and display settings across portals.
* **Progress & Achievements** — Learning progress, battle performance, crafting milestones, and badges.
* **Economic State** — Staking positions, token balances, resource levels, and open orders.
* **Contextual Awareness** — Current mode or focus (e.g., “user is optimizing yield” or “user is in learning mode”) that other portals can respond to.
* **Automation Rules** — User-defined or ownership-unlocked automation preferences that can apply across relevant experiences.

All sharing is done with strong user control and transparency — nothing happens without clear consent and visibility.

## 🛡️ Security & User Control

Shared state is only valuable if it is also secure and respects user sovereignty:

* Users have full visibility into what information is being shared and with which portals.
* Granular controls allow users to limit or disable specific types of state sharing.
* All cross-portal communication follows strict security principles defined within Px Packages.
* Sensitive operations (especially those involving keys or large value transfers) remain isolated unless explicitly authorized.

This balance between convenience and security is a core design goal of Px Portals.

## 🚀 Long-Term Vision

As Px Portals matures, shared state and cross-portal communication are expected to become even more sophisticated:

* Real-time synchronization of key metrics (Arena Power, staking multipliers, resource status) across portals.
* Contextual recommendations that adapt based on activity in other parts of the ecosystem.
* Deeper orchestration where actions in one portal can intelligently trigger or influence workflows in another.
* Foundation for advanced multi-chain experiences where state can flow across different blockchains.

Shared state is what transforms Pixel Journey from a set of useful tools into a truly intelligent, interconnected ecosystem.

## 🤝 Get Involved

We are still defining the boundaries and priorities for shared state. Your perspective on what information should flow between portals — and what should remain private — is very valuable.

**Join our Discord** to share ideas about cross-portal communication and state sharing.

*High-level strategic overview. Specific implementation details are still being defined. DYOR.*