iota-tangle-io/dtlg

App for making the IOTA network faster.

DTLG

The Distributed Tangle Load Generator is an application for "spamming" the Tangle with healthy transactions in order to increase overall transaction throughput.

features:

• modern web interface written in React
• websocket communication for real time updates from the spammer
• chart which shows transactions per seconds
• metrics about used trunk, branch and milestone transactions
• on-the-fly node and PoW method changing
• transaction log with confirmation rate

usage

note on the downloads: you can check the md5 checksums of the binaries on the Travis build log.

desktop

1. download the zip file for your operating system from the release page. (darwin is for mac os)
2. unzip the zip file and execute the binary
3. your browser opens automatically
4. enter an IRI node url (you can use http://iota-tangle.io:14265 if you don't have an own node)*
5. press the start button on the web interface to start generating transactions

headless server

1. download the zip file for your operating system from the release page.
2. unzip the zip file and execute the binary
3. Access http://your-ip:9090 to open DTLG
4. enter an IRI node url (you can use http://iota-tangle.io:14265 if you don't have an own node)*
5. press the start button on the web interface to start generating transactions

the port and interface on which DTLGs listens for requests can be modified in configs/network.json.
* it's discouraged to use public IRI nodes

proof of work

DTLG automatically uses the best available PoW method when starting. This is the preferred order of PoW methods: SSE, C, Go. In our tests however, PoW C was fastest on Mac, thereby DTLG automatically defaults to it when it detects Mac systems. Our test system with Win10 and an i7 4770k@4,1Ghz reaches about ~1 TPS with SSE. The PoW method can be modified on the fly on the web interface.

dtlg's Issues

Change weight magnitude while spamming

For testing purposes it will be nice if we can control the weight magnitude.
Testnets may require a smaller mwm, thus we can do less work.

Add "Choose TAG" as a textbox beside "Choose node"

After crash theres zero notifications

A guy tried running another spammer simultaneously, the dtlg spammer stopped working, no error, nothing in logs, just stopped...

Node configuration not adapting to webinterface inputs.

Only the initial node which is entered on setup will be connected to. Manually changed node url (web interface) is not considered.

URL with localhost is not seen as valid

http://localhost:14265 seems not to be valid with the currently used regex.

Exit or quit button

Adding an exit button to the web ui would be a nice enhancement.

No release versions for Davin since alpha12?

Is there any reason you‘re now longer offering binary releases for Darwin since alpha12++?
—-

Issues with node selection

Node does not switch properly upon entering it

Once WebUI opens, minimize cmd

Add port to WebUI to README

Tooltips to buttons

Add tooltips with short explanations to these buttons so people understand easier what they're about.

Remove tracking of 'bad' tips

I don't think confirming our own transactions is a bad thing anymore. Now that our code consistently gets confirmations it doesn't make sense to severely restrict our tip options. It should help to further confirm the other transactions if we bury them behind more of our own.

Integrate confirmation ratio statistics on webinterface.

Code base for ratio checking per address is already present https://github.com/cwarner818/tt