Andrew Poelstra

@sanket1729 noticed that our `MoneyRange` check does not take differing assets into account, so you cannot create a transaction with more than 21MM total units of all assets. This is...

When we add bulletproofs we should also add a global transaction-wide 32-byte "scalar offset" field which is used to make the blinding factors all add to 0. This would greatly...

This is an issue in upstream as well, that signmessage/venifymessage only work with p2pkh. BIP322 is a proposed replacement but the specification isn't complete and it hasn't seen very much...

@achow101 the trick here is that they actually **don't** need to understand these fields at all, they just throw them onto the pegin witness stack as byte vectors (The specific...

Sorry for letting this issue sit so long. The wallet appears to be balancing the transaction correctly. The error `txns-in-ne-out` is a generic "something in CT validation failed" error, which...

Ok, so reading this code it actually looks like it's impossible to do a blind reissuance of an asset that was originall issued in a non-blinded way. The reason is...

The quoted line does not determine whether or not the reissuance is blinded, I think. This is decided by `blindrawtransaction` which defaults to blinding issuances.

The output of `rawissueasset` will always be unblinded, because `rawissueasset` does not do blinding. When blinding issuances, the wallet just generates a random blinding pubkey. The message sidechannel is not...

:( we really need to rewrite the wallet blinding logic

Do you have the transaction? Curious what the offending output(s) look like.