Schedule Transactions used for Secure / Safe Trade Standard

[AdrianKBL]

Summary:

This proposal aims to standardize the way of generating the codes of a Schedule Transaction, so for example, when we use tools such as Secure Trade (HashPack) or Safe Trade (Kabila), they are compatible.

Motivation:

Right now if someone tries to send one or more NFTs through Schedule Transactions, either from Kabila to HashPack, from HashPack to Kabila or from HashPack to Blade or any other Wallet, it is not supported as we use different algorithms to obfuscate the generated code. . We believe that this is a great barrier for users, we have to make their lives easier and in this case we are making it more difficult for them.

Specification:

From Kabila, we believe that the correct way to standardize this, would be to use as the generated code:

scheduleId-accReceiver-timeStampCreated and obfuscate it to base64.

These parameters are necessary, so when the person who receives them introduces the code, through the accReceiver we can know if the code is correct for that AccountId, so he doesn't have to pay the fee to consult the scheduleId, the timeStampCreated, to know if it has expired (if it has expired we do not consult the network and we do not pay fees).

Backwards Compatibility

This proposal is expected to be backwards compatible, as it only introduces a new way to standardize how wallets or applications generate these codes.

[mshakeg]

@AdriMsM91 I wouldn't say the following is directed to the idea you're proposing, but more around the idea of scheduled transactions. Does it not open up the possibility for MEV on Hedera? As it publicises when the Hedera network will process a transaction well in advance.

[teacoat]

We are open to a standard at hashpack, though our big concern around this is fee display in other wallets. Fee's can be set up quite maliciously and without a comprehensive fee breakdown or a fee-type blacklist of this could be used to scam users.

[nickpoorman]

@AdriMsM91 - What's the use case here? I'm not clear on what the goal is or why. Are you saying that you want to standardize putting scheduleId-accReceiver-timeStampCreated in a memo field? If so, what's the reason for that?

[AdrianKBL]

Hello @nickpoorman this is nothing related about the memo, this is related about how Wallets can share the different codes of Schedule Transactions, such as Kabila / HashPack / Blade...

As you can see the Code generated by HashPack wallet isn't valid for Kabila Wallet and viceverse. This is creating a really big GAP for new users, then you need to explain them that they need to import the Account in the other wallet If they want to transfer NFTs with FallBack Fees otherwise there isn't any way...etc.

We faced many many big problems with this, that's why we think it's really important.