AscribeRevived

Edition · 27/100

edition id 1Mxdpo6TANZcig9h9cDRS3kbpj3xkpyCAw · main era (2015-2018) unconsigned

Add information as the owner

Piece
12TMQaxmZYcygnymvhxA7e1PUxudByVD5U assignment uncertain: this file was registered several times
Registered on-chain
2016-07-22 19:13:14 UTC
Current owner address
1Mxdpo6TANZcig9h9cDRS3kbpj3xkpyCAw
Current holder address
1Mxdpo6TANZcig9h9cDRS3kbpj3xkpyCAw
File hash address
1LRB3AkfkYmbTryJBxaS5KXXAwTCNTbUBb
Metadata hash address
1GEeHPfjLQC6BzZbisuMG9cyq49SWUqTfg
Edition number
issued 2 times The original service registered edition 27 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: 1MMvjfZS…9XKWvHgw.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-07-22 19:13REGISTER1AScRhqd…FsqmLquG1Mxdpo6T…3xkpyCAwdfff5dab…370a27a8
2016-07-23 01:56CONSIGN1Mxdpo6T…3xkpyCAw1N1fbys3…SYTrTF1D297cf329…1daa64b6
2016-08-24 07:37UNCONSIGN1N1fbys3…SYTrTF1D1Mxdpo6T…3xkpyCAwc6ae5a5e…bd60001c

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