Simplifies BIP-322 to ONLY address signing/verifying a message, removing traces of proof-of-funds. Also adds some missing fields that were asked for, such as lock time and sequence.
The intention is to make a separate BIP which builds on top of this one for the proof of funds part.
Edit: I am still trying to figure out this and a separate BIP which addresses the proof of funds part. Not ready for merging yet.
@kallewoof Been trying to do a proof-of-reserves BIP with another approach: https://github.com/stevenroose/bips/tree/por
It has an optional PSBT extension for integration too. I'm finishing it up in order to write to the mailing list. Any early feedback would be appreciated.
@stevenroose I haven't looked at your proposal yet, but it feels like the two standards are very closely related and everyone would benefit from them being integrated with respect to each other. I have a work in progress for proof of funds already on my end, but having two proposals can only be good for the community as long as they're judged purely on their merits.
That being said, please keep BIP 322 compatibility in consideration in your proposal.
But the proposal I worked out has nothing to do with signed messages. The proofs are just serialized transactions. And yeah, I totally agree we should compare proposals and try to reach some form of consensus. Do you have anything public about your proposal?
Oops, this isn't really the place for WIPs... @kallewoof Do you want this reverted?
Sorry for late reply -- yes, sorry I should've closed this until I had time to actually work on it. Please revert. Sorry for the trouble.
Reverted