# BIP352: PSBT support

**URL:** <https://delvingbitcoin.org/t/bip352-psbt-support/877>\
**Category:** wg-silent-payments\
**Tags:** wallet, psbt\
**Created:** [May 17, 2024, 11:48am UTC](https://delvingbitcoin.org/t/bip352-psbt-support/877 "2024-05-17T11:48:32Z")\
**Posts on this page:** 1\
**Showing post:** 30

<div class="post-metadata">

**Author:** ![vazertuche](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/vazertuche/32/593_2.png) [@vazertuche](https://delvingbitcoin.org/u/vazertuche)\
**Post date:** [August 5, 2024, 9:35pm UTC](https://delvingbitcoin.org/t/bip352-psbt-support/877/30 "2024-08-05T21:35:18Z")

</div>

Have you considered also implementing the Anti-exfil protocol in secp256k1 library given that we are gonna require DLEQ proofs anyways in v3 of PSBT? It would make sense given that some of the top hardware wallets don’t come with any particular software wallet and will only implement things inherent in core, in the secp library and in a well tested and accepted psbt spec. The new [darkskippy.com](http://darkskippy.com) attack only re-iterates the need for things like this and I can’t help but think this new spec is an excellent opportunity to kill two birds with one stone?

---

_[View the full topic](https://delvingbitcoin.org/t/bip352-psbt-support/877)._