NXT :: descendant of Bitcoin - Updated Information

[pinarello]

NXT Newsletter #2

http://nxter.org/nxt-newsletter-2/

nice work thank you!

[Damelon]

New Nxt Clients - updated Press release:
https://docs.google.com/file/d/0BwAGADgnQcrtYW9aZDZLQ1R0MVE/edit

So community, what do you think now?

Good, but missing Offspring.

[bitcoinpaul]

Bitcoin depends on a small network of mining nodes who support their operations by generating a fixed profit of 3600 bitcoins per day.  The available daily operating budget to keep Bitcoin from freezing up is thus $3.6M or less (at $1K/BTC or under) to  generate the current 25 million GHash/s needed daily.  A representative miner “pickaxe” is a Butterfly Labs Monarch costing $2000 and using 350W of power to produce 600 GHash/sec. Thus the current Bitcoin mining network has sunk unit infrastructure costs of at least $83 million and (at $0.10/KwH) ongoing electricity costs of at least $35,000 per day.  

Both costs are rising faster and faster. Exponential growth of Bitcoin’s hashrate (see blockchain.info/charts/hashrate) means mining rigs and energy use will skyrocket out of control, sooner rather than later.  Bitcoin, and clones like Doge, are thus by their very nature destined to fail.

NXT is the sustainable solution to this problem.  By using cooperative transparent forging, not competitive gigahash mining, NXT does not have an exponential forcing function at its core that drives its costs and energy consumption ever higher.  A NXT blockchain support network of 1000 Odroid U3 nodes has a one-time unit infrastructure cost of only $60 thousand and uses only $48 per day in electricity – forever.  
 

You could maybe include that every NXT is a virtual mining machine with zero power consumption. I think this is a nice 'picture' to grasp.

[pinarello]

cross posted

Unclaimed coins fund forming commitees.

candidates for the commitees, please apply!

https://docs.google.com/spreadsheet/ccc?key=0AsrKGhOkVcFpdFRFeHNUdWx3Qy1nTjBPLUFNWUJKQkE&usp=sharing

Please somebody, post this on nextcoin.org also thx

Pin

[salsacz]

New Nxt Clients - updated Press release:
https://docs.google.com/file/d/0BwAGADgnQcrtYW9aZDZLQ1R0MVE/edit

So community, what do you think now?

Nice document. You could however add some Offspring screenshots from here https://bitbucket.org/incentivetoken/offspring-public/wiki/Home.

thank you, so the version with Offspring:
https://docs.google.com/file/d/0BwAGADgnQcrtR3ZCdVRkNExZSVE/edit

[opticalcarrier]

cross posted

Unclaimed coins fund forming commitees.

candidates for the commitees, please apply!

https://docs.google.com/spreadsheet/ccc?key=0AsrKGhOkVcFpdFRFeHNUdWx3Qy1nTjBPLUFNWUJKQkE&usp=sharing

thx

what are the planned scopes and responsibilities for the 3 groups?  seems to me that tech/infrastructure will overlap quite a bit

[rickyjames]

Sorry to say, if you cut away the smoke and mirrors NXT is not a way to make money by mining or forging.  NXT makes mining obsolete by making the required infrastructure so cheap that it's going to happen as a low -cost NXT community effort just because we want it to happen.

Here's some words I'm writing for distribution in Texas:

NXT Is Green

Ecological?  Financial?  BOTH !!!

Bitcoin depends on a small network of mining nodes fighting for their share of a fixed profit pool of 3600 bitcoins per day.  The only thing keeping Bitcoin from freezing up is $3.6M or so (at $1K/BTC or under) inflation per day, funding miner generation of the current 25 million GHash/s needed daily.  A representative miner “pickaxe” is a Butterfly Labs Monarch costing $2000 and using 350W of power to produce 600 GHash/sec. Thus the current Bitcoin mining network has sunk unit infrastructure costs of at least $83 million and (at $0.10/KwH) ongoing electricity costs of at least $35,000 per day.  

Both costs are rising faster and faster. Exponential growth of Bitcoin’s hashrate (see blockchain.info/charts/hashrate) means mining rigs and energy use will skyrocket out of control, sooner rather than later.  Bitcoin, and clones like Doge, are thus by their very nature destined to fail.

NXT is the sustainable solution to this problem.  By using cooperative transparent forging, not competitive gigahash mining, NXT does not have an exponential forcing function at its core that drives its costs and energy consumption ever higher.  A NXT blockchain support network of 1000 ($60 ea., 10W) Odroid U3 nodes has a one-time unit infrastructure cost of only $60 thousand and uses only $48 per day in electricity – forever.  
 

Excellent – thanks. I read the forum posts everyday trying to improve my (still) very limited understanding and this is one of those stand out posts that produce that 'Ah ha' moment.

Thank you for your kind words.  I've edited mine to the version above and I am going to try to get 2000 people to read them on March 6 at the Texas Bitcoin Conference.  Hopefully that will generate 2000 ah-ha moments - and 2000 new NXT users.

[TwinWinNerD]

Hey guys i need some help!

The reddit-tip-bot went opensource now and i need someone to check the code before i release the Bounty to the dev. Can someone please do this?

Please please

The source code resides in https://github.com/nxtip/nxtip and is GPLv2 licensed!

The bot is based on ALTCoinTip, with some extra files that emulate the bitcoind daemon behavior as far as ALTCoinTip is concerned, plus handle the deposits. See the src/ctb/nxtip* files.

Contact me, there might be a bounty for the code checking!


PUSH

[jkoil]

Code:

		for (w = 0, i = 0; i < 32; i++)
			w |= v[i] = tmp1[i];

Is my pascal version correct?

Code:

w:=0;
for i:=0 to 31 do
begin
  v[i]:= tmp1[i];
  w:=w OR v[i];
end;

What exactly is the "if (i==0) { i=0;}" supposed to do???

looks fine, but are you sure your Pascal compiler supports 0 as an array index?
(Can't remember if the starting index could be set ...)

What exactly is the "if (i==0) { i=0;}" supposed to do???

that looks like a place for a "conditional" breakpoint for debugging ...  unless someone had wanted to adjust some timing in the loop

Thanks for the review!

Yes, pascal arrays are 0-based. :-)

ok   apparently you have compiled it already.
I was just remembering that by default Pascal arrays are [1..n] but they can be set   [ 0 .. N ];
Once ported Pascal/C ... maybe it was Pascal to C and the arrays were used as 1..N. So then there was two different ways to be chosen in C.


About OR :
I guess the Pascal compilers are still case-insensitive. And they haven't invented different operators to logical/bitwise OR  and to Boolean OR
 

[rickyjames]

cross posted

Unclaimed coins fund forming commitees.

candidates for the commitees, please apply!

https://docs.google.com/spreadsheet/ccc?key=0AsrKGhOkVcFpdFRFeHNUdWx3Qy1nTjBPLUFNWUJKQkE&usp=sharing

thx

what are the planned scopes and responsibilities for the 3 groups?  seems to me that tech/infrastructure will overlap quite a bit

I think you're right.  Hopefully the techdev fund will support programming and infrastructure fund will support deploying permanent hardware nodes like the Odroid U3  - which I have been converted to from the Raspberry Pi as the low-cost solution for NXT.

http://hardkernel.com/main/products/prdt_info.php

[marcus03]

ok   apparently you have compiled it already.
I was just remembering that by deafult Pascal arrays are [1..n] but they can be set   [ 0 .. N ];
Once ported Pascal/C ... maybe it was Pascal to C and the arrays were used as 1..N. So then there was two different ways to be chosen in C.

In Pascal, characters in strings are 1 based, dynamic arrays are zero-bases and static arrays are based on whatever you defined them.

[Jean-Luc]

OK so as far as web browser javascript transaction generation and signing goes, does it matter where the end client sends their signed transaction to?  do they have to send it to a NRS process that has active forgers, or can they just send it to any NRS system with a synced blockchain?  Im asking because Im considering opening up API for all the 24 VPSs I manage on nxtcrypto.org and am also considering adding SSL certs for that domain into the Jetty for each server as well.

The node doesn't need to be forging. If you send a transaction to any node, it will broadcast it to others, and eventually a forging node will include it in a block.

[pinarello]

cross posted

Unclaimed coins fund forming commitees.

candidates for the commitees, please apply!

https://docs.google.com/spreadsheet/ccc?key=0AsrKGhOkVcFpdFRFeHNUdWx3Qy1nTjBPLUFNWUJKQkE&usp=sharing

thx

what are the planned scopes and responsibilities for the 3 groups?  seems to me that tech/infrastructure will overlap quite a bit

good question, TBD I think.

but you are a tech guy for sure  

edit: maybe one commitee would be a better solution?

[Come-from-Beyond]

According to Wiki TF decides the next forger dependent on the previous block. So, if there is a partition of the network N1 and N2, then the nodes in these two different partitions have different TF outputs.

So, there are two cases: (next blocks/accounts are C, C' (part of N1) and D (part of N2); TF1 and TF2 are the output of TF of N1 and N2 respectively)
1) TF1 says C; TF2 says D => branches will get longer as foreign blocks get rejected
2) TF1 says C; TF2 says C' => C will get accepted; C' will get rejected as N1 expects C => What does N2? I would say: penalize C', ignore C and move on on its branch.

Still don't see how this conflict can be resolved. I need some idea for that.

Nxt uses Bitcoin's consensus rule. How would Bitcoin resolve this conflict?

IIRC, each node analyzes the known graph and assumes the longest chain as the correct one.

The same in Nxt.

[jkoil]

ok   apparently you have compiled it already.
I was just remembering that by deafult Pascal arrays are [1..n] but they can be set   [ 0 .. N ];
Once ported Pascal/C ... maybe it was Pascal to C and the arrays were used as 1..N. So then there was two different ways to be chosen in C.

In Pascal, characters in strings are 1 based, dynamic arrays are zero-bases and static arrays are based on whatever you defined them.

ok, looks like that you have it ongoing already on the good rails

[Come-from-Beyond]

OK so as far as web browser javascript transaction generation and signing goes, does it matter where the end client sends their signed transaction to?  do they have to send it to a NRS process that has active forgers, or can they just send it to any NRS system with a synced blockchain?  Im asking because Im considering opening up API for all the 24 VPSs I manage on nxtcrypto.org and am also considering adding SSL certs for that domain into the Jetty for each server as well.

Any node can be used.

[opticalcarrier]

OK so as far as web browser javascript transaction generation and signing goes, does it matter where the end client sends their signed transaction to?  do they have to send it to a NRS process that has active forgers, or can they just send it to any NRS system with a synced blockchain?  Im asking because Im considering opening up API for all the 24 VPSs I manage on nxtcrypto.org and am also considering adding SSL certs for that domain into the Jetty for each server as well.

The node doesn't need to be forging. If you send a transaction to any node, it will broadcast it to others, and eventually a forging node will include it in a block.

ok, ill pursue getting SSL running on those VPSs, and opening up API for allowedBotHosts to * and leave allowedUserHosts nulled out to prevent remote forging, unless someone can think of a reason to open that up as well

IIRC, each node analyzes the known graph and assumes the longest chain as the correct one.

The same in Nxt.

Anon136's video described it as the chain that had the most stake involved in forging the blocks was the 'correct' one, even though there may be a longer chain.   

[Come-from-Beyond]

Anon136's video described it as the chain that had the most stake involved in forging the blocks was the 'correct' one, even though there may be a longer chain.   

It's slang. "Longer chain" == "chain with the most stake involved".

[rickyjames]

edit: maybe one commitee would be a better solution?

Ummmmmmmmmmmmmmmmmmmmmmmmmm ............ I don't think so.

[fmiboy]

UPDATE Clienxt GUI

version 0.0.6 [codename] Lite

Since last release, I got number of feedbacks, feature requests, bug reports. Thank you everyone for attention and using Clienxt GUI.

changelog:

* TestNet and Local - from this version on, user can change client from testnet to local and vice versa, simply by changing default values (Settings->Default settings) and restart client.
* Auto Update for Nxt - need some testing, With one click, check latest version, if yes, removes local nxt folder from /lib/ folder and downloads latest from download.nxtcrypto.org and unzips nxt folder in /lib/. Before update, please stop the server from Console window if you using Local version. after update is complete simple Restart server from Console window again. (from right click menu) In future, updates will keep database.
* Fixed Mac (OSX) cmd+c, cmd+v, cmd+x commands for all textfields (feature requested by swartzfeger and antanst)
* simple lightweight NXT Tray icon, minimized window will stay in System tray (near clock)! (feature requested by Mario123)
* Multi-thread support for all heavy operations
* Optimized transactions table (1 table has messages/assets/other transactions)
* Optimized assets table
* User can see his Assets in Overview window (account label, asset name, quantity)
* Fixed some Russian language words
* Support for German language (thanks to teletobi 11810049982317883239)
* Support for Portuguese language (thanks to gracias ...)
* Added support for Generate&Decode Tokens (in Unlock window)
* QR address generator (in Unlock window)
* Removed Watch Window and added option in simplified Unlock Window.
** Forging with multiple accounts by Unlocking them... (There is timer bug, yet to be fixed! And after restart need unlocking again working to get around this)
** Voting System (available features get All Polls, create Poll, Cast a Vote) more coming

NOTE: Voting System and Asset Exchange works only on testnet for now.

I know a lot changes in this release, but was going to wait until VS is completely released, currently it has two features create a poll and cast a vote, when more APIs are available it will implemented. Enjoy your testnet and public net use

------
Download
------
https://bitbucket.org/fmiboy/clienxt/downloads/clienxt_006.zip

------
Usage
------
Simply unzip archive and

- Windows users - double click Clienxt.jar and enjoy
- Linux&Mac users - in terminal ./Clienxt.run & and enjoy

------
Screenshots
------






------
Reports
------
report feature requests, bugs https://bitbucket.org/fmiboy/clienxt/issues?status=new&status=open


------
Support
------
Translators are very much welcome to contribute. PM here or fmiboy@mail.ru

Any donation is appreciated...
13792774143018875909

If you like work of Translators donate some
teletobi 11810049982317883239 (German)
garcias .#. (Portuguese)


Thank you for taking time to read this post and for using Clienxt GUI!