-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FV, LV, Lease Support #151
Comments
Can you explain where exactly you want these fields supported? They don't apply to inner transactions and I'm not sure why you'd want to check them in an app. |
These are useful to ensure you don't have a duplicate transaction within a given set of blocks based on a given lease value. One example would be a contract that allows a receiver to receive x amount of token every 1000 blocks. When receiving a request, the smart contract would make the check and if the request hasn't been performed in that set of blocks, it would issue an inner transaction to give the receiver the coins. I can give you an example in Teal if you would like to see it. These values are defined here under the block Common Fields for Teal: FirstValid - fv I am an attorney and these are useful in creating spend thrift trusts (or allowances). |
It's a [sender / lease ] pair thats tracked up through its LastValid round. So any duplicate wouldn't even be allowed into the mempool at all. A contract would never find a conflict because one would never be submitted. |
I noticed that txns don't allow for fv, lv and lease support. This would be very beneficial.
The text was updated successfully, but these errors were encountered: