Difficulty integrating with keplr (cosmos)

[xpt1x]

I cant use this with keplr as i am seeing an error like: "unmatched chain id"

Keplr (most popular cosmos wallet) takes chain-id as a param to sign message which for this example let's say is local-mainnet because the signer signing this message has his address derived from this local-mainnet chain but i believe when creating a signDoc to be signed, aleph creates it with chain-id signed-message-v1 which creates conflict at time of signing and hence throws this above error

What i have tried till now

1. tried to change CHAIN_ID from aleph-js source for testing to local-mainnet, so that chain-id stays same, after running submit fn, it provides me with item hash, like it succeeded but i don't see anything on explorer or aleph's server
2. tried mocking actual chain with a chain which is similar in all aspects, just chain-id will be signed-message-v1 for it (using keplr's suggest chain) and signing messages from this chain, after running submit fn, it provides me with item hash, like it succeeded but i don't see anything on explorer or aleph's server

I haven't read how handling of these messages is done on aleph network itself so pardon me if i am doing something completely wrong, i was just trying to make it work with keplr. I also don't understand if something wrong happens after submit fn, why its generating a success result and providing me with a item hash at the end ?

Message that i sign at keplr

{
  "chain_id": "local-mainnet",
  "account_number": "0",
  "fee": {
    "gas": "0",
    "amount": [
      {
        "denom": "uiov",
        "amount": "0"
      }
    ]
  },
  "memo": "",
  "sequence": "0",
  "msgs": [
    {
      "type": "signutil/MsgSignText",
      "value": {
        "message": "CSDK\nstar1yark4kdrn29erxpnh3njy2756pmlgwn0sta5sf\nAGGREGATE\n64667490389d514e794373b59601a085e83f25abcea57f4e049f3bb368dc2ea8",
        "signer": "star1yark4kdrn29erxpnh3njy2756pmlgwn0sta5sf"
      }
    }
  ]
}

Result from aggregateSubmit

{
    "chain": "CSDK",
    "channel": "TEST",
    "sender": "star1yark4kdrn29erxpnh3njy2756pmlgwn0sta5sf",
    "type": "AGGREGATE",
    "time": 1659689807.291,
    "item_type": "inline",
    "item_content": "{\"address\":\"star1yark4kdrn29erxpnh3njy2756pmlgwn0sta5sf\",\"key\":\"do*iov\",\"content\":{\"biography\":\"i am do\",\"name\":\"\",\"photo\":null},\"time\":1659689807.29}",
    "item_hash": "64667490389d514e794373b59601a085e83f25abcea57f4e049f3bb368dc2ea8",
    "signature": "{\"pub_key\":{\"type\":\"tendermint/PubKeySecp256k1\",\"value\":\"AuWRwc/FteDNIeGTJ0gOXx7bPrNWBcnBuGDyETeApCSd\"},\"signature\":\"mqoIWiJy+bMTu3CPTmF9yGe6jaVFV618wwFHAiSEVFNn2SskKVVWIlpvxrxW9lz9W5tYSe5IYGz4n1HwmsHjOg==\",\"account_number\":\"0\",\"sequence\":\"0\"}"
}

[hoh]

Thanks for reporting this issue.

The same validation logic is used on Aleph.im Core Channel Nodes to validate the messages, explaining why (2.) fails as well.

For reference, the relevant code on PyAleph is here:
https://github.com/aleph-im/pyaleph/blob/deaa4c3f0d7d9463078def59f2bfb69ac7023f3c/src/aleph/chains/cosmos.py#L29

[hoh]

I also don't understand if something wrong happens after submit fn, why its generating a success result and providing me with a item hash at the end ?

The validation is asynchronous for performance reasons, but we have this issue in mind and plan to add validation upon submission on the HTTP endpoint.

[xpt1x]

@hoh thanks for quick replies, i understood the issue
I actually saw something strange with my dev env maybe, but currently method (2.) is working fine
As pubKey will be same for mock chain and actual chain as their HDPaths are same and so is prefix
So i don't see why verification can fail

[xpt1x]

Alright, found the actual issue..
Actually using keplr sign function without specifying signOptions object will generate a transaction with fee object with amount property filled with the chain currency

"fee": {
    "gas": "0",
    "amount": [
      {
        "denom": "uiov",
        "amount": "0"
      }
    ]
  },

However at aleph while verifying message, an object is created where amount prop is required to be just an empty array [ ]

"fee": {
   "amount": [],
   "gas": "0",
},

as referenced by @hoh above at pyaleph

Solution here would be to use optional object signOptions for keplr like this
(so that we don't generate and sign a object with filled amount as it will fail at verification stage at aleph)

keplr.signAmino(alephChainId, signerAddress, signDoc, {
      preferNoSetFee: true,
      preferNoSetMemo: true,
});

Or (if possible)
Aleph updates their verification method to extract fee object from original messages and create verification object accordingly