#baby $BABY @BabylonLabs_io
I dug back into the docs myself after writing about how nobody in a group could agree whether slashing hits delegators too, instead of just flagging the confusion and leaving it there.
I opened the official documentation first. The slashing section is short, it describes the punishable behavior, double-signing or equivocating, but doesn't state in one clear line whether delegator stake actually gets touched. I moved on to more technical writeups, then went straight into the community channel to ask directly.
The answer I got wasn't wrong, but it wasn't fully clear either, something like "the mechanism is designed to concentrate risk on the provider side," not a flat "delegators are completely safe." I reread it three times to make sure I wasn't misreading the intent.
Technical point: what struck me wasn't a wrong answer, it was that the correct answer lives scattered across layers, docs cover part of it, community explanation fills in another part, and an ordinary user has to piece those fragments together to get the full picture. For a mechanism that decides whether you lose BTC or not, having to piece it together like that is a real barrier, not a minor inconvenience.
Self-critique: I had the advantage of knowing where to look and the time to reread things multiple times. Someone delegating for the first time, eager to start earning, almost certainly won't go through all the steps I just did, and will end up delegating with the same vague understanding they started with.
$BABY only pulls in capital that actually stays if delegators understand what risk they're carrying, not if they're just running on a feeling of safety.
I think Babylon needs one clear, definitive answer placed right at the delegation step, instead of leaving users to go dig for it the way I just did.
I dug back into the docs myself after writing about how nobody in a group could agree whether slashing hits delegators too, instead of just flagging the confusion and leaving it there.
I opened the official documentation first. The slashing section is short, it describes the punishable behavior, double-signing or equivocating, but doesn't state in one clear line whether delegator stake actually gets touched. I moved on to more technical writeups, then went straight into the community channel to ask directly.
The answer I got wasn't wrong, but it wasn't fully clear either, something like "the mechanism is designed to concentrate risk on the provider side," not a flat "delegators are completely safe." I reread it three times to make sure I wasn't misreading the intent.
Technical point: what struck me wasn't a wrong answer, it was that the correct answer lives scattered across layers, docs cover part of it, community explanation fills in another part, and an ordinary user has to piece those fragments together to get the full picture. For a mechanism that decides whether you lose BTC or not, having to piece it together like that is a real barrier, not a minor inconvenience.
Self-critique: I had the advantage of knowing where to look and the time to reread things multiple times. Someone delegating for the first time, eager to start earning, almost certainly won't go through all the steps I just did, and will end up delegating with the same vague understanding they started with.
$BABY only pulls in capital that actually stays if delegators understand what risk they're carrying, not if they're just running on a feeling of safety.
I think Babylon needs one clear, definitive answer placed right at the delegation step, instead of leaving users to go dig for it the way I just did.