AscribeRevived

Edition · 1/1

edition id 1HHWAUthhDP5xEEfydrcAyoJhxStE1CNUG · main era (2015-2018) consigned

Add information as the owner

Piece
1PpJxqDrbqtjJcpN36UH5uJcKDE8iM19ex assignment uncertain: this file was registered several times
Registered on-chain
2017-10-18 11:28:47 UTC
Current owner address
1HHWAUthhDP5xEEfydrcAyoJhxStE1CNUG
Current holder address
17SPqsAZiBZPXp2gg2VBBLWnQ3ACmQ6unK (consigned)
File hash address
15jjwHZuYoMxi66dt7d4DnAM3hN42Sx9vh
Metadata hash address
1Mzaw7TSbDCnmNEd3d7fxK8tVFxCqcWyqz
Edition number
issued 2 times The original service registered edition 1 of this file to 2 different addresses. Often one file was registered as several separate works, each with its own edition numbers. The service's software was meant to issue each number only once per file, but that check was switched off. This edition is not a copy. This site treats every address as its own edition, because the SPOOL specification defines an edition by its address, and a registration never moves an edition that already exists. How duplicate edition numbers are read.
The same number of this file also went to: 17ZtFsTs…BtJ7aMFa.
Notes
registered again by 575fb3fbc824
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2017-10-18 11:28REGISTER1AScRhqd…FsqmLquG1HHWAUth…StE1CNUG3fb05148…c5433cac
2017-10-18 11:28REGISTER1AScRhqd…FsqmLquG1HHWAUth…StE1CNUG575fb3fb…11e9000erepeat registration; the protocol allows one per edition
2017-10-19 18:09CONSIGN1HHWAUth…StE1CNUG17SPqsAZ…ACmQ6unK20220479…b440af86

What people did on ascribe.io between 19 October 2017 and 18 September 2018 reached the blockchain only if the service's final batch of 18 September 2018 carried it, so a registration, transfer, consignment or loan from those months may be missing here. Why

JSON: /api/editions/1HHWAUthhDP5xEEfydrcAyoJhxStE1CNUG/