# When using QUIC numerous \`State mismatch\` errors appear

**URL:** <https://forum.autonomys.xyz/t/when-using-quic-numerous-state-mismatch-errors-appear/1936>\
**Category:** Testing\
**Created:** [September 30, 2023, 5:57pm UTC](https://forum.autonomys.xyz/t/when-using-quic-numerous-state-mismatch-errors-appear/1936 "2023-09-30T17:57:00Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![SeryogaLeshii](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/seryogaleshii/32/551_2.png) [@SeryogaLeshii](https://forum.autonomys.xyz/u/SeryogaLeshii)\
**Post date:** [September 30, 2023, 5:57pm UTC](https://forum.autonomys.xyz/t/when-using-quic-numerous-state-mismatch-errors-appear/1936/1 "2023-09-30T17:57:00Z")

</div>

Release: gemini-3f-2023-sep-29  
Listening on both QUIC and QUIC-v1.  
So far, the problem only arises for the farmer.

The issue is described in [Quic state mismatch error · Issue #3507 · libp2p/rust-libp2p · GitHub](https://github.com/libp2p/rust-libp2p/issues/3507) and fixed in libp2p-quic v0.9.0.

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [October 1, 2023, 12:36am UTC](https://forum.autonomys.xyz/t/when-using-quic-numerous-state-mismatch-errors-appear/1936/2 "2023-10-01T00:36:32Z")

</div>

We have not upgraded to latest QUIC version on 3f and I’m not sure we will, I’ll let @shamil to weight in on that. But it should be fully functional on next version of Gemini network and maybe even enabled as the primary protocol.

---

<div class="post-metadata">

**Author:** ![SeryogaLeshii](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/seryogaleshii/32/551_2.png) [@SeryogaLeshii](https://forum.autonomys.xyz/u/SeryogaLeshii)\
**Post date:** [October 1, 2023, 9:22am UTC](https://forum.autonomys.xyz/t/when-using-quic-numerous-state-mismatch-errors-appear/1936/3 "2023-10-01T09:22:57Z")

</div>

Well, I tried building it myself with libp2p-quic v0.9.2 and everything is working fine so far, except, of course, there are almost no peers on QUIC.

Also the farmer’s logs are filled with these warnings. Based on what I have researched, they are generally harmless.

```plaintext
2023-10-01T07:46:48.960778Z INFO single_disk_farm{disk_farm_index=0}: subspace_farmer::reward_signing: Successfully signed reward hash 0xf498ddb2dfc3dbba8d75aa398bfd962214ffa24977f448696495cd737c30122a
2023-10-01T07:53:55.462243Z WARN quinn_proto::connection: discarding possible duplicate packet                
2023-10-01T07:53:55.512635Z WARN quinn_proto::connection: discarding possible duplicate packet
2023-10-01T07:53:55.512890Z WARN quinn_proto::connection: discarding possible duplicate packet                
2023-10-01T07:53:55.820844Z WARN quinn_proto::connection: discarding possible duplicate packet                
2023-10-01T07:53:55.821112Z WARN quinn_proto::connection: discarding possible duplicate packet                
2023-10-01T07:53:55.821862Z WARN quinn_proto::connection: discarding possible duplicate packet
2023-10-01T07:53:55.822154Z WARN quinn_proto::connection: discarding possible duplicate packet                
2023-10-01T07:53:56.123143Z WARN quinn_proto::connection: discarding possible duplicate packet                
2023-10-01T07:53:56.123165Z WARN quinn_proto::connection: discarding possible duplicate packet                
2023-10-01T07:53:56.124398Z WARN quinn_proto::connection: discarding possible duplicate packet                
2023-10-01T08:03:47.868658Z INFO single_disk_farm{disk_farm_index=0}: subspace_farmer::reward_signing: Successfully signed reward hash 0x9b1c3b3741349c46ded282ca79d7e46a237d7d0fb125b4bbe5596b426fd3afee

```

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [October 1, 2023, 9:54am UTC](https://forum.autonomys.xyz/t/when-using-quic-numerous-state-mismatch-errors-appear/1936/4 "2023-10-01T09:54:12Z")

</div>

It might be necessary to upgrade the rest of the network to newer version as well to avoid these

---

<div class="post-metadata">

**Author:** ![z\_W](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/z_w/32/1135_2.png) [@z\_W](https://forum.autonomys.xyz/u/z_W)\
**Post date:** [October 1, 2023, 3:35pm UTC](https://forum.autonomys.xyz/t/when-using-quic-numerous-state-mismatch-errors-appear/1936/5 "2023-10-01T15:35:40Z")

</div>

Is your Quic version compiled after modifying the official code? I also want to give Quic a try.

---

<div class="post-metadata">

**Author:** ![SeryogaLeshii](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/seryogaleshii/32/551_2.png) [@SeryogaLeshii](https://forum.autonomys.xyz/u/SeryogaLeshii)\
**Post date:** [October 1, 2023, 3:50pm UTC](https://forum.autonomys.xyz/t/when-using-quic-numerous-state-mismatch-errors-appear/1936/6 "2023-10-01T15:50:17Z")

</div>

If you want to use libp2p-quic v0.9.2, just edit the corresponding line with the crate version in the `crates/subspace-networking/Cargo.toml` file:

```diff
[dependencies.libp2p-quic]
+ version = "0.9.2-alpha"
- version = "0.8.0-alpha"
features = ["tokio"]

```

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [October 2, 2023, 1:19am UTC](https://forum.autonomys.xyz/t/when-using-quic-numerous-state-mismatch-errors-appear/1936/7 "2023-10-02T01:19:05Z")

</div>

You don’t need `-alpha` anymore

---

<div class="post-metadata">

**Author:** ![shamil](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/shamil/32/875_2.png) [@shamil](https://forum.autonomys.xyz/u/shamil)\
**Post date:** [October 9, 2023, 7:48am UTC](https://forum.autonomys.xyz/t/when-using-quic-numerous-state-mismatch-errors-appear/1936/8 "2023-10-09T07:48:46Z")

</div>

This PR upgrades QUIC: [Adjust QUIC usage in subspace-networking crate by shamil-gadelshin · Pull Request #2075 · subspace/subspace · GitHub](https://github.com/subspace/subspace/pull/2075)
