reput open sourcing motion because of : Error in motion counting method found
Modified the parking rates because:
- the buy liquidity has improved (at the time of this writing 50k, previously 20k)
- i mistook annual rates and rates for specific periods.
Previously I intended 5% of return rate for 1 month.
I now reduce that to 2% and I extend the reward period from 1.5 months to 3 months.
Voting for the final proposal for continuing developments on Android wallet from cybnate.
Removed 387e7f6ffc7d69311ac2e1d0ca7cd98d4ecbdea9 (because Proposal for Transfer of Liquidity from Existing Grant Reserves passed)
Added ed7b9fc65dc4e9d9acad61e528420c2690f599d2 (motion to end LPC operations of KTm, Jamie and NSR sales of Jordan Lee)
- Removed BPuTsT9FiDLSDihCHxzaieVXoksXqoffHk, 1 (because the proposal for small liquidity by creon passed)
- Added BMKCHYVwRpoAS1iB5iiqqudYy7USctAbkd, 1 (New grant address for continuing liquidity operations)
- Added BRTkmQ7Fz6vkg48iadLD1WfzmF7vech22v, 1 (Bittylicious liquidity provision)
Park rates : no change
Added: 876e10611809f3a90f2216fb61f107d3b7c9c469 : NSR auction
I’m subscribed to this datafeed right now without any political reasons. I don’t always have immediate access to my NSR miner so it’s better if it’s subscribed to a trusted representative. Is there any means to find out how many nushareholders use datafeeds and how much weight do these feeds have in the overall voting?
Great questions. Probably better to ask @sigmike .
No but someone could write a program that frequently downloads the data feed and count how many blocks are voting for the same thing. It would have to separate the vote parts because people can for example update only motions from the data feed.
Would it somehow harm the network if each datafeed had a random identifier that is not actually a hash of a motion but instead carries the purpose to differentiate the datafeed from the others in the block chain by its weight? For example, in the case of ‘cryptog’, we would convert it to hex which is 63727970746f67 and append zero byte padding to the end getting this: 63727970746f6700000000000000000000000000.
Now cryptog’s data feed would include this arbitrary identifier and a bot could be built that would monitor the block chain and record the proportion of cryptog’s datafeed in the overall voting. What do you think?
Yes this would work, the blockchain has no idea which motion is real an which not. However, note that anyone else could also add this motion just to fake the statistics.
Yes but are all the motions going to the block or just one at a time? If all the motions go to the block then we could differentiate “fake statistics” from real ones programmatically. A real datafeed vote would include all the motions of the representative including their identifier.
Its all motions, but also the data feed provider may change the content of the feed - theoretically on each block (which could even make sense to model a weighting of votes). So from the set of motions itself you can not be 100% sure about the origin.
I would disagree with it. If at any point of time we have a set of motions that includes the fingerprint of a representative then we can compare that set with the representative’s motions as given in their datafeed URL. This means that solely from the block chain we wouldn’t be able to reconstruct the history of the proportion of the datafeed in overall votes but we would be able to get the proportion at the current moment. Seeing the current state is better than having no knowledge at all. The history of the representative’s votes could be logged by means outside the block chain.
Ah got it. So you want to compare it to the live data. Yes that would certainly work! In this case I guess the data feed provider should ideally always add a random motion.
Yes, adding a salt to the list of motions seems like a good idea.
deleted 876e10611809f3a90f2216fb61f107d3b7c9c469 because it passed.
There are some issues:
- privacy: the data feed consumer may not want to reveal he’s using this data feed
- security: if it’s clear a data feed has a large consumer base then it becomes a target
The data feed system was designed with the goal that you can’t differentiate someone voting by himself from someone using a data feed. This is not completely achieved but adding an identifier would be a step in another direction.
Ok that’s a good point, I guess. But from the attacker’s point of view, isn’t it possible to approximate a data feed’s popularity anyway? If that can be done then it’s easy to still target popular data feeds. Does this secrecy really solve a problem or is it just an easy obstacle for the attacker?