Normally a card application implements certain countermeasures to protect contained assets from attacks. Like blocking a PIN code and thus use of a card until a PUK/unblock, deleting sensitive assets or terminating the card altogether. No PUK has been in design this far (maybe it should be added?) and wiping phonons is not what we want. Thus the only active countermeasure for attack detection is "do not allow to send phonons". Receiving and revealing phonons is not affected.
Normally a card application implements certain countermeasures to protect contained assets from attacks. Like blocking a PIN code and thus use of a card until a PUK/unblock, deleting sensitive assets or terminating the card altogether. No PUK has been in design this far (maybe it should be added?) and wiping phonons is not what we want. Thus the only active countermeasure for attack detection is "do not allow to send phonons". Receiving and revealing phonons is not affected.