# OP\_CHECKSIGFROMSTACKVERIFY ECDSA useful?

**URL:** <https://delvingbitcoin.org/t/op-checksigfromstackverify-ecdsa-useful/438>\
**Category:** Protocol Design\
**Created:** [January 19, 2024, 5:50am UTC](https://delvingbitcoin.org/t/op-checksigfromstackverify-ecdsa-useful/438 "2024-01-19T05:50:08Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![reardencode](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/reardencode/32/27_2.png) [@reardencode](https://delvingbitcoin.org/u/reardencode)\
**Post date:** [January 25, 2024, 11:38pm UTC](https://delvingbitcoin.org/t/op-checksigfromstackverify-ecdsa-useful/438/6 "2024-01-25T23:38:55Z")

</div>

That makes sense to me. For example, if we do reactivate CAT similar PoW proofs could be done with plain hashes.

```auto
stack: <nonce> <hash_prefix>
script: <required_hash_suffix> CAT SWAP <preimage_suffix> CAT SHA256 EQUALVERIFY

```

(probably missing some details in ^ by allowing any length nonce, but it’s the general idea)

In short there are better ways to achieve this than ECDSA (which matches my gut reaction).

---

_[View the full topic](https://delvingbitcoin.org/t/op-checksigfromstackverify-ecdsa-useful/438)._