use new ticket

Author: rklaehn

src/app/blog/0rtt-api/page.mdx

@@ -247,17 +247,17 @@ Running the accept side prints a ticket that we need to connect. We want this to
 ```
 Listening on: NodeAddr { node_id: PublicKey(e7c3b8c21ad4393c1d21c2ca05c5e9fdb6492aa2f077ae776a6fe6d0c5ff3dd7), relay_url: None, direct_addresses: {5.223.43.41:34981, [2a01:4ff:2f0:14d4::1]:34982} }
 Node ID: PublicKey(e7c3b8c21ad4393c1d21c2ca05c5e9fdb6492aa2f077ae776a6fe6d0c5ff3dd7)
-Ticket: nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjuwiqeajkaecp6axqctkaaaaaaaaaaaabu2iqe
+Ticket: nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjrtxaeajkaecp6axqctkaaaaaaaaaaaabrxxae
 ```
 
 ## Connect side
 
 On the connect side, we just need to specify the node ticket to connect to and optionally the number of rounds.
 
 ```
-❯ RUST_LOG=0rtt=trace cargo run --release --features examples --example 0rtt nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjuwiqeajkaecp6axqctkaaaaaaaaaaaabu2iqe
+❯ RUST_LOG=0rtt=trace cargo run --release --features examples --example 0rtt nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjrtxaeajkaecp6axqctkaaaaaaaaaaaabrxxae
     Finished `release` profile [optimized + debuginfo] target(s) in 0.17s
-     Running `target/release/examples/0rtt nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjuwiqeajkaecp6axqctkaaaaaaaaaaaabu2iqe`
+     Running `target/release/examples/0rtt nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjrtxaeajkaecp6axqctkaaaaaaaaaaaabrxxae`
 2025-05-27T11:13:09.846859Z TRACE 0rtt: 0-RTT not possible from our side
 round 0: 537464 us
 2025-05-27T11:13:10.384057Z TRACE 0rtt: 0-RTT possible from our side
@@ -334,10 +334,10 @@ So you would use 0-RTT if communication is in small bursts spaced many minutes t
 So this is the option we ended up implementing. Here is the output after this modification. We now get a 0-rtt connection every time.
 
 ```
-❯ RUST_LOG=0rtt=trace cargo run --release --features examples --example 0rtt nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjuwiqeajkaecp6axqctkaaaaaaaaaaaabu2iqe
+❯ RUST_LOG=0rtt=trace cargo run --release --features examples --example 0rtt nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjrtxaeajkaecp6axqctkaaaaaaaaaaaabrxxae
    Compiling iroh v0.35.0 (/Users/rklaehn/projects_git/iroh/iroh)
     Finished `release` profile [optimized + debuginfo] target(s) in 16.63s
-     Running `target/release/examples/0rtt nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjuwiqeajkaecp6axqctkaaaaaaaaaaaabu2iqe`
+     Running `target/release/examples/0rtt nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjrtxaeajkaecp6axqctkaaaaaaaaaaaabrxxae`
 2025-05-27T11:17:11.384959Z TRACE 0rtt: 0-RTT not possible from our side
 round 0: 556011 us
 2025-05-27T11:17:11.941692Z TRACE 0rtt: 0-RTT possible from our side
@@ -440,7 +440,7 @@ cargo run --release --features=examples --example 0rtt <ticket>
 You can also connect to our test node that should be far away from most readers of this blog post:
 
 ```
-cargo run --release --features examples --example 0rtt nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjuwiqeajkaecp6axqctkaaaaaaaaaaaabu2iqe
+cargo run --release --features examples --example 0rtt nodeadt4hogcdlkdspa5ehbmubof5h63msjkulyhpltxnjx6nugf7465oaacaac56kzjrtxaeajkaecp6axqctkaaaaaaaaaaaabrxxae
 ```
 
 You can disable 0-rtt using the `--disable-0rtt` arg. Since the node above is far away, you should see a noticeable difference.