i was looking at the certificate system inside $SIGN CBDC setup again… and one small thing just kept bothering me every participant in the network — banks, operators — they all get a identity certificate
if something goes wrong… that certificate gets revoked access gone
participation stopped. .......clean control… atleast it looks like that
but then I start thinking about timing
because systems like this don’t really work in one step they move in flows. a bank doesn’t just send one transaction
it process batches
sign approvals
push multiple things at once
now imagine this
a bank signs a batch of transactions
everything is valid at that moment then seconds later…
Its certificate gets revoked
so now there is this weird gap the signatures are still valid but the participant is not allowed anymore nothing is broken but system still has to decide
do we accept those transactions…
because they were valid when signed?
or reject them…
because now the issuer is not trusted anymore?
and honestly both feels wrong
if accepted → a revoked entity still affecting the system
if rejected → valid transactions just disappear mid process
payments drop
no clear error
no clear reason
and this doesn’t really look like failure
it looks more like… inconsistency
because technically both sides are correct
that’s where I keep getting stuck
revocation sounds like a clean cutoff… but in real systems there is always this in between
a small window where status changes but actions are still moving
and that window… isn’t really defined clearly so the question becomes
when access is removed in real time…
what happens to everything that was already in motion?
because systems don’t just depend on rules
they depend on when those rules actually apply