AVP-DS: Increasing the Number of Confirmed Transactions Through Address-Based Parallel Validation Paths and Separation of the Decision Layer from the Execution Layer (formerly ATHENA)

Ouverte
#905 12 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
20/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
À l'abandon
Domaine
documentation

Piste de recherche

Start by reading the ATHENA proposal in this issue and the complete TIP draft referenced there. Review Pull Request #906 to determine the current proposal scope and status; the work is done when the proposal's design and review discussion have reached a clear decision.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

AVP-DS: Address-Based Parallel Validation Paths — Dynamic & Smart

The AVP-DS capability enables more efficient distribution of incoming transactions based on instructions and execution permits issued by the Network Protocol, through the separation of the Decision Layer from the Execution Layer and the organization of address-based parallel validation paths.

In this approach, parallel validation paths are created and expanded dynamically based on transaction addressing and the execution permits issued by the Network Protocol, rather than being established by default or predetermined in advance.

This capability does not increase the network's base TPS or the TPS of its execution engine. Rather, by distributing incoming transactions among parallel validation paths and effectively utilizing existing or additional capacity, it increases the number of confirmed transactions in the network without requiring any changes to the consensus algorithm, ledger structure, state transition logic, or the network's native validation rules.

All decisions regarding sequential or parallel validation, path determination, conflict management, and execution permit issuance are made exclusively by the Network Protocol and communicated to the network's execution components through the Execution Permit. Once an Execution Permit is issued, all relevant network components are required to strictly follow the path and instructions specified in it. No execution component may independently alter the authorized path or act outside the scope of the issued permit.

Thank you for your time and consideration.
A complete TIP draft is available for review and discussion.
Pull Request: #906

Langage dominant
Aucune donnée de langage
Étoiles
341
Forks
347
Métriques de merge des PR
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de tronprotocol/tips

Toutes les issues de tronprotocol/tips

Issues similaires

Plus d'issues Documentation

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.