Skip to content

[Permissioned MVP] Transition Flow Implementation - Ensuring single use for a nametag address by a token state #12

Open

Description

@mareksepp
No description provided.

Activity

  1. moved this to Todo in Unicityon Feb 14, 2025
  2. changed the title [-][MVP] Transaction Flow Implementation - Verification of Unicity anchor connection[/-] [+][MVP] Transaction Flow Implementation - Ensuring single use for a nametag address by a token state[/+] on Feb 14, 2025
  3. changed the title [-][MVP] Transaction Flow Implementation - Ensuring single use for a nametag address by a token state[/-] [+][Permissioned MVP] Transaction Flow Implementation - Ensuring single use for a nametag address by a token state[/+] on Feb 14, 2025
  4. mareksepp commented on Feb 14, 2025

    @mareksepp
    ContributorAuthor

    Transaction flow: all token operations (mint, send, receive, split, permissioned dust collection, nametags). Verifies inclusion of hashroot into the Unicity anchor chain.

  5. self-assigned this
    on Feb 20, 2025
  6. changed the title [-][Permissioned MVP] Transaction Flow Implementation - Ensuring single use for a nametag address by a token state[/-] [+][Permissioned MVP] Transition Flow Implementation - Ensuring single use for a nametag address by a token state[/+] on Mar 20, 2025
  7. vrogojin commented on Mar 25, 2025

    @vrogojin

    Will be resolved after unicitynetwork/aggregators_net#4 is completed. Will be resolving nametag to its reference address at the verifiable timepoint when the respective transaction addressing the nametag token was created. The aggregator block number attached to the AB rootchain will serve as verifiable timestamp. In this way double-spend via multiple changes of nametag proxied address will be resolved since at any time point only single address referenced by the nametag may exist

  8. moved this from Todo to Blocked in Unicityon Jan 20, 2026
  9. mareksepp commented on Mar 22, 2026

    @mareksepp
    ContributorAuthor

    "Will be resolved after unicitynetwork/aggregators_net#4 is completed" is completed that was referenced in the previous comment, also this task has rather long history - what are the next steps here @vrogojin to get it out from "Blocked", is it still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

  • Status
    Blocked

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions