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 Proxy TON standard specs #161

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

dariotarantini
Copy link

No description provided.

@giadan89
Copy link

Good

@dariotarantini dariotarantini marked this pull request as ready for review June 27, 2024 09:28
@peymanp966
Copy link

**Otherwise should do:**

1. increase internal jetton balance by `ton_amount`
2. the receiver's jetton-wallet send message to `owner` address with unused gas attached and with the TEP-74 `transfer_notification` message body
Copy link

Choose a reason for hiding this comment

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

it’s not very clear what amount should be in transfer_notification. equal to ton_amount?

**Otherwise should do:**

1. decrease ton balance on sender wallet by `amount`
2. send a message to receiver with the `ton_transfer` layout described above
Copy link

Choose a reason for hiding this comment

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

it’s not very clear what ton_amount should be in ton_transfer. equal to amount in transfer?

Choose a reason for hiding this comment

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

ton_amount is the amount of ton to be tokenized, this amount is sent in transfer_notification, the rest of the ton is used as gas (of course tx value must be greater than specified ton_amount or it will throw)

1. decrease ton balance on sender wallet by `amount`
2. send a message to receiver with the `ton_transfer` layout described above

#### 3. `internal_deploy`
Copy link

Choose a reason for hiding this comment

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

why do we need internal deploy if jetton deploys on demand in decentralized manner?

Choose a reason for hiding this comment

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

pton is not a traditional jetton, the end-user should never interact with it directly, rather the purpose of pton is to automatically tokenize native ton and send std notification to the owner that is some kind of contract with general jetton notification logic

so the user sends ton not to their pton wallet but directly to the target contract's pton wallet, so there's no auto-deploy

Copy link

Choose a reason for hiding this comment

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

I understand. But you can simple attach stateInit to ton_transfer message and wallet will be deployed. So why do we need internal deploy?

Copy link

@sikvelsigma sikvelsigma Jul 24, 2024

Choose a reason for hiding this comment

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

because ton_transfer is not an internal operation to pton wallets, users send their ton_transfer msgs to interact with it and the wallet sends ton_transfer when it unwraps pton to ton

pton is not a standard jetton

@dariotarantini
Copy link
Author

This specs is still WIP, do not merge until we confirm it

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.

6 participants