What is the size limit of a single message?
1000 bytes currently.
so does that mean msg size can be increased?
Yes.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 1688. (Read 2761645 times)
1000 bytes currently.
so does that mean msg size can be increased?
Yes.
What is the size limit of a single message?
1000 bytes currently.
so does that mean msg size can be increased?
is there an API to query that limit (as presumably it might be increased down the track)?
No, someone should add such the request to https://bitcointalksearch.org/topic/nxt-api-2-brainstorming-406839
I see "To the MOON and beyond! NXT will change the world! Forget Bitcoin and the 51% Attack! Alias, Arbitrary Messaging, Asset Exchange, Transparent Mining, Instant Transactions..." message.
http://localhost:7874/nxt?requestType=getTransaction&transaction=7790905943202759516
http://localhost:7874/nxt?requestType=getTransaction&transaction=7790905943202759516
Are you kidding me? I guess you haven't been following NXT development at all, as many people are contributing their time and skills to make NXT better for everyone. Also, you're deluding yourself if you think the "core 20-30" of emunie are not acting out of self-interest (even a tiny bit).
You misunderstand my point. On the contrary, I have followed NXT very closely (every page on this thread, the other forums, the wiki etc etc) and I am very impressed with what the NXT community is doing. I own some NXT and have done very well!
The point I'm making is many here might be tempted to take the events of the last few days with Fuserleer postponing the IPO in response to the repeated FUD and personal attacks on his professional integrity as an indication that emunie is no longer a serious competitor to NXT. I am challenging this idea directly. Fuserleer is honest, and very skilled, and now he's even more determined than he was before to make emunie the best crypto financial system ever.
eMunie has the features and the backing to be THE main contender to fiat currencies after it is launched. The eMunie team IS obviously motivated by self-interest, and financial rewards are part of that, but a large part of that self-interest is also the desire for satisfaction they'll get when emunie becomes a world wide phenomenon, and Fuserleer has been lauded as a genius, and all those who questioned his honesty hide their heads in shame. NXT does not have that X-factor. The BCNext disappearing act is enigmatic, but it doesn't inspire loyalty
What is the size limit of a single message?
1000 bytes currently.
Thanks - and is there an API to query that limit (as presumably it might be increased down the track)?
Depreciating voting weight may not be a perfect solution, but I think it will work better than the simpler options.
Could be true.
What is the size limit of a single message?
1000 bytes currently.
I did send the transaction, but didn´t receivre any confirmation or tx number..
Set pushThreshold to higher value.
What is the size limit of a single message?
CfB, will we get an interface for this like we did for aliases? Or will it be handled on the client side?
Client side. Someone could create a small html-file and send to Jean-Luc.
And how can the recipient see the message?
http://localhost:7874/nxt?requestType=getTransaction&transaction=10485209809271728163
I did send the transaction, but didn´t receivre any confirmation or tx number..
Repost from https://forums.nxtcrypto.org/viewtopic.php?f=2&t=530:
Thinking about vote weighting here:
One of the major issues with a voting system is deciding how to weight the votes.
As examples:
One NXT account = one vote will inevitably lead to the creation of zillions (or lots) of sock-puppet accounts purely for voting. Giving an account with 2 NXT the same voting weight as one with 2,000,000 is also unfair on larger stakeholders who have much more invested in NXT than the smaller accounts.
...
My proposal is:
One NXT = one vote, with depreciation of voting weight from a certain point.
...
Only problem I can see is that if a whale does want to unfairly influence voting they could split up his/her/its NXT holdings over multiple smaller accounts. However, this seems like a lot of work and would be visilble in the blockchain, if anyone cared to check.
Thinking about vote weighting here:
One of the major issues with a voting system is deciding how to weight the votes.
As examples:
One NXT account = one vote will inevitably lead to the creation of zillions (or lots) of sock-puppet accounts purely for voting. Giving an account with 2 NXT the same voting weight as one with 2,000,000 is also unfair on larger stakeholders who have much more invested in NXT than the smaller accounts.
...
My proposal is:
One NXT = one vote, with depreciation of voting weight from a certain point.
...
Only problem I can see is that if a whale does want to unfairly influence voting they could split up his/her/its NXT holdings over multiple smaller accounts. However, this seems like a lot of work and would be visilble in the blockchain, if anyone cared to check.
Statement 1: there will be created zillions of sock puppet accounts
Statement 2: Creating hundreds of sock puppet accounts seems like a lot of work
?
Good point.
The difference is that with one account = one vote anyone can generate 1000's of sock puppets and get more voting power. Almost no NXT needed.
With a depreciating vote weight only whales will benefit from having multiple accounts, and they will have to not only create the puppets, but split up their NXT holdings into the puppet accounts to get extra voting power, which I'm not sure will happen on a large scale. Whales will still have lots of voting power anyway, and I don't think they will be willing to split up a 1 megaNXT account into, for example, 100 x 10kNXT accounts, just to get some extra voting power.
I might be wrong, but I can see very big problems with both one account = one vote and one NXT = one vote.
Depreciating voting weight may not be a perfect solution, but I think it will work better than the simpler options.
And how can the recipient see the message?
http://localhost:7874/nxt?requestType=getTransaction&transaction=10485209809271728163
CfB, will we get an interface for this like we did for aliases? Or will it be handled on the client side?
That's weird but account with secret phrase "123" had 1 NXT on the balance and I suddenly sent a message!
To the account with the number 0?
And how can the recipient see the message?
http://localhost:7874/nxt?requestType=getTransaction&transaction=10485209809271728163
That's weird but account with secret phrase "123" had 1 NXT on the balance and I suddenly sent a message!
And how can the recipient see the message?
Jump to: