Web appOpen in Telegram
EeCash Node Support

eCash Node Support

@eCashNode · group · Crypto · indexed since 2026-07-15
137members
1 516messages in the index
K
Is there a web page where I can find node address to put into conf file as addnode=?
P
Running the new 33.7 node with your ckpool fork. Have about 130 in/out peers most of them low latency. Looking at the debug file I see a few issues I would like your insights on please:
P
1. Rejection of Invalid Blocks (policy-bad-rtt) 2026-07-13T06:10:54Z Park block because it violated a block policy: policy-bad-rtt, Block 00000000000000005e3e66fc4df3ce8409595c3ede2f431625b6e357986c8ff0 at height 957600 violates the real time target... 2026-07-13T06:10:56Z Avalanche invalidated block 00000000000000005e3e66fc4df3ce8409595c3ede2f431625b6e357986c8ff0 2. Brief Staking Reward Warnings (policy-bad-staking-reward) 2026-07-13T03:00:46Z Park block because it violated a block policy: policy-bad-staking-reward, Block ... violates staking reward policy 2026-07-13T03:00:49Z Avalanche finalized block 000000000000000020c3ea797c2372c98bf48ff969334e28a682cbcf68ac5d27 3. Stalled Avalanche Proof (f64541a2...) 2026-07-13T02:53:57Z Avalanche stalled proof f64541a217e0927c6dabb6eec0dd02e85679e1bbfcbe62e275a4bf9f4bf3f15c
  1. F
    1. means your node saw a block that violated the RTT policy, and the avalanche network agreed and invalidated the block. 2. means your node saw a block that violated the staking rewards policy, and the avalanche network disagreed and finalized the block 3. means your node polled for an avalanche proof that the peers typically did not know about so the vote was not conclusive. 1. can happen if a miner did not implement heartbeat (RTT) correctly, 2. and 3. are typical of a node restart (for 3. you likely loaded a previously connected proof that has been replaced since). They are not errors or issues but your node giving information about what is happening on the chain
Whole thread · 1 reply →
P
Thank you Fabien. Can the RTT issue happen if there is a time-sync issue? The reason, I looked into it because I have been running the setup in the past 4 days with 1.8Ph ASICs pointed on the pool. I fished out 8 blocks in the first 24 hrs and zero in the past 3 days.
  1. F
    It depends on the pool implementation, it can happen if the RTT algo is implemented at the pool. But with the ckpool fork the RTT value is computed by the node so no sync issue. Note that the above rejected blocks from your logs are not yours, it's unrelated to your pool.
  2. F
    Can you point me to some of your blocks ? You can DM me if you want to
Whole thread · 2 replies →
G
Link
click to show
Why do the e.cash/staking page says to not use Tor for the staking node, even though Tor (and proxy in general) options are integrated into Bitcoin ABC ? Is it still not possible to use Tor for a staking node, even with the proxy options in Bitcoin ABC ?
  1. F
    A staking node needs to be discoverable and reachable by all the peers on the network, so it's not really conpatible with the use of TOR
    1. G
      Does that mean that the tor proxy options in Bitcoin ABC should not be used at all for staking nodes ?
Whole thread · 3 replies →
  1. E
    🔄 Translation: "The top-up didn't arrive"
Whole thread · 1 reply →
  1. E
    🔄 Translation: "Sent it and it didn't arrive"
  2. K
    I am sorry, but I don't think this is related to our project /translate russian
    1. E
      @eKoush "Извините, но я не думаю, что это связано с нашим проектом"
Whole thread · 3 replies →
A
Photo
click to show
Node upgrade done ✅ SoloFury is now on Bitcoin ABC 0.33.9 across all regions. Supporting eCash solo miners with direct coinbase payouts — solofury.com

An open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.

Public content only, official Telegram API. About · FAQ · What we do not do · Remove a page · Catalog · Search · How we count