AscribeRevived

Edition · 1/1

edition id 16Aoy8WLYHKYCEAdSptkD5Jk9h2vzoJbKn · main era (2015-2018) consigned

Add information as the owner

Piece
19MN2JdQhYSUizLwmCvTcdAa671wkJBtP2 assignment uncertain: this file was registered several times
Registered on-chain
2016-02-10 14:51:22 UTC
Current owner address
16Aoy8WLYHKYCEAdSptkD5Jk9h2vzoJbKn
Current holder address
1Ku8tN5gdrejdXnd8ZsCg7v4MyF9NEgW2h (consigned)
File hash address
1G41wPJ7BDrRQqB4uaejBU8KdfhNxBYXML
Metadata hash address
14MB9V9vHzVm9fcuQoocths2oi7xUpk3SN
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: 1MtyKiup…jLT9SG1Y.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-02-10 14:51REGISTER1AScRhqd…FsqmLquG16Aoy8WL…2vzoJbKn2411e460…e01f2997
2016-02-11 14:30CONSIGN16Aoy8WL…2vzoJbKn1Ku8tN5g…F9NEgW2hbf9a14f0…28bcfaaa

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/16Aoy8WLYHKYCEAdSptkD5Jk9h2vzoJbKn/