taproot – non-mandatory-script-verify-flag (Invalid Schnorr signature)

I am attempting to inscribe a Switch of BRC-20 ship an quantity of Bitcoin from and to a single handle. Would this attainable?

Sure you’ll be able to pay from an handle again to the identical handle, although clearly you might want to make an allowance for a payment, so the returned quantity is much less otherwise you want an additional enter to cowl the payment.

This isn’t what’s implied by the error message. It isn’t the supply of your downside creating a sound Schnorr signature.

    const script = [
        pubkey.toString("hex"),
        "OP_CHECKSIG",
        "OP_0",
        "OP_IF",
        toHexString(ec.encode("ord")),
        "01",
        toHexString(mimetype),
        "OP_0",
        toHexString(content),
        "OP_ENDIF",
    ].be a part of(" ");
    const leafScript = bitcoin.script.fromASM(script);

I am unfamiliar with this Javascript .fromASM operate. Presumably it provides the suitable opcodes for the implicit information pushes? For instance the pubkey.toString("hex"), has to finally be prefixed with opcode 0x20 because the opcode for pushing 32-bytes. I might test what .fromASM produces.

I am additionally puzzled by ec.encode("ord") – it appears to be changing a UTF-8 string to UTF-8 except your supply is definitely in some encoding that’s not a superset of 7-bit ASCII.

My understanding of the community encoding of the related script is at differentiate between BTC transactions and BRC20 transactions on a blockchain?