Align HeadLogic: Not validate tx on NewTx

[ch1bo]

When updating the spec we realized we do not need an applicability to the confirmed (last snapshot) UTxO set on NewTx. This is reason enough to re-think whether this makes even sense.

• This PR is now dropping TxSeen and TxExpired in favor of TxValid and TxInvalid. See commit description for rationale.

• Although it fixes a bug int he ttl handling, this PR does not change the behavior. Notably, the ttl == 0 cases for ReqSn and AckSn are not defined. They will just fall out of the queue. We might want to emit a SnapshotExpired or HeadLikelyStuck message.

---

• CHANGELOG updated
• Documentation updated
• Added and/or updated haddocks
• No new TODOs introduced or explained herafter

[github-actions]

Transactions Costs

Sizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using arbitrary values and results are not fully deterministic and comparable to previous runs.

Metadata
Generated at	2023-02-24 20:55:06.652088709 UTC
Max. memory units	14000000
Max. CPU units	10000000000
Max. tx size (kB)	16384

Script summary

Name	Hash	Size (Bytes)
μHead	N/A	4600
νInitial	7bb44e248f92ae5d2c4c744244b469d59a5bfa8a5d8ce9b6b27e5750	5530
νCommit	70c545fc894ada81ad46715bac1a11fa755b3e3a1d94f03254a4d397	2473
νHead	58cef84ce7e80b1b3089a10d825da2f41ec1cb5ad923d9f39d842f3c	9998

Cost of Init Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	5198	15.32	6.07	0.55
2	5399	16.74	6.58	0.57
3	5611	20.38	7.99	0.62
5	6017	25.18	9.80	0.69
10	7046	37.41	14.44	0.87
36	12374	99.20	37.77	1.77

Cost of Commit Transaction

Currently only one UTxO per commit allowed (this is about to change soon)

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	633	20.95	8.45	0.41

Cost of CollectCom Transaction

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	13260	21.89	8.77	0.97
2	114	13604	37.14	15.01	1.16
3	170	13957	54.10	22.04	1.36
4	227	14309	74.92	30.67	1.61
5	284	14660	97.76	40.22	1.88

Cost of Close Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	10634	16.83	7.37	0.81
2	10777	17.73	7.78	0.82
3	10942	19.21	8.58	0.85
5	11300	22.59	10.60	0.91
10	12165	29.95	14.69	1.03
43	14801	58.67	27.18	1.47

Cost of Contest Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	10641	21.47	8.96	0.86
2	10841	23.33	10.08	0.89
3	10978	24.47	10.56	0.91
5	11301	28.02	12.38	0.96
10	12152	37.56	17.34	1.11
35	16321	80.90	39.86	1.81

Cost of Abort Transaction

Some variation because of random mixture of still initial and already committed outputs.

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	15306	27.81	11.83	1.13
2	15203	35.93	15.02	1.22
3	16085	68.59	29.80	1.63
4	15667	73.13	31.22	1.66

Cost of FanOut Transaction

Involves spending head output and burning head tokens. Uses ada-only UTxO for better comparability.

Parties	UTxO	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
5	0	0	15182	9.70	4.01	0.93
5	1	57	15222	10.97	4.79	0.94
5	5	285	15358	16.83	8.21	1.02
5	10	570	15542	24.95	12.82	1.13
5	20	1139	15903	39.71	21.42	1.33
5	30	1707	16262	54.98	30.24	1.53
5	33	1879	16370	59.81	32.98	1.59

[github-actions]

Test Results

292 tests  +12   286 ✔️ +12   19m 36s ⏱️ + 3m 49s
  98 suites +  4       6 💤 ±  0 
    5 files   +  1       0 ❌ ±  0 

Results for commit cf45fb7. ± Comparison against base commit 427c97c.

This pull request removes 10 and adds 22 tests. Note that renamed tests count towards both.

Hydra.Behavior/in an open head ‑ can be finalized by all parties after contestation period
Hydra.Behavior/in an open head ‑ contest automatically when detecting closing with old snapshot
Hydra.Behavior/in an open head ‑ multiple transactions get snapshotted
Hydra.Behavior/in an open head ‑ outputs utxo from confirmed snapshot when client requests it
Hydra.Behavior/in an open head ‑ reports transactions as seen only when they validate (against the confirmed ledger)
Hydra.Behavior/in an open head ‑ sees the head closed by other nodes
Hydra.Behavior/in an open head ‑ sending two conflicting transactions should lead one being confirmed and one expired
Hydra.Behavior/in an open head ‑ valid new transactions are seen by all parties
Hydra.Behavior/in an open head ‑ valid new transactions get snapshotted
Hydra.HeadLogic/Coordinated Head Protocol ‑ rejects if a requested tx is expired

Hydra.Behavior/Two participant Head ‑ can be finalized by all parties after contestation period
Hydra.Behavior/Two participant Head ‑ contest automatically when detecting closing with old snapshot
Hydra.Behavior/Two participant Head/in an open head ‑ depending transactions expire if not applicable in time
Hydra.Behavior/Two participant Head/in an open head ‑ depending transactions stay pending and are confirmed in order
Hydra.Behavior/Two participant Head/in an open head ‑ multiple transactions get snapshotted
Hydra.Behavior/Two participant Head/in an open head ‑ outputs utxo from confirmed snapshot when client requests it
Hydra.Behavior/Two participant Head/in an open head ‑ sees the head closed by other nodes
Hydra.Behavior/Two participant Head/in an open head ‑ sending two conflicting transactions should lead one being confirmed and one expired
Hydra.Behavior/Two participant Head/in an open head ‑ valid new transactions are seen by all parties
Hydra.Behavior/Two participant Head/in an open head ‑ valid new transactions get snapshotted
…

This pull request removes 1 skipped test and adds 1 skipped test. Note that renamed tests count towards both.

Hydra.Behavior/in an open head ‑ multiple transactions get snapshotted

Hydra.Behavior/Two participant Head/in an open head ‑ multiple transactions get snapshotted

[v0d1ch]

LGTM!