how to withdraw ETH from gatehub

[bitcoinranger]

 I go to send payment then click on ethereum. it says i have to use a hosted wallet to send a ether payment.

I have ether from gatehub fifth.

I also have a ethereum wallet that i want to send it to.

[T8493]

I don't use Gatehub very often, but have you tried sending your ether to your hosted wallet first?

[bitcoinranger]

I dont think i have a hosted wallet. not really sure what that is.

[bitcoinranger]

it seems like i may have to send ether to my hosted wallet from my ripple hosted wallet.

[T8493]

You probably have 2 wallets. One is called "hosted". Check in the Gatehub UI, there is a list of wallets.

[tulo]

I don't understand the use of the hosted wallet...it generates only confusion.

BTW you need to send the ETH from your Ripple wallet to hosted wallet (both on gatehub) and then from hosted to ethereum wallet.

[bitcoinranger]

ya i have my ripple wallet and a hosted wallet. the Ether is on my ripple wallet. 

 

[bitcoinranger]

so i'm looking for my ripple public address on my hosted wallet and i cant find it. ugg I'm a software engineer and this is confusing to me.

[tulo]

59 minutes ago, bitcoinranger said:

so i'm looking for my ripple public address on my hosted wallet and i cant find it. ugg I'm a software engineer and this is confusing to me.

there is not address on hosted wallet...it is a wallet in the private gatehub ledger. Just do send and specify the name of your hosted wallet in gatehub

[bitcoinranger]

ok i think i figured it out but my hosted wallet has not been verified yet... but my account has. 

Im sure this process is done to increase security. Although its confusing.

 

Thanks for your help guys.

[mazi]

Here's the GateHub Help page about Hosted and Ripple wallets (login required to access the page):

https://wallet.gatehub.net/#/help/overview/wallets

I think the page explains it rather concisely and well, especially the Comparison Table. Just mentally replace "Send & Receive (bank)" with something like "Send & Receive (native network)", where the "native nework" for ETH is Ethereum, for EUR it is SEPA, for USD it is bank wire network etc.

It would help if there were a few links to the help page from the parts of the UI where users get confused the most (like the Send page).

[Guest]

On 4/30/2016 at 1:51 AM, bitcoinranger said:

ok i think i figured it out but my hosted wallet has not been verified yet... but my account has. 

Im sure this process is done to increase security. Although its confusing.

 

Thanks for your help guys.

We will make this process much simpler in the future releases so the confusion with hosted and ripple wallets will be gone. If you guys have any suggestions about how would you like it to be we will listen. Thanks @tulo for assistance.

[tulo]

1 hour ago, gregor said:

We will make this process much simpler in the future releases so the confusion with hosted and ripple wallets will be gone. If you guys have any suggestions about how would you like it to be we will listen. Thanks @tulo for assistance.

As it is now (don't know your future developing plans), the best for me would be this scenario:

• User deposits EUR or USD with SEPA or international transfer (or ETH now via Ethereum)
• Gatehub (automatically and behind the scenes) generates a Ripple address (if not created or added one already already) using a small amount of the deposit to generate the minimum XRP to fund the wallet. The XRP are bought using actual offers on the Ripple market.
• Gatehub deposits IOUs of the currency to Ripple wallet (minus the fee to buy initial XRP)
• When outbound (not to Ripple) payments are made (SEPA, ETH, etc), automatically Gatehub client sends (redeem) the IOUs and issues the payment on the external system (SEPA, Ethereum,...)
• When inbound (in Ripple) payments are made, only IOUs move.

In this way you don't even need an internal Ledger. 

[tulo]

1 hour ago, gregor said:

We will make this process much simpler in the future releases so the confusion with hosted and ripple wallets will be gone. If you guys have any suggestions about how would you like it to be we will listen. Thanks @tulo for assistance.

As it is now (don't know your future developing plans), the best for me would be this scenario:

• User deposits EUR or USD with SEPA or international transfer (or ETH now via Ethereum)
• Gatehub (automatically and behind the scenes) generates a Ripple address (if not created or added one already) using a small amount of the deposit to generate the minimum XRP to fund the wallet. The XRP are bought using actual offers on the Ripple market (so you even create a small market for your IOUs).
• Gatehub deposits IOUs of the currency to Ripple wallet (minus the fee to buy initial XRP)
• When outbound (not to Ripple) payments are made (SEPA, ETH, etc), automatically Gatehub client sends (redeem) the IOUs and issues the payment on the external system (SEPA, Ethereum,...)
• When inbound (in Ripple) payments are made, only IOUs move.

In this way you don't even need an internal Ledger. 

Edited May 2, 2016 by tulo

[Guest]

On 5/2/2016 at 6:30 PM, tulo said:

As it is now (don't know your future developing plans), the best for me would be this scenario:

• User deposits EUR or USD with SEPA or international transfer (or ETH now via Ethereum)
• Gatehub (automatically and behind the scenes) generates a Ripple address (if not created or added one already) using a small amount of the deposit to generate the minimum XRP to fund the wallet. The XRP are bought using actual offers on the Ripple market (so you even create a small market for your IOUs).
• Gatehub deposits IOUs of the currency to Ripple wallet (minus the fee to buy initial XRP)
• When outbound (not to Ripple) payments are made (SEPA, ETH, etc), automatically Gatehub client sends (redeem) the IOUs and issues the payment on the external system (SEPA, Ethereum,...)
• When inbound (in Ripple) payments are made, only IOUs move.

In this way you don't even need an internal Ledger. 

The UX of our solution will work similar to your description. We want to have GateHub ledger due to better security of funds. Thanks for the feedback.