Mapped how Babylon checkpoints itself onto Bitcoin against two other projects doing something similar Pikachu and Nomic because Babylon's own materials name both as comparison Points.
Babylon's method validators sign the digest of each PoS block one relayer aggregates the Signatures using BLS then packages everything into a Bitcoin transaction using OP RETURN.
Two transactions per checkpoint each carrying at least one OP RETURN output verified Against Trustless Bitcoin Vaults TBV style light client proofs on the receiving eNd.
Pikachu built by Protocol Labs for Filecoin Uses a similar OP RETURN approach but Babylon's blog specifically calls its own version simpler more timely and more flexible bY comparison.
Nomic takes a different Route entirely using this checkpointing style specifically to manage the Bitcoin backing its nBTC token rather than for general PoS security.
One real constraint applies to all OP RETURN based approaches though. Bitcoin caps OPRETURN data at 80 bytes, so encoding a growing validator set means checkpoint transaction Count scales up linearly as m0re validators join.
So the design tradeoff isn't really "better or worse" between these three its more about what eac h one Optimized for general PoS security for Babylon Filecoin specifically for Pikachu and backing a wrapped token for Nomic.
$SKY $BLESS $BIO
Babylon's method validators sign the digest of each PoS block one relayer aggregates the Signatures using BLS then packages everything into a Bitcoin transaction using OP RETURN.
Two transactions per checkpoint each carrying at least one OP RETURN output verified Against Trustless Bitcoin Vaults TBV style light client proofs on the receiving eNd.
Pikachu built by Protocol Labs for Filecoin Uses a similar OP RETURN approach but Babylon's blog specifically calls its own version simpler more timely and more flexible bY comparison.
Nomic takes a different Route entirely using this checkpointing style specifically to manage the Bitcoin backing its nBTC token rather than for general PoS security.
One real constraint applies to all OP RETURN based approaches though. Bitcoin caps OPRETURN data at 80 bytes, so encoding a growing validator set means checkpoint transaction Count scales up linearly as m0re validators join.
So the design tradeoff isn't really "better or worse" between these three its more about what eac h one Optimized for general PoS security for Babylon Filecoin specifically for Pikachu and backing a wrapped token for Nomic.
$SKY $BLESS $BIO