AscribeRevived

Edition · 52/100

edition id 1HU4kNsDGdFAiSZRJ4T2H1ENsP7PqqrCY1 · main era (2015-2018) unconsigned

Add information as the owner

Piece
17EMcThGgcx8o1d7dv31orJvyJud2Yq3CF assignment uncertain: this file was registered several times
Registered on-chain
2016-07-22 21:12:49 UTC
Current owner address
1HU4kNsDGdFAiSZRJ4T2H1ENsP7PqqrCY1
Current holder address
1HU4kNsDGdFAiSZRJ4T2H1ENsP7PqqrCY1
File hash address
1LRB3AkfkYmbTryJBxaS5KXXAwTCNTbUBb
Metadata hash address
13Ttu56PpPBHakUwvWvMhQgJSjF63eQ7NG
Edition number
issued 2 times The original service registered edition 52 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: 1GBCDSfc…jrExdAR7.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-07-22 21:12REGISTER1AScRhqd…FsqmLquG1HU4kNsD…7PqqrCY154ca78c7…67160572
2016-07-23 10:14CONSIGN1HU4kNsD…7PqqrCY11HQnC8YY…yDHCNETHaa9f8b52…d543116a
2016-08-24 07:18UNCONSIGN1HQnC8YY…yDHCNETH1HU4kNsD…7PqqrCY15cdf5f0d…a8661a4d

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/1HU4kNsDGdFAiSZRJ4T2H1ENsP7PqqrCY1/