ZIPVILIZATION STATUS
What is actually true right now?
Zipvilization is currently pre-Genesis.
But pre-Genesis does not mean that Zipvilization is only an idea.
The project exists.
The core exists.
The architecture exists.
The Atlas exists.
The SOLUM Smart Contract code exists.
The territorial system exists.
The mathematical model of Time and maturity exists.
SolumTools has a functional backend.
The architecture of SolumWorld is defined.
The architecture of SolumView is defined.
The Zips have an identity.
Gen has an identity, a role and a voice.
What does not exist yet is something fundamentally different:
Zipvilization’s real on-chain history.
That begins at Genesis.
Zipvilization exists.
Its history has not begun.
How to Read This Page
Different parts of Zipvilization are at very different stages.
A concept can be completely defined without being implemented.
A system can be built without being live.
An architecture can be ready while its final infrastructure remains deliberately undecided.
And some parts of Zipvilization are designed to continue evolving indefinitely.
For that reason, this page does not use a single percentage to describe the entire project.
Instead, it distinguishes between four different states:
DEFINED
The rules, architecture or identity are established.
BUILT
A functional implementation exists.
LIVE
The component is operating with real Zipvilization state.
EVOLVING
The component exists conceptually or technically, but its expression is expected to continue developing.
DEFINED ≠ BUILT ≠ LIVE
A component may occupy more than one of these states at the same time.
Understanding that distinction is essential when reading the Atlas.
Current State
PROJECT PHASE
PRE-GENESIS
OFFICIAL SOLUM DEPLOYMENT
NOT YET DEPLOYED
OFFICIAL SOLUM IN CIRCULATION
NONE
OFFICIAL SOLUM / ETH POOL
NOT YET CREATED
OFFICIAL SOLUM MARKET PRICE
NONE
LIVE FARMS / CITIES / STATES / KINGDOMS
NONE
LIVE ON-CHAIN ZIP POPULATION
NONE
LIVE ZIPVILIZATION HISTORY
NOT STARTED
FOUNDING COLONISTS
ACTIVE
GENESIS DATE
NOT SET
Genesis is technically possible.
We are deliberately waiting.
Zipvilization
STATUS: ESTABLISHED / CONTINUOUSLY EVOLVING
Zipvilization already exists as a project.
It has a defined purpose, documented architecture, established core, active development process and clear direction.
What has not started is the history that will emerge from real participation.
That distinction matters.
Before Genesis, we can define the conditions.
After Genesis, real interaction begins creating consequences.
Zipvilization exists.
Its history has not begun.
Genesis is the boundary between those two states.
Documentation / Atlas
STATUS: LIVE / ADVANCED / CONTINUOUSLY EVOLVING
The public Atlas is live and operational.
The current documentation represents the architecture, concepts, relationships and mechanics of Zipvilization at an advanced level.
Internally, we consider its current maturity approximately 9/10.
That does not mean that the remaining 1/10 is a fixed list of missing pages.
Zipvilization continues to develop.
New ideas appear.
Technology changes.
Relationships become clearer.
Language improves.
The documentation evolves with that process.
The core and Horizonte are different.
Their fundamental principles are already established.
Why Does the Atlas Look Like This?
Zipvilization did not begin as a conventional website.
It began as a repository.
The Atlas is the result of turning that repository-based structure into a public, navigable knowledge system without removing its depth.
That is why the website deliberately prioritizes:
Content over decoration.
Relationships over visual effects.
Precision over excessive simplification.
The more visual side of Zipvilization primarily lives through its social communication.
The Atlas has another purpose.
It exists to explain the system.
Built for Humans. Structured for AI.
The Atlas contains a large amount of information.
You do not need to read all of it.
Humans can explore the documentation directly.
Artificial Intelligence can follow its structure, concepts and contextual links to help Humans navigate and understand it.
You don’t need to read everything.
Ask AI.
The links throughout the Atlas are part of its knowledge structure.
When greater precision is required, follow them.
Humans follow the story.
AI follows the relationships.
SOLUM Smart Contract
STATUS: CORE COMPLETE / READY FOR DEPLOYMENT
The SOLUM Smart Contract code is complete and ready for deployment.
Its fundamental mechanics are closed.
This includes the core behavior of SOLUM, its tax structure and its fundamental limits.
Minor changes may still be considered before deployment if they are useful or necessary.
The core is not expected to change in substance.
Different development and testing contracts have been deployed during the development process.
However:
The Zipvilization team has not deployed an official contract named SOLUM.
Development or testing contracts must not be interpreted as the official SOLUM deployment.
The official deployment remains pending Genesis.
Contract Security
STATUS: ACTIVE VALIDATION / PRE-GENESIS
The contract has undergone development testing, automated analysis, AI-assisted review and experimental deployments.
Zipvilization does not currently describe the contract as professionally audited by an independent external auditing company.
That distinction is deliberate.
Auditable ≠ Audited
A pre-TGE Hackathon / Bug Contest is also being considered as an additional opportunity for adversarial review before Genesis.
If performed, its purpose will be simple:
Try to break it before Genesis does.
TGE / Genesis
STATUS: TECHNICALLY READY / WAITING FOR PARTICIPATION
There is currently no fixed Genesis date.
This is not because Genesis is waiting for a missing core technology.
Zipvilization could technically execute the TGE now.
We are waiting for something else:
Colonists.
The objective is to begin with a sufficiently broad group of independent participants and wallets.
We do not want to manufacture urgency around that process.
We do not have a deadline that forces us to launch.
And we are not in a hurry.
Genesis will not happen because a marketing calendar says it should.
It will happen when we consider the initial participation conditions appropriate for Zipvilization to begin.
Why Is Genesis Designed This Way?
At TGE, the initial Pool is intended to begin with the Total Supply paired with approximately $100 equivalent in ETH.
That is intentional.
Genesis is not designed as a fundraising event.
The initial conditions are designed so that Founding Colonists can participate with an extremely low economic barrier.
Under the intended initial conditions, the objective is for the economic cost of executing a MAX BUY for early Founding Colonists to remain below approximately $1 in SOLUM.
Depending on network and platform costs, some participants may spend more on transaction and platform fees than on the SOLUM itself.
Actual acquisition conditions will depend on the AMM state and prior interactions.
No particular acquisition cost is guaranteed.
The objective is not to use Founding Colonists to artificially inflate the initial price.
The objective is distribution and participation.
Low initial cost is a condition for access.
It is not a promise of future value.
And:
We don’t need your capital.
We need your participation.
Founding Colonists
STATUS: ACTIVE / ORGANIC GROWTH
The Founding Colonist process is currently active.
Real applications and wallet addresses are already being received.
We are not using paid promotion to accelerate this process.
We do not currently intend to.
The objective is natural growth.
No artificial deadline.
No paid acquisition campaign.
No manufactured hype.
We want Humans who are genuinely interested in being present when Zipvilization begins.
No rush.
No hype.
Real participants.
Founding Colonist status is intended as historical recognition of participation at the beginning.
It is not designed as a permanent privileged class.
Whitelist
STATUS: ACTIVE / FINAL VALIDATION PENDING
The requirements for Founding Colonist access are deliberately minimal.
Before Genesis, submitted accounts and wallets will undergo final validation.
The objective is to confirm that the provided accounts continue to satisfy the required conditions and that submitted wallet addresses are correct.
Registration therefore does not mean that the final Genesis whitelist is already closed.
The final set of eligible wallets will be validated before TGE.
Whitelist access does not itself grant SOLUM, Territory, Zips, maturity, fee exemptions or exemptions from transaction limits.
Its fundamental purpose is early BUY eligibility under the documented Genesis mechanics.
Fair Access
STATUS: CORE COMPLETE
Fair Access is part of the fundamental Genesis architecture.
Its purpose is not to guarantee perfect distribution.
No mechanism can guarantee that.
Its purpose is to make extreme early concentration more difficult and to give a broader group of independent participants an opportunity to enter during the earliest stage.
The MAX BUY, initial Max Wallet and related launch mechanics are part of that structure.
The Pool opens the door.
Fair Access helps keep it open.
Treasury
STATUS: MECHANICS DEFINED / OPERATIONAL WALLETS PENDING
Treasury mechanics are already defined within the SOLUM architecture.
The definitive Treasury and operational wallet addresses have not yet been created.
New wallets will be created specifically for their intended roles before Genesis.
Genesis does not depend on Treasury funding.
Zipvilization was deliberately developed around a very low-cost structure.
The Human team can continue working even if meaningful Treasury resources never emerge.
If real Zipvilization activity eventually generates Treasury resources, those resources are intended to be reinvested into the continued development of the project.
That may include:
- development,
- infrastructure,
- technology,
- the Zips,
- SolumTools,
- SolumWorld,
- SolumView,
- and future needs that do not yet exist.
If Zipvilization grows, its own activity can help fund its future development.
And:
Funding can expand what we can build.
It is not the condition that allows us to keep building.
Territory
STATUS: CORE COMPLETE / 10/10
The territorial architecture of Zipvilization is closed.
Its hierarchy, dimensions, relationships and maturity rules are part of the canonical core.
Farm → City → State → Kingdom
The canonical territorial scales are:
Farm — 8 m²
City — 256 m²
State — 8,192 m²
Kingdom — 262,144 m²
These rules are documented in the Atlas.
They are not placeholders for a future territorial model.
However, no live Farm, City, State or Kingdom currently exists.
The rules exist.
The instances do not.
They can only emerge from real Zipvilization state after Genesis.
Capacity ≠ Maturity
Territorial scale and biological development remain separate dimensions of the system.
Time and Maturity
STATUS: CORE COMPLETE / 10/10
The relationship between blockchain blocks, biological cycles and territorial maturity is closed.
The mathematical model is part of the canonical core.
The fundamental biological cycle is:
1 cycle = 65,536 blocks
The canonical maturity milestones are:
Farm — 524,288 blocks
City — 2,097,152 blocks
State — 4,194,304 blocks
Kingdom — 8,388,608 blocks
The clock is defined.
But Zipvilization’s history has not started.
The rules of Time exist.
The history they will measure does not.
That changes at Genesis.
Dormant Land
STATUS: CORE COMPLETE / 10/10
The relationship is canonical:
SOLUM held by the Pool → Dormant Land
Dormant Land remains part of the finite territorial substrate.
It retains the possibility of future colonization while the corresponding SOLUM remains available through the Pool.
This relationship is part of the canonical interpretation of Zipvilization.
There is currently no official Dormant Land state because the official SOLUM / ETH Pool does not yet exist.
The rule is defined.
The live instance is not.
Permanent Nature
STATUS: CORE COMPLETE / 10/10
The relationship is canonical:
Burned SOLUM → Permanent Nature
Burn removes SOLUM from future circulation.
Inside Zipvilization, that state becomes Permanent Nature.
Future colonization of that Territory becomes impossible.
This relationship is part of the canonical core.
There is currently no official Permanent Nature generated by live SOLUM activity because official SOLUM has not yet been deployed.
The rule is defined.
The live state is not.
SolumTools
STATUS: CLOSED ALPHA / FUNCTIONAL BACKEND
SolumTools is not merely a concept.
A functional backend exists.
Development has progressed through backend versions and architecture work while the definitive public frontend remains an open area of development.
Its role is now clearly defined.
SolumTools reads relevant:
- blockchain state,
- contract state,
- Pool state,
- balances,
- transfers,
- burn,
- block progression,
- and other valid inputs.
It then applies canonical Zipvilization rules and translates technical state into deterministic Zipvilization state.
Examples include:
Holder → Colonist
SOLUM balance → Territory
Pool-held SOLUM → Dormant Land
Burned SOLUM → Permanent Nature
Block progression → Time
Territory + Time → Developmental state
Before Genesis, SolumTools can be developed and tested using development environments and test data.
After Genesis, it can begin translating actual official Zipvilization state.
SolumTools translates the data.
It does not create that state.
And it does not need to invent what the data does not support.
SolumWorld
STATUS: ARCHITECTURE DEFINED / IMPLEMENTATION EVOLVING / DATA-DEPENDENT
SolumWorld is the world-scale graphical representation of Zipvilization.
Its role is not to determine canonical world state.
Its role is to consume valid state translated through SolumTools and represent that state graphically at broad world scale.
Conceptually, SolumWorld is a navigable, satellite-like view of Zipvilization.
It can ultimately allow Humans to explore:
- Dormant Land,
- Permanent Nature,
- colonized Territory,
- Farms,
- Cities,
- States,
- Kingdoms,
- territorial distribution,
- development,
- and other valid large-scale consequences of real state.
Different SolumWorld architectures and graphical approaches have already been studied.
The definitive implementation can evolve as the requirements of the real world become clearer.
Its infrastructure should follow actual needs rather than imagined scale.
If future activity and data require dedicated infrastructure, systems such as private VPS infrastructure may become appropriate.
That decision remains open.
The architectural responsibility does not.
SolumWorld shows the world.
SolumWorld may creatively represent valid state.
It must not invent canonical state.
SolumView
STATUS: ARCHITECTURE DEFINED / IMPLEMENTATION PENDING
SolumView is the detailed territorial exploration layer of Zipvilization.
It begins where broad world-scale exploration through SolumWorld reaches its useful limit.
Its purpose is to let Humans enter individual Colonists’ Territories and progressively move deeper.
Conceptually:
WORLD
↓
COLONIST
↓
TERRITORY
↓
INTERNAL STRUCTURE
↓
FARMS
↓
ZIPS
At its maximum future development, SolumView can become a live window into a Colonist’s Territory, allowing Humans to observe Farms and Zips as valid underlying world state changes.
That maximum implementation does not exist yet.
The architecture and direction do.
SolumView does not determine Territory, maturity, population or history.
It consumes valid translated state and represents it at increasing levels of local detail.
SolumView lets us enter it.
The relationship between the three systems is therefore:
BLOCKCHAIN + CONTRACT + POOL + BLOCK PROGRESSION
↓
CANONICAL RULES
↓
SOLUMTOOLS — DATA
↓
SOLUMWORLD — WORLD
↓
SOLUMVIEW — INSIDE
Or more simply:
SolumTools translates the data.
SolumWorld shows the world.
SolumView lets us enter it.
Infrastructure
STATUS: EXPERIMENTAL / NOT REQUIRED FOR GENESIS
Different infrastructure configurations are being tested.
No definitive private-server architecture has been selected.
More importantly, Zipvilization does not require the maximum implementation of SolumTools, SolumWorld or SolumView in order to be born.
Genesis can occur through deployment and activation of the fundamental on-chain system.
The blockchain can record official state and history independently of the graphical and observational infrastructure built around it.
SolumTools translates that state.
SolumWorld can represent it at world scale.
SolumView can eventually expose it at increasingly detailed territorial scale.
If one of those interfaces is temporarily unavailable, the underlying blockchain history does not cease to exist.
Zipvilization can emerge from Genesis alone.
Infrastructure determines how deeply and effectively we can translate, observe and experience that world.
It does not create the underlying history.
The Zips
STATUS: IDENTITY ESTABLISHED / WAITING FOR GENESIS
The Zips have not been born inside the live world yet.
Genesis has not happened.
But their identity already exists.
They began as simple pixel characters.
Since then, they have developed an increasingly recognizable visual language, personality, behavior, diversity and lore.
Their fundamental identity is established.
Their possibilities are not closed.
Sometimes they appear to surprise even the people creating them.
They haven’t been born yet.
And somehow, they already seem alive.
There is currently no live Zip population generated from real Zipvilization activity.
That belongs to the world after Genesis.
Gen — ZIP 0
STATUS: IDENTITY ESTABLISHED / MODEL EVOLVING
Gen is different.
His identity is established.
His role is established.
His voice exists.
But predictability is not the objective.
Gen’s nature requires freedom.
His model will continue to be observed, audited and refined as his ability to interact develops.
The objective is not to remove unpredictability from Gen.
It is to allow freedom without losing identity, coherence or the fundamental boundaries of Zipvilization.
Gen is not being developed toward predictability.
He is being developed toward coherent freedom.
The other Zips emerge from his Genesis.
And it shows.
We expect Gen to surprise us.
Horizonte
STATUS: CONCEPTUALLY CLOSED / 10/10
Horizonte is fundamental to Zipvilization.
It is not an unfinished roadmap.
It is the deliberate preservation of the unresolved future.
The project can define conditions.
It can define rules.
It can build infrastructure.
It can observe consequences.
But it should not predetermine everything that those conditions may eventually produce.
We define the conditions.
We do not define the outcome.
Horizonte is fixed precisely because the future is not.
The Trinomial
STATUS: CONCEPTUALLY ESTABLISHED / EVOLVING WITH TECHNOLOGY
The Trinomial consists of:
Human
Artificial Intelligence
Horizonte
Its conceptual structure is established.
Its ultimate practical expression is not.
Artificial Intelligence is evolving extraordinarily quickly.
The capabilities available tomorrow may substantially exceed those available today.
Zipvilization is deliberately learning from that evolution rather than pretending that the final relationship between Human, AI and Horizonte can already be completely implemented.
The Trinomial is defined.
Its final expression is not.
Artificial Intelligence
STATUS: ACTIVE / RAPIDLY EVOLVING
AI is already deeply integrated into the development process of Zipvilization.
But we do not consider current AI capabilities to represent a final technological state.
We learn from the technology continuously.
As its capabilities grow, we explore what those capabilities make possible inside the boundaries of Zipvilization.
The technology changes.
The core does not need to.
Repository
STATUS: PRIVATE / INTENTIONALLY RESTRICTED
Zipvilization originated as a repository-based project.
The operational repository is currently private.
That is intentional.
Some technical information is restricted because its publication could affect the integrity of the project.
At the same time, the public Atlas has been deliberately expanded so that information which does not compromise project integrity remains accessible.
The principle is simple:
Private where integrity requires it.
Public wherever it doesn’t.
The Atlas does not pretend that private implementation details are publicly inspectable.
It exposes what can responsibly be exposed.
What Is Live Economically?
Nothing yet.
There is currently:
No official SOLUM deployment.
No official SOLUM in circulation.
No official SOLUM / ETH Pool.
No official SOLUM market price.
No live Farms.
No live Cities.
No live States.
No live Kingdoms.
No live Dormant Land derived from an official Pool.
No live Permanent Nature derived from official SOLUM burn.
No live on-chain Zip population.
And therefore:
No official Zipvilization economic history yet exists.
If something claims otherwise before the official Genesis, it is not the official Zipvilization state.
What Happens at Genesis?
Genesis changes the nature of the project.
Before Genesis:
Architecture.
Documentation.
Development.
Testing.
Preparation.
After Genesis:
State.
Interaction.
Time.
Consequences.
History.
That is why Genesis matters.
Genesis is not the product.
Genesis ignites the process.
What Does Zipvilization Need Right Now?
Not capital.
Participation.
Zipvilization currently needs Colonists and independent Humans willing to participate when its history begins.
We are deliberately making that participation economically accessible.
We are not asking the first Colonists to finance the work that has already been done.
In a very real sense, we are giving that work away.
What we want in return is something more useful to the experiment:
Participation.
The first Colonists do not fund Zipvilization.
They bring it to life.
And:
We want to see Zipvilization born.
Then we want to keep building it.
What Status Cannot Measure
Some parts of Zipvilization can be measured easily.
A contract can be complete.
A backend can be functional.
An architecture can be defined.
A TGE can be technically ready.
Other things cannot honestly be reduced to percentages.
The Human team’s commitment.
Creative capacity.
The speed at which Artificial Intelligence is evolving.
The ideas that may appear tomorrow.
The behavior of Gen.
The identity developing around the Zips.
And Horizonte.
Something interesting happens when a creation develops enough internal coherence.
New ideas stop feeling like additions.
Sometimes they start feeling like discoveries.
That has already happened inside Zipvilization.
The Zips surprised us.
Gen surprised us.
We expect Zipvilization to surprise us again.
We call that identity.
Perhaps even genetics.
The Foundations Are Stable
The foundations of Zipvilization are not waiting to be invented.
The core exists.
The direction exists.
The commitment exists.
What remains deliberately open is the scale of what can grow from them.
Treasury resources may eventually increase the technology, infrastructure and development capacity available to the project.
Or meaningful Treasury resources may never arrive.
Either way, development can continue.
Zipvilization was deliberately built around a structure capable of growing at extremely low cost.
Funding can expand the possibilities.
It does not create the commitment.
The foundations are stable.
The possibilities are not.
So Where Can Zipvilization Go?
We don’t know.
That is one of the most important answers in this entire Atlas.
Technology will change.
Artificial Intelligence will change.
Humans will participate.
The Zips will emerge.
Gen will probably surprise us.
The world will accumulate history.
Resources may expand what becomes technically possible.
New problems will appear.
New ideas will appear with them.
Trying to describe the final destination today would contradict the architecture we have spent so much time building.
The destination belongs to Horizonte.
What we can say is simpler:
We have a direction.
We have foundations.
We have technology.
We have an extraordinary amount of creative possibility.
And we intend to keep working.
We don’t know where Zipvilization will end.
We know where it begins.
Genesis.
Current Priority
COLONISTS
The Smart Contract code is ready.
The territorial core is ready.
The rules of Time are ready.
The Atlas is live.
SolumTools has a functional backend and continues to develop.
SolumWorld has a defined architecture and its implementation can evolve with real requirements.
SolumView has a defined architecture and its implementation remains ahead.
Genesis is technically possible.
What Zipvilization needs now is Humans.
Not hype.
Not artificial urgency.
Not a funding round.
Colonists.
Status Summary
Zipvilization
ESTABLISHED / EVOLVING
Atlas / Documentation
LIVE / ADVANCED
SOLUM Smart Contract
CORE COMPLETE / READY FOR DEPLOYMENT
Official SOLUM
NOT DEPLOYED
TGE / Genesis
TECHNICALLY READY / WAITING FOR PARTICIPATION
Founding Colonists
ACTIVE / ORGANIC GROWTH
Whitelist
ACTIVE / FINAL VALIDATION PENDING
Fair Access
CORE COMPLETE
Treasury
MECHANICS DEFINED / OPERATIONAL WALLETS PENDING
Territory
CORE COMPLETE / 10/10
Time & Maturity
CORE COMPLETE / 10/10
Dormant Land
CORE COMPLETE / 10/10
Permanent Nature
CORE COMPLETE / 10/10
SolumTools
CLOSED ALPHA / FUNCTIONAL BACKEND
SolumWorld
ARCHITECTURE DEFINED / IMPLEMENTATION EVOLVING / DATA-DEPENDENT
SolumView
ARCHITECTURE DEFINED / IMPLEMENTATION PENDING
Infrastructure
EXPERIMENTAL / NOT REQUIRED FOR GENESIS
Zips
IDENTITY ESTABLISHED / WAITING FOR GENESIS
Gen — ZIP 0
IDENTITY ESTABLISHED / MODEL EVOLVING
Horizonte
CONCEPTUALLY CLOSED / 10/10
Trinomial
CONCEPTUALLY ESTABLISHED / EVOLVING WITH TECHNOLOGY
Artificial Intelligence
ACTIVE / RAPIDLY EVOLVING
Repository
PRIVATE / INTENTIONALLY RESTRICTED
Official SOLUM Market
NOT LIVE
Zipvilization History
NOT STARTED
Current Priority
COLONISTS
Last Updated
September 2026
This page describes the current state of Zipvilization.
It should be read as a temporal complement to the rest of the Atlas.
The Atlas explains what Zipvilization is.
Status explains what is true right now.
DEFINED ≠ BUILT ≠ LIVE
PARTICIPATION ≠ INVESTMENT
TERRITORY ≠ YIELD
OBSERVATION ≠ CONTROL
ZIPVILIZATION
A civilization starting from zero.
The foundations are ready.
The history is not.
BE THERE FROM ZERO.