Skip to content
Menu

Mnemosphere Org

Dev Tools

Is this your project? Claim and verify →

Solidity source, tests, deployment evidence, and security disclosures for Mnemosphere.

What HEY knows

Building
Quiet for 46 daysQuiet: 0 meaningful events in 30 days; latest ship on 2026-09-09. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-09-07 – 2026-09-13 · 1 commit · · Code activity

Why it matters: The first week of code changes HEY has recorded for this project.

This change
Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it to the week of 2026-09-09; HEY first knew on 2026-09-18. HEY indexed it later, as history.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts Mnemosphere Org on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me Mnemosphere Org’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer.

HEY can answer 7 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Quiet.
“Quiet” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-09-09.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · 1 commitv0.1.0-preview.1 — Protocol public previewWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source6 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · 1 commitv0.1.0-preview.1 — Protocol public previewsource:e5593a74-3b6a-48df-8980-9c9d6b31c123+4 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-09-07 – 2026-09-13 · 1 commit mnemosphere-org/mnemosphere-docs

Code activitySource linked

What changed, in the repository’s own words:

1 active day in mnemosphere-org/mnemosphere-docs.

This week HEY looked inside 1 commit to see what changed: 1 changed code.

Record ship:dc1348ef… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗ (opens in a new tab)

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 5 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Mnemosphere Org — as of 25 Oct

Is Mnemosphere Org still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship on 2026-09-09. Evidence
What did Mnemosphere Org ship last?
FactCode changes, week of 2026-09-07 – 2026-09-13 · 1 commit — Code activity, on 2026-09-09. Evidence
What does HEY not know about Mnemosphere Org?
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer. Details

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-09-07 – 2026-09-13 · 2 commits mnemosphere-org/mnemosphere-examples

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in mnemosphere-org/mnemosphere-examples.

    How HEY read this week

    This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · 2 commits (opens in a new tab)

  2. Code changes, week of 2026-09-07 – 2026-09-13 · 2 commits mnemosphere-org/mnemosphere-sdk

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in mnemosphere-org/mnemosphere-sdk.

    How HEY read this week

    This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · 2 commits (opens in a new tab)

  3. Code changes, week of 2026-09-07 – 2026-09-13 · 3 commits mnemosphere-org/mnemosphere-protocol

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in mnemosphere-org/mnemosphere-protocol.

    How HEY read this week

    This week HEY looked inside 1 of 3 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · 3 commits (opens in a new tab)

  4. v0.1.0-preview.1 — Protocol public preview mnemosphere-org/mnemosphere-protocol

    GitHub releaseSource linked

    Mnemosphere Protocol public preview Initial public preview of the Mnemosphere EVM continuity protocol. Included · Solidity Factory and Vault source · deterministic lifecycle and adversarial tests · Robinhood Chain Mainnet deployment evidence · reproducible build artifacts and… Show all
    • Mnemosphere Protocol public preview Initial public preview of the Mnemosphere EVM continuity protocol. Included
    • Solidity Factory and Vault source
    • deterministic lifecycle and adversarial tests
    • Robinhood Chain Mainnet deployment evidence
    • reproducible build artifacts and release manifest
    • deployment guards and public security review Security status This is unaudited preview software. The current source includes a token-settlement fix that is not present in the deployed no-pause Factory bytecode. The deployed contracts have no global deposit pause and the review decision remains…
    View evidence: v0.1.0-preview.1 — Protocol public preview (opens in a new tab)

  5. v0.1.0-preview.1 — Read-only examples preview mnemosphere-org/mnemosphere-examples

    GitHub releaseSource linked

    Mnemosphere Examples public preview Initial collection of read-only verification examples. Included · verify chain ID 4663 · verify deployed Factory runtime hash · inspect the deployment transaction receipt · discover an owner's vault · read vault lifecycle and accounting state… Show all
    • Mnemosphere Examples public preview Initial collection of read-only verification examples. Included
    • verify chain ID 4663
    • verify deployed Factory runtime hash
    • inspect the deployment transaction receipt
    • discover an owner's vault
    • read vault lifecycle and accounting state The scripts never read a private key and never send transactions. They fail closed on network and runtime-hash mismatch.
    View evidence: v0.1.0-preview.1 — Read-only examples preview (opens in a new tab)

  6. v0.1.0-preview.1 — Read-only SDK preview mnemosphere-org/mnemosphere-sdk

    GitHub releaseSource linked

    Mnemosphere SDK public preview Initial read-only TypeScript SDK for Robinhood Chain Mainnet. Included · canonical network and deployment constants · minimal Factory and Vault ABIs · runtime bytecode hash verification · vault discovery and lifecycle/accounting reads · typed ESM… Show all
    • Mnemosphere SDK public preview Initial read-only TypeScript SDK for Robinhood Chain Mainnet. Included
    • canonical network and deployment constants
    • minimal Factory and Vault ABIs
    • runtime bytecode hash verification
    • vault discovery and lifecycle/accounting reads
    • typed ESM build and mocked provider-boundary tests This preview intentionally exposes no signer, private-key, transaction-sending, or deposit API. It does not imply that the deployed contracts are audited or suitable for larger deposits.
    View evidence: v0.1.0-preview.1 — Read-only SDK preview (opens in a new tab)

  7. v0.1.0-preview.1 — Documentation preview mnemosphere-org/mnemosphere-docs

    GitHub releaseSource linked

    Mnemosphere Documentation public preview Initial public technical documentation set. Included · English whitepaper and architecture · private planning and encryption boundaries · vault lifecycle and deployment registry · security disclosures and current review decision · legacy… Show all
    • Mnemosphere Documentation public preview Initial public technical documentation set. Included
    • English whitepaper and architecture
    • private planning and encryption boundaries
    • vault lifecycle and deployment registry
    • security disclosures and current review decision
    • legacy Solana recovery boundary
    • roadmap with proposed features clearly separated from launched functionality The documentation states that native ETH is the only publicly enabled vault deposit asset and that the deployed no-pause contracts remain unaudited and unsuitable for larger deposits.
    View evidence: v0.1.0-preview.1 — Documentation preview (opens in a new tab)

What changed

8 changes on HEY’s record for Mnemosphere Org: 4 releases · 4 weeks of code pushed.

All 8 changes for Mnemosphere Org →

The full change record holds 2 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 21h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 46d ago.
  • TimelineMeasured

Official site

  • Official docsSource unavailableIts website did not answer.
  • API descriptionSource unavailableIts website did not answer.
  • Official site changesSource unavailableIts website did not answer.

Code and packages

  • Repository detailsMeasuredRead 5d ago.
  • Published packagesMeasuredRead 5d ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources