I need suggestion for iNxt (iPhone app) what di you want to see next?
Landscape mode
Topic: NXT :: descendant of Bitcoin - Updated Information - page 678. (Read 2761645 times)
Landscape mode
Thank you dear Mr. Stackeholder, what a generous move!! 
This is so cool!
I think we would all appreciate if more big stakeholders did what 7017504655955743955 has done today, especially top 50 accounts which are all from 5 million to 50 million NXT.
To them to spread 100,000 like 7017504655955743955 did would be nothing but this would show even more greatness of this community and this project.
In the end, doing something like this would just raise the worth of NXT in a long run and paradoxically their main stash would be worth much more than this little part that they have possibly disbursed to this hard working community.
Just something to think about.
Once again BRAVO for 7017504655955743955!!
It seems everyone received that except me
What is the status of our discussion regarding:
- incentive for running a node vs. running a node and trying to forge and running a node and actually forge
- 51% attacks, TF, penalty
- a world without fees: spam prevention possible?
- incentive for running a node vs. running a node and trying to forge and running a node and actually forge
- 51% attacks, TF, penalty
- a world without fees: spam prevention possible?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Release 0.8.2e
http://download.nxtcrypto.org/nxt-client-0.8.2e.zip
sha256: cd0ceda97fd1752d6fa2877bd4a343570f8b62ae1de2009cd7688087c619c3d4
Change log:
Mostly minor fixes for problems reported with 0.8.1e.
Fixed hallmark string in json peer info.
Improved Logger, added removeListener methods.
Don't set Content-lenght headers when using XMLHttpRequest to send POST
requests.
Added jetty-security jar.
Moved worker_sha256.js to tools.
Also add random mynxt.info nodes to default wellKnownPeers.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJTDNiwAAoJEFOhyXc7+e2A1lYQANcxMSCbyzTkzYKLwGFtphxe
3gtZfbN+PW/KZrvp3am4pRKiP2HsEVxKzk8UjC2dRUYkbNKc/K79ck9o+qkIprqF
+oOnj5VgjT1LmUrBg0sQrScxyDELLmF4A89dk4WFre+JRdGYManLdEsCRfbCf2jC
uOwhIrtej5gEP8FMj6NG2UiY59xdc2UMtSdGYUaSsYZhQNjS6514LQPtwlKGXUfh
bZNqaRut4ZoegbDEtNfVJOI+BzZB3OOkReEl371YeCBSkhAkboZm1Zhzi+oLwni0
3nENhzCk0LurufoBIzFW/sKr0HyMhJYAXfSKsGRb3blJO1KeVNIStjAwWJgcqcNF
agyL/5aciBMvTj6eu6wl/TqtB1pSwQzks3DPfUT79vAlECkb+5JnYQxFtuseKV44
IaSRUMNXfcfn2LjHU7Pz1Hrhfmc525fUHcD1V0S8ANVlb6Ig0X0snxPCSli2SmQL
atABusbXjaFxDRh7bbGTdQGWlu/6cN5AIuNjuDFElrRnmf/ItyxwpHweeEdV3f5j
2dJz8vQ3AJyuTC+hCqUcYgrPGFpEKuknK5T/4uI4yADSmBH6LnOJkG76yNwMugBu
swu5INrushwQZkL4rxmnQMFN+r57VRXy+2hA7bbWW/+G3DPq7DW7SaWi3umyZV61
Obqrmy8qIs1siIy2rmva
=Zg4G
-----END PGP SIGNATURE-----
Hash: SHA1
Release 0.8.2e
http://download.nxtcrypto.org/nxt-client-0.8.2e.zip
sha256: cd0ceda97fd1752d6fa2877bd4a343570f8b62ae1de2009cd7688087c619c3d4
Change log:
Mostly minor fixes for problems reported with 0.8.1e.
Fixed hallmark string in json peer info.
Improved Logger, added removeListener methods.
Don't set Content-lenght headers when using XMLHttpRequest to send POST
requests.
Added jetty-security jar.
Moved worker_sha256.js to tools.
Also add random mynxt.info nodes to default wellKnownPeers.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJTDNiwAAoJEFOhyXc7+e2A1lYQANcxMSCbyzTkzYKLwGFtphxe
3gtZfbN+PW/KZrvp3am4pRKiP2HsEVxKzk8UjC2dRUYkbNKc/K79ck9o+qkIprqF
+oOnj5VgjT1LmUrBg0sQrScxyDELLmF4A89dk4WFre+JRdGYManLdEsCRfbCf2jC
uOwhIrtej5gEP8FMj6NG2UiY59xdc2UMtSdGYUaSsYZhQNjS6514LQPtwlKGXUfh
bZNqaRut4ZoegbDEtNfVJOI+BzZB3OOkReEl371YeCBSkhAkboZm1Zhzi+oLwni0
3nENhzCk0LurufoBIzFW/sKr0HyMhJYAXfSKsGRb3blJO1KeVNIStjAwWJgcqcNF
agyL/5aciBMvTj6eu6wl/TqtB1pSwQzks3DPfUT79vAlECkb+5JnYQxFtuseKV44
IaSRUMNXfcfn2LjHU7Pz1Hrhfmc525fUHcD1V0S8ANVlb6Ig0X0snxPCSli2SmQL
atABusbXjaFxDRh7bbGTdQGWlu/6cN5AIuNjuDFElrRnmf/ItyxwpHweeEdV3f5j
2dJz8vQ3AJyuTC+hCqUcYgrPGFpEKuknK5T/4uI4yADSmBH6LnOJkG76yNwMugBu
swu5INrushwQZkL4rxmnQMFN+r57VRXy+2hA7bbWW/+G3DPq7DW7SaWi3umyZV61
Obqrmy8qIs1siIy2rmva
=Zg4G
-----END PGP SIGNATURE-----
Thanks .
Oh, I also figured out a much easier way for people to be able to test this. When it is ready for testing, just post your DOGE address and I will send you some DOGE for testing along with a deposit address. I will set the withdrawal address to your DOGE address. I believe there is even an online DOGE wallet, so no need to install DOGE-qt. No need to compile any source code. Since the gateway uses the "sender" field in the AM to verify you are the owner of the NXT acct, I dont think it is so easy to spoof gateway_AM packets. Havent really bullet proofed that yet as we need to have basic functionality first.
https://www.dogevault.com/
I just setup a test wallet. If any Nxters here are like me, your Doge-QT client may be out of date (1.4) and needs upgraded to 1.5.2 and the blockchain needs re-indexed, updated etc. The online wallet is slick (nice enough for testing purposes, anyway).
SWARM NEEDED
Here is the reddit post, please everyone sign up at Bittrex.
Go to https://bittrex.com/Account/Register and use SUPPORT_NXT as the invite code.
done. Here is the reddit post, please everyone sign up at Bittrex.
Go to https://bittrex.com/Account/Register and use SUPPORT_NXT as the invite code.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Release 0.8.2e
http://download.nxtcrypto.org/nxt-client-0.8.2e.zip
sha256: cd0ceda97fd1752d6fa2877bd4a343570f8b62ae1de2009cd7688087c619c3d4
Change log:
Mostly minor fixes for problems reported with 0.8.1e.
Fixed hallmark string in json peer info.
Improved Logger, added removeListener methods.
Don't set Content-lenght headers when using XMLHttpRequest to send POST
requests.
Added jetty-security jar.
Moved worker_sha256.js to tools.
Also add random mynxt.info nodes to default wellKnownPeers.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJTDNiwAAoJEFOhyXc7+e2A1lYQANcxMSCbyzTkzYKLwGFtphxe
3gtZfbN+PW/KZrvp3am4pRKiP2HsEVxKzk8UjC2dRUYkbNKc/K79ck9o+qkIprqF
+oOnj5VgjT1LmUrBg0sQrScxyDELLmF4A89dk4WFre+JRdGYManLdEsCRfbCf2jC
uOwhIrtej5gEP8FMj6NG2UiY59xdc2UMtSdGYUaSsYZhQNjS6514LQPtwlKGXUfh
bZNqaRut4ZoegbDEtNfVJOI+BzZB3OOkReEl371YeCBSkhAkboZm1Zhzi+oLwni0
3nENhzCk0LurufoBIzFW/sKr0HyMhJYAXfSKsGRb3blJO1KeVNIStjAwWJgcqcNF
agyL/5aciBMvTj6eu6wl/TqtB1pSwQzks3DPfUT79vAlECkb+5JnYQxFtuseKV44
IaSRUMNXfcfn2LjHU7Pz1Hrhfmc525fUHcD1V0S8ANVlb6Ig0X0snxPCSli2SmQL
atABusbXjaFxDRh7bbGTdQGWlu/6cN5AIuNjuDFElrRnmf/ItyxwpHweeEdV3f5j
2dJz8vQ3AJyuTC+hCqUcYgrPGFpEKuknK5T/4uI4yADSmBH6LnOJkG76yNwMugBu
swu5INrushwQZkL4rxmnQMFN+r57VRXy+2hA7bbWW/+G3DPq7DW7SaWi3umyZV61
Obqrmy8qIs1siIy2rmva
=Zg4G
-----END PGP SIGNATURE-----
Hash: SHA1
Release 0.8.2e
http://download.nxtcrypto.org/nxt-client-0.8.2e.zip
sha256: cd0ceda97fd1752d6fa2877bd4a343570f8b62ae1de2009cd7688087c619c3d4
Change log:
Mostly minor fixes for problems reported with 0.8.1e.
Fixed hallmark string in json peer info.
Improved Logger, added removeListener methods.
Don't set Content-lenght headers when using XMLHttpRequest to send POST
requests.
Added jetty-security jar.
Moved worker_sha256.js to tools.
Also add random mynxt.info nodes to default wellKnownPeers.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJTDNiwAAoJEFOhyXc7+e2A1lYQANcxMSCbyzTkzYKLwGFtphxe
3gtZfbN+PW/KZrvp3am4pRKiP2HsEVxKzk8UjC2dRUYkbNKc/K79ck9o+qkIprqF
+oOnj5VgjT1LmUrBg0sQrScxyDELLmF4A89dk4WFre+JRdGYManLdEsCRfbCf2jC
uOwhIrtej5gEP8FMj6NG2UiY59xdc2UMtSdGYUaSsYZhQNjS6514LQPtwlKGXUfh
bZNqaRut4ZoegbDEtNfVJOI+BzZB3OOkReEl371YeCBSkhAkboZm1Zhzi+oLwni0
3nENhzCk0LurufoBIzFW/sKr0HyMhJYAXfSKsGRb3blJO1KeVNIStjAwWJgcqcNF
agyL/5aciBMvTj6eu6wl/TqtB1pSwQzks3DPfUT79vAlECkb+5JnYQxFtuseKV44
IaSRUMNXfcfn2LjHU7Pz1Hrhfmc525fUHcD1V0S8ANVlb6Ig0X0snxPCSli2SmQL
atABusbXjaFxDRh7bbGTdQGWlu/6cN5AIuNjuDFElrRnmf/ItyxwpHweeEdV3f5j
2dJz8vQ3AJyuTC+hCqUcYgrPGFpEKuknK5T/4uI4yADSmBH6LnOJkG76yNwMugBu
swu5INrushwQZkL4rxmnQMFN+r57VRXy+2hA7bbWW/+G3DPq7DW7SaWi3umyZV61
Obqrmy8qIs1siIy2rmva
=Zg4G
-----END PGP SIGNATURE-----
I need suggestion for iNxt (iPhone app) what di you want to see next?
A good UI
Hello!
Some testNXT for 18099455365806700711 please, thanks!
Some testNXT for 18099455365806700711 please, thanks!
Sent 5K TestNxt.
I need suggestion for iNxt (iPhone app) what di you want to see next?
Am I forging right? I bought a BTC worth of NXT a few days ago, so I have around 11.5k. All I have to do is leave on my NXT client (NRS 0.7.6) and forging will happen by itself? The past few pages have been talking about how to change up forging to be more profitable... but my question is, how do I check on the progress of my forging?
Thanks! And happy NXTing!
Thanks! And happy NXTing!
If you leave your client on for 24 hours (1440 minutes) then you are forging. Your client is broadcasting its availability to forge the next block, and there is a lottery system going on once a minute behind the scenes that your 11.5K NXT is participating in to win you the right to forge the next block. Wait long enough, you will win that lottery at some particular minute, and you will forge a block. As for monitoring your "progress" - I am not sure if you can really do that.
The two arrows represents "transactions in and out of your account". The globe / peers is just an item of general interest - your client is not communicating with all the computers on the NXT network, only this subset. The puzzle piece is data about the most recently forged blocks.
Great thanks for the help! Still more questions!
1) How can I tip you through this forum?
2) Do I have to leave the wallet unlocked for a strict, straight 24 hours? I use a laptop that I bring to work, then bring to home. So I lose internet connection during transit. If I do need to leave the website on 24/7, raspberry pi is best right for minimal cost/best efficiency?
To be *able* to forge, the balance in your accounts needs to be confirmed 1440 times.
This equates to 24-36 hours.
After that, everytime you open your account, you will be forging with that amount that has 1440 confirmations.
No need to leave your account open to *get* it confirmed. That happens anyway.
If I do need to leave the website on 24/7, raspberry pi is best right for minimal cost/best efficiency?
Yes.
Am I forging right? I bought a BTC worth of NXT a few days ago, so I have around 11.5k. All I have to do is leave on my NXT client (NRS 0.7.6) and forging will happen by itself? The past few pages have been talking about how to change up forging to be more profitable... but my question is, how do I check on the progress of my forging?
Thanks! And happy NXTing!
Thanks! And happy NXTing!
If you leave your client on for 24 hours (1440 minutes) then you are forging. Your client is broadcasting its availability to forge the next block, and there is a lottery system going on once a minute behind the scenes that your 11.5K NXT is participating in to win you the right to forge the next block. Wait long enough, you will win that lottery at some particular minute, and you will forge a block. As for monitoring your "progress" - I am not sure if you can really do that.
The two arrows represents "transactions in and out of your account". The globe / peers is just an item of general interest - your client is not communicating with all the computers on the NXT network, only this subset. The puzzle piece is data about the most recently forged blocks.
Great thanks for the help! Still more questions!
1) How can I tip you through this forum?
2) Do I have to leave the wallet unlocked for a strict, straight 24 hours? I use a laptop that I bring to work, then bring to home. So I lose internet connection during transit. If I do need to leave the website on 24/7, raspberry pi is best for minimal cost/best efficiency?
Some testNXT for 18099455365806700711 please, thanks!
- some testNXT sent.
Hello!
Some testNXT for 18099455365806700711 please, thanks!
Some testNXT for 18099455365806700711 please, thanks!
Maybe there is a penalty or blacklist for a node but IS that purely based on forging activity? and this entire piece should be checked or it could in the future be a ddos exploitation vector as it breaks the network because nodes stop listening to nodes.
This is why we *need* math rather than opinion - I've seen many suggestions put forward but not one of them has any "math" to back them up (so sorry to those who have put them forward but that is why I've not replied to most of them).
I'll look into it.
what if we were to come to the forging issue from a different angle:
The problem as defined here is HOW to keep a small NXT holder (whose motivation is financial and not ideological) interested in maintaining the network?
Another problem (for some at least) was the holding size of larger stakeholders which means that the rich will get richer and the small guy will not make enough.
How do we tackle this? we need to find a solution that will consider both issues: give a chance to the low balance guy to make enough from forging and be motivated while also allowing a chance for a higher balance holder or pool to enjoy suitable returns. we also need enough machines... hence the pool idea.
We also need to remember that high balance individuals have a vesting interest that the network will prosper which means that their equity is worth more. so the motivation there is not only forging rights.
------------------------
The conceptual solution is to create a completely random, lottery like, naturally decentralized algorithm that will assign fees randomly per transaction to any 1NXT in the system without consideration to any holder's NXT balance
Naturally- if you have more NXT you will gravitate toward having better chances to win the transaction fee
However, if you are a low balance guy you KNOW that you can win more fees than your relative holding size.
This will both provide motivation to the low balance holders that at any given moment can win a larger fee than the relative size of their account, and they will stay on and open for that extra chance--- while also take care (statistically) of the higher balance people but from a decentralized perspective- i.e. the system wouldnt care who has more NXT because it will randomly divide fees between all NXT in the system, 1 fraction at a time and not in any particular order-- which will allow for someone to win more than his "natural" share at any given time
Maybe the system can also be programmed to automatically reduce/increase fees above/below a given number of transactions per hour or 24 hours to naturally attract more forging if number of network points decline. However, When there are enough transactions in the system and the network is both lucrative and stable everyone will be happy.
Dont know if this is at all possible and maybe this is nonsense........... but conceptually it seems to be solving issues for all stakeholders by catering to both needs
The problem as defined here is HOW to keep a small NXT holder (whose motivation is financial and not ideological) interested in maintaining the network?
Another problem (for some at least) was the holding size of larger stakeholders which means that the rich will get richer and the small guy will not make enough.
How do we tackle this? we need to find a solution that will consider both issues: give a chance to the low balance guy to make enough from forging and be motivated while also allowing a chance for a higher balance holder or pool to enjoy suitable returns. we also need enough machines... hence the pool idea.
We also need to remember that high balance individuals have a vesting interest that the network will prosper which means that their equity is worth more. so the motivation there is not only forging rights.
------------------------
The conceptual solution is to create a completely random, lottery like, naturally decentralized algorithm that will assign fees randomly per transaction to any 1NXT in the system without consideration to any holder's NXT balance
Naturally- if you have more NXT you will gravitate toward having better chances to win the transaction fee
However, if you are a low balance guy you KNOW that you can win more fees than your relative holding size.
This will both provide motivation to the low balance holders that at any given moment can win a larger fee than the relative size of their account, and they will stay on and open for that extra chance--- while also take care (statistically) of the higher balance people but from a decentralized perspective- i.e. the system wouldnt care who has more NXT because it will randomly divide fees between all NXT in the system, 1 fraction at a time and not in any particular order-- which will allow for someone to win more than his "natural" share at any given time
Maybe the system can also be programmed to automatically reduce/increase fees above/below a given number of transactions per hour or 24 hours to naturally attract more forging if number of network points decline. However, When there are enough transactions in the system and the network is both lucrative and stable everyone will be happy.
Dont know if this is at all possible and maybe this is nonsense........... but conceptually it seems to be solving issues for all stakeholders by catering to both needs
Never forget that NXT (unlike BTC) is a ZERO SUM system. There are no new coins every X minutes being created by mining. This means that if you gimmick the system to put more NXT in one guy's pocket, it means there is less NXT going in somebody else's pocket. This naturally leads to
BTCNext's First Law: "For every increased incentive created in one part of the NXT system, there is an equal and opposite disincentive created elsewhere in the NXT system".
If you haven't identified the disincentive created by your ideas to improve somebody's lot, you haven't done your homework. The current system assures that EVERYBODY GETS THE SAME RETURN ON THEIR INVESTMENT. For a first cut at distributing forging rewards, this is a pretty good idea. Every NXT holder has the opportunity, (if EVERYBODY were to forge simultaneously) to get the same ROI, the SAME interest rate on their "savings account". Saying the "rich will get richer and the small guy will not make enough" is a TRUE STATEMENT, and also a snapshot of the Achilles heel of a Proof of Stake system (and many if not most national fiat currencies). It is also true to say, "Both the rich guy and the small guy are getting the same savings account interest rate on their stockpiled, saved NXT". So the current system has an element of equality in it as well as an element of perceived injustice.
NXT is an experimental attempt to create a stable economic system. This is a completely different proposition than creating a fair social system. Good luck trying to merge the two.
+1
NXT should be PoS.
@AE devs: I seem to be having issues with the AE: When I call 'getAssets', I get these 6 assets, created today after CfB restarted the testnet:
However, looking at 'getState', I see 12 trades.
However, looking at 'getState', I see 12 trades.
There r indeed 12 trades. Check ur response parser for getTrades.
Update - Here is a good riddle: Now I do see the 13Trades in total, just as in the getState - so problem solved.
Important thing to note for DEVs:
Below is a screen from my direct api access. The way this works is that it takes the api call prototype, puts them into the lineedits, and then takes the text from the lineedits to send them to the server.
When I do NOT supply anything for firstIndex and lastIndex, i.e. https://holms.cloudapp.net:6875/nxt?firstIndex=&requestType=getTrades&asset=16739598998421896224&lastIndex=
I get the correct list of all trades for that asset:
But when I supply both zeros as first+last index, I only get one trade:
https://holms.cloudapp.net:6875/nxt?firstIndex=0&requestType=getTrades&asset=16739598998421896224&lastIndex=0
So this explains it - NRS seems to look the index up differently with '' and with '0'
Nice
In all accounts in NXTio forged. Even with 1 NXT.
So does that win the prize as the account forging with least NXT?
so it seems that
Jump to: