Expand the CCDScan backend logic to extract the input_parameter/message e.g. via the SDK (not from the event) for init_transactions. Expand the frontend to display the input_parameter/message for init_transactions as well:
Back-end functions:
#[ComplexObject]
impl ContractInitialized {
// TODO: the send message/input parameter is missing and not exposed by the event of the node currently.
async fn message(&self) -> ApiResult<String> {
// TODO: decode `self.input_parameter` with the schema.
Ok(input_parameter_decoded)
}
// TODO: the send message/input parameter is missing and not exposed by the event of the node currently.
async fn message_as_hex(&self) -> ApiResult<String> {
Ok(hex::encode(self.input_parameter))
}
...
}
Task description The current CCDScan (as well as other tooling https://github.com/Concordium/concordium-client/issues/291) doesn't display the
input_parameter/message
forinit_transactions
. The reason is that theContractInitializedEvent
from the node doesn't expose the value so this edge case was not handled previously. https://developer.concordium.software/concordium-grpc-api/#concordium.v2.ContractInitializedEventIn contrast,
contract_update_transactions
have theinput_parameter
available in the event. https://developer.concordium.software/concordium-grpc-api/#concordium.v2.InstanceUpdatedEventTasks:
Expand the CCDScan backend logic to extract the
input_parameter/message
e.g. via the SDK (not from the event) forinit_transactions
. Expand the frontend to display theinput_parameter/message
forinit_transactions
as well:Back-end functions: