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
This is a list of remaining low-priority protocol team tasks for implementing object mapping and retrieval from the DSN.
Cleanups
Create a separate gateway info RPC on the node server and gateway client
Rewrite object_fetcher.rs to use regular positions, not source positions (optional - we improved the source position code instead)
Only return mappings from find_last_archived_block() if we’re starting mapping at that exact block
Potential Object Mapping Changes
add acknowledgements to provide backpressure and make sure the client gets all the mappings (at least from the point where they connect) - awaiting feedback on whether this is needed
mapping generation completed
Extract mappings to objects in system.remark, system.remark_with_event, and seed_history extrinsics
Add a new command line argument (or an optional height) where the node starts creating mappings. This will speed up recovery after downtime when there are lots of archived segments/mappings.
This is a list of remaining low-priority protocol team tasks for implementing object mapping and retrieval from the DSN.
Cleanups
Potential Object Mapping Changes
mapping generation completed
system.remark
,system.remark_with_event
, andseed_history
extrinsicsThe mapping indexer/storage is a separate component, which is out of scope for the protocol team.
Object Fetching
object fetching completed
subspace-networking
piece request-response protocols #3099PieceProvider
PieceProvider
, create anObjectFetcher
, and launch the RPC server - Implement gateway RPC launch and piece getting #3148Documentation
Testing
low priority tests
Object Mappings
Object Fetching
Preparation
Unit Tests
The text was updated successfully, but these errors were encountered: