AscribeRevived

Edition · 1/1

edition id 17j5Xye9VUH5v9QkQGkMtrctJzmMuUvJv6 · main era (2015-2018) transferred

Add information as the owner

Piece
1AiDUJwkQi9JsfqoUHCbt9SN6gQtgT4CqL assignment uncertain: this file was registered several times
Registered on-chain
2016-11-18 16:30:58 UTC
Current owner address
12PCyoaQhNQGbQWqjMgMSQ8vpy3TsqUEci
Current holder address
12PCyoaQhNQGbQWqjMgMSQ8vpy3TsqUEci
File hash address
1JKbPyixLQJXa6pgDUgTELVmsvFGmn4TYL
Metadata hash address
12e5UjV1bTRhAPn8a6jt86DxjfFVN3ThYu
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: 1AAd2UNN…Kn5iqe76.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-11-18 16:30REGISTER1AScRhqd…FsqmLquG17j5Xye9…mMuUvJv6e1840730…6dd805a7
2016-11-18 22:54TRANSFER17j5Xye9…mMuUvJv612PCyoaQ…3TsqUEcia583d4fc…b466b72a

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/17j5Xye9VUH5v9QkQGkMtrctJzmMuUvJv6/