Scout

Paisley Project Tracker

Live Database Edition
220Total Tasks
38Discuss
57Agree
0In Dev
85In QA
0QA Approved
0In Stage
0Ready for Prod
0In Prod
0Shipped
21Deferred
19Out of Scope
Paisley Wallet Requirements

Paisley Wallet

1. Self-Custodial Wallet Infrastructure

MVP
P1

BIP-39 mnemonic phrase generation (12–24 words)

3 Comments
Rich:SOW Reference: Page 5
Puja:Completed
Observer:ready for QA
P1

Client-side encryption for private keys

2 Comments
Rich:SOW Reference: Page 10
Puja:Completed
P1

Import existing wallet functionality

2 Comments
Puja:Completed
Observer:Ready for QA
P1

UI instructions guiding users to save their mnemonic phrase backup manually

2 Comments
Puja:Will be completed in scope
Observer:Ready for QA
P1

Warning prompts about the importance of secure mnemonic storage

2 Comments
Puja:Will be completed in scope
Observer:Ready for QA
P1

User acknowledgment checkbox for mnemonic phrase responsibility

1 Comments
Puja:Will be completed in scope
P1

Automated mnemonic backup flow with user confirmation (requires server-side storage which contradicts self-custodial principle)

3 Comments
Puja:Not possible in current scope
Mike:This is existing functionality. If we are removing functionality, need to be clear what, why and how
Puja:mnemonic will be backup, already in current code, but we are not storing pass phrase
P1

Wallet recovery from mnemonic phrase (not feasible without storing mnemonic, as agreed)

2 Comments
Puja:Not possible in current scope
Mike:Wallet recovery is clearly necessary for a functional wallet (whether from backed up mnemonic or user-saved mnemonic). MVP needs working seed backup.
P1

Passphrase-protected private key storage on server-side

3 Comments
Puja:Not possible in current scope
Mike:Again existing functionality
Observer:Ready for QA

2. Public Profile System

MVP
P1

Basic member registration system for Paisley cooperative

2 Comments
Puja:Completed
Observer:Ready for QA
P1

KYC verification integration via DIDIT

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Profile editing interface with validation

3 Comments
Rich:SOW Reference: Page 5
Puja:Completed
Observer:Ready for QA
P1

Profile data storage in PostgreSQL with indexing

2 Comments
Puja:Completed
Observer:Ready for QA
P1

User-addressable public profiles with custom URLs (e.g., paisley.app/username)

3 Comments
Rich:SOW Reference: Page 5
Puja:Completed
Observer:Ready for QA
P1

Displaying professional information, skills, and availability

3 Comments
Rich:SOW Reference: Page 5
Puja:Completed
Observer:Ready for QA
P1

Real-time profile preview functionality

2 Comments
Rich:SOW Reference: Page 5
Puja:Completed

3. Multi-Chain Wallet Operations — ETHEREUM

MVP
P1

ETH send functionality with address validation

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

ETH receive with address generation (QR code pending)

1 Comments
Puja:Completed
P1

ETH balance display from Base Sepolia RPC public node endpoint

2 Comments
Puja:Completed
Observer:Ready for QA
P1

ERC-20 send/receive functionality using third-party API (Alchemy or QuickNode)

1 Comments
Puja:Will be completed in scope
P1

Ethereum transaction history via third-party API (Alchemy free tier or QuickNode at $50/month)

1 Comments
Puja:Will be completed in scope
P1

QR code generation for ETH receive address

1 Comments
Puja:Will be completed in scope
P1

Enhanced transaction history with full details (QuickNode $50/month or Alchemy free tier)

1 Comments
Puja:Will be completed in scope
P1

Transaction confirmation UI (pending/success/failed) via third-party API integration

2 Comments
Puja:Not possible in current scope
Puja:No stages just final state of transaction
P1

Gas fee estimation + adjustable gas (Alchemy RPC method available - need to test, or QuickNode at free tier)

3 Comments
Puja:Not possible in current scope
Puja:Will check with etherun api response
Rich:Moved from DEFER. SoW Page 6 explicitly states: 'Gas Fee Management: Implement dynamic gas fee setting with recommended presets and real-time network condition updates'. This is a contracted deliverable.
P1

Real-time ETH balance updates (requires WebSocket connection via Alchemy/QuickNode)

3 Comments
Puja:Not possible in current scope
Puja:if it's provided by api
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

6. Multi-Asset Portfolio Management

MVP
P1

Basic portfolio view for Convex and Base tokens

2 Comments
Puja:Completed
Puja:Ready for QA
P1

Asset listing by network

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Puja:Ready for QA
P1

Unified portfolio view across ETH, USDC, CRED, CVM, PT using third-party APIs

1 Comments
Puja:Will be completed in scope
P1

Asset filtering by network

2 Comments
Rich:SOW Reference: Page 6
Puja:Will be completed in scope
P1

USD conversion for each asset (CoinGecko or CoinMarketCap API)

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Token icons/logos integration

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Real-time balance updates across all networks (Alchemy/QuickNode WebSocket)

3 Comments
Puja:Not possible in current scope
Puja:if it's provided by api
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Total portfolio value calculation in USD

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Portfolio performance tracking

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

7. Transaction History & Tracking

MVP
P1

Complete transaction list for Convex network

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Transaction detail view for Convex (hash, timestamp, amount, status)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Basic transaction history UI

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

Filter by network (Ethereum/Base/Convex)

1 Comments
Puja:Will be completed in scope
P1

Filter by token type

2 Comments
Rich:SOW Reference: Page 6
Puja:Will be completed in scope
P1

Copy transaction hash functionality

1 Comments
Puja:Will be completed in scope
P1

Search by date or amount

1 Comments
Puja:Will be completed in scope
P1

Export to CSV/PDF functionality

3 Comments
Rich:SOW Reference: Page 6
Puja:Not possible in current scope
Puja:will have in next phase
P1

Advanced transaction analytics

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Transaction status tracking for Ethereum and Base

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Block-explorer links for all networks

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Complete transaction history across all networks (Alchemy/QuickNode)

3 Comments
Puja:Not possible in current scope
Puja:if it's provided by api
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

8. Gas Fee Management

MVP
P1

Basic gas estimation for critical transactions

1 Comments
Puja:Will be completed in scope
P1

Real-time gas estimation for Ethereum/Base (Alchemy RPC method - need to test, or QuickNode free tier)

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Moved from DEFER. SoW Page 6 explicitly states: 'Gas Fee Management: Implement dynamic gas fee setting with recommended presets'. This is a contracted deliverable.
P1

Slow / Normal / Fast gas presets

4 Comments
Rich:SOW Reference: Page 6
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Moved from DEFER. SoW Page 6 explicitly states: 'Gas Fee Management: recommended presets'. This is a contracted deliverable.
P1

Custom gas input option

4 Comments
Rich:SOW Reference: Page 6
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Moved from DEFER. SoW Page 6 explicitly states: 'Gas Fee Management: dynamic gas fee setting'. This is a contracted deliverable.
P1

Gas price display in GWEI and USD

4 Comments
Rich:SOW Reference: Page 6
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Moved from DEFER. SoW Page 6 explicitly states: 'Gas Fee Management: gas price display'. This is a contracted deliverable.
P1

Network congestion indicator

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Moved from DEFER. SoW Page 6 explicitly states: 'Gas Fee Management: real-time network condition updates'. This is a contracted deliverable.
P1

Estimated confirmation time

4 Comments
Rich:SOW Reference: Page 7
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Moved from DEFER. SoW Page 6 explicitly states: 'Gas Fee Management: real-time network condition updates'. This is a contracted deliverable.

9. Network Switching & Multi-Chain Support

MVP
P1

Network selector UI (Ethereum/Base/Convex)

1 Comments
Puja:Will be completed in scope
P1

Current network indicator badge

2 Comments
Rich:SOW Reference: Page 6
Puja:Will be completed in scope
P1

Network-specific asset lists

2 Comments
Rich:SOW Reference: Page 6
Puja:Will be completed in scope
P1

Warning prompts on network switch

2 Comments
Rich:SOW Reference: Page 6
Puja:Will be completed in scope
P1

Automatic network detection (not available in any wallet)

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Cross-chain bridging UI (requires extensive third-party integration)

2 Comments
Puja:Not possible in current scope
Rich:Moved from OOS. SoW Page 7 explicitly states: 'Cross-Chain Bridging: Implement bridging functionality for assets across supported networks'. This is a contracted deliverable.
P1

Advanced network management features

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

10. Custom Token Integration

MVP
P1

Basic custom token addition by contract address

2 Comments
Rich:SOW Reference: Page 6
Puja:Will be completed in scope
P1

Add custom token by contract address with validation

2 Comments
Rich:SOW Reference: Page 6
Puja:Will be completed in scope
P1

Auto-fetch token metadata (name/symbol/decimals) via Alchemy/QuickNode

1 Comments
Puja:Will be completed in scope
P1

Token logo display via third-party token list APIs

3 Comments
Puja:Will be completed in scope
Observer: will have in next phase
Rich:Moved from DEFER. SoW Page 10 explicitly states: 'Custom Token Integration: Token metadata and logos'. This is a contracted deliverable.
P1

Send/receive custom token functionality

2 Comments
Rich:SOW Reference: Page 6
Puja:Will be completed in scope
P1

Hide/remove tokens from portfolio view

3 Comments
Puja:Not possible in current scope
Mike:This is obviouisly necessary in order for custom tokens to be usable. If you have add, the UI needs remove
Puja:checkbox or toggle to remove the custom token

11. Invoicing System

MVP
P1

Integrated Unibee tool for invoicing (as agreed upon)

2 Comments
Puja:Completed
Puja:Ready for QA, implemented Unibee
P1

Comprehensive invoicing backend with PDF generation

2 Comments
Puja:Not possible in current scope
Rich:Moved from OOS. SoW Page 5 explicitly states: 'Invoicing System: Develop comprehensive invoicing backend with PDF generation'. This is a contracted deliverable.
P1

Payment tracking

3 Comments
Rich:SOW Reference: Page 5
Puja:Not possible in current scope
Rich:Moved from OOS. SoW Page 5 explicitly states: 'Invoicing System: payment tracking'. This is a contracted deliverable.
P1

Tax calculation support

3 Comments
Rich:SOW Reference: Page 5
Puja:Not possible in current scope
Rich:Moved from OOS. SoW Page 5 explicitly states: 'Invoicing System: tax calculation support'. This is a contracted deliverable.

12. Affiliate Marketing System

MVP
P1

Magic link authentication for affiliates

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Basic affiliate signup form with unique referral code generation

2 Comments
Puja:Completed
Observer:Ready for QA
P1

CVM-based payment handling

4 Comments
Puja:Not possible in current scope
Mike:Not clear how magic links are supposed to be useful if can't payout rewards?
Observer:will have in next phase, we need to have efficient tracking system
Rich:Moved from DEFER. SoW Page 8 explicitly states: 'Affiliate Marketing: CVM-based payment handling'. This is a contracted deliverable.
P1

Basic Convex Lisp smart contract for affiliate functions

2 Comments
Puja:Not possible in current scope
Rich:Moved from OOS. SoW Page 8 explicitly states: 'Affiliate Marketing: Implement Convex Lisp smart contract for affiliate functions'. This is a contracted deliverable.
P1

Integrate Paisley ID into user sessions with role-based access control (Admin, Manager, Affiliate)

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase, we need to have efficient tracking system
Rich:Moved from DEFER. SoW Page 7 explicitly states: 'Affiliate Marketing: Integrate Paisley ID with role-based access control (Admin, Manager, Affiliate)'. This is a contracted deliverable.
P1

Pixel-based referral click tracking with real-time analytics

3 Comments
Rich:SOW Reference: Page 8
Puja:Not possible in current scope
Puja:Tracking the count of referrals who has becoming the member using paisley id will not go pixel based, reward calculation to the next phase
P1

Enable affiliates to join multiple projects with approval workflow

4 Comments
Rich:SOW Reference: Page 8
Puja:Not possible in current scope
Puja:will have in next phase, we need to have efficient tracking system
Rich:Moved from DEFER. SoW Page 8 explicitly states: 'Affiliate Marketing: Enable affiliates to join multiple projects with approval workflow'. This is a contracted deliverable.
P1

Flexible reward calculation with tiered commission structures

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase, we need to have efficient tracking system
Rich:Moved from DEFER. SoW Page 8 explicitly states: 'Affiliate Marketing: Implement flexible reward calculation logic with tiered commission structures'. This is a contracted deliverable.
P1

Comprehensive reward history tracking with filtering, export, and reconciliation tools

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase, we need to have efficient tracking system
Rich:Moved from DEFER. SoW Page 8 explicitly states: 'Affiliate Marketing: Create comprehensive reward history tracking with filtering, export, and reconciliation tools'. This is a contracted deliverable.
P1

Real-time earnings estimation and payment scheduling

4 Comments
Rich:SOW Reference: Page 8
Puja:Not possible in current scope
Puja:will have in next phase, we need to have efficient tracking system
Rich:Moved from DEFER. SoW Page 8 explicitly states: 'Affiliate Marketing: Develop real-time earnings estimation and payment scheduling'. This is a contracted deliverable.
P1

Referral validation and conversion tracking on smart contract

2 Comments
Puja:Not possible in current scope
Rich:Moved from OOS. SoW Page 8 explicitly states: 'Affiliate Marketing: referral validation and conversion tracking'. This is a contracted deliverable.

13. Calendar & Scheduling System

MVP
P1

User can input any calendar link (as agreed upon)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Calendar backend for freelancers with availability management

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Moved from DEFER. SoW Page 5 explicitly states: 'Calendar Backend: Implement calendar system for freelancers with availability management'. This is a contracted deliverable.
P1

Booking slots and integration with external calendar services (Google Calendar, Outlook)

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Moved from DEFER. SoW Page 5 explicitly states: 'Calendar Backend: booking slots and integration with external calendar services (Google Calendar, Outlook)'. This is a contracted deliverable.
P1

Professional dashboard for freelancers to manage calendar

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Moved from DEFER. SoW Page 5 explicitly states: 'Professional Dashboard: Create unified dashboard for freelancers to manage calendar'. This is a contracted deliverable.
P1

Deep integration with calendar systems (as agreed upon, only calendar link input provided)

3 Comments
Puja:Not possible in current scope
Puja:will have in next phase
Rich:Moved from DEFER. SoW Page 5 explicitly states: 'Calendar Backend: integration with external calendar services'. This is a contracted deliverable.
P1

Stand up Cal.com as Sched.ID

1 Comments
Rich:Added by Rich

14. Token Swap Functionality

MVP
P1

Basic swap UI framework

1 Comments
Puja:Will be completed in scope
P1

Uniswap v3 integration on Base network

3 Comments
Rich:SOW Reference: Page 4 (Success Criteria)
Puja:Will be completed in scope
Rich:Moved from AGREE. SoW Page 4 explicitly states: 'Token swap functionality (USDC ↔ Ethereum via Uniswap v3)'. This is a contracted deliverable.
P1

USDC ↔ ETH swap functionality

3 Comments
Rich:SOW Reference: Page 4 (Success Criteria)
Puja:Will be completed in scope
Rich:Moved from AGREE. SoW Page 4 explicitly states: 'Token swap functionality (USDC ↔ Ethereum via Uniswap v3)'. This is a contracted deliverable.
P1

Slippage settings (0.5%, 1%, 3%, custom)

3 Comments
Puja:Not possible in current scope
Puja:will check with uniswap api response
Rich:Moved from DEFER. SoW Page 4 explicitly states: 'Token swap functionality - slippage control implied'. This is a contracted deliverable.
P1

Swap preview with fee breakdown

3 Comments
Rich:SOW Reference: Page 7
Puja:Not possible in current scope
Rich:Moved from DEFER. SoW Page 4 explicitly states: 'Token swap functionality - preview and fees implied'. This is a contracted deliverable.
P1

Swap confirmation UI with approval flow

2 Comments
Puja:Not possible in current scope
Rich:Moved from DEFER. SoW Page 4 explicitly states: 'Token swap functionality - confirmation flow required'. This is a contracted deliverable.
P1

Swap history tracking

3 Comments
Rich:SOW Reference: Page 8
Puja:Not possible in current scope
Rich:Moved from DEFER. SoW Page 4 explicitly states: 'Token swap functionality - history tracking'. This is a contracted deliverable.
P1

Minimum received calculation

2 Comments
Puja:Not possible in current scope
Rich:Moved from DEFER. SoW Page 4 explicitly states: 'Token swap functionality - minimum received calculation'. This is a contracted deliverable.

15. Address Book / Contact Management

MVP
P1

Add contacts (screen name + addresses)

3 Comments
Rich:SOW Reference: Page 3 (Executive Summary)
Puja:Completed
Observer:Ready for QA
P1

Contact avatars

3 Comments
Rich:SOW Reference: Page 3
Puja:Completed
Observer:Ready for QA
P1

Delete contacts

3 Comments
Rich:SOW Reference: Implied CRUD
Puja:Completed
Observer:Ready for QA
P1

Quick send to contacts

3 Comments
Rich:SOW Reference: Page 3
Puja:Completed
Observer:Ready for QA
P1

Recent contacts saved automatically

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Search contacts functionality

2 Comments
Puja:Will be completed in scope
Observer:Ready for QA
P1

Contact sorting and filtering

1 Comments
Puja:Will be completed in scope
P1

Edit contacts (only delete is implemented)

2 Comments
Puja:Not possible in current scope
Mike:Edit contacts is clearly necessary for users if contacts are meant to be usable. As a general principle, being functional for users is an absolute minimum
P1

Contact import/export

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Contact synchronization across devices

3 Comments
Puja:Not possible in current scope
Mike:Where are contacts stored? Presumably in the database, in which case you get contact sync for free whenever the user logs on?
Puja:will be same for all devices as we are using paisley db
P1

Bulk contact management

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

16. QR Code Features

MVP
P1

Generate QR code for all network addresses

2 Comments
Rich:SOW Reference: Page 5
Puja:Will be completed in scope
P1

Share QR code functionality

2 Comments
Rich:SOW Reference: Page 6
Puja:Will be completed in scope
P1

Save QR as image

1 Comments
Puja:Will be completed in scope
P1

Scan QR code to send (requires camera API integration)

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Advanced QR customization

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

QR code with embedded payment amounts

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

QR includes chain/network information

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

17. Security Features (Not in SOW)

Phase 2 (Hidden)
P1

PIN/password app lock

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

High-value send confirmations (threshold-based)

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Basic suspicious-activity warnings

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Biometric login (Face ID/Fingerprint) - requires native mobile app

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Address whitelist functionality

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Auto-lock settings with time-based triggers

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Advanced fraud detection system

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

18. Fiat-to-Crypto On-Ramp

MVP
P1

Unlimit integration (replaced Stripe)

3 Comments
Rich:SOW Reference: Page 7
Puja:Completed
Observer:Ready for QA
P1

Buy USDC on Base

3 Comments
Rich:SOW Reference: Page 7
Puja:Completed
Observer:Ready for QA
P1

Buy CVM via USDC conversion using Permit function

3 Comments
Rich:SOW Reference: Page 7
Puja:Completed
Observer:Ready for QA
P1

KYC workflow via DIDIT (integrated during membership buying)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Payment method selection (tested with sandbox)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Purchase confirmation with fee breakdown (sandbox tested)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Buy ETH directly

2 Comments
Rich:SOW Reference: Page 7
Puja:Will be completed in scope
P1

Purchase history (not provided in Unlimit sandbox)

3 Comments
Puja:Will be completed in scope
Observer:QA has sandbox unlimit, need to check history on unlimit prod
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

19. Personal Token (PT) Operations

MVP
P1

Create PT with custom parameters

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

Set PT parameters (name, symbol, supply, etc.)

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

Mint PT

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Send PT to other users

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

PT balance display

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

PT transaction history

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

Basic PT metadata

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Enhanced PT metadata display

2 Comments
Puja:Will be completed in scope
Puja:Need to see what details will be showing, as we are showing all details in the transaction history

20. PT Redemption System

MVP
P1

Redeem PT for services

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

Redemption request UI

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

Escrow functionality (PT locked until acceptance)

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

Acceptance/rejection workflow

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

Notifications for redemption events

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Redemption history with on-chain process states

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Rating system for completed redemptions

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

On-platform dispute/appeal system (as agreed, disputes handled offline via email)

2 Comments
Puja:Will be completed in scope
Observer:Ready for QA

21. PAI & CVM Token Operations (PAI replaced with CRED)

MVP
P1

CRED send to Contact IDs (replaced PAI)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

CVM send functionality

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

CRED and CVM balance tracking

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Buy CVM from USDC via Permit function

3 Comments
Rich:SOW Reference: Page 7
Puja:Completed
Observer:Ready for QA
P1

CVM ↔ CRED conversion (not provided by Convex)

4 Comments
Puja:Not possible in current scope
Mike:This is possible on Convex (Torus buy/sell CRED<->CVM)
Puja:defer for PAI and CRED live or on testnet
Rich:Moved from DEFER. SoW Page 7 explicitly states: 'PAI Conversion: Implement CVM to PAI conversion system'. This is a contracted deliverable.
P1

Real-time exchange rates (marked as Not in Scope)

4 Comments
Puja:Not possible in current scope
Mike:Again this is supported by Convex, it's a 1-line query
Puja:defer for PAI and CRED live or on testnet
Rich:Moved from DEFER. SoW Page 7 explicitly states: 'PAI Conversion: real-time exchange rates'. This is a contracted deliverable.
P1

Fee previews (not possible in Convex architecture)

4 Comments
Puja:Not possible in current scope
Mike:Again possible on Convex via API
Puja:defer for PAI and CRED live or on testnet
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

CVM send with automatic conversion

4 Comments
Puja:Not possible in current scope
Mike:What does this mean? Automatic conversion to what?
Puja:defer for PAI and CRED live or on testnet
Rich:Moved from DEFER. SoW Page 6 explicitly states: 'CVM Token Handling: Send CVM tokens with integrated conversion rates and fee calculations'. This is a contracted deliverable.

22. Wallet Interface Design

MVP
P1

Modern, clean UI implementation

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Responsive design (mobile/tablet/desktop)

3 Comments
Rich:SOW Reference: Page 7
Puja:Completed
Observer:Ready for QA
P1

Tailwind CSS framework

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Loading states for async operations

3 Comments
Rich:SOW Reference: Page 7
Puja:Completed
Observer:Ready for QA
P1

Error messages with user-friendly text

2 Comments
Rich:SOW Reference: Page 7
Puja:Completed
P1

Success animations for completed actions

1 Comments
Puja:Completed
P1

Basic cross-browser support

1 Comments
Puja:Completed
P1

Comprehensive cross-browser testing (Chrome, Firefox, Safari, Edge)

2 Comments
Puja:Will be completed in scope
Puja:Check AA Compliance, chrome tool LightHouse
P1

Advanced animations beyond basic success/loading states

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Full accessibility audit and certification

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

23. Performance Optimization

MVP
P1

Basic performance optimization

2 Comments
Puja:Completed
Puja:Ready for QA
P1

Smooth animations for core interactions

2 Comments
Puja:Completed
Puja:Ready for QA
P1

Minimal re-renders in React components

2 Comments
Puja:Completed
Puja:Ready for QA
P1

Advanced state management optimization

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Service worker implementation for offline functionality

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

CDN integration for static assets

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Load time optimization to <3 seconds

2 Comments
Rich:SOW Reference: Page 7
Puja:Not possible in current scope
P1

Optimized asset loading (lazy loading, code splitting)

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Efficient API batching for multiple requests

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Progressive transaction loading for large histories

2 Comments
Puja:Not possible in current scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Fully functional landing page design with modern aesthetics

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Custom designed icons, images, and supporting pages (About, Contact Us, FAQ)

2 Comments
Puja:Completed
Puja:Ready for QA
P1

Faux time token flow implementation

2 Comments
Puja:Completed
Observer:Ready for QA
P1

MercurJs integration for digital assets marketplace (agreed for PT marketplace only)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

PAI → WD → CRED token replacement and migration (accepted multiple token changes)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Custom smart contract development (originally agreed Mike would write all contracts, but our team wrote them with Mike's assistance)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Soulbound NFT UI and smart contract implementation

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Enhanced contact management system beyond basic requirements

3 Comments
Puja:Completed
Observer:which fields need to be updated - other than email and Id
Puja:Avtar and Screen name editable
P1

Convex-specific transaction history and analytics

2 Comments
Puja:Completed
Observer:Ready for QA
P1

CRED token operations (complete replacement of PAI token)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Full Convex ecosystem integration

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Enhanced user onboarding flow

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Alchemy or QuickNode (for Ethereum/Base operations):

2 Comments
Puja:Completed
Puja:will go with Alchemy, we needed access
P1

Gas fee estimation (Alchemy: free/need to test, QuickNode: free tier)

3 Comments
Puja:Completed
Puja:if it's provided by api
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Transaction history (Alchemy: free tier, QuickNode: $50/month)

1 Comments
Puja:Completed
P1

ERC-20 token operations (Alchemy: free tier)

1 Comments
Puja:Completed
P1

Transaction status and confirmations (QuickNode: $50/month)

1 Comments
Puja:Completed
P1

Real-time balance updates via WebSocket

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Puja:if it's provided by api
P1

Token List APIs (for custom tokens):

1 Comments
Puja:Completed
P1

Token metadata and logos

3 Comments
Puja:Completed
Puja:Token Metadata will be added but logos will have in next phase
Rich:Moved from DEFER. SoW Page 10 explicitly states: 'Token metadata and logos'. This is a contracted deliverable.
P1

Token verification status

1 Comments
Puja:Completed
P1

Token contract validation

1 Comments
Puja:Completed
P1

Uniswap V3 SDK (for swap functionality):

1 Comments
Puja:Completed
P1

Swap quotes and routing

1 Comments
Puja:Completed
P1

Liquidity pool data

3 Comments
Puja:Completed
SD:dex integration not in scope
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Slippage calculation

3 Comments
Puja:Completed
Puja:will have in next phase
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

⚠️ = Partially implemented or pending completion

2 Comments
Puja:Completed
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

❌ = Not implemented (requires third-party API or marked Not in Scope)

2 Comments
Puja:Completed
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

4. Multi-Chain Wallet Operations — BASE BLOCKCHAIN

MVP
P1

Base network integration

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

USDC send/receive on Base

3 Comments
Rich:SOW Reference: Page 4-6
Puja:Completed
Observer:Ready for QA
P1

ETH send/receive on Base

3 Comments
Rich:SOW Reference: Page 4-6
Puja:Completed
Observer:Ready for QA
P1

Base USDC with Permit function to buy CVM

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Base transaction history using third-party API (QuickNode free tier)

1 Comments
Puja:Will be completed in scope
P1

Base address QR code generation

2 Comments
Rich:SOW Reference: Page 5
Puja:Will be completed in scope
P1

Network switching UI between Ethereum ↔ Base

1 Comments
Puja:Will be completed in scope
P1

Clear network indication in UI

1 Comments
Puja:Will be completed in scope
P1

Base gas fee handling and estimation (requires RPC provider integration)

3 Comments
Puja:Not possible in current scope
Puja:based on API response
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Real-time Base transaction status updates

4 Comments
Puja:Not possible in current scope
Observer:How does user see transaction confirmation?
Puja:based on API response
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

Enhanced Base transaction details and history

3 Comments
Puja:Not possible in current scope
Puja:based on API response, if we get more information from api
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.

5. Multi-Chain Wallet Operations — CONVEX VM

MVP
P1

Convex account creation

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

CRED Token balance display (replaced PAI)

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

CRED Token send functionality (Convex accounts / Paisley Contact IDs)

2 Comments
Puja:Completed
Observer:Ready for QA
P1

CVM balance display

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

CVM send functionality

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

PT (Personal Token) balance display

2 Comments
Puja:Completed
Observer:Ready for QA
P1

PT send functionality

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

Convex transaction history

3 Comments
Rich:SOW Reference: Page 6
Puja:Completed
Observer:Ready for QA
P1

Integration with Convex API

2 Comments
Puja:Completed
Observer:Ready for QA
P1

Enhanced transaction history filtering

1 Comments
Puja:Will be completed in scope
P1

Transaction detail views with timestamps

4 Comments
Rich:SOW Reference: Page 6
Puja:Will be completed in scope
Puja:we are using server timestamp
Observer:Ready for QA
P1

Improved error handling for Convex operations

2 Comments
Puja:Will be completed in scope
Puja:based on error code, dialog text for reasons
P1

Fee previews (not possible in Convex architecture)

4 Comments
Puja:Not possible in current scope
Mike:This is possible via API call on Convex (run a query to get estimate)
Puja:will be possible when mike provides query
Rich:Not explicitly in SoW. This feature was extrapolated from general requirements but not contracted.
P1

CVM ↔ PAI/CRED conversion (not provided by Convex)

3 Comments
Puja:Not possible in current scope
Puja:defer for PAI and CRED live or on testnet
Rich:Moved from DEFER. SoW Page 7 explicitly states: 'PAI Conversion: Implement CVM to PAI conversion system'. This is a contracted deliverable.
P1

Real-time exchange rates for Convex tokens

3 Comments
Puja:Not possible in current scope
Puja:defer for PAI and CRED live or on testnet, related to torus dex
Rich:Moved from DEFER. SoW Page 7 explicitly states: 'PAI Conversion: real-time exchange rates for Convex tokens'. This is a contracted deliverable.