AscribeRevived

Edition · 1/100

edition id 1Dim3yPRbmebXHsSv6Wajp4rCW37AJz9P4 · main era (2015-2018) consigned

Add information as the owner

Piece
16wBXY77p5LpJShbr3pmehFYjfbCEiukhA assignment uncertain: this file was registered several times
Registered on-chain
2017-06-11 21:16:55 UTC
Current owner address
1Dim3yPRbmebXHsSv6Wajp4rCW37AJz9P4
Current holder address
1MoxVnfUrCc7VFZEqMP7fDR1JBxASFCuBK (consigned)
File hash address
1Px6P1c382ZaJWbSFR8g9ApoLSFv7QmuZo
Metadata hash address
19BBdg6xfM7fNwDxhRQbnhebhRjfYyJwBw
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: 159dQcmo…7zW92C6k.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2017-06-11 21:16REGISTER1AScRhqd…FsqmLquG1Dim3yPR…37AJz9P43b5b78ff…5d8de7c9
2017-06-16 06:08CONSIGN1Dim3yPR…37AJz9P41MoxVnfU…xASFCuBK7fd4c522…8c70d8d2

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