Data Model: Crypto Wallet
Purpose: The Crypto Wallet entity records the blockchain address associated with a Profile. The address can hold and transfer tokens for RWA interests.
Fields/Attributes
| Name | Type | Description | Validation Rules |
|---|---|---|---|
id | Unique Identifier | The primary internal system ID for the wallet record. | • Required • System-generated |
profile_id | Foreign Key | A reference to the Profile that owns this wallet address. | • Required, Unique |
address | Text | The unique, public blockchain address of the wallet (e.g., 0x...), public key. | • Required, Unique • Must be a valid EVM address |
balance | Decimal | The balance of the USDC currency. Read-only, fetched from the blockchain. | • Read-only • System-managed |
status | Choice | The verification or operational status of the wallet (e.g., created, verified). | • Read-only • System-managed |
created_at | Timestamp | The date and time the wallet record was created in our system. | • Read-only |
updated_at | Timestamp | The date and time the wallet record was changed. | • Read-only |
Key Relationships
Profile: Each
Crypto Walletis owned by exactly one Profile (a one-to-one relationship).EVM Transfers: A
Crypto Walletcan be the sender or receiver in many EVM Transfer records (a one-to-many relationship).
Global Business Rules
A
Crypto Walletrecord can only be created for a Profile with a VERIFIED KYC status.Token holdings (e.g., "100 tokens of 'Fund A'") are not stored in this model but are queried in real-time from the respective EVM Contract on the blockchain.
Auditing & Event History
The system records significant actions or changes involving a Crypto Wallet as immutable entries in the system-wide EventLog.