Pages:
Author

Topic: NAS :: Descendant of NXT 100% PoS|More Exchanges|WinNAS is ready! - page 12. (Read 143776 times)

sr. member
Activity: 459
Merit: 250

Code:
03-17 02:16:09 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException:
Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-176]
Are them normal?, is it due to NAS code changes from NXT code?. I didn't shutdown the server, nor the Java VM, is there something wrong on my node?




This error appears for me when I CTRL+C to stop NAS.  I'm guessing that you stopped NAS at that time to clear the block chain and download a new copy from us.
sr. member
Activity: 459
Merit: 250
I see both of your nodes fighting to forge blocks which is good.
I see your transaction in block 259461.  Smiley

I picked up some NAS on bter.com and tried to withdrawal it but it's stuck.

The response from the support ticket is:
Quote
Dear Sir,
We will process the withdrawal as soon as we are possible

Thanks for your patience.

Hopefully this means that bter.com will come back.  Smiley
hero member
Activity: 520
Merit: 500
OK, can you tell once more how to start NAS? Correct links?
member
Activity: 93
Merit: 10
My node is now synchronized. Sometimes I stop forging, then I see the account NAS-5HZF-TPQ5-GSHF-7GV33 forging, so we are on the same blockchain.

I see just other 5 peers now, 6 with me: 
funkyvps3.funkymonkey.org; 88.130.221.201; cb2.flipflop.mooo.com; 99.227.137.145; 222.92.62.194; patapato.ddns.net

The client say: "0/5 Up-to-date Peers": is it about version number, or about blockchain?, can we correct it?

Looking into the "nas_db/nas.trace.db" file (it is plain text, despite the extension) I have 2 recurring errors, this one:
Code:
03-17 02:05:10 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException:
Table "VERSION" not found; SQL statement:
SELECT next_update FROM version [42102-176]
and this one:
Code:
03-17 02:16:09 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException:
Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-176]
Are them normal?, is it due to NAS code changes from NXT code?. I didn't shutdown the server, nor the Java VM, is there something wrong on my node?

@lcharles123, I've just send you all my forged balance, 665 NAS Wink (transaction 8730736024937643212). But, as you need an outgoing transaction *, I ask you to please donate 10 NAS to the account NAS-AXUZ-74SZ-9SB8-5SFUT, who lent me 10 NAS. That way we are testing the network.

*: "The recipient account is an unknown account, meaning it has never had an incoming or outgoing transaction. Please double check your recipient address before submitting."
member
Activity: 93
Merit: 10
So we need to reach the agreement with exchanges, am I right? To convince them to use the same blockchain and verify the transactions of users. And if they don't find some of withdrawal transactions in a blockchain, then rollback and return NAS to a balance.
But what if there were unconfirmed deposits and then a person sold NAS?
... anyway, in case of Poloniex and dgex, there was no trades. Dgex closed NAS trading a long time ago. If they also did not perform deposits and withdrawals, so any blockchain will do. As for Polo, they can easily rollback at least some of the last withdrawals, after the announsement

I agree. But I think that the network is not strong enough yet, we are few nodes, only two forgers, and we are not 24h/7d nodes (at least not me). It would be good that more people, not only exchanges run more nodes, either at home or at hosting.

Come on, people, join us to keep NAS alive!
hero member
Activity: 520
Merit: 500
So we need to reach the agreement with exchanges, am I right? To convince them to use the same blockchain and verify the transactions of users. And if they don't find some of withdrawal transactions in a blockchain, then rollback and return NAS to a balance.
But what if there are deposits unconfirmed by new blockchain and then a person sold NAS?
... anyway, in case of Poloniex and dgex, there was no trades. Dgex closed NAS trading a long time ago. If they also did not perform deposits and withdrawals, so any blockchain will do. As for Polo, they can easily rollback at least some of the last withdrawals, after the announsement
member
Activity: 93
Merit: 10
member
Activity: 68
Merit: 10
nas is best rapper alive!  Grin
sr. member
Activity: 459
Merit: 250

I disconnect every day at 09:00 AM UTC for 05-10 min in order to reconnect and prevent auto-disconnect from provider.
The DNS update should start after 5 min max and the propagation should take the longest part.

I see, ok.  So for about 15 minutes each day there's no forging until Patapato resets or someone else finds some way to gain some NAS and starts forging.  Smiley

To get  NAS exchange im very important so ..?

Not sure if I understand this correctly but to get an exchange we first need to agree on the correct fork.  Then we need to be sure there's no other forks out there that we are not aware of which might be better forks than our own.

Then we might be able to convince an exchange to resync their node with our chain to re-enable NAS trading or just hand them a public API node such as funkyvps3.funkymonkey.org:7873 to use.
newbie
Activity: 51
Merit: 0
So we're all on the same chain as you (User1397367406) then.  The nightly disconnects means that we have no one forging on our chain over night.

Patapato's node has drifted off our chain some how.  It sounds like Patapato's node is the only node that's on that fork.  All of the other nodes agree that User1397367406's blocks are correct.

If Patapato reset's their node and downloads the blockchain from the rest of us, Patapato should then be forging or fighting with User1397367406's node to forge blocks during the day, and gets all of the blocks during the night when User1397367406 is offline.

The node "funkyvps3.funkymonkey.org" is a new VPS node I setup last week.  I added my desktop as a well known peer for the chain to download and it downloaded the chain just fine matching my desktop's node.

Patapato:  If you do decide to reset your block chain, add "funkyvps3.funkymonkey.org" to your well known peers list.  You should be on the same chain as the rest of us then.

I disconnect every day at 09:00 AM UTC for 05-10 min in order to reconnect and prevent auto-disconnect from provider.
The DNS update should start after 5 min max and the propagation should take the longest part.
full member
Activity: 154
Merit: 100
To get  NAS exchange im very important so ..?
sr. member
Activity: 459
Merit: 250
So we're all on the same chain as you (User1397367406) then.  The nightly disconnects means that we have no one forging on our chain over night.

Patapato's node has drifted off our chain some how.  It sounds like Patapato's node is the only node that's on that fork.  All of the other nodes agree that User1397367406's blocks are correct.

If Patapato reset's their node and downloads the blockchain from the rest of us, Patapato should then be forging or fighting with User1397367406's node to forge blocks during the day, and gets all of the blocks during the night when User1397367406 is offline.

The node "funkyvps3.funkymonkey.org" is a new VPS node I setup last week.  I added my desktop as a well known peer for the chain to download and it downloaded the chain just fine matching my desktop's node.

Patapato:  If you do decide to reset your block chain, add "funkyvps3.funkymonkey.org" to your well known peers list.  You should be on the same chain as the rest of us then.
newbie
Activity: 51
Merit: 0
I don't understand, as I am also forging all the blocks, but I have quite the same peers than you. So it looks like we have 2 different forks with the same peers, in the same network.

... cut ...

By the way, in my client/server NAS-5HZF-TPQ5-GSHF-7GV33 has his last transaction on 06/10/2014. But he was forging on the same fork as me (NAS-H5AW-7J9F-7VCY-DJ8NB) on 20/02, this is block history on that date:
...
233218 20/02/2015 11:19:33 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 25874 %
233217 20/02/2015 11:17:34 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 13046 %
...

But I have to say that on 20/02/15 I copied the blockchain of User1397367406. My previous blockchain was not synchronizing since many days ago.


I'm thinking you some how ended up on your own fork.  Both of my nodes show NAS-5HZF-TPQ5-GSHF-7GV33 as the one forging all of the blocks.  This means my nodes agree with lcharles123's node.  Both of my nodes were started clean downloading the block chain from the peers on the network.

Chances are, your forging node and the other forging node at some point stopped talking to each other and both started forging your own threads.  When things merged back (more than 1440 blocks later) the two forging nodes couldn't rewrite history since it's too far back so you continued on your own chains while the rest of the nodes agree with chain from the other node.

I'd say take a look at the previous messages about missing transactions, period of silence (no blocks) from Nov. to Jan. and if you're node has the same missing information, scrap it and join ours.

... cut ...

Is this right?  If so, switching to our chain won't cost you anything.

If User1397367406 is still watching this thread, who do you see as the current forger of the blocks (since patapato's chain started with your download last month)?

There are at least 2 forks: patapato and mine ( NAS-5HZF-TPQ5-GSHF-7GV33 / 5802728473452724205 )
Last transaction on 06/10/2014 on my account is what i have here.

I was forging some time on the same chain as patapato (NAS-H5AW-7J9F-7VCY-DJ8NB) some time ago (saw him forging most of the blocks), can't tell exactly when it was ...
Is there a better way to look at the (forged) block than the client in a browser?

<< If User1397367406 is still watching this thread, who do you see as the current forger of the blocks (since patapato's chain started with your download last month)?
I see my node forging all the blocks, as far as i can tell from the little Blocks history.
I also tried to sync a new client with the network and ended up with the same blockchain as now (my node wasn't running at that time).
I have no clue, yet, as why i'm not able to stay on the same chain as patapato.
By the way, i'm on a daily disconnect/re-connect with IP change: should be at 09:00 UTC.
Should enable more logging on client/server to see whats going on there ...
May be it's a hallmark thing or a mutual ignore/Connection refused ...

As to the remarke from lcharles123:
<< Haven't connected to NAS network for quite some time and try to sync to these peers. From what I observe this blockchain does sync properly until Nov 17 last year, then suddenly gets no block found for more than 1.5 months until Jan 7 and then continue. This blockchain seems 'broken' for me.
Well i'd had to stop forging some time in November ( if i remember correctly there where only max 1-2 other nodes present), as i started the server again, in mid/end december it took me a while longer to sync to the network again. I think at that period there was maybe only 1 node left, if any.
If anybody has a better chain i'm willing to take it Wink

<< About the two other, some people sent NAS from Poloniex to Bter without success (Kozan, Mr.Dux, ...), and it happened at least since September 19 2014. So, the two greatest exchanges was in different fork at least since then.
I know for sure that Poloniex doesn't run a server right now. Last time i messaged them they told me that they'll be willing to re-sync there node.
At least the person i spoke to saied that i'll pass the message to there team ...
I have also an open transaction from Poloniex to my wallet.

My current peers list:

Code:
  patapato.ddns.net	0	157 MB	19 MB	NRS 1.1.3.N1	Win7-64b
  cb2.flipflop.mooo.com 0 4 MB 5 MB NRS 1.1.3.N1 PC
  funkyvps3.funkymonkey.org 0 16 MB 22 MB NRS 1.1.3.N1 VPS
  99.227.137.145 0 19 MB 28 MB NRS 1.1.3.N1 PC
  222.92.62.194 0 287 KB 2 MB NRS 1.1.3.N1 www.nascoin.org
  cb2.flipflop.mooo.com 1'314'800 16 MB 17 MB NRS 1.1.3.N1 CubieBoard2
  cb2.flipflop.mooo.com 1'314'800 10 MB 13 MB NRS 1.1.3.N1 CubieBoard2
  222.92.62.194 0 266 KB 2 MB NRS 1.1.3.N1 www.nascoin.org
  23.95.44.142 0 8 MB 11 MB NRS 1.1.3.N1 PC
sr. member
Activity: 459
Merit: 250
I don't understand, as I am also forging all the blocks, but I have quite the same peers than you. So it looks like we have 2 different forks with the same peers, in the same network.

My peers:
  cb2.flipflop.mooo.com 657'400 6 MB 149 MB NRS 1.1.3.N1 CubieBoard2
  funkyvps3.funkymonkey.org 0 3 MB 70 MB NRS 1.1.3.N1 VPS
  flipflop.mooo.com 657'400 11 MB 8 MB NRS 1.1.3.N1 CubieBoard2
  cb2.flipflop.mooo.com 0 230 KB 331 KB NRS 1.1.3.N1 CubieBoard2
  cb2.flipflop.mooo.com 657'400 24 MB 13 MB NRS 1.1.3.N1 CubieBoard2
  99.227.137.145 0 9 MB 284 MB NRS 1.1.3.N1 PC
  cb2.flipflop.mooo.com 657'400 1 MB 1 MB NRS 1.1.3.N1 CubieBoard2
  222.92.62.194 0 1 MB 4 MB NRS 1.1.3.N1 www.nascoin.org
  cb2.flipflop.mooo.com 657'400 5 MB 9 MB NRS 1.1.3.N1 CubieBoard2
  23.95.44.142 0 3 MB 110 MB NRS 1.1.3.N1 PC

By the way, in my client/server NAS-5HZF-TPQ5-GSHF-7GV33 has his last transaction on 06/10/2014. But he was forging on the same fork as me (NAS-H5AW-7J9F-7VCY-DJ8NB) on 20/02, this is block history on that date:
...
233218 20/02/2015 11:19:33 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 25874 %
233217 20/02/2015 11:17:34 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 13046 %
...

But I have to say that on 20/02/15 I copied the blockchain of User1397367406. My previous blockchain was not synchronizing since many days ago.


I'm thinking you some how ended up on your own fork.  Both of my nodes show NAS-5HZF-TPQ5-GSHF-7GV33 as the one forging all of the blocks.  This means my nodes agree with lcharles123's node.  Both of my nodes were started clean downloading the block chain from the peers on the network.

Chances are, your forging node and the other forging node at some point stopped talking to each other and both started forging your own threads.  When things merged back (more than 1440 blocks later) the two forging nodes couldn't rewrite history since it's too far back so you continued on your own chains while the rest of the nodes agree with chain from the other node.

I'd say take a look at the previous messages about missing transactions, period of silence (no blocks) from Nov. to Jan. and if you're node has the same missing information, scrap it and join ours.

On my nodes, I see your account NAS-H5AW-7J9F-7VCY-DJ8NB has 22'000'670.0038 NAS with the last transactions of:
Date   Type   Amount   Fee   Account
21/02/2015 16:06:15   Ordinary payment      10   1   NAS-H5AW-7J9F-7VCY-DJ8NB
20/02/2015 05:22:52   Alias assignment      0   1   NAS-MRCC-2YLS-8M54-3CMAJ
24/06/2014 15:30:34   Ordinary payment      21'900'009.0038   1   NAS-H5AW-7J9F-7VCY-DJ8NB
24/06/2014 03:43:38   Ordinary payment      11   1   NAS-QNSP-RHXF-R4JB-B2SL5
24/06/2014 03:37:23   Alias assignment      0   1   NAS-MRCC-2YLS-8M54-3CMAJ
23/06/2014 20:46:04   Ordinary payment      100'000   1   NAS-H5AW-7J9F-7VCY-DJ8NB

Is this right?  If so, switching to our chain won't cost you anything.

If User1397367406 is still watching this thread, who do you see as the current forger of the blocks (since patapato's chain started with your download last month)?
member
Activity: 93
Merit: 10
About exchanges, there has been just 4 exchanges trading NAS:
    Poloniex, DGEX, Bter and BTC38. [/li][/list]

It is clear that DGEX is not running a node now.

It is clear for me that BTC38 has no running a node, as it has not withdraw or deposit option (it trades smoke called NAS, not real NAS).

About the two other, some people sent NAS from Poloniex to Bter without success (Kozan, Mr.Dux, ...), and it happened at least since September 19 2014. So, the two greatest exchanges was in different fork at least since then.

Recently User1397367406 said:
I know for sure that Polionex does not run a node/wallet right now.

I'm in doubt that Bter is running a node also.
member
Activity: 93
Merit: 10
I have 3 conecteds peers:
cb2.flipflop.mooo.com ... CubieBoard2
99.*.137.145
222.*.62.194

Send-me please. Smiley
NAS-VBK9-5ZXA-CJQ8-GEWVU


Haven't connected to NAS network for quite some time and try to sync to these peers. From what I observe this blockchain does sync properly until Nov 17 last year, then suddenly gets no block found for more than 1.5 months until Jan 7 and then continue. This blockchain seems 'broken' for me.

Anyone knows the same issue found on other fork(s) as well? Could anyone post the peers of other fork(s) so we can compare?

This account forge all blocks for me: NAS-5HZF-TPQ5-GSHF-7GV33
Here is a example of a block, if you want to compare
Block: 258433
Hash: 7115900780532831094
timestamp: 30758915 (3/16/2015 12:08:35 GMT)

Peers:
  funkyvps3.funkymonkey.org   0   32 MB   2 MB   NRS 1.1.3.N1   VPS
  patapato.ddns.net   0   102 MB   3 MB   NRS 1.1.3.N1   Win7-64b
  99.*.137.145   0   91 MB   2 MB   NRS 1.1.3.N1   PC
  cb2.flipflop.mooo.com   986'100   5 MB   3 MB   NRS 1.1.3.N1   CubieBoard2
  222.*.62.194   0   74 MB   1 MB   NRS 1.1.3.N1   www.nascoin.org
  cb2.flipflop.mooo.com   986'100   1 MB   936 KB   NRS 1.1.3.N1   CubieBoard2
  cb2.flipflop.mooo.com   986'100   140 MB   6 MB   NRS 1.1.3.N1   CubieBoard2
  cb2.flipflop.mooo.com   0   120 KB   88 KB   NRS 1.1.3.N1   CubieBoard2
  23.*.44.142   0   4 MB   4 MB   NRS 1.1.3.N1   


I don't understand, as I am also forging all the blocks, but I have quite the same peers than you. So it looks like we have 2 different forks with the same peers, in the same network.

My peers:
  cb2.flipflop.mooo.com 657'400 6 MB 149 MB NRS 1.1.3.N1 CubieBoard2
  funkyvps3.funkymonkey.org 0 3 MB 70 MB NRS 1.1.3.N1 VPS
  flipflop.mooo.com 657'400 11 MB 8 MB NRS 1.1.3.N1 CubieBoard2
  cb2.flipflop.mooo.com 0 230 KB 331 KB NRS 1.1.3.N1 CubieBoard2
  cb2.flipflop.mooo.com 657'400 24 MB 13 MB NRS 1.1.3.N1 CubieBoard2
  99.227.137.145 0 9 MB 284 MB NRS 1.1.3.N1 PC
  cb2.flipflop.mooo.com 657'400 1 MB 1 MB NRS 1.1.3.N1 CubieBoard2
  222.92.62.194 0 1 MB 4 MB NRS 1.1.3.N1 www.nascoin.org
  cb2.flipflop.mooo.com 657'400 5 MB 9 MB NRS 1.1.3.N1 CubieBoard2
  23.95.44.142 0 3 MB 110 MB NRS 1.1.3.N1 PC

By the way, in my client/server NAS-5HZF-TPQ5-GSHF-7GV33 has his last transaction on 06/10/2014. But he was forging on the same fork as me (NAS-H5AW-7J9F-7VCY-DJ8NB) on 20/02, this is block history on that date:
...
233218 20/02/2015 11:19:33 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 25874 %
233217 20/02/2015 11:17:34 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 13046 %
...

But I have to say that on 20/02/15 I copied the blockchain of User1397367406. My previous blockchain was not synchronizing since many days ago.

legendary
Activity: 1697
Merit: 1074
I have 3 conecteds peers:
cb2.flipflop.mooo.com ... CubieBoard2
99.*.137.145
222.*.62.194

Send-me please. Smiley
NAS-VBK9-5ZXA-CJQ8-GEWVU


Haven't connected to NAS network for quite some time and try to sync to these peers. From what I observe this blockchain does sync properly until Nov 17 last year, then suddenly gets no block found for more than 1.5 months until Jan 7 and then continue. This blockchain seems 'broken' for me.

Anyone knows the same issue found on other fork(s) as well? Could anyone post the peers of other fork(s) so we can compare?

This account forge all blocks for me: NAS-5HZF-TPQ5-GSHF-7GV33
Here is a example of a block, if you want to compare
Block: 258433
Hash: 7115900780532831094
timestamp: 30758915 (3/16/2015 12:08:35 GMT)

Peers:
  funkyvps3.funkymonkey.org   0   32 MB   2 MB   NRS 1.1.3.N1   VPS
  patapato.ddns.net   0   102 MB   3 MB   NRS 1.1.3.N1   Win7-64b
  99.*.137.145   0   91 MB   2 MB   NRS 1.1.3.N1   PC
  cb2.flipflop.mooo.com   986'100   5 MB   3 MB   NRS 1.1.3.N1   CubieBoard2
  222.*.62.194   0   74 MB   1 MB   NRS 1.1.3.N1   www.nascoin.org
  cb2.flipflop.mooo.com   986'100   1 MB   936 KB   NRS 1.1.3.N1   CubieBoard2
  cb2.flipflop.mooo.com   986'100   140 MB   6 MB   NRS 1.1.3.N1   CubieBoard2
  cb2.flipflop.mooo.com   0   120 KB   88 KB   NRS 1.1.3.N1   CubieBoard2
  23.*.44.142   0   4 MB   4 MB   NRS 1.1.3.N1   
sr. member
Activity: 459
Merit: 250
I'm not aware of any other forks right now.  As far as I know, you're seeing the only fork of NAS right now.

As for the 1.5 month quiet period; it's most likely that there were no forging nodes online during that time period.
sr. member
Activity: 271
Merit: 250
Share Love
I have 3 conecteds peers:
cb2.flipflop.mooo.com ... CubieBoard2
99.*.137.145
222.*.62.194

Send-me please. Smiley
NAS-VBK9-5ZXA-CJQ8-GEWVU


Haven't connected to NAS network for quite some time and try to sync to these peers. From what I observe this blockchain does sync properly until Nov 17 last year, then suddenly gets no block found for more than 1.5 months until Jan 7 and then continue. This blockchain seems 'broken' for me.

Anyone knows the same issue found on other fork(s) as well? Could anyone post the peers of other fork(s) so we can compare?
sr. member
Activity: 326
Merit: 250
I think Poloniex problem should be solved somehow. They forced people to withdraw their NAS, and now will everything be lost? Maybe they can rollback, cancel withdrawals and use other blockchain, the one you use?
Also note that there is lot of NAS in dgex accounts. They don't trade NAS now, but it's kept in accounts, I can see NAS balance. All my NAS is on dgex and on the way from POLO to BTER. Both more than 100 million. If I get back all my NAS I'll donate 15 million.

If they're forcing people to withdraw their NAS then they must either be connected to a different fork or the API of public nodes.  Before asking them to switch to our fork we should probably find out if they're connected on another fork.  It's possible there's another small group of nodes out there that might be more active.

I tried to withdraw NAS from Poloniex yesterday and withdrawals were frozen for me.
Pages:
Jump to: