
Security News
How Enterprise Security Is Adapting to AI-Accelerated Threats
Socket CTO Ahmad Nassri discusses why supply chain attacks now target developer machines and what AI means for the future of enterprise security.
ton-contract-executor
Advanced tools
This library allows you to run Ton Virtual Machine locally and execute contract. That allows you to write & debug & fully test your contracts before launching them to the network.
TON Contract executor allows you to:
Basically you can develop, debug, and fully cover your contract with unit-tests fully locally without deploying it to the network
yarn add ton-contract-executor
This package internally uses original TVM which runs on actual validator nodes to execute smart contract. TVM build to WASM so this library could be used on any platform. We also added some layer of abstraction on top of original TVM to allow it to run contracts via some JSON configurations (those changes could be found here)
Usage is pretty straightforward: firstly you should create instance of SmartContract. You could think of SmartContract as an existing deployed smart contract with which you can communicate.
Creating SmartContract from FunC source code:
import { SmartContract } from "ton-contract-executor";
import { Cell } from "ton";
async function main() {
const source = `
() main() {
;; noop
}
int sum(int a, int b) method_id {
return a + b;
}
`
let contract = await SmartContract.fromFuncSource(
source, // String with FunC source code of contract
new Cell() // Data Cell (empty Cell in this case)
)
}
In some cases it's useful to create SmartContract from existing precompiled code Cell & data cell. For example if you need to debug some existing contract from network.
Here is an example of creating local copy of existing wallet smart contract from the network deployed at EQD4FPq-PRDieyQKkizFTRtSDyucUIqrj0v_zXJmqaDp6_0t address and getting it's seq:
import {Address, Cell, TonClient} from "ton";
import {SmartContract} from "ton-contract-executor";
const contractAddress = Address.parse('EQD4FPq-PRDieyQKkizFTRtSDyucUIqrj0v_zXJmqaDp6_0t')
let client = new TonClient({
endpoint: 'https://toncenter.com/api/v2/jsonRPC'
})
async function main() {
let state = await client.getContractState(contractAddress)
let code = Cell.fromBoc(state.code!)[0]
let data = Cell.fromBoc(state.data!)[0]
let wallet = await SmartContract.fromCell(code, data)
let res = await wallet.invokeGetMethod('seqno', [])
console.log('Wallet seq is: ', res.result[0])
}
Once you have created instance of SmartContract you can start to interact with it.
You can invoke any get method on contract using invokeGetMethod function:
import { SmartContract } from "ton-contract-executor";
import { Cell } from "ton";
async function main() {
const source = `
() main() {
;; noop
}
int sum(int a, int b) method_id {
return a + b;
}
`
let contract = await SmartContract.fromFuncSource(source, new Cell())
let res = await contract.invokeGetMethod('sum', [
// argument a
{ type: 'int', value: '1' },
// argument b
{ type: 'int', value: '2' },
])
console.log('1 + 2 = ', res.result[0])
}
You can send both external and internal messages to your contract via calling sendInternalMessage or sendExternalMessage:
import { SmartContract } from "ton-contract-executor";
import { Cell, InternalMessage, CommonMessageInfo, CellMessage } from "ton";
async function main() {
let contract = await SmartContract.fromFuncSource(source, new Cell())
let msgBody = new Cell()
let res = await this.contract.sendInternalMessage(new InternalMessage({
to: contractAddress,
from: from,
value: 1, // 1 nanoton
bounce: false,
body: new CommonMessageInfo({
body: new CellMessage(msgBody)
})
}))
}
As the result of calling sendInternalMessage, sendExternalMessage or invokeGetMethod ExecutionResult object is returned.
ExecutionResult could be either successful or failed:
declare type FailedExecutionResult = {
type: 'failed';
exit_code: number;
gas_consumed: number;
result: NormalizedStackEntry[];
actionList: OutAction[];
action_list_cell?: Cell;
logs: string;
};
declare type SuccessfulExecutionResult = {
type: 'success';
exit_code: number;
gas_consumed: number;
result: NormalizedStackEntry[];
actionList: OutAction[];
action_list_cell?: Cell;
logs: string;
};
declare type ExecutionResult = FailedExecutionResult | SuccessfulExecutionResult;
What is what:
You also can configure some parameters of your smart contract:
Firstly both fromFuncSource and fromCell accept configuration object as third parameter:
type SmartContractConfig = {
getMethodsMutate: boolean; // this allows you to use set_code in get methods (usefull for debug)
debug: boolean; // enables or disables TVM logs (it's usefull to disable logs if you rely on performance)
runner: TvmRunner;
};
TvmRunner allows you to select TVM executor for specific contract, by default all contracts use TvmRunnerAsynchronous which runs thread pool of wasm TVM.
By default, for each call to TVM current unixtime is set to C7 register, but you can change it by calling setUnixTime on SmartContract instance.
C7 register is used to access some external information in contract:
export declare type C7Config = {
unixtime?: number;
balance?: number;
myself?: Address;
randSeed?: BN;
actions?: number;
messagesSent?: number;
blockLt?: number;
transLt?: number;
globalConfig?: Cell;
};
We prefill it by default, but you can change it by calling setC7Config or setC7.
MIT
FAQs
TON Contracts local executor
The npm package ton-contract-executor receives a total of 165 weekly downloads. As such, ton-contract-executor popularity was classified as not popular.
We found that ton-contract-executor demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
Socket CTO Ahmad Nassri discusses why supply chain attacks now target developer machines and what AI means for the future of enterprise security.

Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.