AscribeRevived

Edition · 4/10

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

Add information as the owner

Piece
1nkoPsH8YKGQFLDkVEyCtV5snaKWye2Xq assignment uncertain: this file was registered several times
Registered on-chain
2016-02-10 12:49:52 UTC
Current owner address
1FGm85LVG1yBcSm1eE2nAhNTCRz3ytL8Hi
Current holder address
14d3EM5EMvbgbMcZht4T9iwam5EY5xgmNj (consigned)
File hash address
1PJYim9MyL2wFbQ3vhYWmgd5QhL12QBiq7
Metadata hash address
1HoatJcQRedC5HMLzjdFJ9UmGwBEFhkyxH
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, 1HuFxaLU…rCi3C7BS, 1BDaJjVe…RbqVpFxD, 15vrZuGy…BsFfZtzk.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-02-10 12:49REGISTER1AScRhqd…FsqmLquG1FGm85LV…z3ytL8Hi6e6a13d3…702d306c
2016-02-10 14:51CONSIGN1FGm85LV…z3ytL8Hi14d3EM5E…EY5xgmNj7646c846…1ee7d059

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