Edition numbers issued more than once
A work on Ascribe was issued in numbered editions, and each number was meant to be registered once. The original service sometimes registered the same number of the same file to more than one address. This page explains how this site shows those editions, and why.
Why one number can appear many times
The blockchain records an edition against the artwork's file, not against the work. The same file was often registered as several separate works (one file was used for 368 of them), and each of those works has its own edition 1, its own edition 2, and so on. So a badge such as "issued 191 times" usually means that many separate editions carry that number for that file. Sometimes the service also registered the same number of the same work twice.
How they are shown
Every registration address is its own edition. Each keeps its own history and its own holder. The only difference is a badge saying how many addresses received its number, with links to the others.
Why
The SPOOL specification defines an edition by its Bitcoin address. Its summary figure, as re-published by its author, reads "bitcoin address of owner = Edition ID", and the 2015 whitepaper says the same in words. An edition changes hands only when the address holding it signs it over (a transfer, consignment or unconsignment), or when the original service moved it to a new address for the same owner (a migration). A registration is none of these. It is the original service (ascribe's own wallet, called the "federation") creating an edition at an address, and it says nothing about any edition that already exists. So it cannot take an edition away from anyone, and the address it names is an edition of its own.
The protocol's software library gives two other answers, and neither fits what happened:
- Its registration check says a number must not be registered again for the same file. That tells us these registrations should not exist, but not what to do now that they do. The original service never ran this check: it switched it off on every registration it sent.
- Its ownership calculation gives a number to whichever transaction came last (loans aside) among everything recorded under the file. It pools every work that shares the file, so it would treat editions of different works as one, and it has no order for two transactions made in the same block.
Where these editions were used, the chain shows them used separately. Here is one case: in block 396762 the service registered edition 1 of one file to four different addresses. In the next block each of the four addresses used the small amount of bitcoin it had received at registration (the coin that stands for the edition) to transfer its edition to a different recipient.
Treating such editions as one would erase all but one of those transfers.
A correction
On 23 September 2026 (UTC), for a few hours, this site merged some of these editions into one, loosely following the library's ownership calculation. That reading showed moves no holder had signed and hid real transfers, so it was withdrawn the same day. Only this site's reading changed: nothing on the blockchain changed, no account or link was lost, and every edition affected is shown again as its own edition.
Sources: the SPOOL specification and the pyspool library (ownership.py: can_register, can_transfer; spoolex.py: BlockchainSpider).