AscribeRevived

Edition · 1/100

edition id 159dQcmogi11UVuEfJeaX3obJm7zW92C6k · main era (2015-2018) registered

Add information as the owner

Piece
16wBXY77p5LpJShbr3pmehFYjfbCEiukhA assignment uncertain: this file was registered several times
Registered on-chain
2017-06-10 02:58:49 UTC
Current owner address
159dQcmogi11UVuEfJeaX3obJm7zW92C6k
Current holder address
159dQcmogi11UVuEfJeaX3obJm7zW92C6k
File hash address
1Px6P1c382ZaJWbSFR8g9ApoLSFv7QmuZo
Metadata hash address
18LSVm4C2nYC8micUTTiH8xsqhbzuT48g7
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: 1Dim3yPR…37AJz9P4.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2017-06-10 02:58REGISTER1AScRhqd…FsqmLquG159dQcmo…7zW92C6k640e1b93…ca50bc76
2017-06-10 05:27LOAN until May 13, 2017159dQcmo…7zW92C6k1Ki1VwBP…36PwuDf31db77fad…0540ae7f

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/159dQcmogi11UVuEfJeaX3obJm7zW92C6k/