Thanks, both points sharpen it.
On coverage: agreed, conditionally required rather than optional. Letting it be silently absent would break the same “silence can’t pass as clean” rule we apply to encumbrance. An if/then on backingType (required for RESERVES, COLLATERAL and RECEIVABLES_POOL, not for GUARANTEE) keeps a single schema to validate against. GUARANTEE may eventually want its own shape, a cap rather than a ratio, but I’d treat that as a follow-up rather than force it into coverage.
On currency: report both amounts in their native currencies and leave conversion to the consumer. I’d drop the single shared currency so the schema carries referenceCurrency and backedCurrency separately, with no slot for a pre-converted figure. Applying a published FX rate is mechanical in itself, but choosing the rate, the timestamp and the haircut for FX risk is an adequacy decision, and adequacy is already the consumer’s call under this schema. Native amounts keep the attestor on facts and leave that judgment to the reader.
That points to a sharper version of the same boundary, which I think is the next thing to pin down: what is backedAmount measured on? For a receivables pool, a nominal outstanding balance from the ledger is a fact; an appraised or marked-to-market figure is a judgment, and the schema can’t tell them apart today. One option that reuses what ERC-8320 already has: a small basis field (NOMINAL / APPRAISED), where APPRAISED must reference a VALUATION claim authored by whoever did the appraisal. The number would then always be signed by the party accountable for it, and BACKING would never carry a valuation under the attestor’s name. Curious whether you and @thamerdridi see that as in scope for this claimType or better left per-issuer.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | ERC-8392: Asset Status Interface for Tokenized Assets | 0 | 8.06 | 28-09-2026 |
| 2 | Onchain IP Asset and License Registry | 0 | 8 | 28-09-2026 |
| 3 | ERC-8226: Regulated Agent Mandate | 0 | 5.76 | 28-09-2026 |
| 4 | ERC-8415: Asynchronous Register Projection for NFTs | 0 | 12.36 | 28-09-2026 |
| 5 | ERC-8183: Agentic Commerce | 0 | 12.88 | 28-09-2026 |
| 6 | ERC-8427: Portable Spend Grants | 0 | 10.76 | 28-09-2026 |
| 7 | RFC: Procedure Manifests - Mechanism for AI Agents to Resolve Contractual Disputes | 0 | 13.78 | 29-09-2026 |
| 8 | ERC-8404: Recomputable Verification Receipts | 0 | 8.74 | 28-09-2026 |
| 9 | EIP-8425: Quantum Freeze and Account Recovery | 0 | 4.76 | 28-09-2026 |
| 10 | ERC-8412: Preregistered Acceptance Criteria | 0 | 6.62 | 28-09-2026 |