AscribeRevived

Edition · 1/4

edition id 1MYe11Tv5zDFTDkSJk5LhruY53sT8WQGJ7 · main era (2015-2018) transferred

Add information as the owner

Piece
1JFga3cT87LE834kRigPXXPS3XdqmrFxXb assignment uncertain: this file was registered several times
Registered on-chain
2016-02-15 05:35:39 UTC
Current owner address
1EhN5XfYcVhe9NTKBJ77w43ake29UrZzAA
Current holder address
1EhN5XfYcVhe9NTKBJ77w43ake29UrZzAA
File hash address
1FiZ47fy8DiYYWDQY4KNnQmjeZfgv5ZS5b
Metadata hash address
1PUueBnaqiX1Jxr6MdJacngLkahyXtCCqN
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: 19Yo8MgU…9j2a3Trx.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-02-15 05:35REGISTER1AScRhqd…FsqmLquG1MYe11Tv…sT8WQGJ74b1168c3…e5c392da
2016-02-15 05:59TRANSFER1MYe11Tv…sT8WQGJ71HqJrCBC…q4dGc1Co6745e0d5…cc62f922
2016-02-15 05:59TRANSFER1HqJrCBC…q4dGc1Co1EhN5XfY…29UrZzAA18a90531…57d75f80

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