Skip to content
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

Exposed Safety Analysis at Contract Creation and Input Application #850

Closed
wants to merge 16 commits into from

Conversation

nhenin
Copy link
Contributor

@nhenin nhenin commented Apr 11, 2024

No description provided.

paluh added 12 commits April 11, 2024 09:47
…uite.

1. Fixes in integration:
  * Expose separate chain-sync for quering in test env.
  * Sync wallets before usage.
  * Sync utxos after script publishing
  * Expose traces in a log file.

2. FSSemantics now operates in time intervals with slot resolution which
   we can use in "real world" transaction testing.

3. Accross the test suite we are using conflicting approaches to
   Arbitrary instances of the `Contract` type - sometimes we assume that
   the contract has correct structutre and sometimes we assume that it
   doesn't (contain invalid addresses, contain invalid currencies etc.).
   I introduced `ValidContractStructure` to distinguish these two cases.
@nhenin nhenin force-pushed the nhenin/safety-errors branch 2 times, most recently from 6f3983d to 497bf06 Compare April 12, 2024 14:00
@nhenin nhenin mentioned this pull request Apr 15, 2024
15 tasks
@nhenin nhenin changed the title Safety Analysis (WIP/draft) Exposed Safety Analysis at Contract Creation and Input Application Apr 15, 2024
@nhenin nhenin requested a review from paluh April 15, 2024 08:45
@nhenin nhenin added this to the v1.0.0 Release milestone Apr 15, 2024
@nhenin nhenin closed this Apr 18, 2024
@nhenin nhenin deleted the nhenin/safety-errors branch April 18, 2024 06:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants