Ok, maybe i have not been clear enough & obviously not technical in this regard.
My query "Have there been a 'control' check to see if there is a potential bug/exploit" specifically for the dig process with clam clinet, BTC is not a proof-of-stake coin so i don't see the relevance.
- Due diligence is all that is asked
I think you have been plenty clear.
Maybe I have not.
Check
what, exactly?
check to see if there is a potential bug/exploit" specifically for the dig process
There is no
"dig process".
A "dig" is nothing more than a transaction.
BTC is not a proof-of-stake coin so i don't see the relevance.
A "dig" transaction is secured by the same
asymmetric key cryptography that is used in BTC.
It is, in fact, a standard transaction.
It is very relevant.
If someone can sign a transaction to "dig" an output, without the private key which corresponds to the output/public key - then they can steal every CLAM, BTC, LTC, etc. in existence.
Proof-Of-Work/Proof-Of-Stake, used to secure the state of the chain, is not related.
- Due diligence is all that is asked
The chain is reviewed daily by multiple parties who have an interest in the system.
The code in question deals with standard asymmetric key signatures.
If there is an "exploit" - then you, and the world, have bigger problems than CLAM.