AscribeRevived

Edition

edition id 1CAiGhr6dSmrABAJud47PaUtZ8qvn88Tc4 · main era (2015-2018) transferred

Add information as the owner

Piece
1Uie8ENSA3vxWhKwF371h43UvpxE5KAbK assignment uncertain: this file was registered several times June-July 2015 format
Registered on-chain
2015-07-01 09:53:47 UTC
Current owner address
1Mm6TXr8os2orjygmpbU9XTLKCBj1ZTwXj
Current holder address
1Mm6TXr8os2orjygmpbU9XTLKCBj1ZTwXj
File hash address
1NHXUfW1MfKsU83yGY52xrTDVux8UwMXio
Metadata hash address
1HCnLDnbHvgddPKGkkYXaQtLZzbc23P3cE
Edition number
issued 5 times The original service registered edition 0 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: 15VAua2D…fXMFgZPe, 1Q1upi3m…Yr9oyg1A, 126GQBrM…wo83gE2s, 16v566vr…pPMwKypR.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2015-07-01 09:53REGISTER12udvE3z…DUCpbgoq1CAiGhr6…qvn88Tc4ea382a62…3be4f536
2015-07-01 11:55TRANSFER1CAiGhr6…qvn88Tc41Mm6TXr8…Bj1ZTwXj76695f34…8c762b30

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