AscribeRevived

Edition · 8/20

edition id 19bFcVoe1JL3KPMaMVViVfF4Jbdxrf3HJ3 · main era (2015-2018) consigned

Add information as the owner

Piece
1FrLS3rYANsLKFkACHeAxCxgbLiKpvrPoq
Registered on-chain
2016-02-10 11:12:37 UTC
Current owner address
19bFcVoe1JL3KPMaMVViVfF4Jbdxrf3HJ3
Current holder address
1BzUFzqcsd4JmcC82Rco9xfGjLr7ZoojQU (consigned)
File hash address
1PJYim9MyL2wFbQ3vhYWmgd5QhL12QBiq7
Metadata hash address
1H5xWdHRmoznmCCST1KcKDjLiJchPkrDwB
Edition number
issued 5 times The original service registered edition 8 of this file to 5 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: 1GcXsJnH…6fRREAyc, 19uSxmgM…5gezp9Bw, 1MHGtaMR…64f3LKvw, 1PULMC45…qoZ8LJtW.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-02-10 11:12REGISTER1AScRhqd…FsqmLquG19bFcVoe…dxrf3HJ3b378c25f…3733528a
2016-02-10 11:57CONSIGN19bFcVoe…dxrf3HJ31BzUFzqc…r7ZoojQU66b3d69a…a2a046b7

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