How does Silverscript verify signatures in a Kaspa contract?

Silverscript provides two built-in functions for signature verification: checkSig(sig, pubkey) for single Schnorr signatures, and checkMultiSig for threshold signatures requiring multiple parties to sign. A Schnorr signature is a compact, efficient way to prove that the holder of a private key authorized a transaction — Kaspa uses Schnorr rather than the older ECDSA scheme used by Bitcoin. checkMultiSig extends this to "M-of-N" arrangements, where, for example, any 2 out of 3 designated key holders must sign before a contract action is allowed. For beginners, this means Silverscript contracts can enforce who is allowed to move funds, including shared-custody setups, entirely in on-chain code.