• Content count

  • Joined

  • Last visited

  • Days Won

  1. Vote for the system that you primarily or mostly use.
  2. Second poll related to One Wallet to Rule Them All:
  3. What is the legal name of this legal entity and where is it registered? GateHub is not a different legal entity AFAIK. And I doubt they can create a separate legal entity out of the blue without informing the customers and maybe getting their consent (because the data controller changes).
  4. Good point. I was actually thinking about the client-only wallet. Bitcoin-qt is given as an example of how this wallet should be distributed ("downloaded") and how it should look like. (although I personally don't like non-native look on Windows). When the community decides about these things, the amount of possible technical solutions will boil down to maybe two or three options. GateHub is a great hosted wallet. But it has some inherent weaknesses: it cannot be (easily) audited and people can't be really sure what is happening with their secret keys.
  5. Can wxWidgets achieve recent (UWP) look & feel in Windows apps?
  6. Exodus explicitly says they won't support Ripple. I'm not sure Bitgo will soon have a "community" version of their (enterprise) wallet. The big question is why gateways don't want to develop a "serious" desktop wallet. It would benefit all of them.
  7. I think the main issues with existing wallets are: they're relatively unknown to the majority of people (there is no clear web page which would say e.g. "Ripple Wallet" + download button), safety and trust issues (how can I know if executable was tampered with?), no one has seriously reviewed the code of these wallets, their UI doesn't native and it looks "foreign" in a typical environment (windows) teams behind them are mostly one-man bands - bus factor 1 (Who will maintain these wallets? Will I be able to use it after one or two years? Will I be able to use my secret key after X years in it?) I don't think Exodus supports Ripple.
  8. Paging doesn't work?
  9. This is just centralized storage solution with local encryption of content. If they go bust, your secret keys go bust. One could probably use a plethora of other more established services (Amazon S3, Azure, DropBox, etc.) and just encrypt the files that you want to store there.
  10. But entering secret keys is practical only for cold storage wallets. Semi? But integration with browsers is questionable...
  11. Try using curl instead of patching rippled.
  12. However, it is probably easier to implement safe alternatives in other (non-browser based) models.
  13. I've heard Malta is more interested in non-financial uses of blockhains (public records, etc.).
  14. These GitHub pages could be a good idea. But there is still one fundamental issue. How to store secret keys? If you use a browser-based wallet, you're a little bit limited to storage facilities supported by your browser (e.g. local storage). Local storage is dangerous because it is often completely emptied (for example, when the user tries to delete cookies or cache because some site tells him/her to do it).