TON Macro Assembler Multi-Signature Wallet 

The goal was create an efficient multi signature wallet using only basic TON operation, native data structures and minimise the gas consumption based on the formula Pb := 10 + b + 5r. 

No dictionaries, no procedures call, minimum iterated execution, just macros. 

Smart garbage collection - store nearest expiry date for message array and clean only when needed.

Use mswallet-test.fif to see the performance.

Description is here: https://github.com/sevriugin/mswallet/blob/master/README.md

Have a nice ride!

Updated DMSWALLET (MSWallet.fif) on GitHub including key and message dictionaries. Check dmswallet-test.fif to see how it performs - n= 10, k = 3 - steps: 527 gas: 16,819 https://github.com/sevriugin/mswallet

for i in {0..15}; do cp $((i-1)).pubk $i.pubk; fift -s keys-mswallet.fif $i 16; done
fift -s new-mswallet.fif 0 15 16 10
... sendfile 15-query.boc

Account has 1G, nothing happens.

You have whole branch of code without ACCEPT. And as I understand c4 is reverted after throw. <b b> <s 0 <{ 1 INT NEWC 32 STU ENDC c4 POP 1 THROW }>s <b b> | runvmctx <s csr.

Can't create a wallet

fift -s keys-mswallet.fif test 16

Saved new private key to file test.pk
Creating new key array for 16  keys
[ 1][t 0][1571630455.403860092][words.cpp:2906] keys-mswallet.fif:49: key&: not a cell
[ 1][t 0][1571630455.403938055][fift-main.cpp:196] Error interpreting file `keys-mswallet.fif`: error interpreting included file `keys-mswallet.fif` : keys-mswallet.fif:49: key&: not a cell

After contest I tested similar technique, number encoding in base4 exact path that needs to be taken through cells. n % 4 (0, 1, 2, 3) is cell reference that should be loaded. And once n / 4 is less than 4 (1, 2, or 3) - 1 * 256 it encodes the shift within a cell.

I thought that it was very simple an efficient way to navigate through cell tree. Although I knew exactly which reference to load I still could not beat dictionary in gas usage.

I guess dictionary has super-powers because it is also used for subroutine calls. And you can't make random-access data structure that is faster.

Yes, and no accept when you a try to store the signatures either. They are not stored if you don't accept the message. And you don't accept messages which do not have enough signatures.

Here is contract that cannot increase it's sequence number past 6 https://gist.github.com/rainydio/e6c5ad5dbc848e0c9071f2e1e6e99c59

fift -I$FIFTPATH:lib -s new-mswallet.fif
Just hangs. Nothing happens