-
Notifications
You must be signed in to change notification settings - Fork 66
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
Add predicate support #886
Comments
|
|
In this case, it would be filtering predicate inputs by the owner address. Here's the overall flow that I'm picturing, given that we want to have handlers for specific witnesses and coin owners:
Witness validation procedure:
Here's an example of what I'm thinking this standardized witness format could be to enable validation:
|
Witness
data to filter Transaction
s
Here's a more concrete description of how this could work, broken down step by step. There's definitely some lower-level details I'm missing but this should give a rough sketch of the general usage & flow. User flow: Opening and fulfilling a market orderSetup:
User A opens a position to buy eth:
User B fulfills market order by selling eth
|
Hi guys, I am happy to participate in this discussion in any case, if you need any help tag me 🫡 |
Temporarily blocked by release of fuels 0.50 |
log
#881 we need to create a standard for includingWitness
data in aTransaction
- where thisWitness
data can be filtered on aTransaction
level downstreamThe text was updated successfully, but these errors were encountered: