Topic: NXT :: descendant of Bitcoin - Updated Information - page 1638. (Read 2761645 times)
Just one suggestion, concerning voting.
When making polls concerning decisions about NXT, POS should have the biggest weight.
Anything else, like Eurovision, could indeed be weighted per individual account. And then it would be a nice feature to be able to share transaction revenues with Eurovision organisers.
And, yes, the song festival is just an example.
Can't. Login didn't work. Asked to reset password, still waiting on email. Any chance of having thread on nxtcrypto?
My brain will blow up if I try to memorize one password more.
What raw data do you have from zombie attacks?
I could create a predictor for prior attacks as a starting point
James
In my mind a true democratic system would be each person has an equal say regardless how much you own (NXT in this case).
"Decentralized" doesn't imply "democratic" i think. Comments?
That's a fair point.
In my mind a true democratic system would be each person has an equal say regardless how much you own (NXT in this case).
"Decentralized" doesn't imply "democratic" i think. Comments?
Can't. Login didn't work. Asked to reset password, still waiting on email. Any chance of having thread on nxtcrypto?
My brain will blow up if I try to memorize one password more.
bit777 asks about Nxt Daemon https://bitcointalk.org/index.php?topic=183798.new#new
Ah thank you ! I was asking for help from devs but no one is moving.If bit777 add Nxt this will be the biggest promotion ever.
Pin
Just helping him understand how the client work and how to implement it to his casino (considering the high traffic/transactions).
The Nxt client is very different from BitcoinQt.
This is a main problem we see also appear with exchange, people dont know how to implement it in they environment. Can we have somebody other than core DEVs JL and CfB to help people with this?
who is willing to do this?
Pin
repost:
This is a main problem we see also appear with exchange, people don’t know how to implement it in they environment.
Can we have somebody other than core DEVs JL and CfB to help people with this?
Do we have someone other than core devs that could explain how NXT works and help them setup business; this is also in the interest of NXT
This should be documented somewhere, and be made the reference people are pointed to.
All the NXT APIs are in here http://www.thenxtwiki.org/wiki/For_Programmers. So the general information is there for everyone and if they have specific questions they can contact Cfb
Exactly what i neede, thx!
bit777 asks about Nxt Daemon https://bitcointalk.org/index.php?topic=183798.new#new
Ah thank you ! I was asking for help from devs but no one is moving.If bit777 add Nxt this will be the biggest promotion ever.
Pin
Just helping him understand how the client work and how to implement it to his casino (considering the high traffic/transactions).
The Nxt client is very different from BitcoinQt.
This is a main problem we see also appear with exchange, people dont know how to implement it in they environment. Can we have somebody other than core DEVs JL and CfB to help people with this?
who is willing to do this?
Pin
repost:
This is a main problem we see also appear with exchange, people don’t know how to implement it in they environment.
Can we have somebody other than core DEVs JL and CfB to help people with this?
Do we have someone other than core devs that could explain how NXT works and help them setup business; this is also in the interest of NXT
This should be documented somewhere, and be made the reference people are pointed to.
All the NXT APIs are in here http://www.thenxtwiki.org/wiki/For_Programmers. So the general information is there for everyone and if they have specific questions they can contact Cfb
Nice one pal ill check this out :-D
bit777 asks about Nxt Daemon https://bitcointalk.org/index.php?topic=183798.new#new
Ah thank you ! I was asking for help from devs but no one is moving.If bit777 add Nxt this will be the biggest promotion ever.
Pin
Just helping him understand how the client work and how to implement it to his casino (considering the high traffic/transactions).
The Nxt client is very different from BitcoinQt.
This is a main problem we see also appear with exchange, people dont know how to implement it in they environment. Can we have somebody other than core DEVs JL and CfB to help people with this?
who is willing to do this?
Pin
repost:
This is a main problem we see also appear with exchange, people don’t know how to implement it in they environment.
Can we have somebody other than core DEVs JL and CfB to help people with this?
Do we have someone other than core devs that could explain how NXT works and help them setup business; this is also in the interest of NXT
This should be documented somewhere, and be made the reference people are pointed to.
I was simply requesting creating a poll to summarize what has been suggested... nothing more.
Perfect solution for Voting app:- you run it
- it downloads latest blockchain
- it extracts newest votings
- it shows you that votings
- you do some left-mouse-button clicks on checkboxes
- you click "submit"
- you go to sleep (as C-f-B recommends)
Democracy on the march!
+1, except CFB "sleep" is code for "testing major bugs". Seriously though, really like the idea of a voting section in client, based on your public key block height and voting topic block height, click boxes that are up for vote and done.
Perfect!
I was simply requesting creating a poll to summarize what has been suggested... nothing more.
Perfect solution for Voting app:- you run it
- it downloads latest blockchain
- it extracts newest votings
- it shows you that votings
- you do some left-mouse-button clicks on checkboxes
- you click "submit"
- you go to sleep (as C-f-B recommends)
Democracy on the march!
+1, except CFB "sleep" is code for "testing major bugs". Seriously though, really like the idea of a voting section in client, based on your public key block height and voting topic block height, click boxes that are up for vote and done.
I was simply requesting creating a poll to summarize what has been suggested... nothing more.
Perfect solution for Voting app:- you run it
- it downloads latest blockchain
- it extracts newest votings
- it shows you that votings
- you do some left-mouse-button clicks on checkboxes
- you click "submit"
- you go to sleep (as C-f-B recommends)
Democracy on the march!
+1, except CFB "sleep" is code for "testing major bugs". Seriously though, really like the idea of a voting section in client, based on your public key block height and voting topic block height, click boxes that are up for vote and done.
I was simply requesting creating a poll to summarize what has been suggested... nothing more.
Perfect solution for Voting app:- you run it
- it downloads latest blockchain
- it extracts newest votings
- it shows you that votings
- you do some left-mouse-button clicks on checkboxes
- you click "submit"
- you go to sleep (as C-f-B recommends)
Democracy on the march!
going to a size-of-wallet voting scheme is plain MEDIEVAL - sure this has been brought up here before, but how about this:
Thanks everyone for the great ideas and discussion about voting, it's what I was hoping for
I agree with the above statement and that's why I proposed what I did. My concept of voting is only based on the American democratic process. So that's why I proposed how I did.
I am curious that no one commented about the account restrictions based on blockchain height I mentioned: If a vote was proposed and went public on block height of 45,000 an account would have to have existed for 'X' number of blocks before the block containing the vote (i.e, you have to be 18yrs old to vote in the U.S.), we could take it a bit further and say that that account would also have to NXT in it for a certain amount of blocks before the vote as well (like the 1440 blocks before you can forge). This could surely cut down on the amount of gaming no?
This makes a lot of sense on so many levels. Not only would it prevent gaming the system from large holders, but it prevents people from buying large sums of NXT (for a short period) to try to manipulate the vote. The more I think about this approach, the more it grows on me.
This is a great idea. A forging account with public key will be able to get one vote. Or as mentioned above, only an account that existed at a particular block height would get to vote on the particular topic. That way you could go back in time and put up a vote for a smaller group of founders, etc...
+1 I like the idea. But if you go back to the first block, there aren't anyone else to vote except BCNext or anyone else ?
Well haha of course if you go back to the Genesis block
But it would an arbitrary number. Need to be an account with a public key for at least the previous 10,000 blocks when the vote block come up. Or whatever.....One idea is that when a voting issue is raised and up for public debate we can mark the block at that time and only accounts "older" than that mark can vote on that issue.
Furthermore, I think setting up a vote should cost a certain amount of NXT to avoid spamming.
Yes, exactly, that would be a default (topic submitted at current block height), but the person could also choose at which block they want to issue the vote topic. I think the vote topic should cost at least 1 Nxt of course. Really think we are on to something here, seems like a fair system. Perhaps we could put it up for vote in the Nxtcrypto forum then forward result to JLP for implementation, or whomever is responsible.
Not everyone has all day to ready through endless posts, I was simply requesting creating a poll to summarize what has been suggested... nothing more. No decisions made based on a poll. Anyway, that's my 2 cents... it's decentralized, do as you please.
I understand the frustration of reading through this enormous topic - we just need to work out a way to do things that isn't easily screwed by gamers.
Your input is appreciated (and yes - "the revolution will not be centralised")!
Hash was not the maker, it was a friend of him and he received 1000 NXT for it, but I think there is concensus in the community to give him 4000 NXT more.
IMHO, forum polls is useless and meaningless.
Note: this opinion is for polls only, not for Voting System.
Note: this opinion is for polls only, not for Voting System.
Agreed - I am not against the Voting System idea but I am strongly against any "forum polls" (especially Bitcointalk ones).
I wasn't referring to creating a poll in this cesspool called Bitcointalk, I meant on the community forums. Yes, people will game the system... I'm suggesting simply checking the pulse, the same way we've handled other community actions in the past.
I think you need to carefully think how to do this as such things are very easily gamed.
Not everyone has all day to ready through endless posts, I was simply requesting creating a poll to summarize what has been suggested... nothing more. No decisions made based on a poll. Anyway, that's my 2 cents... it's decentralized, do as you please.
Simpler seems better to me. The more requirements, the more complicated, the longer to get it working right.
I think there will be (is?) a bidding process for space in the forged block. As long as the bidding is based on NXT per byte used in the blockchain, then it won't matter if it is for transaction, AM, AS, etc. Mission critical items will need to bid higher, best efforts can use minimum fees, etc. I think it makes sense for the client to dynamically change the fee paid if something doesn't get into the blockchain. The core protocol should use some sort of universal metric to determine what goes in or out, NXT/byte seems logical.
There might be some EBS (emergency broadcast system) payloads that always make it, but not sure how to make it spamproof.
I think there will be (is?) a bidding process for space in the forged block. As long as the bidding is based on NXT per byte used in the blockchain, then it won't matter if it is for transaction, AM, AS, etc. Mission critical items will need to bid higher, best efforts can use minimum fees, etc. I think it makes sense for the client to dynamically change the fee paid if something doesn't get into the blockchain. The core protocol should use some sort of universal metric to determine what goes in or out, NXT/byte seems logical.
There might be some EBS (emergency broadcast system) payloads that always make it, but not sure how to make it spamproof.
I'm all for simplicity.
Regarding transaction size: yes there will be a bidding war, and the forging node has an incentive to consider transaction size when deciding which transactions to include and which to exclude. It's aim is to push a block which includes whatever collection of transactions maximises its own fees.
But it has no incentives to take TTL into account, and so unless the network imposes some hard rule with arbitrarily-chosen fees (e.g. 0.0001 nxt per day) why would a client not always opt for the maximum TTL?
IMO the protocol should be modified to allow the network to enforce a transactionFee/transactionBiteSize ratio, rather than let a forging node use whichever transactions maximize its fees.
I say forget about TTL. Let it sit till checkpoint, like NXT transfers do. Just enforce a transactionFee/transactionBiteSize ratio.
Unfortunately I believe this is much harder said than done.
Edit: may be easiest to enforce a 1-size-fits-all strategy to prevent spamming/bloat: Determine the smallest-transaction-type-size-in-bytes and set its fee to X, then find out the total transaction size of the largest possible AM and find the byte size multiplier between the 2, and multiply the fee of the smallest-transaction-type-size-in-bytes by that multiplier to determine the fee for any sized AM
(sorry - but I think that "polls" in forums are about the most stupid thing I've ever come across - I don't have polls in CIYAM Open for this exact reason)
Agreed.IMHO, forum polls is useless and meaningless.
Note: this opinion is for polls only, not for Voting System.
Jump to: