Error sending transaction to tmgox

Tech Support
1

i just tried to buy something on tmgox with grin. Using a Grin-Wallet 1.1.0 beta for windows 10, i received the following error-message:

Password: 20190428 10:53:56.989 ERROR grin_wallet_impls::adapters::http - Posting transaction slate (is recipient listening?): Request error: Wrong response code: 500 Internal Server Error with data Body
Wallet command failed: LibWallet Error: Client Callback Error: Posting transaction slate (is recipient listening?): Request error: Wrong response code: 500 Internal Server Error with data Body

I tried to send the transaction to the specified https-address shown when the order is placed. I don’t have a clue why the transaction failed.

I noticed also another issue. Before trying to buy something on tmgox today, i did send a small amount of Grin via Transaction-File to a forum member via E-Mail (this was yesterday).
After creating the transaction-file, which did only hold a fraction of my spendable grin, the complete amount of my wallet was suddenly “locked by previous transaction” and not just the fraction i did want to send via transaction-file. The Forum-Member unfortunately did not react to my E-Mail yet and thus still did not confirm the transaction. Because of this i could not use my grin-wallet to spend the rest of my available grin that was not affected by the tx-file for the forum-member. I first had unfortunately to cancel the transaction to the forum-member because he did not send me the confirmation-file back yet, so i could use my wallet for the intended tmgox-purchase. Is this normal behaviour? It seems odd to me that when sending a transaction-file you are not able to use your wallet until the receiver confirm the transaction, send back the response-file and you finalize the payment.

This would lead to a situation in which you cannot access the content of your wallet until the recipient of a payment has reacted or do I see this incorrectly?

2

Maybe you have to use this?

This looks like a hard fork to me. I find it strange that nobody discusses this upcoming disruption of the ecosystem. How should exchanges handle this?

3

The second issue is probably related to the utxo selection strategy used by the wallet. I think the default is ‘all’ which means your wallet will use as many outputs as possible to build the transaction. I suspect your wallet funds were locked because all of your utxos were used as change to the transaction.

The first issue is either an issue on the tmgox size or an incompatibility between your wallet and the tmgox wallet due to some recent changes in the wallet. Please ask at the support channel about it.

4

The transaction protocol is not part of the node protocol so while I think there is an incompatibility between some wallet versions, it’s definitely not going to result in a hard fork.

5

This looks like a hard fork to me.

This has nothing to do with hard/soft forks as the consensus rules do not change. The reason this happens is because versioning was added to the slate files. The new slate version (V1) changed some fields to a more compact encoding.

How should exchanges handle this?

grin-wallet v1.1.0 uses V1 slates by default and older wallets use V0 and can’t understand V1. If you upgrade to grin-wallet v1.1.0 you can receive from anyone. If you want to send to an older wallet though you need to add a -v 0 parameter. i.e grin-wallet send <amount> -d <address> -v 0

1 Like
6

If you want to send to an older wallet though you need to add a -v 0 parameter. i.e grin-wallet send <amount> -d <address> -v 0

This did work, i could send the transaction now. thanks!

1 Like