AscribeRevived

Edition · 6/1

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

Add information as the owner

Piece
15VAua2D8SMrLiuCqfFmKxmzLCfXMFgZPe June-July 2015 format
Registered on-chain
2015-07-01 12:48:17 UTC
Current owner address
1LBB5SEkQqoCnaieWZ7GiSKtM19EAq2hWo
Current holder address
1La9KDxyiZPp19xh99p3UgLFoyYJnyZ7Nh (consigned)
File hash address
1NHXUfW1MfKsU83yGY52xrTDVux8UwMXio
Metadata hash address
16bNy1txLP9Yi8GK7T98Jqe67Vbe5oFh7H
Edition number
issued 2 times The original service registered edition 6 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: 13GfSurc…NzX4fEGh.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2015-07-01 12:48REGISTER12udvE3z…DUCpbgoq1LBB5SEk…9EAq2hWodedca39c…48253d81
2015-07-01 12:48CONSIGN1LBB5SEk…9EAq2hWo1La9KDxy…YJnyZ7Nhd28371c1…aa867e71

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