We are aware of the problem, and discuss possible actions.
All actions mean a change in Neoscrypt or a change of the mining process.
This needs to be discussed and decided carefully, so don’t expect a solution within a week or two.
Watever is decided the changes will be implemented in code version 0.19 or 0.20, as extended tests will be required before implementing on the main net.
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.
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 .
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.
@jonathonas said in Feathercoin comes out as a gold rated coin on Cryptopia.:
Is it just me who couldn’t find the “Gold rate” in that photo? I think cryptopia might made some kind of mistake. Probably they forget to notice the hard fork.
It has 5 Gold stars and a 5/5 rating?