AscribeRevived

Edition · 1/5

edition id 19Yo8MgUPF5vAC9jh4KQmdkogg9j2a3Trx · main era (2015-2018) transferred

Add information as the owner

Piece
12Kysrosih6JHUiYJvRGhv68fpB7PEmYZN assignment uncertain: this file was registered several times
Registered on-chain
2016-02-12 02:11:17 UTC
Current owner address
1LYk9PpkV4xr6zH6MBfU83REujZ9brRX2N
Current holder address
1LYk9PpkV4xr6zH6MBfU83REujZ9brRX2N
File hash address
1FiZ47fy8DiYYWDQY4KNnQmjeZfgv5ZS5b
Metadata hash address
1nLZhgQHmKroPjDfnP9XuACgHSvWk9SS6
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: 1MYe11Tv…sT8WQGJ7.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-02-12 02:11REGISTER1AScRhqd…FsqmLquG19Yo8MgU…9j2a3Trxd46297bd…4d9c41d0
2016-02-12 02:28TRANSFER19Yo8MgU…9j2a3Trx1LYk9Ppk…Z9brRX2N8db0af06…5fd69e28

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/19Yo8MgUPF5vAC9jh4KQmdkogg9j2a3Trx/