Jacek Sieka

> Is there a benefit though? consider `array[1024, stint[16]]` / `openArray[stint[15]]` and so on > and so far the aim is to make the implementation ABI-compatible with `_ExtInt` in most...

> Is ABI compatibility necessary for size > 64? well, `_Extint` defines an ABI but it's not easily achieved, in particular when passing parameters (due to differences in `struct` vs...

> big-endian architecture these practically don't exist anymore, so the focus is on little-endian - the rest can follow if ever there's a usecase.

~~the same for seq would be nice, ie strings are pretty niche at the end of the day.~~ never mind, forgot that it was already fixed :)

ping, would be nice to see this PR merged

> message too big This is essentially a precondition that the caller knows about - I don't think `publish` is the right spot for this kind of error checking. >...

> finalized=2424:3abe601d this is the epoch number, ie 2424*32 = slot 77568 and the head in this log is at 77642 - there is no (significant) gap. the `epoch=9341` in...

> then stop this is not where the issue lies, generally .. ie something else is preventing finalized from being updated. There's no reason for the CL to "hold back"...

oof, you're right, forgot about the lc stuff :/

btw, now that the head block is stored in the database, memory consumption is not really a problem any more - block bodies can be stored in db for branches...