Enhance Non-Rowan Yield Reward Functionality with Optional Duration Feature about sifnode HOT 1 OPEN

https://github.com/Sifchain/sifnode/blob/main/x/dispensation/claims.md#L0-L30

https://github.com/Sifchain/sifnode/blob/main/x/dispensation/claims.md#L15-L30

https://github.com/Sifchain/sifnode/blob/main/ui/README.md#L0-L133

https://github.com/Sifchain/sifnode/blob/main/docs/clp/clp-adr.md#L0-L201

https://github.com/Sifchain/sifnode/blob/main/smart-contracts/Deployment.md#L0-L105

Action: modify
File: x/dispensation/claims.md
Lines: [1, 31]
Dependencies: []
Instructions: In the 'x/dispensation/claims.md' file, update the documentation to include a section on the optional duration parameter for liquidity distribution. This section should explain how the distribution method changes with the duration parameter, allowing liquidity to be spread out incrementally over the set duration instead of being released all at once. Reference the 'General use case' section for context on how claims are currently processed and highlight the benefits of having a controlled distribution method.

Action: modify
File: x/clp/keeper/add_liquidity_to_rewards_bucket.go
Lines: [1, 50]
Dependencies: ['Step 1']
Instructions: In the 'x/clp/keeper/add_liquidity_to_rewards_bucket.go' file, modify the 'AddLiquidityToRewardsBucket' function to accept an additional parameter 'duration'. This parameter should specify the time over which the added liquidity is to be distributed. Update the function's logic to ensure that the distribution of rewards is spread out over the specified duration. This involves adjusting the calculation of rewards per block or per epoch to account for the total distribution period.

Action: modify
File: x/clp/types/message_add_liquidity_to_rewards_bucket.go
Lines: [10, 30]
Dependencies: ['Step 2']
Instructions: Modify the 'MsgAddLiquidityToRewardsBucket' message in 'x/clp/types/message_add_liquidity_to_rewards_bucket.go' to include a new field 'Duration' of type 'int64'. This field represents the duration over which the liquidity is to be distributed. Ensure that the message validation logic is updated to check for a valid duration value (e.g., non-negative).

Action: modify
File: x/clp/handler.go
Lines: [50, 100]
Dependencies: ['Step 3']
Instructions: In the 'x/clp/handler.go' file, update the handler for 'MsgAddLiquidityToRewardsBucket' to extract the 'Duration' parameter from the message and pass it to the 'AddLiquidityToRewardsBucket' function. Ensure that the handler correctly processes the duration parameter and that any necessary validation is performed before calling the function.

Action: modify
File: x/clp/client/cli/tx_add_liquidity_to_rewards_bucket.go
Lines: [1, 50]
Dependencies: ['Step 4']
Instructions: Modify the CLI command for adding liquidity to the rewards bucket in 'x/clp/client/cli/tx_add_liquidity_to_rewards_bucket.go' to accept a new flag '--duration' that specifies the distribution duration. Update the command logic to include the duration in the 'MsgAddLiquidityToRewardsBucket' message. Provide clear instructions in the command's help text explaining the purpose of the duration parameter and how to use it.

Action: modify
File: x/dispensation/claims.md
Lines: [1, 31]
Dependencies: []
Instructions: In the 'x/dispensation/claims.md' file, update the documentation to include a section on the optional duration parameter for liquidity distribution. This section should explain how the distribution method changes with the duration parameter, allowing liquidity to be spread out incrementally over the set duration instead of being released all at once. Reference the 'General use case' section for context on how claims are currently processed and highlight the benefits of having a controlled distribution method.

Action: modify
File: x/clp/keeper/add_liquidity_to_rewards_bucket.go
Lines: [1, 50]
Dependencies: ['Step 1']
Instructions: In the 'x/clp/keeper/add_liquidity_to_rewards_bucket.go' file, modify the 'AddLiquidityToRewardsBucket' function to accept an additional parameter 'duration'. This parameter should specify the time over which the added liquidity is to be distributed. Update the function's logic to ensure that the distribution of rewards is spread out over the specified duration. This involves adjusting the calculation of rewards per block or per epoch to account for the total distribution period.

Action: modify
File: x/clp/types/message_add_liquidity_to_rewards_bucket.go
Lines: [10, 30]
Dependencies: ['Step 2']
Instructions: Modify the 'MsgAddLiquidityToRewardsBucket' message in 'x/clp/types/message_add_liquidity_to_rewards_bucket.go' to include a new field 'Duration' of type 'int64'. This field represents the duration over which the liquidity is to be distributed. Ensure that the message validation logic is updated to check for a valid duration value (e.g., non-negative).

Action: modify
File: x/clp/handler.go
Lines: [50, 100]
Dependencies: ['Step 3']
Instructions: In the 'x/clp/handler.go' file, update the handler for 'MsgAddLiquidityToRewardsBucket' to extract the 'Duration' parameter from the message and pass it to the 'AddLiquidityToRewardsBucket' function. Ensure that the handler correctly processes the duration parameter and that any necessary validation is performed before calling the function.

Action: modify
File: x/clp/client/cli/tx_add_liquidity_to_rewards_bucket.go
Lines: [1, 50]
Dependencies: ['Step 4']
Instructions: Modify the CLI command for adding liquidity to the rewards bucket in 'x/clp/client/cli/tx_add_liquidity_to_rewards_bucket.go' to accept a new flag '--duration' that specifies the distribution duration. Update the command logic to include the duration in the 'MsgAddLiquidityToRewardsBucket' message. Provide clear instructions in the command's help text explaining the purpose of the duration parameter and how to use it.