Ёлки палки, забыл добавить в архив файлы stdlib.fc и mylib.fif,
только сейчас вспомнил, а там были доп функции.

Link to the entire archive.
http://complex-soft.com/res/ton2.zip

Link to the "utils".
http://complex-soft.com/res/utils.zip


I forgot to add the stdlib.fc and mylib.fif files to the archive, I just remembered now, and there were additional functions. Attach here.
Where can I send them?

Multisig wallet:
plus:
accept_message() is called only after one signature was verified.
Good perfomance (0.066G for a transfer with n=16, k=10).

minus:
Not all features are implemented (merge signatures)
Single query to add all coowners would work much faster (currently ~0.2G for full initialization)

Manual DNS:
- Only category -1 is supported.
- Maximum domain length is limited by 44 bytes.
- Returns wrong length in case of partial match.
- There is no seqno() method.
- When domain is found, but category is not found the returned length must be non-zero.
- Ability to change code of an inited smart contract is very dangerous.
- Ability to change transaq_id of the smart contract is very-very dangerous.

365 Automatic DNS:
+ Ability to withdraw earnings.
- No garbage collection for expired domains.
- There is no way to customize domain fees.
- There is no way to customize domain expiration time.
- Ability to change code of an inited smart contract is very dangerous.
- Function send_register_domain is used but not defined.
- recv_internal ignores messages not only from masterchain.
- Maximum domain length is limited by 44 bytes.
- Wrong domain length is returned on partial matches.
- When domain is found, but category is not found the returned length must be non-zero.

Manual DNS:
- uses small (352 bit, 44 bytes) max key length in prefix dicts (support up to 1023 bits)
- a lot of extra functionality like send_register_domain
- store_uint(count, 32) in storage is not used anywhere
- supports changing code and seqno - why would anyone trust contract that can change at any moment?

Multisig: requires two signatures for any message (even if it adds only one signature to the storage).
Strange check if(num == 0) { accept_message(); } on ln 183. I cant evaluate, whether it may cause problems or just useless

When redirect to child DNS server occurs contract should return length of found domain path. Instead both manual and auto dns return (length+1)*8 of the original query. Thus it is not clear waht query should be sent to child dns.

new_multisig_wallet.fif:4: include: cannot locate file `../utils/mylib.fif`

You may answer this issue with a link to missing files. On github, for example.

If I see it correctly just actual outgoing message is signed by members. So if I collected signatures of it I can execute it as many times as I would like without collecting signatures again.