Appearance
Notifications
Overview
The platform sends notifications to keep users informed about activity that involves them. Each notification is delivered as a push notification to the recipient's registered devices and is also stored so it can be reviewed at any time. Notifications are either simple alerts or requests that require a response — such as a transfer, a chain access request, or a showroom share invitation.
Fields
| Field | What it represents |
|---|---|
| Sender | The user whose action triggered the notification; may be the system for automated alerts |
| Recipient | The user who receives the notification |
| Title | Short heading displayed in the notification |
| Message | Body text providing context |
| Type | Whether this is a plain alert or a request requiring a response |
| Related object | The entity the notification refers to — a card, transfer, chain, showroom, post, or message |
| Read | Whether the recipient has opened the notification |
Relations
Notification Types
Registration
| Trigger | Recipient | Type |
|---|---|---|
| User completes registration | New user | Alert |
Social
| Trigger | Recipient | Type |
|---|---|---|
| Another user follows the recipient | Followed user | Alert |
| Another user likes the recipient's post | Post owner | Alert |
| Another user comments on the recipient's post | Post owner | Alert |
| Another user likes the recipient's comment | Comment owner | Alert |
| A comment mentions the recipient by name | Mentioned user | Alert |
Cards
| Trigger | Recipient | Type |
|---|---|---|
| User creates a new card | Creator (self) | Alert |
Chains (see Chains)
| Trigger | Recipient | Type |
|---|---|---|
| User requests chain access to a card | Card owner | Request |
| User requests chain access to a card | Requester (self, copy) | Request |
| Card owner accepts a chain request | Original requester | Alert |
| Card owner declines a chain request | Original requester | Alert |
Transfers (see Transfer)
| Trigger | Recipient | Type |
|---|---|---|
| User initiates a card transfer | Proposed recipient | Request |
| User initiates a card transfer | Sender (self, copy) | Request |
| Proposed recipient accepts the transfer | Original sender | Alert |
| Proposed recipient declines the transfer | Original sender | Alert |
| A transfer fails due to a processing error | Other party | Alert |
Showrooms (see Showrooms)
| Trigger | Recipient | Type |
|---|---|---|
| User creates a new showroom | Creator (self) | Alert |
| User invites another to a shared showroom | Invited user | Request |
| User invites another to a shared showroom | Inviting user (self, copy) | Request |
| Invited user accepts a showroom invitation | Inviting user | Alert |
| Invited user declines a showroom invitation | Inviting user | Alert |
| Owner closes a shared showroom | Each invited participant | Alert |
Chat (see Chat)
| Trigger | Recipient | Type |
|---|---|---|
| User sends a chat message | Message recipient | Request |
Verification (see Verification)
| Trigger | Recipient | Type |
|---|---|---|
| User submits an identity or artist verification request | Submitting user (self) | Alert |
| Back-office updates the status of a verification request | Applicant | Alert |
Coins (see Coins)
| Trigger | Recipient | Type |
|---|---|---|
| A paid action fails because the user's coin balance is insufficient | User | Alert |
| User completes a coin recharge purchase | User | Alert |
Business Rules
- Notifications are delivered as push notifications to the recipient's registered devices and are also stored for later review.
- Request-type notifications (chain access, transfer, showroom share, chat message) require a response. When the request is resolved, the original notification is marked as processed.
- When a user initiates a transfer, a chain request, or a showroom share invitation, they also receive a copy of the notification so they can track their own pending requests.
- A chat message notification is not delivered if the recipient has blocked the sender (see Blocking).
States
| State | What it means |
|---|---|
| Unread | The recipient has not yet opened the notification |
| Read | The recipient has opened the notification |
| Checked | The notification has been acknowledged — happens automatically for self-confirmations and after a request is resolved |
Constraints
- A notification cannot be delivered to a user who has blocked the sender (applies to chat notifications).
- A notification cannot exist without both a sender and a recipient.