Info

Funny Deer
Author
Download ZIP (34.4 KB)

Testing and Issues

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

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

Voting

33

Comments

Funny Deer Oct 16, 2019 at 12:11
Multisignature wallet. My Telegram: @gr8den

- New wallet
- Create request
- View request
- Add signature to request
- Debug using runvmctx
You have not added any comments yet...
by time

Issues

Magic Python Oct 23, 2019 at 13:47
It is a bit weird to use address serialization instead of public key serialization.

Anyway. I have a private key p.pk. How do I get a public key in your format?
1
Funny Deer Oct 23, 2019 at 17:50
I use human-readable addresses (not hex) because it have checksum.
Yes, script for creating public keys from private key is missing.
But you can use script "create-test-keys.fif" for testing. It generate private keys and show public key.

You can generate public key address like described in new.fif usage "<public key N> is human-readable address like 0QCW0ROe4WFlIB4RyRxVMdpLEOidRN-vrM3MjaKUr1DYh4uF (for any workchain, any flags, used only public key)".

I write simple script for your case: https://gist.github.com/gr8den/37bd1dc914c2ad90fb265f60db820b96
But I think you could use any script for creating wallet also (it generate or load pk and show public address)
Magic Python Oct 23, 2019 at 17:53
There is a user-friendly representation for public keys too. Not only for addresses.
https://github.com/ton-blockchain/ton/blob/master/doc/LiteClient-HOWTO#L36
1
Funny Deer Oct 23, 2019 at 18:06
Fift have functions for it? I seen only $>smca and $<smca in documentation
Magic Python Oct 23, 2019 at 18:09
pubkey>$ in TonUtil.fif. Not in fiftbase.pdf though.
1
Funny Deer Oct 23, 2019 at 18:24
Yes, you right. Using pubkey>$ (and parse-pubkey) is right way in this case. I didn't know about this functions. Thanks
Magic Python Nov 4, 2019 at 10:38
plus:
A separate private key is used which is always verified before accept_message().
While being slow, works on our test. (one transfer with n=16, k=10)

minus:
A bit complicated code
Slow (0.189G for a transfer with n=16, k=10)
Not all features are implemented (merge signatures)
10
Funny Deer Nov 6, 2019 at 17:33
< Not all features are implemented (merge signatures)
> You can add signatures to exist order using script exist-order.fif
Nobody added any issues yet...