AscribeRevived

Edition · 1/1

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

Add information as the owner

Piece
1E73R3drZ5QLUSdCup88GN1bRS6u3vw4K6 assignment uncertain: this file was registered several times
Registered on-chain
2017-03-10 05:18:26 UTC
Current owner address
1NCWG88oNHhN5NPpds17qLPZEd8NxyU6AE
Current holder address
1NCWG88oNHhN5NPpds17qLPZEd8NxyU6AE
File hash address
1GBuubamYMq3PfkxQatxGifRX2YRegtAbk
Metadata hash address
1AV5cEXj8YwC9jpQ3bUUs4cF2ZBmGkZQDW
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: 13XNDcKp…ggrXMhRC.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2017-03-10 05:18REGISTER1AScRhqd…FsqmLquG1K1w5B1b…Yxba2hKCbe243a0b…1ac72736
2017-03-10 05:42CONSIGN1K1w5B1b…Yxba2hKC1HDmwK4v…8XT5T6aQd94376a3…ea8f52cd
2017-03-10 07:57TRANSFER1HDmwK4v…8XT5T6aQ1NCWG88o…8NxyU6AEaee6d075…489e014c

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