Skip to content
Snippets Groups Projects
Select Git revision
  • 91241bd2a566c5dce001fe9cb11a162e9ee698eb
  • develop default protected
  • congestioncontrol
  • merge-v-data-collection-spammer-0.8.2
  • WIP-merge-v-data-collection-spammer-0.8.2
  • merge-v-data-collection-spammer-0.7.7
  • tmp
  • test-masterpow-fixing
  • test-masterpow
  • test-echo
  • v-data-collection
  • v-data-collection-spammer
  • tmp-dump-spam-info
  • dump-msg-info-0.3.1
  • test-dump-message-info
  • spammer-exprandom
  • extra/tutorial
  • without_tipselection
  • hacking-docker-network
  • hacking-docker-network-0.2.3
  • master
  • v0.2.3
22 results

relay-checker

  • Clone with SSH
  • Clone with HTTPS
    • user avatar
    :recycle: refactors web api and client
    capossele authored
    91241bd2
    History
    user avatar 91241bd2
    History
    Name Last commit Last update
    ..
    README.md
    config.go
    config.json
    main.go
    parameters.go
    README.md

    Relay-Checker

    This tool checks whether a transaction which is created on a given node (via broadcastData), is actually relayed/gossiped through the network by checking the transaction's existence on other specified nodes after a cooldown.

    This program can be configured via CLI flags:

    --relayChecker.cooldownTime int    the cooldown time after broadcasting the data on the specified target node (default 10)
--relayChecker.data string         data to broadcast (default "TEST99BROADCAST99DATA")
--relayChecker.repeat int          the amount of times to repeat the relay-checker queries (default 1)
--relayChecker.targetNode string   the target node from the which transaction will be broadcasted from (default "http://127.0.0.1:8080")
--relayChecker.testNodes strings   the list of nodes to check after the cooldown
--relayChecker.txAddress string    the transaction address (default "SHIMMER99TEST99999999999999999999999999999999999999999999999999999999999999999999")