Unable to add a message key in XPRL to claim Spark tokens

[Ayumi]

I own XRP in Toast wallet and followed the Flare instructions to claim Spark airdrop.  I've connected my Toast wallet to XRPL, created MetaMask wallet and tried to copy the MetaMask address to message kay. Converted to Flare format and clicked submit, then it says 'Unable to Sign - none of your added accounts can sign this transaction'.  What does this mean and what do I need to do? Can anyone help me please?

[SimpleXRPTools]

The old Toast wallet has been discontinued, you shouldn't use that anymore (although I'm pretty sure it still works). See here: 

 

If you really need to, you can still use the browser version here: https://toastwallet.com/browser/index.html

I really hope you're not using Toast Plus because that's been proven to be a scam wallet. If so, it's likely your XRPs have been stolen and your account deleted.

Search your XRP Address here to check it's current balance/status: https://livenet.xrpl.org/

If you can get a hold of your XRP secret/seed then you can use my tools to claim flare. See here: https://github.com/SimpleXRPTools/SimpleXRPTools

If you don't trust my tools (you'd be right to be sceptical) you might be better off using Wieste Wind's tool and the Xumm app. See here: https://flare.wietse.com/

[xrp-sharp]

I have an issue setting up Toast wallet account for Spark/Flare airdrop

Just found out Toast Wallet is now a legacy product (discontinued and unsupported!)

Logged into XRPTOOLKIT and tried to set/amend ‘message key’ on XRP-ledger-account (have setup ETH address needed for SPARK token airdrop)

Update fails with message:

            Unable to Sign

            You have only added an address and can only view your account. Connect a   supported wallet to sign  

             transactions.

Does this mean another XRP address has to (1) be created then (2) somehow linked/enabled to ‘sign’ changes to the TOAST main XRP account?

Can anyone advise as to how to go about doing this?

Of course I have TOAST wallet self-custody info: PIN, pass-phrase, and secret key... but not sure how to solve/work-round this issue.

Thanks if anyone can help..   

[Flintstone]

16 minutes ago, xrp-sharp said:

I have an issue setting up Toast wallet account for Spark/Flare airdrop

Just found out Toast Wallet is now a legacy product (discontinued and unsupported!)

Logged into XRPTOOLKIT and tried to set/amend ‘message key’ on XRP-ledger-account (have setup ETH address needed for SPARK token airdrop)

Update fails with message:

            Unable to Sign

            You have only added an address and can only view your account. Connect a   supported wallet to sign  

             transactions.

Does this mean another XRP address has to (1) be created then (2) somehow linked/enabled to ‘sign’ changes to the TOAST main XRP account?

Can anyone advise as to how to go about doing this?

Of course I have TOAST wallet self-custody info: PIN, pass-phrase, and secret key... but not sure how to solve/work-round this issue.

Thanks if anyone can help..   

Import your secret key to XUMM wallet and then use xrptoolkit.

Or if you want to stay offline, download Bithomp tools and do it yourself. I knocked up a tutorial here:

 

[xrp-sharp]

Hey Flintstone thanks for help

Here's the latest...

Created xumm mobile wallet (on android)

Imported toast (desktop) wallet...

XUMM wallet shows same XRP balance & public address ETC... as TOAST wallet (ie: imported OK)

(xumm wallet was set-up with ‘full-access’)

Again ran XRPTOOLKIT (on laptop) to alter message-key field... & still get the same error message... (seems I’m still missing something)

How can I convince XRPTOOLKIT that I have valid full-control of this account... to tweak tmessage-key?

Thanks

[xrp-sharp]

Sterling stuff Flintstone! 

Just sorted it...

Was a matter of opening xrptoolkit and linking NEW xumm account (used same ledger-account Rxx-etc) THEN modifying message-key AND confirming transaction via-app QR code scan... (confirming tx with xumm-app  password).

AND ... lo and behold transaction was confirmed/accepted/signed.

Double-checked transaction on ledger easily enough via Bithomp... & all looked fine...

As Watson said to Holmes... Case Closed.

Thanks again for help.

ps: xumm looks like a neat wallet