feat: add nano contract info to tx history [6]

[alexruzenhack]

This change enables to show nano contract context information on regular transaction list and details. Also, it enables to set marks based on transaction type and make visual differentiation among them.

Look at the approved design #445. Go to "Flow 4".

Acceptance Criteria

• should extract TxHistory construction to the model
• should add nano contract information on tx details view
• should change icon to access token info

TxHistory Screen:

TxDetails Modal (Nano Contract:

ActionDot to access token info

---

Note

It depends on:

• feat: add icons [4] #453
• feat: add components [5] #454
• feat: nano contract history [3] #432
• fix: getTxHistory [1] hathor-wallet-lib#630

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.

[anafigueired]

The TokensHeader component is not using the new one.

Besides that, everything meets the Design accordingly.

[andreabadesso]

This one is interesting, what do you think about "Caller do Nano Contract"?

[alexruzenhack]

I think it is ugly. I prefer "Acionador do Nano Contract" to avoid a heavy "foreignism" (estrangeirismo).

[andreabadesso]

What would be the best person to discuss this translation with? Campana?

I don't like this translation, but I don't have anything better to suggest, so I'm going to approve this PR

[alexruzenhack]

@BrunoCampana , @pedroferreira1

[pedroferreira1]

I don't like it either. While we wait for the best names from the other areas, I think we can call "Endereço que assinou o Nano Contract", even if it's big, I think it's better.

What do you think?

[alexruzenhack]

Just to keep it as a noun we can use "Endereço de assinatura do Nano Contract".

[BrunoCampana]

@alexruzenhack

At the moment, in our documentation about nano contracts, this field was named "caller", you can see in the diagram at:
https://beta-test.docs.hathor.network/explanations/features/nano-contracts/how-it-works#transactions

However, please note that this name was provided for two reasons:

• This is how Marcelo named it.
• It relates to who is indeed calling the contract.

Thus, it is the adequate term for documentation purposes.

That said, it might not be suitable in terms of UI/UX. Because I don't know the overall terminology of this and also other features in our UIs, is difficult to suggest something at this moment.

[alexruzenhack]

Hi, @BrunoCampana, thank you to add more light in this case. I got it!

Regarding the translation, do you do have a suggestion?

I found a better word for the translation so far: "Signatário"; see definition. I believe it is more aligned with all the explanation you showcased here @BrunoCampana. What do you guys say about this one?