AscribeRevived

Edition · 1/1

edition id 15XMVkdDnjgAYjCwHXVPv3yP2FKSBvV2hF · main era (2015-2018) transferred

Add information as the owner

Piece
16cmm5TRwgQVddgSySGnGySgxnaPd4mRd5 assignment uncertain: this file was registered several times
Registered on-chain
2017-10-18 11:29:50 UTC
Current owner address
15BpPQyQT5s2xuMpskART3385Wo1CgdVr4
Current holder address
15BpPQyQT5s2xuMpskART3385Wo1CgdVr4
File hash address
1CaHwE973qEwH8TMuPTigfhP3vD2w2QkFR
Metadata hash address
17J7QgrM2irCU3HvGNCZ7JodycrNACBSeA
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: 16E5ZwVt…GdwWvjzk.
Notes
registered again by 9abeaee7224a
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2017-10-18 11:29REGISTER1AScRhqd…FsqmLquG15XMVkdD…KSBvV2hF5e34c157…21c1d6ae
2017-10-18 11:29REGISTER1AScRhqd…FsqmLquG15XMVkdD…KSBvV2hF9abeaee7…629df790repeat registration; the protocol allows one per edition
2017-10-19 18:09TRANSFER15XMVkdD…KSBvV2hF15BpPQyQ…o1CgdVr4068944d3…9f2e6b15

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/15XMVkdDnjgAYjCwHXVPv3yP2FKSBvV2hF/