Skip to content
This repository has been archived by the owner on Oct 30, 2018. It is now read-only.

Feature: Create a public API on the bridge for estimated payouts or for GB uploaded + GB/h accumulation for each node-ID. #432

Closed
MeijeSibbel opened this issue Apr 25, 2017 · 5 comments
Labels

Comments

@MeijeSibbel
Copy link

Idea one

  • The bridge already sums-up all the parameters that will determine a node's payout by default (GB/h + uploaded data) , take a snapshot of the network to get the mean values and finally combine this data with the payout formula to get the estimated SJCX payout amount for that point in time. Then make this data public via a API on the bridge. Parameters: nodeID , estimated payout.

Idea two

  • The bridge already sums-up all the parameters that will determine a node's payout (GB/h + uploaded data). Make this data public via a API on the Storj bridge so that farmers can look-up the values for their nodes.

Idea three

  • combine idea one and two, this will result in more parameters that will be given in the API for each node-ID.
@pgerbes1 pgerbes1 self-assigned this Apr 27, 2017
@VanillaScent
Copy link

Please do make this! Would really appreciate it.
This would be handy for new users who want to see how much they make.

@JukeboxRhino
Copy link

I'm not sure how much the wantoo board gets seen (as in I really don't know) but I'll definitely vouch for this here. It would be a big improvement.

@kdavis
Copy link

kdavis commented Jun 23, 2017

I think a combination of both is great. You could even apply some predictions (as an addon) for predictions. I think this'd be great.

@ghost
Copy link

ghost commented Jul 2, 2017

This would be awesome, and it gives motivation to keep going because they see how much they've made, without having to wait til the end of the month, and they might give up because they have to wait.

@RichardLitt
Copy link

👋 Hey! Thanks for this contribution. Apologies for the delay in responding!

We've decided to rearchitect Storj, so that we can scale better. You can read more about this decision here. This means that we are entirely focused on v3 at the moment, in the storj/storj repository. Our white paper for v3 is coming very, very soon - follow along on the blog and in our Rocketchat.

As this repository is part of the v2 network, we're no longer maintaining this repository. I am going to close this for now. If you have any questions, I encourage you to jump on Rocketchat and ask them there. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

7 participants