feat: whitepaper v6.0, tokenomics, roadmap, security, ecosystem refresh

CLAUDE.md

@@ -0,0 +1,65 @@
+# CLAUDE.md
+
+Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.
+
+**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.
+
+## 1. Think Before Coding
+
+**Don't assume. Don't hide confusion. Surface tradeoffs.**
+
+Before implementing:
+- State your assumptions explicitly. If uncertain, ask.
+- If multiple interpretations exist, present them - don't pick silently.
+- If a simpler approach exists, say so. Push back when warranted.
+- If something is unclear, stop. Name what's confusing. Ask.
+
+## 2. Simplicity First
+
+**Minimum code that solves the problem. Nothing speculative.**
+
+- No features beyond what was asked.
+- No abstractions for single-use code.
+- No "flexibility" or "configurability" that wasn't requested.
+- No error handling for impossible scenarios.
+- If you write 200 lines and it could be 50, rewrite it.
+
+Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
+
+## 3. Surgical Changes
+
+**Touch only what you must. Clean up only your own mess.**
+
+When editing existing code:
+- Don't "improve" adjacent code, comments, or formatting.
+- Don't refactor things that aren't broken.
+- Match existing style, even if you'd do it differently.
+- If you notice unrelated dead code, mention it - don't delete it.
+
+When your changes create orphans:
+- Remove imports/variables/functions that YOUR changes made unused.
+- Don't remove pre-existing dead code unless asked.
+
+The test: Every changed line should trace directly to the user's request.
+
+## 4. Goal-Driven Execution
+
+**Define success criteria. Loop until verified.**
+
+Transform tasks into verifiable goals:
+- "Add validation" → "Write tests for invalid inputs, then make them pass"
+- "Fix the bug" → "Write a test that reproduces it, then make it pass"
+- "Refactor X" → "Ensure tests pass before and after"
+
+For multi-step tasks, state a brief plan:
+```
+1. [Step] → verify: [check]
+2. [Step] → verify: [check]
+3. [Step] → verify: [check]
+```
+
+Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
+
+---
+
+**These guidelines are working if:** fewer unnecessary changes in diffs, fewer rewrites due to overcomplication, and clarifying questions come before implementation rather than after mistakes.

CONTENT-REVIEW-PIVOT.md

@@ -0,0 +1,106 @@
+# Content Review: Cambodia Pivot Alignment
+
+**Date:** 2026-04-17
+**Status:** Complete
+
+## Summary
+
+All content has been reviewed and aligned with Selendra's strategic pivot from "global public L1 blockchain" to "Cambodia-specific application infrastructure."
+
+## The Pivot
+
+**Key Changes:**
+1. NO global ambitions — Cambodia only until domestic traction
+2. Selendra is INVISIBLE to end users — "blockchain" in marketing = instant turnoff
+3. KOOMPI owns the stack: StadiumX, Riverbase, Bitriel Bong, Baray, Selendra
+4. NO stablecoin on Selendra — use existing USDC/USDT on Base/BSC
+5. NO bridging — USDC stays on native chains
+6. Internal bootstrapping — ship own products first
+
+## Files Changed
+
+### REWRITTEN
+
+| File | Changes |
+|------|---------|
+| `content/paper/whitepaper.md` | v6.0 → v7.0. Removed global expansion (Thailand, Vietnam), removed CEX/DEX plans, added KOOMPI product stack, clarified no stablecoin/bridge strategy |
+| `content/docs/concepts/tokenomics.md` | Removed CEX listing, DEX launch, wSEL on Ethereum plans. Added internal bootstrapping focus, success metrics before exchange listings |
+| `content/docs/concepts/economic-model.md` | Aligned with pivot. Added stablecoin strategy section (no native stablecoin, use existing) |
+| `content/blog/selendra-2026-vision.md` | Removed regional expansion, CEX/DEX plans. Added Cambodia-first focus, KOOMPI product stack, no exchange plans until domestic traction |
+
+### ARCHIVED (moved to `content/archived/`)
+
+| File | Reason |
+|------|--------|
+| `content/biz/selendra-stablecoin-concept.md` | Contradicts pivot — NO stablecoin on Selendra. We use existing USDC/USDT on native chains |
+| `content/biz/technical/evm-first-design.md` | Premature implementation detail. Technically valid but not currently prioritized |
+
+### KEPT (no changes needed)
+
+| File | Reason |
+|------|--------|
+| `content/docs/concepts/architecture.md` | Technical documentation, accurate |
+| `content/docs/cambodia-opportunity.md` | Showcase page for why Selendra exists, already aligned |
+| `content/blog/introducing-selendra.md` | General introduction, focuses on Cambodia/SEA |
+| `content/blog/running-mainnet-lessons-learned.md` | Technical lessons, still accurate |
+| `content/blog/performance-upgrade-block-time.md` | Pure technical content |
+| `content/blog/wdk-integration.md` | Technical WDK integration, accurate |
+| `content/blog/unified-accounts-architecture.md` | Technical architecture, accurate |
+| `content/blog/dual-smart-contracts.md` | Technical content about EVM/WASM |
+| `content/blog/2025-roadmap-validator-expansion.md` | Technical validator roadmap, still accurate |
+
+All developer documentation (SDK, smart contracts, tools, run nodes) kept intact as technically accurate.
+
+## Key Messaging Changes
+
+### Before
+- "Global L1 blockchain for Southeast Asia"
+- "Thailand, Vietnam expansion in 2027"
+- "CEX listings (MEXC, Gate.io)"
+- "DEX launch (SEL/USDT)"
+- "wSEL on Ethereum (Uniswap)"
+- "KHR-pegged stablecoin (sKHR)"
+
+### After
+- "Cambodia-specific application infrastructure"
+- "No regional expansion until domestic traction proven"
+- "No exchange plans until Cambodia success metrics met"
+- "No native stablecoin — use existing USDC/USDT"
+- "No bridging — stablecoins stay on native chains"
+- "Internal bootstrapping through KOOMPI products"
+
+## Success Metrics Before Expansion
+
+- 1,000+ active Riverbase merchants
+- 100,000+ Bitriel Bong users
+- 3+ government ministry partnerships
+- Sustained daily transaction volume
+
+## KOOMPI Product Stack (Featured)
+
+1. **StadiumX** — Sports platform (tickets, loyalty, athlete tokens)
+2. **Riverbase** — E-commerce for Cambodian SMEs (~100 merchants live)
+3. **Bitriel Bong** — Tourist payment app (chain-agnostic, optional Selendra backend)
+4. **Baray** — Banking API for financial services
+5. **Selendra** — Ledger backend for all the above
+
+## Technical Accuracy Preserved
+
+All technical documentation remains accurate:
+- EVM/WASM dual VM architecture
+- Unified accounts (0x... addresses)
+- Consensus (Aura + AlephBFT)
+- Staking mechanics
+- SDK, CLI, smart contract docs
+- Security documentation
+
+Only strategic messaging changed. Technical details intact.
+
+## Next Steps
+
+1. ✅ All content aligned with pivot
+2. ✅ Archived outdated concepts
+3. ✅ Whitepaper updated to v7.0
+4. ✅ Tokenomics reflects actual strategy
+5. → Commit changes with clear message
+6. → Update website to reflect new messaging

CONTRIBUTING.md

@@ -82,6 +82,91 @@ pnpm start
 
 ## How to Contribute
 
+### Smart Contract Contributions
+
+Selendra smart contracts use Foundry for testing and deployment.
+
+**Setup**
+```bash
+# Install Foundry
+curl -L https://foundry.paradigm.xyz | bash
+foundryup
+
+# Navigate to contracts directory
+cd contracts/
+
+# Install dependencies
+forge install
+```
+
+**Testing**
+```bash
+# Run all tests
+forge test
+
+# Run tests with gas reporting
+forge test --gas-report
+
+# Run specific test
+forge test --match-test testWithdraw
+```
+
+**Requirements**
+- All tests must pass before PR submission
+- Gas optimizations must not break functionality
+- Follow Solidity 0.8.x style guidelines
+- Include NatSpec comments for all public functions
+
+**PR Process**
+1. Create branch from `main`
+2. Write tests for new functionality
+3. Ensure `forge test` passes with 100% coverage for new code
+4. Submit PR with description of changes
+5. Address review feedback
+
+### Documentation Contributions
+
+We welcome documentation improvements!
+
+**Style Guide**
+- Use clear, concise language
+- Target technical audience (developers, node operators)
+- Include code examples for all API references
+- Test your changes locally before submitting
+
+**How to Contribute**
+1. Small fixes: Use "Edit this page" link at bottom
+2. Larger changes: Create issue first, then submit PR
+3. New content: Discuss in GitHub issue before writing
+
+**Documentation Structure**
+- `content/docs/` — Main documentation
+- `content/paper/` — Whitepaper
+- `content/blog/` — Blog posts
+
+### WDK Module Contributions
+
+The Tether WDK (Wallet Development Kit) integration uses a modular architecture.
+
+**Adding New Chain Modules**
+
+1. Create module in `contracts/wdk/modules/`
+2. Implement required interfaces:
+   - `IWalletModule`
+   - `IGaslessModule` (if applicable)
+   - `ISwapModule` (if applicable)
+   - `IBridgeModule` (if applicable)
+
+3. Add module configuration in `contracts/wdk/config/`
+4. Write tests for all module functions
+5. Update documentation with chain-specific parameters
+
+**Module Requirements**
+- Gasless transactions must use ERC-4337
+- Swap modules must support SEL/USDT pairs
+- Bridge modules must verify on-chain finality
+- All modules must pass Foundry tests
+
 ### Reporting Issues
 
 1. **Bug Reports**: If you find errors in the documentation, broken links, or incorrect information