interesting times.....
at our team 4-6 people are busy analyze and counter ur attempts
how big is ur team?
what exactly u try to achieve?
u know we never give up since close to 2 years?
try to break dmd before code changes go active?
u will have no luck
just a bit over 6000 blocks
3 days
u cant stop us
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FK5Sfawr.png&t=665&c=8MMPOsCYQhXETA)
in times like this a community have to stay close side by side
thx for ur support
sure additional pools would be welcome
not because of over 50% hashrate because thats no issue
the pool is managed by our main dev
but because its a single point to attack
more pools are welcome where is miningfield and donkeypool
get ur pools up again and people distribute ur hashrate across the pools
what users can do help our efforts in this battle?
u can change bantime=36000
the old 600 setting was helping against other attack pattern
but actual its more damaing than helping because
the bad block sending nodes only get banned for 10 min each time
if u have good node try get a listen=1 and addnode config running and support network relay good data
but adapt bantime=36000
but with that config u need to check that ur node stay on right chain if u land in fork u have no chance rejoin mainnet becaiuse u will them block all good nodes for to long
people who have no time active monitor their wallet and support our battle
why not just stop ur wallet and wait until weekend when trigger is over and victory will be visible
for now worst case u act as helper of an attack by relay bad blocks if u not able active watch ur wallet
again thx for support of community
we gave a lot for u please give us back a bit
at least moralic support in middle of battle
and dont cry bullshit unstable network
because any non active maintained coin would be broken since 2 days.......
we stand and fight and no way we can lose the battle
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fwww.quickmeme.com%2Fimg%2Feb%2Febe30aa90ee7fe261333e407d720eb3bfc9eef8972cf56e42a4fd40b1ef80c51.jpg&t=665&c=AWLyD2PPaWdK1A)