Skip to content

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

FieldWhat it represents
SenderThe user whose action triggered the notification; may be the system for automated alerts
RecipientThe user who receives the notification
TitleShort heading displayed in the notification
MessageBody text providing context
TypeWhether this is a plain alert or a request requiring a response
Related objectThe entity the notification refers to — a card, transfer, chain, showroom, post, or message
ReadWhether the recipient has opened the notification

Relations

Notification Types

Registration

TriggerRecipientType
User completes registrationNew userAlert

Social

TriggerRecipientType
Another user follows the recipientFollowed userAlert
Another user likes the recipient's postPost ownerAlert
Another user comments on the recipient's postPost ownerAlert
Another user likes the recipient's commentComment ownerAlert
A comment mentions the recipient by nameMentioned userAlert

Cards

TriggerRecipientType
User creates a new cardCreator (self)Alert

Chains (see Chains)

TriggerRecipientType
User requests chain access to a cardCard ownerRequest
User requests chain access to a cardRequester (self, copy)Request
Card owner accepts a chain requestOriginal requesterAlert
Card owner declines a chain requestOriginal requesterAlert

Transfers (see Transfer)

TriggerRecipientType
User initiates a card transferProposed recipientRequest
User initiates a card transferSender (self, copy)Request
Proposed recipient accepts the transferOriginal senderAlert
Proposed recipient declines the transferOriginal senderAlert
A transfer fails due to a processing errorOther partyAlert

Showrooms (see Showrooms)

TriggerRecipientType
User creates a new showroomCreator (self)Alert
User invites another to a shared showroomInvited userRequest
User invites another to a shared showroomInviting user (self, copy)Request
Invited user accepts a showroom invitationInviting userAlert
Invited user declines a showroom invitationInviting userAlert
Owner closes a shared showroomEach invited participantAlert

Chat (see Chat)

TriggerRecipientType
User sends a chat messageMessage recipientRequest

Verification (see Verification)

TriggerRecipientType
User submits an identity or artist verification requestSubmitting user (self)Alert
Back-office updates the status of a verification requestApplicantAlert

Coins (see Coins)

TriggerRecipientType
A paid action fails because the user's coin balance is insufficientUserAlert
User completes a coin recharge purchaseUserAlert

Business Rules

  1. Notifications are delivered as push notifications to the recipient's registered devices and are also stored for later review.
  2. 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.
  3. 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.
  4. A chat message notification is not delivered if the recipient has blocked the sender (see Blocking).

States

StateWhat it means
UnreadThe recipient has not yet opened the notification
ReadThe recipient has opened the notification
CheckedThe 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.