oasisprotocol / oasis-core

Performant and Confidentiality-Preserving Smart Contracts + Blockchains
https://oasisprotocol.org
Apache License 2.0
332 stars 109 forks source link

registry entity gen_register output does not match ledger output #3727

Open chadbean opened 3 years ago

chadbean commented 3 years ago

(Apologies for some fuzzy details. This is going off of memory.)

When creating a registry transaction like:

TX_FLAGS=(--genesis.file "$GENESIS_FILE"
  --signer.dir entity/
  --signer.backend plugin
  --signer.plugin.name ledger
  --signer.plugin.path "$LEDGER_SIGNER_PATH"
)

oasis-node registry entity gen_register \
  "${TX_FLAGS[@]}" \
  --genesis.file $GENESIS_JSON \
  --transaction.file /tmp/tx_entity_gen_register.json \
  --transaction.fee.gas 2000 \
  --transaction.fee.amount 0 \
  --transaction.nonce $NONCE \

I see output to stdout which seems to be in base64 (such as signature). However, when reviewing the transaction on the ledger, it seems like the transaction details are in some hash format so I had no obvious or easy way to confirm that the transaction on the ledger matches what I see from stdout.

I suppose it's less of an issue with these types of transactions since I could always do a show_tx to confirm, but it'd be nice to always ensure that there's a way to verify what I'm approving.

chadbean commented 3 years ago

cc @tjanez (per slack chat)