 Show Posts
|
|
Pages: « 1 2 [3] 4 5 »
|
Hey!, I am synchronized again  I didn't stop my node, just I stopped to forge and it synchronized after 5.5 hours, here is the block history of that time (GMT+1): ... 260632 18/03/2015 23:00:54 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 8708 % 260631 18/03/2015 22:59:17 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 5386 % 260630 18/03/2015 16:29:59 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 2693 % 260629 18/03/2015 16:28:10 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 1482 % ... Thank you, User1397367406. I didn't set a hallmark, I really don't know what exactly it is, but I will read tomorrow how to do it. Meanwhile I prefer to stay without forging, I will start and stop forging occasionally to test it. I can lease my balance to tiker for few days, do you want it, tiker? |
|
|
|
I saw patapato forging today  @User1397367406, good to see you yesterday too But I can not see you today when I stop forging. Do you see me today?, are you forging?, are we on different fork again  ? I think you're forked again. All of the blocks are forged by NAS-5HZF-TPQ5-GSHF-7GV33 on both of my nodes. (If you ever want to check another node, you can use http://funkyvps3.funkymonkey.org:7873 and check the blocks... just don't use a password with funds... I use "hello" as my phrase when logging in here..) If you (Patapato) have forked again, how is that possible? The fork would begin if one of the forging nodes loses connectivity to the other forging node but continues to forge new blocks on its own. (Example: User1397367406 resets internet connection so the node continues to forge but on its own since it can't communicate with the other nodes.) As long as the two forging nodes meet up again before 1440 blocks have passed they should be able to agree on a chain and go from there. Now if the problem was User1397367406's node going offline and causing the problem then the rest of us would agree with Patapato's node but for some reason we all agree with User1397367406. Is your node disconnected from the web but still forging for any long periods of time? (I really wish bter.com would send me my NAS so that we have a more permanent forging node running from funkyvps3.) Thank you for your public NAS browser, tiker, and for explanation. I didn't stopped my node since my recent reset of blockchain, I just stopped forging sometimes to test if I can see the other forger. Yesterday I saw him all the day. I think that my connection was alive all the time. It is a dynamic IP, I am using noip.com to get a fixed domain, as suggested by NXT wiki The maximum time to reassign IP to my dynamic name is 5 minutes, or 5 blocks (well, one block is enough to fork , fast blocks of NAS are against network stability). I have just one node, I think that User1397367406 has several nodes, probably all of them forging, isn't it?, so his forging is more stable against internet or machine problems. Maybe the rest of you has greater chance of finding him, as well. Or maybe just that he is before me on your nas.wellKnownPeers list. You are right about that our nodes have to agree when reconnecting, but how can just 2 forgers agree?, if there is needed a majority for the agreement then we need at least 3 forgers to keep the network stable, am I right? |
|
|
|
I saw patapato forging today @User1397367406, good to see you yesterday too But I can not see you today when I stop forging. Do you see me today?, are you forging?, are we on different fork again ? |
|
|
|
OK, can you tell once more how to start NAS? Correct links?
Quick guide to setup a NAS node. Steps 1 and 5 is for a public node, you can avoid them if you just need the client. This guide is mostly for Windows, but the only point specific for Windows is point 6. 1.- The guide for NXT is quite the same, mainly the paragraph "Public Node from your home" (if you are thinking to do it from home). Take from that paragraph the way to open port 7871 (not 7874, which is for NXT) and use a web service to get a fixed domain name for your variable IP: http://wiki.nxtcrypto.org/wiki/How-To:CreatePublicNode#Public_Node_from_your_home2.- The link to download the software is this, taken from the first post of this thread, as tiker said: https://www.dropbox.com/s/svdjyo4ozdzfdhp/nas_client.1.1.3%28N1%29.zip3.- You should also have Java installed, you can download it from the original Oracle page: https://www.java.com/en/download4.- What I suggest is to change the configuration file before the first run of the node (otherwise, delete the database folder if you want to start from scratch), in order that the blockchain folder and files will be named with prefix "nas" instead of "nxt", and to avoid conflict of ports with NXT. You can take a corrected 'conf/nas-default.properties' file from my post here: https://bitcointalk.org/index.php?topic=523187.msg10593432#msg105934325.- Then, you should have another file on the same folder called 'conf/nas.properties' where you write just the parameters that are not by default, mainly your node IP address and platform label (for a public node), and an initial list of trusted peers (also good for just a client node), like this: nas.myAddress=your.internet.address
nas.myPlatform=PC
nas.wellKnownPeers=funkyvps3.funkymonkey.org;cb2.flipflop.mooo.com;patapato.ddns.net;99.227.137.145;222.92.62.194
6.- Lastly, if your Java version is greater than 7 (the default for NAS is 7), you should edit the script file 'run.bat' changing: IF EXIST java ( by for %%X in (java.exe) do (set IS_JAVA_IN_PATH=%%~$PATH:X) IF defined IS_JAVA_IN_PATH ( 7.- When you are done, all that you have to do is running this file (in Windows, 'run.sh' in Linux). If you opened the port 7871 on your router and on system firewall, and if everything is working properly, you have now a NAS public node. You can access the client from a web browser by entering the URL (if you are not using my config file, port is 7876 instead, the same as NXT web client port): http://localhost:7873But you must wait for the blockchain to fully download from the NAS network. After that time you will have your client and node working. |
|
|
|
|
Yes, you are right!, that time was the last time that I stopped the server with <ctrl> + C.
I did the transaction without forging, in order to not forge my own transaction. I stopped and restarted forging several times for testing, but you are right again, now I am forging and I see some blocks forged by the account of User1397367406, it is healthy for the network.
Do you, or anybody with a node, try forging?, I can lease my balance to your account for few hours.
|
|
|
|
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: 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: 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 (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." |
|
|
|
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! |
|
|
|
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)? I have all that transactions, but I have one more transaction 15842066818581290243, that is when I sent 20 NAS to lcharles123: 20/02/2015 11:20:45 Ordinary payment 20 1 NAS-VBK9-5ZXA-CJQ8-GEWVU 1440+ lcharles123 didn't received it, and you don't have it on your chain (the same chain as him), but I later received 10 NAS from a friend (also to test the chain) and it is on both chains, yours and mine, as well as my alias assignment (2 minutes later of my unsuccessful sending, as my time is GMT+1 in winter, yours is GMT-5, I see). I agree with reseting my node, I don't want to be on my own isolated chain :-) , and now it seems to be enough synchronized nodes, so I'm going to stop my node now, then I will try to synchronize with majority. 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 ...
I was not forging all the time, and there was times that I stopped my node. In that situation the network was too weak, as it was only you and me as nodes verifying blocks, so a fork was very probable. |
|
|
|
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. |
|
|
|
I have 3 conecteds peers: cb2.flipflop.mooo.com ... CubieBoard2 99.*.137.145 222.*.62.194 Send-me please. 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. |
|
|
|
Maybe ask Poloniex to give us their blockchain? They told users to withdraw their NAScoins and I think it was the only important number of transactions during last months.
I think that those transactions are already in any of the current forks. Which is the NAS address of Poloniex?, I would check its last transaction on my client. I could not find out Polo NAS address, but my transactions were: 7362465635498249985 2014-12-28 09:48:35 COMPLETE: 10648211179026911635 7362465635498249985 2014-12-26 11:01:37 COMPLETE: 1249385332064167760 If I understand right, this is my bter address to which I sent NAS In my wallet, I can only see 5 transactions on account 7362465635498249985, all of them on same date, months before your transactions, and the sum (balance) is zero:
10/07/2014 07:13:04 Ordinary payment - 2'135'298 1 NAS-P8QB-T29S-RPQF-8D8ZG
10/07/2014 06:36:36 Ordinary payment + 34'997 1 NAS-RY9C-485Z-3UNT-83ULH
10/07/2014 06:34:28 Ordinary payment + 2'100'302 1 NAS-Z6C7-MGQK-GDBH-3BDSV
10/07/2014 06:29:44 Ordinary payment - 7'100'412 1 NAS-P8QB-T29S-RPQF-8D8ZG
10/07/2014 06:09:40 Ordinary payment + 7'100'413 1 NAS-EUDJ-RU5A-Z8US-4PSJV
Following the account with the two output transactions, I see a transaction of 1 billion NAS on 15/08/2014 to the account NAS-7PWB-9NGV-3CC7-5U4EF, which now has a balance of 1'017'047'352.79539068 NAS. Maybe this is the address of Bter?, can anybody check or confirm it?. Last transaction from this account was on 31/10/2014 (at least in the fork of my wallet). |
|
|
|
|
Which means that BTC38.com has not a working NAS wallet now. They are not really managing the NAS coin, just their internal numbers representing the price of something called "NAS".
Which has no sense as a NAS exchange, as you can neither sell your own NAS (from your own wallet), nor you can get the NAS that you buy there.
|
|
|
|
But there is no option for deposit/withdrawal, there is the word "PAUSE" instead  |
|
|
|
Will the transaction made on 2014-12-28 be on some other fork, or it will work now?
I don't know on which chain the transactions are, i also have an transfer an the way from Poloniex to my account and i'm triing to get Poloniex to resync their wallet. Poloniex says the transaction went out and was beeing confirmed. From my withdrawals from Poloniex, I get that Poloniex use this NAS address (I don't know if he has more than one address): NAS-R8SQ-TUEM-DTHQ-7ATA3, the account has a balance of 783'912'211.18583353 NAS. This is the list of transactions on this address, taken from my wallet (that is, from the fork in which I am), and there is no transaction on 2014-12-28 , but the last one was later than that, on January 25th: Date Type Amount Fee Account
25/01/2015 17:14:08 Ordinary payment 19 1 NAS-WQL3-FB8L-D8GY-2QXNN
20/01/2015 00:56:32 Ordinary payment 249 1 NAS-ELB3-2CZF-BQYL-53XJN
20/01/2015 00:22:58 Ordinary payment 535.964 1 NAS-TFX2-PZBS-QPPM-892V3
13/01/2015 02:57:19 Ordinary payment 498'999 1 NAS-7XRH-SXQT-RBJS-6MVE2
13/01/2015 02:57:19 Ordinary payment 5'886'603.198 1 NAS-9LQQ-D3P3-TRCU-5EJ9C
13/01/2015 02:57:19 Ordinary payment 7'387.66133334 1 NAS-L6XN-LUHK-9TAG-3QYXD
07/01/2015 22:47:46 Ordinary payment 27'999 1 NAS-RA46-XNBL-SLFL-85QGB
07/01/2015 22:47:46 Ordinary payment 27'707 1 NAS-ASYL-26BY-5LTY-4XK8Q
07/01/2015 22:47:45 Ordinary payment 49'999'999 1 NAS-W5ZS-WTDT-AB2Y-9FWQQ
16/11/2014 17:24:42 Ordinary payment 249 1 NAS-6PUY-SBLS-AF79-CLYTM
16/11/2014 17:24:38 Ordinary payment 249 1 NAS-6PUY-SBLS-AF79-CLYTM
16/11/2014 17:24:37 Ordinary payment 249 1 NAS-6PUY-SBLS-AF79-CLYTM
15/11/2014 12:42:19 Ordinary payment 249 1 NAS-ZHEQ-9P5L-QJJV-5PBSD
13/11/2014 20:45:02 Ordinary payment 11'552.846 1 NAS-NYPM-L23V-HUZG-5ENSY
12/11/2014 12:38:40 Ordinary payment 749 1 NAS-N36N-ZH9T-T8YF-GDWM9
12/11/2014 12:33:34 Ordinary payment 249 1 NAS-N36N-ZH9T-T8YF-GDWM9
11/11/2014 18:36:42 Ordinary payment 68'212.3 1 NAS-NYPM-L23V-HUZG-5ENSY
10/11/2014 07:05:08 Ordinary payment 44'785.248 1 NAS-NYPM-L23V-HUZG-5ENSY
06/11/2014 14:53:43 Ordinary payment 497 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
06/11/2014 14:43:55 Ordinary payment 498 1 NAS-Z2WC-MKKH-LQ6G-BVF32
06/11/2014 08:01:26 Ordinary payment 1'243 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
05/11/2014 22:54:15 Ordinary payment 4'999 1 NAS-9UXF-QBV3-74U7-4S58K
05/11/2014 19:22:40 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
05/11/2014 19:17:19 Ordinary payment 249 1 NAS-Z2WC-MKKH-LQ6G-BVF32
05/11/2014 16:31:44 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
05/11/2014 16:26:13 Ordinary payment 249 1 NAS-ZNV4-NSLH-ZB3H-6PQWN
04/11/2014 18:36:33 Ordinary payment 249 1 NAS-K6S4-SKE4-8Y97-AQRRH
04/11/2014 05:53:40 Ordinary payment 249 1 NAS-DZXU-3RF4-8FRF-DLMDJ
03/11/2014 10:59:03 Ordinary payment 249 1 NAS-K6S4-SKE4-8Y97-AQRRH
03/11/2014 01:35:09 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
02/11/2014 20:11:08 Ordinary payment 249 1 NAS-Z2WC-MKKH-LQ6G-BVF32
28/10/2014 23:28:47 Ordinary payment 20'065'314 1 NAS-HBLG-NL35-8D7J-G6QC4
24/10/2014 18:17:41 Ordinary payment 249 1 NAS-K6S4-SKE4-8Y97-AQRRH
24/10/2014 09:05:17 Ordinary payment 249 1 NAS-K6S4-SKE4-8Y97-AQRRH
23/10/2014 20:32:56 Ordinary payment 4'999 1 NAS-ANHM-HNH2-5HJB-2FFA8
23/10/2014 20:32:56 Ordinary payment 249 1 NAS-K6S4-SKE4-8Y97-AQRRH
23/10/2014 20:32:56 Ordinary payment 249 1 NAS-QALE-KL7U-NVCD-GNENB
23/10/2014 20:32:56 Ordinary payment 2'310'729.90174999 1 NAS-4K3M-M3V6-5ZYH-CFNX3
23/10/2014 20:32:56 Ordinary payment 22'391.126 1 NAS-NYPM-L23V-HUZG-5ENSY
23/10/2014 20:32:56 Ordinary payment 4'999 1 NAS-M6JL-3Y6W-TLL8-2NQV4
23/10/2014 20:32:55 Ordinary payment 4'999 1 NAS-D9YU-FQBP-K8RD-AECSR
23/10/2014 20:32:55 Ordinary payment 4'999 1 NAS-S7WD-8NNP-XPEP-3K787
23/10/2014 20:32:55 Ordinary payment 4'999 1 NAS-UXHX-QFUE-ULX2-65M6V
23/10/2014 20:32:55 Ordinary payment 4'999 1 NAS-YQ4N-S76M-FR8S-4BURP
23/10/2014 20:32:54 Ordinary payment 4'999 1 NAS-MQ6D-BXAK-DQWJ-EBDM7
23/10/2014 20:32:54 Ordinary payment 4'999 1 NAS-MVUA-57MK-AV4X-HHFR3
23/10/2014 20:32:54 Ordinary payment 4'999 1 NAS-V62Q-XD6G-S5PR-F4G2P
23/10/2014 20:32:54 Ordinary payment 4'999 1 NAS-YUQW-QQ9K-ADVV-BH3D5
23/10/2014 20:32:53 Ordinary payment 4'999 1 NAS-GZFK-VF2F-C8JB-8LNZE
23/10/2014 20:32:53 Ordinary payment 4'999 1 NAS-VEN6-RG2D-VA2A-BA9RH
23/10/2014 20:32:53 Ordinary payment 249 1 NAS-62NU-BBWX-WBZ4-HT9CD
23/10/2014 20:32:53 Ordinary payment 4'999 1 NAS-J64L-TKK4-A85V-BV94K
23/10/2014 20:32:53 Ordinary payment 4'999 1 NAS-MHSB-BPS6-75JR-7V4ZS
13/10/2014 14:33:40 Ordinary payment 5'249 1 NAS-YJ7E-7ZGJ-8EV4-3QPE3
13/10/2014 05:38:53 Ordinary payment 3'740'183 1 NAS-NYTQ-LADR-SSYQ-GW43G
12/10/2014 21:17:14 Ordinary payment 497.822 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
12/10/2014 21:10:52 Ordinary payment 249 1 NAS-D8ZK-3T7P-VW9Z-699PW
12/10/2014 21:10:52 Ordinary payment 249.822 1 NAS-D8ZK-3T7P-VW9Z-699PW
11/10/2014 05:26:02 Ordinary payment 39'999 1 NAS-GCP7-6W5C-NZUG-DMMBE
11/10/2014 04:37:31 Ordinary payment 5'099 1 NAS-GCP7-6W5C-NZUG-DMMBE
11/10/2014 04:05:46 Ordinary payment 332 1 NAS-GCP7-6W5C-NZUG-DMMBE
10/10/2014 02:43:53 Ordinary payment 10'060'200 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
10/10/2014 02:33:11 Ordinary payment 9 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
09/10/2014 03:50:51 Ordinary payment 84'986 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
08/10/2014 14:48:39 Ordinary payment 497 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
08/10/2014 14:45:58 Ordinary payment 498 1 NAS-CJZQ-CKEV-EYFK-GNNTM
08/10/2014 07:09:02 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
08/10/2014 07:08:55 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
08/10/2014 05:51:21 Ordinary payment 49'999'999 1 NAS-EKNN-CSX4-MWY6-FG8ZX
08/10/2014 05:43:21 Ordinary payment 249 1 NAS-6PCT-75E3-8RBT-9DGH5
08/10/2014 05:43:21 Ordinary payment 249 1 NAS-65WJ-63ZP-C97H-HQYWT
08/10/2014 05:43:16 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
30/09/2014 05:43:29 Ordinary payment 49'999'999 1 NAS-EKNN-CSX4-MWY6-FG8ZX
29/09/2014 01:51:32 Ordinary payment 249 1 NAS-RBCY-NLS3-5DN5-E6MHH
28/09/2014 22:58:14 Ordinary payment 79'999 1 NAS-5HZF-TPQ5-GSHF-7GV33
28/09/2014 12:34:21 Ordinary payment 249 1 NAS-JSUZ-PKS4-LEYJ-2CF8V
28/09/2014 09:55:49 Ordinary payment 4'708'890.8210561 1 NAS-8W63-T26Z-UZXU-8RLJS
17/09/2014 20:43:14 Ordinary payment 249 1 NAS-KBMD-4V6Z-XLC3-H4HHV
17/09/2014 16:01:53 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
17/09/2014 15:51:00 Ordinary payment 249 1 NAS-XU8A-DAT8-7YF5-AMQR9
17/09/2014 15:45:51 Ordinary payment 497 1 NAS-TJ4E-6679-5538-ARGNX
17/09/2014 14:36:39 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
17/09/2014 14:31:18 Ordinary payment 249 1 NAS-XU8A-DAT8-7YF5-AMQR9
17/09/2014 05:17:07 Ordinary payment 2'560'541.761 1 NAS-X5LW-K47U-LEB3-7RSWC
17/09/2014 04:31:53 Ordinary payment 49'999'999 1 NAS-EKNN-CSX4-MWY6-FG8ZX
16/09/2014 17:29:22 Ordinary payment 1'991 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
16/09/2014 17:26:28 Ordinary payment 1'992 1 NAS-8QT8-UVEB-E35G-7M95P
16/09/2014 17:26:22 Ordinary payment 2'240 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
16/09/2014 17:19:23 Ordinary payment 2'241 1 NAS-8QT8-UVEB-E35G-7M95P
16/09/2014 14:08:41 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
16/09/2014 14:05:51 Ordinary payment 249 1 NAS-XU8A-DAT8-7YF5-AMQR9
16/09/2014 13:22:55 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
16/09/2014 13:20:09 Ordinary payment 249 1 NAS-CLP3-FNKE-GXLK-9HHEU
16/09/2014 13:16:23 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
16/09/2014 13:13:34 Ordinary payment 249 1 NAS-CLP3-FNKE-GXLK-9HHEU
16/09/2014 13:13:09 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
16/09/2014 13:09:15 Ordinary payment 249 1 NAS-CLP3-FNKE-GXLK-9HHEU
16/09/2014 13:05:15 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
16/09/2014 13:02:30 Ordinary payment 249 1 NAS-3S8R-2AUS-75PU-3KAEG
16/09/2014 13:02:26 Ordinary payment 248 1 NAS-R8SQ-TUEM-DTHQ-7ATA3
|
|
|
|
Maybe ask Poloniex to give us their blockchain? They told users to withdraw their NAScoins and I think it was the only important number of transactions during last months.
I think that those transactions are already in any of the current forks. Which is the NAS address of Poloniex?, I would check its last transaction on my client. Why are there several forks surviving now?, does it mean that the automatic consensus mechanism is not working?. Well, I understand that the main problem is a very low number of nodes and forgers. The first think that we need is more independent nodes working, with different forging accounts. The stronger fork should survive, normally it would be the one on important exchanges. It is now like the early time of a coin, a rebirth. For those interested on setting up his own public node at home, I suggest to use my proposed conf/nas.default-properties file, and follow the instructions on the NXT wiki, changing the ports to the ones defined for NAS in that file (I changed UI and API ports in order to be different than in NXT and avoid conflict; name and folder of blockchain database file also changes, you have to move it manually if you want to keep your current blockchain): - 7871 for peer interface (the one to open in your router/firewall),
- 7872 for UI,
- and 7873 for API interface (the one to use from your web browser).
Then we could collect in this thread a list of enough nodes to put on the file 'conf/nas.properties' under the key 'nas.wellKnownPeers=' (although it is not strictly necessary, just it helps to connect initial peers). We have a clone of NXT with an initial distribution already done. Development can be continued by any medium level programmer, just by adapting again the NXT Open Source code. I think that it will not be difficult to get NAS running with the cloned last version of NXT, 1.4.16. It can serve as an experimental fork of NXT, or just as a pure clone of NXT. The second way will be easy to maintain, it doesn't need high level programmers. Pure clones are not bad idea, why people think that cryptocurrency clones are bad?. Euro is a pure clone of Dollar, gold and silver are pure clones one of the other, just the total supply and the production rate is different. In a free economy it is good to have more than one coin of the same type, then market will choose. |
|
|
|
Hi,
@patapato: are you still running a node and forging?
Is anyone else forging at the moment or are there too much forked chains?
Yes, my node is still running and forging. I don't know who else is forging or what forks exists. I would like to synchronize my node with the nodes of exchanges, if they are still alive, how can I do it? |
|
|
|
Some features, like the ports used, can be changed in the 'nas-default.properties' file, and we can also change the name of directories and files to avoid references to NXT and substitute them by NAS. So we can easily do a new package of files, a new minor revision without changing code, just filenames and text content to make a consistent package.
About this idea, I was comparing the file 'conf/nas-default.properties' with the one in the 3.1.1 1.1.3 version of NXT, as well as the most recent version of it. It is not necessary a new minor revision, but we can get a more consistent installation by modifying this file. I updated the parameters in that file accordingly, and changed the ports in order to be different than in NXT. I kept the 7871 for peerServerPort, so I used 7872 for uiServerPort and 7873 for apiServerPort. I also changed the directory name and file name for database to use the word 'nas' instead of 'nxt'. So you should copy your blockchain file to the new one if you want to use it, and delete the old folder (or use it as a backup copy). You can also delete the old log and trace files with 'nxt' in its name. I disabled DEBUG by default, and let empty the wellKnownPeers. It can go to 'conf/nas.properties' instead, in order to not change the default file. This is the resulting ' conf/nas-default.properties' file: # Do not modify this file. Instead, create a nas.properties file with only the properties
# you need to change, and set them there. The values in nas.properties override those in
# nas-default.properties.
#### PEER NETWORKING ####
# Announce my IP address/hostname to peers and allow them to share it with other peers.
# If disabled, peer networking servlet will not be started at all.
nas.shareMyAddress=true
# Port for incoming peer to peer networking requests, if enabled.
nas.peerServerPort=7871
# Host interface on which to listen for peer networking requests, default all.
# Use 0.0.0.0 to listen on all IPv4 interfaces or :: to listen on all IPv4 and IPv6 interfaces
nas.peerServerHost=0.0.0.0
# My externally visible IP address or host name, to be announced to peers.
# It can optionally include a port number, which will also be announced to peers,
# and may be different from nas.peerServerPort (useful if you do port forwarding behind a router).
nas.myAddress=
# My platform, to be announced to peers.
nas.myPlatform=PC
# My hallmark, if available.
nas.myHallmark=
# A list of well known peer addresses / host names, separated by '; '.
nas.wellKnownPeers=
# Known bad peers to be blacklisted
nas.knownBlacklistedPeers=
# Peers used for testnet only.
nas.testnetPeers=bug.airdns.org; node10.mynxtcoin.org; node9.mynxtcoin.org
# Maintain active connections with at least that many peers.
nas.maxNumberOfConnectedPublicPeers=20
# Peer networking connect timeout for outgoing connections.
nas.connectTimeout=10000
# Peer networking read timeout for outgoing connections.
nas.readTimeout=20000
# Peer networking server idle timeout, milliseconds.
nas.peerServerIdleTimeout=30000
# Use the peer hallmark to only connect with peers above the defined push/pull hallmark thresholds.
nas.enableHallmarkProtection=true
# Hallmark threshold to use when sending data to peers.
nas.pushThreshold=0
# Hallmark threshold to use when requesting data from peers.
nas.pullThreshold=0
# Blacklist peers for 600000 milliseconds (i.e. 10 minutes by default).
nas.blacklistingPeriod=600000
# Consider a new transaction or block sent after 10 peers have received it.
nas.sendToPeersLimit=10
# Enable the Jetty Denial of Service Filter for the peer networking server.
nas.enablePeerServerDoSFilter=true
# Use testnet, leave set to false unless you are really testing.
# Never unlock your real accounts on testnet! Use separate accounts for testing only.
# When using testnet, all custom port settings will be ignored,
# and hardcoded ports of 6874 (peer networking), 6875 (UI) and 6876 (API) will be used.
nas.isTestnet=false
# Save known peers in the database
nas.savePeers=true
# Set to false to disable use of the peers database. This will not delete saved peers.
nas.usePeersDb=true
#### API SERVER ####
# Accept http/json API requests.
nas.enableAPIServer=true
# Hosts from which to allow http/json API requests, if enabled.
nas.allowedBotHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1];
# Port for http/json API requests.
nas.apiServerPort=7873
# Host interface on which to listen for http/json API request, default localhost only.
# Set to 0.0.0.0 to allow the API server to accept requests from all network interfaces.
nas.apiServerHost=127.0.0.1
# Idle timeout for http/json API request connections, milliseconds.
nas.apiServerIdleTimeout=30000
# Directory with html and javascript files for the new client UI, and admin tools utilizing
# the http/json API.
nas.apiResourceBase=html/ui
# Java API documentation directory, optional.
nas.javadocResourceBase=html/doc
# Enable Cross Origin Filter for the API server.
nas.apiServerCORS=false
# Enable SSL for the API server (also need to set nas.keyStorePath and nas.keyStorePassword).
nas.apiSSL=false
# Enforce requests that require POST to only be accepted when submitted as POST.
nas.apiServerEnforcePOST=true
#### NRS USER INTERFACE ####
# Enable the deprecated NRS user interface.
nas.enableUIServer=false
# Hosts from which to allow NRS user interface requests, if enabled.
nas.allowedUserHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1];
# Port for NRS user interface server.
nas.uiServerPort=7872
# Host interface for NRS user interface server, default localhost only.
# Set to 0.0.0.0 to allow the UI to be accessed on all network interfaces.
nas.uiServerHost=127.0.0.1
# Idle timeout for NRS user interface server, milliseconds.
nas.uiServerIdleTimeout=30000
# Directory with html and javascript files for the NRS client user interface.
nas.uiResourceBase=html/nrs
# Enable Cross Origin Filter for NRS user interface server.
nas.uiServerCORS=false
# Enable SSL for the NRS user interface (also need to set nas.keyStorePath and nas.keyStorePassword).
nas.uiSSL=false
# Enforce requests that require POST to only be accepted when submitted as POST.
nas.uiServerEnforcePOST=true
#### DEBUGGING ####
# Log file, will be overwritten at every restart.
nas.log=nas.log
# Enable debug log output.
nas.debug=false
# Enable logging of exception stack traces.
nas.enableStackTraces=true
# Enable logging of Jetty messages.
nas.debugJetty=false
# Used for debugging peer to peer communications.
nas.communicationLoggingMask=0
# Track balances of the following accounts for debugging purposes.
nas.debugTraceAccounts=
# File name for logging tracked account balances
nas.debugTraceLog=nas-trace.csv
# Separator character for trace log
nas.debugTraceSeparator=\t
# Quote character for trace log
nas.debugTraceQuote="
#### DATABASE ####
# Database connection JDBC url, see the H2 documentation for possible customizations.
# Append ;AUTO_SERVER=TRUE to enable automatic mixed mode access.
# The nxt_db folder is expected to be in the current working directory, will be created if missing.
nas.dbUrl=jdbc:h2:nas_db/nas;DB_CLOSE_ON_EXIT=FALSE
# Database connection JDBC url to use with the test network, if isTestnet=true
nas.testDbUrl=jdbc:h2:nas_test_db/nas;DB_CLOSE_ON_EXIT=FALSE
# Database connection timeout in seconds.
nas.dbLoginTimeout=70
# Database default lock timeout in seconds.
nas.dbDefaultLockTimeout=60
# Maximum simultaneous database connections.
nas.maxDbConnections=30
# The memory allocated to database cache, in kB.
# If set to 0, defaults to 50 % of the memory available to the JVM.
nas.dbCacheKB=0
#### JETTY ####
# Settings for the Jetty Denial Of Service Filter, used for the peer networking server only.
nas.peerServerDoSFilter.maxRequestsPerSec=30
nas.peerServerDoSFilter.delayMs=1000
nas.peerServerDoSFilter.maxRequestMs=300000
# keystore file and password, required if uiSSL or apiSSL are enabled.
nas.keyStorePath=keystore
nas.keyStorePassword=password
EDIT: empty 'nas.wellKnownPeers='; nonempty should go to the file 'conf/nas.properties' REMEMBER: your new web interface using this file will be: http://localhost:7873It is convenient that you have your customized parameters in the file 'conf/nas.properties'. I suggest the next file to get connected with few initial known peers (note that I explicitly write both ports, the new and the old one, in order to avoid problems now). You can fill your address:port and platform if you are going to be a public node. You can easily enable and disable debug and trace here. nas.myAddress=
nas.myPlatform=PC
nas.myHallmark=
nas.wellKnownPeers=99.227.137.145;222.92.62.194;nxtnode.ddns.net;cb2.flipflop.mooo.com;flipflop.mooo.com;patapato.ddns.net;89.247.173.211;89.247.163.145;62.42.108.235
nas.debug=false
nas.enableStackTraces=true
nas.debugJetty=false
EDIT: modified list of peers, 2 added, and ports not set (default 7871 is taken) Also, I suggest to modify the 'run.bat' file the way as it is in the last version of NXT in order to better find your installed version of Java, that is to substitute the line by
for %%X in (java.exe) do (set IS_JAVA_IN_PATH=%%~$PATH:X)
IF defined IS_JAVA_IN_PATH (
|
|
|
|
I looked at the history of the number 1 account on the ranking cited by lcharles1232: But she was fully distributed? Here in this topic is written that some accounts has almost all the coins, https://bitcointalk.org/index.php?topic=570366.0 you must ask the NAS whaleholders to make a transparent fund for bounties and giveaways. It would be nice to see the features promised for that currency working. I found this other address in his first transaction, it has a negative balance of 10 bn coins: Account NAS-MRCC-2YLS-8M54-3CMAJ Info
The account has a balance of -9'999'999'999 NASCan anybody explain it? |
|
|
|
|
Well, clearly we have at least 2 forks, and at least 2 forgers. It is not enough for a healthy coin.
I also think like you, that base code for web wallet is very close to the NXT code, NAS is essentially a NXT clone, as the pretended added features are just in the Windows client, WinNAS: BlockDice, Chatroom, BlockLottery, ...
Some features, like the ports used, can be changed in the 'nas-default.properties' file, and we can also change the name of directories and files to avoid references to NXT and substitute them by NAS. So we can easily do a new package of files, a new minor revision without changing code, just filenames and text content to make a consistent package.
So, if we get enough nodes to run the server, and we agree in one fork, the coin can revive. The fact that development is stopped is an advantage in order to trust the coin. The initial distribution is already done, and the ones who have more stake can donate few of them for bounties or promotion.
It is very interesting for me the idea of a cryptocurrency with frozen development (although, if it is really just a clone of NXT, further independent development could be done).
What do other people think?, are there more supporters for this idea?, contrary opinions?
|
|
|
|
|
Sorry, in the previous post content, time is not UTC, it is GMT + 1
|
|
|
|
|
