NXT :: descendant of Bitcoin - Updated Information

[Come-from-Beyond]

Any chance to be able to have function calls to a subset of what is in nxt core?
That way for extra cost, sha256 can be done without bloating script with lots of opcodes

Let's see how it works without SHA256 and then decide.

[1714822900]

1714822900

[1714822900]

1714822900

[1714822900]

1714822900

[1714822900]

1714822900

[Come-from-Beyond]

Any chance to be able to have function calls to a subset of what is in nxt core?
That way for extra cost, sha256 can be done without bloating script with lots of opcodes

Basic cryptographic functions should be made opcodes. Implementing sha in this really doesn't make much sense. 

Why would someone need SHA256 in a script?

[lucky88888]

Tonight I was thinking again about the fees. We should not change the fees already, it's not wise.

In this early fase of Nxt I hear nobody complaining about the high fees, mostly because not a lot of payments are done.

But I DO hear a lot of complaining about the joke of forging. In the early fase of a cryptocoin, the miners/investors are the most important people, they make a coins succesfull (look at Dogecoin). To get a lot of attention, we need to attract the miners and investors first!

Later when it gets more populair you can lower the fees!

Actually at the moment most blocks mined are with 0 fees inside. So lowering the fee may encourage many new nxters with very low balances to play around and afford to send a friend a nxt without bankrupting their own.

With new lower fees you may actually receive 0.1fees in almost all blocks, this is better than 0 fees received. Which actually is more enticing to forging. Most new nxters are not here to forge for a profit at this early stage of the growing nxt economy, but they are forging because they are hoping they would receive something at all.

As the nxt economy grows, naturally things will come together, but this would encourage a better boost.

EDIT: MOST doge owners are probably in their teens, and the most would probably have 100doges and be very happy about it. Think how much is that worth?? nearly nothing, but that 100doge multiply by a million teens, that is something. Which is one reason doge is not dead yet.

Now think of nxt in the same situation, young people getting their nxt from faucets would be their only source of nxt income, everyone receives 1-2nxt some may have 10nxt! wow! Now if they are able to spend 1 or 2 nxt without bankruptcy i'm sure they would be happy to pass it on to their friends.
This, multiply by 1million and it doesn't seem so stupid for those kids who only have 1 or 2nxt.

EDIT 2： Kids/Teens are what causes viral things on the internet that just explodes over night. Maybe someone should think of marketing somthing towards the younger generations.

[landomata]

Guys & Gals,

I think it would be great to have a Asset Exchange Explorer type website similar to our blockexplorer http://87.230.14.1/nxt/nxt.cgi?action=1


Development can begin now so that it would be ready when the Asset Exchange officially launches.

[CIYAM]

Why would someone need SHA256 in a script?

Atomic-cross chain transactions and the like will require a hash function (I would assume SHA256 would be the most likely to include).

If we can't get atomic-cross chain transactions to work then I think the idea of being able to have a trust-less P2P "coin" exchange simply won't work (not that we have to use a "smart contract" to do this of course but it would seem like something reasonable to support as other such "use cases" undoubtedly will arise).

[Coinonaer]

this has to be a record amount of time between comments in this thread

I thought it must have been broken!
If it weren't for my blabber, it would have been over 90 minutes between posts.

wonder why its so quiet. it isnt some sort of holiday or something is it.

chinese new year!

Chinese new year is over now.I miss all of you.

welcome Back Sir 

[l8orre]

Guys & Gals,

I think it would be great to have a Asset Exchange Explorer type website similar to our blockexplorer http://87.230.14.1/nxt/nxt.cgi?action=1


Development can begin now so that it would be ready when the Asset Exchange officially launches.

I am making good progress on getting AE into my Client - as let's see what the testing does. Any tentative dates for 'official launch' of AE??
 

[Come-from-Beyond]

Advanced data compression algos are helped by moores law
Same for switches, routers
Cables are problem, but maybe big breakthrough in wireless bandwidth

shannon says otherwise, and we are much closer to his comm theory limit than we are to running up on moore.  thats a very large maybe in there as well

We could switch to three-valued logic for better compression. Not so effective as 2.72-valued but still better then binary...

[l8orre]

Holy java errors batman!

Code:

root@vps1:~/nxt-kit/nxt# java -jar start.jar 
WARNING: System properties and/or JVM args set.  Consider using --dry-run or --exec
2014-02-06 05:38:30.341:WARN:root:main: unavailable
javax.servlet.UnavailableException: Servlet class Nxt is not a javax.servlet.Servlet
	at org.eclipse.jetty.servlet.ServletHolder.checkServletType(ServletHolder.java:447)
	at org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:312)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
	at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:839)
	at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:300)
	at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
	at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
	at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
	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.addBean(ContainerLifeCycle.java:281)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(ContainerLifeCycle.java:213)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.updateBeans(ContainerLifeCycle.java:763)
	at org.eclipse.jetty.server.handler.HandlerCollection.setHandlers(HandlerCollection.java:89)
	at org.eclipse.jetty.server.handler.ContextHandlerCollection.setHandlers(ContextHandlerCollection.java:144)
	at org.eclipse.jetty.server.handler.HandlerCollection.addHandler(HandlerCollection.java:155)
	at org.eclipse.jetty.deploy.bindings.StandardDeployer.processBinding(StandardDeployer.java:41)
	at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186)
	at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:498)
	at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:146)
	at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
	at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
	at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:605)
	at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:528)
	at org.eclipse.jetty.util.Scanner.scan(Scanner.java:391)
	at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
	at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
	at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:560)
	at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:235)
	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.server.Server.start(Server.java:355)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
	at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
	at org.eclipse.jetty.server.Server.doStart(Server.java:324)
	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)
	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)
2014-02-06 05:38:30.366:WARN:root:main: unavailable
javax.servlet.UnavailableException: Servlet class Nxt is not a javax.servlet.Servlet
	at org.eclipse.jetty.servlet.ServletHolder.checkServletType(ServletHolder.java:447)
	at org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:312)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
	at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:857)
	at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:300)
	at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
	at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
	at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
	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.addBean(ContainerLifeCycle.java:281)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(ContainerLifeCycle.java:213)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.updateBeans(ContainerLifeCycle.java:763)
	at org.eclipse.jetty.server.handler.HandlerCollection.setHandlers(HandlerCollection.java:89)
	at org.eclipse.jetty.server.handler.ContextHandlerCollection.setHandlers(ContextHandlerCollection.java:144)
	at org.eclipse.jetty.server.handler.HandlerCollection.addHandler(HandlerCollection.java:155)
	at org.eclipse.jetty.deploy.bindings.StandardDeployer.processBinding(StandardDeployer.java:41)
	at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186)
	at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:498)
	at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:146)
	at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
	at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
	at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:605)
	at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:528)
	at org.eclipse.jetty.util.Scanner.scan(Scanner.java:391)
	at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
	at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
	at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:560)
	at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:235)
	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.server.Server.start(Server.java:355)
	at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
	at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
	at org.eclipse.jetty.server.Server.doStart(Server.java:324)
	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)
	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)

23 public hallmarked VPSs (ery heavy weights) down hard.

I experienced this epic java faiul too. rescanning whole blockchain now. interesting to see how long it'll take ..

[CrazyEyes]

Message by Come-from-Beyond
Relevance: 25.2%
Quote from: wesleyh on December 26, 2013, 10:51:24 AM
Here's a question from j0b (who for some reason can't post in here) :

"if a new client joins the network and need to sync the blockchain. if the clients current blockchain id is >= existing blockchain number - 10000 (or something).. send a compressed version of blockchain and extract it locally"

Wouldn't that save a bit on processing, as some clients may not have an up-to-date blockchain. (new users, etc)

Think of it as gzip compression in PHP.

Thoughts?



Looks like premature optimization.

............. Eh? Now all the sudden compression is a good idea. Arrogance is bless (changed that;))) /j0b

[Fatih87SK]

Hi CFB,

I think I've got it now. The final result;

https://i.imgur.com/FI2i3Ls.jpg

Aye, very similar to what I wanted. Tomorrow I'll find a better texture of slate, this one looks ugly.

Alright! I'm waiting for it. Will work on it when I get home.

Ps. I received two donations today. Thank you guys! You made me feel good!

[Passion_ltc]

Wasn't the AE integrated into the 0.6.0er update?

[lucky88888]

Guys & Gals,

I think it would be great to have a Asset Exchange Explorer type website similar to our blockexplorer http://87.230.14.1/nxt/nxt.cgi?action=1


Development can begin now so that it would be ready when the Asset Exchange officially launches.

I am making good progress on getting AE into my Client - as let's see what the testing does. Any tentative dates for 'official launch' of AE??
 

what date do you have in mind?

What about 7th of Feb?

[Come-from-Beyond]

J-L: I hate u......<engaging upgrade process for the second time today>

U shouldn't blame J-L. When I got info about the bug I offered a solution that was implemented in 0.5.12, actually it was just an uneffective work-around. Later BCNext poped up and proposed a better way to fix the bug. Enjoy 0.6.0.

[Come-from-Beyond]

Folks, I have a "Nxt Basics" question I want to run past people who Know Better.  I could dig through code to figure this out for myself, I know, but I don't trust my ability to read Java.

Re: block generation: Is this true?

When an account wants to forge a block, it generates a hash based on the previous block's signature and its own secret key.  This hash is compared to the target, and if it is lower than the target, it "wins" the right to forge a block.

Am I correct in my thinking that an account only generates this hash ONCE, and then waits until the "hit value" doubles enough, each second, for this value to "win"?

My gut tells me this is right, because it forms a sensible basis for Transparent Forging, etc.  But I want to make sure before I, um, say it in a podcast.

Thanks!

Not "secret" key. Public one.

[landomata]

J-L: I hate u......<engaging upgrade process for the second time today>

U shouldn't blame J-L. When I got info about the bug I offered a solution that was implemented in 0.5.12, actually it was just an uneffective work-around. Later BCNext poped up and proposed a better way to fix the bug. Enjoy 0.6.0.

BCNext popped up    

[lucky88888]

J-L: I hate u......<engaging upgrade process for the second time today>

U shouldn't blame J-L. When I got info about the bug I offered a solution that was implemented in 0.5.12, actually it was just an uneffective work-around. Later BCNext poped up and proposed a better way to fix the bug. Enjoy 0.6.0.

BCNext popped up    

BCNext is now some magical fairy

[ChuckOne]

If we do pruning (aka restart genesis) every 1k blocks, I'm pretty sure even the slowest smartphone can do it in under a second. Assuming a constant 1000tps, that's 60,000,000 transactions every 1000 blocks. I'm not sure how many processor cycles it takes to iterate through each transaction and do addition/subtraction to the proper accounts. I'm pretty sure my galaxy S2 (old phone, I know) can crunch that in a few seconds tops.

Why the hurry? 2 weeks (14*1440 blocks) should be fast enough for now. In the end, we can adjust the length according to our needs.

It's a security issue as well, if you cut the chain too often.

Remember, we still have only 0.05 TPS. So, don't worry. It the algos are flexible, we can change the parameters.

---

Another issue is, what to do with the other blockchains aka, script blockchain, file blockchain etc. Pruning these, seems highly impossible.

[Come-from-Beyond]

CfB:

How will new cryptos that use AM on top of NXT as their blockchain deal with the periodic purges of AM transactions?

And will implementation of .01 versus .001 for fees require differing amounts of work from dev teams ?

All AMs will be removed but child cryptos will have 1440 blocks from last chain. They r supposed to use it for storing actual data.

0.001 indeed requires more work than 0.01.

[ChuckOne]

Is it possible to have scaling transaction fees?


You know, for larger transactions to get hit with more transaction fees? This would be a really nice feature for NXT

I would like it.