Every number here comes from the platform's configuration, so it is what is actually enforced right now.
Submitting a collection
| Limit | Value |
|---|---|
| Items per collection | 1,000 |
| Size per item | 20 MB |
| Collections you can have in the review queue at once | 5 |
That last one counts collections you have submitted and that are not resolved yet. A rejected one keeps its place until you delete it.
Accepted files
| Where | What is accepted |
|---|---|
| Collection items | images, video, audio, 3D models (.glb, .gltf), PDF and HTML |
| Collection cover | images only |
The cover is images-only on purpose: it has to render as a thumbnail everywhere — in a list, in a card, in a shared link — and a 3D model or an HTML page cannot do that reliably.
Whatever the format, it ends up in the same frame:
HTML items run sandboxed. A piece can be a full HTML document, which is what makes pieces that change over time possible, but it is served isolated: it cannot reach your wallet, your session or the rest of the page.
It is still somebody else's code, and it can draw whatever it likes inside its own frame. So: if a piece asks you for a password, a key or a signature, that is not Zoide asking — close it and report it. HTML items also go through a security review before publication, which is deliberately strict.
The exact list of accepted types is enforced at upload time, so if a format is rejected the uploader will tell you rather than failing later.
Your wallet
| Limit | Value |
|---|---|
| Pieces a single wallet can manage | 100,000 |
This is a hard cap: a purchase or a transfer that would push a wallet over it is refused. It is not a business rule, it is a practical one — beyond that number the wallet page stops being usable.
Following addresses (Balances)
| Limit | Value |
|---|---|
| Addresses you can follow for free | 5 |
| Extra addresses each payment unlocks | 5 |
| Cost of each unlock | 1,000,000 sats |
Bulk payments
| Limit | Value |
|---|---|
| Minimum per address | 1,000 sats |
| Fee | 5% of the amount sent |
The minimum per address exists because of how Bitcoin works, not because of us: an output too small to be worth its own network fee is a dust output, and the network will not relay it.
Drops
| Limit | Value |
|---|---|
| Days a drop stays open after it goes live | 1 |
| Same, for subscribers | 5 |
That window is not a reservation. When it expires, whatever has not been minted is turned into an airdrop and the drop leaves the active list.
Chat
| Limit | Value |
|---|---|
| Days a message is kept | 30 |
The global chat is not an archive. Older messages are deleted, so anything worth keeping does not belong only in the chat.