* rewards: claim what the chain pays, without recording a score first
The People chain has no pezRewards.recordTrustScore and no userEpochScores since the payroll
started holding the roll still through each claim window: a claim pays the trust score at
claim time times the epoch's rate, plus the seat share for a Parlementer seat taken by the
time of the roll. The app still asked for the recorded score, so the claimable list was
always empty, and three screens offered a Record Trust Score button that signed a call that
does not exist.
The buttons, their handlers and texts, and the messages for an error and a success that can
no longer happen are removed; the claimable amount is worked out as the chain's entitlement
does, and the empty state shows in every epoch status. Past recordTrustScore extrinsics in
the transaction history keep their label.
* backend: body-parser 2.4.0 and ip-address 10.7.5
npm audit on the production dependencies: body-parser 2.0.0-2.3.0 (GHSA-27r3-jxmh-p828,
high, denial of service by trailing bytes after a compressed body) and ip-address <=10.7.3
(GHSA-rxp7-6hxx-x8q5, moderate). Lockfile only; npm audit --omit=dev finds nothing after.
* ops: lower the typecheck baseline to 335
Four TS2339 errors in shared/lib/scores.ts went with the userEpochScores code.
* web: dompurify 3.4.17 and zod 4.6.7
npm audit on the production dependencies: dompurify <=3.4.16 (critical: GHSA-cg2g-xh64-v4q7,
GHSA-mrv2-3pqr-j5jr, GHSA-c6gr-qvv4-5v3f) and zod <4.6.6 (high, GHSA-mrhx-c7xc-m3w5, fixed
only in 4.x). No code imports zod; it is here for abitype, whose peer range is
^3.22.0 || ^4.0.0. Typecheck ratchet, lint and the build are unchanged.
- Update staking score/tracking calls from relayApi to peopleApi
- Fix referral score to use on-chain tiered scoring with penalties
- Fix perwerde score to query studentCourses + enrollments storage
- Update Dashboard and StakingDashboard for People Chain API
Remove all frontend staking/trust score calculation and localStorage
fallback code. All scores now read directly from People Chain pallets
(pezpallet-trust, pezpallet-referral, pezpallet-tiki). Trust pallet
computes composite score on-chain.
On-chain trust pallet exists but StakingInfoProvider returns None,
causing trust score to be 0 even when user has stake. Use frontend
calculation until runtime upgrade is deployed.
- Remove LP staking score (not available in blockchain)
- All scores now fetched from People Chain
- Add Start Score Tracking button to Dashboard
- Add staking status display showing tracking duration
Features:
- Add XCMTeleportModal for cross-chain HEZ transfers
- Support Asset Hub and People Chain teleports
- Add "Fund Fees" button with user-friendly tooltips
- Use correct XCM V3 format with teyrchain junction
Fixes:
- Fix PEZ transfer to use Asset Hub API
- Silence unnecessary pallet availability warnings
- Fix transaction loading performance (10 blocks limit)
- Remove Supabase admin_roles dependency
CI/CD:
- Add auto-deploy to VPS on main branch push
- Add version bumping on deploy
- Upload build artifacts for deployment
- Fixed TypeScript type assertion issues
- Updated imports from api-augment/substrate to api-augment/bizinikiwi
- Fixed imgConvert.mjs header and imports
- Added @ts-expect-error for runtime-converted types
- Fixed all @polkadot copyright headers to @pezkuwi
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>
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.
