[86c6kqcw7]: Add transaction message to token transfer - #177
Merged
conxtantyn merged 36 commits intoFeb 5, 2026
Merged
Conversation
conxtantyn
force-pushed
the
constantine/feat/transaction-message
branch
from
February 3, 2026 12:39
4ca25fc to
5d7e844
Compare
github-actions
Bot
added
build
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
This PR introduces support for optional transaction messages when transferring Peer Tokens (PT) between users. The goal is to improve transparency and context in wallet transactions, allowing users to better understand the intent behind transfers. The feature is designed to be lightweight, with balance preview logic handled on the frontend for now.
Description
Adds an optional message field to PT transfer transactions and persists it alongside the transaction record. The backend validates and processes transfers as usual, returning success or error states. Transaction history responses now include the message when present, making it visible to both sender and recipient. No balance calculations are performed server-side for preview; the frontend derives remaining balance from the current balance response.
Links