ChainSafe / ChainSafe/gossamer

Implement `rep::ANY_TRANSACTION` and `rep::ANY_TRANSACTION_REFUND` reputation changes

Open
#2,300 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
454
Forks
144
PR merge metrics
No merged PRs in 30d

Description

## Issue summary

- substrate `rep::ANY_TRANSACTION` and `rep::ANY_TRANSACTION_REFUND` is not implemented in Gossamer
- For each received transaction `rep::ANY_TRANSACTION` is applied to peer reputation. `rep::ANY_TRANSACTION_REFUND` is applied after the transaction is imported

## Other information and links

- substrate [line](https://github.com/paritytech/substrate/blob/e9d79daaa782f41680ada04719151371a737c6fb/client/network/src/transactions.rs#L399)
- https://github.com/ChainSafe/gossamer/issues/1887

Contributor guide

Open the contributing guide

Research direction

Start by reading the linked Substrate transactions.rs reference and the related Gossamer issue #1887 to understand the expected reputation behavior. Done means implementing both reputation changes: apply ANY_TRANSACTION for each received transaction and ANY_TRANSACTION_REFUND after the transaction is imported.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.