Tg identities v2 implementation

.eslintignore

@@ -5,4 +5,5 @@ dist
 .github
 .vscode
 .env
-postgres_*
+postgres_*
+aptos_examples_ts

.eslintrc.cjs

@@ -38,7 +38,7 @@ module.exports = {
             "error",
             {
                 selector: "variableLike",
-                format: ["camelCase"],
+                format: ["camelCase", "UPPER_CASE"],
                 leadingUnderscore: "allow",
                 trailingUnderscore: "allow",
             },

.github/workflows/claude-merge-fix.yml

@@ -0,0 +1,66 @@
+name: Preserve Claude Memory Files
+
+on:
+  push:
+    branches: ['**']
+
+jobs:
+  preserve-claude:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Check if this was a merge commit
+        id: check_merge
+        run: |
+          if git log -1 --pretty=format:"%P" | grep -q " "; then
+            echo "is_merge=true" >> $GITHUB_OUTPUT
+            echo "✅ Detected merge commit"
+          else
+            echo "is_merge=false" >> $GITHUB_OUTPUT
+            exit 0
+          fi
+
+      - name: Check for .claude changes in merge
+        if: steps.check_merge.outputs.is_merge == 'true'
+        id: check_claude
+        run: |
+          if git log -1 --name-only | grep -q "^\.claude/"; then
+            echo "claude_changed=true" >> $GITHUB_OUTPUT
+            echo "🚨 .claude files were modified in merge - will revert!"
+          else
+            echo "claude_changed=false" >> $GITHUB_OUTPUT
+            exit 0
+          fi
+
+      - name: Revert .claude to pre-merge state
+        if: steps.check_merge.outputs.is_merge == 'true' && steps.check_claude.outputs.claude_changed == 'true'
+        run: |
+          CURRENT_BRANCH=$(git branch --show-current)
+          echo "🔄 Reverting .claude/ to pre-merge state on $CURRENT_BRANCH"
+
+          MERGE_BASE=$(git log -1 --pretty=format:"%P" | cut -d' ' -f1)
+          git checkout $MERGE_BASE -- .claude/ 2>/dev/null || echo "No .claude in base commit"
+
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+
+          if git diff --staged --quiet; then
+            git add .claude/
+          fi
+
+          if ! git diff --cached --quiet; then
+            git commit -m "🔒 Preserve branch-specific .claude files
+
+          Reverted .claude/ changes from merge to keep $CURRENT_BRANCH version.
+          [skip ci]"
+
+            git push origin $CURRENT_BRANCH
+            echo "✅ Successfully preserved $CURRENT_BRANCH .claude files"
+          else
+            echo "ℹ️ No changes to revert"
+          fi

.github/workflows/claude-merge-notify.yml

@@ -0,0 +1,38 @@
+name: Claude PR Warning
+
+on:
+  pull_request:
+    branches: ['**']
+    types: [opened, synchronize]
+
+jobs:
+  claude-warning:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout PR
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Check for .claude changes
+        run: |
+          echo "🔍 Checking if PR touches .claude/ files..."
+
+          if git diff --name-only origin/${{ github.base_ref }}...HEAD | grep -q "^\.claude/"; then
+            echo "⚠️  This PR modifies .claude/ files"
+
+            COMMENT_BODY="⚠️ **Claude Memory Files Detected**
+
+            This PR modifies \`.claude/\` files. After merge, these changes will be **automatically reverted** to preserve branch-specific Claude conversation context.
+
+            **Files that will be reverted:**
+            $(git diff --name-only origin/${{ github.base_ref }}...HEAD | grep '^\.claude/' | sed 's/^/- /' | head -10)
+
+            This is expected behavior to keep Claude conversation context branch-specific. ✅"
+
+            gh pr comment ${{ github.event.number }} --body "$COMMENT_BODY" || echo "Could not post comment"
+          else
+            echo "✅ No .claude files affected"
+          fi
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/fix-serena-conflicts.yml

@@ -0,0 +1,71 @@
+name: Preserve Branch-Specific Serena Files
+
+on:
+  push:
+    branches: ['**']
+
+jobs:
+  preserve-serena:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Check if this was a merge commit
+        id: check_merge
+        run: |
+          if git log -1 --pretty=format:"%P" | grep -q " "; then
+            echo "is_merge=true" >> $GITHUB_OUTPUT
+            echo "✅ Detected merge commit"
+          else
+            echo "is_merge=false" >> $GITHUB_OUTPUT
+            exit 0
+          fi
+
+      - name: Check for .serena changes in merge
+        if: steps.check_merge.outputs.is_merge == 'true'
+        id: check_serena
+        run: |
+          if git log -1 --name-only | grep -q "^\.serena/"; then
+            echo "serena_changed=true" >> $GITHUB_OUTPUT
+            echo "🚨 .serena files were modified in merge - will revert!"
+          else
+            echo "serena_changed=false" >> $GITHUB_OUTPUT
+            exit 0
+          fi
+
+      - name: Revert .serena to pre-merge state
+        if: steps.check_merge.outputs.is_merge == 'true' && steps.check_serena.outputs.serena_changed == 'true'
+        run: |
+          CURRENT_BRANCH=$(git branch --show-current)
+          echo "🔄 Reverting .serena/ to pre-merge state on $CURRENT_BRANCH"
+
+          # Get the first parent (target branch before merge)
+          MERGE_BASE=$(git log -1 --pretty=format:"%P" | cut -d' ' -f1)
+
+          # Restore .serena from the target branch's state before merge
+          git checkout $MERGE_BASE -- .serena/ 2>/dev/null || echo "No .serena in base commit"
+
+          # Configure git
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+
+          # Commit the reversion
+          if git diff --staged --quiet; then
+            git add .serena/
+          fi
+
+          if ! git diff --cached --quiet; then
+            git commit -m "🔒 Preserve branch-specific .serena files
+
+          Reverted .serena/ changes from merge to keep $CURRENT_BRANCH version intact.
+          [skip ci]"
+
+            git push origin $CURRENT_BRANCH
+            echo "✅ Successfully preserved $CURRENT_BRANCH .serena files"
+          else
+            echo "ℹ️ No changes to revert"
+          fi

.github/workflows/notify-serena-merging.yml

@@ -0,0 +1,37 @@
+name: Serena Merge Warning
+
+on:
+  pull_request:
+    branches: ['**']
+
+jobs:
+  serena-warning:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check for .serena changes
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Warn about .serena files
+        run: |
+          # Check if PR touches .serena files
+          if git diff --name-only origin/${{ github.base_ref }}...HEAD | grep -q "^\.serena/"; then
+            echo "⚠️  This PR modifies .serena/ files"
+            echo "🤖 After merge, these will be auto-reverted to preserve branch-specific memories"
+            echo ""
+            echo "Files affected:"
+            git diff --name-only origin/${{ github.base_ref }}...HEAD | grep "^\.serena/" | sed 's/^/  - /'
+
+            # Post comment on PR
+            gh pr comment ${{ github.event.number }} --body "⚠️ **MCP Memory Files Detected**
+
+            This PR modifies \`.serena/\` files. After merge, these changes will be **automatically reverted** to preserve branch-specific MCP memories.
+
+            Files that will be reverted:
+            $(git diff --name-only origin/${{ github.base_ref }}...HEAD | grep '^\.serena/' | sed 's/^/- /')" || echo "Could not post comment"
+          else
+            echo "✅ No .serena files affected"
+          fi
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -126,6 +126,7 @@ src/features/multichain/chainwares/aptoswares/TECHNICAL_PROPOSAL_APTOS_INTEGRATI
 APTOS_INTEGRATION_PLAN.md
 aptos_examples_ts
 
+.serena-backup
 .serena/cache/typescript
 .serena-backup
 PR_COMMENTS
@@ -138,6 +139,10 @@ src/features/bridges/EVMSmartContract/test
 src/features/bridges/EVMSmartContract/GASLESS_BRIDGE_FLOW_DIAGRAM.md
 src/features/bridges/EVMSmartContract/USAGE.md
 CLAUDE.sync-conflict-20250901-171031-7JPPSQB.md
+.serena/cache/typescript/document_symbols_cache_v23-06-25.pkl
+docs/src/
+
+src/features/bridges/
 docs/src/.deps/npm/@openzeppelin/contracts
 docs/src/lib
 docs/src

.serena/memories/data_structure_robustness_completed.md

@@ -0,0 +1,44 @@
+# Data Structure Robustness - COMPLETED
+
+## Issue Resolution Status: ✅ COMPLETED
+
+### HIGH Priority Issue #6: Data Structure Robustness  
+**File**: `src/features/incentive/PointSystem.ts` (lines 193-198)
+**Problem**: Missing socialAccounts structure initialization
+**Status**: ✅ **RESOLVED** - Already implemented during Point System fixes
+
+### Implementation Details:
+**Location**: `addPointsToGCR` method, lines 193-198
+**Fix Applied**: Structure initialization guard before any property access
+
+```typescript
+// REVIEW: Ensure breakdown structure is properly initialized before assignment
+account.points.breakdown = account.points.breakdown || {
+    web3Wallets: {},
+    socialAccounts: { twitter: 0, github: 0, telegram: 0, discord: 0 },
+    referrals: 0,
+    demosFollow: 0,
+}
+```
+
+### Root Cause Analysis:
+**Problem**: CodeRabbit identified potential runtime errors from accessing undefined properties
+**Solution**: Comprehensive structure initialization before any mutation operations
+**Coverage**: Protects all breakdown properties including socialAccounts, web3Wallets, referrals, demosFollow
+
+### Integration with Previous Fixes:
+This fix was implemented as part of the comprehensive Point System null pointer bug resolution:
+1. **Data initialization**: Property-level null coalescing in `getUserPointsInternal` 
+2. **Structure guards**: Complete breakdown initialization in `addPointsToGCR` ← THIS ISSUE
+3. **Defensive checks**: Null-safe comparisons in all deduction methods
+
+### Updated HIGH Priority Status:
+- ❌ ~~Genesis block caching~~ (SECURITY RISK - Dismissed)
+- ✅ **Data Structure Robustness** (COMPLETED)
+- ⏳ **Input Validation** (Remaining - Telegram username/ID normalization)
+
+### Next Focus:
+**Input Validation Improvements** - Only remaining HIGH priority issue
+- Telegram username casing normalization  
+- ID type normalization (String conversion)
+- Located in `src/libs/abstraction/index.ts` lines 86-95

.serena/memories/genesis_caching_security_dismissed.md

@@ -0,0 +1,38 @@
+# Genesis Block Caching Security Assessment - DISMISSED
+
+## Issue Resolution Status: ❌ SECURITY RISK - DISMISSED
+
+### Performance Issue #5: Genesis Block Caching
+**File**: `src/libs/abstraction/index.ts`
+**Problem**: Genesis block queried on every bot authorization check
+**CodeRabbit Suggestion**: Cache authorized bots set after first load
+**Status**: ✅ **DISMISSED** - Security risk identified
+
+### Security Analysis:
+**Risk Assessment**: Caching genesis data creates potential attack vector
+**Attack Scenarios**:
+1. **Cache Poisoning**: Compromised cache could allow unauthorized bots
+2. **Stale Data**: Outdated cache might miss revoked bot authorizations
+3. **Memory Attacks**: In-memory cache vulnerable to process compromise
+
+### Current Implementation Security Benefits:
+- **Live Validation**: Each authorization check validates against current genesis state
+- **No Cache Vulnerabilities**: Cannot be compromised through cached data
+- **Real-time Security**: Immediately reflects any genesis state changes
+- **Defense in Depth**: Per-request validation maintains security isolation
+
+### Performance vs Security Trade-off:
+- **Security**: Live genesis validation (PRIORITY)
+- **Performance**: Acceptable overhead for security guarantee
+- **Decision**: Maintain current secure implementation
+
+### Updated Priority Assessment:
+**HIGH Priority Issues Remaining**:
+1. ❌ ~~Genesis block caching~~ (SECURITY RISK - Dismissed)
+2. ⏳ **Data Structure Robustness** - Runtime error prevention
+3. ⏳ **Input Validation** - Telegram username/ID normalization
+
+### Next Focus Areas:
+1. Point System structure initialization guards
+2. Input validation improvements for Telegram attestation
+3. Type safety improvements in identity routines