AscribeRevived

Edition · 1/1

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

Add information as the owner

Piece
1GnWmEPq1wjSmMPjnGya7SUZYwppqQSKkA assignment uncertain: this file was registered several times
Registered on-chain
2016-05-27 18:21:44 UTC
Current owner address
19gAyFUz2MTN7qoo94vSUkcUMag5GqSqKp
Current holder address
19gAyFUz2MTN7qoo94vSUkcUMag5GqSqKp
File hash address
15MTqk9h6JhyLJ1yp5ra2RuRvSSSbhu2gi
Metadata hash address
1BQWpBUHWMR5uXne9mYdfcSaR8u3f3C5fV
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: 1LmAFkn7…a1duev1V.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-05-27 18:21REGISTER1AScRhqd…FsqmLquG1LESXuaq…gj8WQFvH1fb59292…812de020
2016-05-27 18:21MIGRATE1LESXuaq…gj8WQFvH19gAyFUz…g5GqSqKpdc65e3b0…da135775

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