AscribeRevived

Edition · 83/100

edition id 18z1AFnWVkhyVbWQQS562FHEjb8nUTDKrE · 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
18z1AFnWVkhyVbWQQS562FHEjb8nUTDKrE
Current holder address
18z1AFnWVkhyVbWQQS562FHEjb8nUTDKrE
File hash address
1LRB3AkfkYmbTryJBxaS5KXXAwTCNTbUBb
Metadata hash address
125AqFYoPKKwW4wkEy2jG2NZ32CB3YuCYj
Edition number
issued 2 times The original service registered edition 83 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: 1FrQDXQq…hkBied33.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-07-22 21:12REGISTER1AScRhqd…FsqmLquG18z1AFnW…8nUTDKrE134c81c1…b853d2ac
2016-07-23 13:48CONSIGN18z1AFnW…8nUTDKrE1GsWnor7…zHDd5oMJ795e9a5c…712c6635
2016-08-24 07:37UNCONSIGN1GsWnor7…zHDd5oMJ18z1AFnW…8nUTDKrEcfdcc3e4…ad532cc0

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