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

Come-from-Beyond

legendary

Activity: 2142

Merit: 1010

Newbie

Quote from: ?? on ??

Quote from: Come-from-Beyond on December 25, 2013, 01:33:09 PM

Announcement:
We are moving further on our way to decentralization. Soon I'll stop updating well-known peers in web.xml.
U (community) should cooperate and decide how u will share well-known peers addresses.
I'll make it a bit more convenient to edit the list. This will be a text file next to start.jar.

Sounds great.

Will it be an ip address per line?

We can use both ways.

EmoneyRu

hero member

Activity: 600

Merit: 500

Nxt-kit developer

Quote from: Ardolafat on December 25, 2013, 09:35:51 PM

Quote from: nexern on December 25, 2013, 09:30:29 PM

----------------------------------------------
blockexplorer update
----------------------------------------------

here is a nice example (1.721 registered aliases) -> http://87.230.14.1/nxt/nxt.cgi?action=4000&acc=2345678935869777788

cybersquatter Grin

Yes, I am

P.S. someone (1484707122620701696) covered my expenses on them. Thanks! Roll Eyes

Meizirkki

hero member

Activity: 616

Merit: 500

Quote from: Meizirkki on December 25, 2013, 11:47:48 PM

Quote from: BitAddict on December 25, 2013, 10:56:21 PM

Quote from: Meizirkki on December 25, 2013, 10:53:41 PM

Why are there so many unconfirmed transactions?

I can see only one unconfirmed. I think it is not working properly for you.

Is it possible the network is split? At the time of writing my earlier post I had 2400 unconfirmed transactions and a "well known" peer 78.46.63.221 was blacklisted (and would blacklist immediately again if I unlisted it). Sometimes the block page would show 800 orphaned blocks too, but it seemed to fix when I reloaded the page.

I restarted the node while ago and I'm seeing very few unconfirmed transactions now.

EDIT: Could have been my fault. I was running a hallmarked node without myaddress specified in web.xml
EDIT2: Is this a bug?

Sorry for the monologue.

I'm now having no other issues except for few major nodes disconnecting me (banning?)

Is this normal?

EDIT: reinstalled nxt and no longer halmarked. everything ok so far

NxtChoice

full member

Activity: 238

Merit: 100

Questions on hallmark:

How to set the weight, and the date to get the hallmark?

Should I set the weight as the number of coins in my account?

msin

legendary

Activity: 1470

Merit: 1004

Quote from: opticalcarrier on December 25, 2013, 11:49:21 PM

Quote from: lophie on December 25, 2013, 11:09:36 PM

Guys can someone please link me to a proper hallmark thing wiki page where I can get some info on that. I am going all out and installing at least 10 nodes, hallmarked. Just tell me what I can do to help, Not being able to forge is really pissing me off....

https://nextcoin.org/index.php/topic,607.0.html

personally i would not forge on a VPS. Its possible for provider to read passphrase in memory that way. I have 6 halmarked VPSs now, adding more, an only forge on my local PC

Good point, although forging on VPS is a lot easier to manage.

gbeirn

full member

Activity: 126

Merit: 100

Quote from: lophie on December 25, 2013, 11:56:49 PM

Quote from: opticalcarrier on December 25, 2013, 11:49:21 PM

Quote from: lophie on December 25, 2013, 11:09:36 PM

Guys can someone please link me to a proper hallmark thing wiki page where I can get some info on that. I am going all out and installing at least 10 nodes, hallmarked. Just tell me what I can do to help, Not being able to forge is really pissing me off....

https://nextcoin.org/index.php/topic,607.0.html

personally i would not forge on a VPS. Its possible for provider to read passphrase in memory that way. I have 6 halmarked VPSs now, adding more, an only forge on my local PC

Please share the pec of the VPSes I am planning on budgetVM the one with 1024MB burt ram, do you think they will work just fine? The original post suggests 1-2GB.

I have mix of both 1GB and 2GB, they seem to have no difference as far as I can tell. I set the Java run command with different arguments based on the RAM differences though.

gbeirn

full member

Activity: 126

Merit: 100

Quote from: lophie on December 25, 2013, 11:36:58 PM

just to check again, so the hallmarked nodes are just overtrusted because they were made by a stakeholder? they are not forging as well Sad

?

Hallmarking makes no difference in forging blocks. It does help the network however

joefox

full member

Activity: 210

Merit: 100

Quote from: MadCow on December 25, 2013, 11:37:28 PM

I'm running I can see from the block explorer that my NXT client is up to date, but every time I try to send NXT to another account the transaction does not work, but the client 'send' confirmation does pop-up. The transaction does not appear in my transaction history as a fail - it just doesn't appear anywhere. I've tried to register alias names using localhost, and they always fail too.

Is it possible your computer does not have the correct time? You should get your system time from the network. Nxt will reject any transactions with a timestamp that is more than 15 seconds ahead of the network time.

lophie

hero member

Activity: 924

Merit: 1001

Unlimited Free Crypto

Quote from: opticalcarrier on December 25, 2013, 11:49:21 PM

Quote from: lophie on December 25, 2013, 11:09:36 PM

Guys can someone please link me to a proper hallmark thing wiki page where I can get some info on that. I am going all out and installing at least 10 nodes, hallmarked. Just tell me what I can do to help, Not being able to forge is really pissing me off....

https://nextcoin.org/index.php/topic,607.0.html

personally i would not forge on a VPS. Its possible for provider to read passphrase in memory that way. I have 6 halmarked VPSs now, adding more, an only forge on my local PC

Please share the pec of the VPSes I am planning on budgetVM the one with 1024MB burt ram, do you think they will work just fine? The original post suggests 1-2GB.

ferment

full member

Activity: 168

Merit: 100

IDEX - LIVE Real-time DEX

Quote from: mtbitcoin on December 25, 2013, 11:16:12 PM

May I know where are you all downloading the "0.4.7e" version from? The first link point to 0.4.4

http://files.nxtbase.com/nrs-0.4.7e.zip

opticalcarrier

full member

Activity: 238

Merit: 100

Quote from: lophie on December 25, 2013, 11:09:36 PM

Guys can someone please link me to a proper hallmark thing wiki page where I can get some info on that. I am going all out and installing at least 10 nodes, hallmarked. Just tell me what I can do to help, Not being able to forge is really pissing me off....

https://nextcoin.org/index.php/topic,607.0.html

personally i would not forge on a VPS. Its possible for provider to read passphrase in memory that way. I have 6 halmarked VPSs now, adding more, an only forge on my local PC

Meizirkki

hero member

Activity: 616

Merit: 500

Quote from: BitAddict on December 25, 2013, 10:56:21 PM

Quote from: Meizirkki on December 25, 2013, 10:53:41 PM

Why are there so many unconfirmed transactions?

I can see only one unconfirmed. I think it is not working properly for you.

Is it possible the network is split? At the time of writing my earlier post I had 2400 unconfirmed transactions and a "well known" peer 78.46.63.221 was blacklisted (and would blacklist immediately again if I unlisted it). Sometimes the block page would show 800 orphaned blocks too, but it seemed to fix when I reloaded the page.

I restarted the node while ago and I'm seeing very few unconfirmed transactions now.

EDIT: Could have been my fault. I was running a hallmarked node without myaddress specified in web.xml
EDIT2: Is this a bug?

MadCow

hero member

Activity: 655

Merit: 500

I'm running the latest version of NXT. I open my account using localhost in my browser. I can see from the block explorer that my NXT client is up to date, but every time I try to send NXT to another account the transaction does not work, but the client 'send' confirmation does pop-up. The transaction does not appear in my transaction history as a fail - it just doesn't appear anywhere. I've tried to register alias names using localhost, and they always fail too.

It looks like I can receive blocks from the network (my client is up to date), but my client can't send transactions out to the network. What am I doing wrong? Could this be a firewall problem (i'm using Windows 7 and google chrome).

Is there a setting in web.xml that might be blocking my send transactions, even though I can still receive blocks?
Thanks for any help! I've been trying things for days now and I'm very frustrated Sad

lophie

hero member

Activity: 924

Merit: 1001

Unlimited Free Crypto

just to check again, so the hallmarked nodes are just overtrusted because they were made by a stakeholder? they are not forging as well Sad

?

gbeirn

full member

Activity: 126

Merit: 100

easyCopyString:
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; vps1.nxtcrypto.org; vps2.nxtcrypto.org; vps3.nxtcrypto.org; vps4.nxtcrypto.org; vps5.nxtcrypto.org; nxtwallet.com; 31.220.50.208; nxt.ddos.me; 203.174.12.17; 88.198.142.92

One thing I am going to suggest right now is staggered updates for new versions when the roll out. Unless there are critical security vulnerabilities we are dealing with or the issue with the overflow yesterday, as new versions of NRS arrive, we should update a few nodes at a time to minimize downtime and loads on the other nodes especially when under heavy DDoS.

It'll be hell on the network if every time a new release come out all the major nodes go down within 5 min of it coming out.

gbeirn

full member

Activity: 126

Merit: 100

Quote from: ferment on December 25, 2013, 11:22:59 PM

Quote from: jl777 on December 25, 2013, 10:44:50 PM

gbeirn,

Are you using cssh or equivalent? Without it there is no way I could manage 100+ servers

James

ssh automation + git + scripts = not to bad to manage 100. The hard part is designing and setting up the flow for install, version updates, blockchain preservation, monitoring, etc, etc.

Yeah it's not so terrible, plus the more familiar I am becoming with NXT the easier it is becoming to keep everything up and flowing smoothly.

ferment

full member

Activity: 168

Merit: 100

IDEX - LIVE Real-time DEX

Quote from: jl777 on December 25, 2013, 10:44:50 PM

gbeirn,

Are you using cssh or equivalent? Without it there is no way I could manage 100+ servers

James

ssh automation + git + scripts = not too bad to manage 100. The hard part is designing and setting up the flow for install, version updates (experimental vs norm), blockchain preservation, monitoring, etc, etc. yeahaw nxt devops.

gbeirn

full member

Activity: 126

Merit: 100

Quote from: jl777 on December 25, 2013, 11:19:20 PM

gbeirn,

I setup about 16 to 25 servers into a single cluster. Then I can type a single command, they all do it. You can also drill down to each single server.

Really, after more than 5, you have to get cssh. Trust me on this. On the Mac csshX is even better,but same core functionality

James

Oh this sounds awesome. I'm off to bed tonight but I will check it out tomorrow and then maybe expand even more.

Thanks!

gbeirn

full member

Activity: 126

Merit: 100

Quote from: mtbitcoin on December 25, 2013, 11:16:12 PM

May I know where are you all downloading the "0.4.7e" version from? The first link point to 0.4.4

Here you go:

Quote from: jl777 on December 25, 2013, 09:55:33 AM

I put a copy of 4.7e at http://209.126.73.170/nxt_4_7e.zip

Could somebody make sure it works properly?

James

jl777

legendary

Activity: 1176

Merit: 1134

gbeirn,

I setup about 16 to 25 servers into a single cluster. Then I can type a single command, they all do it. You can also drill down to each single server.

Really, after more than 5, you have to get cssh. Trust me on this. On the Mac csshX is even better,but same core functionality

James

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