AscribeRevived

Edition · 2/2

edition id 1Nw8ZAuhVtJivjL1NawkV9FCVFLR9VqXGn · main era (2015-2018) consigned

Add information as the owner

Piece
1P4dYbysNum2sQa4tcjEBPABLmBpmWiHES assignment uncertain: this file was registered several times
Registered on-chain
2016-02-10 14:58:44 UTC
Current owner address
1Nw8ZAuhVtJivjL1NawkV9FCVFLR9VqXGn
Current holder address
1D6NavLXfTQrLXmjZSKt3dptcJUws9zyoY (consigned)
File hash address
1EyVSvqD3ApNEKx9fndhWucTZubUzvJYit
Metadata hash address
12itXY7auoVwegbHDx1ZwFKEhPrZ4ui3B1
Edition number
issued 3 times The original service registered edition 2 of this file to 3 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: 1KEuExy1…NfcDryD3, 1Q9qcr3R…D53Np2E6.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-02-10 14:58REGISTER1AScRhqd…FsqmLquG1Nw8ZAuh…LR9VqXGn00a75911…87b706ce
2016-03-24 14:52CONSIGN1Nw8ZAuh…LR9VqXGn1D6NavLX…Uws9zyoYf5073865…87563e4a

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