Skip to content

docs: correct the SOL attestation note -- the staking page supports pays_yield=0 - #186

Merged
eaitbrahim merged 1 commit into
mainfrom
docs/correct-sol-attestation-note
Aug 8, 2026
Merged

docs: correct the SOL attestation note -- the staking page supports pays_yield=0#186
eaitbrahim merged 1 commit into
mainfrom
docs/correct-sol-attestation-note

Conversation

@eaitbrahim

Copy link
Copy Markdown
Contributor

Follow-up to #185, correcting a claim I made there.

The correction

Open item 3 said the live-DB SOL attestation's source (solana.com/staking) "sits awkwardly against pays_yield=0". Fetching the page shows the opposite — it is direct evidence for the field:

"In order to earn staking rewards … the tokens in a stake account must be delegated to a validator."

No rebasing, no automatic distribution to holders. Bare holding earns nothing, which is exactly what pays_yield=0 asserts.

The gap that is actually there

It is the wrong kind of source, not a contradictory one. AssetAttestation.source is documented as "where this was established — a URL, a standard, a scholar's ruling." A vendor product page establishes the mechanical fact; it cannot establish the ruling that a native L1 coin is Mal Hukmi, lawful to own and trade.

Every keel.db attestation carries both — KB source-86, the three-layer screen reasoning, and an explicit "Attests bare unstaked spot only." This row carries only the mechanical half, and only implicitly. screen_asset cannot tell the difference: screen.py:249 checks source.strip() is non-empty and nothing more.

Provenance — closed, not left as "should be confirmed"

~/.zsh_history records the exact command at epoch 1786148982, one second before the row's attested_at:

./.venv/bin/keel --config config.live-sandbox.yaml --db keel-live.db \
  assets attest --asset SOL --sector "layer-1 smart-contract blockchain infrastructure" \
    --backing native --source "https://www.solana.com/staking" \
    --attested-by "Elmehdi Aitbrahim"

Preceded by a placeholder attempt at 1786148907 and two keel fetch --products SOL-USD runs. Hand-typed at the terminal — not an agent, not the daemon, not the #185 investigation.

Also added

  • SOL now has two attestations with different evidentiary bases; which one governs depends on which --db a command runs against.
  • The page notes ~8% initial inflation decaying to 1.5%, so a bare holder is diluted rather than paid — not a riba yield, but whether that makes staking economically quasi-compulsory is a scholarly question, not one this file can answer.
  • None of it is live-reachable: SOL is not in the live allowlist and has no rule in keel-live.db, so rail 1 blocks any SOL intent regardless of the attestation.

Docs-only. No code, no config, no database touched.

🤖 Generated with Claude Code

…ays_yield=0

Follow-up to #185, correcting a claim I made there.

Open item 3 said the live-DB SOL attestation's `source` (solana.com/staking) "sits awkwardly
against pays_yield=0". Fetching the page shows the opposite. It states: "In order to earn
staking rewards ... the tokens in a stake account must be delegated to a validator," with no
rebasing and no automatic distribution to holders. Bare holding earns nothing -- which is
precisely what pays_yield=0 asserts. The citation is direct evidence FOR the field, not
against it.

The real gap is narrower and different: it is the wrong KIND of source. AssetAttestation.source
is documented as "where this was established -- a URL, a standard, a scholar's ruling." A vendor
product page establishes the mechanical fact but not the RULING that a native L1 coin is Mal
Hukmi, lawful to own and trade. Every keel.db attestation carries both (KB source-86 + the
three-layer screen reasoning + "Attests bare unstaked spot only"); this row carries only the
mechanical half, implicitly. screen.py:249 cannot tell the difference -- it checks
source.strip() is non-empty and nothing more.

Provenance also resolved, and it was an open question worth closing rather than leaving as
"should be confirmed": ~/.zsh_history records the exact command at epoch 1786148982, one second
before the row's attested_at, preceded by a placeholder attempt and two `keel fetch --products
SOL-USD` runs. Hand-typed at the terminal -- not an agent, not the daemon.

Added: SOL now carries two attestations with different evidentiary bases, so which governs
depends on which --db a command runs against; and the page's ~8% initial inflation decaying to
1.5% means a bare holder is diluted rather than paid, which is a scholarly question rather than
one this file can answer. None of it is live-reachable -- SOL is not in the live allowlist and
has no rule in keel-live.db, so rail 1 blocks any SOL intent regardless.

Docs-only; no code, no config, no database touched.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@eaitbrahim
eaitbrahim merged commit a783443 into main Aug 8, 2026
1 check passed
@eaitbrahim
eaitbrahim deleted the docs/correct-sol-attestation-note branch August 8, 2026 04:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant