benduran ab0cf6f7d8 chore: updated gitignore to excluse the built dist/ folder		3 周之前
..
contracts	5e14d51ad3 fix: handle remaining data in read_and_store_large_data when size > input	3 月之前
scripts	1b5195aa0a fix: run turbo fix	8 月之前
tests	18a9b76b88 Revert "deleting extraneous tests for greater numbers of price feeds"	3 月之前
wrappers	1b5195aa0a fix: run turbo fix	8 月之前
.prettierignore	b1dc4c27f5 chore: move prettier to individual packages & upgrade prettier	8 月之前
README.md	7bf23f24b8 add comments and ignore bounced messages (#2151)	11 月之前
jest.config.ts	e82158d82f feat(target_chains/ton): wormhole contract (#1814)	1 年之前
package.json	ab0cf6f7d8 chore: updated gitignore to excluse the built dist/ folder	3 周之前
tsconfig.build.json	928aa4bb6f chore: updated tsconfig.build.json files	3 周之前
tsconfig.json	fe92275443 chore: migrated all package.json and tsconfig files to a single, modern standard	3 周之前

pyth

Project structure

contracts - source code of all the smart contracts of the project and their dependencies.
wrappers - wrapper classes (implementing Contract from ton-core) for the contracts, including any [de]serialization primitives and compilation functions.
tests - tests for the contracts.
scripts - scripts used by the project, mainly the deployment scripts.

How to use

Build

npx blueprint build or yarn blueprint build

Test

npx blueprint test or yarn blueprint test

Deploy or run another script

First, visit TON Center and register to get an API key to bypass rate limits. Replace <YOUR-API-KEY> with the API key you obtained from TON Center. <CUSTOM-TYPE> is either testnet or mainnet. <CHAIN-ID> is the chain ID of the chain you want to deploy to.

Then run:

CHAIN_ID=<CHAIN-ID> npx blueprint run --custom https://testnet.toncenter.com/api/v2/jsonRPC --custom-version v2 --custom-type <CUSTOM-TYPE> --custom-key <YOUR-API-KEY>

Add a new contract

npx blueprint create ContractName or yarn blueprint create ContractName

Important Note on Message Handling

When using the Pyth price feed in the recommended flow (User/App -> Pyth -> Protocol), be aware that:

Security Warning ⚠️

CRITICAL: Integrators MUST validate the sender address in their receive function to ensure messages are coming from the Pyth Oracle contract. Failure to do so could allow attackers to:

Send invalid price responses
Impersonate users via the sender_address and custom_payload fields
Potentially drain the protocol

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.
This could be significant when dealing with large amounts of TON (e.g., in DeFi operations).
Integrators should implement proper error handling and refund mechanisms in their applications.

README.md