Jump to content


  • Content Count

  • Joined

  • Last visited


About xrptoolkit

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Ripple Address

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. We believe finding consensus within the XRP community for issuing USDT tokens on the XRP ledger would be hard, don't you agree? The ERC-20 tokens TrueUSD, Circle USD, Gemini USD, PAX and Dai looks more doable.
  2. The majority of USDT is issued on the Omni layer of Bitcoin, while TrueUSD, USDC, GUSD, PAX, Dai are all ERC-20 tokens. Considering this, would you vote for the largest one (USDT) or unlock 3-4 ERC-20 based ones?
  3. How big is the Factom community and why Factom? How would Factom issued on the XRP ledger benefit the XRP community?
  4. We would really appreciate if the XRP community raised their voice for a minute and provided feedback on this matter. Assume you had access to the XRP ledger's decentralized exchange. What digital asset would you like to be able to send and trade on the XRP ledger?
  5. Yes, the DEX is implemented as one orderbook per issued currency, all paired with XRP. Issuing gateways include exchanges like Bitstamp, GateHub and Bitso. Auto-bridging pairs all issued currencies with each other via XRP. https://developers.ripple.com/decentralized-exchange.html You could deposit USD, EUR, BTC or ETH at an issuing gateway and withdraw the issued currency to your XRP address, then trade it for XRP. It'd be much easier to buy XRP directly. The use-case is rather for trading issued currencies (or tokenized assets like gold), Bitstamp.USD/GateHub.ETH, Bitstamp.BTC/GateHub.EUR etc.
  6. First fan submitted video showcasing secure transaction signing using a Ledger Nano S.
  7. Well, it'll eventually toggle memos on basically ALL transaction types, i.e all pages. Thanks a lot for your feedback!
  8. Login using 'Test Account' and go to Settings > Properties. You should at least be able to see the entire component/card with account flags toggle. We also use the Advanced toggle to hide some seldom used features, such as Source Tag and Invoice ID on the Payments page.
  9. It currently toggles potentially dangerous account flags under Settings > Properties, such as the Disable Master flag. It also toggles the No Ripple flag under Trust Lines. We intend to expand this concept of Basic vs. Advanced mode, as we iterate and introduce even more complex XRPL features. We want to make it really hard to do something really stupid, so to speak. Patience is key. They are coming, take a look at our preliminary roadmap.
  10. The XRP ledger supports associating an email hash with an account (https://developers.ripple.com/rippleapi-reference.html#settings), which is the only data needed to perform a Gravatar (https://en.gravatar.com/site/implement/images/) profile image API request. Bitso, Bitstamp etc. have simply registered a Gravatar account with the corresponding email address and uploaded a profile image (which is the image the XRP Toolkit is showing).
  11. The XRP Toolkit is now ready for a first public beta release (v0.3.0). You are encouraged to experiment with it and feedback is more than welcome. For those of you less familiar with the XRP Toolkit, it’s a project started in mid 2018 by RareData, an XRP community developer with a background in software development and cybersecurity. Live Application: https://www.xrptoolkit.com Mid 2018 the XRP community still lacked a proper XRP ledger interface, one that could help inexperienced users learn more about the XRP ledger in a factual way and help mitigate the widespread FUD. The XRP Toolkit project was started to solve these problems and to unlock more of the XRP ledger's full potential. Another important reason for the XRP Toolkit, was the low usability of existing XRP hardware wallets and applications. The XRP ledger was built for way more than simply sending and receiving XRP, it features things like a decentralized exchange, issued currencies and escrow transactions for good reasons. The XRP Toolkit is not just another "send, receive, view balances" app. When visiting https://www.xrptoolkit.com a client-side web interface is loaded, capable of fetching XRP ledger information, preparing, signing and submitting transactions. Imagine a future where you can securely sign any XRP ledger transaction type, be it an escrow transaction or a decentralized exchange order, using a hardware wallet and web browser. No need for airgapped devices or secret key concerns. Project Goals: Accelerate XRP mainstream adoption, by releasing a secure and user-friendly web interface to the XRP ledger. Encourage learning and XRP ledger experimentation, by making the test net more accessible. Enable multisignature coordination and high security use-cases, by implementing transaction notifications and hardware wallet support. Live Features (v0.3.0): Send and receive XRP payments Adjust trust lines Adjust account settings View asset balances View recent transactions Login Options (v0.3.0): Ledger Nano S: The Ledger Nano S can currently be used to send and receive XRP payments, trust lines and other transaction types are not yet supported by Ledger’s XRP app. To login using a Ledger Nano S, you need to use Google Chrome or equivalent, and have the latest Ledger XRP app (1.0.6) installed. Account Address (View Only) You can login using any account address and view balances, trust lines and settings. Here’s a few addresses you can try: XRP Toolkit: rTooLkitCksh5mQa67eaa2JaWHDBnHkpy Bitso: rG6FZ31hDHN1K5Dkbma3PSB5uVCuVVRzfn Bitstamp: rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B Test Account (Free Practice) All test accounts are pre-filled with 10,000 XRP for free experimentation. You can try different XRP ledger features in a fail-safe manner and experience how they affect the sender or recipient. You can open multiple browser tabs, login using test accounts, try different settings and send XRP payments between them. Secret Key (Not Recommended) Wait for XRP Toolkit offline support or at least minimize your risk exposure, by only using this login option with low value wallets. Security Details: All transaction signing is securely done client-side, inside your browser or hardware wallet, depending on your chosen login option. Fetching the user interface is only possible over an encrypted connection, thanks to enforced HTTPS with HSTS preloading (RFC6797). DNS security extensions (RFC4035) are enabled, to protect against DNS spoofing. Strict security response headers are used, providing defense in depth. UI/UX Details: The XRP Toolkit features a responsive web interface, compatible with a wide range of screen sizes. All transactions involves a confirmation step, where transaction details must be confirmed before they are signed and later submitted to the XRP ledger. Advanced or potentially dangerous features are hidden by default and colored icons makes sure the user understands this. What's Next? A preliminary roadmap is available at https://gitlab.com/xrptoolkit/xrptoolkit-client#roadmap. The project is now on a rolling release and will be updated continuously. With support and feedback from the XRP community, the first stable release (v1.0.0) is expected for early 2019. Short term, the priorities are to prepare the source code for publishing and add additional login options, while lobbying for full XRP support to a handful of hardware wallet companies. Tips: Twitter: @xrptoolkit XRP Address: rTooLkitCksh5mQa67eaa2JaWHDBnHkpy How to Contribute? Experiment with the XRP Toolkit and provide feedback, spread the word in social media or create content such as tutorials, on how to login and send payments using a Ledger Nano S or how to set trust lines. Note that you can use test accounts to simulate real transactions.
  12. I'd just like to clarify that the coming https://www.xrptoolkit.com is more of a web interface than a web wallet, especially since the XRP Toolkit doesn't store any user credentials. Apart from security, the XRP Toolkit is designed for user-friendliness including interoperability. Even if there will be signing options (5) handled by the browser, it's recommended to use a hardware wallet. Additionally, transaction submission (6) can be done separately or by another application like ToastWallet.
  13. When/if Ledger adds support for the required transaction types, the xLedg and XRP Toolkit interfaces should be interoperable. Since both are built on top of the XRP ledger and its built-in orderbook. Regarding Ledger, there's an open issue (https://github.com/LedgerHQ/ledger-app-xrp/issues/3) for 'SetTrust' transactions. Raising awareness about this and have more users reach out to Ledger is probably a good idea.
  • Create New...