Several SHKeepers at the Same Time
We are excited to introduce the possibility of simultaneously installing several SHKeeper instances on the same server!
We’ll delve into the purpose of namespaces – they allow for installing multiple SHKeeper instances on a single server in different namespaces. As part of this update, we had to separate one of the modules into a standalone setup.
The instructions have already been updated if you’re performing SHKeeper installation on a clean server.
However, if you’re upgrading an existing SHKeeper installation on a server where SHKeeper is already installed, you’ll need to perform an update. Starting from release shkeeper-1.3.92, you’ll need to install an additional component to ensure SHKeeper functions properly during the update.
Specifically:
helm repo add mittwald https://helm.mittwald.de
helm repo update
helm install kubernetes-secret-generator mittwald/kubernetes-secret-generatorLatest News & Announcements
-
Bitcoin Support via Public Node & Reduced Server Requirements
#announcementsWe’ve expanded SHKeeper’s capabilities!Bitcoin can now be used through a public node, without the need to run your own full node. This makes integration significantly easier and reduces setup time. In addition, thanks to support for public nodes for Bitcoin and other cryptocurrencies, the VPS requirements...
-
SHKeeper Introduces TRON Staking for Lower TRC-20 Fees
#announcementsWe have added TRON Staking to SHKeeper, including management of Energy, Bandwidth, and optional Super Representative (SR) voting.This feature helps significantly reduce TRX burn during TRC-20 payouts and makes network costs predictable. How It Works In TRON, transaction costs are paid with Bandwidth...
-
SHKeeper Update – ETH Internal Transaction Detection
#announcementsSHKeeper now automatically detects Ethereum internal transactions (transfers initiated through smart contracts, marked as Internal Transactions on Etherscan) and correctly notifies the merchant once the payment is received. Previously, such transfers were visible on-chain but were not triggering invoice...