This section elaborates on the transaction message handler methods being exposed by the House module.
When a create transaction is processed, the following things happen:
Validate the incoming create message.
Call the Create
method of the keeper.
The RPC for creating a subaccount is as follows:
The request message for Create
is MsgCreate
. The proto for the request message is as follows:
The response message for Deposit
is MsgDepositResponse
. The proto for the request message is as follows:
When a top-up transaction is processed, the following things happen:
Validate the incoming create message.
Call the TopUp
method of the keeper.
The RPC for a top-up of the subaccount is as follows:
The request message for TopUp
is MsgTopUp
. The proto for the request message is as follows:
The response message for TopUp
is MsgTopUpResponse
. The proto for the request message is as follows:
When a top-up transaction is processed, the following things happen:
Validate the incoming create message.
Call the WihtdrawUnlocked
method of the keeper.
The RPC for a top-up of the subaccount is as follows:
The request message for WihtdrawUnlockedBalances
is MsgWihtdrawUnlockedBalances
. The proto for the request message is as follows:
The response message for WihtdrawUnlockedBalances
is MsgWihtdrawUnlockedBalancesResponse
. The proto for the request message is as follows:
When a wager transaction is processed, the following things happen:
Validate the incoming create message.
Call the Wager
method of the keeper.
The RPC for a wager of the subaccount is as follows:
The request message for Wager
is MsgWager
. The proto for the request message is as follows:
The response message for Wager
is MsgWagerResponse
. The proto for the request message is as follows: