Ripple (XRP) is Now Available
We’re excited to share some exciting enhancements:
1. Receive Payments in Ripple (XRP). Users can now accept payments in XRP, expanding their payment options with SHKeeper – a self-hosted crypto processor.
2. Multi-Payout Capability for XRP. With our new multi payout feature, users can effortlessly make payouts in XRP to multiple addresses with just one API call. This streamlines the process, saving time and effort for users managing multiple transactions.
3. Download and Import Private Keys. We’ve added the functionality for users to download their private keys securely and import them into another wallet of their choice. This gives users greater control over their assets and allows for seamless management across different platforms.
4. Enhanced Security with Wallet Encryption. To ensure the utmost security of XRP holdings, we’ve introduced wallet encryption for XRP transactions. This adds an extra layer of protection to users’ funds, safeguarding them against unauthorized access and potential threats.
These SHKeeper updates aim to enhance the user experience, provide greater convenience, and bolster security measures for handling XRP transactions.
Latest News & Announcements
-
SHKeeper Now Supports Lightning Network!
#announcementsWe are thrilled to announce the addition of Lightning Network support to SHKeeper, making transactions faster, cheaper, and more efficient than ever before! Why Use Lightning Network? Important to Note: While SHKeeper fully supports Lightning Network payments, the setup of payment channels and management...
-
External Node Capability for Monero
#announcementsWe are thrilled to announce the release of the capability to utilize an external node for Monero transactions. This powerful new feature enables users to streamline operations by reducing server requirements and optimizing the overall performance of their SHKeeper setup. Here’s What This Release Brings:...
-
Temporary Tron Fullnode Issue Resolved
#announcementsThe Tron fullnode experienced a short-term unavailability yesterday. While it is now back online, there was a period when the fullnode returned an incorrect “last block” number before eventually providing the correct one.If SHKeeper queried the fullnode during this period of incorrect data,...