Declare your edition size before you register the first piece. Fidaty's database itself refuses to register #N+1. Over-printing scandal solved at the infrastructure level — no off-chain spreadsheet can beat a DB constraint.
9999
Max edition size
From single-piece to mass series
1:1
Number uniqueness
Partial UNIQUE index
0
Over-prints possible
DB raises 23514 on #N+1
~30s
Setup time
Title + medium + size
In photography, printmaking and sculpture editions, over-printing scandals (Ansel Adams estate, contemporary print shops) have slashed artist valuations by 40-70% overnight. Fidaty makes the cap enforceable at the database level — no human process, no reconciled Excel, no room for error.
Create an edition with title + optional medium + size. Every certificate you subsequently link to that edition must have a unique number between 1 and size. Try to register #N+1: DB raises check_violation, transaction rolls back, no data pollution.
Create edition row with size 1..9999. Publicly readable.
Each cert.edition_id + edition_number populated at creation.
Trigger before insert + partial unique index. #N+1 always fails.
Flip sealed=true to block new additions even with slots free.
Archival prints in edition of 50 + 5 APs. Fidaty locks the run; no "rediscovered #52".
Bronze casts numbered 1/8. Track foundry provenance per cast in chain of custody.
Limited-edition furniture run. Scarcity enforced, resale royalty kicks in automatically.
Buyer scans /verify and sees "3/50" on the certificate. No forgery possible.
Every service in the Fidaty platform is integrated with the rest: identity, compliance, analytics and consumer engagement flow seamlessly. No data silos, no duplicate work.
Book a demoDeclare your series in 30 seconds. The DB handles the rest.
Attempted: register #51 of "Sunset…" → ERROR 23514: edition_number 51 exceeds edition size 50