Redeem tokens not always working

[wiadran]

I have an issue redeeming tokens:
it works smoothly on some markets (e.g., BTC 15 Minutes),
but it doesn’t work at all on football markets.
I’m using the same code in both cases:

    const ctfAddress = "0x4d97dcd97ec945f40cf65f87097ace5ea0476045"; 
    const collateralToken = "0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174"; 

    const parentCollectionId = "0x0000000000000000000000000000000000000000000000000000000000000000"; 
    const indexSets: number[] = [1, 2]; //any combination here was used - restricted to owned tokens, and generic 1 and 2 as well

    const redeemTx: SafeTransaction = {
        to: ctfAddress,
        operation: OperationType.Call,
        data: ctfInterface.encodeFunctionData("redeemPositions", [
            collateralToken,
            parentCollectionId,
            conditionId,
            indexSets
        ]),
        value: "0"
    };


    const response = await client.execute(
        [redeemTx],
        "Simple redeem test"
    );

In both cases the transactions are created and appear on Polygonscan as successful, but for football markets the positions remain unredeemed.
There is a difference on the logs on polygonscan; for football there seem to be 4 "steps":

1. SafeMultiSigTransaction (address to, uint256 value, bytes data, uint8 operation, uint256 safeTxGas, uint256 baseGas, uint256 gasPrice, address gasToken, address refundReceiver, bytes signatures, bytes additionalInfo)[View Source]
2. PayoutRedemption (index_topic_1 address redeemer, index_topic_2 address collateralToken, index_topic_3 bytes32 parentCollectionId, bytes32 conditionId, uint256[] indexSets, uint256 payout)[View Source]
3. ExecutionSuccess (bytes32 txHash, uint256 payment)[View Source]
4. LogFeeTransfer (index_topic_1 address token, index_topic_2 address from, index_topic_3 address to, uint256 amount, uint256 input1, uint256 input2, uint256 output1, uint256 output2)[View Source]

while bitcoin market (the working one) is like:

1. SafeMultiSigTransaction (address to, uint256 value, bytes data, uint8 operation, uint256 safeTxGas, uint256 baseGas, uint256 gasPrice, address gasToken, address refundReceiver, bytes signatures, bytes additionalInfo)[View Source]
2. TransferSingle (index_topic_1 address operator, index_topic_2 address from, index_topic_3 address to, uint256 id, uint256 value)[View Source]
3. TransferSingle (index_topic_1 address operator, index_topic_2 address from, index_topic_3 address to, uint256 id, uint256 value)[View Source]
4. Transfer (index_topic_1 address from, index_topic_2 address to, uint256 value)
5. PayoutRedemption (index_topic_1 address redeemer, index_topic_2 address collateralToken, index_topic_3 bytes32 parentCollectionId, bytes32 conditionId, uint256[] indexSets, uint256 payout)
6. ExecutionSuccess (bytes32 txHash, uint256 payment)
7. LogFeeTransfer (index_topic_1 address token, index_topic_2 address from, index_topic_3 address to, uint256 amount, uint256 input1, uint256 input2, uint256 output1, uint256 output2)

[callmedraxx]

I also have the same issue. Sometimes it works sometimes it doesn't. I think it's related to negative risk market

[callmedraxx]

Did you find a solution yet? I asked on discord also no one is responding

[shanghaojia-1]

I have the same issue. All markets included btc 15m do not work.

[ShantanuNair]

@callmedraxx Any luck on discord?

[callmedraxx]

@callmedraxx Any luck on discord?

No luck. No one responded

[wiadran]

Did you find a solution yet? I asked on discord also no one is responding

nope, no luck, what i could notice so far is it doesn't work on soccer or cricket when there are 3 markets (home, away, draw). It seems to work fine on all sports (including cricket moneyline or soccer's totals or spreads markets) with all the cases of "single markets" where there are 2 options...
But as for now i could not get the reason for cases with 3 markets etc

The main difference i can see there is that 3-market sets are having negrisk=true (as @callmedraxx noticed)
my lucky guess was to use that neg risk market id or something like that as parentCollectionId rather than null value - but no luck with it...

[callmedraxx]

Did you find a solution yet? I asked on discord also no one is responding

nope, no luck, what i could notice so far is it doesn't work on soccer or cricket when there are 3 markets (home, away, draw). It seems to work fine on all sports (including cricket moneyline or soccer's totals or spreads markets) with all the cases of "single markets" where there are 2 options... But as for now i could not get the reason for cases with 3 markets etc

The main difference i can see there is that 3-market sets are having negrisk=true (as @callmedraxx noticed) my lucky guess was to use that neg risk market id or something like that as parentCollectionId rather than null value - but no luck with it...

I even thought to use the negrisk contract or exchange as ctfaddress instead but haven't tried yet

[tongjun741]

Same issue on btc 15m market.