Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@tonconnect/sdk
Advanced tools
⚠️ TonConnect is currently in beta testing. Use it at your own risk.
Use it to connect your app to TON wallets via TonConnect protocol. You can find more details and the protocol specification in the docs. See the example of sdk usage here.
Add the script to your HTML file:
<script src="https://unpkg.com/@tonconnect/sdk@latest/dist/tonconnect-sdk.min.js"></script>
ℹ️ If you don't want auto-update the library, pass concrete version instead of latest
, e.g.
<script src="https://unpkg.com/@tonconnect/sdk@0.0.34/dist/tonconnect-sdk.min.js"></script>
You can find TonConnect
in global variable TonConnectSDK
, e.g.
<script>
const connector = new TonConnectSDK.TonConnect();
</script>
npm i @tonconnect/sdk
import TonConnect from '@tonconnect/sdk';
const connector = new TonConnect();
connector.restoreConnection();
App needs to have its manifest to pass meta information to the wallet. Manifest is a JSON file named as tonconnect-manifest.json
following format:
{
"url": "<app-url>", // required
"name": "<app-name>", // required
"iconUrl": "<app-icon-url>", // required
"termsOfUseUrl": "<terms-of-use-url>", // optional
"privacyPolicyUrl": "<privacy-policy-url>" // optional
}
Best practice is to place the manifest in the root of your app, e.g. https://myapp.com/tonconnect-manifest.json
. It allows the wallet to handle your app better and improve the UX connected to your app.
Make sure that manifest is available to GET by its URL.
If your manifest placed not in the root of your app, you can specify its path:
const connector = new TonConnect({ manifestUrl: 'https://myApp.com/assets/tonconnect-manifest.json' });
connector.onStatusChange(
walletInfo => {
// update state/reactive variables to show updates in the ui
}
);
TonConnect is build to support different wallets. You can fetch all supported wallets list and show a custom wallet selection dialog for user
const walletsList = await connector.getWallets();
/* walletsList is
{
name: string;
imageUrl: string;
tondns?: string;
aboutUrl: string;
universalLinkBase?: string;
bridgeUrl?: string;
jsBridgeKey?: string;
injected?: boolean; // true if this wallet is injected to the webpage
embedded?: boolean; // true if the dapp is opened inside this wallet's browser
}[]
*/
const walletConnectionSource = {
universalLinkBase: 'https://app.mycooltonwallet.com',
bridgeURL: 'https://bridge.mycooltonwallet.com,'
}
const universalLink = connector.connect(walletConnectionSource);
Then you have to show this link to user as QR code, or use it as a deeplink. You will receive an update in connector.onStatusChange
when user approves connection in the wallet
const walletConnectionSource = {
jsBridgeKey: 'tonkeeper'
}
connector.connect(walletConnectionSource);
You will receive an update in connector.onStatusChange
when user approves connection in the wallet
if (!connector.connected) {
alert('Please connect wallet to send the transaction!');
}
const transaction = {
valid_until: 1658253458,
messages: [
{
address: "0:412410771DA82CBA306A55FA9E0D43C9D245E38133CB58F1457DFB8D5CD8892F",
amount: "20000000",
initState: "base64bocblahblahblah==" // just for instance. Replace with your transaction initState or remove
},
{
address: "0:E69F10CC84877ABF539F83F879291E5CA169451BA7BCE91A37A5CED3AB8080D3",
amount: "60000000",
payload: "base64bocblahblahblah==" // just for instance. Replace with your transaction payload or remove
}
]
}
try {
const result = await connector.sendTransaction(transaction);
// you can use signed boc to find the transaction
const someTxData = await myAppExplorerService.getTransaction(result.boc);
alert('Transaction was sent successfully', someTxData);
} catch (e) {
if (e instanceof UserRejectedError) {
alert('You rejected the transaction. Please confirm it to send to the blockchain');
} else {
alert('Unknown error happened', e);
}
}
To authorize user in your backend with TonConnect you can use following schema:
connector.connect(walletConnectionSource, { tonProof: "<your-fetched-payload>" });
Note that you can use tonProof
only with connector.connect()
method. This feature is not available in connector.restoreConnection()
.
connector.onStatusChange(wallet => {
if (!wallet) {
return;
}
const tonProof = wallet.connectItems?.tonProof;
if (tonProof) {
if ('proof' in tonProof) {
// send proo to your backend
// e.g. myBackendCheckProof(tonProof.proof, wallet.account);
return;
}
console.error(tonProof.error);
}
});
Account
contains the walletStateInit
property which can be helpful for your backend to get user's public key if user's wallet contract doesn't support corresponding get method.localStorage
and use it to access to auth-required endpoints. Client should delete the token when user disconnects the wallet.See an example of a dapp using backend authorization.
See an example of the dapp backend.
You can use the SDK in frontend apps and in backend apps created with NodeJS.
npm i @tonconnect/sdk
When you use the SDK in backend, you have to pass manifestUrl
and IStorage
implementation to the TonConnect constructor.
import TonConnect from '@tonconnect/sdk';
const storage: IStorage = <your implementation of the IStorage>
const connector = new TonConnect({ manifestUrl, storage });
Your storage should implement following interface:
export interface IStorage {
setItem(key: string, value: string): Promise<void>;
getItem(key: string): Promise<string | null>;
removeItem(key: string): Promise<void>;
}
See details about IStorage in the API documentation.
Other steps are the same as for browser apps.
FAQs
Use it to connect your app to TON wallets via TonConnect protocol. You can find more details and the protocol specification in the [docs](https://docs.ton.org/develop/dapps/ton-connect/overview). See the example of sdk usage [here](https://github.com/ton
The npm package @tonconnect/sdk receives a total of 26,728 weekly downloads. As such, @tonconnect/sdk popularity was classified as popular.
We found that @tonconnect/sdk demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.