Added blockchain show block/transactions/contracts commands

[cschuchardt88]

Change Log

• Add command show block <index>
• Add command show block <hash>
• Add command show tx <hash>
• Add command show contract <name>
• Add command show contract <hash>

[shargon]

I like it :)
My review:

• print or show?
• Can you add print and show contract (by id, hash, or name if it's native)?

[cschuchardt88]

[EdgeDLT]

@cschuchardt88 Can we add application logs if the node supports them (e.g. state, notifications, etc)? It could be appended on print tx.

[cschuchardt88]

see neo-project/neo-modules#807

[Jim8y]

I like it :) My review:

• print or show?
• Can you add print and show contract (by id, hash, or name if it's native)?

@cschuchardt88 show has being used as a command to print things to the console, would be good to change to show. We can discuss whether to change from show to print in the future

[shargon]

@superboyiii could you test it?

[superboyiii]

@superboyiii could you test it?

I will

[cschuchardt88]

@superboyiii can you make sure you can get blocks, transactions and contracts with all the attributes on them.

[superboyiii]

@superboyiii can you make sure you can get blocks, transactions and contracts with all the attributes on them.

I can't get all, but will choose some special cases to see if it still works well.

[superboyiii]

Maybe it's better to support getting details of attribute, currently it only gets Type, AllowMultiple and size, but for example, for an Oracle response tx, id, code and result is critical.
like tx 0x6ccda4f935da375f32110d321e04b16c59b2118154ff3a8c570384382fc96746 on mainnet

"attributes": [
            {
                "type": "OracleResponse",
                "id": 20847,
                "code": "Success",
                "result": "W251bGxd"
            }
        ]

Test result:

And for conflict attribute, like 0x5ebf8d379ce15d440daedb8f8cbe1215cb0b08988f57d0407bf419cb4ed14dff on testnet, there should be type and hash.

"attributes": [
            {
                "type": "Conflicts",
                "hash": "0x2474ecd9f2e0e0ec149aad323db654a3c60fb00386c204a5175d856fdff853c4"
            }
        ]

Test result:

[shargon]

Maybe it's better to support getting details of attribute, currently it only gets Type, AllowMultiple and size, but for example, for an Oracle response tx, id, code and result is critical. like tx 0x6ccda4f935da375f32110d321e04b16c59b2118154ff3a8c570384382fc96746 on mainnet

"attributes": [
            {
                "type": "OracleResponse",
                "id": 20847,
                "code": "Success",
                "result": "W251bGxd"
            }
        ]

Test result:

And for conflict attribute, like 0x5ebf8d379ce15d440daedb8f8cbe1215cb0b08988f57d0407bf419cb4ed14dff on testnet, there should be type and hash.

"attributes": [
            {
                "type": "Conflicts",
                "hash": "0x2474ecd9f2e0e0ec149aad323db654a3c60fb00386c204a5175d856fdff853c4"
            }
        ]

Test result:

Agree, AllowMultiple is not needed.

[cschuchardt88]

[superboyiii]

Works well for me.