elective-stereophonic
elective-stereophonic
Show Posts - Meizirkki
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Meizirkki

Pages: [1] 2 3 4
1
Nxt General Discussion / For the love of BCNext lower the fees!
« on: October 25, 2014, 01:29:59 pm »
block reward would encourage to hoard coins instead of offering bounties.

This is already the case without block reward. Whales keep hoarding because their stake grows by itself every day. Lowering the fees would help Nxt grow. DO IT!

2
Interested.

Nxt: Meizirkki
BTT: Meizirkki

3
Nxt Client Helpdesk / Re: Java connects to random localhost 51xxx port?
« on: October 07, 2014, 05:42:25 pm »
I changed my whitelist to exclude all ports except 7874 for Java.. I suppose that should be secure..

I guess I'll just have to disable FW notifications altogether, this is driving me nuts :P

Should I flush my stash just in case someone actually got in ?

EDIT: btw, it's now tried ports up to 58000 already :D

4
Nxt Client Helpdesk / Re: Java connects to random localhost 51xxx port?
« on: October 07, 2014, 05:17:56 pm »
What version of your Java? The one with NSA backdoor that spies on Nxt users?
7 update 67

Never heard of the backdoor please go on.

5
Nxt Client Helpdesk / Re: Java connects to random localhost 51xxx port?
« on: October 07, 2014, 03:14:32 pm »
It has now moved up to 52xxx and I noticed right after (or before not sure in which order the list is :D ) each blocked attempt to localhost there's an allowed connection to an address that doesn't make any sense, with the same port.


6
Nxt Client Helpdesk / Java connects to random localhost 51xxx port?
« on: October 07, 2014, 03:01:00 pm »
I'm using the latest Wesleyh Nxt Wallet app with NXT 1.2.8 on OS X 10.9.

My firewall constantly notifies me (more than once a minute) of the Java process connecting to (or getting connected to from) a seemingly random port in the range of 51xxx.

Is this Nxt? I'm not running any other Java applications.
If so, is it important?

Java is on my firewall's whitelist but for some reason these connections get blocked anyway.

7
Nxt Community News and Announcements / Re: [ANN] Jinn
« on: September 23, 2014, 04:39:48 pm »
Could you share further details about the hardware design, and how far have you already got with it?

8
Jinn / Re: where is it?
« on: September 23, 2014, 04:10:55 pm »
Timer ran out. Hashes don't match. Scam.  :D

9
Nxt General Discussion / Re: Price speculation
« on: September 12, 2014, 09:06:30 pm »
Have any of you noticed that the market cap of most popular Nxt assets is several hundred million $ while Nxt itself is only around 40 ?

What's up with that? Either assets are seriously overvalued or Nxt seriously undervalued??

10
Nxt General Discussion / Re: Price speculation
« on: September 03, 2014, 12:13:18 am »
I installed nxtty today. Very cool yet many things difficult/unstable. I never understood what exactl the nxttycoins do.

11
Nxt General Discussion / Re: BitSharesX Onslaught
« on: August 26, 2014, 03:20:47 pm »
One of the bubbles I wish I didn't miss ;D

12
Nxt General Discussion / Re: Price speculation
« on: August 25, 2014, 04:21:59 pm »
Nxt to the mooon!

13
Nxt General Discussion / Re: When will Nxt fees be decreased?
« on: August 25, 2014, 04:20:05 pm »
FOR THE GOOD OF NXT, LET THE SPAMMING BEGIN  :D

14
Nxt General Discussion / Re: When will Nxt fees be decreased?
« on: August 24, 2014, 06:44:47 pm »
This has been brought up repeatedly for at least the past 6 months. Good to know it's finally taken into consideration.

15
Nxt General Discussion / Re: 1.2.7 NRS
« on: August 23, 2014, 04:36:12 pm »
JL is using it in main net.

16
Nxt General Discussion / Re: BitSharesX Onslaught
« on: August 21, 2014, 06:23:05 pm »
I'd call it a bubble as well. Just like Darkcoin/Auroracoin etc. Speculation.

17
General / Re: Forging questions
« on: August 19, 2014, 03:46:45 pm »
Nxt nodes need to know global time to function properly. Every block contains timestamp which must be greater than timestamp of the previous block but not greater than [current time + 15 seconds].

If u delay ur block then success of accepting it by the network is determined by the topology and the "Longest chain wins" rule.

Ok; let's apply the longest chain rule.

   One chain goes ... <- A -< B
and another goes ... <- A <- C

Now, C actually has a lower hit and thus the 2nd chain is longer, BUT
C's timestamp is close to current time + 15 sec. Let's say half the peers
consider it past 15 secs (thus rejecting the block) and half see it as within 15 secs
(thus accepting it). How is this split resolved?
Unless half the networks nodes time is set incorrectly, how could that scenario happen?

EDIT: Forger time set 15 sec in the future?

18
Bitpay  ;D

19
ANY KIND OF REWRITE HOWEVER SMALL IS THE FIRST STEP TOWARDS CENSORSHIP. The first step towards big forgers collaborating to control who can use Nxt and what for. If this becomes reality, a goverment or any private entity with a lot of money can simply bribe forgers to turn Nxt into PayPal.

Let's not make the first step!

20
Lets not rewrite history

Pages: [1] 2 3 4
elective-stereophonic
elective-stereophonic
assembly
assembly