Frequently Asked Questions.

KODA is the coordination layer that supports the MyHOME ID residential identity framework and its related infrastructure registry.

It supports infrastructure coordination, metadata certification workflows, network participation, and future interoperability between systems tied to modern connected homes.

In practice, that means bringing structure, continuity, and transfer-readiness to the growing world of Smart Device Fixtures and the systems that organize them.

KODA, short for Keeper of Digital Assets, is the name used for that coordination asset within the ecosystem.

MyHOME ID is the persistent identity layer for a property.

A simple analogy: a VIN identifies a vehicle. MyHOME ID is designed to identify a home's connected infrastructure layer over time.

It helps organize transfer-sensitive metadata tied to Smart Device Fixtures, documentation, credentials, infrastructure events, and future certification records associated with modern connected homes.

SDFs are connected devices or systems that are physically associated with a property and typically remain with the home after a sale.

This is different from portable consumer electronics like phones, tablets, or standalone smart speakers.

No. KODA does not represent ownership of real estate, deeds, title interests, or property equity.

The ecosystem is focused on metadata coordination, infrastructure identity, certification frameworks, and digital continuity associated with connected homes and Smart Device Fixtures.

KODA has a fixed 5 trillion total supply. Three trillion KODA is the infrastructure reserve, and that reserve is burned at launch as part of the network's supply design.

The supply model was designed around long-duration infrastructure coordination rather than short-term market scarcity. MyHOME ID begins with approximately 135 million U.S. residential properties already instantiated, and the architecture anticipates future growth in property-linked identity records, metadata certifications, infrastructure coordination, enterprise participation, and ecosystem expansion.

The model was intentionally built for decades of network participation. Over time, portions of KODA may also be permanently removed from circulation through depletion mechanisms, creating two related curves: circulating supply may compress while infrastructure represented by the network expands.

The purpose is infrastructure planning and ecosystem capacity design, not price signaling or valuation commentary.

Ethereum provides settlement and verification. MyHOME ID provides identity. KODA provides coordination.

Infrastructure networks often require their own coordination layer even when they operate on top of existing infrastructure. In this system, KODA supports metadata certification, registry participation, infrastructure coordination, ecosystem operations, and future interoperability frameworks.

It complements Ethereum rather than replacing it.

Identity exists independently of ownership. MyHOME ID is pre-instantiated, which means the property identity exists before any participant interacts with it.

The identity is not created during a transaction. Future records, certifications, assets, or attestations may reference a MyHOME ID, but the identity itself is the foundational layer.

The identity exists before the activity.

Identity infrastructure should exist before documentation events occur. VINs are not created after a vehicle is sold, and routing numbers are not created after a payment occurs.

Property identity should exist before a scan, certification, transfer, or transaction. That is the same design principle used here: identity exists before the scan.

MyHOME ID follows a registry-first model so the identity layer can precede later metadata, certification, or participation events.

MyHOME ID is being structured for continuity beyond any single company. The registry architecture is intended to outlive individual contributors, vendors, or operating entities.

Governance responsibilities are being separated through foundation and DAO structures so long-term stewardship is not dependent on one operator alone.

The objective is measured, durable stewardship of residential identity infrastructure rather than a promise of permanence or a legal guarantee.

Our simple and truthful answer is: no.

But it is fair to acknowledge that the digital asset ecosystem has earned skepticism. There have been countless projects built around hype cycles, unrealistic promises, celebrity marketing, and short-term speculation.

That is not what we are building.

We are not promising overnight wealth. We are not using "to the moon" marketing. We are not paying influencers to manufacture hype. We are not pretending to reinvent finance overnight.

Instead, we are focused on building infrastructure around something tangible and increasingly important: the connected home.

Modern homes already contain growing layers of digital infrastructure, transfer-sensitive systems, and metadata complexity. Our belief is that this layer eventually requires identity, organization, continuity, and standardized coordination.

That is the problem space we are working in. Could we fail? Any startup can fail. Could the market evolve differently than expected? Of course.

But there is a major difference between execution risk and fraudulent intent. We are operating transparently, building publicly, filing intellectual property protections, engaging legal counsel, pursuing structured governance frameworks, and continuously shipping infrastructure tied to a real-world use case.

The goal is long-term utility and stewardship, not short-term hype.

You will not find us prioritizing Formula 1 sponsorships, celebrity campaigns, or "number go up" marketing. We would rather invest in infrastructure, legal structure, product development, and real-world implementation tied to a rapidly emerging category: connected homes and residential digital infrastructure.

The numbers may feel unfamiliar because many presales launch with enormous supplies priced at fractions of a fraction of a cent. That is not the direction we chose.

KODA was anchored around a one-cent framework because the point is to coordinate infrastructure tied to real-world systems and metadata, not to optimize for token trivia.

The minimum helps reduce bot-driven fragmentation, discourages spam wallet farming, creates a more intentional participation base, limits micro-transaction overhead, and supports long-term ecosystem alignment.

The wallet maximum exists to encourage broader participation and reduce concentration during early ecosystem formation.

The goal is not to create an environment dominated by a small number of oversized participants. It is to encourage healthier distribution and alignment while the network is still forming.

The current gateway uses multiple participation controls: access code entry, Regulation S attestation, non-U.S. IP/session checks, OFAC/sanctions screening, wallet connection, wallet auto-enrollment, whitelist authorization, USDC approval, active phase status, and on-chain purchase limits.

These controls are designed to separate review, jurisdictional attestation, wallet authorization, purchase execution, and vesting state. They are good-faith platform and contract controls, not a legal determination that any individual is eligible to participate or that participation is lawful.

Yes. Wallets are screened against OFAC/sanctions data before the gateway issues purchase authorization, auto-enrollment, or whitelist actions.

A confirmed sanctions hit is denied, logged for audit, and surfaced only as a generic compliance-block message to the buyer. Passing screening is only a technical control outcome; it is not legal approval, endorsement, or a conclusion that a particular participation is lawful.

This screening step is separate from Regulation S attestation and separate from geographic session checks.

Setting up a wallet is not that hard if you follow the steps carefully. Most problems happen when people rush, click fake links, share private information, use the wrong network, or let someone else control the wallet for them.

MetaMask is the recommended beginner path because it is widely supported and works well in a desktop browser. Other compatible self-custody wallets may also work through WalletConnect, including Trust Wallet, Coinbase Wallet, and similar wallets that support Polygon and USDC.

Participants connect a compatible wallet, complete the required access checks, and contribute using USDC on the Polygon network.

POL is needed for network gas so the wallet can sign and submit the required on-chain actions. Participation represents early access to the ecosystem, not a finished product, and the participant remains responsible for determining whether participation is permitted under the laws that apply to them.

Polygon gives the presale a lower-fee, faster-confirmation operating environment than Ethereum mainnet, which is better suited for repeated participation checks, approval transactions, and wallet actions during an active access window.

USDC keeps the contribution unit stable and easy to account for. ETH would add more price volatility to the participation flow and is not the cleanest unit for a USDC-denominated presale.

In short: Polygon is the execution layer for the presale, USDC is the contribution rail, ETH remains the settlement asset of the broader network.

The v0.6 presale contract is designed to allow treasury USDC sweeps during an active presale while preserving cumulative raised-all-time reporting.

This was an explicit improvement after v0.5 testing. In v0.6, USDC held by the contract and USDC raised all time are separate values, so treasury operations should not erase the public raised-all-time figure.

No.

KODA is intended to function as infrastructure-oriented coordination layer technology associated with residential identity systems, issuance frameworks, and future interoperability models.

The focus is utility, continuity, infrastructure coordination, and long-term ecosystem development.

No.

Nothing presented by CleanSL8, MyHOME ID, or KODA constitutes legal, financial, tax, investment, or securities advice.

Participants should consult their own professional advisors before making decisions involving digital assets or emerging technologies.

No.

There are no guarantees regarding adoption, future utility, liquidity, market value, participation outcomes, or ecosystem success.

Any forward-looking statements represent goals, expectations, or beliefs, not guarantees.

Because trust matters, especially in emerging technology ecosystems. We believe long-term infrastructure projects require clear communication, measured expectations, transparent positioning, responsible stewardship, and real execution.

That approach may feel less flashy than typical crypto marketing, and we are comfortable with that. It also means saying clearly that presale allocations are not immediately liquid and that public liquidity is a separate launch milestone, not part of the presale phase.

Not during the presale phase. Presale allocations are structured for vesting, access control, and orderly distribution. Public liquidity is a separate launch step that opens only after presale close and launch readiness.

The launch-liquidity reserve, if deployed, is held in the separate Safe-controlled address 0xd493B62A6Da23DFD7BB2d5aFDD5f0190FF574510 and kept distinct from presale funds. That separation keeps the presale focused on allocation and compliance rather than implying immediate market access.

No.

The Regulation S step is a user-submitted attestation plus platform access controls. CleanSL8 does not independently verify citizenship, residency, tax status, legal status, investment eligibility, or sanctions status through the gateway.

Participants remain responsible for complying with the laws that apply to them. Wallet authorization means the platform has allowed the wallet through the current technical controls; it is not a legal opinion, legal approval, or final eligibility determination.

Not as an identity-control step. The current gateway checks for a basic email format and uses the email for access records, notices, and audit context.

The system may send a confirmation email, but it does not currently require OTP, magic-link confirmation, or equivalent proof that the participant controls the inbox.

The email confirms that an attestation record was submitted. Purchase access also requires a valid non-U.S. session, location check, OFAC/sanctions screening, wallet authorization, and an active contract phase.

For example, a U.S. IP or a sanctioned wallet can record an attestation event but still be blocked from receiving a purchase session or completing wallet authorization. That result reflects technical access controls only and does not determine whether participation is lawful.

Possibly. Presale access sessions are time-limited and may expire after approximately 30 days or earlier if compliance, operational, jurisdictional, or platform controls are updated.

A participant may be asked to re-attest, refresh their session, reconnect a wallet, or reconfirm access information before additional participation is permitted. This helps keep eligibility records current and preserves a cleaner audit trail as the presale progresses through testing, active phases, sweeps, closeout, and future distribution events.

Hype creates short-term attention but often weak long-term foundations. We are far more interested in sustainable infrastructure, real-world applicability, enterprise credibility, transfer utility, metadata coordination, and long-term ecosystem trust.

That may not move as fast as meme culture, but it builds stronger foundations.

Participation does not give equity ownership, shareholder rights, creditor rights, profit-sharing rights, dividend rights, or ownership of CleanSL8, MyHOME ID, KODA, or the Foundation.

KODA is a coordination asset for the network. It is not property title, not a claim on the company, and not a promise of financial return.

It also does not imply immediate exchange access or any right to public liquidity before the launch milestone is reached.

The broader architecture is designed around pre-instantiated property identity frameworks at scale. Participation and engagement are optional and evolve over time through onboarding, reporting, verification workflows, and future integrations.

KMC stands for KODA Metadata Certificate. Conceptually, KMCs represent structured certification or issuance events tied to verified infrastructure metadata associated with a residential identity framework.

VIA stands for Verified Infrastructure Asset. It is part of the schema and data framework used to organize and standardize connected infrastructure metadata tied to properties and Smart Device Fixtures.

No.

Much of the long-term vision assumes many future users may never directly interact with blockchain infrastructure at all. The infrastructure layer may eventually operate behind the scenes while consumers, agents, service providers, and enterprise participants simply interact with improved workflows, transfer systems, and digital continuity experiences.

Because homes are becoming increasingly digital, but the systems surrounding them remain fragmented. We believe the future connected home ecosystem eventually requires identity, continuity, transfer-awareness, structured metadata, and coordination frameworks.

That is the long-term problem space we are attempting to help solve.