What keeps dragging me back to Sign is not whether the attestation travels.
Its how fast acceptance stops traveling with it.
Yes.. The acceptance on @SignOfficial .
Sign protocol's Cross-chain portability sounds great for about five minutes. Then the claim leaves home and people start reading the same object like it dragged the same liability everywhere with it. It didn't. It dragged the attestation. Different thing.
Portable, sure. Settled, not really.
On Sign $SIGN , the record can stay perfectly clean while the meaning around it starts splitting the second it crosses environments. Same issuer. Same schema. Same evidence pointer. Same neat object on SignScan. Chain A lets it through an eligibility gate. Chain B wants another check wrapped around it. A bridge flow treats it as enough. A partner on the other side says that issuer scope was for the original context, not this one.
Great. The argument is too.
And that spreads faster than people like admitting. One workflow already moved. Another one bounced the same claim. Ops is now staring at two valid-looking states with one extra offchain note glued on top because apparently reusable trust still needed local babysitting the second it hit a different environment.
Fine.
Cross-chain on Sign can move the object cleanly. It does not move shared institutional agreement with it. Same attestation path. Different relying logic. Different blame, too, once something gets challenged.
Usually after one side already moved the file.
Then local logic starts piling up.
One side adds a scope check.
Another adds issuer restrictions. Great actually.
Someone else keeps a side list offchain because nobody wants to say Sign's portable attestation stopped settling the portable decision.
Still the same record though.
Still... valid. Anyways.
Still moving.
Just landing in more places that won’t clear it without their own patch on top.