crypto-com / crypto-com/chain-indexing
Problem: Tx decoder rejects unknown transaction types by default
Open
- Dominant language
- Go
- Stars
- 34
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
## Background
Each Cosmos-based chains may have included different modules onto the chain. In the current design the default behaviour upon unknown transaction types is to panic, which is good for development but produce unfriendly result to production.
## Proposed Solution
- Provide default `RegisterInterface` for different chains (chains can also submit new PR to add their own Interfaces)
- Offer configs on decode error behaviour (panic or ignore)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.