Topic: NAS :: Descendant of NXT 100% PoS|More Exchanges|WinNAS is ready! - page 14. (Read 143776 times)
March 02, 2015, 02:10:21 PM
Mine is from Poloniex to Bter, so my case is worse.
March 02, 2015, 01:56:01 PM
Hi,
@patapato: are you still running a node and forging?
Is anyone else forging at the moment or are there too much forked chains?
Poloniex says the transaction went out and was beeing confirmed.
Maybe i'll be lucky.
@patapato: are you still running a node and forging?
Is anyone else forging at the moment or are there too much forked chains?
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.
Maybe i'll be lucky.
February 27, 2015, 09:45:30 PM
Will the transaction made on 2014-12-28 be on some other fork, or it will work now?
February 26, 2015, 04:31:14 PM
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
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:
Code:
# 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
REMEMBER: your new web interface using this file will be: http://localhost:7873
It 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.
Code:
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
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
Code:
IF EXIST java (
Code:
for %%X in (java.exe) do (set IS_JAVA_IN_PATH=%%~$PATH:X)
IF defined IS_JAVA_IN_PATH (
February 22, 2015, 09:07:46 PM
I have part of my NAS on dgex and part on the way from Poloniex to bter. Is there a hope that I will see them again?
February 22, 2015, 08:50:08 AM
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 NAS
Can anybody explain it?
Account NAS-MRCC-2YLS-8M54-3CMAJ Info
The account has a balance of -9'999'999'999 NAS
Can anybody explain it?
It's the genesis account. That is the account that distributed all the coins into the NAS system. It is negative because the total number of coins in NAS is zero.
More info:
http://wiki.nxtcrypto.org/wiki/Glossary#Genesis_Account
February 22, 2015, 04:28:20 AM
I looked at the history of the number 1 account on the ranking cited by lcharles1232:
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 NAS
Can anybody explain it?
But she was fully distributed?
Here in this topic is written that some accounts has almost all the coins, https://bitcointalksearch.org/topic/nas-the-latest-greedyponzi-distribution-model-71-to-11-people-what-570366 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.
Here in this topic is written that some accounts has almost all the coins, https://bitcointalksearch.org/topic/nas-the-latest-greedyponzi-distribution-model-71-to-11-people-what-570366 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 NAS
Can anybody explain it?
February 21, 2015, 08:07:54 PM
Cool. NAS *might* live on
It does seem obvious that NAS whales need to be involved if this is serious.
It does seem obvious that NAS whales need to be involved if this is serious.
February 21, 2015, 07:45:52 PM
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?
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?
GREAT JOB!
I think we should let nas 1.3.2 revive first. Suggest you upload the nas.rar of nas directory include nxt_db for others to download and call for them to run servers. The first step is to make it alive.
Here in this topic is written that some accounts has almost all the coins, https://bitcointalksearch.org/topic/nas-the-latest-greedyponzi-distribution-model-71-to-11-people-what-570366 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.
February 21, 2015, 10:16:52 AM
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?
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?
GREAT JOB!
I think we should let nas 1.3.2 revive first. Suggest you upload the nas.rar of nas directory include nxt_db for others to download and call for them to run servers. The first step is to make it alive.
February 21, 2015, 09:14:33 AM
February 21, 2015, 08:01:29 AM
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?
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?
February 21, 2015, 05:54:39 AM
Done, now you have your first 20 NAS, on transaction 15842066818581290243:
Date Type Amount Fee Account Confirmations
20/02/2015 11:20:45 Ordinary payment 20 1 NAS-VBK9-5ZXA-CJQ8-GEWVU 15
Date Type Amount Fee Account Confirmations
20/02/2015 11:20:45 Ordinary payment 20 1 NAS-VBK9-5ZXA-CJQ8-GEWVU 15
ID not found, the blockchain are in Height 233247 2/20/2015 12:13:39 and transaction not in.
Is possible to this account are forging all blocks: NAS-5HZF-TPQ5-GSHF-7GV33 with 3M NAS and create a new chain and im in
Here not appear any NAS value passed far as i can see: height 233152 02/20/2015 09:30:16 GMT
He is dead. :/
With so few forgers (sometimes 0, sometimes 1, sometimes 2, ...) it is easy to have forks. My wallet was stopped tonight, I restarted it few hours ago. I can see on the block history that at about 11:18 UTC I started to forge, previously the address that you say was forging (I have more stake):
...
233219 20/02/2015 11:19:49 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 12937 %
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 %
233216 20/02/2015 11:16:18 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 10299 %
...
These are the transaction details from my wallet:
Code:
SenderPublicKey: c81c7a26f496ca23486ad5d3e55b7310812b887b35a3452f1f60ecbb6441675f
Signature: fc48fa79b83b4adcbe274b585bf8d643fcfa5f20ccad8d3125e33b49464a5e08f78caeb952c8f628ee98d4a51ca2ea1f0b48dab723739135bd731560812f789b
FeeNQT: 100000000
Type: 0
Confirmations: 53
FullHash: 035d8a2dd653dadb5191acf206d57ae940329e248009e6882a67b4ce06aa88d5
SignatureHash: 9519cb9c41e3592c6e5438502f289b560bc9a849ab2f4a968e1f0a9a75b30e4b
SenderRS: NAS-H5AW-7J9F-7VCY-DJ8NB
Subtype: 0
AmountNQT: 2000000000
Sender: 13029142609628990748
RecipientRS: NAS-VBK9-5ZXA-CJQ8-GEWVU
Recipient: 17109047578379265575
Block: 320087056910960173
BlockTimestamp: 28678874
Deadline: 1440
Timestamp: 28678845
Height: 233222
The same Block appears like this for me:
Code:
PayloadLength: 209
TotalAmountNQT: 0
Generator: 5802728473452724205
BaseTarget: 28718327414
GeneratorRS: NAS-5HZF-TPQ5-GSHF-7GV33
NextBlock: 8167957520048415331
NumberOfTransactions: 1
BlockSignature: 11a17e3a065467f92478f63967c115112fc797c1546f1f38a4c6819aa40fed0d42c6abb87ca93fbe6ffa1680a70625daa4f4020b5115b60454e93cc7f52eff1c
Version: 3
TotalFeeNQT: 100000000
PreviousBlock: 6302124221230908110
Height: 233222
Timestamp: 28679076
There is a transaction on it, but there is no volume transacted.
I would have to use the blockchain of its portfolio to leave the alternate current, but then I'll use your fork blockchain
The lack of open source is no problem, because I believe that it is a clone 1: 1 NXT, just pick up the original NXT and change the suply, initial addresses and P2P port for 7871.
February 20, 2015, 07:37:17 AM
Sorry, in the previous post content, time is not UTC, it is GMT + 1
February 20, 2015, 07:32:28 AM
Done, now you have your first 20 NAS, on transaction 15842066818581290243:
Date Type Amount Fee Account Confirmations
20/02/2015 11:20:45 Ordinary payment 20 1 NAS-VBK9-5ZXA-CJQ8-GEWVU 15
Date Type Amount Fee Account Confirmations
20/02/2015 11:20:45 Ordinary payment 20 1 NAS-VBK9-5ZXA-CJQ8-GEWVU 15
ID not found, the blockchain are in Height 233247 2/20/2015 12:13:39 and transaction not in.
Is possible to this account are forging all blocks: NAS-5HZF-TPQ5-GSHF-7GV33 with 3M NAS and create a new chain and im in
Here not appear any NAS value passed far as i can see: height 233152 02/20/2015 09:30:16 GMT
He is dead. :/
With so few forgers (sometimes 0, sometimes 1, sometimes 2, ...) it is easy to have forks. My wallet was stopped tonight, I restarted it few hours ago. I can see on the block history that at about 11:18 UTC I started to forge, previously the address that you say was forging (I have more stake):
...
233219 20/02/2015 11:19:49 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 12937 %
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 %
233216 20/02/2015 11:16:18 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 10299 %
...
These are the transaction details from my wallet:
Code:
SenderPublicKey: c81c7a26f496ca23486ad5d3e55b7310812b887b35a3452f1f60ecbb6441675f
Signature: fc48fa79b83b4adcbe274b585bf8d643fcfa5f20ccad8d3125e33b49464a5e08f78caeb952c8f628ee98d4a51ca2ea1f0b48dab723739135bd731560812f789b
FeeNQT: 100000000
Type: 0
Confirmations: 53
FullHash: 035d8a2dd653dadb5191acf206d57ae940329e248009e6882a67b4ce06aa88d5
SignatureHash: 9519cb9c41e3592c6e5438502f289b560bc9a849ab2f4a968e1f0a9a75b30e4b
SenderRS: NAS-H5AW-7J9F-7VCY-DJ8NB
Subtype: 0
AmountNQT: 2000000000
Sender: 13029142609628990748
RecipientRS: NAS-VBK9-5ZXA-CJQ8-GEWVU
Recipient: 17109047578379265575
Block: 320087056910960173
BlockTimestamp: 28678874
Deadline: 1440
Timestamp: 28678845
Height: 233222
February 20, 2015, 06:31:23 AM
You mean 20 NAS?
Yes, 20 NAS, I corrected my offering :-)Code:
NAS-VBK9-5ZXA-CJQ8-GEWVU
Thanks!
Done, now you have your first 20 NAS, on transaction 15842066818581290243:
Date Type Amount Fee Account Confirmations
20/02/2015 11:20:45 Ordinary payment 20 1 NAS-VBK9-5ZXA-CJQ8-GEWVU 15
ID not found, the blockchain are in Height 233247 2/20/2015 12:13:39 and transaction not in.
Is possible to this account are forging all blocks: NAS-5HZF-TPQ5-GSHF-7GV33 with 3M NAS and create a new chain and im in
Here not appear any NAS value passed far as i can see: height 233152 02/20/2015 09:30:16 GMT
He is dead. :/
February 20, 2015, 05:50:58 AM
Yes, it works with Java8, mine is working with jre1.8.0_31.
@lcharles123, send me your account ID and I will send you 20 NAS for testing the blockchain and the network.
I also think that the port should be different than the one of NXT ... but it was the developer, he diappeared ... I think it was on his TODO list, because the README file and other files are also not changed from NXT.
@lcharles123, send me your account ID and I will send you 20 NAS for testing the blockchain and the network.
I also think that the port should be different than the one of NXT ... but it was the developer, he diappeared ... I think it was on his TODO list, because the README file and other files are also not changed from NXT.
Did the dev disappear before releasing the source code? Is it impossible to change the port into a different one from the one NXT uses?
February 20, 2015, 05:45:10 AM
You mean 20 NAS?
Yes, 20 NAS, I corrected my offering :-)Code:
NAS-VBK9-5ZXA-CJQ8-GEWVU
Thanks!
Done, now you have your first 20 NAS, on transaction 15842066818581290243:
Date Type Amount Fee Account Confirmations
20/02/2015 11:20:45 Ordinary payment 20 1 NAS-VBK9-5ZXA-CJQ8-GEWVU 15
February 19, 2015, 08:36:48 PM
Yes, it works with Java8, mine is working with jre1.8.0_31.
@lcharles123, send me your account ID and I will send you 20 NXT for testing the blockchain and the network.
I also think that the port should be different than the one of NXT ... but it was the developer, he diappeared ... I think it was on his TODO list, because the README file and other files are also not changed from NXT.
@lcharles123, send me your account ID and I will send you 20 NXT for testing the blockchain and the network.
I also think that the port should be different than the one of NXT ... but it was the developer, he diappeared ... I think it was on his TODO list, because the README file and other files are also not changed from NXT.
You mean 20 NAS?
I'm running on jre1.8.0_25 myself, haven't updated to _31 yet.
I'll see if I can find a script or write one to output the "richlist" for the NAS accounts. I don't even have an account with published public key since I only found NAS about 2 months ago.
But the port of the web interface is the same as NXT, 7876 , the devs did not even bothered to change.
Code:
NAS-VBK9-5ZXA-CJQ8-GEWVU
Thanks!
February 19, 2015, 01:05:31 PM
Yes, it works with Java8, mine is working with jre1.8.0_31.
@lcharles123, send me your account ID and I will send you 20 NXT for testing the blockchain and the network.
I also think that the port should be different than the one of NXT ... but it was the developer, he diappeared ... I think it was on his TODO list, because the README file and other files are also not changed from NXT.
@lcharles123, send me your account ID and I will send you 20 NXT for testing the blockchain and the network.
I also think that the port should be different than the one of NXT ... but it was the developer, he diappeared ... I think it was on his TODO list, because the README file and other files are also not changed from NXT.
You mean 20 NAS?
I'm running on jre1.8.0_25 myself, haven't updated to _31 yet.
I'll see if I can find a script or write one to output the "richlist" for the NAS accounts. I don't even have an account with published public key since I only found NAS about 2 months ago.
Jump to: