Marco Argentieri

> What are the advantages of enabling a socks5 proxy as opposed to using the http proxy? This means "tinkering" with the tor client configuration. I have use case in...

Fun fact, from that issue we ended up writing pkgs ourself for handling transactions/blocks :) https://github.com/vulpemventures/go-elements Not full node yet, altough working on a neutrino fork for Elements as well...

I am aware the reissuance token must be "blinded when spent" to grant powers to make a re-issuance. That being said, in the current transaction the original issuance is unblinded,...

The resulting raw transaction decoded says otherwise tho: - `commitmentnonce` is empty - `value` and `asset` are explicit I just ran again the script, you can reproduce it all the...

> the issue is hit even when you don't add the issuance, only the reissuance. I tried with Elements Core to do this instead (attaching an unblinded reissuance ) and...

> The output of rawissueasset will always be unblinded, because rawissueasset does not do blinding. The output I show in the previous comment [is the output of `signed_tx`](https://github.com/vulpemventures/liquidjs-lib/blob/issuance-mixed-reissuance/issuance-mixed-reissuance.sh#L55) so it...

Just for now, You can use `createrawtransatcion` and spend to an OP RETURN output

the current implementation of `destroyamount` AFAIR will lock in a OP_RETURN output the given amount (don't recall if it possible to blind with a bogus key)

Should we have a a command `importcontract` to make possible to make reissuance from asset issued somewhere else?

It may be slightly related, but I can't make a (blinded) re-issuance in the same tx where I am issuing a control asset. Also this useful in covenant scripts :)...