nil interface gets serialized as '<invalid Value>'

It seems a special case was missed.

Fixing this properly would break existing implementations.

I need to think of a way to catch this, and not break backwards compatibility.