Note: You can increase the size of the app vertically to see Settings options more clearly!
Hover over your Node Name beneath your profile picture, until you see a “pencil” icon. Click to edit. This is shown along with your Node ID, so your node can be identified during computation.
Your Node ID is a long HEX number used to identify you in the network. It is a unique identifier that cannot be changed. This is necessary for your node to connect to other nodes for computation, and for troubleshooting if any issues arise.
Here you can see how efficient your machine is for computing specific tasks. You can increase those values by giving more resources to your machine in the Network view > Resources.
If you are a Requestor these values will, in future product releases, be used to estimate real deadlines for your tasks and if you are a Provider they will be used to decide if your machine is powerful enough to compute any given task.
Here you can calculate your machines performance benchmarks in 3 categories:
Each app will run a local benchmark, with the same setting on each category and give you a score based on quickly the benchmark completes. Current apps available are blender, luxrender (testnet only) The score is not updated based on performance on the network, only when re-calculated.
Click the calculate button to get a clearer understanding of your machine’s capabilities.
With performance slider (at the bottom of Performance tab) you are able to choose how powerful nodes are going to compute your tasks. This functionality will filter out all providers that do not meet your minimal performance requirements. If you do not want to filter any nodes from your requests just leave the slider at "0" - it will disable this function. After performing local benchmarks you'll see where in performance range your node is placed.
Here you can set the minimum price you will accept as a Provider and the maximum price you will pay per subtask as a Requestor.
This is where you determine your place in the market. The lower your Provider price, the more likely it is that you will be chosen for tasks, but you will make less GNT per subtask. The converse will happen if your Provider price is higher.
If you have a powerful machine and can compute tasks efficiently you can make more money as a Provider.
For task specific pricing instructions go to our Pricing Best Practices section.
If your Requestor maximum is set very low, then you will only get the assigned the lowest price Providers. It is not always the case the low cost = low power machine, but low power machines could cause timeouts which could result in you paying more to get your task completed. A higher Requestor maximum will give you more access to more expensive Providers, which are likely to have more powerful and efficient machines than low price Providers.
The default settings are:
When you navigate to Network Trust you will see a slider and a switch between Providing and Requesting.
Note: Setting trust to 100 will mean that you will only work with nodes with which you have already successfully collaborated with in the past, so this is not recommended when you first start and have yet to compute or request a task.
For Brass Beta, every user’s node starts with the same neutral reputation. Network Trust will become more important as the network grows and node reputations are established through consistent and accurate computations/transactions. As nodes begin to request and compute tasks, the reputation score changes. Reputation is determined by the speed, accuracy and frequency of computations from Providers and the consistency of Requestors. For example, if a Requestor submits a task and then cancels the computation halfway through, leaving providers without a task to compute, the Requestor’s reputation will be negatively impacted.
Here you can define the default output folder where the returned results of your tasks will be saved. You are able to change this location on a task by task basis, but this allows you to set the default.
Note: This is an advanced setting for users more comfortable with the technical aspects of Blockchain dApps.
Some users prefer to use a custom Geth node on their local network to decrease latency.
When you run your own Geth node you can use these options to replace our public nodes with your node. There are options to start geth from golem on the current machine on a certain port, or fill in a remote address with the location of your geth server.