Before reading the explanation, I wanted to understand what the 80-byte limit actually changes.
A Babylon checkpoint is bigger than Bitcoin's OP_RETURN limit. Just over 100 bytes of data trying to fit into an 80-byte space.
So the checkpoint has to be split.
At first, that sounds like a small technical detail.
But it means every time Babylon anchors a checkpoint on Bitcoin, there is extra transaction overhead because of a rule Babylon cannot change.
The interesting part isn't that Bitcoin has an 80-byte limit.
It's that Babylon has to design around a rule that was created long before this use case existed.
Small constraint. Large consequences.
@BabylonLabs_io $BABY #baby
$BLESS $BANK
A Babylon checkpoint is bigger than Bitcoin's OP_RETURN limit. Just over 100 bytes of data trying to fit into an 80-byte space.
So the checkpoint has to be split.
At first, that sounds like a small technical detail.
But it means every time Babylon anchors a checkpoint on Bitcoin, there is extra transaction overhead because of a rule Babylon cannot change.
The interesting part isn't that Bitcoin has an 80-byte limit.
It's that Babylon has to design around a rule that was created long before this use case existed.
Small constraint. Large consequences.
@BabylonLabs_io $BABY #baby
$BLESS $BANK