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)

Open
#905 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

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.

Written by the indexing model from the issue text.

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

Dominant language
No language data
Stars
341
Forks
347
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tronprotocol/tips

All issues in tronprotocol/tips

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.