No way I can think of off the top of my head. Perhaps better to use their own Discord IDs, and then help them at the other end when we send through the rewards?
But that way they wonāt be able to participate in wave 1 for a reward, right?
Privacy. Security. Freedom
1 Like
Ah I see what you mean. Iāll have a think.
1 Like
Youāll need to either have another field or allow appending a code (self defined deviceID) to the end of the discord ID which just allows people to identify their device (for instance)
EG for me I might go with āneo:Odyssey1ā and āneo:odyssey2ā and so on.
By being able to append (or 2nd field) their device ID then people can evaluate which device works best for them and then people can list their device & earnings and we can tally the results to see if there is a statistical significance to the device-type/OS
You send back to the user a list with earnings by deviceID and is upto the user if they will tell others the results. Also if people state the device used and OS for any given deviceID then Maidsafe could do this analysis automatically. This could prove very valuable
And it solves @Dimitar situation nicely.
And then you reward according to discordID and the user does what he will with the deviceID figures
2 Likes
It adds a bit to the build, and certainly adds another layer of complexity when it comes to the reporting and back-office processes, and around the rewards payments after launch too.
All the mechanisms are are there for individuals to have their contributions measured and then rewardedā¦ so Iād say itās unlikely that weāll be adding extra to cater specifically for pools. The Netowrk is design to not require pooling either.
Other thing I would add @Dimitar, is that although youād be helping those 20-100 contributors to be in the Wave 1 competitionā¦ they wouldnāt count towards our overall targets of participants.
Butā¦ add those 100 people individually, and we are a good step closer to the 1000 target where everyones rewards will double, including yours!
4 Likes
By appending using a specified separator, it becomes a case of the reward program truncating the ID at the separator and all the same from there.
Then the list of results you are sending people will have the full ID with the rewards gathered by ID in the āreport writerā program you would be using to generate the rewards list to send each userID of their rewards sent in.
Its something I used to do for one of the government departments collecting stats back in the 80ās to make separation of figures much easier in a later process. Its not difficult and is a simple truncation done when totalling rewards for each discord ID and leaving the full for doing a āmailoutā listing for each discordID that I actually suspect you would be doing anyhow. Maybe even the figures separated by day or week or month and by using full ID then it automatically separates by deviceID.
And since the ID is only now being incorporated then its adding a line of code for tallying rewards by discord ID. And adding a field for the āreport generatorā configuration
1 Like
Iām just going to add up all the nodes together that will use my discord id and split the rewards evenly between the total number of nodes people are running ie if someone has 10 nodes running out of a combined total of 200 nodes they get 5% of my rewards total (less my commission of course 
)
2 Likes
The point is that some people are technically illiterate and after setting up the nodes I want to know that they worked + if I include people I donāt know I want to know that they are honest, not that they just say āIām connecting with 10 nodesā , but subsequently they did notā¦
Privacy. Security. Freedom
4 Likes
People you donāt know should just be added to the next wave I think then itās down to them. As for knowing if they worked maybe run vdash alongside the nodes so it can show them their nodes are still connected.
3 Likes
Guys I running for last 3 weeks about 100 nodes for entire time, is there any way of participating in waves? Can someone point me where on autonomy server at discord i can find additional data regarding that?
Yeah, I think this is a better approach for the whole.
I think people not apt to run nodes themselves at this point is better left for later waves. We want to have folks that are somewhat willing to take it to themselves and able to keep running the nodes.
@JimCollinson, when are the number of people running nodes measured? I think some kind of delay would be great to have in order to keep people running the nodes after the startup.
1 Like
To be included in the total, you have to:
- Sign up to the rewards program with your Discord Username (youāll be added to a channel/group when you are in)
- Run a node and add your Discord Username
- Earn your first Token/Nano
At that point, you are added to the wave, and count towards the overall totalā¦ And we inch closer to those multipliers!!-
4 Likes
But what if participants drop out? We may get to 2000 for example, and after a while drop back to 1900 again.
It you contributed, then you still count!
2 Likes
That is my concern, how to make sure to have critical number of nodes for running the network. Either as nodes comes and go, either users have to provision/decomission new/old nodes. So even if nodes are running and are considered bad ones this is not a guarantee that we will have stable number of critical nodes. Because bad ones doesnāt count.
Bad nodes can no longer earn, so people are incentivised to get good nodes earning, and keep them earning to work their way up the leaderboard and stay there, to get the most rewards.
If you stop earning, then you will be overtaken, and your share of rewards will go down.
We may also consider promoting people between waves, too, if there are some that drop out from Wave 1 without earning for example. But we will see how it goes.
9 Likes
Remember there will be some who do not wish to give out any information in order to be in the beta rewards program, but still run nodes.
Also there will be people running nodes to earn beta tokens so they can upload data and wish that the data will remain to launch. This is more true probably for later betas when that chance of data surviving gets higher and higher. (that is no restarts of network for surviving)
3 Likes
This sounds like you could increase your share by creating multiple IDs and ensuring each has nodes on the board.
Two IDs doubles your share, three IDsā¦ etc, by dropping nodes for IDs that have made the cut and starting nodes for IDs that havenāt yet.
Maybe itās marginal but will that stop people and does it matter? 
1 Like
Sure i am running nodes constantly for three weeks, and some of them gives errors and are up but no earnings and vdash says that there is some error with the node connection or sth. In that case earnings for that ābadā node will perish? Doesnāt matter if the node runs for let say 6months or year with earnings prior the node goes bad?
I thought wave 1 was for OGās. Is letting others in like this not against the ethos.
May as well have it unlimited then.
1 Like