{"version":"2.1.223","anchor":"peer-message-envelopes-can-carry-a-hop-chain-attribute","canonical_anchor":"peer-message-envelopes-can-carry-a-hop-chain-attribute","heading":"Peer message envelopes can carry a hop-chain attribute","tier":"internal","area":"Peer Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/peer-message-envelopes-can-carry-a-hop-chain-attribute","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Peer message envelopes can carry a hop-chain attribute\n\nMessages passed between peer sessions now record the path they took to get to you.\n\n**What**\n\nDelivered peer message envelopes can now include the chain of hops a message travelled, making previously internal routing state visible in the envelope itself.\n\n**Details**\n\n- The envelope builder gained a fourth argument and emits a `hop-chain=\"\u2026\"` attribute alongside the existing from, from-session and from-name attributes when a validated chain is present.\n- The sender pulls the chain from the last peer-origin user message.\n- The hop-chain admission limits \"hop-runaway\" and \"hop-loop\" already existed; this only surfaces the chain in the envelope.\n\n**Evidence**\n\n`hop-chain=\"`\n\n- Area: Peer Messaging\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}