An open API service indexing awesome lists of open source software.

https://github.com/danog/toncontest

My submission to the TON blockchain contest
https://github.com/danog/toncontest

Last synced: 2 months ago
JSON representation

My submission to the TON blockchain contest

Awesome Lists containing this project

README

          

# Daniil Gentili entry

This is my entry for the TON contest.

## Building

Simply run the build.sh script to automatically build tonlib and set up some simplified wrapper scripts.

```
toolchain/build.sh
```

This will automatically build the lite client, fift and func, and will also edit .bashrc to add some wrapper scripts to the PATH.

* `lite-client` runs the lite client, already preconfigured to connect to the testnet, with db path set to $TONLIB_HOME/../ton-db-dir (aka this repo/ton-db-dir).
* `funcompile` is a wrapper for the `func` compiler, automatically including the stdlib while compiling.
* `fift` is a simple wrapper for the fift compiler.

## Contents

* `wallet` - Advanced upgradable multisignature wallet, along with a TON collator emulator testing suite written in FIFT, and some scripts to test the wallet using the actual TON collator.
* `toolchain` - Some automatic builder scripts and wrappers around the funC compiler and fift, along with a tweaked zerostate generator and testgiver scripts.
* `test` - A small bugreport about issues with fift exception traces
* [GitHub issues and bugreports](https://github.com/ton-blockchain/ton/issues?utf8=%E2%9C%93&q=author%3Adanog+):
* [#59, bug in funC compiler](https://github.com/ton-blockchain/ton/issues/59)
* [#96, issues with fift exception traces](https://github.com/ton-blockchain/ton/issues/96)
* [#87, pull request with more funC dictionary manipulation primitives](https://github.com/ton-blockchain/ton/pull/87)
* [#98, pull request with minor fift script shebang fixes](https://github.com/ton-blockchain/ton/pull/98)
* [#144, missing create-state instructions](https://github.com/ton-blockchain/ton/issues/144)
* Another improvement for the funC language would be the implementation of more tuple manipulation primitives, such as quiet tuple fetching primitives:
```
// _atq(tuple t, int index) asm "INDEXVARQ";
AsmOp compile_tuple_atq(std::vector& res, std::vector& args) {
assert(args.size() == 2 && res.size() == 1);
auto& y = args[1];
if (y.is_int_const() && y.int_const >= 0 && y.int_const < 16) {
y.unused();
return exec_arg_op("INDEXQ", y.int_const, 1, 1);
}
return exec_op("INDEXVARQ", 2, 1);
}

// ...

define_builtin_func("int_atq", TypeExpr::new_map(TupleInt, Int), compile_tuple_atq);
define_builtin_func("cell_atq", TypeExpr::new_map(TupleInt, Cell), compile_tuple_atq);
define_builtin_func("slice_atq", TypeExpr::new_map(TupleInt, Cell), compile_tuple_atq);
define_builtin_func("tuple_atq", TypeExpr::new_map(TupleInt, Tuple), compile_tuple_atq);
define_builtin_func("atq", TypeExpr::new_forall({X}, TypeExpr::new_map(TupleInt, X)), compile_tuple_atq);
```

...as well as tuple set primitives (which I actually intended to implement in funC and use in a previous version of the wallet smart contract, then scrapped in favor of a simple dictionary).