---
title: "HopStamp"
description: "one hop of an acquisition unit through the system: the stage, the host, the time, the job, and the trace and span that hop wrote, so the unit's flow is one trace"
section: concepts
address: /concepts/hopstamp
contract: 0476e35e6e275db5
---

# HopStamp

one hop of an acquisition unit through the system: the stage, the host, the time, the job, and the trace and span that hop wrote, so the unit's flow is one trace

[figure: HopStamp is a value at none scope. The drawing shows its fields and the objects that they point at.]

| property | value |
|---|---|
| kind | value |
| scope | none |
| key | none |
| store | none |
| family | registers |



## Fields


| field | type | required | note |
|---|---|---|---|
| `stage` | `one of fetched \| captured \| deposited \| refined \| closed \| handed over \| accepted \| matched \| delivered` | yes |  |
| `host` | `text` | yes |  |
| `at` | `time` | yes |  |
| `job` | `id` | yes |  |
| `trace_id` | `text` | yes | the W3C trace id of the unit's flow |
| `span_id` | `text` | yes | this hop's span |



## Routes that use it
No route takes or returns HopStamp directly. The record holds it, and the objects that point at it reach it.