elective-stereophonic
elective-stereophonic
Show Posts - ScripterRon
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

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.

Topics - ScripterRon

Pages: [1]
1
IGNIS / Insufficient IGNIS fee for exchange payment
« on: January 25, 2018, 02:10:11 pm »
ARDOR-9NLR-4UUL-6RPV-3ZA5B

This address has been creating IGNIS payments with an insufficient fee, resulting in the transactions remaining unconfirmed.  At the moment, this happens only for new accounts since there is an IGNIS bundler running with a low-enough rate to process payments to existing accounts.  I have been creating the accounts to get these pending transactions processed, but I'm not continually checking for unconfirmed transactions.

Jelurida has contacted the exchange about the problem but it is up to them to correct it.  In the mean time, if you have a new account and expect to receive payments from an exchange, make sure your account is created first.  This can be done by having somebody create a transaction to send you coins or a message.

2
Ardor General Discussion / Discarded child chain transactions
« on: January 24, 2018, 01:37:02 pm »
If you create a child chain transaction, make sure it gets confirmed before you assume that it is good.  If your fee is too low, the transaction will not get picked up by a bundler and will eventually expire.  Several transactions this morning were lost because a bundler was started with a very low rate and was then stopped.  However, the low rate was published across the network, resulting in transactions being created using this rate.

3
Nxt Monetary System / NxtMint Java minter
« on: January 16, 2015, 10:53:52 pm »
NxtMint 1.6.0

Download the latest version from NxtMint Releases
  • Unpack the files in a directory of your choice
  • Copy sample.NxtMint.conf to the application data directory and rename it to NxtMint.conf
    • Linux: <user-home>/.NxtMint/NxtMint.conf
    • Mac: <user-home>/Library/Application Support/NxtMint/NxtMint.conf
    • Windows: <user-home>\AppData\Roaming\NxtMint\NxtMint.conf
  • Copy sample.logging.properties to the application data directory and rename it to logging.properties
  • Edit NxtMint.conf to specify your desired NRS server (you can use scripterron.dyndns.biz if you don't run a local server) and your secret passphrase (the passphrase will not be sent to the server).  Update the other parameters as needed.
  • Install OpenCL if you want to use the GPU for minting
  • Rename and edit sample.mint.bat (Windows) or sample.mint.sh (Linux/Mac) as desired


NxtMint requires the Java 8 runtime since it uses language features that are not available in earlier versions of Java.
Nxt NRS works with Java 8, so you can upgrade without worrying that you will break the server.

NxtMint mints currencies defined by the Nxt Monetary System. A single currency can be minted as specified by the NxtMint configuration file. The minting algorithm is executed using one or more CPU threads or GPU devices. Newly-minted coins will be added to the account specified in the configuration file.

The NRS node used to create the mint transactions must accept API connections. This is done by specifying nxt.apiServerPort, nxt.apiServerHost and nxt.allowedBotHosts in nxt.properties. The account secret phrase is not sent to the Nxt server since the mint transactions are created and signed locally.

OpenCL is used to mint using the GPU and is not needed if you are using just the CPU. You will need to obtain OpenCL from your graphics card vendor (OpenCL may be automatically installed as part of the graphics card driver installation). The directory containing the OpenCL runtime library needs to be in either PATH (Windows) or LD_LIBRARY_PATH (Linux).  On Windows, OpenCL.dll is often placed in \Windows\system32 by the device driver installer, so it is always available and you won't need to update PATH.

Runtime Options
The following command-line options can be specified using -Dname=value

nxt.datadir=directory-path
Specifies the application data directory. Application data will be stored in a system-specific directory if this option is omitted:
  • Linux: user-home/.NxtMint
  • Mac: user-home/Library/Application Support/NxtMint
  • Windows: user-home\AppData\Roaming\NxtMint

java.util.logging.config.file=file-path
Specifies the logger configuration file. The logger properties will be read from 'logging.properties' in the application data directory. If this file is not found, the 'java.util.logging.config.file' system property will be used to locate the logger configuration file. If this property is not defined, the logger properties will be obtained from jre/lib/logging.properties.

JDK FINE corresponds to the SLF4J DEBUG level
JDK INFO corresponds to the SLF4J INFO level
JDK WARNING corresponds to the SLF4J WARN level
JDK SEVERE corresponds to the SLF4J ERROR level

Configuration options
The following configuration options can be specified in NxtMint.conf. This file is required and must be in the application data directory.

connect=host
Specifies the NRS host name and defaults to 'localhost'

apiPort=port
Specifies the NRS API port and defaults to 7876.

secretPhrase=phrase
Specifies the account secret phrase and must be specified. The secret phrase will not be sent to the NRS server.  Note that the configuration file is processed using the current user locale which can cause problems if the characters in the secret phrase aren't defined in the locale.

currency=code
Specifies the code for the currency to be minted.

units=count
Specifies the number of units to generate for each hash round and defaults to 1. The hash difficulty increases as the number of units increases but the transaction fee is 1 Nxt no matter how many units are generated. Thus you want to increase units as much as possible to reduce the cost of minting the currency but don't set it so high that you don't mint anything during a session. The count can be specified as an integer value or as a decimal value with a maximum number of digits following the decimal point as defined for the currency.

cpuThreads=count
Specifies the number of CPU threads to be used and defaults to 1. Specifying a thread count greater than the number of CPU processors will not improve minting since the mint algorithms are CPU-intensive and will drive each process to 100% utilization. Decrease the thread count if your computer becomes too hot or system response degrades significantly.

gpuIntensity=count
Specifies the GPU computation intensity and defaults to 0.  Your graphics card must support OpenCL in order to use the GPU.  You will need to try different values to determine an acceptable hash rate.  Specifying too large a value will result in performance degradation and GPU memory errors.  Start with an initial value of 10 and raise or lower needed.  A GPU will not be used if gpuIntensity is 0.   
   
gpuDevice=index,wsize,gcount
Specifies the GPU device number (0, 1, 2, ...), the work group size and the work group count.  The first GPU device will be used if this parameter is omitted.  This parameter can be repeated to use multiple GPU devices.  The GPU devices that are available are listed when NxtMint is started with a non-zero value for gpuIntensity. 

The work group size specifies the number of work items per work group and defaults to 256.  Performance can sometimes be improved by setting the work group size to the number of cores in a compute unit.  You can determine this value by dividing the number of cores on the card by the number of compute units.  For Scrypt, local memory contention can occur if the work group size is too large, so experiment with smaller values.   

The work group count specifies the number of work groups that will be executed by OpenCL before returning control to the application.  Specifying too large a value can result in adapter global storage being exceeded and can cause sluggish display performance as display work groups get delayed by mining work groups.

enableGUI=true|false
Specifies whether or not to enable the GUI and defaults to true. Disabling the GUI allows NxtMint to run in headless environments such as a disconnected service.

4
Nxt General Discussion / Invalid hallmarks
« on: January 08, 2015, 06:22:59 pm »
Nxt blacklists nodes with invalid hallmarks.  I've been seeing a lot of blacklisting due to invalid hallmarks.  To help people detect this problem, here is a list of recent failures (I've modified my version of NRS to display connect/disconnect/blacklist events).

I think there is a problem in the NRS IPv6 support where a DNS entry contains both A and AAAA records.  This is causing hallmark failures for IPv6 connections that I think should be valid.  I'll dig into this one some more.  The IPv4 failures are correct though - the hallmark address does not match the peer address.

2015-01-07 18:44:11 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for [2001:16d8:dd24:0:86c9:681e:f931:256], hallmark host is zdani.szn.dk
2015-01-07 19:13:35 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 91.201.23.46, hallmark host is 89.250.240.63
2015-01-07 19:21:55 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 23.89.192.152, hallmark host is 23.89.192.151
2015-01-07 21:12:49 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 89.250.243.240, hallmark host is 89.250.243.200
2015-01-07 23:06:43 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 95.25.214.116, hallmark host is vh44.ddns.net
2015-01-07 23:09:34 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for [2001:1af8:fe00:83f5:9d13:6876:8c5c:9312], hallmark host is banli.szn.dk
2015-01-07 23:20:55 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 91.201.23.46, hallmark host is 89.250.240.63
2015-01-07 23:41:26 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 54.88.185.158, hallmark host is 54.88.54.58
2015-01-07 23:43:08 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 23.89.192.152, hallmark host is 23.89.192.151
2015-01-08 01:18:32 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 89.250.243.240, hallmark host is 89.250.243.200
2015-01-08 01:51:25 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for [2001:6f8:1232:0:b25b:eb31:1683:a949], hallmark host is dilnu.szn.dk
2015-01-08 03:24:16 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 78.52.215.250, hallmark host is nxt.cryonet.de
2015-01-08 03:39:19 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 91.201.23.46, hallmark host is 89.250.240.63
2015-01-08 04:24:34 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 54.88.185.158, hallmark host is 54.88.54.58
2015-01-08 04:54:04 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 23.89.192.152, hallmark host is 23.89.192.151
2015-01-08 05:27:12 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 89.250.243.240, hallmark host is 89.250.243.200
2015-01-08 06:03:01 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for [2a01:7e00:0:0:f03c:91ff:fe73:9fcf], hallmark host is sluni.szn.dk
2015-01-08 08:22:06 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for [2001:1af8:fe00:83f5:9d13:6876:8c5c:9312], hallmark host is banli.szn.dk
2015-01-08 09:11:07 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 91.201.23.46, hallmark host is 89.250.240.63
2015-01-08 09:39:43 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 54.88.185.158, hallmark host is 54.88.54.58
2015-01-08 09:45:30 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for [2001:16d8:dd24:0:86c9:681e:f931:256], hallmark host is zdani.szn.dk
2015-01-08 10:09:58 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 89.250.243.240, hallmark host is 89.250.243.200
2015-01-08 11:06:25 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 23.89.192.152, hallmark host is 23.89.192.151
2015-01-08 11:23:17 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for [2a01:7e00:0:0:f03c:91ff:fe73:9fcf], hallmark host is sluni.szn.dk
2015-01-08 13:57:48 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 54.88.185.158, hallmark host is 54.88.54.58
2015-01-08 13:59:39 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for [2001:1af8:fe00:83f5:9d13:6876:8c5c:9312], hallmark host is banli.szn.dk
2015-01-08 14:10:51 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 91.201.23.46, hallmark host is 89.250.240.63
2015-01-08 14:39:20 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 89.250.243.240, hallmark host is 89.250.243.200
2015-01-08 15:22:36 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 23.89.192.152, hallmark host is 23.89.192.151
2015-01-08 16:12:35 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for 113.70.46.27, hallmark host is xypku.vicp.net
2015-01-08 17:14:57 FINE: PeerImpl.analyzeHallmark: Invalid hallmark for [2001:6f8:1232:0:b25b:eb31:1683:a949], hallmark host is dilnu.szn.dk

5
Nxt General Discussion / Creating hallmarks
« on: November 18, 2014, 06:31:22 pm »
A hallmark is used as a trust indicator when sending a request to a peer node.  The hallmark is tied to a host name and a Nxt account.  The adjusted weight for a hallmark is derived from the account balance.  You can use the same Nxt account for multiple hallmarks to spread the load among a group of servers.  If a Nxt node connects to two peers with the same hallmark account, it will split the adjusted weight between the two peers as determined by the hallmark weight ratios.  However, this happens only if both hallmarks have the same date.  If the hallmarks have different dates, the hallmark with the latest date is used and the earlier hallmark is ignored (its adjusted weight is set to 0).

This also has an effect when establishing connections.  If hallmark protection is enabled (the default), the local node will continue to create connections until it connects to the number of hallmarked nodes as specified by nxt.maxNumberOfConnectedPeers (default 20).  If a hallmarked node has its adjusted weight set to 0, it will not be counted when creating these connections.

So, if you want to use the same account for multiple servers, make sure the hallmarks are created with the same date.

6
Nxt Projects / NxtCore library
« on: October 13, 2014, 01:58:52 pm »
I'm working on a Java library for interfacing with the NRS API.  It handles creating the JSON request, sending the request to the node server and then processing the response.  Transactions are created and signed locally with no node interaction.  This means your secret phrase is never sent to the node server and the node server does not create the transaction bytes.  This is important because you should not trust a remote node.  By creating the transaction locally, a rogue server cannot provide a different transaction than what you requested.

The code is available at https://github.com/ScripterRon/NxtCore.  You can download the source and compile it yourself or download the compiled binaries from the Releases tab.  Javadoc documentation is provided.  I'm using Java 8 to take advantage of the new lambda and functional expression support but I'm willing to revert to Java 7 if this becomes a problem.

A sample wallet application is available at https://github.com/ScripterRon/NxtWallet.  You can download the source and compile it yourself or download the compiled binaries from the Releases tab.

I'm using new interfaces which will be available in NRS 1.3.0.  If you want to test the code, I'm running a public server at http://scripterron.dyndns.biz:7876.  This is a dual-processor Debian VPS with an SSD disk running the Java 8 runtime.  Since the NRS node is just used to transmit the signed transaction, this should be safe to use with NxtCore since the node cannot modify the transaction without invalidating the signature.

Support for Asset Exchange and Digital Goods Store will be added in the future.  I'm currently working on NxtMonitor which will allow you to monitor a remote node without having to logon to the node.  It will also use NxtCore to provide API support.

7
General / Invalid transaction message
« on: April 25, 2014, 09:56:11 pm »
This message is showing up on the NXT RRS console for the past 6 hours:

[2014-04-25 13:20:55.520] DEBUG: Dropping invalid transaction: Alias already owned by another account: freenxncoin9

It repeats every 5 seconds.  It doesn't appear to hurt anything, but I don't think it should keep repeating.  I'm running 0.9.9 on ScripterRon.noip.me.

Ron

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