Skip to content
This repository has been archived by the owner on Mar 8, 2023. It is now read-only.

Latest commit

 

History

History
 
 

platformvm

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
message
message
 
 
README.md
README.md
 
 
abort_block.go
abort_block.go
 
 
add_delegator_tx.go
add_delegator_tx.go
 
 
add_delegator_tx_test.go
add_delegator_tx_test.go
 
 
add_subnet_validator_tx.go
add_subnet_validator_tx.go
 
 
add_subnet_validator_tx_test.go
add_subnet_validator_tx_test.go
 
 
add_validator_tx.go
add_validator_tx.go
 
 
add_validator_tx_test.go
add_validator_tx_test.go
 
 
advance_time_tx.go
advance_time_tx.go
 
 
advance_time_tx_test.go
advance_time_tx_test.go
 
 
atomic_block.go
atomic_block.go
 
 
base_tx.go
base_tx.go
 
 
base_tx_test.go
base_tx_test.go
 
 
block_builder.go
block_builder.go
 
 
block_builder_test.go
block_builder_test.go
 
 
blockchain_status.go
blockchain_status.go
 
 
blockchain_status_test.go
blockchain_status_test.go
 
 
cache_current_staker_chain_state.go
cache_current_staker_chain_state.go
 
 
cache_current_validator.go
cache_current_validator.go
 
 
cache_internal_state.go
cache_internal_state.go
 
 
cache_pending_staker_chain_state.go
cache_pending_staker_chain_state.go
 
 
cache_validator.go
cache_validator.go
 
 
cache_versioned_state.go
cache_versioned_state.go
 
 
client.go
client.go
 
 
codec.go
codec.go
 
 
commit_block.go
commit_block.go
 
 
common_blocks.go
common_blocks.go
 
 
create_chain_tx.go
create_chain_tx.go
 
 
create_chain_tx_test.go
create_chain_tx_test.go
 
 
create_subnet_tx.go
create_subnet_tx.go
 
 
create_subnet_tx_test.go
create_subnet_tx_test.go
 
 
error.go
error.go
 
 
export_tx.go
export_tx.go
 
 
export_tx_test.go
export_tx_test.go
 
 
factory.go
factory.go
 
 
fx.go
fx.go
 
 
health.go
health.go
 
 
import_tx.go
import_tx.go
 
 
import_tx_test.go
import_tx_test.go
 
 
json.go
json.go
 
 
mempool.go
mempool.go
 
 
metrics.go
metrics.go
 
 
mock_cache_current_staker_chain_state_test.go
mock_cache_current_staker_chain_state_test.go
 
 
mock_cache_internal_state_test.go
mock_cache_internal_state_test.go
 
 
network.go
network.go
 
 
network_test.go
network_test.go
 
 
proposal_block.go
proposal_block.go
 
 
reward.go
reward.go
 
 
reward_test.go
reward_test.go
 
 
reward_validator_tx.go
reward_validator_tx.go
 
 
reward_validator_tx_test.go
reward_validator_tx_test.go
 
 
service.go
service.go
 
 
service_test.go
service_test.go
 
 
spend.go
spend.go
 
 
spend_test.go
spend_test.go
 
 
stakeable_lock.go
stakeable_lock.go
 
 
standard_block.go
standard_block.go
 
 
standard_block_test.go
standard_block_test.go
 
 
state.go
state.go
 
 
static_service.go
static_service.go
 
 
static_service_test.go
static_service_test.go
 
 
status.go
status.go
 
 
status_test.go
status_test.go
 
 
subnet.go
subnet.go
 
 
tx.go
tx.go
 
 
tx_heap.go
tx_heap.go
 
 
tx_heap_by_age.go
tx_heap_by_age.go
 
 
tx_heap_by_end_time.go
tx_heap_by_end_time.go
 
 
tx_heap_by_end_time_test.go
tx_heap_by_end_time_test.go
 
 
tx_heap_by_start_time.go
tx_heap_by_start_time.go
 
 
tx_heap_by_start_time_test.go
tx_heap_by_start_time_test.go
 
 
tx_heap_metrics.go
tx_heap_metrics.go
 
 
user.go
user.go
 
 
user_test.go
user_test.go
 
 
validator.go
validator.go
 
 
validator_test.go
validator_test.go
 
 
vm.go
vm.go
 
 
vm_test.go
vm_test.go
 
 

README.md

PlatformVM

Mempool Gossiping

The PlatformVM has a mempool which tracks unconfirmed transactions that are waiting to be issued into blocks. The mempool is volatile, i.e. it does not persist unconfirmed transactions.

In conjunction with the introduction of Snowman++, the mempool was opened to the network, allowing the gossiping of local transactions as well as the hosting of remote ones.

Mempool Gossiping Workflow

The PlatformVM's mempool performs the following workflow:

  • An unconfirmed transaction is provided to node A, either through mempool gossiping or direct issuance over a RPC. If this transaction isn't already in the local mempool, the transaction is issued into the mempool.
  • When node A issues a new transaction into its mempool, it will gossip the transaction ID by sending an AppGossip message. The node's engine will randomly select peers (currently defaulting to 6 nodes) to send the AppGossip message to.
  • When node B learns about the existence of a remote transaction ID, it will check if its mempool contains the transaction or if it has been recently dropped. If the transaction ID is not known, node B will generate a new requestID and respond with an AppRequest message with the unknown transaction's ID. node B will track the content of the request issued with requestID for response verification.
  • Upon reception of an AppRequest message, node A will attempt to fetch the transaction requested in the AppRequest message from its mempool. Note that a transaction advertised in an AppGossip message may no longer be in the mempool, because they may have been included into a block, rejected, or dropped. If the transaction is retrieved, it is encoded into an AppResponse message. The AppResponse message will carry the same requestID of the originating AppRequest message and it will be sent back to node B.
  • If node B receives an AppResponse message, it will decode the transaction and verifies that the ID matches the expected content from the original AppRequest message. If the content matches, the transaction is validated and issued into the mempool.
  • If nodeB's engine decides it isn't likely to receive an AppResponse message, the engine will issue an AppRequestFailure message. In such a case node B will mark the requestID as failed and the request for the unknown transaction is aborted.