Skip to content

Flow docs: in-chat token transfers end to end #636

Closed

Description

@codebestia

Branch: Open your PR against dev. PRs targeting main are closed automatically.

Description:
Write docs/flows/token-transfer.md: one sequence from "user clicks send tokens in a chat" to "both users see a confirmed transfer card", spanning apps/web (TransferCard.tsx, Freighter signing, lib/soroban.ts), the token_transfer contract, POST/GET /conversations/:id/transfers, the tokenTransfers table, and the Stellar listener's reconciliation.

Acceptance criteria:

  • A sequence diagram covering client, wallet, Soroban RPC, contract, backend, database and listener
  • States which record is the source of truth — the on-chain event or the backend row — and how the two are reconciled when they disagree
  • Documents every failure point (user rejects in Freighter, transaction fails, backend POST fails after an on-chain success) and what the user sees for each
  • Documents what transfer metadata the backend can see, given that message content is end-to-end encrypted

Activity

  1. tyson-mill commented on Oct 19, 2026

    @tyson-mill

    @tyson-mill has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Please assign this issue to me.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @tyson-mill to this issue.

  2. Depo-dev commented on Oct 20, 2026

    @Depo-dev
    Contributor

    @Depo-dev has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello team.

    I’m Depodev, a software engineer with a strong background in building scalable systems and contributing to open-source projects. I’ve taken some time to go through the repository and understand the current implementation, and I’m clear on the issue, its context, and the expected outcome.

    I’d love to work on this and take ownership of the fix. I’m confident I can cleanly resolve it while keeping everything aligned with the existing codebase and ensuring all criteria are met. Would appreciate being assigned to this issue.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Depo-dev to this issue.

  3. drips-wave commented on Oct 20, 2026

    @drips-wave

    Congratulations, @Depo-dev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @Depo-dev: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  4. github-actions commented on Oct 20, 2026

    @github-actions

    Closed by #649, merged into dev.

  5. drips-wave commented on Oct 20, 2026

    @drips-wave

    This issue has been completed by @Depo-dev as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @Depo-dev: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programblockchaindocumentationImprovements or additions to documentation

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions