Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 1487. (Read 2761645 times)

newbie
Activity: 56
Merit: 0
Working on the math behind the voting system.

What variables do you think should be included to determine voting power?

So far I have

(This isn't in any known language, just organized in a way that people should be able to understand)
Code:
variables that are added to vote weight

account size
account age

Hypothetically let
lastblock ==1400
account creation[0]== 1400
account creation[1]== 700
account creation[2]== 100

accountSize[0]== 1,00,000
accountSize[1]== 500,000
accountSize[2]== 250,000

Let relativeAge = (lastBlock) / (accountCreation) '

therefore : relativeAge[0]= 1
relativeAge[1]= 2
relativeAge[2]=14

Let fairWeight = (accountSize)^(1/3)

therefore : fairWeight[0]= 63
fairWeight[1]= 51
fairWeight[2]=41

votingPower = (relativeAge)*(fairWeight)

votingPower[0] = 63
votingPower[1] =  102
votingPower[2] = 574
hero member
Activity: 840
Merit: 1002
Simcoin Developer
Well, if it's only going to take that long then I probably shouldn't bother; http://nxtra.org/voting/add.php (unfinished...)

Hey, that's looking good!

--

Can we read somewhere about this built-in voting system? If it's good then there is indeed no point in building a site.
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
ill have to think about it for a bit. im certain it would work if you could hide how much was being donated to each address. but if that information was public and being monitored by the participants in real time fraud may still creep its way in no matter how large x was.

I appreciate the thought exercise (and have to sleep now) but I do think when we consider the real potential benefits of Nxt and other such platforms are we have to try and rethink some of the basic ways we do things.

We are never going to 100% stop corruption but if we make it expensive enough in an environment that means that your input amount gets distributed to others evenly then I think we might get a lot better situation than we do currently.
legendary
Activity: 1722
Merit: 1217

not much of an exchange. I wouldnt trust them at this point.

why wouldnt you trust them?
hero member
Activity: 840
Merit: 1002
Simcoin Developer
I can code a client by the end of today for macs.

Ok. Let me check my schedule...

20th - Implement mining in Lakshmi
21st - Test JS-implementations of NRS crypto algo, deploy NRS with Asset Exchange to the testnet
22nd - Resolve some issues assigned to me in Jira
23rd - Implement transaction handling in Lakshmi
24th - Review Account Control code
25th - Fix bugs in Account Control code
26th - Day-off

Well, I could do VS review on 26th, then bug fixes and testing...

Could you also post things like this more often? Smiley

I mean, we're basically in the dark what devs are doing...
legendary
Activity: 1722
Merit: 1217
So for example you may say: A1 is spend on alice for marking, A2 is spend on bob for marketing, and A3 is spend on charlie for marketing. B1 is spend on nate for development, B2 is spend on frank for development, and B3 is spend on jim for development? Asside from being a little bit sexist, is that something like what you are talking about?

Yes - this is the basic idea - so people are voting whether to spend on "marketing" or "development" but who will actually *get* the funds for either choice would be a random choice of the winning "side" (the randomness could be based upon timestamps or something else blockchain related such as hashes).

So if you are "Alice" then spending a huge amount of NXT may guarantee that A wins the vote but it doesn't at all guarantee that *you* win the vote.


ill have to think about it for a bit. im certain it would work if you could hide how much was being donated to each address. but if that information was public and being monitored by the participants in real time fraud may still creep its way in no matter how large x was.
sr. member
Activity: 336
Merit: 250
AKA jefdiesel

not much of an exchange. I wouldnt trust them at this point.
legendary
Activity: 1120
Merit: 1000
I can code a client by the end of today for macs.

Ok. Let me check my schedule...

20th - Implement mining in Lakshmi
21st - Test JS-implementations of NRS crypto algo, deploy NRS with Asset Exchange to the testnet
22nd - Resolve some issues assigned to me in Jira
23rd - Implement transaction handling in Lakshmi
24th - Review Account Control code
25th - Fix bugs in Account Control code
26th - Day-off

Well, I could do VS review on 26th, then bug fixes and testing...

I noticed someone squatted on Lakshmi  Sad    

Edit: TODAY even...Squatters  Undecided

It's someone who is a regular here. I suspect someone out of the top "30" guys here.
legendary
Activity: 2184
Merit: 1000
Yesssss - can't wait until 21st. I want to test the asset exchange. Would be fun enough to forget all the voting and funding discussion for a while.

Then u should read Asset Exchange APIs. We don't have a client yet.

there is something in the works...
legendary
Activity: 2142
Merit: 1010
Newbie
Yesssss - can't wait until 21st. I want to test the asset exchange. Would be fun enough to forget all the voting and funding discussion for a while.

Then u should read Asset Exchange APIs. We don't have a client yet.
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
So for example you may say: A1 is spend on alice for marking, A2 is spend on bob for marketing, and A3 is spend on charlie for marketing. B1 is spend on nate for development, B2 is spend on frank for development, and B3 is spend on jim for development? Asside from being a little bit sexist, is that something like what you are talking about?

Yes - this is the basic idea - so people are voting whether to spend on "marketing" or "development" but who will actually *get* the funds for either choice would be a random choice of the winning "side" (the randomness could be based upon timestamps or something else blockchain related such as hashes).

So if you are "Alice" then spending a huge amount of NXT may guarantee that A wins the vote but it doesn't at all guarantee that *you* win the vote.
sr. member
Activity: 308
Merit: 250
I can code a client by the end of today for macs.

Ok. Let me check my schedule...

20th - Implement mining in Lakshmi
21st - Test JS-implementations of NRS crypto algo, deploy NRS with Asset Exchange to the testnet
22nd - Resolve some issues assigned to me in Jira
23rd - Implement transaction handling in Lakshmi
24th - Review Account Control code
25th - Fix bugs in Account Control code
26th - Day-off

Well, I could do VS review on 26th, then bug fixes and testing...

Well, if it's only going to take that long then I probably shouldn't bother; http://nxtra.org/voting/add.php (unfinished...)
legendary
Activity: 2184
Merit: 1000
I can code a client by the end of today for macs.

Ok. Let me check my schedule...

20th - Implement mining in Lakshmi
21st - Test JS-implementations of NRS crypto algo, deploy NRS with Asset Exchange to the testnet
22nd - Resolve some issues assigned to me in Jira
23rd - Implement transaction handling in Lakshmi
24th - Review Account Control code
25th - Fix bugs in Account Control code
26th - Day-off

Well, I could do VS review on 26th, then bug fixes and testing...

I noticed someone squatted on Lakshmi  Sad    

Edit: TODAY even...Squatters  Undecided
newbie
Activity: 56
Merit: 0
I can code a client by the end of today for macs.

Ok. Let me check my schedule...

20th - Implement mining in Lakshmi
21st - Test JS-implementations of NRS crypto algo, deploy NRS with Asset Exchange to the testnet
22nd - Resolve some issues assigned to me in Jira
23rd - Implement transaction handling in Lakshmi
24th - Review Account Control code
25th - Fix bugs in Account Control code
26th - Day-off

Well, I could do VS review on 26th, then bug fixes and testing...

That actually works perfectly for me, I have the 26th off too.
sr. member
Activity: 602
Merit: 268
Internet of Value
I can code a client by the end of today for macs.

Ok. Let me check my schedule...

20th - Implement mining in Lakshmi
21st - Test JS-implementations of NRS crypto algo, deploy NRS with Asset Exchange to the testnet
22nd - Resolve some issues assigned to me in Jira
23rd - Implement transaction handling in Lakshmi
24th - Review Account Control code
25th - Fix bugs in Account Control code
26th - Day-off

Well, I could do VS review on 26th, then bug fixes and testing...

Yesssss - can't wait until 21st. I want to test the asset exchange. Would be fun enough to forget all the voting and funding discussion for a while.
legendary
Activity: 1722
Merit: 1217
on second thought you would still need to craft the incentives right either way because a gamer could in theory purchase votes from stakeholders.

But once again if the vote is only for A or B rather than A1..x and B1..x then buying those votes are no better than using your own NXT.

The idea being that the choice of A1...x or B1...x would be entirely *random* (not a specific choice) so the specific choice that has been voted on is just the general idea of either A or B.

Hope this makes sense (yes corruption could still happen if all the A's or B's colluded and that would have to be another issue to be considered).


I thought I understood what you were saying before. now i am not so certain Undecided

So for example you may say: A1 is spend on alice for marking, A2 is spend on bob for marketing, and A3 is spend on charlie for marketing. B1 is spend on nate for development, B2 is spend on frank for development, and B3 is spend on jim for development? Asside from being a little bit sexist, is that something like what you are talking about?
newbie
Activity: 14
Merit: 0
Hello Guys,
I published the first alpha version of my Android App "NXT Watcher".
See https://nextcoin.org/index.php/topic,2588.0.html for further details and install instructions.

Screenshot to get a first impression of how it looks like:
https://dl.dropboxusercontent.com/u/1304372/NXTWatcher/Screenshots/NXTWatcher2.png

I need a lot help testing on different devices, especially Gingerbread and Honeycomb!

So if you own an Android device, follow the link above and please provide some feedback Smiley

Additionally there is a 1k bounty for providing a good looking, Android-ready laucher logo for the app -- two guys working on it already.


And now the obligate NXT signature  Grin :
If you like it, you are welcome to donate a few NXT to keep me motivated Smiley
6887853321138092071

Newsflash!

NXT Watcher version 0.1.4. is out!

Not a groundbreaking release, but I added a few new features.
v0.1.4, 20.01.2014:
  • Added refresh button to the chart view, thus no more need to re-download data each time (except android closes the app).
  • Added free-vertical zoom/move mode.
  • Implemented a smart vertical grid instead of the fixed grid.
  • Fixed a bug that caused the app to crash if it was closed by android and restarted using the app history.
legendary
Activity: 1092
Merit: 1010
so r u saying he would have to invent TF himself to compete?

Yes.  Grin

 Grin  its a feature

Edit: features don;t have to be open source do they...just like HIVE or DNA

Sorry but I just stumbled upon this while preparing my summary.

Nearly blew coffee through my nose laughing.

I had never realised it and it's bloody hilarious  Grin
legendary
Activity: 2142
Merit: 1010
Newbie
I can code a client by the end of today for macs.

Ok. Let me check my schedule...

20th - Implement mining in Lakshmi
21st - Test JS-implementations of NRS crypto algo, deploy NRS with Asset Exchange to the testnet
22nd - Resolve some issues assigned to me in Jira
23rd - Implement transaction handling in Lakshmi
24th - Review Account Control code
25th - Fix bugs in Account Control code
26th - Day-off

Well, I could do VS review on 26th, then bug fixes and testing...
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
on second thought you would still need to craft the incentives right either way because a gamer could in theory purchase votes from stakeholders.

But once again if the vote is only for A or B rather than A1..x and B1..x then buying those votes are no better than using your own NXT.

The idea being that the choice of A1...x or B1...x would be entirely *random* (not a specific choice) so the specific choice that has been voted on is just the general idea of either A or B.

Hope this makes sense (yes corruption could still happen if all the A's or B's colluded and that would have to be another issue to be considered).
Jump to: