been digging on SOLANA and ETH chart and also into the X.509 certificate layer inside the SIGN CBDC network since last night and honestly the revocation mechanic is the part i cant stop poking at 😂
so every participant gets a certificate from the central bank certificate authority. commercial banks, node operators, everyone. want to join the network. get a cert. central bank controls who gets one. clean governance model
and revocation is the emergency control. bank goes rogue. cert gets puLled.. access cut.done.except.
what about transactions that were already in flight when the cert was pulled. a commercial bank endorses a batch of transactions.those endorsements are cryptographically valid - the cert was live when they signed . two seconds later the cert gets revoked.
does the network honor those endorsements or reject them.
if it honors them - a revoked participant's approvals are still processing after their access was cut. the revocation didnt fully stop them.
if it rejects them - valid in-flight transactions get dropped mid-process. citizens payments disappear with no clear failure signal.
the docs describe certificate revocation as the mechanism for removing participants. they dont describe what hapens to work that participant already signed before the revocation landed.
honestly dont know if X.509 revocation here is a clean hard cutoff or a soft boundary with an in-flight window the design hasnt fully closed?? 🤔
#SignDigitalSovereignInfra @SignOfficial $SIGN
