This is a project for some more advanced coders with C++ experience.
BIP-322 is a proposal by @kallewoof that extends the old legacy single-key signing of messages, to sign or partially sign a message for any Bitcoin script from which they could conceivably spend.
Potentially @kallewoof might be up for mentoring interns tackling this project.
@wip-abramson has also offered support:
I am also happy to support/work with anyone taking this on. I have been exploring this bip for the past month or so on behalf of Digital Contract Design. I have developed a separate implementation using Jimmy Song's buidl-python library. Currently, this exists in a set of Jupyter notebooks - https://github.com/LegReq/bip0322-signatures, which I would be happy to go over with people. I think it should be a useful tool for understanding how bip322 signatures work in practice - especially for those not well versed in c++.
At some point I plan to submit a P.R. to add this implementation to the buidl-python bitcoin library.
This is a project for some more advanced coders with C++ experience.
BIP-322 is a proposal by @kallewoof that extends the old legacy single-key signing of messages, to sign or partially sign a message for any Bitcoin script from which they could conceivably spend.
There is a https://github.com/bitcoin/bitcoin/pull/16440 to update bitcoin-core that has been languishing for some time, but it should be possible to leverage code from @kallewoof's Bitcoin Script Debugger to make a standalone tool that can sign messages.
Potentially @kallewoof might be up for mentoring interns tackling this project.
@wip-abramson has also offered support: