AscribeRevived

Edition · 19/100

edition id 1EPbLmgTb6TT1UWhvgWxXYkYyb1mpXVADG · 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
1EPbLmgTb6TT1UWhvgWxXYkYyb1mpXVADG
Current holder address
1EPbLmgTb6TT1UWhvgWxXYkYyb1mpXVADG
File hash address
1LRB3AkfkYmbTryJBxaS5KXXAwTCNTbUBb
Metadata hash address
1NfYxnp6S2b897QQfPqmijQnes5mC1Nz86
Edition number
issued 2 times The original service registered edition 19 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: 162rpuYC…NPbr616V.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-07-22 19:13REGISTER1AScRhqd…FsqmLquG1EPbLmgT…1mpXVADGe5d0826a…fb1f1e67
2016-07-23 01:56CONSIGN1EPbLmgT…1mpXVADG1DwGiWme…Y4xQAumU926fd666…af258eb7
2016-08-24 07:37UNCONSIGN1DwGiWme…Y4xQAumU1EPbLmgT…1mpXVADGfb551401…31751700

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