Another possible solution:

when no new blocks are seen for a given time frame, the daemons themself generate one special block at the configured lowest difficulty.

Characteristics of the block:

no coins generated no transactions are contained

That way a new difficulty can be calculated /announced after the hash rate drops dramatically and the time to block can be limited without breaking the protocol.

For sure there are complications in this solution, that need to be addressed.
This is a high level idea only

If it is worth the money, is your own decision. It is like buying shares, nobody can tell tomorrows share value.

You may win or loose

Never try to predict the price of a crypto coin ;)

got it, I had already just made a fresh install on a new pc and started messing with the wallet.dat file there once i had my coins moved over. (removing it, replacing it… seeing what happens etc) but its good to know i can just do it on 1 pc in the future. thanks!

while this has been a great learning experience and fun to host for the community, I am unpinning this as we now have a full Feathercore / bitcore port thanks to @Bushstar

This was a very old repo and should no longer be used.

Have an updoot, sir!

Cheers :)

Hi @curiosity81

Thanks for this suggestion, I’ve raised it with our Team.

@wellenreiter

I post an issue on github. Could you please check it? :)

I’d need to ask @Bush to see if he built the release binaries with UPNP.

It’s quite possible they weren’t built with it so in that case you’d need to build the client yourself.

Welcome to openSource :)

How you wanna get even 200k listing fee?

We have to be more careful, 2fa is a great way to increase security

@acidd

you dont have to apologize, man… its no big deal to me. i am just trying to give you guys a heads up.

6fb52561cb7022a46c02a30ae53bfcc9e1d1887010f795f75cfeda5b4610156d

I should ad, it doesn’t mean I won’t do it …, I haven’t decided yet . Depends on other unrelated projects. If I did do it, it would likely be just to see if I could . Probably the only way to make such a system feasible is to design a coin that requires a ui/cpu only (ever) to be mined .

Great, you sorted it out. Thanx @Wellenreiter

@jimmy24651

Not sure for windows, but:

open a command window (cmd) type ‘netstat /help’ or ’ netstat --help’
not sure about the right syntax from the output locate the parameters to show listening ports only (in linux -l) (lowercase L) use numeric values ( in linux -n) show process information ( in linux -p) issue the netstat command again with the parameter you found out locate the line(s) with ‘127.0.0.1:9336’ identify the process listened at the end of the line open a process monitor window (strg-alt-del) and select process display right click on the process you found in the first step select stop process

If that doesn’t work for you I hope some windows guys can help.

Quote from the test:

“I can provide some info here as I was the “attacker”. I simply setup a loop to send dust to another address I control. I used my VPS as the sending wallet so the loop probably just ran as fast as the VPS would allow which could be why it limited it to 1100 transactions per block. It could also have hit the block limit of 1mb, but I’m not sure how to tell if that was the case or not. I honestly thought it would be a lot higher than 1100.”

So it might have been the block limit. Or just the vps. But with segwit the possible tx/s will increase anyway. And we can already handle a very large amount of transactions.