AscribeRevived

Edition · 1/1

edition id 1LZ4tzNzmZvn8XL9puZ97hXm6ecLCGhzU · main era (2015-2018) migrated

Add information as the owner

Piece
155KExWRTuNJuXrfFpN8dgtjQ3VViuHffS assignment uncertain: this file was registered several times
Registered on-chain
2016-05-27 18:06:05 UTC
Current owner address
1PKqo2kyVcSKeo94tD8dzh6taGJMS3vDR5
Current holder address
1PKqo2kyVcSKeo94tD8dzh6taGJMS3vDR5
File hash address
1Co1xau9obUUCFHiEJjksXV2nqqCqbJDge
Metadata hash address
1C4BdgbAmHjEEKUMt5fapcRmk27s1enUUX
Edition number
issued 3 times The original service registered edition 1 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: 1Q8ELARq…cL2MP6Av, 1GSzcYbD…dGEVL7L6.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-05-27 18:06REGISTER1AScRhqd…FsqmLquG1LZ4tzNz…ecLCGhzUfb64127b…cd7a34f0
2016-05-27 18:06MIGRATE1LZ4tzNz…ecLCGhzU1PKqo2ky…JMS3vDR5f10703ee…73334ca5

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