crypto-org-chain / crypto-org-chain/cronos

"unsafe" binaries

Open
#2,124 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
336
Forks
299
Avg merge
2d 17h
Merged PRs (30d)
4

Description

I'm wondering what those "unsafe" binaries are used for. As probably many people do, I'm experiencing severe performance issues with Cronos block import due to the database size. My understanding is that these "unsafe" binaries are meant to improve things. However, they mention they will crash on staking transactions. So, what can we expect from that? A crash once in a full moon or pretty much immediately - IOW, how often will they crash? Related, when will this be fixed properly without the need for "unsafe" binaries?

Contributor guide

Open the contributing guide

Research direction

The issue does not name any files, tests, or entry points. First identify which unsafe binaries and staking transaction paths are involved, then establish how often they fail and what database-size-related block import behavior is expected before defining a fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
blockchain, databases, performance
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.