assembly
assembly
Show Posts - tiker
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Ardor Client: Ardor 2.2.5

Show Posts

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

Messages - tiker

Pages: [1] 2
1
Ardor Software Releases / Re: Ardor v2.0.1e
« on: March 07, 2017, 02:35:54 pm »
There's a GUI problem on the peers page which also exists for the NXT client.

Using Windows 7 and Chrome as the browser, view the peers page.  Move the mouse cursor over one of the peer services shown ("CS" for example) which then shows the balloon (bubble or whatever you want to call it showing the full service name).

When the page refreshes to show updated information, move the mouse off off the service.  The balloon remains on the screen.

When changing to other pages now (Dashboard for example) the balloon remains on the screen.  If you happen to have a long list of peers and test this with a peer at the bottom of the list, all of the pages now scroll a long ways down showing nothing until you get to the bubble.

So far, the only way I've found to get rid of the bubble is to log out of the wallet.

2
Testnet / Re: If you want some testNXT (or ARDR, IGNIS) - ask here
« on: February 23, 2017, 06:36:34 pm »
Please send me a mixed bag of goodies again.  I lost my test stuff with the new test release.

NXT-NUVP-62HN-ZP3F-DWGCL

Thanks.

3
Testnet / Re: If you want some testNXT (ARDR, IGNIS) - ask here
« on: February 14, 2017, 07:00:16 pm »
Please send me some test ARDR, IGNIS, etc. as well if you can.

NXT-NUVP-62HN-ZP3F-DWGCL

Thanks.

4
General / Re: Who forged a second block?
« on: August 11, 2015, 06:18:58 pm »
I think the public keys for the initial distribution was included with the transactions from the genesis account.

If I'm reading the source correctly...  https://bitbucket.org/JeanLucPicard/nxt/src/b60b4dba968068fe01c595889146cf898881af5b/src/java/nxt/Genesis.java?at=master

Edit:  or maybe the signatures are transaction signatures and not public keys...   ignore me.

5
I'd actually like to see the MS transactions use a fraction of the MS currency as the transaction fee and not NXT.

This would allow different countries using MS to have fees paid at an amount scaled to their currency values and not restricting all different MS currency transactions to the same NXT value fees.
What would stop me creating a worthless currency and then getting all my transactions effectively for free forever?
For example forgers' rule to process only limited set of MS currencies.
In other words, more technical  :), allow a new type of MS, which cost 0 nxt to create and uses its own unit as transaction fee, but is still being forged according to the nxts forging algoritm AND POS of nxt.

There would still be fees to setup the MS currency and possibly even higher setup fees than others to prevent people from randomly claiming MS currency codes for fun.  Setting up is one thing and shouldn't be free.  Making it easier (and in some cases cheaper) for people to use is the goal I had in mind.

6
I'd actually like to see the MS transactions use a fraction of the MS currency as the transaction fee and not NXT.

This would allow different countries using MS to have fees paid at an amount scaled to their currency values and not restricting all different MS currency transactions to the same NXT value fees.

This would also make it easier for people familiar with bitcoin like chains to use MS currencies because the rules would be similar rather than having to tell them they need to buy NXT tokens to send their ABCDE coins.  As a forger, I wouldn't have any issues processing a transaction for a MS fee.  I still have the option of putting the MS fees up for sale.

Perhaps make it an option for forgers:  Only include transactions with NXT fees, Include transactions with MS fees...

7
Transparent Forging / Re: Strange behavior and extreme long blocks
« on: July 13, 2015, 01:14:13 pm »

I had 3 different transactions that was supposed to happen during that time.

On my NXT node, 2 of 3 transactions showed in my wallet as unconfirmed.  I checked the site above and noticed that neither of them had appeared and that it has been about 45 minutes since the previous block had been forged.  I watched for about 15 minutes (1 hour passed since previous block was forged) and then gave up...

This morning, transaction 1 has disappeared and did not end up crediting my wallet.  Transaction 2 and 3 appeared and confirmed.  I lost 1 transaction in there somewhere.

8
General / Re: lease forging without penalty
« on: May 25, 2015, 10:50:06 pm »
I tried re-leasing my balance once before the existing lease ended...  It ended up cancelling the existing lease immediately and resumed after the 1440 block confirmation.

As far as I know, there is no way to renew an existing lease without the 1440 block delay.

9
Nxt General Discussion / Re: 1.5.8e out of memory
« on: May 20, 2015, 12:52:05 pm »
I believe lyaffe has identified the problem.

The start of the NXT log file shows java running from "Program Files (x86)" which would indicate it is using a 32-bit version of the JRE.

Code: [Select]
2015-05-19 12:42:55 FINE: java.version = 1.8.0_45
2015-05-19 12:42:55 FINE: java.vm.version = 25.45-b02
2015-05-19 12:42:55 FINE: java.vm.name = Java HotSpot(TM) Client VM
2015-05-19 12:42:55 FINE: java.vendor = Oracle Corporation
2015-05-19 12:42:55 FINE: java.vm.vendor = Oracle Corporation
2015-05-19 12:42:55 FINE: java.home = C:\Program Files (x86)\Java\jre1.8.0_45
2015-05-19 12:42:55 FINE: java.library.path = C:\Program Files (x86)\Java\jre1.8.0_45\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\Calibre2\;C:\Program Files\TortoiseGit\bin;.
2015-05-19 12:42:55 FINE: java.class.path = nxt.jar;lib\bcprov-jdk15on-152.jar;lib\h2-1.3.176.jar;lib\jetty-continuation-9.2.10.v20150310.jar;lib\jetty-http-9.2.10.v20150310.jar;lib\jetty-io-9.2.10.v20150310.jar;lib\jetty-security-9.2.10.v20150310.jar;lib\jetty-server-9.2.10.v20150310.jar;lib\jetty-servlet-9.2.10.v20150310.jar;lib\jetty-servlets-9.2.10.v20150310.jar;lib\jetty-util-9.2.10.v20150310.jar;lib\json-simple-1.1.1.jar;lib\lucene-core-3.6.2.jar;lib\servlet-api-3.1.jar;lib\slf4j-api-1.7.7.jar;lib\slf4j-jdk14-1.7.7.jar;lib\websocket-api-9.2.10.v20150310.jar;lib\websocket-client-9.2.10.v20150310.jar;lib\websocket-common-9.2.10.v20150310.jar;lib\websocket-server-9.2.10.v20150310.jar;lib\websocket-servlet-9.2.10.v20150310.jar;conf
2015-05-19 12:42:55 FINE: os.arch = x86
2015-05-19 12:42:55 FINE: sun.arch.data.model = 32
2015-05-19 12:42:55 FINE: os.name = Windows 7
2015-05-19 12:42:55 FINE: file.encoding = Cp1252
2015-05-19 12:42:55 FINE: availableProcessors = 8
2015-05-19 12:42:55 FINE: maxMemory = 1037959168

I shall make some changes to fix this.

Thank you!

10
Nxt General Discussion / Re: 1.5.8e out of memory
« on: May 19, 2015, 03:36:01 pm »
The box is a Win7-64 bit with 12 gigs of ram.  OS reports 55% is in use (just after NXT died).

11
Nxt General Discussion / 1.5.8e out of memory
« on: May 19, 2015, 03:04:50 pm »
Since I updated to 1.5.8e, I haven't been able to keep the program running for more than a couple of days.

The .bat file I use to start NXT uses the following line to start NXT:
Code: [Select]
start "NXT NRS" java -Xmx1024M -cp nxt.jar;lib\*;conf nxt.Nxt

After a day or two, NXT dies.  Here's the end of a couple log files:
Code: [Select]
2015-05-17 01:43:58 FINE: Blacklisting 188.48.72.91 because of: nxt.dy: Peer sends invalid transactions: [nxt.dy: Invalid transaction signature for transaction {"senderPublicKey":"fad868f91878093dd9c2422bdb4f601a9e6c3b2b6d0f12559b4fbfd04ef85c6f","signature":"adf09a3f0984a40eeb2adf751147639c0a2ae780b55d1fb0a426b3f0851887050bd10a014d34c8287035846ea0d67baa76757e30ed84df0dc3e7f2bd8e74c50f","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"7217849232031679657","attachment":{"version.Message":1,"messageIsText":true,"message":"{\"contract\":{\"description\":\"SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description. SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description. SEO","version.ArbitraryMessage":0},"subtype":0,"amountNQT":0,"recipient":"0","ecBlockHeight":428929,"deadline":1440,"timestamp":46547039}]
nxt.dy: Peer sends invalid transactions: [nxt.dy: Invalid transaction signature for transaction {"senderPublicKey":"fad868f91878093dd9c2422bdb4f601a9e6c3b2b6d0f12559b4fbfd04ef85c6f","signature":"adf09a3f0984a40eeb2adf751147639c0a2ae780b55d1fb0a426b3f0851887050bd10a014d34c8287035846ea0d67baa76757e30ed84df0dc3e7f2bd8e74c50f","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"7217849232031679657","attachment":{"version.Message":1,"messageIsText":true,"message":"{\"contract\":{\"description\":\"SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description. SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description. SEO","version.ArbitraryMessage":0},"subtype":0,"amountNQT":0,"recipient":"0","ecBlockHeight":428929,"deadline":1440,"timestamp":46547039}]
at nxt.ez.a(Unknown Source)
at nxt.ez.a(Unknown Source)
at nxt.peer.u.a(Unknown Source)
at nxt.peer.PeerServlet.a(Unknown Source)
at nxt.peer.PeerServlet.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at org.eclipse.jetty.websocket.servlet.WebSocketServlet.service(WebSocketServlet.java:167)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:83)
at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:364)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(DoSFilter.java:470)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:322)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:292)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:517)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:497)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Unknown Source)
2015-05-17 01:53:52 FINE: Unblacklisting 5.9.8.9
2015-05-17 01:54:52 FINE: Unblacklisting 188.48.72.91
2015-05-17 02:08:08 FINE: Will process a fork of 2 blocks
2015-05-17 02:08:08 FINE: Rollback from block 3534093948153901715 at height 428945 to 2778486728366414826 at 428944
2015-05-17 02:08:14 FINE: Switched to peer's fork
2015-05-17 02:08:15 FINE: Error sending request to peer 176.94.115.161: Read timed out
2015-05-17 02:08:27 SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
java.lang.OutOfMemoryError


Code: [Select]
2015-05-19 06:04:33 FINE: Unblacklisting 82.226.204.140
2015-05-19 06:05:33 FINE: Unblacklisting 195.28.85.114
2015-05-19 06:05:33 FINE: Unblacklisting 124.135.104.190
2015-05-19 06:18:46 FINE: Inbound WebSocket connection with 97.87.75.68 completed
2015-05-19 06:29:15 FINE: Hallmark host 54.77.53.42 doesn't match 131.72.136.251
2015-05-19 06:40:09 FINE: Error sending request to peer 217.17.88.5: Read timed out
2015-05-19 06:43:26 FINE: Inbound WebSocket connection with 97.87.75.68 closed
2015-05-19 06:45:45 FINE: Error sending request to peer 77.88.208.12: connect timed out
2015-05-19 06:48:50 FINE: Inbound WebSocket connection with 90.51.43.27 closed
2015-05-19 06:49:02 FINE: Inbound WebSocket connection with 23.88.59.163 closed
2015-05-19 06:49:27 FINE: Database connection pool current size: 26
2015-05-19 06:49:27 FINE: Database connection pool current size: 27
2015-05-19 06:49:27 FINE: Database connection pool current size: 28
2015-05-19 06:49:27 FINE: Database connection pool current size: 29
2015-05-19 06:49:27 FINE: Database connection pool current size: 30
2015-05-19 06:50:56 SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
java.lang.OutOfMemoryError: unable to create new native thread
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.addWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.execute(Unknown Source)
at java.util.concurrent.AbstractExecutorService.submit(Unknown Source)
at nxt.cc$1.a(Unknown Source)
at nxt.cc$1.a(Unknown Source)
at nxt.cc$1.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Is this a problem with my setup?  I haven't seen any other reports for this so far.  Previous versions such as 1.5.6e did not have this problem.  Same .bat file used in the past.



12
Nxt General Discussion / Re: Public NRS to query
« on: May 12, 2015, 12:56:00 am »
how can we see a list of public hallmark nodes?

Another list can be seen here - http://peerexplorer.com/

13
Nxt General Discussion / Re: [CORE] Critical Update to 1.4.17
« on: April 20, 2015, 04:51:26 pm »
Don't break NAS.. we just got it going again.  :)

BURST (forked from NXT) just announced an update today as well indicating fixes for the asset exchange along with a few other things.

14
Nxt General Discussion / Re: Blockchain Malware Question
« on: March 27, 2015, 06:14:37 pm »
The block chain can store malicious data but it can not execute malicious code alone.  An application such as a modified wallet could be used to locate malicious data in the chain and act accordingly.  As long as people are not using untrusted wallets and their systems are clean from unwanted programs, this wouldn't be an issue.  It's no different than the malicious code that was stored in .jpg files and executed by an application on a system.

If you look at the common malicious programs today, a large number of them are just downloaders which replicate and attempt to download additional malicious code from the web (web servers or whatever).  In theory, one of these downloader programs could download data from a list of public nodes (bitcoin, NXT, etc.) and cause problems.  This process would be somewhat short lived because once the virus scanners detect the downloaders and the data in the block chain, the threat would become minimal.

A more likely scenario I'd expect to see is someone using the block chains as a communication platform to instruct malicious applications to perform tasks.  I don't think it would be too difficult to write an application that monitors a single or multiple NXT accounts from any public node.  (It could also monitor the same account(s) for NHZ, NAS or any other alt using the same account format for additional data sources.)  It would wait for a transaction to show up with a message containing the instructions for the bot to download malware, execute programs, start email spamming, apply updates to itself such as adding new public nodes to use, etc.  All someone would need to do is build that application, infect as many systems as possible and they now have a botnet which they can control by sending AM transactions to an account.  As virus scanners pick up the malicious code on the infected systems, new versions would be created all using the same source for instructions, the block chain.

15
Nxt Mobile / Re: [ANN] Nxt Mobile
« on: March 17, 2015, 05:06:34 pm »
I downloaded this last night but haven't had much time to test it yet.

First thought or comment though.  The client defaults to a single public node.  If that node goes down for whatever reason, the application won't function.  If 1000s of people pick this up and start using it, that node could become over loaded.  (I don't know anything about the default node.)  I know people can change the node to their own but is the targeted user group going to know what server to use?

A few options I'd recommend:
- add a list of several nodes where a node is randomly selected when the application starts to balance the load on public servers
- gives the application the ability automatically switch to another node if one stops responding
- list the servers in a drop down menu so the average user can select a different server
- keep the ability to add private servers to the list, but possibly add the ability to remove or ignore the default public servers for the paranoid

I don't think you want your application to stop if the owner of the default node decides to shut down the node for whatever reason (updates, etc.).

I'll spend some time and actually test the functionality tonight.  :)

16
Nxt General Discussion / Re: A question from the Nxt Facebook Group
« on: March 10, 2015, 10:29:27 pm »
priceNQT is always the price of NXT / 100000000. NQT refers to NextQuant, which is 1/10^8 NXT
So for your example:
"priceNQT":"17100000000" = 171 NXT


Wouldn't priceNQT = (NXT * 100000000) if (priceNQT / 100000000) = NXT?

17
Alternate Cryptocurrencies / Re: MapOfCoins
« on: March 03, 2015, 05:56:54 pm »
There's a few missing such as NFD.
(Can't post the link but search for NFDcoin and find the bitcointalk link.)

Although, it was just announced yesterday I believe that NFD is being aquired by NHZ (or HZ) and will be ending soon.

There's also:
FIM (FimKrypto)
NTX
BILS (BilShares) (dying - 3 or 4 nodes left)

NBC (which didn't go very far)

On my "not released yet" or "beta" list:
NEM
NEX
Stag

18
ORA / Re: NAS diaspora
« on: February 19, 2015, 09:48:31 pm »
You don't need to modify the config file at all.  I just checked and your peer port is open now.  My NAS client is connected to you as well now.

19
ORA / Re: NAS diaspora
« on: February 19, 2015, 04:46:16 pm »
Ah, ok.  I saw forging on your image so I thought it was you.  :)

My IP address is in your peer list so you are connected to me.  NAS (and NXT) only shows peers that the client is connecting out to, not incoming connections.  The fact that you're connected to me should be fine but if you want clients to connect to you then yes, you'll need to open a firewall port to your client.  The default port for NAS is 7871 (I believe) so if you're using the default, that's the port.  If you're not using the default port, you'll need to check the config file, look for "nas.peerServerPort=" and the port number will follow.

20
ORA / Re: NAS diaspora
« on: February 19, 2015, 03:02:51 pm »
So you're the one forging all of the blocks.  ;)

The blocks stop when your client is offline.

My list:
Address   Weight   Downloaded   Uploaded   Application   Platform
  flipflop.mooo.com   986'100   29 MB   13 MB   NRS 1.1.3.N1   CubieBoard2
  cb2.flipflop.mooo.com   986'100   22 MB   10 MB   NRS 1.1.3.N1   CubieBoard2
  nxtnode.ddns.net   0   3 MB   4 MB   NRS 1.1.3.N1   PC
  89.247.173.211   0   196 KB   188 KB   NRS 1.1.3.N1   CubieBoard2
  62.42.108.235   0   105 KB   62 KB   NRS 1.1.3.N1   PC
  89.247.163.145   0   731 KB   711 KB   NRS 1.1.3.N1   CubieBoard2
  cb2.flipflop.mooo.com   986'100   7 MB   4 MB   NRS 1.1.3.N1   CubieBoard2


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