Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 1888. (Read 2761650 times)

full member
Activity: 154
Merit: 100
I sent 100k nxt to the peercover NXT Gateway.
How much time is needed for them to appear on my balance?

10 confirmations, so about 13 minutes

even faster, sometime less than 1 min. i have tested.
hero member
Activity: 695
Merit: 500
Its already running close to one hour now and ist still on block 1. I have 19 connected peers....do you think adding peers manually would help?
If so, do you by any chance have a link to a peer list and how to add them?
Thanks

Use http://nxtra.org/nodes/ to get peers.

Switch "communicationLoggingMask" to "3" and send me log after 5 mins of working.

OK, did as you sad...but I think I will be unable to send you a log file as strangly there are none (I am looking in the "logs" folder, is this correct? )...
Also I am now running fo a couple of minuts and its the same story as before, though this time I only have 3 conected peers....but more should drop in as time passes.

Run "java -jar start.jar > log.txt" and send me log.txt file.

Code:
[2014-01-03 18:26:54.320] Nxt 0.4.9e started.
[2014-01-03 18:26:54.321] "blockchainStoragePath" = "blockchain.nrs"
[2014-01-03 18:26:54.321] "myPlatform" = "PC"
[2014-01-03 18:26:54.321] "myScheme" = "http"
[2014-01-03 18:26:54.321] "myPort" = "7874"
[2014-01-03 18:26:54.321] "myAddress" = ""
[2014-01-03 18:26:54.321] "shareMyAddress" = "true"
[2014-01-03 18:26:54.321] "myHallmark" = ""
[2014-01-03 18:26:54.321] "wellKnownPeers" = "87.230.14.1; 46.19.137.116; 95.85.22.142; node18.nxtbase.com; node10.nxtbase.com; vps1.nxtcrypto.org; vps2.nxtcrypto.org; vps3.nxtcrypto.org; vps4.nxtcrypto.org; vps5.nxtcrypto.org; node16.nxtbase.com; node09.nxtbase.com; node29.nxtbase.com; 162.243.214.183; 162.243.213.115; 78.46.63.221; 95.85.46.233; 162.243.140.133; 146.185.129.54; 162.243.143.15; 109.230.224.65; 46.165.208.107:32151; 54.249.101.252; 37.209.120.192; 84.112.39.24; 78.46.63.221; 69.163.47.173; 95.85.46.233; 162.243.140.133; 146.185.129.54; 162.243.117.63; 192.241.155.44; 162.243.214.68; 95.85.46.164; 162.243.216.55; 162.243.143.15; 95.85.46.249; 93.190.92.74; 37.209.120.192; 93.190.92.75; 85.25.134.59; 93.190.92.76; nxtwallet.com; 31.220.50.208; nxt.ddos.me; 203.174.12.25; 88.198.142.92; 66.197.138.90; 64.120.180.106; 109.230.224.65; 80.86.92.50; node1.nextcoin.it; node2.nextcoin.it; node3.nextcoin.it; node4.nextcoin.it; node5.nextcoin.it; nxt.homer.ru; 31.204.130.123; 209.222.0.194; 209.222.16.10; node85.nxtbase.com; node19.nxtbase.com; node6.nxtbase.com; node90.nxtbase.com; node67.nxtbase.com; node69.nxtbase.com; node88.nxtbase.com; node50.nxtbase.com; nxt20.tweetmondo.com; nxt6.tweetmondo.com; node58.nxtbase.com; node82.nxtbase.com; node86.nxtbase.com; nxt2.tweetmondo.com; 91.115.213.16; node37.nxtbase.com; node81.nxtbase.com; 95.85.46.233; node59.nxtbase.com; nxt12.tweetmondo.com; vps5.nxtcrypto.org; node5.nxtbase.com; nxt5.tweetmondo.com; node52.nxtbase.com; node61.nxtbase.com;"
[2014-01-03 18:26:54.327] "maxNumberOfConnectedPublicPeers" = "20"
[2014-01-03 18:26:54.327] "connectTimeout" = "2000"
[2014-01-03 18:26:54.327] "readTimeout" = "5000"
[2014-01-03 18:26:54.327] "enableHallmarkProtection" = "true"
[2014-01-03 18:26:54.328] "pushThreshold" = "0"
[2014-01-03 18:26:54.328] "pullThreshold" = "0"
[2014-01-03 18:26:54.328] "allowedUserHosts" = "127.0.0.1; localhost; 0:0:0:0:0:0:0:1;"
[2014-01-03 18:26:54.328] "allowedBotHosts" = "127.0.0.1; localhost; 0:0:0:0:0:0:0:1;"
[2014-01-03 18:26:54.328] "blacklistingPeriod" = "300000"
[2014-01-03 18:26:54.328] "communicationLoggingMask" = "3"
[2014-01-03 18:26:54.328] Loading transactions...
[2014-01-03 18:26:54.345] ...Done
[2014-01-03 18:26:54.345] Loading blocks...
[2014-01-03 18:26:54.348] ...Done
[2014-01-03 18:26:54.348] Scanning blockchain...
[2014-01-03 18:26:54.360] ...Done
[2014-01-03 18:27:50.163] "31.220.50.208": {"shareAddress":true,"port":7874,"platform":"PC","application":"NRS","scheme":"http","requestType":"getInfo","version":"0.4.9e"} >>> java.net.SocketTimeoutException: connect timed out

[2014-01-03 18:28:53.626] "162.243.214.183": {"shareAddress":true,"port":7874,"platform":"PC","application":"NRS","scheme":"http","requestType":"getInfo","version":"0.4.9e"} >>> java.net.SocketTimeoutException: connect timed out

[2014-01-03 18:29:29.412] "162.243.117.63": {"protocol":1,"requestType":"getPeers"} >>> java.net.SocketTimeoutException: connect timed out

[2014-01-03 18:30:46.210] "54.249.101.252": {"shareAddress":true,"port":7874,"platform":"PC","application":"NRS","scheme":"http","requestType":"getInfo","version":"0.4.9e"} >>> java.net.SocketTimeoutException: connect timed out

[2014-01-03 18:30:51.538] "93.190.92.76": {"shareAddress":true,"port":7874,"platform":"PC","application":"NRS","scheme":"http","requestType":"getInfo","version":"0.4.9e"} >>> java.net.ConnectException: Connection refused

[2014-01-03 18:31:43.859] "nxt20.tweetmondo.com": {"shareAddress":true,"port":7874,"platform":"PC","application":"NRS","scheme":"http","requestType":"getInfo","version":"0.4.9e"} >>> java.net.SocketTimeoutException: connect timed out

[2014-01-03 18:32:07.268] "91.115.213.16": {"shareAddress":true,"port":7874,"platform":"PC","application":"NRS","scheme":"http","requestType":"getInfo","version":"0.4.9e"} >>> java.net.SocketTimeoutException: connect timed out

[2014-01-03 18:32:48.296] "nxt12.tweetmondo.com": {"shareAddress":true,"port":7874,"platform":"PC","application":"NRS","scheme":"http","requestType":"getInfo","version":"0.4.9e"} >>> java.net.SocketTimeoutException: connect timed out
Here is the log file
full member
Activity: 160
Merit: 100
I sent 100k nxt to the peercover NXT Gateway.
How much time is needed for them to appear on my balance?

It took me over 48 hours... DGEX is better.
full member
Activity: 154
Merit: 100
Does anyone see a fundamental reason why nxt is falling on dgex? Transaction fees are against dgex but not against nxt..

don't worry, the NXT price will up going.
only bad thing is the DGEX change fees without pre-notice.
they complain that lost NXT because of 0 fee for transaction but never talk about ther earn BTC from the withdraw.
legendary
Activity: 1470
Merit: 1004
Does anyone see a fundamental reason why nxt is falling on dgex? Transaction fees are against dgex but not against nxt..

People are willing to sell at a lower price.  That is typically how it works.
legendary
Activity: 1372
Merit: 1000
Quote
Also it doesn't help the price when the source is released, and the first things being said are that there are 3 major, fatal flaws with it. If that doesn't stop a buyer, I don't know what will.

Quote
I agree.  That wasn't done properly.

Quote
I disagree. Those bounties will help find other potential flaws in code more than any occasional code reviewer.

I agree with you there.  It's the PR aspect that wasn't handled properly.
legendary
Activity: 1176
Merit: 1134
I sent 100k nxt to the peercover NXT Gateway.
How much time is needed for them to appear on my balance?

10 confirmations, so about 13 minutes
member
Activity: 94
Merit: 10
The main reason for 1.4% NXT withdrawal fee is that we have lost a total of approx. 800 000 NXT during the processing of 11000+ deposits and 7000+ payouts within the month in the unstable NXT network and experimental API, plus our own software in the quick time to market and extremely risky circumstances.

If you think that's too much of a loss, you should have attempted to run the whole show yourself. There ALWAYS are losses in realtime payment processing. They need to be budgeted.

Yet at the same time, we have not complained but have enabled for the community 10000% value increase for their NXT, and through operating nextcoin.org and dgex.com have been a crucial factor in the expansion of NXT adoption.

Now, with the 800 000 NXT deficit, how would you suggest we recover that if not as fees from those who have benefited from us making live trading available in the first place (the customers)? Any suggestions are welcome!

Fees cover the facilities, and they cover the risks. We deal with it, and so should our customers.


So the main reason for the additional fees is a loss. I understand this is not the goal of a business. You provided a service and earned revenue from it (fees, ask-bid margin and other trading engine profits, forging, possible other sources of profit I'm not aware of since I don't run an exchange Smiley) But those profits are OK and fair I suppose, since everybody assumes they are there. But incurring an inexpected loss should not be a reason or an excuse to become unfair to your customers.

You ask for any suggestions. It's possible to give one. But first some thoughts about your comments and arguments:

First, regarding your loss: You have the database with all the accounts and all the transactions. With some additional effort it should be possible to show, explain or even prove what caused your losses.
Nevertheless, together with your first message about your loss, you quickly give a few uncertain indications about possible causes of your loss(es):
  • "unstable NXT network" OK. Who is responsible for that? Not the dgex customers IMO. On the contrary. Since all of them probably ran an NRS that helped to stabilize the network.
  • "experimental API" OK. Who is responsible for that? Not the dgex customers IMO.
  • "our own software" OK. Who is responsible for that? Your FAQ claims "We have more than a decade's experience in combatting e-currency hackers of a wide variety, and two years' intensive experience of the Bitcoin tricksters." Your customers probably trusted you. Should they be punished?
  • "quick time to market" OK. But your FAQ also mentions "DGEX started by trading Freicoin", so I suppose you've used the software before Nxt started in November, right. And who forced you to come quickly to the market. That was your own decision, not one of your customers.
  • "extremely risky circumstances" OK. If your customers added risk, you should try everything to identify those instead of blaming and charging everybody.

Second, regarding your logic to recover these losses:
  • "have enabled for the community 10000% value increase". Not all your customers have benefited from this value increase. Yes, the early adopters (73 owners/founders/stakeholders and other). And they might have been gone from your exchange already @ 0 fee. I'm even sure some of your current customers are losing money.
  • "as fees from those who have benefited from us" OK. But as already indicated, the group of dgex users who have benefited and the group of all customers @ the time of the increased fee announcement are two groups that are not the same.
  • "Fees cover the facilities, and they cover the risks. We deal with it, and so should our customers." OK. I understand you're mad about the loss. But you can only expect your customers to deal with it the way you propose if your terms are announced upfront. Now you have suddenly a lot of customers who feel themselves imprisoned and they clearly don't like it. And as a business, you should try to keep your customers happy or satisfied I suppose. Unless ... That's up to you.

Your solution of increasing fees for all customers is a quick and easy one. But not the right one as I'm sure you understand. I hope you also care, as I think you do, because you remain a visitor of the forum.

So, finally, my suggestion: Please provide more info about the possible causes of your loss(es). I'm sure the community (including the large holders) can help to come up with proper and fair solutions.

I hope you can put in the extra effort to come up with that extra info and you will reconsider your fee structure after proper alternatives to recover your loss(es)
legendary
Activity: 2142
Merit: 1010
Newbie
sr. member
Activity: 441
Merit: 250
Does anyone see a fundamental reason why nxt is falling on dgex? Transaction fees are against dgex but not against nxt..
legendary
Activity: 2142
Merit: 1010
Newbie
Its already running close to one hour now and ist still on block 1. I have 19 connected peers....do you think adding peers manually would help?
If so, do you by any chance have a link to a peer list and how to add them?
Thanks

Use http://nxtra.org/nodes/ to get peers.

Switch "communicationLoggingMask" to "3" and send me log after 5 mins of working.

OK, did as you sad...but I think I will be unable to send you a log file as strangly there are none (I am looking in the "logs" folder, is this correct? )...
Also I am now running fo a couple of minuts and its the same story as before, though this time I only have 3 conected peers....but more should drop in as time passes.

Run "java -jar start.jar > log.txt" and send me log.txt file.
sr. member
Activity: 392
Merit: 250
I sent 100k nxt to the peercover NXT Gateway.
How much time is needed for them to appear on my balance?
full member
Activity: 160
Merit: 100
NXT is great, the fees are reasonable, becaues NXT is more risky than Bitcoin. Stop worrying, start trading.
hero member
Activity: 695
Merit: 500
Its already running close to one hour now and ist still on block 1. I have 19 connected peers....do you think adding peers manually would help?
If so, do you by any chance have a link to a peer list and how to add them?
Thanks

Use http://nxtra.org/nodes/ to get peers.

Switch "communicationLoggingMask" to "3" and send me log after 5 mins of working.

OK, did as you sad...but I think I will be unable to send you a log file as strangly there are none (I am looking in the "logs" folder, is this correct? )...
Also I am now running fo a couple of minuts and its the same story as before, though this time I only have 3 conected peers....but more should drop in as time passes.
full member
Activity: 154
Merit: 100
totally agreed!one more point,NXT is 2nd version of ripple!or we can call NXT as color xrp, of course, not now, must wait untill all the worked planned for NXT done!

(Where have I seen these exclamation marks?......)

here you see! Cheesy

BTW, on the first page,MR.2Kool4Skewl use the “ripple giveaway” as his signature and which still open, therefore, i think MR.2kool4skewl must one of the ripple fans.
legendary
Activity: 2142
Merit: 1010
Newbie
Perhaps - but can you clarify how this works? Does the client (or node that initially creates the transaction) lookup the alias at time of transaction to get the account ID, and then create a transaction with that account ID as recipient; or does it create a transaction with that alias as recipient (with the forging node doing the alias lookup when the block is forged)? If it is the latter, what format does the API expect the alias to be? E.g. '123456789', 'acct:123456789', 'acct:123456789@nxt', etc? Could it handle more complex alias URIs that bundle not only account number but also email address, web address, etc?

The latter. Format is not standardized yet, community should do it.
full member
Activity: 196
Merit: 100


EpicThomas -

It is a generous offer for you to say you will donate your personal holdings of around 50K NXT to cover lost coins.  If we are unable to arrange getting the bandit accounts emptied back to their original owners, I think you should plan on doing this as restitution.  I have an second account with only 10 NXT in it that I use for testing with Raspberry Pi.   Its number is 16092180239932658439.    Any coins you put in there I will make sure get distributed to the people who have lost NXT from infected clients.  I will publicly post just this one paragraph of our ongoing discussion so the forum group can police my handling of any NXT you choose to surrender in this manner.
sr. member
Activity: 378
Merit: 250
With this talk about sending to alias, do you have any thoughts on my question about what/when does the alias lookup?

As a side question: one important feature for nxt is the ability to send funds to a named alias rather than a number. I can see this being implemented in two ways:

1. Purely client side. The client looks up the alias to get the account ID, and then creates a transaction with that account (not alias) as the recipient
2. Within network/API. The client creates a transaction with the alias as the recipient, and the network (i.e. forging node, and other nodes through validation) translates the alias into an account id at time of forging

The second seems to me to be cleaner and preferred. Example: a transaction might take hours to get processed, and what's important is the account that the alias corresponds to at the time it gets processed, not when it is initially shoved into the network.

However, this would require API changes. And so any URI conventions that are adopted by browser extensions/addons would need to be adopted into the API.

Another point in favour of #2: I would rather see in the block chain a transaction that says I sent to 'bob', not to '123456789'.


"Send to alias" payment should solve this, right?

Perhaps - but can you clarify how this works? Does the client (or node that initially creates the transaction) lookup the alias at time of transaction to get the account ID, and then create a transaction with that account ID as recipient; or does it create a transaction with that alias as recipient (with the forging node doing the alias lookup when the block is forged)? If it is the latter, what format does the API expect the alias to be? E.g. '123456789', 'acct:123456789', 'acct:123456789@nxt', etc? Could it handle more complex alias URIs that bundle not only account number but also email address, web address, etc?
hero member
Activity: 695
Merit: 500
Its already running close to one hour now and ist still on block 1. I have 19 connected peers....do you think adding peers manually would help?
If so, do you by any chance have a link to a peer list and how to add them?
Thanks

did you try 0.4.9e yet? it's actually more stable and has more peers in the web.xml file.

http://info.nxtcrypto.org/client-update-0-4-9e-beta/

Yes, thats the version I am using right now
Jump to: