AscribeRevived

Edition · 1/28

edition id 1Hgv1Hy7331eGd2hDu2AqZcgMp429CqUnt · 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
1JgNgRHbuCd52hTqrknssBMgsLS5QUbQjT
Current holder address
1JgNgRHbuCd52hTqrknssBMgsLS5QUbQjT
File hash address
1LuTaizocjqyYCJaJ9yJJE2ou3uTc7bx4n
Metadata hash address
1GQqneGWD8RA69PcSzeQqp8UFRSfBFW7we
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: 14BQEXUg…j3RN34yX.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2015-12-01 13:12REGISTER1AScRhqd…FsqmLquG1Hgv1Hy7…429CqUntd9db4b87…5a01fe22
2015-12-01 13:12MIGRATE1Hgv1Hy7…429CqUnt1BAvyVGj…qbDwxWDxd5a04dc5…4b0cfb7d
2015-12-01 23:50TRANSFER1BAvyVGj…qbDwxWDx1JgNgRHb…S5QUbQjT5430be13…c839b54d

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