Nectar Network
nothing to read yetStenion publishes no safety score for Nectar Network — not a low one, not a zero.
Known and next on the list to evaluate, with no Stellar mainnet deployment to read yet — and nothing yet confirmed about whether it would be scorable when there is.
Not live on Stellar mainnet yet
Known, and on the list to evaluate. There is no mainnet deployment to read, so there is nothing to score — and nothing yet confirmed about whether it would be scorable when there is.
Why Nectar Network isn’t scored
What we found, stated as what is verified and what is inferred. None of this is a risk finding, and none of it feeds a number.
Flagged as the next protocol to evaluate once it is live on Stellar mainnet. There is no deployment to read, so there is nothing to score.
Listed to be clear about what is and is not known: nothing has been confirmed about whether Nectar would be scorable. That question gets settled from its own contracts when they exist — whether reserves, utilization, liquidity, admin and oracle are all readable via Soroban RPC and Horizon from contracts it controls, rather than the market turning out to be another Blend pool or a deployment whose state lives on another chain. Both of those have happened with other candidates.
This entry rests on no dated check of our own. Unlike the K2 markets above, there is no reading behind it — it records that Nectar is known and being watched, not that its absence from mainnet was verified on some particular day.
Verify this yourself
Look for a Nectar deployment on Stellar mainnet. If one exists, the cheap first test is the one in CONTRIBUTING.md: read the contract’s instance storage, check whether Blend’s V2 pool factory (CDSYOAVX…) answers is_pool(address) with true, and compare its wasm hash against a known Blend pool. A byte-for-byte match means it is a Blend market, not an independent protocol.
This page is a coverage decision, not an assessment of the protocol’s safety, and nothing on it feeds any score. If Nectar Network becomes scorable, this page goes away in the same change that registers it — it is replaced by a real entry in the registry, with a number derived from its own contracts.
Protocol names, logos and trademarks belong to their respective owners and are shown for identification only. Their presence here and any link to a protocol's own site or documentation does not imply endorsement, partnership, or any relationship with Stenion, in either direction.