http://www.nxt-e.com, a new trading platform on NXT, safe, convenient, simple and more suitable for everyone transaction, we hope that a positive test, there are many tips that will surpass God as my witness BTER. Please we like to believe NXT as we believe, equally worthy of your trust that we will be together for the NXT ecological sacrificed their part!
Welcome everyone to share!
We have been working hard!
Topic: NXT :: descendant of Bitcoin - Updated Information - page 1252. (Read 2761626 times)
Can someone answer me this:
If i forge a block, can someone else see my IP then?
Or lets phrase it diffrently. I need to run a node to forge, is my account number connected to the forging IP?
If i forge a block, can someone else see my IP then?
Or lets phrase it diffrently. I need to run a node to forge, is my account number connected to the forging IP?
Could someone please answer this?
I was discussing this with a friend and we came to the conclusion that this would be a huge security concern if it is indeed so.
However, an adversary who monitors all your internet traffic (your ISP) could possible deduce that it was your node that generated a block based on traffic analysis. It is possible to run Nxt over tor if you want to completely avoid that risk. To do so, assuming you have tor running on localhost at port 9050, add the following system properties to your start.d/nxt.ini file:
-DsocksProxyHost=localhost
-DsocksProxyPort=9050
This will force outgoing traffic to use tor as a socks proxy, but jetty will still listen on all interfaces and accept connections that didn't come over tor. If you are behind a router or firewall, this is not an issue, if not, edit the jetty configuration files (start.ini) to limit jetty.host to localhost. Also, if you are using tor, you cannot share your address with other peers that want to connect to you (because what they see is the tor exit node IP), so you should disable shareMyAddress in web.xml and not set myAddress there. It is like being behind a router without being able to set up port forwarding.
why not 0.6?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Release 0.5.11
...
Hash: SHA1
Release 0.5.11
...
Thank you!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Release 0.5.11
http://download.nxtcrypto.org/nxt-client-0.5.11.zip
sha256: 2157335852e7b5013229f5b73f5f156b1b72a116f8625fc73d4de80a0f7ffa11
Change log:
Fixed performance problems in getState, getEffectiveBalance and
getGuaranteedBalance. The getGuaranteedBalance calculation now
uses a different algorithm and may in some cases give different
results than the 0.5.10 guaranteedBalance calculation which had
some bugs, so it is advisable that everyone upgrades to 0.5.11
to avoid the risk of a fork.
Fixed a bug with setting the public keys of accounts that forged
blocks without having any outgoing transactions.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJS6hPPAAoJEFOhyXc7+e2A4JIQAJCid4K4z+07zVSXIrNdjC+7
B/9riaqdXL6pNhbuXRFqmFazJb2LQfw2CHDxiYujqOzQr9lfYDkJSaSa8tpY1seY
ZxMhzq2OcIcvp2KFuiueq25GNuWxAj/2Ctjm8Cco4SvzhXrK10JpOWgGexFN1ZHX
VDGgZiNheLwqYMqcfouVtPlNAR0l1hu26pUqw3zFUfRFWxfc7lIJZmj3uBJXdLxw
HSLEosCHtME7J2GL526rtpvY1PwNBJszrd6ustSRfevLY6JyAYj8yoqpbPfsc/r5
PEEQlPw0RUAWsaW+r2V7zXHKGtpyLWaI84MyHIpSZKsGZuWcDqXXDLGQxIE6sm1a
/mJgewfU63mxym+LA+M+fEg57xtry+YldOrwyv8AATfANsusXX/A50gG/CHdqBDF
m4nUKlWjeXfDhrwxjE2ZVnwSO7pPYrvnEkw9LxvKF4sv0LfCFKDdhNsgDfLPEQp8
mWy0WfIiraz5QDkDf1JKBJM+1tRJWwBuNY1Z4nHZwsVPO0cf6aXOg52qP63sIe98
CgR6xVn8S2xhhyUMFluJcfldQA0vMr2dNAnt9eTjUykDpS0VHNcW54RSpQZxE0Z6
WT0xSCvknUB86N7BzatZz27BtCSieC+MWn3KrQvofB6wbW9OMXuTjFTuBxMoMD1H
9fZmQKaXviyVQ8C9ci/H
=plAW
-----END PGP SIGNATURE-----
Hash: SHA1
Release 0.5.11
http://download.nxtcrypto.org/nxt-client-0.5.11.zip
sha256: 2157335852e7b5013229f5b73f5f156b1b72a116f8625fc73d4de80a0f7ffa11
Change log:
Fixed performance problems in getState, getEffectiveBalance and
getGuaranteedBalance. The getGuaranteedBalance calculation now
uses a different algorithm and may in some cases give different
results than the 0.5.10 guaranteedBalance calculation which had
some bugs, so it is advisable that everyone upgrades to 0.5.11
to avoid the risk of a fork.
Fixed a bug with setting the public keys of accounts that forged
blocks without having any outgoing transactions.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJS6hPPAAoJEFOhyXc7+e2A4JIQAJCid4K4z+07zVSXIrNdjC+7
B/9riaqdXL6pNhbuXRFqmFazJb2LQfw2CHDxiYujqOzQr9lfYDkJSaSa8tpY1seY
ZxMhzq2OcIcvp2KFuiueq25GNuWxAj/2Ctjm8Cco4SvzhXrK10JpOWgGexFN1ZHX
VDGgZiNheLwqYMqcfouVtPlNAR0l1hu26pUqw3zFUfRFWxfc7lIJZmj3uBJXdLxw
HSLEosCHtME7J2GL526rtpvY1PwNBJszrd6ustSRfevLY6JyAYj8yoqpbPfsc/r5
PEEQlPw0RUAWsaW+r2V7zXHKGtpyLWaI84MyHIpSZKsGZuWcDqXXDLGQxIE6sm1a
/mJgewfU63mxym+LA+M+fEg57xtry+YldOrwyv8AATfANsusXX/A50gG/CHdqBDF
m4nUKlWjeXfDhrwxjE2ZVnwSO7pPYrvnEkw9LxvKF4sv0LfCFKDdhNsgDfLPEQp8
mWy0WfIiraz5QDkDf1JKBJM+1tRJWwBuNY1Z4nHZwsVPO0cf6aXOg52qP63sIe98
CgR6xVn8S2xhhyUMFluJcfldQA0vMr2dNAnt9eTjUykDpS0VHNcW54RSpQZxE0Z6
WT0xSCvknUB86N7BzatZz27BtCSieC+MWn3KrQvofB6wbW9OMXuTjFTuBxMoMD1H
9fZmQKaXviyVQ8C9ci/H
=plAW
-----END PGP SIGNATURE-----
Could someone teach me how to check signature/hash. Someone said a couple of days ago that he can't confirm hash with 0.5.10 so I though it's better to learn before the next update.
Release 0.5.11
http://download.nxtcrypto.org/nxt-client-0.5.11.zip
sha256: 2157335852e7b5013229f5b73f5f156b1b72a116f8625fc73d4de80a0f7ffa11
http://download.nxtcrypto.org/nxt-client-0.5.11.zip
sha256: 2157335852e7b5013229f5b73f5f156b1b72a116f8625fc73d4de80a0f7ffa11
http://localhost:7874/update.html is not recognizing installed version (0.5.10) for some reason.
Indeed, latest available update not recognised
Works for me, you probably do not yet have the latest block which contains updated alias.
Release 0.5.11
http://download.nxtcrypto.org/nxt-client-0.5.11.zip
sha256: 2157335852e7b5013229f5b73f5f156b1b72a116f8625fc73d4de80a0f7ffa11
http://download.nxtcrypto.org/nxt-client-0.5.11.zip
sha256: 2157335852e7b5013229f5b73f5f156b1b72a116f8625fc73d4de80a0f7ffa11
http://localhost:7874/update.html is not recognizing installed version (0.5.10) for some reason.
edit: works
Thank you, Mr. Picard.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Release 0.5.11
http://download.nxtcrypto.org/nxt-client-0.5.11.zip
sha256: 2157335852e7b5013229f5b73f5f156b1b72a116f8625fc73d4de80a0f7ffa11
Change log:
Fixed performance problems in getState, getEffectiveBalance and
getGuaranteedBalance. The getGuaranteedBalance calculation now
uses a different algorithm and may in some cases give different
results than the 0.5.10 guaranteedBalance calculation which had
some bugs, so it is advisable that everyone upgrades to 0.5.11
to avoid the risk of a fork.
Fixed a bug with setting the public keys of accounts that forged
blocks without having any outgoing transactions.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJS6hPPAAoJEFOhyXc7+e2A4JIQAJCid4K4z+07zVSXIrNdjC+7
B/9riaqdXL6pNhbuXRFqmFazJb2LQfw2CHDxiYujqOzQr9lfYDkJSaSa8tpY1seY
ZxMhzq2OcIcvp2KFuiueq25GNuWxAj/2Ctjm8Cco4SvzhXrK10JpOWgGexFN1ZHX
VDGgZiNheLwqYMqcfouVtPlNAR0l1hu26pUqw3zFUfRFWxfc7lIJZmj3uBJXdLxw
HSLEosCHtME7J2GL526rtpvY1PwNBJszrd6ustSRfevLY6JyAYj8yoqpbPfsc/r5
PEEQlPw0RUAWsaW+r2V7zXHKGtpyLWaI84MyHIpSZKsGZuWcDqXXDLGQxIE6sm1a
/mJgewfU63mxym+LA+M+fEg57xtry+YldOrwyv8AATfANsusXX/A50gG/CHdqBDF
m4nUKlWjeXfDhrwxjE2ZVnwSO7pPYrvnEkw9LxvKF4sv0LfCFKDdhNsgDfLPEQp8
mWy0WfIiraz5QDkDf1JKBJM+1tRJWwBuNY1Z4nHZwsVPO0cf6aXOg52qP63sIe98
CgR6xVn8S2xhhyUMFluJcfldQA0vMr2dNAnt9eTjUykDpS0VHNcW54RSpQZxE0Z6
WT0xSCvknUB86N7BzatZz27BtCSieC+MWn3KrQvofB6wbW9OMXuTjFTuBxMoMD1H
9fZmQKaXviyVQ8C9ci/H
=plAW
-----END PGP SIGNATURE-----
Hash: SHA1
Release 0.5.11
http://download.nxtcrypto.org/nxt-client-0.5.11.zip
sha256: 2157335852e7b5013229f5b73f5f156b1b72a116f8625fc73d4de80a0f7ffa11
Change log:
Fixed performance problems in getState, getEffectiveBalance and
getGuaranteedBalance. The getGuaranteedBalance calculation now
uses a different algorithm and may in some cases give different
results than the 0.5.10 guaranteedBalance calculation which had
some bugs, so it is advisable that everyone upgrades to 0.5.11
to avoid the risk of a fork.
Fixed a bug with setting the public keys of accounts that forged
blocks without having any outgoing transactions.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJS6hPPAAoJEFOhyXc7+e2A4JIQAJCid4K4z+07zVSXIrNdjC+7
B/9riaqdXL6pNhbuXRFqmFazJb2LQfw2CHDxiYujqOzQr9lfYDkJSaSa8tpY1seY
ZxMhzq2OcIcvp2KFuiueq25GNuWxAj/2Ctjm8Cco4SvzhXrK10JpOWgGexFN1ZHX
VDGgZiNheLwqYMqcfouVtPlNAR0l1hu26pUqw3zFUfRFWxfc7lIJZmj3uBJXdLxw
HSLEosCHtME7J2GL526rtpvY1PwNBJszrd6ustSRfevLY6JyAYj8yoqpbPfsc/r5
PEEQlPw0RUAWsaW+r2V7zXHKGtpyLWaI84MyHIpSZKsGZuWcDqXXDLGQxIE6sm1a
/mJgewfU63mxym+LA+M+fEg57xtry+YldOrwyv8AATfANsusXX/A50gG/CHdqBDF
m4nUKlWjeXfDhrwxjE2ZVnwSO7pPYrvnEkw9LxvKF4sv0LfCFKDdhNsgDfLPEQp8
mWy0WfIiraz5QDkDf1JKBJM+1tRJWwBuNY1Z4nHZwsVPO0cf6aXOg52qP63sIe98
CgR6xVn8S2xhhyUMFluJcfldQA0vMr2dNAnt9eTjUykDpS0VHNcW54RSpQZxE0Z6
WT0xSCvknUB86N7BzatZz27BtCSieC+MWn3KrQvofB6wbW9OMXuTjFTuBxMoMD1H
9fZmQKaXviyVQ8C9ci/H
=plAW
-----END PGP SIGNATURE-----
Mom told me to study C++, but I preferred useless stuff like Asm, Basic and Pascal.
That source code is old, anyway.
Here's what I could understand from video and reading till 4 in the morning yesterday:
The core of their proof is SNARK (Succinct Non-interactive ARgument of Knowledge) - voodoo math that allows others to verify that you actually executed some piece of code, that's why it's so complicated. Everything else is easy: in new version they just use SHA256 and Merkle tree to store the coins.
So this SNARK thing looks a bit suspicious to me, but that's probably because it's so original and counter-intuitive and I don't even fully understand it yet
Anyway, what they do with it, is create an alternative way for you to prove that you did a chain of SHA256's up to the root.
So you can prove that your coin is somewhere on the tree, without revealing any actual hashes, which would identify on which branch your coin is located.
Gonna drink my coffee and read more.
He also said he hopes people don't invest too much in it at first in case it's flawed. This might give him reason to be cautious about integrating with Nxt before he can prove it works well in a real-world test application.
Also, I don't know anything about this, but do economies of scale also apply to electricity? I.e. is it more efficient/cheaper-per-unit to run 10000 computers than it is to run one?
Yes. If you use a lot of power, you can negotiate with your power company to get cheaper rates.
Ok, if that's true, then the assumption of linearly increasing electricity costs needs to be corrected as well. Any idea what rate of discount is reasonable? On page 25:
"The person with 1 million Nxt has 100x higher chance to get the transaction fees than
the person with 100 Nxt. He still pays the same electricity. The person with 1 million GPU
miners has 100x higher chance to get Bitcoin block than the person with 100 GPU miners.
However, he was able to purchase those 1 million GPU miners at a fraction of the cost per miner than the person who only purchased 100, and negotiate a discount with his electricity supplier, due to the economies of scale advantage associated with large-scale operations."
And on page 26:
"World of Bitcoin:
- If you have 1000$, you can mine X Btc thanks to the GPU
- If you have 100.000$, you can mine 1000X Btc thanks to some super machine
you buy
- if you have 100x1000$GPU, you get 100X Btc (+ pay 100x minus discount for
- if you have 1x100.000$Machine, you get 1000X Btc (+ pay for
After a month of almost daily work I can present you a full text version of the NxtMyths:
https://drive.google.com/file/d/0BwAGADgnQcrtM3g1cU1VSHZtTGM/edit?usp=sharing
https://drive.google.com/file/d/0BwAGADgnQcrtM3g1cU1VSHZtTGM/edit?usp=sharing
Another edit: on page 26 the title "Only PoW is unfair and rich gets richer" would make more sense as "The rich are favored more in PoW than PoS".
Mom told me to study C++, but I preferred useless stuff like Asm, Basic and Pascal.
That source code is old anyway.
Here's what I could understand from video and reading till 4 in the morning yesterday:
The core of their system is SNARK (Succinct Non-interactive ARgument of Knowledge) - voodoo math that allows others to verify that you actually executed some piece of code, that's why it's so complicated. Everything else is easy: in the new version they just use SHA256 and Merkle tree to store the coins.
So this SNARK thing looks a bit suspicious to me, but that's probably because it's so original and counter-intuitive and I don't even fully understand it yet
Anyway, what they do with it, is create an alternative way for you to prove that you did a chain of SHA256's up to the root.
So you can prove that your coin is somewhere on the tree, without revealing any actual hashes, which would identify on which branch your coin is located.
Gonna drink my coffee and read more.
Also, I don't know anything about this, but do economies of scale also apply to electricity? I.e. is it more efficient/cheaper-per-unit to run 10000 computers than it is to run one?
Yes. If you use a lot of power, you can negotiate with your power company to get cheaper rates.
I can draw some pictures for NXT.
Very nice, it would be an enrichment for the project.
After a month of almost daily work I can present you a full text version of the NxtMyths:
https://drive.google.com/file/d/0BwAGADgnQcrtM3g1cU1VSHZtTGM/edit?usp=sharing
New still unpublished chapters - 7. Rich get richer and 8. (no) Innovations over Bitcoin start at the page 25 (actually 8th chapter is only one known table..). There are also some new tables you probably didn't see on previous pages.
Comments are enabled for grammar mistakes. Facts and wrong ideas can be discussed here...
If you think it's worth any donations, feel free to send them to: 15003961341330858247
Now I can finally switch to the infographics stage
(infographics will mention the NxtMyths paper as a source...)
https://drive.google.com/file/d/0BwAGADgnQcrtM3g1cU1VSHZtTGM/edit?usp=sharing
New still unpublished chapters - 7. Rich get richer and 8. (no) Innovations over Bitcoin start at the page 25 (actually 8th chapter is only one known table..). There are also some new tables you probably didn't see on previous pages.
Comments are enabled for grammar mistakes. Facts and wrong ideas can be discussed here...
If you think it's worth any donations, feel free to send them to: 15003961341330858247
Now I can finally switch to the infographics stage
(infographics will mention the NxtMyths paper as a source...)This paragraph at the bottom of page 25 seems to conflict with the general thrust of the argument it is supporting:
"The person with 1 million Nxt has 100x higher chance to get the transaction fees than
the person with 100 Nxt. He still pays the same electricity. The person with 1 million GPU
miners has 100x higher chance to get Bitcoin block than the person with 100 GPU miners.
But he pays 100x more for the electricity."
You should add: "However, he was able to purchase those 1 million GPU miners at a fraction of the cost per miner than the person who only purchased 100, due to the economies of scale advantage associated with large-scale acquisitions."
This provides a logical connection with the next statement concerning economies of scale.
Also, I don't know anything about this, but do economies of scale also apply to electricity? I.e. is it more efficient/cheaper-per-unit to run 10000 computers than it is to run one?
Any UK Nxt holders? We need to position ourselves to get on Bittylicious to increase liquidity. The ability to purchase Nxt without Bitcoin is a big deal and one we should put some energy towards.
I was hoping somebody else would step up to the plate on this one, but since they haven't. here's my two cents, er, shillings worth. I have a UK Barclays bank account I use to fund my online poker adventures. It's a totally legal one in my own name, no funny business; I've filed the correct paperwork on it with the IRS and Department of the Treasury here in the US and even voluntarily gave up the number for it during my last security clearance interview. I go thru a proxy and look like I'm in London since the online poker sites block me otherwise coming from an American IP address block. All of these gyrations are due to the 2006 UIEGA anti-online-poker act that was passed here in America, land of the free; but I digress...
Bottom line, I've got the UK bank account but I have no desire to sell any of the NXT I've accumulated. However, I understand the importance of getting NXT hooked up to Bittylicious so I'm willing to try and help. If I've got enough public trust built up here, maybe people could dump NXT they wanted to sell into one of my toy NXT accounts, Bittilocious could take it out of that account to give to a buyer, send GBP to my Barclays account, and I could send that back to the original NXT holders via Moneybookers/Skrill (I've also got accounts there, too.)
This would require me to be a trusted middleman, which I'm OK with if you are.
If we really want to pursue this, let me know, I'll do my part to get NXT rolling in the UK.
As soon as the Decentralized Exchange is released we should have our EUR-NXT gateway ready.. It should give people an option to buy NXT for Euro
And I can see that and agree with jl777's thought, it is well said... but would a government agent who supported the NSA agree with that?
I would think about what I want in Nxt and work towards it. And if govts and the NSA have a problem with that, then I would think about how to deal with them in Nxt.
"The universe believes in encryption.
It is easier to encrypt information than it is to decrypt it."
- Julian Assange.
@CfB - to me this looks like a security feature on the testnet. I have been doing this manually, and not really massively, maybe 10 or 15 times over the course of 1 hour.
Is it a bug, or is it a feature
Traceback (most recent call last):
File "/home/azure/workbench/nxtDev/nxTrader/nxtApiSigs.py", line 249, in getBalance_Slot
self.apiRepl1=requests.get( self.userData['serverProt'], params = self.apiReq, verify=False)
File "/usr/lib/python3/dist-packages/requests/api.py", line 55, in get
return request('get', url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 44, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 357, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 460, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 354, in send
raise ConnectionError(e)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='holms.cloudapp.net', port=6874): Max retries exceeded with url: /nxt?account=7126304194855053556&requestType=getBalance (Caused by
The testnet is being updated to new version right now. Maybe this caused ur error?
no big deal anyway - just a funny thing ..
Jump to: