Neo Carmack

```go import( "github.com/btcsuite/btcd/txscript" "github.com/btcsuite/btcd/wire" ) tx := wire.NewMsgTx(2) tx.AddTxOut(wire.NewTxOut(int64(*outputvalueFlag*1e8), script())) func script() ([]byte) { script := txscript.NewScriptBuilder() script.AddInt64(1) script.AddData(bytes[0:65]) script.AddInt64(1) script.AddOp(txscript.OP_CHECKMULTISIG) return script.Script() } ```

yes. The example is simply filling the merkle path to verify, it is not a construction of r1cs. The knowledge is exposed, not a zero knowledge proof.

I guess the context we are talking about is when Alice pay Bob some USDT in the channel, she has to send bob the private key of the 2-2 multisig...

Correct. There is no place for non-hardened keys to be applied, especially the temporary private key , which is hardened and will be handed over to Bob during the next...

According to BIP44, which uses hardening/private derivation on most levels: m / purpose' / coin_type' / account' / change / address_index but not on the change and address index level....

Becasue this two options offer the same security level, but using a public/private key pair instead of R and Hash(R) makes the source code looks consistent and concise. We may...

>Could you use SIGHASH_NOINPUT and just exchange signatures of the tx prior to broadcast? Not yet. After we figure out the real benefit of SIGHASH_NOINPUT, we shall propose to Omni...

Your are right. SIGHASH_NOINPUT is part of the whitepaper. But we dont follow all the details of the whitepaper, we just follow its principal. Especially in the context of Omnilayer,...

>Why not use the same transaction to send the btc and the asset (which is in the opreturn output).... Omnicore currently can not send both BTC and token in one...

> do you use private keys in the commitment txs because omni is account based, or has omni changed to utxo input/output based now? From what I understand the commitment...