NXT :: descendant of Bitcoin - Updated Information

[Come-from-Beyond]

That should be easy.

Or u can use an alias that contains CRC.

[1713292617]

1713292617

[1713292617]

1713292617

[1713292617]

1713292617

[stdset]

That should be easy.

Or u can use an alias that contains CRC.

Then you should enforce using CRCed aliases only.

[opticalcarrier]

how is someone sending lots of 0 NXT transactions for fee of 1 NXT to genesis?

http://87.230.14.1/nxt/nxt.cgi?action=2000&tra=11197541541396848736

Alias.

ah.  didnt realize that those went to genesis

[Come-from-Beyond]

That should be easy.

Or u can use an alias that contains CRC.

Then you should enforce using CRCed aliases only.

It's a client soft issue.

[martismartis]

Becomes boring:

[2014-01-08 13:30:43.918] "communicationLoggingMask" = "0"
[2014-01-08 13:30:43.918] Loading transactions...
[2014-01-08 13:30:46.403] ...Done
[2014-01-08 13:30:46.404] Loading blocks...
[2014-01-08 13:30:48.561] ...Done
[2014-01-08 13:30:48.561] Scanning blockchain...
[2014-01-08 13:30:49.980] ...Done
2014-01-08 13:30:50.023:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppCo
ntext@5577d330{/,file:/D:/nxt/webapps/root/,AVAILABLE}{D:\nxt\webapps\root}
2014-01-08 13:30:50.039:INFO:oejs.ServerConnector:main: Started ServerConnector@
20bb82ca{HTTP/1.1}{0.0.0.0:7874}
2014-01-08 13:30:50.221:INFO:oejs.ServerConnector:main: Started ServerConnector@
4e54b5d4{SSL-http/1.1}{0.0.0.0:7875}
[2014-01-08 16:47:54.232] Re-scanning blockchain...
[2014-01-08 16:48:18.732] ...Done
[2014-01-08 23:01:01.653] Re-scanning blockchain...
[2014-01-08 23:01:22.350] Generated an incorrect block. Waiting for the next one
...
[2014-01-08 23:01:23.353] Generated an incorrect block. Waiting for the next one
...
[2014-01-08 23:01:24.357] Generated an incorrect block. Waiting for the next one
...
[2014-01-08 23:01:28.602] ...Done


What the hell is going on? Never had forged a block. Client 0.5.3

[stdset]

That should be easy.

Or u can use an alias that contains CRC.

Then you should enforce using CRCed aliases only.

It's a client soft issue.

This solution is ugly.

1) You will have aliases like CfB\0CFA67D9 - looks ugly
2) In another client your alias will be just CfB => people will get confused what your alias really is.
3) Some people won't use aliases at all and will continue to send money to nowhere.

It's a total mess.

[salsacz]

Brainstorming

I'd like to introduce a concept of a new feature called Account Control. This feature will allow to do different things with ur accounts. For example, u will be able to set a lock on an account to prohibit any outgoing transactions until a special condition met (e.g. an incoming transaction from a predefined account). Another example is Pooled Forging, when an account leases its forging power to another account.

Please, post here what u would like to see in Account Control.

Nxt transfer, Alias selling and buying prohibition until a special condition met.

But hackers could probably register, when the special condition happens.


 

[NxtChg]

It's a client soft issue.

Would you stop being silly?

Ok, core devs, consider this very real scenario:

I am building an automated payment collection API right now, similar to blockchain.info. Mostly for the exchange, but I will make it available for others too.

So the merchant calls this API via URL to generate a unique address for each customer and also passes the main account number to forward money to.

And now all your silly talk about how client verification is enough is shuttered into pieces, because now we have a very long and unreliable path between address source and the place where transaction is actually signed.

So what happens if something goes wrong along this path? Human error, network problem, bug, glitch, anything.

Bitcoin: Money isn’t forwarded.
Nxtcoin: Bam! Brains all over the place.

I don’t know how things are going in that perfect, illusory world of yours, where memory corruption doesn’t occur and everything’s rosy, but here in the real world, losing money is kinda big deal.

So why are we playing Russian roulette with it?!

Would you kindly pull your collective head out of your collective ass and start taking this issue seriously?

[BaiMangal]

I post a few days ago in nexcoin.org that aws.amazon.com cloud gives 1 year free micro t1 VPS
I have a windows one free and now I added onepaid both with slightly more than 600mb ram. It seems that the nxt nodes run ok on them. I don't have them hallmarked but I thought we run as many like them as we could to support the stability.

It costs 0 for 1 year.
Go make accounts in aws.amazon.com and set up a VPS with nxt node.
You need to modify the web.xml
         <param-name>myAddress</param-name>
         <param-value>PUT THE VPS IP HERE</param-value>

Don't put money to fogrge just run nxt client.

Just running nxt node (client) with 0 nxt in it will help the stability right?? or am I confused again!!!!

Would be great if you could write up a guide on getting people up and running on AWS. Windows and Linux.

Bai,

I signed up and I'm at my console home page. How do I set up a VPS? Do I launch an EC2 instance? Which flavor (linux, windows) of Amazon Machine Image should I choose?

Also, has anyone confirmed that this will help nxt network stability?

Why am I doing this when I can't even get my client to run properly?

I will do Windows set instructions later on tonight. I am with a customer at the moment and cannt do any work on NXT!!

Would be nice if some of the leaders/genii can confirm that this will help the stability of the newtork else its waste of time.

Step by step with images how to install a VPS in amazon:

AWS (aws.amazon.com) consol set up of a windows server to allow NXT running on it. Should be free for 1 year if you run 1 instance only and its t1 micro (at least it is free for me).
Step are the links (images/screenshots) below in chronological order:
They are really every click so its not as bad as it looks!! less than 20 clicks (simpleS)
https://www.dropbox.com/s/zndsmv3wi0sv15e/AWS_STEP1.jpg
https://www.dropbox.com/s/393eskvlw27gwzw/AWS_STEP2.jpg
https://www.dropbox.com/s/7dgkemjq251a6xp/AWS_STEP3.jpg
https://www.dropbox.com/s/tmeed7hq71kenr7/AWS_STEP4.jpg
https://www.dropbox.com/s/09c297b5jkszkkv/AWS_STEP5.jpg
https://www.dropbox.com/s/90ha0svt8e4c8cv/AWS_STEP6.jpg
https://www.dropbox.com/s/7njp1xdlm8jdh4g/AWS_STEP7.jpg
https://www.dropbox.com/s/71o7rx83g6y21k9/AWS_STEP8.jpg
https://www.dropbox.com/s/0p2us3z167vmaw8/AWS_STEP9.jpg
https://www.dropbox.com/s/w03i7a0qjz2p4w1/AWS_STEP91.jpg
https://www.dropbox.com/s/9wiw7iz1vhhe7dj/AWS_STEP92.jpg
https://www.dropbox.com/s/gizi50y7k82oh4x/AWS_STEP93.jpg
https://www.dropbox.com/s/78bvo8x57zpb7yp/AWS_STEP94.jpg
https://www.dropbox.com/s/nspbhaua0cwc8nm/AWS_STEP95.jpg
https://www.dropbox.com/s/1ba8e784wcn8wi9/AWS_STEP96.jpg
https://www.dropbox.com/s/guqpdagzyv6up7g/AWS_STEP97.jpg
https://www.dropbox.com/s/abuw7m6ue7gk9vv/AWS_STEP98.jpg
https://www.dropbox.com/s/b6tawpzs1muupwl/AWS_STEP99.jpg

After you create and connect to the VPS using the remote desktop shortcut you need to set up Firewall Rule on the Server to allow everything for NXT.
Here are the steps:
https://www.dropbox.com/s/2r345y4j034g8tw/AWS_VPS1.jpg
https://www.dropbox.com/s/r26ee457vynt85z/AWS_VPS2.jpg
https://www.dropbox.com/s/a3bo6zyimtv9do2/AWS_VPS3.jpg
https://www.dropbox.com/s/4ly7zjplf3sp72m/AWS_VPS4.jpg
https://www.dropbox.com/s/iwxtxk4zdueb72k/AWS_VPS5.jpg
https://www.dropbox.com/s/qfotbe1angnda69/AWS_VPS6.jpg
https://www.dropbox.com/s/ofkaxb7nlxodmre/AWS_VPS7.jpg
https://www.dropbox.com/s/0jmc9l305tragar/AWS_VPS8.jpg

DO NOT USE THIS VPS FOR REAL MONEY ACCOUNTS!!
Use them only to put more nodes on the network.

After you set up NXT you need to go in the web.xml file in ....webapps\root\WEB-INF
Open the web.xml and edit the section
         <param-name>myAddress</param-name>
         <param-value>PUT THE VPS IP HERE</param-value>
You can see the IP address in the Remote Desktop Connection Title.

The example VPS that I created is deleted now so there is no point trying to connect to it

[Come-from-Beyond]

Would you kindly pull your collective head out of your collective ass and start taking this issue seriously?

Well, give me an answer on a simple question:

- Where CRC should be added to protect a user from sending 90000 NXT instead of 80000 NXT and how is it different from incorrect account issue?

[davethetrousers]

Total badass, low-cost, always on, client / hallmark node for the home:



Dual-Core ARM, 2Gig RAM, 8Gig fast Flash onboard, GigEthernet, sub-100$
http://docs.cubieboard.org/products/start#cubietruck_cubieboard3

[ferment]

It's a client soft issue.

Would you stop being silly?

Why is that silly? Anyone can build on top of the NXT API and put whatever verification checks they want in a client.

It would take a few days (or less) to hack together an "idiot proof" send money page that uses aliases, verifies the recipient account exists, and asks 3 times if you're really really really sure.

[chanc3r]

Anyone else had a problem with the mac-client auto-update...
I get this worrying message

"The hash of the downloaded update does not equal the one supplied by the blockchain. Aborting update."

Which implies wherever its trying to autoupdate to 0.5.3 from it thinks the source is corrupted  

[msin]

I post a few days ago in nexcoin.org that aws.amazon.com cloud gives 1 year free micro t1 VPS
I have a windows one free and now I added onepaid both with slightly more than 600mb ram. It seems that the nxt nodes run ok on them. I don't have them hallmarked but I thought we run as many like them as we could to support the stability.

It costs 0 for 1 year.
Go make accounts in aws.amazon.com and set up a VPS with nxt node.
You need to modify the web.xml
         <param-name>myAddress</param-name>
         <param-value>PUT THE VPS IP HERE</param-value>

Don't put money to fogrge just run nxt client.

Just running nxt node (client) with 0 nxt in it will help the stability right?? or am I confused again!!!!

Would be great if you could write up a guide on getting people up and running on AWS. Windows and Linux.

Bai,

I signed up and I'm at my console home page. How do I set up a VPS? Do I launch an EC2 instance? Which flavor (linux, windows) of Amazon Machine Image should I choose?

Also, has anyone confirmed that this will help nxt network stability?

Why am I doing this when I can't even get my client to run properly?

I will do Windows set instructions later on tonight. I am with a customer at the moment and cannt do any work on NXT!!

Would be nice if some of the leaders/genii can confirm that this will help the stability of the newtork else its waste of time.

Step by step with images how to install a VPS in amazon:

AWS (aws.amazon.com) consol set up of a windows server to allow NXT running on it. Should be free for 1 year if you run 1 instance only and its t1 micro (at least it is free for me).
Step are the links (images/screenshots) below in chronological order:
They are really every click so its not as bad as it looks!! less than 20 clicks (simpleS)
https://www.dropbox.com/s/zndsmv3wi0sv15e/AWS_STEP1.jpg
https://www.dropbox.com/s/393eskvlw27gwzw/AWS_STEP2.jpg
https://www.dropbox.com/s/7dgkemjq251a6xp/AWS_STEP3.jpg
https://www.dropbox.com/s/tmeed7hq71kenr7/AWS_STEP4.jpg
https://www.dropbox.com/s/09c297b5jkszkkv/AWS_STEP5.jpg
https://www.dropbox.com/s/90ha0svt8e4c8cv/AWS_STEP6.jpg
https://www.dropbox.com/s/7njp1xdlm8jdh4g/AWS_STEP7.jpg
https://www.dropbox.com/s/71o7rx83g6y21k9/AWS_STEP8.jpg
https://www.dropbox.com/s/0p2us3z167vmaw8/AWS_STEP9.jpg
https://www.dropbox.com/s/w03i7a0qjz2p4w1/AWS_STEP91.jpg
https://www.dropbox.com/s/9wiw7iz1vhhe7dj/AWS_STEP92.jpg
https://www.dropbox.com/s/gizi50y7k82oh4x/AWS_STEP93.jpg
https://www.dropbox.com/s/78bvo8x57zpb7yp/AWS_STEP94.jpg
https://www.dropbox.com/s/nspbhaua0cwc8nm/AWS_STEP95.jpg
https://www.dropbox.com/s/1ba8e784wcn8wi9/AWS_STEP96.jpg
https://www.dropbox.com/s/guqpdagzyv6up7g/AWS_STEP97.jpg
https://www.dropbox.com/s/abuw7m6ue7gk9vv/AWS_STEP98.jpg
https://www.dropbox.com/s/b6tawpzs1muupwl/AWS_STEP99.jpg

After you create and connect to the VPS using the remote desktop shortcut you need to set up Firewall Rule on the Server to allow everything for NXT.
Here are the steps:
https://www.dropbox.com/s/2r345y4j034g8tw/AWS_VPS1.jpg
https://www.dropbox.com/s/r26ee457vynt85z/AWS_VPS2.jpg
https://www.dropbox.com/s/a3bo6zyimtv9do2/AWS_VPS3.jpg
https://www.dropbox.com/s/4ly7zjplf3sp72m/AWS_VPS4.jpg
https://www.dropbox.com/s/iwxtxk4zdueb72k/AWS_VPS5.jpg
https://www.dropbox.com/s/qfotbe1angnda69/AWS_VPS6.jpg
https://www.dropbox.com/s/ofkaxb7nlxodmre/AWS_VPS7.jpg
https://www.dropbox.com/s/0jmc9l305tragar/AWS_VPS8.jpg

DO NOT USE THIS VPS FOR REAL MONEY ACCOUNTS!!
Use them only to put more nodes on the network.

After you set up NXT you need to go in the web.xml file in ....webapps\root\WEB-INF
Open the web.xml and edit the section
         <param-name>myAddress</param-name>
         <param-value>PUT THE VPS IP HERE</param-value>
You can see the IP address in the Remote Desktop Connection Title.

The example VPS that I created is deleted now so there is no point trying to connect to it

Nice work, thanks for doing that.

[gbeirn]

Would you kindly pull your collective head out of your collective ass and start taking this issue seriously?

Well, give me an answer on a simple question:

- Where CRC should be added to protect a user from sending 90000 NXT instead of 80000 NXT and how is it different from incorrect account issue?

Exactly it's a user/client side issue.

[wesleyh]

Anyone else had a problem with the mac-client auto-update...
I get this worrying message

"The hash of the downloaded update does not equal the one supplied by the blockchain. Aborting update."

Which implies wherever its trying to autoupdate to 0.5.3 from it thinks the source is corrupted  

Hi, download 0.20 here: http://nxtra.org/mac

The reason you got that message is because they're using another location for downloads now (hopefully the final time they change it..) - and what was compared was the hash of a HTML page returned at the old download location no longer in use instead of the zip.

[NxtChg]

- Where CRC should be added to protect a user from sending 90000 NXT instead of 80000 NXT and how is it different from incorrect account issue?

The big difference is in case of addresses you can add such checksum. So there is no reason not to.

In my API example this alone is enough to solve the problem.

Also, in case of the amount, the user can verify it, because it's human-readable.

In case of the address - he can't notice a typo that easily.

EDIT: And this is a silly talk anyway. "Let's not bother with our plane engine safety, because somebody might die of a heart attack on the plane, anyway"!

[stdset]

Would you kindly pull your collective head out of your collective ass and start taking this issue seriously?

Well, give me an answer on a simple question:

- Where CRC should be added to protect a user from sending 90000 NXT instead of 80000 NXT and how is it different from incorrect account issue?

Guys. Please calm down. We all want Nxt to succeed. No need for insults. I beleive we are all mature enough to be above that.
Let CfB and especially Jean-Luc think about it. And, I strongly beleive, they won't be able not to fix it. In several days Jean-Luc will figure out details of the right solution, and will schedule it for implementation. There is just no other way.

[TwinWinNerD]

I guess im pretty unlucky. Forging with 60k-100k for >2 weeks now, no block found...

[notsoshifty]

But 3 GB???  

That is. Just. Wrong.

I also don't see why this amount of memory should be required, given the traffic volumes we're seeing now, except for buggy code. I'd (still) like to see GC logs from a JVM with >=1GB heap that runs out of memory, when using these logging parameters:

Code:

-verbose:gc -Xloggc:gc.log -XX:+PrintGCDateStamps -XX:+PrintGCDetails

Anyone can supply?