AscribeRevived

Edition · 4/10

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

Add information as the owner

Piece
1MC4PcVUGTf2Kh6uaQByr67NJZVDP44898 assignment uncertain: this file was registered several times
Registered on-chain
2016-02-10 13:15:29 UTC
Current owner address
1HuFxaLU5ZNPZf1aNWqbxga36ZrCi3C7BS
Current holder address
17sqaoBdG1HXGDpihmn1vfs4fLAcDzXnTc (consigned)
File hash address
1PJYim9MyL2wFbQ3vhYWmgd5QhL12QBiq7
Metadata hash address
138GCknFSGSWwTmx9pJQtmwX6estDfVaVM
Edition number
issued 5 times The original service registered edition 4 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: 14j3aoj9…uoyfJ6dw, 1FGm85LV…z3ytL8Hi, 1BDaJjVe…RbqVpFxD, 15vrZuGy…BsFfZtzk.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-02-10 13:15REGISTER1AScRhqd…FsqmLquG1HuFxaLU…rCi3C7BSaf08a921…bcfbdebf
2016-02-10 14:51CONSIGN1HuFxaLU…rCi3C7BS17sqaoBd…AcDzXnTc42f356a6…eb31b757

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