On Sun, Jan 12, 2014 at 02:49:00PM +0000, Amir Taaki wrote:
> Ahh yes, those errors aren't a problem. I thought the chain wasn't
> updating. I will downgrade those now to warnings so they don't seem so
> extreme.

The error message

> ERROR [poller]: Storing block
> 0000000000000028010d8b756cf7e9cbeb5f7b9925aac3b941f4553ea7483d29:
> Matching previous object found

is from line 124

    if (ec && info.status != block_status::orphan)
    {
        log_error(LOG_POLLER)
            << "Storing block " << encode_hex(block_hash)
            << ": " << ec.message();
        return;
    }

So commit 79d6eb0aebc600d262c293d561d02038102a3c6b won't do much,
although it does make sense to downgrade `block_status::rejected` to
warning anyway.

The blockchain continues updating, yes.