AscribeRevived

Edition · 1

edition id 1GLeXVGgsMTEWHDy49EaokriAtVDf2wffb · main era (2015-2018) registered

Piece
unknown (no registration with this file hash found)
Registered on-chain
2015-07-28 12:34:04 UTC
Current owner address
1GLeXVGgsMTEWHDy49EaokriAtVDf2wffb
Current holder address
1GLeXVGgsMTEWHDy49EaokriAtVDf2wffb
File hash address
1AYU24QDgQhfMSfz2pLMPSroxdexegMzY
Metadata hash address
1FLuGjYUY9KWukwqLXXFN6jYC69SoUWRe1
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: 12rrBwUH…jte1qsGY.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2015-07-28 12:34REGISTER1AScRhqd…FsqmLquG1GLeXVGg…VDf2wffb7388a956…ddd4b82b

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