Hardware wallet maker Trezor says old order records that should have been deleted were found in the ShipMonk leaked dataset.

At a Glance Organization SafePal (crypto hardware wallet maker) Data exposed Names, emails, shipping addresses, phone numbers, purchase details Affected About 39,798 customers (company figure) Cause Authorization flaw in an order-tracking plug-in Disclosure status Confirmed and disclosed by SafePal; customers notified Source SafePal security advisory TL;DR SafePal disclosed a data breach affecting about 39,798 customers. An authorization flaw in an order-tracking plug-in let outsiders view other customers' order information.

Nederlanders kiezen steeds vaker voor vaste energiecontracten voor alleen gas. Volgens analyse van interne orderdata van Overstappen.nl is het aandeel alleen gas-contracten in een halfjaar verdubbeld: van 1,8% in januari naar 3,6% in juni 2025. Consumenten maken steeds vaker een bewuste splitsing in hun energiecontracten. Waar voorheen stroom en gas meestal samen werden afgesloten, ontstaat nu een andere aanpak: het hybride contract. Dit betekent een vast contract voor gas gecombineerd met een dynamisch contract voor stroom.

Hi Kornel, Hum you right, I've moved the order creation out of the loop (which indeed it is more relevant, in the real world the orders are created from another workflow and the executions are applied to existing orders..) and now the method invokation takes 0sec: fn test_dynamic_trait(){ let t0 = Instant::now(); let ord = FooOrder { order_data:Some(OrderData::default()), order_variant: Box::new(MarketOrderData{ quantity: 25, tif: TimeInForce::Day, side: OrderSide::Buy }), basket_id:Some(AtomicCell::new(0)), order_id:25, action_counter: AtomicCell::new(12) }; for _it in 0..100_000_000{ // let ord = FooOrder { // order_data:Some(OrderData::default()), // order_variant: Box::new(MarketOrderData{ // quantity: 25, // tif: TimeInForce::Day, // side: OrderSide::Buy // }), // basket_id:Some(AtomicCell::new(0)), // order_id:25, // action_counter: AtomicCell::new(12) // }; _=ord.execute(&ExecutionData{ order_quantity:45, side: OrderSide::Buy, last_execution_price:12.3, average_price:45.5, last_execution_quantity:14, remaining_quantity:11, cumulative_quantity:11 }); } let elapsed = t0.elapsed().as_secs_f64(); println!("test dynamic method invoke Time elapsed: {:.3} sec. ", elapsed); } I've learn a lot today....

Hi Kornel Thanks for your answer, i agree, but we can't use dyn Trait inside structs as field, which is what I'm are using, so I need some container such as Box... Maybe you have better approach to do that, I'll appreciate pub struct FooOrder<'a> { pub order_data: Option<OrderData<'a>>, pub order_variant: Box<dyn TOrderType>, pub order_id: u64, pub basket_id: Option<AtomicCell<u32>>, pub action_counter: AtomicCell<u16>, }

Hi Kornel, Yes of course, I' m using release mode: cargo.toml nohash = "0.2.0" crossbeam-channel="0.5.13" mimalloc = "0.1" [profile.release] codegen-units = 1 lto = "fat" panic = "abort" opt-level = "s" about Box::new, this take really short time: doing only this, fn test_dynamic_trait(){ let t0 = Instant::now(); for _it in 0..100_000_000{ let ord = FooOrder { order_data:Some(OrderData::default()), order_variant: Box::new(MarketOrderData{ quantity: 25, tif: TimeInForce::Day, side: OrderSide::Buy }), basket_id:Some(AtomicCell::new(0)), order_id:25, action_counter: AtomicCell::new(12) }; /* _=ord.execute(&ExecutionData{ order_quantity:45, side: OrderSide::Buy, last_execution_price:12.3, average_price:45.5, last_execution_quantity:14, remaining_quantity:11, cumulative_quantity:11 }); */ } let elapsed = t0.elapsed().as_secs_f64(); println!("test dynamic invoke Time elapsed: {:.3} sec. ", elapsed); } it takes <1ms for the 100_000_000 iterations, so we can exclude the cost of that...No it is only the dynamic call of execute which takes abnormal time ...And I don't understand why. Did you have similar use case? What are your results? Thanks for your help!

Hi, For my business requirements (basically we need flexibility to create new type of order, as structs, easily without to deliver entire platform, I need to use dyn Trait instead of enum of each order. See below the elements of the code required to understand my concerns... What is really insane is the performances using dynamic binding... Structs (orders) pub struct FooOrder<'a> { pub order_data: Option<OrderData<'a>>, pub order_variant: Box<dyn TOrderType>, pub order_id: u64, pub basket_id: Option<AtomicCell<u32>>, pub action_counter: AtomicCell<u16>, } impl<'a> FooOrder<'a> { pub fn static_execute(&mut self){ self.order_id = 45; let exec_data = ExecutionData{ order_quantity:45, side: OrderSide::Buy, last_execution_price:12.3, average_price:45.5, last_execution_quantity:14, remaining_quantity:11, cumulative_quantity:11 }; _=self.order_variant.execute(&exec_data); } } pub trait TOrderType{ fn execute(&self, exec_data: &ExecutionData) ->Result<bool, OrderErrorMessages>; fn update(&self, value: Box<dyn TOrderType>); } pub struct LimitOrderData { pub price: f32, pub quantity: u32, pub tif: TimeInForce, pub side: OrderSide } pub struct MarketOrderData { pub quantity: u32, pub tif: TimeInForce, pub side: OrderSide } //there are lot of order types pub struct ExecutionData { pub side: OrderSide, pub last_execution_price: f32, pub average_price:f32, pub last_execution_quantity: u32, pub remaining_quantity: u32, pub order_quantity: u32, pub cumulative_quantity: u32 } pub enum OrderSide{ Buy, Sell } pub enum TimeInForce { Day, Gtc, Gtd(u64),//expiration time Ioc, Fok, Moo, Loo, Moc, Loc } So, here the test: fn test_dynamic_trait(){ let t0 = Instant::now(); for _it in 0..100_000_000{ let ord = FooOrder { order_data:Some(OrderData::default()), order_variant: Box::new(MarketOrderData{ quantity: 25, tif: TimeInForce::Day, side: OrderSide::Buy }), basket_id:Some(AtomicCell::new(0)), order_id:25, action_counter: AtomicCell::new(12) }; _=ord.execute(&ExecutionData{ order_quantity:45, side: OrderSide::Buy, last_execution_price:12.3, average_price:45.5, last_execution_quantity:14, remaining_quantity:11, cumulative_quantity:11 }); } let elapsed = t0.elapsed().as_secs_f64(); println!("test dynamic invoke Time elapsed: {:.3} sec. ", elapsed); } This takes 4.9 sec!!! 40 ns by dyn call. How is it possible? In C++, Java, C#, virtual methods takes, in my pc between, 0.8 and 2 ns by call. Last versions of JIT are using PGO, but anyway, using old versions has well, the time for dynamic invocation are under 5ns. Using static invocation, the time for the same example (using as order_variant an enum wrapping order structs) is 0.052 sec, so really as expected using rust. (The time to create objects takes around 0.052 sec, the time to call methode is under 1ns) There are way to understand what happens? I believe that the differences should be around x2 or x3 but not > x25...