Hakuzaru is unnecessarily strict about ak_ vs ct_ prefixes #10

Closed
opened 2025-11-18 11:09:19 +09:00 by spivee · 1 comment
Member

This is more of a note for myself, but if you try to pass in a ct_ to a function that expects an arbitrary address, (which can include contracts!) then it complains. Also, if a function returns an address that happens to be a contract, hakuzaru is blind to this, and wraps it up as ak_, even though technically the address binary has enough info to deduce whether it is a contract or an ECDSA account.

This is more of a note for myself, but if you try to pass in a ct_ to a function that expects an arbitrary address, (which can include contracts!) then it complains. Also, if a function returns an address that happens to be a contract, hakuzaru is blind to this, and wraps it up as ak_, even though technically the address binary has enough info to deduce whether it is a contract or an ECDSA account.
Owner

The recipient case is a bit strict indeed.

This should fix it: #23

The recipient case is a bit strict indeed. This should fix it: https://git.qpq.swiss/QPQ-AG/hakuzaru/pulls/23
zxq9 closed this issue 2026-05-10 17:57:14 +09:00
Sign in to join this conversation.