v0.1.7 was deployed, it's an experimental version! (path payment lacks testing) - I've been testing it for XLM->PHP and seems to work fine! still need feedbacks!
- added path payments
- changed the way the sending form works
Normal payments should be fine as they've not been modified!
orbit84 It works for valid federated addresses ?
Regading bugus ones, you're right - I've noticed that Federation lookup function in the stellar sdk wasn't returning an error when a lookup failed so the .catch() function was never called has it stopped working - I now use an ajax trick to handle bugus destinations ?
Can you share more info? I checked the code of BlackWallet and I don't see any ajax code around StellarSdk.FederationServer calls.
bartek Hello!
Yes, here is the FederationServer code + my workaround with ajax jquery.get!
It's been a few days since that issue now but as far as I remember, when the domain lookup fails with StellarSdk.FederationServer, it's not rejected and so the catch function is not called.
$.get('https://'+destination.split('*')[1]+'/.well-known/stellar.toml')
.then(function() {
StellarSdk.FederationServer.resolve(destination)
.then(federationRecord => {
resolve(federationRecord);
})
.catch(function(error) {
reject(error.detail);
});
})
.catch(function() {
reject(getTextFor('domainNotFound'));
});v0.1.8 was deployed!
09/15/2017 v0.1.8 beta changelog:
- improved overall performance (mostly for mobile use)
- added a pin encryption system when using the mobile mode, secret keys will be encrypted using that pin - for users already in mobile mode, you will be prompted to enter your pin = first time is to set the pin
- inflation address is now displayed in the settings (in the "set inflation destination" input)
- improved the inspect tool (now has json of the latest transactions)
- assets name, description & image retrieving improvements
- charts design was a bit improved (now fits with the website color scheme)
- added changelly in the community section
- fixed some translations problems
can you help me. i cant seem to input the fund quantity or memo hash and thus cant send any funds from my wallet. why would this be and how can i fix it?
When I tried to send XML to my wallet, the Public Key is not recognised as a valid destination tag. Why?
I still not receive my transfer to black wallet. Can administration help me?
Hey thanks, I will fix it asap, can't do it now but it should be done within the coming week ?
merukoin Hello, what's the problem? Not sure to understand. Btw blackwallet do not store any key on its servers, everything is done client side so if it's a problem with your account(private key) I can't do anything sorry ?
Hey,
The problem mentioned above should be fixed now, can anyone confirm?
Also, Blackwallet will take part to the coming SBC, some updates will be released this week nor the week after ?
Update
- added a new tool: contacts, you can now add contacts and specify their address/federated address/email and memo
Trading coming soon on blackwallet!
Trading system should be live soon (maybe this weekend) - It is still being tested (works great so far)
I'm new to Black Wallet.
Had transferred XLM from Bittrex to Black Wallet a week ago. Worked fine.
Then today I tried to transfer XLM from Black Wallet to XLM Bittrex wallet.
It seemed to go through on the Black Wallet side.
But nothing has showed up on the Bittrex XLM wallet for last several hours!
How to recover the XLM funds?!
the transaction operation id:
62709292775510017
memo text was entered as specified in the Bittrex XLM wallet receiving screen.
The Black Wallet website was not helpful at all in figuring this out?!
Please help!
Duke
Hello,
Transaction: https://horizon.stellar.org/operations/62709292775510017
The payment was made through a "merge_account" operation - this operation is not supported by bittrex and most exchanges, that's why there is a message to warn about this:
So that's not a blackwallet issue. To solve that, you can contact bittrex and tell them that you sent your lumens through a merge_account op instead of a payment op.
As your transaction has a memo, it should be fine:
"memo_type": "text",
"memo": "dd5669dc8d0a474486c",
Hope it helps!
orbit84 you could use
https://www.npmjs.com/package/stellarterm-directory
to check for known destinations if
mergeOpAccepted and pathPaymentAccepted and if memo is required. And prevent users from making mistakes.
