Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 2428. (Read 2761629 times)

hero member
Activity: 597
Merit: 500
What does that mean (blockchain explorer):

Code:
Balance Total 	:	23631343 NXT	Confirmed [1] 	:	14368105 NXT	Unconfirmed 	:	9263487 NXT

Does it mean that 9263487 NXT are not yet included in blocks? Why? Yet they show up in our balance. Are they in risk of being reversed / returned?

coins, once confirmed on your account can't be reversed. the 1440 confirmations defines also when coins are able to mining fees.
iirc counted from the first transaction on a new account. problem is we haven't any official white paper or specifications about the
inner algos now, so i decided to add this indicator because the api also delivers this. in case the mining algo will change i can remove
this distinction. in your case this makes no difference, genesis accounts are able to mining right away from start.
legendary
Activity: 2142
Merit: 1010
Newbie
What does that mean (blockchain explorer):

Code:
Balance Total 	:	23631343 NXT	Confirmed [1] 	:	14368105 NXT	Unconfirmed 	:	9263487 NXT

Does it mean that 9263487 NXT are not yet included in blocks? Why? Yet they show up in our balance. Are they in risk of being reversed / returned?
They become confirmed once they reach 1440 confirms.

Why?
member
Activity: 112
Merit: 10
What does that mean (blockchain explorer):

Code:
Balance Total 	:	23631343 NXT	Confirmed [1] 	:	14368105 NXT	Unconfirmed 	:	9263487 NXT

Does it mean that 9263487 NXT are not yet included in blocks? Why? Yet they show up in our balance. Are they in risk of being reversed / returned?
They become confirmed once they reach 1440 confirms.
hero member
Activity: 566
Merit: 500
What does that mean (blockchain explorer):

Code:
Balance Total 	:	23631343 NXT	Confirmed [1] 	:	14368105 NXT	Unconfirmed 	:	9263487 NXT

Does it mean that 9263487 NXT are not yet included in blocks? Why? Yet they show up in our balance. Are they in risk of being reversed / returned?
legendary
Activity: 1367
Merit: 1000
Two times today client suddenly lost all balance and began counting forged fees from zero. Restart helped. Wrong was only balance, other things seemed ok.
sr. member
Activity: 392
Merit: 250
Yes, you have to url-encode at least # and &, that I can think of. You can't even fix it on the server side because in the case of # I don't think the string after the hash gets submitted to the server at all. So, people with special characters in the password will have to encode them manually, see e.g. table here:
http://www.w3schools.com/tags/ref_urlencode.asp
Or do a simple javascript page that does the encoding in javascript on the client. Obviously, don't submit your passwords to any online services that offer url-encoding.
hero member
Activity: 687
Merit: 509
works

"#" to "%23"
legendary
Activity: 2142
Merit: 1010
Newbie
A "#" in the secret in the url before the host?

Hehe, seems so. It must be url-encoded.
hero member
Activity: 687
Merit: 509
hero member
Activity: 687
Merit: 509
Have a problem with version 0.3.15

secretPhrase=MY_SECRET

In my password uses ":,()*+' ", length 64 Grin

Client out that {"errorCode":3,"errorDescription":"\"host\" not specified"}

+1  Grin
legendary
Activity: 2142
Merit: 1010
Newbie

I'll check it, moment...

Looks like "host" is not specified.

Problem in pass. I'll check it by change my ugly secret to "123" and all works.

Guys, does anyone see what maybe the problem in

Code:
						case "markHost":
{

String secretPhrase = req.getParameter("secretPhrase");
String host = req.getParameter("host");
String weightValue = req.getParameter("weight");
String dateValue = req.getParameter("date");
if (secretPhrase == null) {

response.put("errorCode", 3);
response.put("errorDescription", "\"secretPhrase\" not specified");

} else if (host == null) {

response.put("errorCode", 3);
response.put("errorDescription", "\"host\" not specified");

} else if (weightValue == null) {

response.put("errorCode", 3);
response.put("errorDescription", "\"weight\" not specified");

} else if (dateValue == null) {

response.put("errorCode", 3);
response.put("errorDescription", "\"date\" not specified");

} else {

if (host.length() > 100) {

response.put("errorCode", 4);
response.put("errorDescription", "Incorrect \"host\" (the length exceeds 100 chars limit)");

} else {

try {

int weight = Integer.parseInt(weightValue);
if (weight <= 0 || weight > 1000000000) {

throw new Exception();

}

try {

int date = Integer.parseInt(dateValue.substring(0, 4)) * 10000 + Integer.parseInt(dateValue.substring(5, 7)) * 100 + Integer.parseInt(dateValue.substring(8, 10));

byte[] publicKey = Crypto.getPublicKey(secretPhrase);
byte[] hostBytes = host.getBytes("UTF-8");

ByteBuffer buffer = ByteBuffer.allocate(32 + 2 + hostBytes.length + 4 + 4 + 1);
buffer.order(ByteOrder.LITTLE_ENDIAN);
buffer.put(publicKey);
buffer.putShort((short)hostBytes.length);
buffer.put(hostBytes);
buffer.putInt(weight);
buffer.putInt(date);

byte[] data = buffer.array();
byte[] signature;
do {

data[data.length - 1] = (byte)ThreadLocalRandom.current().nextInt();
signature = Crypto.sign(data, secretPhrase);

} while (!Crypto.verify(signature, data, publicKey));

response.put("hallmark", convert(data) + convert(signature));

} catch (Exception e) {

response.put("errorCode", 4);
response.put("errorDescription", "Incorrect \"date\"");

}

} catch (Exception e) {

response.put("errorCode", 4);
response.put("errorDescription", "Incorrect \"weight\"");

}

}

}

}
break;
legendary
Activity: 1334
Merit: 1004
TTM

I'll check it, moment...

Looks like "host" is not specified.

Problem in pass. I'll check it by change my ugly secret to "123" and all works.
legendary
Activity: 2142
Merit: 1010
Newbie
Have a problem with version 0.3.15

secretPhrase=MY_SECRET

In my password uses ":,()*+' ", length 64 Grin

Client out that {"errorCode":3,"errorDescription":"\"host\" not specified"}

+1 !

I'll check it, moment...

Looks like "host" is not specified.
legendary
Activity: 2142
Merit: 1010
Newbie

U guys continue to confuse ppl using "nextcoin" brand. This is "Nxt", no "e", no "coin".
Hmmm you are right! I will tell him to correct it!
So no 'Next' anywhere? Just 'NXT'?

I believe the brand is "Nxt" and the currency code is "NXT".
hero member
Activity: 597
Merit: 500
allowedUserHosts is not enabled yet. I'll add logging feature in 0.3.16. TIME_WAIT is normal behavior, what is the timeout btw?
Code:
$ cat /proc/sys/net/ipv4/tcp_fin_timeout 
5
I reduced it to 5, was 60 before the last crash.


currently running this

Quote
echo 7 > /proc/sys/net/ipv4/tcp_fin_timeout
echo 1 > /proc/sys/net/ipv4/tcp_tw_reuse
echo 30 > /proc/sys/net/ipv4/tcp_keepalive_intvl
echo 5 > /proc/sys/net/ipv4/tcp_keepalive_probes

with +400 peers. seems ok.
newbie
Activity: 34
Merit: 0
Have a problem with version 0.3.15

secretPhrase=MY_SECRET

In my password uses ":,()*+' ", length 64 Grin

Client out that {"errorCode":3,"errorDescription":"\"host\" not specified"}

+1 !
legendary
Activity: 1498
Merit: 1000

U guys continue to confuse ppl using "nextcoin" brand. This is "Nxt", no "e", no "coin".
Hmmm you are right! I will tell him to correct it!
So no 'Next' anywhere? Just 'NXT'?
legendary
Activity: 2142
Merit: 1010
Newbie

U guys continue to confuse ppl using "nextcoin" brand. This is "Nxt", no "e", no "coin".
legendary
Activity: 1498
Merit: 1000
sr. member
Activity: 392
Merit: 250
allowedUserHosts is not enabled yet. I'll add logging feature in 0.3.16. TIME_WAIT is normal behavior, what is the timeout btw?
Code:
$ cat /proc/sys/net/ipv4/tcp_fin_timeout 
5
I reduced it to 5, was 60 before the last crash.
Jump to: