AscribeRevived

Edition · 1/5

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

Add information as the owner

Piece
1E4MzBnPNj4266rAREU6ZTwum3UkFi64Nn assignment uncertain: this file was registered several times
Registered on-chain
2016-02-10 15:11:45 UTC
Current owner address
1MtyKiupKspvmVfAsJcjmnKcrajLT9SG1Y
Current holder address
15TP8fWJCUazzShEzPUzNPEAGzC8VNDyGx (consigned)
File hash address
1G41wPJ7BDrRQqB4uaejBU8KdfhNxBYXML
Metadata hash address
18vGtEVFahgYz15fDADDDCSjB9JmbogvVA
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: 16Aoy8WL…2vzoJbKn.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-02-10 15:11REGISTER1AScRhqd…FsqmLquG1MtyKiup…jLT9SG1Y0f990297…769d8d43
2016-02-10 15:24CONSIGN1MtyKiup…jLT9SG1Y15TP8fWJ…C8VNDyGxb2c9136f…b68643d8

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