Update scp script to refresh docker-compose by default
Home /
Input Output /
hydra-poc
577 commits this week
Sep 24, 2022
-
Oct 01, 2022
Add setup script for credentials && env dirs
Add setup script for credentials && env dirs
Use a consistent chain point for TinyWallet
As we made the wallet "interleaved", where we provide it with blocks through 'update', we need to also give it a starting point from where it queries. The fact that it still uses the local state query to get the initial utxo is another problem not solved in this.
Use a consistent chain point for TinyWallet
As we made the wallet "interleaved", where we provide it with blocks through 'update', we need to also give it a starting point from where it queries. The fact that it still uses the local state query to get the initial utxo is another problem not solved in this.
Clarify a property WalletSpec property
The premise of this property was confusing as I expected it to fail given the latest change (one commit before) in the wallet.
Not update wallet utxo on coverFee
We do not optimistically remove these UTxOs anymore and instead accept re-use should we 'coverFee' multiple times before seeing the outputs spent. This should fix a weird behavior we saw that the node does not see fuel outputs (in presence of submission failures) and even some flakyness on our test suites.
Revert "Add first round of debugging"
This reverts commit c053387c6e69acb6a0000ae285bcd5cb8a1c6c80.
Remove small test used for testing
Fix flaky spec by seeding from faucet before the scenario starts
We dont understnad the reason why, but the chain was getting in synch just too slow making the commit to fail due to missing inputs
Start a clean write of the HeadV1 spec
Based on the discussion document https://docs.google.com/document/d/1XQ0C7Ko3Ifo5a4TOcW1fDT8gMYryB54PCEgOiFaAwGE/edit?pli=1# Goals of this write-up - aims to be compacting things into a more concise definition - the relationship between off-chain and on-chain parts shall become clearer in this notation For now, this is still incomplete and tests out some different notations.
Add first round of debugging
Extended log type for apply block to find tx ids included on every observed block Created small spec to easlily reproduce the flaky spec
Add pending data type
Add helper functions to work with it
deploy: 25055151d64b4b6956cb87c5e8174a4cb59e2528
Only set pending false if we see our Comitted event
Do transition/pending handling also in the commit dialog
The submit continuation makes this very hard to follow, but this should work.
Add sending and transition checking when pending for Abort, Fanout and Close
Fix transition pending feedback
This was always pushed into the feedback list of the state
Set pending False on "response" server outputs
Not all outputs are in response to a client input. In fact, the commit would need to be distinguished.
Add transition pending feedback and extend test
Introduce the pending lens and only send events when there is nothing pending
Add pending to state
Only render "Transition pending" when True
Add a todo where not to submitting init et al twice
Fake it till you make it
Always rendering pending made it green first, then we extended the test case