# `Attesto.RefreshStore.ETS`
[🔗](https://github.com/XukuLLC/attesto/blob/v2.6.1/lib/attesto/refresh_store/ets.ex#L1)

Single-node ETS implementation of `Attesto.RefreshStore`.

Tokens live in an ETS table owned by a `GenServer`. The security-
critical `rotate/4` transition is serialised through the owning process.
It validates the parent/child pair and performs one list-form ETS insert of
the post-parent and child, so direct readers cannot observe an intermediate
state. `insert/1` and `revoke_family/1` go through the same process, so all
family mutations are ordered.

This is a per-node store. A multi-node deployment MUST back
`Attesto.RefreshStore` with a shared store whose complete `rotate/4`
transaction is atomic across nodes and serialized against family
revocation, or reuse detection only holds per node.

Start options: `:sweep_interval_ms` (default `60_000`). The sweeper retains
expired consumed generations only through their successor retry deadline,
then removes them even while a later generation remains live. This bounds a
continuously rotated family's retained history without forcing a live
family to reauthenticate after an arbitrary number of rotations. A
family-keyed membership index keeps revocation proportional to that family's
retained size instead of scanning the complete token table.
Revoked-family markers are retained for the lifetime of the store, as
required by the sticky-revocation contract, including after all token rows
have expired.

    children = [Attesto.RefreshStore.ETS]

# `reset`

```elixir
@spec reset() :: :ok
```

Clear every entry. Test-facing.

# `start_link`

```elixir
@spec start_link(keyword()) :: GenServer.on_start()
```

---

*Consult [api-reference.md](api-reference.md) for complete listing*