You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The transfer of large entities or many entities consumes considerable bandwidth. Which information per entity is most valuable is use-case specific and should be specified by the application.
242
-
243
-
**Let users decide which parts of an entity to return:**
244
-
-**Payload** - Binary data (can be large)
245
-
-**Attributes** - Key-value metadata
246
-
-**Metadata** - Owner, expiration, timestamps
247
-
248
-
**Current implementation:**
249
-
The SDK already supports projections via the `fields` parameter using bitmask flags:
250
-
```python
251
-
from arkiv.types importPAYLOAD, ATTRIBUTES, METADATA
-**Creation Flags**: Entities should support creation-time flags with meaningful defaults.
295
224
Flags can only be set at creation and define entity behavior:
296
225
-**Read-only**: Once created, entity data cannot be changed by anyone (immutable)
@@ -316,8 +245,8 @@ Flags can only be set at creation and define entity behavior:
316
245
```
317
246
318
247
-**Offline Entity Verification**: Provide cryptographic verification of entity data without querying the chain.
319
-
-Signature verification for entity authenticity
320
-
-Minimal trust assumptions for light clients
248
+
-Currently not supported
249
+
-Proposal: Store entity keys (and block number) in smart contracts and work with an optimistic oracle approach (challenger may take entity key and checks claimed data against the data of an Arkiv archival node)
0 commit comments