(Terra) Can't Send $LUNA - Transaction Cost
complete
Matt Roberts
I'm trying to test the multisig and when trying to send $LUNA anywhere from the multisig. I get a transaction error.
insufficient fees; got: 2333uluna required: 3111uluna: insufficient fee
I have plenty of $LUNA in the MultiSig to cover transaction costs.
Dan Jung
Matt Roberts
Regarding your first question, this issue has been fixed. Previously, only tokens registered in our metadata sources (Skip API / chain-registry) were shown as sendable. Now, all tokens in your balance will appear in the send dropdown. For unregistered tokens, a warning will be shown and the amount must be entered in raw units (you may need to manually adjust for decimals).
Sam Kim
marked this post as
complete
I believe it's fixed now. Thank you for reporting.
Matt Roberts
Sam Kim Thank you, that does work now.
New question: I sent another terra asset other than $LUNA to my multisig address. It shows in tokens but does not show as a send able asset. Is it only possible to send luna from the multisig at this time?
Another question: I was talking with philipp from Pheonix Directive/Eris Protocol about logging in or even having a view only for the multisig address and he says there is no pubkey. Is there future plans for this?
Sorry so many questions. If you need me to separate these into new tickets lmk.
Dan Jung
Matt Roberts
Regarding your first question, this issue has been fixed. Previously, only tokens registered in our metadata sources (Skip API / chain-registry) were shown as sendable. Now, all tokens in your balance will appear in the send dropdown. For unregistered tokens, a warning will be shown and the amount must be entered in raw units (you may need to manually adjust for decimals).
Matt Roberts
Dan Jung Huge!! Thank you for your help in these matters. As for the question about pubkey for wallet viewing on dApps like Eris Protocol or even the ability to login and manage with a multisig. Is this possible?