You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Permissioned MVP] Transition Flow Implementation - Ensuring single use for a nametag address by a token state #12
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
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
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
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
"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?
Activity
[-][MVP] Transaction Flow Implementation - Verification of Unicity anchor connection[/-][+][MVP] Transaction Flow Implementation - Ensuring single use for a nametag address by a token state[/+][-][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[/+]mareksepp commentedon Feb 14, 2025
Transaction flow: all token operations (mint, send, receive, split, permissioned dust collection, nametags). Verifies inclusion of hashroot into the Unicity anchor chain.
[-][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[/+]vrogojin commentedon Mar 25, 2025
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
mareksepp commentedon Mar 22, 2026
"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?