NXT :: descendant of Bitcoin - Updated Information

[msin]

We have the original c implementation by djb - let some cryptographers (dmitry was no crypto guy!) port it for us!

The bug was in original c version. The port by dimitry is just fine.

I know one thing: we still need a cryptographer for auditing!

If someone wants to write up an overview of what exactly we need for the crypto auditing, I can send it to a few Crypto experts I've been in contact with.  Just PM me.

Please, CfB, help with that.

Edit: what kind of 'experts'?

I've been in contact with several people, including Matt Green (zerocoin).  I was originally referred to Matt by Susan Waters (http://cs.jhu.edu/~susan/) who was his professor, and Susan also recommended Lisa Yin in the same email.  I've had contact with Lisa and she sounds open to an audit.  Lisa has a PHD from MIT in Crypto.  I have contact with a few other academics as well.

[bitcoinpaul]

If someone wants to write up an overview of what exactly we need for the crypto auditing, I can send it to a few Crypto experts I've been in contact with.  Just PM me.

Please, CfB, help with that.

Edit: what kind of 'experts'?

I've been in contact with several people, including Matt Green (zerocoin).  I was originally referred to Matt by Susan Waters (http://cs.jhu.edu/~susan/) who was his professor, and Susan also recommended Lisa Yin in the same email.  I've had contact with Lisa and she sounds open to an audit.  Lisa has a PHD from MIT in Crypto.  I have contact with a few other academics as well.

Right, Lisa. I remember (https://asktom.cf/index.php?topic=345619.msg4989534#msg4989534). Well, what do you think, CfB?

[swartzfeger]

I've been in contact with several people, including Matt Green (zerocoin).  I was originally referred to Matt by Susan Waters (http://cs.jhu.edu/~susan/) who was his professor, and Susan also recommended Lisa Yin in the same email.  I've had contact with Lisa and she sounds open to an audit.  Lisa has a PHD from MIT in Crypto.  I have contact with a few other academics as well.

Not trying to sound bossy, but you should have your NXT acct in your sig. This is critical stuff.

vs., say, bulldoge/puppydoge/underdoge/wolfe

[opticalcarrier]

Are there any jetty experts here?  Im trying to add new SSL cert to NRS's default keystore which is using default password of storepwd.  I used the keytool command to import a pkcs12 keyfile (containing server.key, server.crt, and intermediate.crt) as per instructions at http://www.eclipse.org/jetty/documentation/current/configuring-ssl.html but after 'NRS 0.7.3 started successfully.' message in console it bombs with

Code:

java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.jetty.start.Main.invokeMain(Main.java:297)
        at org.eclipse.jetty.start.Main.start(Main.java:724)
        at org.eclipse.jetty.start.Main.main(Main.java:103)
Caused by: java.security.UnrecoverableKeyException: Cannot recover key
        at sun.security.provider.KeyProtector.recover(Unknown Source)
        at sun.security.provider.JavaKeyStore.engineGetKey(Unknown Source)
        at sun.security.provider.JavaKeyStore$JKS.engineGetKey(Unknown Source)
        at java.security.KeyStore.getKey(Unknown Source)
        at sun.security.ssl.SunX509KeyManagerImpl.<init>(Unknown Source)
        at sun.security.ssl.KeyManagerFactoryImpl$SunX509.engineInit(Unknown Source)
        at javax.net.ssl.KeyManagerFactory.init(Unknown Source)
        at org.eclipse.jetty.util.ssl.SslContextFactory.getKeyManagers(SslContextFactory.java:904)
        at org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:297)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
        at org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:64)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
        at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:259)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
        at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
        at org.eclipse.jetty.server.Server.doStart(Server.java:336)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
        at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1250)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
        ... 7 more

no idea what Im doing wrong.  Does anyone see anything wrong with my keystore?

# keytool -list -keystore /root/nxt-kit/nxt/etc/keystore -storepass storepwd

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 2 entries

jetty, Nov 7, 2008, PrivateKeyEntry,
Certificate fingerprint (SHA1): 66:62:5A:2B:2F:96:E1:88:E7:27:19:E0:0E:C6:60:B0:FC:86:B2:64
1, Feb 12, 2014, PrivateKeyEntry,
Certificate fingerprint (SHA1): 0B:50:A2:84:81:4A:9C:15:42:6C:19:30:13:98:1D:B2:53:B6:C4:B1
#

[msin]

I've been in contact with several people, including Matt Green (zerocoin).  I was originally referred to Matt by Susan Waters (http://cs.jhu.edu/~susan/) who was his professor, and Susan also recommended Lisa Yin in the same email.  I've had contact with Lisa and she sounds open to an audit.  Lisa has a PHD from MIT in Crypto.  I have contact with a few other academics as well.

Not trying to sound bossy, but you should have your NXT acct in your sig. This is critical stuff.

vs., say, bulldoge/puppydoge/underdoge/wolfe

Why?  I don't need donations.  

[freigeist]

Are there some flaws or disadvantages when defining a stack on this low level?

Yes, it's hard to predict how much memory u'll need if u heavily exploit stack by using recursions and similar stuff.

Python has a recursion limit if a function calls itself for n cycles
the interpreter break execution and will throw an error.
Could something similar be implemented in NXT turing scripts?
Also if you reconsidered about stack languages maybe this
project could be something that could help you or give idea about development
or maybe I' m wrong

http://freecode.com/projects/magicjar

I says is sandboxed and it runs on java VM.

[rriky92]

Are there any jetty experts here?  Im trying to add new SSL cert to NRS's default keystore which is using default password of storepwd.  I used the keytool command to import a pkcs12 keyfile (containing server.key, server.crt, and intermediate.crt) as per instructions at http://www.eclipse.org/jetty/documentation/current/configuring-ssl.html but after 'NRS 0.7.3 started successfully.' message in console it bombs with

Code:

java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.jetty.start.Main.invokeMain(Main.java:297)
        at org.eclipse.jetty.start.Main.start(Main.java:724)
        at org.eclipse.jetty.start.Main.main(Main.java:103)
Caused by: java.security.UnrecoverableKeyException: Cannot recover key
        at sun.security.provider.KeyProtector.recover(Unknown Source)
        at sun.security.provider.JavaKeyStore.engineGetKey(Unknown Source)
        at sun.security.provider.JavaKeyStore$JKS.engineGetKey(Unknown Source)
        at java.security.KeyStore.getKey(Unknown Source)
        at sun.security.ssl.SunX509KeyManagerImpl.<init>(Unknown Source)
        at sun.security.ssl.KeyManagerFactoryImpl$SunX509.engineInit(Unknown Source)
        at javax.net.ssl.KeyManagerFactory.init(Unknown Source)
        at org.eclipse.jetty.util.ssl.SslContextFactory.getKeyManagers(SslContextFactory.java:904)
        at org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:297)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
        at org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:64)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
        at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:259)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
        at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
        at org.eclipse.jetty.server.Server.doStart(Server.java:336)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
        at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1250)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
        ... 7 more

no idea what Im doing wrong.  Does anyone see anything wrong with my keystore?

# keytool -list -keystore /root/nxt-kit/nxt/etc/keystore -storepass storepwd

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 2 entries

jetty, Nov 7, 2008, PrivateKeyEntry,
Certificate fingerprint (SHA1): 66:62:5A:2B:2F:96:E1:88:E7:27:19:E0:0E:C6:60:B0:FC:86:B2:64
1, Feb 12, 2014, PrivateKeyEntry,
Certificate fingerprint (SHA1): 0B:50:A2:84:81:4A:9C:15:42:6C:19:30:13:98:1D:B2:53:B6:C4:B1
#

maybe this http://wiki.eclipse.org/Jetty/Howto/Configure_SSL#Configuring_Jetty

[swartzfeger]

I've been in contact with several people, including Matt Green (zerocoin).  I was originally referred to Matt by Susan Waters (http://cs.jhu.edu/~susan/) who was his professor, and Susan also recommended Lisa Yin in the same email.  I've had contact with Lisa and she sounds open to an audit.  Lisa has a PHD from MIT in Crypto.  I have contact with a few other academics as well.

Not trying to sound bossy, but you should have your NXT acct in your sig. This is critical stuff.

vs., say, bulldoge/puppydoge/underdoge/wolfe

Why?  I don't need donations.  

I dig and respect. I guess you could always pass it along to someone else's project.

Shutting up and done being bossy.

[Damelon]

I've been in contact with several people, including Matt Green (zerocoin).  I was originally referred to Matt by Susan Waters (http://cs.jhu.edu/~susan/) who was his professor, and Susan also recommended Lisa Yin in the same email.  I've had contact with Lisa and she sounds open to an audit.  Lisa has a PHD from MIT in Crypto.  I have contact with a few other academics as well.

Not trying to sound bossy, but you should have your NXT acct in your sig. This is critical stuff.

vs., say, bulldoge/puppydoge/underdoge/wolfe

Why?  I don't need donations.  

Put my account in your sig then

[minusbalancer]

dotNXT client v.0.0.7.5 released:

• Transparent Forging Phase 4 support
• Added new getMilestoneBlockIds call partial support

dotNXT.0.0.7.5.setup.exe 951593 bytes
MD5      332602f8771848bfe336d0bc44737eee
SHA1   712664a0ef644e5b36fc89d4a3f250af945bef1e
SHA256   bc42c15d4eaa6b4f64fc4cbbe0f877959b15033b3a01c0da145e096f784fff08

[farl4web]

Sometimes I feel a bit frustrated about the fee-system of Nxt, when I see these kind of blocks passing by:


Fee = 0,0016%


Fee = 33,33%

It's not really fair and the rich are getting even richer this way. I love Nxt, but there are small flaws which needs to be addressed. The critics will talk negative about Nxt because of these kind of issues. 

Maybe a percentage instead of a fixed fee? Curious to hear about the options.

I dont think approaching anything from the "rich getting richer" is a good idea in a 100% POS system.  IMO though fee should be based on transaction byte size.  And even if it were based on scale of larger transactions = larger fee, the 'rich' are more apt to mine those higher fee blocks anyways.  There just doesnt seem to be a way to prevent the 'problem', as it were.  Regardless, 'the critics' wont matter the more and more NXT features are released.

The real concern here is people just giving up forging, or centralizing their forging power into central pools.

I understand that in a POS system the people with the most stake are getting more rewarded. But how about people with less money/BTC and also want to join Nxt?
I have over 100k, but in 24/7 I forge 9 NXT in a month... So from today I quited forging, to much risk for the reward. I am sorry.

I am just thinking out loud about how we can get Nxt more fair and better.

[ebereon]

Info for Raspberry PI 256MB with NXT 0.7.3:

Code:

Every 1,0s: echo -n "cpu:\t$"; vcgencmd measure_temp; echo -n "arm:\t$"; vcgencmd measure_clock arm; e...  Wed Feb 12 23:26:06 2014

cpu:    $temp=47.1'C
arm:    $frequency(45)=250000000
core:   $frequency(1)=250000000
emmc:   $frequency(47)=250000000
core:   $volt=1.05V
ram:    $volt=1.13V

Resouces:
top - 23:26:08 up 1 day, 6 min,  1 user,  load average: 0,64, 0,49, 0,49
Tasks:  76 total,   1 running,  75 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1,0 us,  5,8 sy,  1,0 ni, 92,3 id,  0,0 wa,  0,0 hi,  0,0 si,  0,0 st
KiB Mem:    249244 total,   226816 used,    22428 free,     1864 buffers
KiB Swap:   102396 total,     2172 used,   100224 free,    24948 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
18672 pi        20   0  4540 1316 1028 R   5,8  0,5   0:00.17 top
 5021 pi        26   6  278m 171m 3744 S   2,9 70,4  26:01.06 java
    1 root      20   0  2144  344  300 S   0,0  0,1   0:07.31 init

Device:            tps    MB_read/s    MB_wrtn/s    MB_read    MB_wrtn
mmcblk0           0,00         0,00         0,00          0          0
sda               0,00         0,00         0,00          0          0

NXT-Log(last 10 lines):
ALTER TABLE transaction ALTER COLUMN sender_account_id RENAME TO sender_id
[2014-02-12 20:38:16.573] DEBUG: Will apply sql:
ALTER INDEX block_generator_account_id_idx RENAME TO block_generator_id_idx
[2014-02-12 20:38:16.588] DEBUG: Will apply sql:
ALTER INDEX transaction_sender_account_id_idx RENAME TO transaction_sender_id_idx
[2014-02-12 20:38:16.621] Updated database is at level 13
[2014-02-12 20:38:16.822] Scanning blockchain...
[2014-02-12 20:47:07.788] ...Done
[2014-02-12 20:47:07.851] NRS 0.7.3 started successfully.
[2014-02-12 xx:xx:xx.xxx] DEBUG: Account xxxxxxxxxxxxxxxxxxx generated block xxxxxxxxxxxxxxxxxx

NXT started with java -Xmx150m ... (This RasPI is a model B with emulated ram (gpu_mem=260) for model A, model A is arriving this week)

Unlocking an account with some transaction takes a while. After some unlocking attempts it opens successfully.

Scanning blockchain takes ~9 minutes. 2MB's swaped.

Greets,
eb

PS: SolarPasPI (model B) was running 46 hours without sun shine. It takes to much power for german winter. I will test model A soon, which will take 2/3 of the power from model B...

[NxtMinnow]

Sometimes I feel a bit frustrated about the fee-system of Nxt, when I see these kind of blocks passing by:


Fee = 0,0016%


Fee = 33,33%

It's not really fair and the rich are getting even richer this way. I love Nxt, but there are small flaws which needs to be addressed. The critics will talk negative about Nxt because of these kind of issues. 

Maybe a percentage instead of a fixed fee? Curious to hear about the options.

Hi nxt community,
I will keep this short and sweet.  In response to farl4web, the rich are not getting richer per your observation of the 63016 nxt costing the same to send as 2 nxt.  In fact, the low transaction percentage cost of the larger transfer is one of nxt coin strongest advantages.  That transfer was from bter.com and it was confirmed lightning fast, another of the core advantages of nxt coin. 

We need more services and products sold from websites that accept nxt coin as payment.  This will drive adoption of the nxt coin platform.   Buy some NXT, move it off the exchanges, register aliases pointed to web URIs, build commerce sites that accept NXT as payment for products or services, and advertise, and the entire NXT ecosystem benefits.  HODL on NXT.

Developers, be calm and carry on.

[swartzfeger]

I am just thinking out loud about how we can get Nxt more fair and better.

I currently hold 7288 NXT. I just purchased 1500 more ($70 USD). I'd love to have 30k by April 3.

There are two ways to be fair:

1. Buy your NXT
2. Work/earn your NXT

That 1500 NXT I purchased? I could afford it because I signed up for an extra shift where I work. That's fair.

Sorry to sound inflammatory, but everything else is BS.

[opticalcarrier]

maybe this http://wiki.eclipse.org/Jetty/Howto/Configure_SSL#Configuring_Jetty

yes those were the instructions I used.  Actually most of that has already been done, as the NRS client as provided by JLP already has SSL enabled with a default keystore and a self-signed cert.

I just imported my cert in there as per those instructions, should be fairly simple, but...

----------------------------------------------------------------------------------------

I dont think approaching anything from the "rich getting richer" is a good idea in a 100% POS system.  IMO though fee should be based on transaction byte size.  And even if it were based on scale of larger transactions = larger fee, the 'rich' are more apt to mine those higher fee blocks anyways.  There just doesnt seem to be a way to prevent the 'problem', as it were.  Regardless, 'the critics' wont matter the more and more NXT features are released.

The real concern here is people just giving up forging, or centralizing their forging power into central pools.

I understand that in a POS system the people with the most stake are getting more rewarded. But how about people with less money/BTC and also want to join Nxt?
I have over 100k, but in 24/7 I forge 9 NXT in a month... So from today I quited forging, to much risk for the reward. I am sorry.

I am just thinking out loud about how we can get Nxt more fair and better.

BTC:  buy tons of mining power, which depreciates, and the cost of the BTC you earn also depreciates by 10% each year.  Or  buy tons of NXT to forge NXT, which doesnt depreciate.  NXT is just as 'unfair' as BTC is; Id say the fact that asic power depreciates puts NXT over the top.  As well as NXT is deflationary since some bozos destroy their NXT.

Dude, RIGHT FREAKING NOW is the opportunity to buy TONS of NXT, BEFORE it really goes mainstream.  We are at the point now comparable to BTC's stage when BTC was $0.01/BTC.  I just dont understand what people are bitching about.  Oh, but some other people bought 49M NXT for only 1BTC, WHAAAAAAAA!  Well what about the point when BTC cost was only $.0001/BTC, was that also not unfair?

[ChuckOne]

Sometimes I feel a bit frustrated about the fee-system of Nxt, when I see these kind of blocks passing by:


Fee = 0,0016%


Fee = 33,33%

It's not really fair and the rich are getting even richer this way. I love Nxt, but there are small flaws which needs to be addressed. The critics will talk negative about Nxt because of these kind of issues. 

Maybe a percentage instead of a fixed fee? Curious to hear about the options.

I dont think approaching anything from the "rich getting richer" is a good idea in a 100% POS system.  IMO though fee should be based on transaction byte size.  And even if it were based on scale of larger transactions = larger fee, the 'rich' are more apt to mine those higher fee blocks anyways.  There just doesnt seem to be a way to prevent the 'problem', as it were.  Regardless, 'the critics' wont matter the more and more NXT features are released.

The real concern here is people just giving up forging, or centralizing their forging power into central pools.

Well, can't see why a percentage would be bad.

Centralization is an issue. How do we counteract?

[Damelon]

I am just thinking out loud about how we can get Nxt more fair and better.

I currently hold 7288 NXT. I just purchased 1500 more ($70 USD). I'd love to have 30k by April 3.

There are two ways to be fair:

1. Buy your NXT
2. Work/earn your NXT

That 1500 NXT I purchased? I could afford it because I signed up for an extra shift where I work. That's fair.

Sorry to sound inflammatory, but everything else is BS.

I'd like to add that I've earned more in Nxt last month than I do at my regular job 

[farl4web]

Dude, RIGHT FREAKING NOW is the opportunity to buy TONS of NXT, BEFORE it really goes mainstream.  We are at the point now comparable to BTC's stage when BTC was $0.01/BTC.  I just dont understand what people are bitching about.  Oh, but some other people bought 49M NXT for only 1BTC, WHAAAAAAAA!  Well what about the point when BTC cost was only $.0001/BTC, was that also not unfair?

I'm not bitching dude, I'm just making constructive criticism. Let me phrase it like this:



Is 1 NXT per 1000 NXT transaction a better idea?  

[Damelon]

Dude, RIGHT FREAKING NOW is the opportunity to buy TONS of NXT, BEFORE it really goes mainstream.  We are at the point now comparable to BTC's stage when BTC was $0.01/BTC.  I just dont understand what people are bitching about.  Oh, but some other people bought 49M NXT for only 1BTC, WHAAAAAAAA!  Well what about the point when BTC cost was only $.0001/BTC, was that also not unfair?

I'm not bitching dude, I'm just making constructive criticism. Let me phrase it like this:



Is 1 NXT per 1000 NXT transaction a better idea?  

This is the situation now, when we still haven't got many transactions (although more than a month ago).

The fees will rise when services are in place. I am still working on getting payment modules in place and also working on a simple shop.
Once there are more shops/services, fees will rise dramatically. Block can hold up to 255 transactions. That can be a LOT of Nxt to forge!

I can imagine why you say this in the current situation, but if we make it higher now, we will have major adoption problems in the future.

Patience, and knowing that there WILL be higher fees in the blocks are important here

[opticalcarrier]

Well, can't see why a percentage would be bad.

Centralization is an issue. How do we counteract?

dude, if you think the thrashing to NXT reputation has been bad so far, just wait till howling about how "the 73 big fat rich NXT stakeholders have decided to mandatory charge a percentage based transaction fee".  Think about it this way: will you still think its a good idea the next time YOU want to transfer 10000 NXT and are hit with a 100 NXT transfer fee instead of our soon to be base fee of .1 NXT?  Especially when that 100 NXT ends up going to a 'big fat rich stakeholder'?  If you do this, prepare for NXT adoption rates to plummet.  

Lower transaction fees will actually end up ENCOURAGING more transactions.

WTF people, I swear its like all the libtards here in the US wanting to raise taxes EVERYWHERE to pay for their social programs, resulting in lower activity in business, and then they wonder why shit isnt working.  WTF people, yeah all the 0bamacare bullshit is REALLY helping out, people are starting to wake up now that employers are starting to cut hours of employees to prevent having to pay healthcare.  nice move dumbasses