TriggerType not correctly recognized in Bybit and Deribit

[marco-rigoni]

Hi everyone,

When I try to place a StopMarketOrder using order_factory.stop_market, both Bybit and Deribit seem to fail to correctly recognize the trigger type.

Bybit accepts the order, but recognizes all trigger types as 'last price' regardless of the type specified.

Deribit rejects the order altogether with the following reason:

'code=-32602: Invalid params (data: {"param":"trigger","reason":"trigger is required"})'

Tested with all available TriggerType values, I'll post the code I used here just to make sure the mistake isn't on my side:

order: StopMarketOrder = self.order_factory.stop_market(
            instrument_id=self.config.instrument_id,
            order_side=OrderSide.BUY,
            quantity=self.create_order_qty(order_size),
            trigger_price=order_price,
            trigger_type=TriggerType.MARK_PRICE,
            time_in_force=TimeInForce.GTC,
            expire_time=None,  # <-- optional (default None)
            reduce_only=True,  # <-- if True, closes existing positions
        )
        
        self.submit_order(order)

I'm running Nautilus build 1.224.0.

Thanks in advance for your help!

Update: I did a quick test with StopLimitOrder and it seems to have the same issues

[cjdsellers]

Hi @marco-rigoni

Thanks for reporting this with the clear reproduction code.

The Bybit trigger type was indeed hardcoded to LastPrice regardless of what was specified on the order. This is now fixed on develop - the adapter reads trigger_type from the order and maps it to the correct Bybit value (MarkPrice, IndexPrice, etc.). The same fix applies to TP/SL attached triggers.

Looking into the Deribit issue next.

[cjdsellers]

The Deribit side is also now fixed on develop. The Python execution client wasn't forwarding trigger_price or trigger_type to the WebSocket client, so stop orders arrived at Deribit without those fields. The trigger type mapping now runs in Rust rather than Python.

[marco-rigoni]

Thanks a lot for the fix @cjdsellers!

I have encountered a couple other bugs using Nautilus, would you like me to report them on separate discussions or are you busy working on other features?

Unfortunately I don't have the technical knowledge to work on core Nautilus code, otherwise I'd have contributed myself.

Let me know and thanks again.

[cjdsellers]

Hey @marco-rigoni

The bug reports are still valuable. If you could raise the issue tickets with detailed descriptions that would be very helpful, thank you 🙏