Topic: [ANN] NoirShares UPDATE REQUIRED Advanced Features✔, Unique PoW✔ - page 31. (Read 69978 times)

✔

i am working on a possible solution, just give me an hour.

The issue is simply that some users have not updated the the new wallet, i am using remote access to fix the issue but it's taking time, give me an hour to come up with a solution.

Wait for it guys, don't panic.

It's all getting sorted soon.

We need to see more nodes. Anyone have a node list for Protocol version 60009 (v0.2.2.1-alpha)?

PLS LET'S FOCUS ON THE SERIOUS THINGS.... WALLET v.0.2.2.1 WONT SYNC....

did you read this part

I take voting seriously, if you call that narrow minded, well...
If you implement a voting system, that has to be based on trust. I just show you what you have to be ahead of if you do not think in advance about how you want to implement that. You can take my advice or leave it.
The problem is that I ask for a technical explanation, and you are only throwing in about 3 lines that do not explain anything. So if I call that simplistic it is because you are not trying to explain.

increasing the vote size from 0.001 to 0.1 still conts as a single vote, and multiple votes using the send many function are treated as one vote. most would try to have a script that creates new addresses and sens sya 1 coin to the address then vote with those addresses, this was encountered in the first implementation and was countered by considering what % of the chain is held by voting addresses, this means that even a thousand micro votes will not unbalance the scale since votes from actual holders will counter the effect, essentially, that person will just be losing themselves a ton of coin.

One issue i am aware of is a 51% attack, where in reality if a single person holds more voting power than the rest of the voters then can easily manipulate the system, however , based off information from the snapshot, this is not likely, and any person willing to buy up the required coin to do this would meet the same constraints as trying to 51% PoS.

I'd imagine sending the token transaction indicates that the sending address votes for the receiving address with its remaining stake, so Sybil attacks nor voting for multiple people are not possible.

I could be wrong.

Edit: Or just slow.

I'm mobile so i cant say too much, but let me correct you.

So user A votes themselves multiple times. the question becomes what % does this user control of the total money supply? If user A votes for himself and controls 10% of the money supply, but other users B-Z vote for user a1 while they control 10% as well, then user a1 gets elected.

The website is not meant to replace the block  chain, it is meant to provide voting instructions in a clearer manner than these posts on the forum. You did ask how it works right? We also use the website to show information of which candidates address has how many votes and who currently occupies the office. Later on, this will likely be worked into the client, but for now, you will be referred to a website to get the stats.

Does it matter that a person has voted multiple times? In this case it does not because we do not only count votes, we also consider what weight of the chain is controlled by the voters. a 0.001 vote from an address holding 0.1 coins is worth much less than a 0.001 vote from an address with 10 NRS.

We can always have a print out of who voted, and votes in NRS are for the community, not just GF, the GF has exclusive voting rights in NG but not in the DACs themselves.


Usually, it is best to try something out before trying to poke holes in it or to outright dismiss it, it's a bit narrow minded. And "simple" usually has better results with regard to software in comparison with complicated solutions.

I'm not saying there aren't flaws, there are obviously issues with every system, but lets try to use the boat, not put cannon balls through the hull.

I am sorry to be negative, but that system cannot work. It is very simplistic and fraud will be imminent.
1. I can send multiple tokens (coins?) to my own address, each is one vote, so then I will pay for my own votes and get chosen.
2. A website cannot replace the blockchain, in fact has nothing to do with the blockchain other than that you can represent information from the blockchain on it
3. People can vote multiple times for the same person
4. How do I know who voted? In the GF I guess that other GF holders vote, but not other people, how to prevent that?

These will  likely be done on the website. We really need it updated

For now, you have to be voted in manually.

To Vote

send your candidate a small token maybe 0.001 NRs to signify your support, the more votes that person gets, the higher the chances they will succeed.

Once we get a web dev, we'll get the website updated.

As for syncing, our servers at centarra are not useable at the moment, i am considering options.

I meant hypothetical. I don't think anyone would vote for me now
But if I would want to, how do I get the votes? Do people just pay some NRS in that address or will there be "yes" or "no" coins? And how will we know I do not vote for myself? I am interested in a more technical explanation of the underlying technology (maybe a whitepaper?)

for which position?? I look at evening

How will the actual voting go in that way? I generated the address, have found people that want to vote for me, and then?

It's time to sleeeeeeeeeeeeeeeeeeeeeeeeeep!!

Barwizi is now Jackie Mason.

But i think github is actually easier, all you do is click "new issue" say your piece and go, maybe check back later after a few hours and you should see a response, maybe even a quick fix.