Thread replies: 9
Thread images: 1
Thread images: 1
happy shift owner (shiftnrg)
when you own shift, safety wallets is taken care of by shift development 2017-07-29 11:36:45 Post No.
[Report] Image search: [Google]
when you own shift, safety wallets is taken care of by shift development 2017-07-29 11:36:45 Post No.
[Report] Image search: [Google]
File: shift-logo.png (9KB, 506x506px) Image search:
[Google]
9KB, 506x506px
when you own shift, safety wallets is taken care of by shift development
happy shift owner (shiftnrg)
2017-07-29 11:36:45
Post No.
[Report]
I think the Shift team did a great job responding to the posting of private keys over http(s). They made it priority #1 and released a new wallet within a week, to take away these concerns.
They have rewritten the API calls in their webwallet to offlineRequests where secrets never leave the clients computer.
https://github.com/shiftnrg/shift-wallet
Lisk should follow their commits, even though they marked their webwallet deprecated. It's still their responsibility as long as lisk-ui is online.
With Rise forking the Shift codebase it's a no brainer for them to take over this security update too.
>>
When will this shitcoin go up I already lost 30% of my funds all-ining in this piece of shit
>>
Basically put 800 dollars into this coin because the all time high is 5 times it's current price
I do good?
>>
>>2904118
The same exact logic would have you buying SIGT right now
>>
Bought at 60k SAT lol
>>
>>2903625
Nice just bought 100k.
Looks like it's really fixed though after looking through the code.
Good on them.
>>
SHIFT seems like one of the highest potential shitcoins with a low marketcap. I'm not going to lie though, it's perhaps my heaviest bag at the moment.
I'm just hoping the devs will hold back the release of phantom until crypto returns to a bull market.
>>
The devs were aware of the problem the entire time but only fixed the issue AFTER it was publicly exposed!!
Sketchy
>>
No it's not true what you're saying. The devs didn't fix it AFTER it was publicly exposed. They were already working on it. Why do you think it was fixed so quickly.
Thread posts: 9
Thread images: 1
Thread images: 1