AscribeRevived

Edition · 72/100

edition id 18rC3N8JPRgKxyteRxa5yQGpHiKgUhLNNZ · main era (2015-2018) unconsigned

Add information as the owner

Piece
17EMcThGgcx8o1d7dv31orJvyJud2Yq3CF assignment uncertain: this file was registered several times
Registered on-chain
2016-07-22 21:12:49 UTC
Current owner address
18rC3N8JPRgKxyteRxa5yQGpHiKgUhLNNZ
Current holder address
18rC3N8JPRgKxyteRxa5yQGpHiKgUhLNNZ
File hash address
1LRB3AkfkYmbTryJBxaS5KXXAwTCNTbUBb
Metadata hash address
1ELee89TktERQVZ6EHt9eynseE9UcXf5uM
Edition number
issued 2 times The original service registered edition 72 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: 193u8XSE…MM1P8NCc.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-07-22 21:12REGISTER1AScRhqd…FsqmLquG18rC3N8J…KgUhLNNZb1324de3…138d146c
2016-07-23 10:14CONSIGN18rC3N8J…KgUhLNNZ1MzYbaJ4…JhFqBb747afb049d…ef2fe759
2016-08-24 07:37UNCONSIGN1MzYbaJ4…JhFqBb7418rC3N8J…KgUhLNNZf2963623…574b0a0f

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/18rC3N8JPRgKxyteRxa5yQGpHiKgUhLNNZ/