Code Monkey home page Code Monkey logo

vsys-host / shkeeper.io Goto Github PK

View Code? Open in Web Editor NEW
199.0 199.0 51.0 325 KB

SHKeeper is a self-hosted and open-source cryptocurrency gateway payment processor. It's integrate with popular CMS, any e-commerce, your own code or product

Home Page: https://shkeeper.io/

License: GNU General Public License v3.0

Python 33.11% CSS 20.64% JavaScript 22.11% Jinja 23.90% Dockerfile 0.10% Mako 0.14%
accept-crypto accept-crypto-payments crypto crypto-gateway crypto-payment crypto-payment-api crypto-payment-gateway crypto-payments crypto-processor cryptocurrency-payments gateway gateway-api gateway-service gateway-services open-source payment-gateway payment-processing payment-processor self-hosted self-hosted-api

shkeeper.io's People

Contributors

dmytro-samoylenko avatar olxndr avatar prerogativaux avatar yukonet avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

shkeeper.io's Issues

Is there an API for shkeeper.io TRC full node?

Hello,

According to the docs and what I've seen in shkeeper repos there is a support for USDT and USDC coins (TRON network).
I've also seen a confirmation about the ability of using TRON in the recent issue. It says

For USDT and USDC you can:

  • use our TRC full node with our API for free
  • or deploy your TRC full node by yourself

I am curious about first option (using your API) – how can I access it? Didn't found anything about it in the docs.
The only thing I could imagine being your API for TRC is kafka-to-ws repo which seems to use kafka.tron.shkeeper.io as a default value for KAFKA_HOST. But I've never managed to get a response from it rather than following error

Unable connect to "kafka.tron.shkeeper.io:9092": [Errno 111] Connect call failed

Could you please clarify how to use your TRC full node with your API and whether it is even possible?

Error: ETH Internal Server Error

reason:

the error occurred when navigating to the page /payout/ETH-USDC and /payout/ETH-USDT
for /payout/ETH there was no mistake

the synchronization process is also not displayed

kubectl -n shkeeper logs shkeeper-deployment-574c5c77b4-t8fm4  --tail 100
[2023-05-02 20:24:12,891] WARNING in tron_token: Response: {'msg': 'can not call a contract without ABI', 'status': 'error'} Error: 'balance'
[2023-05-02 20:24:12,902] WARNING in tron_token: Response: {'msg': 'can not call a contract without ABI', 'status': 'error'} Error: 'balance'
10.42.0.172 - - [02/May/2023:20:24:12 +0000] "GET /api/v1/USDT/status HTTP/1.1" 200 80 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
10.42.0.172 - - [02/May/2023:20:24:12 +0000] "GET /api/v1/USDC/status HTTP/1.1" 200 80 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
10.42.0.172 - - [02/May/2023:20:24:12 +0000] "GET /api/v1/TRX/status HTTP/1.1" 200 79 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
[2023-05-02 20:24:22,742] WARNING in ethereum: Error: Expecting value: line 1 column 1 (char 0)
[2023-05-02 20:24:22,743] WARNING in ethereum: Error: Expecting value: line 1 column 1 (char 0)
[2023-05-02 20:24:22,755] WARNING in ethereum: Error: Expecting value: line 1 column 1 (char 0)
10.42.0.172 - - [02/May/2023:20:24:22 +0000] "GET /api/v1/BTC/status HTTP/1.1" 200 44 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
10.42.0.172 - - [02/May/2023:20:24:22 +0000] "GET /api/v1/ETH/status HTTP/1.1" 200 45 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
10.42.0.172 - - [02/May/2023:20:24:22 +0000] "GET /api/v1/ETH-USDC/status HTTP/1.1" 200 50 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
10.42.0.172 - - [02/May/2023:20:24:22 +0000] "GET /api/v1/LTC/status HTTP/1.1" 200 44 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
10.42.0.172 - - [02/May/2023:20:24:22 +0000] "GET /api/v1/ETH-USDT/status HTTP/1.1" 200 50 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
10.42.0.172 - - [02/May/2023:20:24:22 +0000] "GET /api/v1/DOGE/status HTTP/1.1" 200 45 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
[2023-05-02 20:24:22,977] WARNING in tron_token: Response: {'msg': 'can not call a contract without ABI', 'status': 'error'} Error: 'balance'
[2023-05-02 20:24:22,980] WARNING in tron_token: Response: {'msg': 'can not call a contract without ABI', 'status': 'error'} Error: 'balance'
10.42.0.172 - - [02/May/2023:20:24:22 +0000] "GET /api/v1/TRX/status HTTP/1.1" 200 79 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
10.42.0.172 - - [02/May/2023:20:24:22 +0000] "GET /api/v1/USDC/status HTTP/1.1" 200 80 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
10.42.0.172 - - [02/May/2023:20:24:23 +0000] "GET /api/v1/USDT/status HTTP/1.1" 200 80 "http://10.0.20.90:5000/wallets" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0"
kubectl -n shkeeper logs ethereum-shkeeper-5bf77fc777-zsh5t  --tail 20
Defaulted container "app" out of: app, tasks, redis
10.42.0.190 - bitcoind-user [02/May/2023:20:35:34 +0000] "POST /ETH-USDT/status HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:35 +0000] "POST /ETH/balance HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:35 +0000] "POST /ETH/status HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:35 +0000] "POST /ETH-USDC/balance HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:35 +0000] "POST /ETH-USDT/balance HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:35 +0000] "POST /ETH-USDT/status HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:35 +0000] "POST /ETH-USDC/status HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:45 +0000] "POST /ETH/balance HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:45 +0000] "POST /ETH-USDT/balance HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:45 +0000] "POST /ETH-USDC/balance HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:45 +0000] "POST /ETH/status HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:45 +0000] "POST /ETH-USDT/status HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:45 +0000] "POST /ETH-USDC/status HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:55 +0000] "POST /ETH/balance HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:55 +0000] "POST /ETH-USDC/balance HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:55 +0000] "POST /ETH-USDT/balance HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:55 +0000] "POST /ETH-USDT/status HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:55 +0000] "POST /ETH/status HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:35:55 +0000] "POST /ETH-USDC/status HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
10.42.0.190 - bitcoind-user [02/May/2023:20:36:03 +0000] "POST /ETH-USDC/fee-deposit-account HTTP/1.1" 404 207 "-" "python-requests/2.28.1"
kubectl -n shkeeper logs ethereum-64f4b95675-86gnr --tail 20
Defaulted container "geth" out of: geth, prysm-beacon, nginx
INFO [05-02|20:37:02.025] Forkchoice requested sync to new head    number=17,175,499 hash=763e7f..02c140 finalized=17,175,412
INFO [05-02|20:37:07.984] Syncing beacon headers                   downloaded=3,867,648 left=13,307,666 eta=1h1m17.091s
INFO [05-02|20:37:12.916] Forkchoice requested sync to new head    number=17,175,500 hash=83efad..c622eb finalized=17,175,412
INFO [05-02|20:37:15.985] Syncing beacon headers                   downloaded=3,924,480 left=13,250,834 eta=1h0m35.382s
INFO [05-02|20:37:24.500] Syncing beacon headers                   downloaded=3,978,240 left=13,197,074 eta=59m59.950s
INFO [05-02|20:37:25.478] Forkchoice requested sync to new head    number=17,175,501 hash=1af223..23f173 finalized=17,175,412
INFO [05-02|20:37:32.571] Syncing beacon headers                   downloaded=4,034,560 left=13,140,754 eta=59m20.838s
INFO [05-02|20:37:36.531] Forkchoice requested sync to new head    number=17,175,502 hash=7ca93f..26a0e2 finalized=17,175,412
INFO [05-02|20:37:40.598] Syncing beacon headers                   downloaded=4,083,712 left=13,091,602 eta=58m50.553s
INFO [05-02|20:37:48.675] Syncing beacon headers                   downloaded=4,137,472 left=13,037,842 eta=58m15.820s
INFO [05-02|20:37:49.466] Forkchoice requested sync to new head    number=17,175,503 hash=ad5244..8a8a40 finalized=17,175,412
INFO [05-02|20:37:56.827] Syncing beacon headers                   downloaded=4,184,064 left=12,991,250 eta=57m49.850s
INFO [05-02|20:38:02.142] Forkchoice requested sync to new head    number=17,175,504 hash=528b3f..76713a finalized=17,175,412
INFO [05-02|20:38:05.009] Syncing beacon headers                   downloaded=4,227,072 left=12,948,242 eta=57m28.240s
INFO [05-02|20:38:12.669] Forkchoice requested sync to new head    number=17,175,505 hash=41ca7a..278562 finalized=17,175,412
INFO [05-02|20:38:13.208] Syncing beacon headers                   downloaded=4,277,760 left=12,897,554 eta=56m58.763s
WARN [05-02|20:38:20.535] Header request timed out, dropping peer  peer=d1c94e76 elapsed=7.500732493s
INFO [05-02|20:38:21.234] Syncing beacon headers                   downloaded=4,326,912 left=12,848,402 eta=56m30.879s
INFO [05-02|20:38:24.942] Forkchoice requested sync to new head    number=17,175,506 hash=21f99c..7910b0 finalized=17,175,412
INFO [05-02|20:38:29.400] Syncing beacon headers                   downloaded=4,370,432 left=12,804,882 eta=56m9.666s
eth_fullnode:
  enabled: true
  url: http://ethereum:8545
  mainnet: true
  nodeSelector: {}
  tolerations: []

ethereum_shkeeper:
  image: vsyshost/ethereum-shkeeper:1.0.9

eth:
  enabled: true
eth_usdt:
  enabled: true
eth_usdc:
  enabled: true

Idea: TRON delegation of energy to payment_address

the point is not to pay TRX commission, but to pay with energy

to make 1 transaction (USDT), approximately 14k of energy is needed, energy can be obtained for a steak (it can be done by hand, by spoiling the private key in TronLink).

and make the automatic energy delegation setting (if there is enough of it on the fee_account). and use it together burning TRX

Idea: balance conrtol to API

Reason:

full integrate the Shkeeper into project. from the moment of purchase to withdrawal

Description:

add to the API the ability to view the balance, count the commission and withdraw funds
you can do this based on those CRUD's that are already used in the Shkeeper cabinet

Taxes reports integration

Hello! I love what you do. Open Source is the key for any platform to be Audited, adopted, and trusted.
What do you think about taxes reports? We can add integration with some Open Source tax calculation platforms so that people can generate taxes through their crypto transactions.

Bug(hot): there is no difference which coin to send

I received 9 USDT. and the notification said 9.00000100

i look for key 'balanceCrypto'

my wallet:
USDT
изображение

TRX
изображение

my notification:
{"fiat": "USD", "paid": true, "crypto": "USDT", "status": "PAID", "externalId": "312", "feePercent": "0", "balanceFiat": "9.00", "overpaidFiat": "0.00", "transactions": [{"date": "2023-08-07 16:49:13", "txid": "72***22", "trigger": false, "amountFiat": "9.00", "amountCrypto": "9.00000000"}, {"date": "2023-08-07 18:11:41", "txid": "93***06", "trigger": true, "amountFiat": "0.00", "amountCrypto": "0.00000100"}], "balanceCrypto": "9.00000100"}

although tronscan.org does not display this transaction at 0.00000100 for USDT. it was made in TRX

result: 9.00000100 USDT
from:

  1. 9.00000000 USDT
  2. 0.00000100 TRX

in theory, you can cheat the system by sending 100 TRX instead of 100 USDT

How to connect shkeeper with dogecoind

Hi!

I am trying to deploy shkeeper without the helm chart.
I can get both dogecoind and shkeeper running, but I can't make them communicate with one another.
I tried to follow the content of the helm chart. But it seems like I may be missing some configuration.

So, as the title of the issue suggest, how can I connect dogecoind with shkeeper?

Best regards

[SALES / SUPPORT REQUEST] - website contact form doesn't work

I'm writing about the WHMCS module for shkeeper.io, and we have a few questions:

1.) I can't find the list of Cryptocurrencies that it supports. This is very important and should be prominently displayed on the front page if you're website.

Can you please send that to me?

Does it support the following?

XLM ADA SOL NANO XRP ZEC and XMR?

Those are the Cryptocurrencies we are interested in and are supported by BTCPayserver, which is also a FOSS GPL v3 license.

2.) To be perfectly clear: We can self-host for free, and integrate a single installation of shkeeper.io simultaneously with our following products and services?

WHMCS, WordPress, WooComerce, basic websites, and our web based restaurant point of sale?

3.) We can send email invoices to people?

4.) I couldn't find a donation page. If it's truly 100% free and open source software, then how do you fund your continued development? Where do we send donations to? Do you have Liberapay, OpenCollective, or Ko-Fi accounts?

5.) To be certain: when (if) we self-host shkeeper, it does not connect to your servers - only full node blockchains and places like Coingecko for the current exchange rates, is that correct?

Thank you, we look forward to hearing back from you very soon - you advertise 24/7/365 support, but one of your customers opened a support ticket in Github that went unanswered for 22 days and that doesn't make you look good or reliable.

6.) Your website contact form doesn't seem to worj either! I tried to send this message several times. No Joy.

We hope it doesn't take you 22 days to respond to our ticket like it did for the other person here when they needed installation help that was because your left a step out of the instructions to create a directory.

Our need us immediate.

Thank you.

error password after reboot server

Reason: after server(VM) restart

Pod: litecoind-deployment

 Name:             litecoind-deployment-88d5f4985-tdwbk
Namespace:        shkeeper
Priority:         0
Service Account:  default
Node:             ubuntu2004/192.168.0.73
Start Time:       Sun, 16 Apr 2023 00:27:43 +0000
Labels:           app=litecoind
                  pod-template-hash=88d5f4985
Annotations:      <none>
Status:           Pending
IP:
IPs:              <none>
Controlled By:    ReplicaSet/litecoind-deployment-88d5f4985
Containers:
  nginx:
    Container ID:
    Image:          nginx
    Image ID:
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      SHKEEPER_BACKEND_KEY:  <set to the key 'password' in secret 'shkeeper-btc-key'>  Optional: false
    Mounts:
      /backup from backup (rw)
      /etc/nginx/nginx.conf from nginx-config (rw,path="nginx.conf")
      /etc/nginx/templates/default.conf.template from nginx-config (rw,path="default.conf.template")
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rhrbk (ro)
  litecoind:
    Container ID:
    Image:          vsyshost/litecoind
    Image ID:
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      LTC_USERNAME:          <set to the key 'username' in secret 'litecoin-rpc'>      Optional: false
      LTC_PASSWORD:          <set to the key 'password' in secret 'litecoin-rpc'>      Optional: false
      SHKEEPER_BACKEND_KEY:  <set to the key 'password' in secret 'shkeeper-btc-key'>  Optional: false
    Mounts:
      /backup from backup (rw)
      /root/.litecoin from litecoind-storage (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rhrbk (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  litecoind-storage:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  litecoind-claim
    ReadOnly:   false
  backup:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     Memory
    SizeLimit:  <unset>
  nginx-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      nginx-config
    Optional:  false
  kube-api-access-rhrbk:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason            Age    From               Message
  ----     ------            ----   ----               -------
  Warning  FailedScheduling  6m21s  default-scheduler  0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/disk-pressure: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
  Warning  FailedScheduling  65s    default-scheduler  0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/disk-pressure: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
  Normal   Scheduled         5s     default-scheduler  Successfully assigned shkeeper/litecoind-deployment-88d5f4985-tdwbk to ubuntu2004
  Normal   Pulling           3s     kubelet            Pulling image "nginx"

Pod: shkeeper-deployment

Name:             shkeeper-deployment-bbf75cb9d-6rg29
Namespace:        shkeeper
Priority:         0
Service Account:  default
Node:             ubuntu2004/192.168.0.47
Start Time:       Mon, 17 Apr 2023 09:36:13 +0000
Labels:           app.kubernetes.io/instance=shkeeper-vsys
                  app.kubernetes.io/name=shkeeper
                  pod-template-hash=bbf75cb9d
Annotations:      <none>
Status:           Running
IP:               10.42.0.97
IPs:
  IP:           10.42.0.97
Controlled By:  ReplicaSet/shkeeper-deployment-bbf75cb9d
Containers:
  shkeeper:
    Container ID:   containerd://777f30f803134065e14d05dff9a1b9c8c9bff8b58fb7c49cf1e031155b5ec55c
    Image:          vsyshost/shkeeper:1.1.17
    Image ID:       docker.io/vsyshost/shkeeper@sha256:853980ff17fca6b7a782cf25216d136395667cc9efcb9f8ac825f37ab96cd25c
    Port:           5000/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Mon, 17 Apr 2023 09:36:14 +0000
    Ready:          True
    Restart Count:  0
    Environment:
      TRON_API_SERVER_HOST:      tron-shkeeper
      TRON_API_SERVER_PORT:      6000
      BTC_WALLET:                enabled
      LTC_WALLET:                enabled
      DOGE_WALLET:               enabled
      TRX_WALLET:                enabled
      USDT_WALLET:               enabled
      USDC_WALLET:               enabled
      ETH_WALLET:                disabled
      ETH_USDT_WALLET:           disabled
      ETH_USDC_WALLET:           disabled
      MONERO_WALLET:             disabled
      BTC_USERNAME:              <set to the key 'username' in secret 'bitcoin-rpc'>       Optional: false
      BTC_PASSWORD:              <set to the key 'password' in secret 'bitcoin-rpc'>       Optional: false
      LTC_USERNAME:              <set to the key 'username' in secret 'litecoin-rpc'>      Optional: false
      LTC_PASSWORD:              <set to the key 'password' in secret 'litecoin-rpc'>      Optional: false
      DOGE_USERNAME:             <set to the key 'username' in secret 'dogecoin-rpc'>      Optional: false
      DOGE_PASSWORD:             <set to the key 'password' in secret 'dogecoin-rpc'>      Optional: false
      TRX_USERNAME:              <set to the key 'username' in secret 'usdt-rpc'>          Optional: false
      TRX_PASSWORD:              <set to the key 'password' in secret 'usdt-rpc'>          Optional: false
      USDT_USERNAME:             <set to the key 'username' in secret 'usdt-rpc'>          Optional: false
      USDT_PASSWORD:             <set to the key 'password' in secret 'usdt-rpc'>          Optional: false
      USDC_USERNAME:             <set to the key 'username' in secret 'usdt-rpc'>          Optional: false
      USDC_PASSWORD:             <set to the key 'password' in secret 'usdt-rpc'>          Optional: false
      SHKEEPER_BTC_BACKEND_KEY:  <set to the key 'password' in secret 'shkeeper-btc-key'>  Optional: false
    Mounts:
      /shkeeper.io/instance from shkeeper-db-storage (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-vz95s (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  shkeeper-db-storage:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  shkeeper-db-claim
    ReadOnly:   false
  kube-api-access-vz95s:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  16m   default-scheduler  Successfully assigned shkeeper/shkeeper-deployment-bbf75cb9d-6rg29 to ubuntu2004
  Normal  Pulled     16m   kubelet            Container image "vsyshost/shkeeper:1.1.17" already present on machine
  Normal  Created    16m   kubelet            Created container shkeeper
  Normal  Started    16m   kubelet            Started container shkeeper

Problem in connecting with TRON shkeeper-hosted full node

I tried to connect to your full node to be able to process payments without having to download the full node but it seems that the host is not working though.
values.yaml content:

cat << EOF > values.yaml

#
# General
#

dev:
  imagePullSecrets:

storageClassName: local-path


#
# BTC and forks
#

btc:
  enabled: true
ltc:
  enabled: true
doge:
  enabled: true


monero:

  enabled: false
  image: vsyshost/monero:v0.18.1.2
  mainnet: true

  fullnode:
    enabled: false
    monerod:
      host: "monerod"
      port: "1111"
      user: "monerod"
      password: "monerod"
      nodeSelector: {}
      tolerations: []

tron_fullnode:
  enabled: true
  url: http://fullnode.tron.shkeeper.io
  image: vsyshost/tron-shkeeper:1.0.14
  host: 'tron-shkeeper'
  port: 6000

trx:
  enabled: true
usdt:
  enabled: true
usdc:
  enabled: true
EOF

Backup page internal server error

can't able to fetch backup file.

why again trying to establish connection to sqllite. use the old connection.

[2023-07-11 13:09:56,286] ERROR in app: Exception on /api/v1/BTC/backup [GET]
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/urllib3/connection.py", line 174, in _new_conn
conn = connection.create_connection(
File "/usr/local/lib/python3.8/dist-packages/urllib3/util/connection.py", line 95, in create_connection
raise err
File "/usr/local/lib/python3.8/dist-packages/urllib3/util/connection.py", line 85, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/urllib3/connectionpool.py", line 714, in urlopen
httplib_response = self._make_request(
File "/usr/local/lib/python3.8/dist-packages/urllib3/connectionpool.py", line 415, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/local/lib/python3.8/dist-packages/urllib3/connection.py", line 244, in request
super(HTTPConnection, self).request(method, url, body=body, headers=headers)
File "/usr/lib/python3.8/http/client.py", line 1256, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.8/http/client.py", line 1302, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.8/http/client.py", line 1251, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.8/http/client.py", line 1011, in _send_output
self.send(msg)
File "/usr/lib/python3.8/http/client.py", line 951, in send
self.connect()
File "/usr/local/lib/python3.8/dist-packages/urllib3/connection.py", line 205, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.8/dist-packages/urllib3/connection.py", line 186, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7ff4e027c040>: Failed to establish a new connection: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/requests/adapters.py", line 489, in send
resp = conn.urlopen(
File "/usr/local/lib/python3.8/dist-packages/urllib3/connectionpool.py", line 798, in urlopen
retries = retries.increment(
File "/usr/local/lib/python3.8/dist-packages/urllib3/util/retry.py", line 592, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='localhost', port=5555): Max retries exceeded with url: /2023-07-11_13:09:53_BTC_shkeeper_wallet.dat (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7ff4e027c040>: Failed to establish a new connection:
[Errno 111] Connection refused'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 2525, in wsgi_app
response = self.full_dispatch_request()
File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 1822, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 1820, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 1796, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
File "/crypto_node/shkeeperMain/shkeeper/auth.py", line 64, in wrapped_view
return view(**kwargs)
File "/crypto_node/shkeeperMain/shkeeper/api_v1.py", line 355, in backup
req = requests.get(url, stream=True, headers={"X-SHKEEPER-BACKEND-KEY": bkey})
File "/usr/local/lib/python3.8/dist-packages/requests/api.py", line 73, in get
return request("get", url, params=params, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/requests/api.py", line 59, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/requests/sessions.py", line 587, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.8/dist-packages/requests/sessions.py", line 701, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/requests/adapters.py", line 565, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=5555): Max retries exceeded with url: /2023-07-11_13:09:53_BTC_shkeeper_wallet.dat (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7ff4e027c040>: Failed to establish a new connection: [Errno 111] Connection refused'))

and make one config file for rpcuser. password, ip, port.
they should be custom .
and disabling currencies also from config file that would be good.

Idea: integration TRON Lite FullNode

Reason:

reducing the waiting time for synchronization of the entire blockchain
the jump rate of the full node is 4mbps. and when it is fully downloaded, it will take too much time (or you can make a setup for shkeeper-tron so that you can specify the IP address to another node and follow the node)
this applies to ETH

Description:

this node provides access to all new blocks, but did not provide access to the history. but we don't need the whole story on how much according to the current logic our addresses in the TRON network are being created at the present moment. and we do not have the ability to download the following addresses

sources:

https://tronprotocol.github.io/documentation-en/developers/litefullnode/

callback not being called for DOGE

Hi, I set up this and am running shkeeper with gunicorn. I'm connected to my local wallet, and everything seems to work. I created a payment request, and send 2 dogecoins over. 10 minutes later, and it hasn't done anything. In dogecoin-cli, I can see the transaction has completed, but shkeeper doesn't detect it.

I'm at the latest commit.

Also tried:

$ flask callback list
No unconfirmed transactions found!

Server Full Nodes

I have a doubt when configuring the nodes. For BTC, the local full node worked normally, but for the last update of the code in ethereum and tron ​​network, will I have to install fullnode too? Because the parameter seems to allow me to use an external api node... is it possible? can you provide me with an example of .env with the parameters to run the project?

Idea: import/export private key | backup | restore

The private wallet has already been configured to spoil.

I propose to do "Export" of a private switch, also in the UI. this would be useful when moving to another server
After unrolling the new copy, you didn’t have to bother with the remaining amounts on the old copy

What is /tx-info/<txid> status based on?

Sorry if this is not the correct place to ask quesions... but I see you are pretty active here.

What is the /tx-info/ "status" propery based on? I read the code and I can't seem to see the big picture.
I tried comparing it with the status of the transaction in the block explorer and it doesn't seem to wait for confirmations.

Do you perhaps assume that the transaction will just be "successful" after sending it the respective crypto's blockchain?

Bug: what are the problems with LTC

I made a payment on one time wallet in LTC. but it was not credited to the balance. transaction and notification were not created

I didn't change anything in the settings. just updated to version 1.3.0

I do not know what other information i can provide us with, but please test it. the money remained for this one time wallet

> kubectl -n shkeeper logs litecoind-deployment-85cf98df64-f72z2  --tail 100
Defaulted container "nginx" out of: nginx, litecoind
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
/docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/default.conf.template to /etc/nginx/conf.d/default.conf
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2023/09/07 20:58:31 [notice] 1#1: using the "epoll" event method
2023/09/07 20:58:31 [notice] 1#1: nginx/1.25.2
2023/09/07 20:58:31 [notice] 1#1: built by gcc 12.2.0 (Debian 12.2.0-14)
2023/09/07 20:58:31 [notice] 1#1: OS: Linux 5.15.0-78-generic
2023/09/07 20:58:31 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2023/09/07 20:58:31 [notice] 1#1: start worker processes
2023/09/07 20:58:31 [notice] 1#1: start worker process 36
2023/09/07 20:58:31 [notice] 1#1: start worker process 37
2023/09/07 20:58:31 [notice] 1#1: start worker process 38
2023/09/07 20:58:31 [notice] 1#1: start worker process 39

ETH/BNB seem to be broken in latest release.

Exceptions that occur:

192.168.220.32 - bitcoind-user [18/Nov/2023:12:23:39 +0000] "POST /BNB-USDT/balance HTTP/1.1" 200 119 "-" "python-requests/2.28.1"
[2023-11-18 12:23:39,337] WARNING: Exception: Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1820, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1796, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
  File "/app/app/api/views.py", line 62, in get_status
    last_checked_block_number = int(pd.value)
AttributeError: 'NoneType' object has no attribute 'value'

192.168.220.32 - bitcoind-user [18/Nov/2023:12:36:39 +0000] "POST /ETH-USDC/status HTTP/1.1" 200 70 "-" "python-requests/2.28.1"
023-11-18 12:30:39,513] WARNING: Exception: Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1820, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1796, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
  File "/app/app/api/views.py", line 60, in get_status
    last_checked_block_number = int(pd.value)
AttributeError: 'NoneType' object has no attribute 'value'

ETH fullnode is fully synced.

BNB fullnode deployment isn't configured correctly in helm chart:

INFO [11-18|12:34:36.798] Looking for peers                        peercount=0 tried=54  static=0
WARN [11-18|12:34:39.283] Served eth_chainId                       conn=192.168.219.206:56258 reqid=0 t="22.993µs" err="chain not synced beyond EIP-155 replay-protection fork block" X-Forwarded-For=nil
WARN [11-18|12:34:39.283] Served eth_chainId                       conn=192.168.219.206:56258 reqid=0 duration="22.292µs" err="chain not synced beyond EIP-155 replay-protection fork block"
WARN [11-18|12:34:39.285] Served eth_chainId                       conn=192.168.219.206:56260 reqid=0 t="8.175µs"  err="chain not synced beyond EIP-155 replay-protection fork block" X-Forwarded-For=nil
WARN [11-18|12:34:39.285] Served eth_chainId                       conn=192.168.219.206:56260 reqid=0 duration="7.744µs"  err="chain not synced beyond EIP-155 replay-protection fork block"
WARN [11-18|12:34:41.498] Snapshot extension registration failed   peer=182c008a err="peer connected on snap without compatible eth support"

New Enhancements

New api for adding wallets with password.
so that each will have differnent wallet and they can get unlimited addresses for that wallets.
Backup .sqlite to upload somewhere ( telegram bot , webhook, etc.. ) every 1 hour like that.
get server info in UI like stats for that docker , ram usage, memory.

User management also would be good one.
whitelisting ip's for accessing user wallets.
if not auto-payout then user needs to send password for payout, pass not needed for generating addresses.

get balance of custom user wallet
for payout it need to ask for password verification for users.
rpcwallet add this ... multiple wallets.
and one more option download the backup of all wallets.

Bug: no notification at delay

my tron wallet was in the process of syncing. the payment came to him. shkeeper didn't find it right away. after 40 minutes, shkeeper processed this wallet. and removed 15 TRX from it. but my system didn't get a blackout. also, this withdrawal from the timeone wallet was not included in the list of payments(/transactions)

[SUPPORT REQUEST]

Hello,

according your Docu: https://shkeeper.io/kb/start-to-work/documentation-on-launching
i just tried to install SHkeeper on my local VMWare Ubuntu 20.04


root@ubuntu:# curl -sfL https://get.k3s.io | sh -
[INFO]  Finding release for channel stable
[INFO]  Using v1.24.4+k3s1 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.24.4                                                                                                                                                             +k3s1/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.24                                                                                                                                                             .4+k3s1/k3s
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Skipping installation of SELinux RPM
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating /usr/local/bin/ctr symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/s                                                                                                                                                             ystemd/system/k3s.service.
[INFO]  systemd: Starting k3s
root@ubuntu:# ln -s /etc/rancher/k3s/k3s.yaml /root/.kube/config
ln: failed to create symbolic link '/root/.kube/config': No such file or directo                                                                                                                                                             ry
root@ubuntu:# mkdir -p $HOME/.kube
root@ubuntu:# ln -s /etc/rancher/k3s/k3s.yaml /root/.kube/config
root@ubuntu:# curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 |                                                                                                                                                     bash
 % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                Dload  Upload   Total   Spent    Left  Speed
100 11156  100 11156    0     0  27613      0 --:--:-- --:--:-- --:--:-- 27545
Downloading https://get.helm.sh/helm-v3.9.4-linux-amd64.tar.gz
Verifying checksum... Done.
Preparing to install helm into /usr/local/bin
helm installed into /usr/local/bin/helm
root@ubuntu:# helm repo add vsys-host https://vsys-host.github.io/helm-charts
"vsys-host" has been added to your repositories
root@ubuntu:# helm install my-shkeeper vsys-host/shkeeper
NAME: my-shkeeper
LAST DEPLOYED: Fri Sep  2 09:11:31 2022
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
root@ubuntu~:~# kubectl get pods -n shkeeper
NAME                                   READY   STATUS              RESTARTS   AGE
shkeeper-deployment-5f979f46fc-tsfz5   0/1     ContainerCreating   0          27s
dogecoind-deployment-964cc57c9-hjtxm   0/2     ContainerCreating   0          27s
litecoind-deployment-d978668f6-b8gx9   0/2     ContainerCreating   0          27s
bitcoind-deployment-8597459577-vccs4   0/2     ContainerCreating   0          27s


Unfortunately i can't reach the Login Page:
Login: http://192.168.202.129:5000/

By the way, i will much better if can provide a installation script for SHKeeper.

And how about securing to GUI with SSL ? Is the are a solution as well ?

Helm chart - Secret "password" is missing in shkeeper-btc-key

I am getting the following error when I try to deploy using the helm chart:
Warning Failed 10s (x3 over 28s) kubelet Error: couldn't find key password in Secret shkeeper/shkeeper-btc-key

I checked the chart and it doesn't seem to have a "password" key inside of it, however it is being referenced in the deployment of dogecoind.yaml.

image

And here is the secret shkeeper-btc-key

image

how to deploy shkeeper.io

I've tried to enable tron and tron-related coins like this:

tron_fullnode:
  enabled: true
  url: http://fullnode.tron.shkeeper.io

trx:
  enabled: true
usdt:
  enabled: true
usdc:
  enabled: true

But the server status in the wallet tab is Offline. Is this expected? There are some tron and java related processes running.

I've also tried adding ethereum support:

eth_fullnode:
  enabled: true
  url: http://ethereum:8545
  mainnet: true
  nodeSelector: {}
  tolerations: []

ethereum_shkeeper:
  image: vsyshost/ethereum-shkeeper:1.0.9

eth:
  enabled: true
eth_usdt:
  enabled: true
eth_usdc:
  enabled: true

But the status is also offline. I can see geth synchronizing in the background. Is this expected?
There is no documentation available, i've gathered these settings from older github issues, so they are probably out-ot-date.

TypeError: list indices must be integers or slices, not NoneType

helm-charts
commit 00c9520d31a619aa9901a31805910c0bb01e35f7 - error
I rolled back to the committee f0b4312bb16e881d4fee29168ab8a373c9eac08f , everything works there

kubectl -n shkeeper logs tron-shkeeper-7784758d54-nmvsx --tail 100

10.42.0.167 - bitcoind-user [01/May/2023:04:59:40 +0000] "POST /USDC/status HTTP/1.1" 200 81 "-" "python-requests/2.28.1"
[2023-05-01 04:59:40,970] WARNING <ThreadPoolExecutor-0_0 Thread>: Exception: Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1820, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1796, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
  File "/app/app/api/views.py", line 48, in get_status
    last_seen_block_num = bs.get_last_seen_block_num()
  File "/app/app/block_scanner.py", line 87, in get_last_seen_block_num
    last_block_num = self.get_current_height()
  File "/app/app/block_scanner.py", line 98, in get_current_height
    n = ConnectionManager.client().get_latest_block_number()
  File "/app/app/connection_manager.py", line 29, in client
    return cls.get_instance().get_client()
  File "/app/app/connection_manager.py", line 48, in get_client
    client = self.get_client_for_server_id(server_id)
  File "/app/app/connection_manager.py", line 52, in get_client_for_server_id
    provider = HTTPProvider(self.servers[server_id]['url'])
TypeError: list indices must be integers or slices, not NoneType

Add estimated fee to payout page

Add a table to payout page for bitcoin-like cryptos (BTC, LTC, DOGE) which will show amount of fee needed for the transaction to be included in next 1,5,10 blocks. Fee estimation can be performed by estimatesmartfee api method.

how install tron

I started shkeeper with tron. I started java-tron in docker, threw the settings in values.yaml. I started helm and it gives me the error "Internal Server Error" when going to the page /payout/USDT

values.yaml

tron:
  server:
    host: 'localhost'
    port: 50051

usdt:
  enabled: true
usdc:
  enabled: true

On aarch64

Is this project supported on ARM aarch64?

kubectl get pods -n shkeeper


NAME                                    READY   STATUS                       RESTARTS        AGE
shkeeper-deployment-69567f545b-xr7kr    0/1     CreateContainerConfigError   0               5h30m
mariadb-9f5b8c9c-g2kcn                  1/1     Running                      1 (2m48s ago)   5h30m
litecoind-deployment-6654d9db44-sqc2n   0/2     CreateContainerConfigError   0               5h30m

Events:
  Type     Reason          Age                      From     Message
  ----     ------          ----                     ----     -------
  Normal   Pulled          4m9s (x1510 over 5h29m)  kubelet  Container image "vsyshost/shkeeper:1.1.20" already present on machine
  Normal   SandboxChanged  77s                      kubelet  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled          3s (x8 over 76s)         kubelet  Container image "vsyshost/shkeeper:1.1.20" already present on machine
  Warning  Failed          3s (x8 over 76s)         kubelet  Error: couldn't find key password in Secret shkeeper/litecoin-rpc

Events:
  Type     Reason                  Age                       From     Message
  ----     ------                  ----                      ----     -------
  Normal   Pulled                  18m (x1495 over 5h32m)    kubelet  (combined from similar events): Successfully pulled image "nginx" in 4.091941509s (4.091954509s including waiting)
  Normal   Pulling                 8m57s (x1355 over 5h34m)  kubelet  Pulling image "nginx"
  Warning  FailedCreatePodSandBox  6m1s                      kubelet  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a7e3edc3fa3d3f843cf50f382833c58bd26de63a607327916c3c68c93195e27a": plugin type="flannel" failed (add): open /run/flannel/subnet.env: no such file or directory
  Normal   SandboxChanged          6m (x2 over 6m1s)         kubelet  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulled                  5m57s                     kubelet  Successfully pulled image "nginx" in 1.4793832s (1.47940056s including waiting)
  Normal   Pulled                  5m55s                     kubelet  Successfully pulled image "nginx" in 1.29175s (1.29176256s including waiting)
  Normal   Pulled                  5m39s                     kubelet  Successfully pulled image "nginx" in 1.26967808s (1.2696854s including waiting)
  Normal   Pulled                  5m25s                     kubelet  Successfully pulled image "nginx" in 1.335734696s (1.335741976s including waiting)
  Warning  Failed                  5m25s (x4 over 5m57s)     kubelet  Error: couldn't find key password in Secret shkeeper/shkeeper-btc-key
  Normal   Pulled                  5m25s (x4 over 5m57s)     kubelet  Container image "vsyshost/litecoind:0.21.2.2" already present on machine
  Warning  Failed                  5m25s (x4 over 5m57s)     kubelet  Error: couldn't find key password in Secret shkeeper/litecoin-rpc
  Normal   Pulled                  5m10s                     kubelet  Successfully pulled image "nginx" in 1.259559322s (1.259566962s including waiting)
  
```Normal   Pulling                 55s (x23 over 5m59s)      kubelet  Pulling image "nginx"

Is it correct to clean the memory?

I have BTC LTC DOGE running and synchronized. but I see a lot of occupied "space" for different kube containers
it seems to me that the previous images of my containers remain in the system after the containers themselves have been destroyed
otherwise, I don't understand why I have 200+ GB occupied only by kube containers. when you said that BTC+DOGE+LTC = 15GB

is this normal, or is there some kind of memory cleanup feature?

P.S. if I'm wrong, excuse me in advance, I don't understand so well what is kube and linux

P.S.S all these "spaces" are active, now they have changed their size from 29 -> 30 GB, all without exception. and even more space was occupied

# df -h
Filesystem                         Size  Used Avail Use% Mounted on
tmpfs                              1.2G  3.2M  1.2G   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv  5.3T   29G  5.1T   1% /
tmpfs                              5.8G     0  5.8G   0% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
/dev/sda2                          1.8G  253M  1.4G  16% /boot
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/051593ef0a514663729f7719498ceb03545a72ad9cf1b05d6ec78050653f8a6c/shm
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/3610cb450964835a3a49d4762596d71a68e9741d7704ec219226e9de7d1da75a/shm
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/051593ef0a514663729f7719498ceb03545a72ad9cf1b05d6ec78050653f8a6c/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/3610cb450964835a3a49d4762596d71a68e9741d7704ec219226e9de7d1da75a/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/d8b587f296604ac5c44ee91e7990b0d986b73c086e77414fd2883b28ac58046f/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/a3113fc07392df1c72b279dbf795894c1877cae8cac7e497fc9caa47ed1269bd/rootfs
tmpfs                               12G   12K   12G   1% /var/lib/kubelet/pods/af5c695b-8208-49f8-b8ba-69a8e5097c6d/volumes/kubernetes.io~projected/kube-api-access-c9ttr
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/957eab3ec9e046f12d0e04b8f79e09acb09e3d6e7e154500401b078cfda91bcb/rootfs
tmpfs                              170M   12K  170M   1% /var/lib/kubelet/pods/da16344a-2903-4b5b-ab2e-963c7ebc5b59/volumes/kubernetes.io~projected/kube-api-access-tmkjm
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/2a95dd1cbc250e3935a9deab1f80f52d8bc3654ce7ba42de22688117408e2e94/shm
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/2a95dd1cbc250e3935a9deab1f80f52d8bc3654ce7ba42de22688117408e2e94/rootfs
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/b8c52106ccc9b0e5a8793734a4dc4e0dced9629f2525a3f2d6d68ce07ac7d78f/shm
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/b8c52106ccc9b0e5a8793734a4dc4e0dced9629f2525a3f2d6d68ce07ac7d78f/rootfs
tmpfs                               12G   12K   12G   1% /var/lib/kubelet/pods/79bce365-41bd-4e33-99ab-e1d312f88124/volumes/kubernetes.io~projected/kube-api-access-xwn6h
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/b89abc97a402b9e943d259488af16508b0b4da8b7bf9d7c5fe6c0ee1585ce7df/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/ef67e9d38fcc99ea531a15ec44eff460085067a00c57020cc1c6985a5be8b7cd/rootfs
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/ee27ca2beaf45be27cc4b03e9b52eee6a0f2f161da505ba59c80bd59b37846ad/shm
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/ee27ca2beaf45be27cc4b03e9b52eee6a0f2f161da505ba59c80bd59b37846ad/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/4be7ae192848b2d8bb77269d316c5dbff6977c6e8a52479085b83bce4ff3a5ac/rootfs
tmpfs                               12G     0   12G   0% /var/lib/kubelet/pods/85912418-af58-48c9-9000-d559d2840650/volumes/kubernetes.io~empty-dir/backup
tmpfs                               12G   12K   12G   1% /var/lib/kubelet/pods/c4c70f11-9ae3-422c-beb4-a9aa11a0a81a/volumes/kubernetes.io~projected/kube-api-access-h7qbf
tmpfs                               12G   12K   12G   1% /var/lib/kubelet/pods/85912418-af58-48c9-9000-d559d2840650/volumes/kubernetes.io~projected/kube-api-access-vntgg
tmpfs                               12G   12K   12G   1% /var/lib/kubelet/pods/1a87bd97-a02d-4628-9c3b-90d4c6ee1e77/volumes/kubernetes.io~projected/kube-api-access-27p77
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/330a3e4ccae4e9486f52ada7b87a25a3a402a0ed12a276a1e8a9f2676b5d6de7/shm
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/620962c9e268f70eeeab94f57645b4d2ccf13e9300ac8afc2ab6e08c8a7ba45d/shm
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/330a3e4ccae4e9486f52ada7b87a25a3a402a0ed12a276a1e8a9f2676b5d6de7/rootfs
tmpfs                               12G   12K   12G   1% /var/lib/kubelet/pods/7f1fa26f-8aca-4fcf-97e9-af39525853ed/volumes/kubernetes.io~projected/kube-api-access-5bc24
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/2e006e2e0f054eaf78bf8cd5aa171cf16a1ed1f6467804f731e2d4b5ad24d9ba/shm
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/620962c9e268f70eeeab94f57645b4d2ccf13e9300ac8afc2ab6e08c8a7ba45d/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/2e006e2e0f054eaf78bf8cd5aa171cf16a1ed1f6467804f731e2d4b5ad24d9ba/rootfs
tmpfs                               12G     0   12G   0% /var/lib/kubelet/pods/4fd2f777-a5cd-45c9-88a1-bc066eb8e69f/volumes/kubernetes.io~empty-dir/backup
tmpfs                               12G   12K   12G   1% /var/lib/kubelet/pods/4fd2f777-a5cd-45c9-88a1-bc066eb8e69f/volumes/kubernetes.io~projected/kube-api-access-pvw6g
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/6a2f5beb6fce76394bcf414fc817c9a5a74e395a8d6396200dce638644241228/rootfs
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/4ccd175aea70cd55954ec733f978185f80a2483221ae3e524b9df07f906d0c64/shm
tmpfs                               12G     0   12G   0% /var/lib/kubelet/pods/28cf44fd-c9e2-41b0-8cce-1cd126630e84/volumes/kubernetes.io~empty-dir/backup
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/b20c91af0d825c901b55b90911b91eecaa29172312b304edc7894bed7fd6a0de/shm
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/4ccd175aea70cd55954ec733f978185f80a2483221ae3e524b9df07f906d0c64/rootfs
tmpfs                               12G   12K   12G   1% /var/lib/kubelet/pods/28cf44fd-c9e2-41b0-8cce-1cd126630e84/volumes/kubernetes.io~projected/kube-api-access-lt22f
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/b20c91af0d825c901b55b90911b91eecaa29172312b304edc7894bed7fd6a0de/rootfs
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/dd01c416c601afdeb17dd680b72dec09c0f87ed0e4f6a01db9a42d657eb6a755/shm
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/2f94aa9ba00204365b91d07843dc48e3cff896ce8d1abae552f3d2d9f08613d9/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/dd01c416c601afdeb17dd680b72dec09c0f87ed0e4f6a01db9a42d657eb6a755/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/c7ca28ae2e83c203736416d7449e2ed32a884ff9e8e8c32fe7203d8a906eb9cd/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/8e8629aeb69b5b606659b27245dc7b6db36f51f747371704742236e039b64ad0/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/fe5ace7993e926962f3238776ac95710222a66af16caf6579635c9da9a2e8802/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/a44ac297e71419aed4dd58f881a5ad2654074b55fe4c5a19c47b528e017bdbac/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/600c89b5fb7ae165ab2c8864a6c5d613609d20ea94fb7558789e3d0b96a29685/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/fd6886b3ae7707917cf5d726831b27bd016c28d46668e689f528a9de08fd377e/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/8d798df2ada5d0d6453428b904a64e0ee6ff66e5fc5d44805edbbed410d346da/rootfs
tmpfs                               12G   12K   12G   1% /var/lib/kubelet/pods/571d845d-b5c8-4625-9c73-e6dd8f2670af/volumes/kubernetes.io~projected/kube-api-access-bvnbz
shm                                 64M     0   64M   0% /run/k3s/containerd/io.containerd.grpc.v1.cri/sandboxes/e2efbdf02fede9865996118e7468149e7f9c3e2fabb9c5d347e6851f03cf6c5b/shm
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/e2efbdf02fede9865996118e7468149e7f9c3e2fabb9c5d347e6851f03cf6c5b/rootfs
overlay                            5.3T   29G  5.1T   1% /run/k3s/containerd/io.containerd.runtime.v2.task/k8s.io/d6a6343453a77182a19a6c619d2593ffea79b9dc43599db7bc2e9b663245316d/rootfs

TRON central wallet bag

I have 50 TRX on my balance(Fee-deposit account)

I created a payment for 10 USDT and paid. the transaction paid and it was displayed on the balance (and sent to the central wallet)

then I created another payment for 10 USDT and paid. but there are 10 USDT left on the balance, from the first payment

then I sent another 50 TRX(Fee-deposit account). but the second transaction was never transferred to the central wallet and was not added to the balance. 10 USDT remained on the second wallet

изображение
изображение

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.