|
|
|
|
|
"With e-currency based on cryptographic proof, without the need to
trust a third party middleman, money can be secure and transactions
effortless." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
Noitev
|
|
December 04, 2013, 07:31:08 PM |
|
so whats everbodys estimations on price per nxt coin come january. 0.00010000 is my guess.
Well, QRK is at 0.0002 and it bring absolutely zero to the table. So, using that as a comparison, NXT must be at 0.002 or 0.02. I think if NXT gets more exposure, it'll hit 0.0001-0.0005. Needs stable client and a way for exchanges to implement it.
|
|
|
|
klee
Legendary
Offline
Activity: 1498
Merit: 1000
|
|
December 04, 2013, 07:33:36 PM |
|
I want a Nxt/Yuan pair @btc38 - then the sky is the limit!
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1009
Newbie
|
|
December 04, 2013, 07:34:41 PM |
|
http://88.198.210.245:7874 is it true that I can create a wallet on this link?? Somebody here gave this link to me, but dont know what to do and if its safe… thanks! This is my VPS for bootstrapping. It shouldn't be used as online wallet.
|
|
|
|
pabloangello
Legendary
Offline
Activity: 1344
Merit: 1001
|
|
December 04, 2013, 07:40:00 PM |
|
I want a Nxt/Yuan pair @btc38 - then the sky is the limit!
Yep but not with this suspiciously looking client/wallet :p
|
|
|
|
opticalcarrier
|
|
December 04, 2013, 07:41:22 PM |
|
regarding transaction fees, is a > 1 integer required? what is the long term goal for calculating transactions?
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1009
Newbie
|
|
December 04, 2013, 08:00:42 PM |
|
regarding transaction fees, is a > 1 integer required? what is the long term goal for calculating transactions?
Stakeholders decide. Integer value >= 1 NXT is required by "official" client. If most of stakeholders use other soft that lets to set fee to any value (even minus 0.123 NXT), we'll get transactions with other fees.
|
|
|
|
Jean-Luc
|
|
December 04, 2013, 08:14:50 PM |
|
Which port needs to be open to allow peer connections while behind a firewall, still 7874? Now that the web interface is at 7874, is there a way to block outside users from unlocking their accounts on a node that I run (because it is not secure and I don't want to encourage it), without breaking p2p connectivity?
|
|
|
|
JohnyCrypt
Newbie
Offline
Activity: 56
Merit: 0
|
|
December 04, 2013, 08:19:30 PM |
|
Which port needs to be open to allow peer connections while behind a firewall, still 7874? Now that the web interface is at 7874, is there a way to block outside users from unlocking their accounts on a node that I run (because it is not secure and I don't want to encourage it), without breaking p2p connectivity?
Good point, I had 7874 open for P2P.
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1009
Newbie
|
|
December 04, 2013, 08:20:19 PM |
|
Which port needs to be open to allow peer connections while behind a firewall, still 7874? Now that the web interface is at 7874, is there a way to block outside users from unlocking their accounts on a node that I run (because it is not secure and I don't want to encourage it), without breaking p2p connectivity? I'll add a special option to web.xml to disable web interface.
|
|
|
|
2Kool4Skewl (OP)
|
|
December 04, 2013, 08:28:21 PM |
|
Is the P2P port still 7874?
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1009
Newbie
|
|
December 04, 2013, 08:30:16 PM |
|
Is the P2P port still 7874?
Yes
|
|
|
|
GCInc.
|
|
December 04, 2013, 08:33:18 PM |
|
So the API cannot be used remotely?
|
|
|
|
Noitev
|
|
December 04, 2013, 08:36:01 PM |
|
So, the web interface is at 7874 now for some reason...
|
|
|
|
2Kool4Skewl (OP)
|
|
December 04, 2013, 08:48:42 PM |
|
Come-from-beyond for clarification:
Port 7874 is used for P2P and http web client. Port 7875 is used for https web client. Port 7876 is used for API commands.
Is this correct?
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1009
Newbie
|
|
December 04, 2013, 08:49:00 PM |
|
So the API cannot be used remotely?
It can. Looks like I became the 2nd core dev, so I'm going to add options to restrict interface and API to a list of IPs.
|
|
|
|
JohnyCrypt
Newbie
Offline
Activity: 56
Merit: 0
|
|
December 04, 2013, 08:49:41 PM |
|
I'll add a special option to web.xml to disable web interface.
Thanks. Speaking of web.xml, does it do anything for the 'well knowness' of our client to hard code our external IP?
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1009
Newbie
|
|
December 04, 2013, 08:49:56 PM |
|
Come-from-beyond for clarification:
Port 7874 is used for P2P and http web client. Port 7875 is used for https web client. Port 7876 is used for API commands.
Is this accurate?
Yes, for 0.3.9. Next version will have only 7874 and 7875. I'll post more details when publish it.
|
|
|
|
Come-from-Beyond
Legendary
Offline
Activity: 2142
Merit: 1009
Newbie
|
|
December 04, 2013, 08:50:52 PM |
|
I'll add a special option to web.xml to disable web interface.
Thanks. Speaking of web.xml, does it do anything for the 'well knowness' of our client to hard code our external IP? It's for servlet settings as well. Will get more usage in 0.3.10.
|
|
|
|
hobbster
Newbie
Offline
Activity: 28
Merit: 0
|
|
December 04, 2013, 08:55:41 PM |
|
[2013-12-04 20:09:40.170] 33: java.lang.NullPointerException [2013-12-04 20:09:41.169] 33: java.lang.NullPointerException [2013-12-04 20:09:42.174] 33: java.lang.NullPointerException [2013-12-04 20:09:43.195] 33: java.lang.NullPointerException [2013-12-04 20:09:44.240] 33: java.lang.NullPointerException [2013-12-04 20:09:45.295] 31: java.lang.NullPointerException [2013-12-04 20:09:45.327] 33: java.lang.NullPointerException [2013-12-04 20:09:46.239] 33: java.lang.NullPointerException [2013-12-04 20:09:47.258] 33: java.lang.NullPointerException [2013-12-04 20:09:48.247] 33: java.lang.NullPointerException [2013-12-04 20:09:49.244] 33: java.lang.NullPointerException [2013-12-04 20:10:17.326] 31: java.lang.NullPointerException
|
|
|
|
|