feat: nano contract integration with wallet connect

[alexruzenhack]

Acceptance Criteria

• Add new nano contract modal
  • It should appear when the wallet connect receive an RPC call to create a new nano contract transaction
• Add new nano contract details screen
  • It should allow the user to change the caller address
  • It should allows the user to decline the transaction
  • It should allows the user to accept the transaction
  • It should show a loading feedback content when transaction information is loading
  • It should show a loading feedback content when transaction is processing after user accepts it
  • It should show a success feedback content when transaction is sent with success
  • It should show a failed feedback content when transaction is not sent with success
  • It should show a feedback content instruction user to register Nano Contract when Nano Contract is not registered
    • It should allows the user to decline the transaction only
  • It should show a loading value on Blueprint Name and Caller on initialize call while background requests are being processed
  • It should show a warning value on Blueprint Name or Caller on initialize call if any request fails
  • It should instruct the user to select an address on Caller if request fails
  • It should allows the user to select an address on Caller if requests fails
  • It should show argument's name if a method call has arguments
  • It should show Position $ for each positional argument as a fallback for argument's name when blueprint info fails to load
  • It should load the details of a not registered token used in actions
    • It should show the symbol for the loaded token details
    • It should show an error message of feedback in case it fails to load some token details
    • It should load a cut of token uid as a fallback for not loading the token details

Loading tx info

wc-nc-loading-tx-info.mp4

Declining tx

wc-nc-declining-tx.mp4

Changing caller address

wc-nc-changing-caller-address.mp4

Accepting tx with failure

wc-nc-accepting-tx-with-failure.mp4

Accepting tx with failure and trying again

wc-nc-accepting-tx-with-failure-try-again.mp4

Accepting tx with success

wc-nc-accepting-tx-with-success.mp4

Handling many types of transactions for Nano Contract registered

fix-initialize-registered-nc.mp4

Handling initialize with requests failure

fix-initialize-loading-to-error.mp4

Handling requests for Nano Contract not registered

fix-initialize-not-registered-nc.mp4

Argument names

Android

iOS

Showing action token symbol for not registered token

Showing UID cut as fallback for not registered token and feedback error message

---

Warning

It depends on:

• An API update on hathor-core, related to the nano contract state.
• Proper implementation of nano contract RPC handler

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.

[andreabadesso]

You can use all to make the requests in parallel, also here goes a suggestion for legibility:

Suggested change

	const tokens = {};
	let someError = false;
	for (const uid of uids) {
	try {
	const { tokenInfo: { symbol, name } } = yield call([wallet, wallet.getTokenDetails], uid);
	const token = { uid, symbol, name };
	tokens[uid] = token;
	} catch (e) {
	log.error(`Fail getting token data for token ${uid}.`, e);
	someError = true;
	// continue
	}
	}
	const tokenDetailsRequests = uids.map((uid) =>
	call(function* () {
	try {
	const { tokenInfo: { symbol, name } } = yield call([wallet, wallet.getTokenDetails], uid);
	return [false, { uid, symbol, name }];
	} catch (e) {
	log.error(`Fail getting token data for token ${uid}.`, e);
	return [true, null];
	}
	})
	);
	const [someError, tokenDetails] = (yield all(tokenDetailsRequests)).reduce(
	(acc, tokenDetailRequest) => {
	const [error, tokenObj] = tokenDetailRequest;
	const [lastError, tokenDetails] = acc;
	return [
	lastError || error,
	tokenDetail ? {
	...tokenDetails,
	[tokenDetail.uid]: tokenDetail
	} : tokenObj,
	];
	}, [false, {}]
	);

Also, can you move this code to src/sagas/tokens.js and call it here?

[alexruzenhack]

Oh, thank you! Tbh, I have to think more about it. It involves network calls and may have some hidden pitfalls. I have to test it first. I have had some problems with "parallelism" using promises before. Let me do some tests first. I'm opening this issue #531 to work on it later.

[andreabadesso]

I don't think you'll have any problems here, even with a huge number of tokens

React-native's native HTTP module will queue them for you and only resolve when the request is done

But I agree that this should be tested, so OK to doing it in another PR

[andreabadesso]

I don't think you'll have any problems here, even with a huge number of tokens

React-native's native HTTP module will queue them for you and only resolve when the request is done

But I agree that this should be tested, so OK to doing it in another PR