AscribeRevived

Edition · 1/10

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

Add information as the owner

Piece
1231uWQYvpzqyh5c5bCYW5mW5iV5WK5Jqk assignment uncertain: this file was registered several times
Registered on-chain
2016-02-09 09:26:01 UTC
Current owner address
14xr2WAjDyGkEUbFU4FZ9dW29UuEVUmS5g
Current holder address
14xr2WAjDyGkEUbFU4FZ9dW29UuEVUmS5g
File hash address
1GAmmvJ8fdbQrFTvZ76Hjk1UyKT9kP4USK
Metadata hash address
1BfswMUxxv1A7YH4HBAmfFd2WjaPDjqCgJ
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: 1AxzAGoE…igwDHBx3.
Bitcoin explorer
edition address · holder address

Provenance

Time (UTC)ActionFromToTransaction
2016-02-09 09:26REGISTER1AScRhqd…FsqmLquG1JqUjADV…u8ktow86aba5a402…d9d9242b
2016-02-09 09:38TRANSFER1JqUjADV…u8ktow8614xr2WAj…uEVUmS5gc7003fcc…1908ba82

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