AscribeRevived

Edition · 3/10

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

Add information as the owner

Piece
12zdG9bFbfJeJy3qehGZ1PqCdupP238wuE June-July 2015 format
Registered on-chain
2015-06-05 09:46:24 UTC
Current owner address
1HVMuBh5J2pAtowssYyqAyan6fmMvCo7KA
Current holder address
1HVMuBh5J2pAtowssYyqAyan6fmMvCo7KA
File hash address
14xAR2sR8dmwDiPcDLdBaHj5gidTXK2gm1
Metadata hash address
15A73t4UELzmgyubBcmsap7a5r27hSC2oQ
Edition number
issued 3 times The original service registered edition 3 of this file to 3 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: 1HT2meU5…1t1J9sDX, 13bFnRZy…Csubz6jQ.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2015-06-05 09:46REGISTER12udvE3z…DUCpbgoq1HVMuBh5…mMvCo7KAebaf4eb8…115316e8
2015-06-05 09:59CONSIGN1HVMuBh5…mMvCo7KA1CFs1p7n…BWrWZSW206f95912…f20214a8
2015-06-05 10:17UNCONSIGN1CFs1p7n…BWrWZSW21HVMuBh5…mMvCo7KAd0922f68…9b314de5

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