contract | TODO : add repo description | Portal library

That error is clear. you do not have sufficient funds. This is how you are getting the account information:

By default, graphical marks are plotted in the order they occur in the dataframe (as you noted), which means that the elements last in the dataframe will be plotted last and end up on top in the chart (called the highest "layer" or the highest "z-order"):

It appears 1.10.9-stable version has a problem and is returning a -rpc error. GETH 1.10.8-stable version works fine when running the geth command with --rpc

Having the same issue while working on the same course as you, maybe try using node 10 and redeploy everything.

Let me know if that works.

To deploy and test your smart contracts on RSK regtest yourhardhat.config.js should look as follows:

Payment args in EGLD are auto-filled from the call value you've already specified in the transaction, so you do not need to pass them as argument.

Therefore, your call data in this case would be myEndpoint@aa, without the payment arg.

As a side note, if this would've been an endpoint accepting another token than EGLD, you would've had to specify the token and amount in the data field, like: ESDTNFTTransfer@TokenIdentifier_in_hex@TokenNonce_in_hex@TokenValue_in_hex@Contract_address_in_hex@myEndpoint_in_hex@aa.

The ESDTNFTTransfer function sends any type of ESDT token, with or without nonce. If the token doesn't have a nonce (fungible), you can either pass 00 as nonce or leave the nonce space empty, like @TokenName_in_hex@@TokenValue_in_hex. Mind the fact that in order to use this function, you would have to compose a transaction with the destination set as yourself. The actual address of the destination would be contained in the data field in place ofContract_address_in_hex, making it a parameter of the ESDTNFTTransfer function.

If the endpoint accepted two tokens for example, then you could've used MultiESDTNFTTransfer@Contract_address_in_hex@02@Token1Identifier_in_hex@Token1Nonce_in_hex@Token1Value_in_hex@Token2Identifier_in_hex@Token2Nonce_in_hex@Token2Value_in_hex@myEndpoint_in_hex.

And yeah, you can always check the Elrond docs on ESDT Tokens / NFT Tokens for more details.

In the Elrond blockchain, each token is configured to have a specific number of decimals (between 0 and 18). EGLD is configured to have 18 decimals. So, 1 EGLD is actually the denominated representation of the integer value of 10^18 actually.

Using this example, if you have to send 1.5 EGLD, the un-denominated integer value is 1.5 * 10^18 = 1500000000000000000.

If you send the tx from erdpy or most of any other programmatic way, you should pass the un-denominated value. If you send the tx from web wallet and such user-friendly interfaces, there's a good chance that the values are already denominated automatically, so you sending 1.5EGLD will be automatically denominated to the actual 1.5 * 10^18 value, which is what the destination address/SC will receive as payment amount.

This is probably one of the cases where you need to pick one between being DRY and using enums.

Enums don't go very far as far as code reuse is concerned, in Java at least; and the main reason for this is that primary benefits of using enums are reaped in static code - I mean static as in "not dynamic"/"runtime", rather than static :). Although you can "reduce" code duplication, you can hardly do much of that without introducing dependency (yes, that applies to adding a common API/interface, extracting the implementation of asListString to a utility class). And that's still an undesirable trade-off.

Furthermore, if you must use an enum (for such reasons as built-in support for serialization, database mapping, JSON binding, or, well, because it's data enumeration, etc.), you have no choice but to duplicate method declarations to an extent, even if you can share the implementation: static methods just can't be inherited, and interface methods (of which getMessage would be one) shall need an implementation everywhere. I mean this way of being "DRY" will have many ways of being inelegant.

If I were you, I would simply make this data completely dynamic

You use str(0.05 * 10**18) to get the string for the value.

However, this actually outputs the value in scientific notation, which isn't what the blockchain expects.