proto/initia/gov/v1/query.proto (1)

137-140: Docstring/field name mismatch

The comment says // result is the result of the simulation. while the field is plural results. Either use result (singular) or pluralise the comment to keep documentation consistent.

x/gov/client/cli/util.go (1)

33-38: Minor: reuse loop variable and avoid re-shadowing error

err := ... inside the loop shadows the outer err, losing context if needed later. You can reuse the variable safely:

-    var msg sdk.Msg
-    err := cdc.UnmarshalInterfaceJSON(anyJSON, &msg)
+    var msg sdk.Msg
+    err = cdc.UnmarshalInterfaceJSON(anyJSON, &msg)

x/gov/keeper/custom_grpc_query.go (2)

176-179: Preserve panic information

You replace the actual panic with a generic message, losing valuable debugging info. Capture it instead:

if r := recover(); r != nil {
    err = fmt.Errorf("panic executing msg %d: %v", msgIndex, r)
}

---

203-209: GasWanted set to gas limit of an ‘infinite’ meter – may always be zero

GasWanted is taken from sdkCtx.GasMeter().Limit(). For gRPC queries the meter is often InfiniteGasMeter, whose limit is zero. Consider computing wanted gas as the sum of GasUsed or exposing a realistic value from cache context.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

api/initia/gov/v1/query.pulsar.go (2)

6-8: Prefer a clearer alias than v1beta11 for the ABCI dependency

The alias v1beta11 is non-intuitive and easy to confuse with v1beta1, which is already imported in the same file for pagination types.
Using a semantic alias (e.g. abci or abciV1) greatly improves readability and avoids future mix-ups.

-import (
-    _ "cosmossdk.io/api/amino"
-    v1beta11 "cosmossdk.io/api/cosmos/base/abci/v1beta1"
+import (
+    _ "cosmossdk.io/api/amino"
+    abci "cosmossdk.io/api/cosmos/base/abci/v1beta1"  // clearer alias

---

6153-6157: Doc-comment is singular, field is plural – keep them consistent

The comment still reads “result is the result of the simulation.” but the proto field was renamed to results and is a repeated list.
Update the comment to avoid confusion for client developers and API users.

-// result is the result of the simulation.
-Results []*v1beta11.Result `protobuf:"bytes,2,rep,name=results,proto3" json:"results,omitempty"`
+// results are the execution results of the simulation for each message.
+Results []*v1beta11.Result `protobuf:"bytes,2,rep,name=results,proto3" json:"results,omitempty"`

api/initia/mstaking/v1/query.pulsar.go (2)

15664-15672: Duplicate “Redelegations” RPCs may confuse clients

The service descriptor now exposes both Redelegations and RedelegationsOfDelegator, but they share the same request/response types. Unless there is a clear semantic difference, keeping both endpoints will:

• Break gRPC‐REST gateway generation (duplicate HTTP paths).
• Require extra client-side maintenance.
• Increase API surface without functional gain.

Please confirm that both names are needed; otherwise drop the obsolete one or alias it only at the CLI layer.

---

6279-6285: Minor performance nit – marshal order

During marshalling the code serialises Status after the unknownFields blob.
While functionally correct, the Protobuf wire format prefers known fields first; this keeps streaming encoders simpler and can save a small copy when unknownFields is large.

Not critical (generated file), just flagging in case the generator template can be tweaked.

Also applies to: 11649-11655

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Lite

x/gov/keeper/custom_grpc_query.go (1)

167-169: ⚠️ Potential issue

Nil-request guard missing

Similar to other query methods in this file, the implementation should check for nil requests at the beginning to prevent panics:

func (q CustomQueryServer) SimulateProposal(ctx context.Context, req *customtypes.QuerySimulateProposalRequest) (*customtypes.QuerySimulateProposalResponse, error) {
+   if req == nil || req.MsgSubmitProposal == nil {
+       return nil, status.Error(codes.InvalidArgument, "request cannot be nil")
+   }
    results := make([]sdk.Result, 0, len(req.MsgSubmitProposal.GetMessages()))

x/gov/keeper/custom_grpc_query.go (3)

175-184: Improve panic recovery error message

The panic recovery mechanism is good, but the error message could be more informative to aid debugging:

defer func() {
    if r := recover(); r != nil {
-       err = fmt.Errorf("panic from msg %d", msgIndex)
+       err = fmt.Errorf("panic from msg %d: %v", msgIndex, r)
    }
}()

---

185-196: Consider adding message type details to error messages

When a message is invalid or has no handler, adding the message type to the error would help with debugging:

var msg sdk.Msg
err := q.Keeper.cdc.UnpackAny(anyMsg, &msg)
if err != nil {
-   return nil, status.Errorf(codes.InvalidArgument, "invalid message %d", msgIndex)
+   return nil, status.Errorf(codes.InvalidArgument, "invalid message %d: %s", msgIndex, err.Error())
}

handler := q.Keeper.router.Handler(msg)
if handler == nil {
-   return nil, status.Errorf(codes.InvalidArgument, "invalid message %d", msgIndex)
+   return nil, status.Errorf(codes.InvalidArgument, "no handler for message %d of type %T", msgIndex, msg)
}

---

167-211: Consider exposing simulation logs

The current implementation returns results and gas information but doesn't expose the logs generated during simulation. These logs can be valuable for debugging proposal execution:

return &customtypes.QuerySimulateProposalResponse{
    GasInfo: sdk.GasInfo{
        GasWanted: cacheCtx.GasMeter().Limit(),
        GasUsed:   cacheCtx.GasMeter().GasConsumed(),
    },
    Results: results,
+   // Consider adding logs from the cached context if available
}, nil

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Lite