feat: add support for nano contract details

[pedroferreira1]

Acceptance Criteria

• Add screen to show the details of a nano contract with state and history (TODO the history table still doesn't have pagination but this will be added in the next version).
• Add screen to show details of a blueprint.
• Show nano contract information in the Transaction Detail screen.
• It seems like there's a bug in the TxData component when using the isBlock method. This PR also fixes it.

nano.explorer.mov

Edit on the screen:

Security Checklist

• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

[pedroferreira1]

Without this I was getting an error when running locally (with node 18)

[r4mmer]

For the blueprint detail screen I found it somewhat weird to have a table where one of the cells has a table with the arguments.
Maybe we could show the arguments as a method signature, for instance:

name	arguments	return
initialize	(oracle_script: bytes, token_uid: bytes, date_last_bet: int)	null

Or something like:

initialize(oracle_script: bytes, token_uid: bytes, date_last_bet: int): None

For each method.

[r4mmer]

This TODO is for another PR?

[pedroferreira1]

Yes. Right now we don't have the information when an attribute is a token. I discussed this with Marcelo and we will improve this on hathor-core, so we can better render information on the client.

[tuliomir]

Although it's the nature of the Explorer app to just display data schemas fetched from outside, I felt there could be more references to what data is being displayed here.

This is especially important when displaying the data on the NanoContractDetail screen. I think adding some docstrings and explanatory comments that reference the original schemes and designs would be of great help for future code maintenance.

[pedroferreira1]

@r4mmer

For the blueprint detail screen I found it somewhat weird to have a table where one of the cells has a table with the arguments.
Maybe we could show the arguments as a method signature, for instance:

I agree, it's much better, see: b31843f

[pedroferreira1]

@tuliomir

This is especially important when displaying the data on the NanoContractDetail screen. I think adding some docstrings and explanatory comments that reference the original schemes and designs would be of great help for future code maintenance.

I think having the docs on the APIs is enough. We get the data to show on the screen from the APIs and the user can see it there.

Soon the nano APIs will be in the official API docs, then I can add the links in the code as well.

[r4mmer]

This is only required for node 20 (I think) are we upgrading the required node?

[pedroferreira1]

In the explorer we use node 18 and without this we get an error:

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:69:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/Users/pedroferreira/Hathor/nano-hathor-explorer/hathor-explorer/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/Users/pedroferreira/Hathor/nano-hathor-explorer/hathor-explorer/node_modules/webpack/lib/NormalModule.js:417:16)
    at /Users/pedroferreira/Hathor/nano-hathor-explorer/hathor-explorer/node_modules/webpack/lib/NormalModule.js:452:10
    at /Users/pedroferreira/Hathor/nano-hathor-explorer/hathor-explorer/node_modules/webpack/lib/NormalModule.js:323:13
    at /Users/pedroferreira/Hathor/nano-hathor-explorer/hathor-explorer/node_modules/loader-runner/lib/LoaderRunner.js:367:11
    at /Users/pedroferreira/Hathor/nano-hathor-explorer/hathor-explorer/node_modules/loader-runner/lib/LoaderRunner.js:233:18
    at context.callback (/Users/pedroferreira/Hathor/nano-hathor-explorer/hathor-explorer/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at /Users/pedroferreira/Hathor/nano-hathor-explorer/hathor-explorer/node_modules/babel-loader/lib/index.js:59:103 {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

[r4mmer]

There is a possibility of the "nano contract data loading" message flashing for transactions that are not nano contracts, maybe we should use this.

Suggested change

	this.setState({ ncLoading: true });
	if (this.props.transaction.version !== hathorLib.constants.NANO_CONTRACTS_VERSION) {
	this.setState({ ncLoading: false });
	return;
	}
	if (this.props.transaction.version !== hathorLib.constants.NANO_CONTRACTS_VERSION) {
	this.setState({ ncLoading: false });
	return;
	}
	this.setState({ ncLoading: true });

[pedroferreira1]

Makes sense: 8bdd32b