Source on GitHub

Smart Contract Address


Source on GitHub

Smart Contract Address


Testing and Issues

You can test this entry and submit issues during the testing period of the Blockchain Contest, Stage 2 contest.

Entries with serious issues will not be able to win the contest, but even minor issues might be important for overall results.



Project 1: ERC20 tokens ported to TON blockchain
- token name and symbol
- token decimals
- multiple non-interchangeable networks
- ready to use with lite-client
Project 2: Ring-signature based mixer
Find friends and use this contract to mix your outputs using ring-signature algorithm implemented with RSA keys. Allows to detach senders and recipients without using any centralized service.
- RSA on funC
- Ring signatures on funC
- Prepare contract offchain and process withdrawals onchain
You have not added any comments yet...
by time


Please stop working on useless mixers until sk-SNARKs are implemented. RSA 16, 32 or even 64 is not a synonym of security nowadays!
Clever Turkey Feb 11 at 04:08
We found some issues in your contracts.
- In the Mixer contract RSA keys size is too small to provide robust encryption.
- In the Mixer contract funds can be withdrawed only after fixed amount is collected. The last person may refuse to make a deposit, forcing others to make the deposit for him to return their money.
- The ERC20 contract doesn't allow to send tokens between workchains.
Nice Llama Feb 11 at 09:41
ERC-20 made this way intentionally. I used the workchain feature to create isolated subsets of tokens. Otherwise workchains effectively belong to some global workchain and do not add any value to tokens.
Mixer contract is more like a proof of concept. Real contract should have elliptic curve arithmetics and longer keys. Recipient addresses should not be added while deploying contract but only added on withdrawal. This way one could deposit missing amount and immediately unlock the funds for himself.
Nobody added any issues yet...