elective-stereophonic
elective-stereophonic
Show Posts - neoranga singapore
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.

Messages - neoranga

Pages: [1] 2
1
Official Nxt Releases / Re: NRS v1.5.0e
« on: April 07, 2015, 06:48:21 am »
Amazing release! Congratulations to all the devs involved.

2
Official Nxt Releases / Re: NRS v1.4.9
« on: January 18, 2015, 04:05:09 pm »
Awesome! The speed of releases with improvements continues doesn't cease to impress me  :)

3
Official Nxt Releases / Re: NRS v1.4.7.1
« on: January 11, 2015, 12:14:50 pm »
Thank you, I don't need it now however a lot of people could ask this.

Is it planned to have backup function in wallet?

There is already backup functionality for your contacts, in the contacts page "Export contacts" and "Import contacts" at the top right corner.

4
Official Nxt Releases / Re: NRS v1.4.7.1
« on: January 11, 2015, 12:13:06 pm »
So I downloaded the latest version from nxt.org for OSX (it says 1.4.7.1 but downloads 1.4.7 only, with wallet 2.1.0 - that is the last version for OSX available at BitBucket).

Once I start and update the blockchain I get this (for UI designers leave a little bit of space before the red):



So I click and I see the version is not the latest



I then go to try to update and I am offered correctly a new version:



I click to download it and I get this:



and in my left bar the MS is missing...



Now, if I download the NSR manually, where do I go to replace the old one with the new one? Just double checking...

Refresh

Ctrl+F5 - i faced the same issue.

I'm having the same message. Control + F5 seems to do nothing on mac OS. I'm still getting message after several attempts  ???

Usually there is a specific NRS mac update in addition to the windows. Am I missing something? Seems to be related to catch but not sure what to do really.

I was also missing the Monetary System option after installing the new version.

I followed your advise and refresh the page in my browser (F5) and now it appears :)

5
Official Nxt Releases / Re: NRS v1.4.7
« on: January 08, 2015, 11:14:01 pm »
Two of my nodes (both with hallmark) updated to 1.4.7 also started going mad, what I see in the logs:

2015-01-07 18:21:09 FINE: Blacklisting 183.13.97.9 because of: nxt.NxtException$NotValidException: Peer sends invalid transactions
2015-01-07 18:21:09 FINE: Blacklisting 83.194.179.205 because of: nxt.NxtException$NotValidException: Peer sends invalid transactions
...
2015-01-08 14:55:38 FINE: Blacklisting 109.61.126.142 because of: java.util.concurrent.TimeoutException: Idle timeout expired: 30000/30000 ms
...
2015-01-08 23:57:36 FINE: Blacklisting 108.170.123.66 because of: null
2015-01-08 23:57:36 FINE: Blacklisting 65.93.178.27 because of: null
2015-01-08 23:57:39 FINE: Blacklisting 77.7.155.163 because of: null


I restarted both of them and they are working fine after downloading the last blocks that were not downloaded in the last day.

6
Official Nxt Releases / Re: NRS v1.4.7
« on: January 06, 2015, 11:11:49 pm »
Updated one node, thanks for the release.

7
Nxt Community News and Announcements / Re: NxtOrganization Report 2014
« on: January 06, 2015, 08:31:20 am »
Great job, well done in such a short time!

And the idea to create a demo web to experiment how to use a virtual currency for a total newbie, it's simply awesome! :D

8
Nxt Improvement Proposals / Re: 2 factor authentication in nxt clients
« on: January 02, 2015, 01:33:34 pm »
I was thinking about this topic when I found this thread and, after reading it, I actually align with the idea of HumanFractal but on a slightly different and I hope more secure setup:

  • Have a NRS server in another computer (your raspberry PI, a friend's NRS server, another NRS server you trust, etc.). There you can login with full passphrase and it offers an option to generate local (only to that server) 2FA
  • The NRS server at that moment asks you for a new password (maybe a pin or a password that you remember easily or created with LastPass) and in addition generates a 2FA seed for you.
  • The NRS server encrypts your original NXT passphrase first with the 2FA key and secondly with your new password from point above
  • User records 2FA key on their phone (in Google authenticator or Authy app)
  • User now has two options to login into this NRS server: use full passphrase or use new easier password and the 2FA current key that expires after 30 seconds

This way you need to attack the user's computer to get the new password and the server to get the 2FA seed or steal the phone. In addition, the user still has the original passphrase as a backup or to login into a new NXT client (which shouldn't happen very frequently).

9
Official Nxt Releases / Re: NRS v1.4.6
« on: January 01, 2015, 04:43:28 pm »
Good job!
The update went smoothly and the refactor of the html code is a very nice quality improvement :)

10
Official Nxt Releases / Re: NRS v1.4.5
« on: December 29, 2014, 08:44:02 pm »
Was keen to upgrade, but I just get a 'NRS server has exited.' error.
Same problem here - 'NRS server has exited.'
You need -Xmx1024M added to the line of the batch file or script that runs Java. Mine is a Windows batch file and looks like:
   start "NXT NRS" java -Xmx1024M -cp classes;lib\*;conf nxt.Nxt

Thanks for the tip but sadly, this also didn't work on my 512mb VPS box, failed miserably with:
Code: [Select]
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000f0236000, 180133888, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 180133888 bytes for committing reserved memory.


I deleted the nxt_db directory and started downloading the blockchain from scratch.

(The upgrade process works perfectly on my other 6GB RAM box)

11
Official Nxt Releases / Re: NRS v1.4.5
« on: December 29, 2014, 05:45:43 pm »
Update completed on one of my nodes. My experience:
  • Unzip to new folder and copied db + updated config file from old version
  • Started new NRS and it took 1/2 hour to update all tables and finish upgrading
  • Stopped NRS to restart safely and although the log said that NRS had stopped the application was still hanging on the system
  • Killed NRS, restarted and all working fine :D
Don't kill NRS.  H2 is compacting the database during NRS shutdown.  For the 1.3.5->1.4.5 upgrade, this can take awhile since the database grew to over twice its original size during the upgrade.
Ouch, I closed it following the advice to stop the application and starting it again after the update, I didn't know why it was taking so long to shutdown and there was no message about the compression on the log.

Can I trigger the compression again or will it do it automatically on the next shutdown?

12
Official Nxt Releases / Re: NRS v1.4.5
« on: December 29, 2014, 11:07:29 am »
Update completed on one of my nodes. My experience:
  • Unzip to new folder and copied db + updated config file from old version
  • Started new NRS and it took 1/2 hour to update all tables and finish upgrading
  • Stopped NRS to restart safely and although the log said that NRS had stopped the application was still hanging on the system
  • Killed NRS, restarted and all working fine :D

This is my script to update NXT to a new version on a linux machine (in case anybody is interested):
updateNXT.sh
Code: [Select]
#!/bin/bash
if [ "$#" -ne 2 ]; then
  echo "Incorrect number of parameters (two required)"
  echo "Usage: ./updateNXT.sh old-NXT-version-number new-NXT.zip"
  echo "Example: ./updateNXT.sh nxt-client-1.3.4 nxt-client-1.4.5.zip"
  exit 1
fi
oldNXT=$1
newNXT=$2
mv nxt ${oldNXT}
unzip ${newNXT}
cp ${oldNXT}/run.sh nxt/run.sh
cp -R ${oldNXT}/nxt_db nxt/
cp ${oldNXT}/conf/nxt.properties nxt/conf
diff ${oldNXT}/conf/nxt.properties nxt/conf/nxt-default.properties

I run it from the folder outside nxt and after the script finishes it shows the differences between the old configuration and the new default configuration template, which I use to edit my config and add/change anything that is required for the new version.

13
Official Nxt Releases / Re: NRS v1.4.5
« on: December 28, 2014, 07:36:33 pm »
Great! That was a quick release after the beta period. Congratulations to all involved.

Actually, I just realized my first contribution to import/export contacts made it to the release, from writing the first line of code to production in 8 days! I'm shocked, I wish my day-job company had this speed for delivering new features and improvements.

Awesome work guys!

14
Question: importing contacts replaces the one already in the wallet or add to them?

Only add, if there are any conflicts it will flash a message about it and skip the conflicting contact.


Just for reference, I will add the code changes notes here too:


This feature adds two buttons to the Contacts GUI to export and import the list of contacts with all their information to a JSON file for backup or migration purposes.

Considered in this code:
  • Import of duplicated/existing contacts
  • Manually tested: export, import and import with some duplicates with small sets of contacts

Not included in this code:
  • Automated testing of backup/importing (is there any framework setup for this?)
  • Internationalization (error messages and button translations)

15
Once you are at it, can also import/export the asset groups settings?

Once you own many different assets you can group them in different groups. That is also some info that gets lost and would be amazing it to be saved at will and imported.

Plus, with the import functionality, people could come out with "templates" on how assets should be categorised so when you finally own some assets it automatically goes in a predefined group :)

Just an idea. Amazing work you have done with the contacts ;) (again, also there files with all the VIP/big spenders/etc wallets and matching names will be a good sharing thing)

R
Wau, I didn't even know we have that feature, I was searching for it and found it by accident, I wonder how many people know about it. Anyway, I will see how the contacts feature goes (possible bugs, pending translations and integration in the official release if possible), and then I'll take a look at the "new" categories feature ;)

16
Nice one, thanks a lot for the effort. Would be real practical to have in there.
I assume I can download the two files there and use it now?
Yes, you can start using it just by replacing those three files in your nxt folder, but for some reason (I imagine related to security?) there are compressed files for each of these files in the same folder with the same name and extension .gz, you need to remove those and login again in the wallet to see the changes in action.

17
I've finished with both the export and import buttons, all code submitted for review:
https://bitbucket.org/JeanLucPicard/nxt/pull-request/23/export-import-contacts/diff

It's my first time submitting code to NXT so I apologize in advance for all the code guidelines and rules I may have broken with this pull request ;)

It looks something like this:


18
I started working on the simple export contacts functionality and got it working on my first NXT forked code:
https://bitbucket.org/neoranga55/nxt/commits/0076763ec657a7e2fa66f0e909ba6730af36cc96


Second part is importing this data to a new browser, I haven't read any documentation to see if I'm doing the code changes in the standard way, I guess some items are still pending, like: automated tests, error messages and translations of text. Does anybody know where to go to find out more on these topics and if I'm missing more?
Nice, does this export to a separate smaller db?
This exports your contacts list to a text readable JSON file, example:
Code: [Select]
{
"NXT-6MVF-XTDR-MDTK-DPHEU":{"name":"Coinomat","email":"","account":"NXT-6MVF-XTDR-MDTK-DPHEU","accountRS":"NXT-6MVF-XTDR-MDTK-DPHEU","description":"","id":3},
"NXT-K5KL-23DJ-3XLK-22222":{"name":"pool.nxtcrypto.org","email":"","account":"NXT-K5KL-23DJ-3XLK-22222","accountRS":"NXT-K5KL-23DJ-3XLK-22222","description":"","id":8}
}

19
I started working on the simple export contacts functionality and got it working on my first NXT forked code:
https://bitbucket.org/neoranga55/nxt/commits/0076763ec657a7e2fa66f0e909ba6730af36cc96


Second part is importing this data to a new browser, I haven't read any documentation to see if I'm doing the code changes in the standard way, I guess some items are still pending, like: automated tests, error messages and translations of text. Does anybody know where to go to find out more on these topics and if I'm missing more?

20
Consensus Research / Re: The Paper on Long-Range attack & Nothing-at-Stake
« on: December 18, 2014, 02:27:34 pm »

Thank you! If I understand you correctly that is the same we called "Hidden multibranch" attack, so we think that it is practically impossible to build a chain better than the rest of the network. The key things are the measure function and baseTarget validation procedure. So alone forger should have very significant stake (around 25%+) to produce a better chain. However a short range attacks are still possible due to the block delays in the "best" chain if the rest of the network remains singlebranch and the attacker does multibranching. The easiest opposition is to be multibranch for the network itself.

We do not use checkpoints in the model as we hope the solution could be achieved using the correct block measure function. I suggest however that in practice they could be used to stabilize the branching for hard cases.

Ok, so someone can't just throw a load of computing power with a relatively small stack and generate a viable branch. (Good, sick of hearing bitcoiners tell me that's easy.)

I'm thinking specifically of an attack whereby an attacker tracks down a number of the people who were part of the initial genesis block of Nxt. They manage to buy the addresses used, now empty of current Nxt and worthless to the owners, and manage to hold the addresses of a large amount of historical Nxt. (Say 70%+). They start forging a new chain using this 70%, fastforwording through blocks, faking checkpoints and maybe faking transaction volume until this new chain catches up with real chain. Now, to someone already on the main chain, they aren't going to mistake this new chain for the real chain. But when someone joins the network for the first time, could they be fooled into thinking that the new chain is the real one?

I understood this problem is mostly fixed with the Economic Clustering: each transaction has a signed reference to a previous transaction/block in the chain history so it can't be reused when rebuilding a hidden branch from scratch because referenced hashes will never match. If a new node starts and sees this rebuilt fake branch none of the recent transactions will match any other node.
At least this is how I imagined it will work.

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