Quote from: gjhiggins on June 19, 2021, 01:22:32 PM

Uh-huh, networkhashrate has collapsed.

Is for this reason that the last mined block was #4027220 at 2021-06-21 09:16:58 UTC ?

This morning graymines had 8 workers, now just 1.

It looks like someone is doing this:

Quote from: minerja on June 02, 2021, 03:53:30 PM

-cut-
I could be entirely wrong, but about 3 years ago i had a similar experience, i mined a cpu only coin....its block time was every 2 minutes, but literally no-one was mining it, so the global hash was 1KH/s, i could acheive 65KH/s with just 1 core....so i would solo mine it with 12 threads for approx 3-4 hours, mining a block about every 1-4 seconds, within that 3-4 hours i had mined over 100,000 coins, and then the diff would jump 10 fold, so i would stop, and come back 1-2 weeks later.....when i would find the blocks were coming 1 every 2 mins, and the diff was down at 0.00002414, so i'd repeat.....worked great for about 1 month or 2, then the other miners left, i broke the chain, and couldn't send coins to the 1 and only exchange.
-cut-

More likely, the miner dLeqozLLkdKAQSFJ7evtWCiWNoFcArHngK rightly stopped its activity because he did not receive any DTC due to its segwit address for the payouts.

So, if I understand how PoW works, now we need to wait that someone finds a block at this difficulty. Only then the network will retarget the difficulty at a lower value.

Quote from: gjhiggins on June 19, 2021, 01:22:32 PM

-cut-
I recovered CrossVerse's "madpool" addition, after finally figuring out what it was all about.
It adds a pool server to the client and disables in-wallet mining, allowing the client to act as a local pool server to a local xpmclient GPU mining pool client.
-cut-

I also studied it, because I would like to set up a Datacoin mining pool on ByteStamp servers. But it drove me crazy.

Let me know about it.

Quote from: gjhiggins on June 15, 2021, 04:02:49 PM

Latest list of recently-seen nodes, edited from bytestamp's peers list

-cut-

Edit:
Meh, I fed them into my client, which can only connect to:
addnode=144.76.64.49 addnode=51.148.146.204 addnode=91.250.62.26
So yeah, there were only two listening nodes, now three
-cut-

ByteStamp itself should be a listen node, but obviously ByteStamp does not see itself as a peer.

It should be reachable with

Code:

addnode=dtc.bytestamp.net:4777

Please let me know if it works.

ByteStamp is on your 0.16.3 client since February 2021.

But, what is the "View Bytestamp Record" button supposed to do?

It does nothing...

Last but not least, what about to bring Datacoin to a new level?

What I mean is:

smart contracts running on Datacoin blockchain

Sorry for my annoying post , I don't have much time, so I concentrate everything at once.