While we are at this refactoring, let's completely pull out this buried API call. We shouldn't have any API calls inside a component function. Instead, we only make the API call if there is a flag -- and then we pass the output as a param into the function.

So, sendXEC would have this kind of call before this function is called -- which is okay since these are all lowest level calls.

If (encrypted) {

try {API call to get pub key, return pubKey as recipientPubKey}
catch (err) { throw err}

try {
            const pubKeyBuf = Buffer.from(recipientPubKey, 'hex');
            const bufferedFile = Buffer.from(optionalOpReturnMsg);
            const structuredEj = await ecies.encrypt(pubKeyBuf, bufferedFile);

            // Serialize the encrypted data object
            encryptedEj = Buffer.concat([
                structuredEj.epk,
                structuredEj.iv,
                structuredEj.ct,
                structuredEj.mac,
            ]);
        } catch (err) {
            console.log(`useBCH.handleEncryptedOpReturn() error: ` + err);
            throw err;
        }


generateOpReturnScript = (BCH, optionalOpReturnMsg, destinationAddress, airdropFlag, airdropTokenId, encryptionFlag, encryptedEj) {}

Match the approach used in D11617 so we can display error notifications of specific error msgs in the app

Hm maybe this is reflective of earlier implementation issue -- shouldn't the airdropTokenId be visible in this string? We don't need to further encode this.

https://reviews.bitcoinabc.org/rABCc069254a1268a846506e61ece05df90d7083f413

Let's sort this out before the sendXec refactor -- please open a new task to patch. TokenId should appear directly in the msg rather than hex encoded (which takes more space)

Match the exact returned result of the function and not slice(0,12)

Use currency.opReturn.opReturnPrefixHex

We will be refactoring / deprecating this BCH object

It is a nice idea to have all of these opcodes in a repo, i.e. the ultimate source of this at https://github.com/Bitcoin-com/bitcoincash-ops/blob/master/index.json

But I think not worth it to go through BCH to get to that directly. We'll eventually handle this differently.

Remove the TODO comment

Is this approach (versus the Buffer.from... approach used below in the script.push calls) necessary?

Using a set prefix from the currency settings object should be intuitive or there should at least be a standard approach that future developers can reference. We shouldn't have multiple patterns for this.