swerving the issue is not assuring anyone. all I am asking is for simple reassurance that block 0 is an empty block
i care about this issue, as do others.
block 0 contains 1 transaction: a87d9a593e3e65e96f44be39270e0d0e604e26f1fd567d72306579f3f34c19dd
this transaction is not readable by the client. (and the block-explorer will just always show 404 whenever the daemon sends an error, like for this transaction inside the block).