[quote name=“groll” post=“26106” timestamp=“1377228042”]
[quote]No need to be extreme. 30 minutes is a safe bet.[/quote]
but time adjuted need to be lower then this it is actually 35 minutes. Else you can get attack that adjust time of clients to 35 minutes back than normal time block would be refuse by them. This require the attacker to get most of the connections of the client. This is possible, but difficult as you need to get many rogue clients in many subnet to do this. but we should play safe. the max future should be > time adjust allowed
[/quote]
I’ve thought about it [url=http://forum.feathercoin.com/index.php?topic=2847.msg22378#msg22378]earlier[/url]. nTimeOffset needs to be decreased accordingly. 20 minutes may be fine. Bitcoin uses 70 minutes, Litecoin has had halved it to 35 minutes.
[code=“util.cpp”]// Only let other nodes change our time by so much
if (abs64(nMedian) < 35 * 60) // Feathercoin: changed maximum adjust to 35 mins to avoid letting peers change our time too much in case of an attack.
{
nTimeOffset = nMedian;
}
else
{
nTimeOffset = 0;
[/code]
