TX | Decentralized Exchange for Startups | Blockchain library

A possible solution, based on tidyr::pivot_wider:

Had this issue myself, apparently it's some sort of Ganache CLI error but the simplest fix I could find was to change the network id in Ganache through settings>server to 1337. It restarts the session so you'd then need to change the address and private key variable.

If it's the same tutorial I'm doing, you're likely to come unstuck after this... the code for transaction should be:

It may be easier with names_glue in pivot_wider

Just use the tf.keras.callbacks.CSVLogger and any regression metric you want to log during training:

You get the exact same error with the slightly simpler definition of Foo c m given here:

I checked your full code and it is working.

You are inheriting from ERC721URIStorage which inherits from ERC721 If you check the transferFrom inside ERC721:

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.

I am not sure if you have something like the approach below in mind. It is basically a custom function which we use in a nested purrr::map call. The outer call loops over the number of pairs: 2,3, 4 and the inner call uses combn to create all possible combinations as input and uses the custom function to create the desired output.

You need to write: