casper-network / casper-network/casper-node

Removal of bincode

Open
#4,276 0 comments 0 reactions 0 assignees View on GitHub
tech-debt
Dominant language
Rust
Stars
399
Forks
224
Avg merge
15h 44m
Merged PRs (30d)
2

Description

During the work for data extensibility, it was determined that removing bincode was desireable, but not necessary in the 2.0 timeframe. This ticket is to reconsider making the change.

Discussion from #4057 copied here:

1. Data migration: All at once? vs. Lazy? vs no-migration (runtime detect of legacy structs)
Let's target for Lazy - we might change the approach if there are performance issues with two databases
2. Shall we drop bincode? Or implement the above for bincode?
Drop it! We might need it for parsing the old data, unless we migrate it

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.