NXT :: descendant of Bitcoin - Updated Information - page 1758.

wesleyh

sr. member

Activity: 308

Merit: 250

Quote from: Come-from-Beyond on January 08, 2014, 05:06:06 PM

Quote from: NxtChg on January 08, 2014, 04:59:07 PM

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

Aliases r readable too.

Problem is aliases need to be looked up, and you have to be sure no one is poisoning the alias lookup with fake info (associated id). So you have to do at least 5+ lookups from different peers to be sure that the ID is correct.. (Is this correct?) - That's not very fast and you won't reach 10,000 tps (or however many you want) this way. I may be wrong.

TwinWinNerD

legendary

Activity: 1680

Merit: 1001

CEO Bitpanda.com

Quote from: S3MKi on January 08, 2014, 05:05:58 PM

Quote from: TwinWinNerD on January 08, 2014, 05:03:05 PM

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

buy more

good solution... Cheesy

Come-from-Beyond

legendary

Activity: 2142

Merit: 1010

Newbie

Quote from: NxtChg on January 08, 2014, 04:59:07 PM

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

Aliases r readable too.

S3MKi

legendary

Activity: 1540

Merit: 1016

Quote from: TwinWinNerD on January 08, 2014, 05:03:05 PM

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

buy more

chanc3r

sr. member

Activity: 952

Merit: 253

Quote from: wesleyh on January 08, 2014, 04:57:11 PM

Quote from: chanc3r on January 08, 2014, 04:54:17 PM

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 Shocked

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.

Sorted tyvm...

NxtChg

hero member

Activity: 840

Merit: 1002

Simcoin Developer

Quote from: stdset on January 08, 2014, 04:59:54 PM

Let CfB and especially Jean-Luc think about it.

I already did. There seems to be no progress whatsoever.

kunibopl

full member

Activity: 184

Merit: 100

Quote from: Come-from-Beyond on January 08, 2014, 04:44:33 PM

Quote from: NxtChg on January 08, 2014, 04:27:20 PM

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?

here one has to defend NxtChg. when you are content living with two possible scenarios of typos, why not invent 10 more?
on the other hand I don't understand, why a client can't check if an account is known to the blockchain.

notsoshifty

sr. member

Activity: 378

Merit: 250

Quote from: NxtChg on January 08, 2014, 03:24:51 PM

But 3 GB??? Shocked

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?

TwinWinNerD

legendary

Activity: 1680

Merit: 1001

CEO Bitpanda.com

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

stdset

hero member

Activity: 572

Merit: 506

Quote from: Come-from-Beyond on January 08, 2014, 04:44:33 PM

Quote from: NxtChg on January 08, 2014, 04:27:20 PM

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.

NxtChg

hero member

Activity: 840

Merit: 1002

Simcoin Developer

Quote from: Come-from-Beyond on January 08, 2014, 04:44:33 PM

- 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"!

wesleyh

sr. member

Activity: 308

Merit: 250

Quote from: chanc3r on January 08, 2014, 04:54:17 PM

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 Shocked

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.

gbeirn

full member

Activity: 126

Merit: 100

Quote from: Come-from-Beyond on January 08, 2014, 04:44:33 PM

Quote from: NxtChg on January 08, 2014, 04:27:20 PM

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.

msin

legendary

Activity: 1470

Merit: 1004

Quote from: BaiMangal on January 08, 2014, 04:33:35 PM

Quote from: BaiMangal on January 08, 2014, 08:30:26 AM

Quote from: msin on January 07, 2014, 06:27:16 PM

Quote from: BaiMangal on January 07, 2014, 06:03:06 PM

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

myAddress

PUT THE VPS IP HERE

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.

Quote from: swartzfeger on January 07, 2014, 06:55:23 PM

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? Tongue

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.

myAddress

PUT THE VPS IP HERE

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.

chanc3r

sr. member

Activity: 952

Merit: 253

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 Shocked

ferment

full member

Activity: 168

Merit: 100

IDEX - LIVE Real-time DEX

Quote from: NxtChg on January 08, 2014, 04:27:20 PM

Quote from: Come-from-Beyond on January 08, 2014, 04:03:38 PM

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.

davethetrousers

full member

Activity: 196

Merit: 100

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

Come-from-Beyond

legendary

Activity: 2142

Merit: 1010

Newbie

Quote from: NxtChg on January 08, 2014, 04:27:20 PM

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?

BaiMangal

member

Activity: 111

Merit: 10

Quote from: BaiMangal on January 08, 2014, 08:30:26 AM

Quote from: msin on January 07, 2014, 06:27:16 PM

Quote from: BaiMangal on January 07, 2014, 06:03:06 PM

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

myAddress

PUT THE VPS IP HERE

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.

Quote from: swartzfeger on January 07, 2014, 06:55:23 PM

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? Tongue

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.

myAddress

PUT THE VPS IP HERE

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

NxtChg

hero member

Activity: 840

Merit: 1002

Simcoin Developer

Quote from: Come-from-Beyond on January 08, 2014, 04:03:38 PM

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?

Topic: NXT :: descendant of Bitcoin - Updated Information - page 1758. (Read 2761645 times)