archethic-foundation / archethic-foundation/archethic-node

Avoid node to anticipate election for a transaction

Open
#1,608 0 comments 0 reactions 0 assignees View on GitHub
election feature to-analyze
Dominant language
Elixir
Stars
82
Forks
24
PR merge metrics
No merged PRs in 30d

Description

### Is your feature request related to a problem?

Currently the election for a transaction is determinated by the daily nonce key, the node first public key, the hash of the transaction and the transaction timestamp.
This allow an authorized and available node which know the daily nonce to know the election for a transaction it want to send before the next daily nonce renew.

### Describe the solution you'd like

We should find a new informations to add in the election that evolve frequently and is not predictable.

### Additional context

_No response_

### Epic

_No response_

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified in the issue. Start by tracing how transaction election currently uses the daily nonce key, first public key, transaction hash, and timestamp; done requires that an authorized available node cannot predict the election before the daily nonce renews.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
blockchain, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.