You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Response from creation of ETH address (it ever doesn't include ETH address):
API for XRP says "Service unavailable".
We use both free and enterprise accounts. We use testnet. Can you help with these? What is going on?
We've got response from the BitGo engineer:
"
Please see the "Generating addresses" section of https://www.bitgo.com/api/v2/#ethereum API docs. Ethereum works differently than the bitcoin-like coins in that when you create an address, it takes some time for it to be properly generated because address creation requires a transaction to be confirmed on the Ethereum network, so we don't return the address until it's creation is confirmed on the network. This is just how Ethereum contracts work, if we didn't do it this way, then you could mistakenly send your coin to an address that wasn't created yet and lose the coin.
Thank you for bringing this to our attention! This was a problem with one of our internal components that I've since fixed, you'll see it returning valid response now."
The text was updated successfully, but these errors were encountered:
yivo
changed the title
Defined Big problems with BitGo API
Definitely BIG problems with BitGo API
Apr 6, 2018
We expect big problems with BitGo API which is documented at https://www.bitgo.com/api/v2/
Response from creation of BTC address:
Response from creation of ETH address (it ever doesn't include ETH address):
We use both free and enterprise accounts. We use testnet. Can you help with these? What is going on?
We've got response from the BitGo engineer:
"
Please see the "Generating addresses" section of https://www.bitgo.com/api/v2/#ethereum API docs. Ethereum works differently than the bitcoin-like coins in that when you create an address, it takes some time for it to be properly generated because address creation requires a transaction to be confirmed on the Ethereum network, so we don't return the address until it's creation is confirmed on the network. This is just how Ethereum contracts work, if we didn't do it this way, then you could mistakenly send your coin to an address that wasn't created yet and lose the coin.
Thank you for bringing this to our attention! This was a problem with one of our internal components that I've since fixed, you'll see it returning valid response now."
The text was updated successfully, but these errors were encountered: