linera-io/linera-protocol

Create examples of Custom{Map,Collection}View for ordered integers (and use them)

Open

#5604 opened on Mar 5, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (32,149 stars) (2,354 forks)batch import
good first issue

Description

We use integers as keys in many places (procotol and examples) but usually without a custom key serialization. As a result, graphql queries show keys ordered by little-endian bytes.

See AskPrice and BidPrice in the matching engine example.

Contributor guide

Tech stack
rust
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
RustFamiliarity with Linera protocolUnderstanding of custom views
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Examine the matching engine example in the Linera protocol repository, specifically the AskPrice and BidPrice types. Look at how they currently use integer keys without custom serialization, resulting in little endian byte ordering in GraphQL queries. Study the existing CustomMapView and CustomCollectionView implementations to understand the pattern. The task is to create new example views that serialize ordered integers correctly, then integrate them into the matching engine or another appropriate location. Refer to the relevant source files in the examples directory and the views module to determine the exact files and structures involved.