AscribeRevived

Edition · 1/1

edition id 13XNDcKpwLPcfv6VR1zsaVYapsggrXMhRC · main era (2015-2018) consigned

Add information as the owner

Piece
15rQe2fCdz5oRsj2E283mVYSVnb4p5zGBJ assignment uncertain: this file was registered several times
Registered on-chain
2017-03-09 12:43:33 UTC
Current owner address
13XNDcKpwLPcfv6VR1zsaVYapsggrXMhRC
Current holder address
19iSBbMeMatdeBHZVHK5Xw2as8A8ftWGsP (consigned)
File hash address
1GBuubamYMq3PfkxQatxGifRX2YRegtAbk
Metadata hash address
1BZzPArqtNxxdKMaxJFxoENDxEPucrA4Yb
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: 1K1w5B1b…Yxba2hKC.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2017-03-09 12:43REGISTER1AScRhqd…FsqmLquG13XNDcKp…ggrXMhRC18fef8f9…edaa79ba
2017-04-05 07:19CONSIGN13XNDcKp…ggrXMhRC19iSBbMe…A8ftWGsP70900a78…d7bd5add

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/13XNDcKpwLPcfv6VR1zsaVYapsggrXMhRC/