docs: refresh project overview and env template

Author: Shubbu03

.env.example

@@ -10,6 +10,9 @@ CHALLENGE_TTL_SECONDS=300
 HEARTBEAT_TTL_SECONDS=30
 MAX_MESSAGE_SIZE_BYTES=65536
 MAX_MESSAGE_TTL_SECONDS=604800
+DEFAULT_MESSAGE_TTL_SECONDS=3600
+READ_MESSAGE_TTL_SECONDS=86400
+REPLIED_MESSAGE_TTL_SECONDS=604800
 MAX_MESSAGES_PER_SYNC=200
 MAX_CONVERSATION_ID_LENGTH=128
 MAX_MESSAGE_ID_LENGTH=128
@@ -18,9 +21,34 @@ MESSAGE_RATE_LIMIT_WINDOW_SECONDS=60
 AUTH_RATE_LIMIT_COUNT=12
 AUTH_RATE_LIMIT_WINDOW_SECONDS=60
 MAX_CLIENT_CLOCK_SKEW_MS=300000
+EXPO_ACCESS_TOKEN=
 REPLAY_GUARD_ENABLED=true
 SOLANA_KEYPAIR_PATH=/Users/your-user/.config/solana/id.json
 SOLANA_KEYPAIR_JSON=
 MESSAGE_ROOT_BOOTSTRAP_LEAVES_HEX=01
+REGISTRY_ROOT_BOOTSTRAP_LEAVES_HEX=
 SUNSPOT_GO_DIR=/Users/your-user/DEV/osc/enmarch/vendor/sunspot-sdk/sunspot/go
 GO_BINARY_PATH=/usr/local/go/bin/go
+REGISTRY_SYNC_INTERVAL_MS=30000
+
+# Optional MagicBlock Private Ephemeral Rollup path.
+# Leave disabled to submit root updates directly to Solana.
+MAGICBLOCK_ENABLED=false
+MAGICBLOCK_RPC_URL=
+MAGICBLOCK_VALIDATOR_ADDRESS=
+MAGICBLOCK_MESSAGE_MAGIC_CONTEXT_ADDRESS=MagicContext1111111111111111111111111111111
+MAGICBLOCK_REGISTRY_MAGIC_CONTEXT_ADDRESS=MagicContext1111111111111111111111111111111
+MAGICBLOCK_MESSAGE_ROOT_DELEGATION_BUFFER_ADDRESS=
+MAGICBLOCK_MESSAGE_ROOT_DELEGATION_RECORD_ADDRESS=
+MAGICBLOCK_MESSAGE_ROOT_DELEGATION_METADATA_ADDRESS=
+MAGICBLOCK_MESSAGE_PERMISSION_DELEGATION_BUFFER_ADDRESS=
+MAGICBLOCK_MESSAGE_PERMISSION_DELEGATION_RECORD_ADDRESS=
+MAGICBLOCK_MESSAGE_PERMISSION_DELEGATION_METADATA_ADDRESS=
+MAGICBLOCK_REGISTRY_ROOT_DELEGATION_BUFFER_ADDRESS=
+MAGICBLOCK_REGISTRY_ROOT_DELEGATION_RECORD_ADDRESS=
+MAGICBLOCK_REGISTRY_ROOT_DELEGATION_METADATA_ADDRESS=
+MAGICBLOCK_REGISTRY_PERMISSION_DELEGATION_BUFFER_ADDRESS=
+MAGICBLOCK_REGISTRY_PERMISSION_DELEGATION_RECORD_ADDRESS=
+MAGICBLOCK_REGISTRY_PERMISSION_DELEGATION_METADATA_ADDRESS=
+MAGICBLOCK_COMMIT_THRESHOLD=10
+MAGICBLOCK_COMMIT_INTERVAL_MS=60000

README.md

@@ -1,26 +1,30 @@
 # Enmarch
 
 Private messaging with local encryption, on-chain X-Wing identity, and
-zk-verified message-root updates.
+ZK-verified registry-root and message-root updates.
 
 ## What Is Live Today
 
-- Wallet-authenticated chat clients
+- Wallet-authenticated web and Android chat clients
 - Invite-based encrypted conversations
 - X-Wing public key registration on Solana
 - Redis-backed realtime relay and message sync
-- Backend-generated proofs for message-root updates
-- Solana Explorer-visible message-root transactions
+- Backend-generated proofs for registry-root and message-root updates
+- Configurable MagicBlock Private Ephemeral Rollup (PER) submission path with
+  direct Solana fallback
+- Solana-settled root updates
 
 ## Current Architecture
 
 ### Client
 
 - Solana wallet auth
-- local messaging identity
+- local X25519 and X-Wing messaging identity
 - invite creation and import
 - local encryption and decryption
 - on-chain X-Wing registry integration
+- React + Vite web client
+- Android Expo client with Mobile Wallet Adapter
 
 ### Backend
 
@@ -30,21 +34,30 @@ zk-verified message-root updates.
 - offline sync
 - commitment tracking
 - native proof generation
-- automatic `update_message_root` submission
+- automatic registry-root and message-root submission
+- configurable PER delegation, commit, and undelegation flow
+- direct Solana submission fallback
 
 ### Solana
 
 - main Enmarch program
 - verifier program
-- root state PDAs
+- registry-root and message-root state PDAs
 - append-only X-Wing registry PDA
+- PER permission and delegation instructions
+
+### ZK
+
+- Noir circuit for valid Merkle-tree append transitions
+- native proof generation through Sunspot
+- verifier-gated root updates
 
 ## What Is Not Fully Productized Yet
 
 - durable conversation and message metadata database
 - backend-owned inbox and history model
-- registry-root live submission path
-- long-term replacement for bootstrap Merkle leaves in env
+- long-term replacement for message-root and registry-root bootstrap leaves in
+  env
 - production-ready X-Wing registry account design
 
 ## Repo Layout
@@ -53,11 +66,14 @@ zk-verified message-root updates.
 .
 ├── backend/                  # Bun relay, sync API, on-chain submit path
 ├── frontend/                 # React + Vite messaging app
+├── mobile/                   # Android Expo client with MWA wallet auth
 ├── packages/
 │   ├── circuit/              # Noir circuit + proving artifacts
+│   ├── core/                 # Shared messaging protocol helpers
 │   ├── encryption/           # X-Wing + symmetric encryption helpers
 │   ├── merkle-tree/          # Poseidon tree and witness helpers
-│   └── onchain-client/       # TS Solana client helpers
+│   ├── onchain-client/       # Generated and low-level on-chain helpers
+│   └── solana-client/        # App-facing Solana client helpers
 ├── program/
 │   └── enmarch_program/      # Pinocchio Solana program
 └── setup.sh                  # local dev bootstrap script
@@ -126,11 +142,22 @@ At the repo root:
 - `SOLANA_RPC_URL`
 - `SOLANA_KEYPAIR_PATH`
 - `MESSAGE_ROOT_BOOTSTRAP_LEAVES_HEX`
+- `REGISTRY_ROOT_BOOTSTRAP_LEAVES_HEX`
 - `SUNSPOT_GO_DIR`
 - `REDIS_HOST`
 - `REDIS_PORT`
 - `JWT_SECRET`
 
+Optional MagicBlock PER path:
+
+- `MAGICBLOCK_ENABLED`
+- `MAGICBLOCK_RPC_URL`
+- `MAGICBLOCK_VALIDATOR_ADDRESS`
+- `MAGICBLOCK_MESSAGE_*`
+- `MAGICBLOCK_REGISTRY_*`
+- `MAGICBLOCK_COMMIT_THRESHOLD`
+- `MAGICBLOCK_COMMIT_INTERVAL_MS`
+
 In `frontend/.env.local` if needed:
 
 - `VITE_API_BASE_URL`
@@ -150,8 +177,11 @@ In `mobile/.env` if needed:
 
 - Message payloads are still ephemeral and Redis-backed
 - Conversation metadata is still partly client-side
-- `MESSAGE_ROOT_BOOTSTRAP_LEAVES_HEX` currently bridges pre-existing on-chain
-  tree history until the backend owns durable tree state
+- `MESSAGE_ROOT_BOOTSTRAP_LEAVES_HEX` and `REGISTRY_ROOT_BOOTSTRAP_LEAVES_HEX`
+  currently bridge pre-existing on-chain tree history until the backend owns
+  durable tree state
+- Root updates use MagicBlock PER when enabled and fully configured. The
+  backend falls back to direct Solana submission otherwise.
 
 ## Validation