Skip to content

Commit d254752

Browse files
committed
remove trailing whitespaces
Signed-off-by: master_jedy <[email protected]>
1 parent 41c0c96 commit d254752

File tree

1 file changed

+2
-2
lines changed
  • pages/price-feeds/use-real-time-data

1 file changed

+2
-2
lines changed

pages/price-feeds/use-real-time-data/ton.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -132,8 +132,8 @@ There are typically two main scenarios: either you call a method supplying TON,
132132
- **TON proxy**: `User → Pyth → EVAA Master → ... (further processing)`
133133
Use this method if you only need to send TON to your contract or simply call a contract method, without involving jettons.
134134

135-
- **Jetton on-chain getter**: `User → Jetton Wallet → EVAA Master → Pyth → EVAA Master → ... (further processing)`
136-
In this pattern, your contract first receives the Pyth data, then forwards it to the Pyth contract for validation, and finally gets the validated prices back.
135+
- **Jetton on-chain getter**: `User → Jetton Wallet → EVAA Master → Pyth → EVAA Master → ... (further processing)`
136+
In this pattern, your contract first receives the Pyth data, then forwards it to the Pyth contract for validation, and finally gets the validated prices back.
137137
This approach is useful when you want to transfer jettons to your contract while also providing price data.
138138
<Callout type="info" emoji="ℹ️">
139139
This data flow is simplified. In reality, the "Jetton Wallet" step consists of a sequence of transactions: User's jetton wallet → EVAA jetton wallet → EVAA master. These internal details are omitted here to highlight the main flow and the interaction with Pyth.

0 commit comments

Comments
 (0)