Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add comments and ignore bounced messages #2151

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

add comments and ignore bounced messages #2151

wants to merge 1 commit into from

Conversation

cctdaniel
Copy link
Contributor

No description provided.

Copy link

vercel bot commented Nov 28, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
api-reference ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 28, 2024 6:27am
proposals ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 28, 2024 6:27am
staking ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 28, 2024 6:27am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
component-library ⬜️ Ignored (Inspect) Visit Preview Nov 28, 2024 6:27am
insights ⬜️ Ignored (Inspect) Visit Preview Nov 28, 2024 6:27am


### Message Bouncing Behavior

- If the target protocol bounces the message (e.g., due to invalid custom payload or other errors), the forwarded TON will remain in the Pyth contract and will not be automatically refunded to the original sender.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can't we bounce back?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to handle bounced messages and return funds to the original sender, we need to:

  • store the sender's address when receiving the initial request
  • add a bounce handling function that checks for bounced messages and refunds the original sender

its not as straightforward but if you think its worth it then we can consider implementing this

Copy link
Collaborator

@ali-bahjati ali-bahjati Nov 29, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oof it seems pretty complicated. let's skip it.

Copy link
Collaborator

@ali-bahjati ali-bahjati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I don't know how much of a lift it is to bounce backwards to refund but it's a nice feature to add.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants