pobtoken burn_coins with the -t flag

[buhtignew]

I've tested pobtoken burn_coins 1 -t 5 and have produced the transaction 2fd6f150d891176cb6eccd09c2e4a3a084d97dc41a7fe7351923cdf09dfcc7bb.

My address balance before the transaction was 2289.77.
The transaction show 2fd6f150d891176cb6eccd09c2e4a3a084d97dc41a7fe7351923cdf09dfcc7bb -s output is:

{
    'inputs': [
        {'sender': ['n3MtPoPaAREU5GEhAErBPuju83bVog2opz'], 'value': 0.01},
        {'sender': ['n3MtPoPaAREU5GEhAErBPuju83bVog2opz'], 'value': 103.27}
    ],
    'outputs': [
        {'receivers': ['mmSLiMCoinTestnetBurnAddress1XU5fu'], 'value': 1.0},
        {'receivers': ['mx5MdsenFDZufFuwT9ND7BKQBzS4Hy9YUP'], 'value': 102.27}
    ],
    'blockheight': 484351
}

While my address balance after confirmation is 2186.49.
So I'd say I haven't paid 5 tSLMs of fee as I was trying to by using the -t flag with the pobtoken burn_coins command.
_
Update 13-07-2024
It seems like we have the same situation for the pobtoken create_tx command if used with the -t flag.
For instance I've just run pobtoken create_tx ac0f950a8fd4a8ee8d710a2463ee3c42e3f8a8fc7779e43e63810d12117d7be4 1.3 -t 1 and have produced transaction 00f8a0d480361a5e8321bfa681fb54cfeb74855185a9cff79a9c21d93966306d.
Its transaction show 00f8a0d480361a5e8321bfa681fb54cfeb74855185a9cff79a9c21d93966306d -s output is

{
    'inputs': [
        {'sender': ['n3MtPoPaAREU5GEhAErBPuju83bVog2opz'], 'value': 4.0}
    ],
    'outputs': [
        {'receivers': ['mmSLiMCoinTestnetBurnAddress1XU5fu'], 'value': 1.3},
        {'receivers': ['mx5MdsenFDZufFuwT9ND7BKQBzS4Hy9YUP'], 'value': 2.69}
    ],
    'blockheight': 'unconfirmed'
}

So it seems like in this case I've also was not able to spend 1 tSLM of fees.
_
UPDATE 22-07-2024
Seems like the attoken create_tx command doesn't consider the -t flag either.
I've run attoken create_tx 7a2ae406ddf44ddb17532d4888fdc14573f52749445e9e014075c9f83cbe556f 1 -c n3MtPoPaAREU5GEhAErBPuju83bVog2opz -t 5 and have produced transaction 2dac63879afd8576717bb1010779c6fc75ff0269f42bbe65556bf20177981f7c.
The transaction show 2dac63879afd8576717bb1010779c6fc75ff0269f42bbe65556bf20177981f7c -s output is:

{
    'inputs': [
        {'sender': ['n3MtPoPaAREU5GEhAErBPuju83bVog2opz'], 'value': 0.01},
        {'sender': ['n3MtPoPaAREU5GEhAErBPuju83bVog2opz'], 'value': 0.01},
        {'sender': ['n3MtPoPaAREU5GEhAErBPuju83bVog2opz'], 'value': 1.0}
    ],
    'outputs': [
        {'receivers': ['mpmZCVusQ6WoWHcFTAizmEcqSXdu5YX5PV'], 'value': 1.0},
        {'receivers': ['n3MtPoPaAREU5GEhAErBPuju83bVog2opz'], 'value': 0.01}
    ],
    'blockheight': 497401
}

[d5000]

Fixed in commit df3d2d7. Quite obvious bug so I think this can be closed.