feat: add output execution capability#440
Merged
brunomenezes merged 4 commits intomainfrom Mar 9, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
guidanoli
previously approved these changes
Mar 6, 2026
e365510 to
12014df
Compare
7d39da9 to
494042f
Compare
* When actively displaying outputs and the epoch is not status claim_accepted the components will track the epoch status by invalidating the epoch(s) query to retrieve latest values.
494042f to
bb6a196
Compare
3 tasks
guidanoli
approved these changes
Mar 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Code changes to add support for output execution. issue #427
I want to draw attention to one "business logic" here: If the epoch's status where the output(s) you are looking at was generated is not yet set as
CLAIM_ACCEPTED, the application will present a wordingwaiting claimwith a info icon with a tooltip with more details if you hover on it, and will actively observe the epoch until its status moves to the expected status (i.e.CLAIM_ACCEPTED). The execution itself follows the usual workflow:click the execute button->confirm transaction in the wallet->wait transaction confirmation.A Deployed version of this branch/PR: https://dave-git-feat-add-output-execution-capability-cartesi.vercel.app/
Testing Steps
It is expected that a Cartesi Application is available to generate voucher outputs.
Outputsoption in the input of interest.CLAIM_ACCEPTED, you shall see a blue square at the bottom right of the output content sayingWAITING CLAIMℹ (the square icon here is just for reference)CLAIM_ACCEPTED, you shall see a button with textExecuteif the output is not yet executed.Executed, and on the right side, the Tx hash will appear. PS: The transaction hash becomes a link only for testnets and mainnets. For devnets, it is only text you can copycloses #427