Event Anchor
An event anchor records the event digest, time credential, signature, and predecessor relationship used for later review.
Core Model
Polaris focuses on event anchors, not business payload disclosure
The protocol proves that an event digest was anchored under a time credential. It does not require business data itself to be exposed to public networks or other nodes.
Verification
Verification confirms that the anchor was issued by a trusted node, the event digest matches, and the chain relationship is valid.
Tracing
Anchors from the same source can form a predecessor chain, supporting reconciliation, audit review, and dispute handling.
Developer API
Core event-anchor APIs
Developers mainly integrate Polaris through four actions: create, query, verify, and trace.
| Method | Endpoint | Purpose |
|---|---|---|
| POST | /v1/event-anchors | Create an event anchor |
| GET | /v1/event-anchors/latest | Get the latest anchor for one origin |
| POST | /v1/event-anchors/batch | Create anchors in batch |
| POST | /v1/event-anchors:verify | Verify a single anchor |
| POST | /v1/event-anchors:batchVerify | Verify anchors in batch |
| GET | /v1/event-anchors/{anchor_id} | Read anchor details |
| GET | /v1/event-anchors/{anchor_id}/trace | Trace the event chain |
| POST | /v1/event-anchors/sync | Import offline or remote anchors |
Product Value
What business actions fit Polaris
Polaris does not replace business systems. It adds reviewable time and existence credentials to critical business actions.
Business Event Registration
Orders, approvals, task completion, and state changes can be converted into event digests and written as event anchors.
Audit & Reconciliation
Auditors can use anchor identifiers and event digests to verify whether an event existed, whether it changed, and whether it sits in the expected chain.
Node Coordination
Multiple nodes can compare and synchronize digests to locate differences and improve cross-system review efficiency.