n=16 k=10

Manual DNS:
- Signature and name of dnsresolve method are incorrect.
- There is no way to completely delete expired domains.
- Maximum domain length is limited by 30 bytes.
- Condition `next_subdomain_length > ( slice_bits(data) + 8)` is very strange. This is not a desired behavior for DNS.

Sadly it didn't work on our test (n=16, k=10).
Anybody may send a message to this account and drain its balance.
A lot of required features are not implemented.

The resolve method is named incorrect, expected name is dnsresolve, therefore your resolve will have 128517 method id versus the 123660 expected for a dns resolver, not counting that expected signature is (slice, int -> (int, cell)) versus your (slice -> (int, cell)) result. Moreover, the int and cell in the results contain vastly different data that is expected per specification.

Nevertheless, this is an interesting implementation supporting resolution of multiple domains in one go (although that feature is mostly useless because getters are executed on client anyway, the client may just query multiple times if needed). Using hashes is one of ways of overcoming limitations of prefix trees, and, possibly, accelerating tree lookups and allowing arbitary length of keys at the cost of storage price (even domain with one letter will require storage of 256-bit hash).

Multisig: messages without signatures (or without correct signatures) will not be only accepted, but also will be written to the persistent storage.
It is never checked, by the way that cur_message_hash is indeed hash of msg

As I see accept_message() is called after ALL signatures are checked. It is very likely than it won't be enough gas_credit to handle orders with multiple signatures

DNS: looks like Suave Ram assumed that if there are many domains separated by "\0" it means that contract should return many results (resolve each domain separately).
Besides domains are stored as integers and search is quite ineffective.

Notes on Manual DNS:
- doesn't use prefix dicts, uses fixed-length 256-bit keys; 

- sdns.fc:154 compares subdomain length (query) with length of dns entry (data)? Maybe I don't get something, sorry

- dnsresolve (called resolve) supports multiple domains with custom output format - there is no check for how many items are being added to output cell, so it is likely to overflow.

A bit confused about HOWTO in multisig.
What should I do to create a wallet (with n=16, k=10) in the blockchain?