oasisprotocol / oasisprotocol/cli
Pretty print for Cipher txes
Open
Nobody has claimed this yet.
paratime
ui
- Dominant language
- Go
- Stars
- 80
- Forks
- 23
- Avg merge
- 9h 43m
- Merged PRs (30d)
- 3
Description
Currently, data field is Base64-encoded when showing:
$ oasis contracts instantiate 286 '{instantiate: {initial_counter: 43}}' --paratime cipher
Unlock your account.
? Passphrase:
You are about to sign the following transaction:
Format: plain
Method: contracts.Instantiate
Body:
{
"code_id": 286,
"upgrades_policy": {
"address": "oasis1qrpaguksger8dqq8pn0vcnu8kr4m29ssvqk7kn0y"
},
"data": "oWtpbnN0YW50aWF0ZaFvaW5pdGlhbF9jb3VudGVyGCs=",
"tokens": []
}
Authorized signer(s):
1. MJ2XCjkj132C9YWpDUSQFjkCTI8bSw8bi0w9EwwE1Bg= (ed25519)
Nonce: 3
Fee:
Amount: 0.001417535 TEST
Gas limit: 283507
(gas price: 0.000000005 TEST per gas unit)
Network: testnet
ParaTime: cipher
Account: test
Decode it and show it as JSON.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CLI transaction-confirmation output for the displayed Cipher transaction and reproduce the example from the issue. Trace how the data field is rendered and make the output show decoded JSON; done means the confirmation displays the decoded value correctly and relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100