Flareth Usage

Flareth is a frontend for the ethereum contracts that facillitate nodes on the network discovering each other and working together to do computation. New versions of contracts may not be completely backwards compatible. For this reason you have the option of changing the input at the top from the default contract to operate on a previous version.

There are four main actions: Create Node, View Node, Create DApp, View Dapp. ##Create Node Nodes are not added to the network by default, after setting up a node, it must be manually added. This can be done through Flareth. Parameters are:

Ident a unique identifier for the node matching the the ident set in the configuration file

State

• Offline node will definitely not be selected for dapps
• Online node will potentially be selected for dapps

IP Address a public facing IP for your node

##View Nodes This is a graphical display of the nodes Flare knows exist. This list is reset when the contract powering the system changes. There is currently one action you can take: Donate to a node by providing the from account in the appropriate input box, selecting a node, and clicking the donate button. Amount denomination (wei vs eth) has not yet been determined and is subject to change. Use TestRPC or Blockapps so this is a non issue.

##Create DApp This is how nodes are notified of and assigned to a dapp. Parameters are:

Ident a unique identifier for the dapp

Fee the payment each node will receive per unit of work done what constitutes a unit of work has not yet been defined

to be implemented:

IPFS Hash the ipfs hash of the spark JAR.

Class class that should be called in the JAR

##View DApps This is a display of a dapps in the contract. It is unique per contract, dapps made in one iteration of the contract will not be viewable in another. There are two actions per dapp:

Start This button changes the dapp state to "start" alerting the master node that it should begin the computation.

Delete/Force Quit This button deletes your dapp from memory and resets nodes back to a state for accepting dapps, ideal for deleting a finished dapp. This is a force quit so if computation is in progress nodes may continue doing work even after the button is clicked.