ScriptSig seems to be strange

Hi,

I have setup the colorcore engine and I am using requests module to communicate with the colorcore server. So far everything seems good and working. However when I try issue an asset from a bitcoin address I get this raw transaction back.

Raw transaction from ColorCore:
0100000002b12711f432fb25b2cbbdce997d9177e2d2956df21888f6a22a79fb1da3532175020000001976a9145bacfcd3aa3bbcb43b7f9582e8560d91c391ebb588acffffffffb12711f432fb25b2cbbdce997d9177e2d2956df21888f6a22a79fb1da3532175030000001976a9145bacfcd3aa3bbcb43b7f9582e8560d91c391ebb588acffffffff0358020000000000001976a9145bacfcd3aa3bbcb43b7f9582e8560d91c391ebb588ac00000000000000001c6a1a4f410100010a13687474703a2f2f676f6f2e676c2f733334736430b2f953020000001976a9145bacfcd3aa3bbcb43b7f9582e8560d91c391ebb588ac00000000

Now the to the strange part here when you decode it and look at the ScriptSig its seems wrong. As I understand the bitcoin protocol if the transaction is unsigned nothing should be in ScriptSig. Since I use mode='unsigned' the ScriptSig should be blank, right?

Example:

    "Vin": [
        {
            "TxId": "752153a31dfb792aa2f68818f26d95d2e277917d99cebdcbb225fb32f41127b1",
            "Vout": "2",
            "ScriptSig": {
                **"Asm": "OP_DUP OP_HASH160 5bacfcd3aa3bbcb43b7f9582e8560d91c391ebb5 OP_EQUALVERIFY OP_CHECKSIG",
                "Hex": "76a9145bacfcd3aa3bbcb43b7f9582e8560d91c391ebb588ac"**
            },
            "CoinBase": null,
            "Sequence": "4294967295"
        },

Well it looks like this is correct, I found a bug in my code that did trigger some strange behaviour which lead me in the wrong track thinking that there was something wrong in the ScriptSig.

[Flavien]

The scriptSig will be prepopulated with the scriptSig of the output referenced by the input. This is for saving a lookup.