AscribeRevived

Edition · 2/10

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

Add information as the owner

Piece
1GggJLb2pre1PnsvneirYrsX9uM7YD8BdY assignment uncertain: this file was registered several times
Registered on-chain
2015-12-01 09:58:59 UTC
Current owner address
1E9Am3gHHSyuSTRuSgC6mD7husm72ab1B
Current holder address
1E9Am3gHHSyuSTRuSgC6mD7husm72ab1B
File hash address
1LuTaizocjqyYCJaJ9yJJE2ou3uTc7bx4n
Metadata hash address
16RwXJVwvPeTs3v4EgTzTHTtKKzsqZLpkh
Edition number
issued 2 times The original service registered edition 2 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: 1ArqpLmx…1PkKgPTy.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2015-12-01 09:58REGISTER1AScRhqd…FsqmLquG1A9nNvfB…HysYUUBZf4b20b93…8049c1d0
2015-12-01 09:58MIGRATE1A9nNvfB…HysYUUBZ1LJCeDq5…e3pTUeYF493d17d0…45e08710
2015-12-01 12:26TRANSFER1LJCeDq5…e3pTUeYF1E9Am3gH…sm72ab1Bcf84fd68…0ce88a0a

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