Released the Capability to Use an External Node for Ethereum
Our latest update introduces the capability to leverage an external node for Ethereum, ERC20 USDT, and ERC20 USDC transactions. By utilizing an external node, users can now operate SHKeeper using servers with reduced specifications, optimizing resource usage.
With this enhancement, users can benefit from:
1. Reduce Server Requirements. You can reduce server requirements by minus 4 CPU cores, minus 16GB of RAM, and minus 1TB of SSD or NVMe (2TB recommended). These parameters were previously required for an Ethereum full-node setup.
2. Flexibility to Switch Nodes. Users have the flexibility to switch to another full node at any time, providing a seamless transition in case of any issues with the current node.
3. Immediate Utilization. Users can start using SHKeeper immediately without waiting for the full node to synchronize, streamlining the onboarding process.
This enhancement aims to provide users with greater flexibility, optimize resource utilization, and streamline the user experience when operating on the Ethereum network.
Read a quick guide on how to use Ethereum with SHKeeper public fullnode.
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,...