AscribeRevived

Edition · 1/2

edition id 1L1wiXZiqM81Cr8nhiUPae4ag36wAKbxEH · main era (2015-2018) transferred

Add information as the owner

Piece
1MsXeXsi8vqP5oE6dJZ4khRimSny4fF4PW assignment uncertain: this file was registered several times
Registered on-chain
2016-03-22 10:30:49 UTC
Current owner address
1FbX78jQL4RbLEfwrVr9jHztmSY9ZusgZL
Current holder address
1FbX78jQL4RbLEfwrVr9jHztmSY9ZusgZL
File hash address
18B8prZYBuSZiiggYYtTwoDMQosSoVEH72
Metadata hash address
1285jA4HwUi8bHucZSR3D9zKwxkVBhCgZB
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: 1G5F8g5r…brHGTKXA.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-03-22 10:30REGISTER1AScRhqd…FsqmLquG1L1wiXZi…6wAKbxEHe114ef3a…2b57b90f
2016-03-22 10:40TRANSFER1L1wiXZi…6wAKbxEH1FbX78jQ…Y9ZusgZL5af1cd2f…cc42f5f4

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