SkyDog Nexus Whitepaper Discussion — 05/48

One thing that bothers me about emerging-tech projects is how easily a roadmap can start sounding like a list of existing products.

So for this section of the SkyDog Nexus whitepaper, we’re trying to make the distinction explicit.

Our current project-reported status snapshot separates components into:

🟢 DEPLOYED  
🔵 PROPOSED  
🟠 RESEARCH

Here’s what we’re currently representing:

🟢 Reported as deployed

SKYD — Ethereum Mainnet

The project reports 1 trillion SKYD generated on Ethereum.

SKYD — BNB Smart Chain Mainnet

The project reports 1 trillion SKYD generated on BNB Smart Chain.

Those are blockchain components.

They should not be interpreted as meaning that the broader AI platform is already completed.

⸻

🔵 Proposed

SkyDog Nexus — proposed flagship platform

Truth & Verification Engine — proposed subsystem for evidence/provenance validation

Enterprise Digital Twin — proposed product direction

RWA / Property Intelligence — proposed vertical

These are parts of the architecture we’re describing and working toward.

We’re deliberately not labeling them “deployed” simply because they’re in the whitepaper.

⸻

🟠 Research

Physical AI

This is a longer-horizon research direction.

It shouldn’t be presented as though a commercial Physical AI product exists today.

⸻

Presale policy

The project currently allocates 25% to presale:

20% public sale  
5% private sale

Current fixed presale rate shown in the project material:

$0.00004195/SKYD

But there’s another distinction we think matters:

We don’t want to present a guaranteed future market-price target.

A project can control development decisions.

It cannot guarantee what an open market will eventually price an asset at.

I’d rather have the project judged over time by things such as:

Does the technology ship?

Does anyone actually use it?

Can the claims be independently verified?

Is the infrastructure secure?

Does SKYD eventually have meaningful ecosystem utility?

Is relevant on-chain activity transparent?

That brings me to the part I’d genuinely like feedback on.

What should qualify as “deployed”?

Is publicly accessible code enough?

Should it require:

A) Working production system  
B) Public test environment  
C) Open-source code  
D) Independent security audit  
E) Real users  
F) Usage/performance metrics  
G) Some combination of all of these

And should a project be expected to maintain a public status page showing exactly when components move from research → prototype → testing → deployed?

Critical answers are welcome.

I’d rather establish a demanding definition now than lower the standard later.

This is 05/48 of our SkyDog Nexus whitepaper discussion.

🌐 skydognexus.com

Disclosure: Statuses above are project-reported. Proposed and research-stage components are not representations of completed products and may change or never reach deployment. SKYD is a digital asset; this is not financial advice.

How should an AI/blockchain project distinguish between “deployed,” “proposed” and “research”?