Cowrie Research

nayms-primary-sources-2026-05-08

3 min read

Nayms primary sources — 2026-05-08

Classification takeaway

Nayms is best cataloged as tokenized insurance and reinsurance market infrastructure centered on entities, segregated accounts, participation-token sales, and internal market plumbing. The important mechanism is not simply “insurance onchain”; it is that underwriting vehicles themselves become tokenizable capital-market objects with policy issuance, dividends, and trading routed through one platform ACL and accounting model.

Primary sources reviewed

  1. Docs root — https://docs.nayms.com/

    • Says Nayms uses Ethereum smart contracts to let insurance and reinsurance policies be created, underwritten, tokenized, traded, and settled onchain.
    • Describes companies or segregated accounts as entities that can issue multiple policies.
    • Explains that those accounts can issue participation tokens (P-Tokens) sold to capital providers and later distribute profits to token holders.

  2. GitHub organization — https://github.com/nayms

    • Describes Nayms as the world’s first fully regulated marketplace for onchain insurance.
    • Shows active repositories for contracts-v3, the NAYM token, and build/deployment tooling.
    • Provides a useful reality check that the project is shipping public smart-contract infrastructure instead of only publishing narrative material.

  3. Contracts v3 README — https://raw.githubusercontent.com/nayms/contracts-v3/main/README.md

    • Confirms live deployments on Ethereum and Base.
    • States that the architecture uses the EIP-2535 diamond standard and Gemforge deployment tooling.
    • Notes phased deployments and that mainnet upgrades require enabling via an MPC wallet, which is important evidence about where operational control concentrates.

  4. EntityFacet — https://raw.githubusercontent.com/nayms/contracts-v3/main/src/facets/EntityFacet.sol

    • Documents entity tokenization directly: enabling tokenization, updating token info, and starting token sales.
    • The facet comment explicitly frames entities as the place where policies and token sales are handled.
    • Useful for grounding the claim that underwriting entities themselves are tokenizable financing vehicles.

  5. SimplePolicyFacet — https://raw.githubusercontent.com/nayms/contracts-v3/main/src/facets/SimplePolicyFacet.sol

    • Shows the actual simple-policy lifecycle primitives: create policy, pay premium, pay claim, cancel policy, and calculate premium fees.
    • Makes clear that important policy data can stay offchain while a signed hash anchors it onchain.
    • Suggests a hybrid architecture where execution rails are onchain but much policy context and underwriting workflow remain operationally mediated.

  6. TokenizedVaultFacet and MarketFacet —

Whitepaper / technical-doc status

  • The docs root links a Nayms whitepaper and token paper on DocSend.
  • In this pass, the linked DocSend whitepaper URL returned “This document is not available,” so no canonical paper copy was added to the corpus.
  • The accessible primary materials were still enough to classify the project because the docs root plus public contract facets expose the key entity/token/policy/accounting surfaces directly.

Why it stays in the active corpus

  • Strong long-tail comparison case for insurance-market design that is distinct from Etherisc’s framework model and Ensuro’s tranche-based solvency model.
  • Useful for reasoning about where underwriting control and rent may migrate when insurance vehicles become token issuers and marketplace participants.
  • Adds a meaningful bridge between alternative-risk-transfer intuition, internal-cap-table tokenization, and onchain matching-market design.

Graph View