<think>

Okay, I need to help the user generate a commit message based on the provided diff and history. Let me look at this step by step.

First, I'll examine the diff content. The file changed is `packages/wasm/rust/src/bls.rs`. Looking at the changes, it seems that a block of code has been removed between lines 11 and 16 of this file. Specifically, an enum called `BlsVariant` is being deleted.

The context provided includes prior commit messages. The last one was about removing a structure, so I should follow a similar pattern here. Since the task now involves removing an enum, that aligns well with using 'remove' as the type of change and indicating it's in the scope of the Rust package.

I'll form the message accordingly: '<type>' would be 'remove', the '<scope>' is 'rust', and the summary is what is being removed, which is the BlsVariant enum. Putting that together gives a clear and concise commit message that accurately reflects the change made.
</think>

The provided code diff shows that the `BlsVariant` enum has been removed from the file. This should be reflected in the commit message.

Step-by-step explanation:
1. Identify the type of change (addition, removal, modification).
2. Determine the scope or component affected.
3. Provide a clear and concise summary of the change.

Based on this:

remove(rust): BlsVariant enum

Author: Ansonhkg

packages/wasm/rust/src/bls.rs

@@ -11,12 +11,6 @@ use lit_bls_wasm::{
 };
 
 type JsResult<T> = Result<T, JsValue>;
-#[derive(Tsify, Deserialize, Debug)]
-#[tsify(from_wasm_abi)]
-pub enum BlsVariant {
-  Bls12381G1,
-  Bls12381G2,
-}
 
 // -----------------------------------------------------------------------
 // 1. blsCombine