Changed getReferralScore() to read from pallet_referral::ReferralCount
instead of non-existent pallet_trust::ReferralScores.
Changes:
- Read referral count from api.query.referral.referralCount
- Implement proper score calculation logic:
* 0 referrals: 0 points
* 1-5 referrals: count × 4 points
* 6-20 referrals: 20 + (count - 5) × 2 points
* 21+ referrals: capped at 50 points
- Add detailed documentation explaining score calculation
- Remove warning spam in production (only warn in dev mode)
This fixes the console warning "Referral scores not available in
trust pallet" by using the actual pallet_referral storage that
already exists and is properly maintained.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Only show "Referral scores not available in trust pallet" warning
in development mode to prevent console spam in production.
The warning occurs because api.query.trust.referralScores is not
yet implemented in the trust pallet, but getAllScores() calls it
every time user data is loaded.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
## Problem
Frontend was showing 'connecting network' message on production (pezkuwichain.io) because:
1. WebSocket endpoint was hardcoded to localhost in App.tsx
2. DEFAULT_ENDPOINT in polkadot.ts was not reading environment variables
## Solution
### shared/blockchain/polkadot.ts
- Added getWebSocketEndpoint() function to read VITE_NETWORK and corresponding VITE_WS_ENDPOINT_* env vars
- Changed DEFAULT_ENDPOINT from hardcoded value to call getWebSocketEndpoint()
- Now correctly uses wss://ws.pezkuwichain.io in production
### web/src/App.tsx
- Removed hardcoded endpoint="ws://127.0.0.1:9944" prop from PolkadotProvider
- Now uses DEFAULT_ENDPOINT which reads from environment
### web/vite.config.ts
- Minor formatting improvements (no functional changes)
### CLAUDE_README_KRITIK.md (New file)
- Critical documentation for future Claude instances
- Documents VPS validator setup, bootnode configuration
- Strict warnings not to modify working blockchain
- Troubleshooting commands and procedures
- Frontend deployment steps
## Result
- Production site now correctly connects to wss://ws.pezkuwichain.io
- Environment-based configuration working as expected
- Local dev still uses ws://127.0.0.1:9944
## Files Changed
- shared/blockchain/polkadot.ts: Dynamic endpoint selection
- web/src/App.tsx: Remove hardcoded endpoint
- CLAUDE_README_KRITIK.md: Critical documentation (new)
This commit restores the comprehensive i18n translations file that was
accidentally removed. The file contains:
- 2590 lines of translations
- 6 languages: English, Kurdish (Kurmanji & Sorani), Turkish, Arabic, Persian
- Complete translations for all app screens and features
Changes:
- Restored shared/i18n/translations.ts from commit a04f8b8
- Updated shared/i18n/index.ts to export from translations.ts
- Both JSON locale files and TypeScript translations now available
The translations.ts file includes comprehensive translations for:
- All navigation and UI elements
- Settings, profile, wallet screens
- Citizenship and referral features
- Terms, privacy policy, help screens
- Complete mobile app interface
Sorry for missing this important file in the previous migration.
This commit reorganizes the codebase to eliminate duplication between web and mobile frontends by moving all commonly used files to the shared folder.
Changes:
- Moved lib files to shared/lib/:
* wallet.ts, staking.ts, tiki.ts, identity.ts
* multisig.ts, usdt.ts, scores.ts, citizenship-workflow.ts
- Moved utils to shared/utils/:
* auth.ts, dex.ts
* Created format.ts (extracted formatNumber from web utils)
- Created shared/theme/:
* colors.ts (Kurdistan and App color definitions)
- Updated web configuration:
* Added @pezkuwi/* path aliases in tsconfig.json and vite.config.ts
* Updated all imports to use @pezkuwi/lib/*, @pezkuwi/utils/*, @pezkuwi/theme/*
* Removed duplicate files from web/src/lib and web/src/utils
- Updated mobile configuration:
* Added @pezkuwi/* path aliases in tsconfig.json
* Updated theme/colors.ts to re-export from shared
* Mobile already uses relative imports to shared (no changes needed)
Architecture Benefits:
- Single source of truth for common code
- No duplication between frontends
- Easier maintenance and consistency
- Clear separation of shared vs platform-specific code
Web-specific files kept:
- web/src/lib/supabase.ts
- web/src/lib/utils.ts (cn function for Tailwind, re-exports formatNumber from shared)
All imports updated and tested. Both web and mobile now use the centralized shared folder.
Centralized common code into shared/ folder to eliminate duplication and
improve maintainability across all three frontend projects (web, mobile,
pezkuwi-sdk-ui).
Changes:
- Added token types and constants to shared/types/tokens.ts
- TokenInfo, PoolInfo, SwapQuote, and other DEX types
- KNOWN_TOKENS with HEZ, PEZ, wUSDT definitions
- Token logos (🟡🟣💵)
- Added Kurdistan color palette to shared/constants/
- Kesk, Sor, Zer, Spî, Reş color definitions
- Added TOKEN_DISPLAY_SYMBOLS mapping (USDT vs wUSDT)
- Updated blockchain configuration in shared/blockchain/polkadot.ts
- Added beta testnet endpoint (wss://beta-rpc.pezkuwi.art)
- Defined DEFAULT_ENDPOINT constant
- Moved i18n to shared/i18n/
- Centralized translation files for 6 languages (EN, TR, KMR, CKB, AR, FA)
- Added LANGUAGES configuration with RTL support
- Created isRTL() helper function
- Updated web and mobile to import from shared
- web/src/types/dex.ts now re-exports from shared
- web/src/contexts/PolkadotContext.tsx uses DEFAULT_ENDPOINT
- mobile/src/i18n/index.ts uses shared translations
- mobile/src/contexts/PolkadotContext.tsx uses DEFAULT_ENDPOINT
- Updated shared/README.md with comprehensive documentation
This architecture reduces code duplication and ensures consistency across
all frontend projects.
Restructured the project to support multiple frontend applications:
- Move web app to web/ directory
- Create pezkuwi-sdk-ui/ for Polkadot SDK clone (planned)
- Create mobile/ directory for mobile app development
- Add shared/ directory with common utilities, types, and blockchain code
- Update README.md with comprehensive documentation
- Remove obsolete DKSweb/ directory
This monorepo structure enables better code sharing and organized
development across web, mobile, and SDK UI projects.
pezkuwichain
Claude