Solum Token
Solum is the blockchain asset at the foundation of Zipvilization.
Before it is land,
before it becomes Territory,
before a Holder becomes a Colonist,
before a Farm develops,
before Zips emerge,
Solum is a token governed by a Smart Contract.
This page begins there.
Solum is the blockchain substrate.
Zipvilization gives that substrate territorial meaning.
The token
At contract level, Solum is a fungible blockchain asset.
Its state can be expressed through technical concepts such as:
- total supply,
- balances,
- addresses,
- transfers,
- allowances where applicable,
- Taxes,
- Pool state,
- Burn,
- transaction limits,
- wallet limits,
- and other contract-defined behavior.
These are blockchain concepts.
They should remain understandable without requiring the world metaphor.
The world interpretation comes afterward.
Solum and Zipvilization
Solum has a canonical territorial equivalence:
1 Solum = 1 m²
This relationship connects the token with the world.
At blockchain level:
1 Solum is one unit of the token.
Inside Zipvilization:
1 Solum represents 1 square meter of territorial substrate.
The amount does not change.
The interpretation does.
This two-layer structure is fundamental throughout the project.
| Blockchain | Zipvilization |
|---|---|
| Solum | Territorial substrate |
| Holder | Colonist |
| Balance | Controlled land |
| Pool | Dormant Land |
| Burn | Permanent Nature |
| Transfer | Redistribution of Solum |
| Supply | Finite world substrate |
Blockchain describes the mechanism.
Zipvilization describes the meaning.
Token and land are not two different assets
There is no separate land token hidden behind Solum.
There is no additional territorial NFT required to make Solum meaningful.
There is no second asset that replaces Solum when Territory appears.
Solum remains Solum.
Territory is derived from the canonical interpretation of Solum state.
That means:
Token balance
↓
canonical Solum interpretation
↓
territorial capacity
The underlying blockchain asset remains fungible.
The world layer gives that quantity structure.
Holder and Colonist
At blockchain level, an address that controls Solum is a Holder.
Inside Zipvilization, the relevant participant is understood as a Colonist.
These terms are related.
They are not interchangeable in every context.
Holder
describes blockchain ownership.
Colonist
describes participation inside the world.
The distinction matters because blockchain mechanics must remain technically precise.
A contract transfers Solum between addresses.
It does not need to execute a function called “move a Colonist’s land” for the world interpretation to exist.
Balances
A Solum balance records how much Solum an address controls according to blockchain state.
For example:
10,000 Solum
At the world layer:
10,000 Solum = 10,000 m²
But that does not automatically mean:
10,000 m² = mature State
Several different dimensions must remain separate.
Balance
determines quantity.
Territorial thresholds
determine structural capacity.
Time
determines development.
Zips
express biological state.
The token provides the substrate.
It does not contain the whole civilization.
→ Explore Territories
→ Understand Time
→ Discover Zips
Transfers
Solum can move between addresses according to the contract rules.
A transfer changes blockchain balances.
That operation may also interact with:
- Taxes,
- maximum transaction constraints,
- maximum wallet constraints,
- launch restrictions,
- Pool mechanics,
- and other explicitly implemented rules.
The technical sequence is simple:
Solum leaves one valid balance
↓
the contract applies the relevant rules
↓
resulting balances change
Inside Zipvilization, those changes can alter territorial control.
But the contract should remain describable in blockchain language first.
The contract transfers Solum.
SolumWorld determines the resulting world meaning.
Solum is finite
Solum is not designed as an endlessly expanding territorial currency.
The canonical supply is:
100,000,000,000,000 Solum
or:
100 trillion Solum
Because:
1 Solum = 1 m²
the original territorial substrate is:
100,000,000,000,000 m²
No continuing inflationary minting is required to expand civilization.
Civilization grows through structure and interaction.
Not through the creation of additional land.
Token creation and world creation are different things
This distinction is important.
The Solum token supply establishes the substrate.
It does not create a mature world.
At Genesis, Solum can exist while most of Zipvilization remains barren.
The token exists.
The land exists.
Civilization does not.
Then state begins to change.
Solum leaves its dormant condition.
Holders participate.
Colonists appear.
Territories become possible.
Bloch begins to matter.
Zips emerge.
Time accumulates.
Civilization may eventually develop.
The token can exist before the civilization does.
Solum in the Pool
Part of the finite Solum substrate can remain in its defined Pool state.
Technically:
Pool-held Solum
Inside Zipvilization:
Dormant Land
This is one of the most important translations in the architecture.
Pool-held Solum is not imaginary future supply.
It is not land waiting to be minted.
The Solum already belongs to the finite world.
Its state is simply different.
It has not yet entered active colonization.
The Pool contains Solum.
Zipvilization sees land waiting for life.
Solum and Burn
Solum can also undergo an irreversible technical transition through Burn.
At blockchain level:
Solum is Burned.
Inside Zipvilization:
the corresponding land becomes Permanent Nature.
Again, the blockchain mechanism remains explicit.
We do not rename Burn technically.
We interpret its consequence inside the world.
This creates one of the defining inversions of Zipvilization:
Pool
technically holds Solum,
but represents barren land waiting for civilization.
Burn
technically removes Solum permanently,
but represents land whose natural state becomes permanent.
Dormant Land waits for life.
Permanent Nature cannot be colonized again.
Solum and Taxes
Solum can also move through Tax mechanisms.
Tax does not create new Solum.
It redirects existing Solum according to the contract rules.
This distinction preserves finite accounting.
A Tax may alter:
- balances,
- destinations,
- accumulated Solum,
- and future economic state.
But it does not need to expand supply.
Inside Zipvilization, these movements can later become part of a larger economic architecture.
The contract executes the flow.
Civilization gives the flow context.
Solum and Fair Access
Finite supply creates another problem.
Concentration.
If Solum can be accumulated without meaningful constraints during sensitive phases, a small number of actors may capture a disproportionate part of the finite world before broad participation can develop.
The contract therefore includes technical mechanisms intended to constrain access and concentration where canonically defined.
These can include:
- maximum transaction rules,
- maximum wallet rules,
- launch-phase restrictions,
- dynamic limits,
- and other explicit contract conditions.
Those mechanisms do not change what Solum is.
They change how Solum can move or accumulate under defined conditions.
Solum does not equal Territory
This distinction must remain explicit.
A Solum balance provides territorial substrate.
Territory requires canonical thresholds.
The hierarchy is:
| Territory | Solum |
|---|---|
| Farm | 8 |
| City | 256 |
| State | 8,192 |
| Kingdom | 262,144 |
Therefore:
Solum provides quantity.
Territorial rules provide structure.
And even after a territorial threshold is reached:
structure is not maturity.
Maturity requires development through the canonical biological and temporal architecture.
Solum does not equal population
Solum is land.
Zips are population.
They must not be collapsed into the same variable.
The relationship is:
Solum
territorial substrate.
Zips
native population.
Time
development.
A larger amount of Solum can support larger territorial structures.
It does not simply generate unlimited Zips.
Population follows its own canonical capacity and maturation rules.
Solum does not equal power
Solum matters enormously.
It determines territorial capacity.
But territorial capacity should not automatically become every possible form of power.
A large Holder may control substantial Solum.
Inside Zipvilization, that can support large Territory.
But future civilization may contain other dimensions:
- economic importance,
- productivity,
- political influence,
- alliances,
- strategic position,
- institutions,
- reputation,
- and collective organization.
Solum creates capacity.
It does not pre-write civilization.
Solum does not equal investment
Solum is a crypto asset.
It can have a market.
It can have a price.
It can be transferred.
Those facts should not be hidden.
But Zipvilization does not define Solum solely through expected financial return.
Its canonical role is structural.
Solum provides participation in a finite territorial world.
This creates a critical distinction:
You can buy Solum.
What you are entering is Zipvilization.
The project therefore emphasizes participation rather than reducing Solum to a speculative object.
Market behavior may exist.
It does not define the full purpose of the asset.
Solum and Tokenomics
The token does not exist in isolation.
Its behavior is shaped by the broader economic architecture.
Tokenomics connects:
- finite Supply,
- distribution,
- Pool,
- Taxes,
- Burn,
- Fair Access,
- circulation,
- scarcity,
- and economic incentives.
Solum Token defines the asset.
Tokenomics explains how the economic mechanisms surrounding that asset interact.
Solum and Security
A token only has meaning if its technical behavior can be trusted to follow its contract.
Security therefore matters at the foundation.
Important questions include:
- who has privileged authority,
- which parameters can change,
- which rules are immutable,
- whether supply can be expanded,
- what permissions exist,
- how launch restrictions operate,
- how limits are enforced,
- how external dependencies behave,
- and what risks remain.
Security should describe the actual architecture.
Not make generic claims that the contract is “safe.”
Solum and Canonical Rules
Some contract properties deserve an especially explicit status.
Canonical Rules should identify foundational relationships that other systems depend upon.
For example:
1 Solum = 1 m²
is not merely marketing language.
Territories depend on it.
SolumWorld depends on it.
SolumTools may derive from it.
SolumView represents its consequences.
Artificial Intelligence uses it when reasoning about the world.
A foundational relationship must therefore have a clear canonical source.
ERC-20 compatibility
Solum is designed within an EVM-compatible blockchain environment and follows the ERC-20 token model where defined by the canonical implementation.
That gives the asset familiar blockchain behavior and interoperability.
The important point is architectural:
Zipvilization does not need to invent a completely new ownership primitive merely to create territorial meaning.
It can begin with a standard fungible token architecture.
Then build deterministic world interpretation above it.
Standard token underneath.
Unusual world above it.
The exact deployed implementation, inherited contracts, interfaces, overrides, and extensions belong to the technical Repository and verified source.
Network is infrastructure
The blockchain network provides infrastructure.
It is not the identity of Solum.
The canonical implementation can target an EVM-compatible environment appropriate to the technical requirements of Zipvilization.
Network choice affects:
- transaction cost,
- block progression,
- infrastructure,
- accessibility,
- indexing,
- tooling,
- and operational behavior.
But the conceptual identity remains:
Solum is Solum.
The world architecture should avoid depending unnecessarily on a single provider, interface, or visualization.
Technical migration, if ever necessary and canonically permitted, should preserve the integrity of the system rather than redefine it casually.
Public state
One of the strengths of Solum as a blockchain asset is observability.
Relevant state can be inspected.
Balances can be read.
Transfers can be followed.
Supply can be measured.
Burn can be observed.
Taxes can be analyzed.
Pool state can be tracked.
Concentration can be measured.
This allows SolumTools and Metrics to build upon public evidence.
→ Explore SolumTools
→ Explore Metrics
One asset, several states
The same Solum asset can participate in different technical and world conditions.
For example:
| Solum state | World interpretation |
|---|---|
| Pool-held | Dormant Land |
| Holder-controlled | Colonist-controlled land |
| Burned | Permanent Nature |
| Moving through transfer | Territorial redistribution |
| Redirected through Tax | Economic flow |
The token remains Solum.
State determines the consequence.
This is one of the central ideas of the entire architecture.
Same asset.
Different state.
Different world meaning.
From token to world
The chain can be summarized as:
Solum Token
↓
finite blockchain asset
↓
Balance
↓
controlled quantity
↓
Territorial interpretation
↓
Farm / City / State / Kingdom capacity
↓
Time and Zips
↓
development and maturity
↓
SolumWorld
↓
canonical world state
↓
Civilization
may emerge from participation.
The token is the beginning of that chain.
It is not the end.
Solum Token in one view
Blockchain
Asset: Solum
Model: fungible token
Environment: EVM-compatible architecture
Canonical Supply: 100,000,000,000,000 Solum
Ongoing inflationary minting: No
Core relationships:
- balances,
- transfers,
- Supply,
- Pool,
- Burn,
- Taxes,
- Fair Access,
- Security,
- Canonical Rules.
Zipvilization
1 Solum = 1 m²
Holder = Colonist interpretation
Balance = controlled land
Pool = Dormant Land
Burn = Permanent Nature
Territorial thresholds = structured land
Boundary
Solum is the asset.
Zipvilization is what that asset makes possible.
Follow Solum Token
How much Solum exists?
→ Supply
How do the economic mechanisms interact?
Where is dormant Solum held?
→ Pool
How does Solum leave colonizable supply permanently?
→ Burn
How are transfer Taxes handled?
→ Taxes
How is concentration constrained?
What protects the contract architecture?
→ Security
What foundational rules must remain explicit?
What does Solum mean inside the world?
→ Solum
Where is the technical implementation?
The first piece
Zipvilization can eventually become extremely complex.
Cities.
States.
Kingdoms.
Zips.
Production.
Economics.
Politics.
Alliances.
Conflict.
Nature.
Artificial Intelligence.
A world with history.
But underneath all of that is something deliberately simple.
A finite blockchain asset.
A balance can be read.
A transfer can be verified.
A Supply can be counted.
A Burn can be observed.
A Tax can be measured.
A rule can be inspected.
And one canonical relationship connects that technical substrate with everything above it:
1 Solum = 1 m²
That is where the token stops being only a token.
And where Zipvilization begins to acquire ground beneath its feet.
→ Return to Smart Contract
→ Continue to Supply
→ Explore Solum in The World