cannot set manager, reserve, freeze, clawback addresses to blank string `''`
See original GitHub issueBefore types
update if we wanted to set manager, reserve, freeze fields to blank using sdk, we passed
let ctxn = algosdk.makeAssetConfigTxnWithSuggestedParams(recoveredAccount2.addr, note, assetID, manager, reserve, freeze, clawback, params, false);
we used the extra strictEmptyAddressChecking parameter in the config change function and set fields to undefined
.
But after types update we cannot set any fields to undefined, and if we use a blank string, we get error address seemed to be malformed
.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Type Error in Asset Creation method · Issue #358 - GitHub
It requires the manager, freeze, clawback and reserve fields. ... However, setting the parameters to an empty string leads to the following ...
Read more >Algorand Standard Assets (ASAs)
Set this address to "" if you want to prove to asset holders that the asset can never be frozen. Clawback Address. The...
Read more >Algorand Dapp Development 2: Standard Asset Management
Clawback Address : The clawback address represents an account that can ... where the `clawback` address has been set to an empty string....
Read more >PyTeal Package — PyTeal documentation - Read the Docs
Used to create a PyTeal Subroutine (returning an ABI value) from a python function. ... address – A string containing a valid base32...
Read more >transaction - Go Packages
Once an address is set to to the empty string, IT CAN NEVER BE CHANGED AGAIN. ... defaultFrozen bool, manager, reserve, freeze, clawback...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks, i was able to solve this with latest commit, probably the problem was with the builds.
This is very strange. With TypeScript v4.3.4 and your
tsconfig.json
from above, I still received no error messages from the IDE and when compiling. I even tried initializing variables asundefined
instead of using direct values, exactly as you wrote in your first example, but I had no luck with it.@jasonpaulos perhaps you could try reproducing this on your computer?