AscribeRevived

Edition · 5/28

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

Add information as the owner

Piece
1JELnAHR4DQqmEkr7hDYjQh9BSvQ23bK9m assignment uncertain: this file was registered several times
Registered on-chain
2015-12-01 13:12:28 UTC
Current owner address
1DvvCqYSUhyQGfFQF7mG6kkiJ38swNmA7x
Current holder address
1DvvCqYSUhyQGfFQF7mG6kkiJ38swNmA7x
File hash address
1LuTaizocjqyYCJaJ9yJJE2ou3uTc7bx4n
Metadata hash address
1LfcxkPt551GnUfCX1HkKAKdKKFWD8967u
Edition number
issued 2 times The original service registered edition 5 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: 1J5AG2Yi…3fvhsqAa.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2015-12-01 13:12REGISTER1AScRhqd…FsqmLquG1GjUgHEN…Va38Zo7ve736bf46…fbb2025c
2015-12-01 13:12MIGRATE1GjUgHEN…Va38Zo7v1ErM9qYn…gfEuKetabedc18d7…3c08cb4e
2015-12-01 23:50TRANSFER1ErM9qYn…gfEuKeta1DvvCqYS…8swNmA7x1bc32b8e…2d8be9d7

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