Sign up to join our community!
Please login to your account!
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
My original storage test passed for "str:clientToken|address:client_1_address": "str:token:client_1_token" is that because ManagedAddress is a known length so doesn't require Nested Encoding whereas the TokenIdentifier can be any length based on its name?
yes address encoding for nested and toplevel are the same :)