NXT :: descendant of Bitcoin - Updated Information

[bitcoinpaul]

(\__/)
(='.'=)
(")_(")

As some guys who reviewed Nxt code already noticed it's quite easy to add new features to Nxt core. All that required is to add a new type/subtype and some code that processes it. After we start testing Asset Exchange I'll have a couple of weeks when I'll be fixing possible bugs mostly. It's quite a boring task and I have to switch to other (more interesting) things time to time to keep working at near-100% effectiveness. We (community) could add our own (not BCNext's one) feature to Nxt. I'm thinking of cloning main Ethereum feature - contracts powered with Turing-complete language. I ask the community if there is anyone who understands Ether concept deeply enough and could consult us.

PS: If Turing-complete language is a too tough task then we could pick some other feature.

What's up with the worm-virus-blabbering?

[1714853728]

1714853728

[1714853728]

1714853728

[1714853728]

1714853728

[landomata]

(\__/)
(='.'=)
(")_(")

As some guys who reviewed Nxt code already noticed it's quite easy to add new features to Nxt core. All that required is to add a new type/subtype and some code that processes it. After we start testing Asset Exchange I'll have a couple of weeks when I'll be fixing possible bugs mostly. It's quite a boring task and I have to switch to other (more interesting) things time to time to keep working at near-100% effectiveness. We (community) could add our own (not BCNext's one) feature to Nxt. I'm thinking of cloning main Ethereum feature - contracts powered with Turing-complete language. I ask the community if there is anyone who understands Ether concept deeply enough and could consult us.

PS: If Turing-complete language is a too tough task then we could pick some other feature.

Lets try  

I propose a TURING - COMPLETE COMMITTEE:

CFB
ANON
NXTCHG
BLOODYROOKIE
JAMES

Bump

sorry and RICOT, SMARAGDA

& A PORTION OF COMMUNITY FUNDS BE SET ASIDE IF THEY DECIDE TO PROCEED.

[google98]

In the meantime, I wish to report that 0.7.0 is running successfully with an H2 database backend, no more serialized java object files. No need to keep all blocks and transactions in memory anymore.

great, any ETA already?

[bitcoinpaul]

(\__/)
(='.'=)
(")_(")

As some guys who reviewed Nxt code already noticed it's quite easy to add new features to Nxt core. All that required is to add a new type/subtype and some code that processes it. After we start testing Asset Exchange I'll have a couple of weeks when I'll be fixing possible bugs mostly. It's quite a boring task and I have to switch to other (more interesting) things time to time to keep working at near-100% effectiveness. We (community) could add our own (not BCNext's one) feature to Nxt. I'm thinking of cloning main Ethereum feature - contracts powered with Turing-complete language. I ask the community if there is anyone who understands Ether concept deeply enough and could consult us.

PS: If Turing-complete language is a too tough task then we could pick some other feature.

Lets try  

I propose a TURING - COMPLETE COMMITTEE:

CFB
ANON
NXTCHG
BLOODYROOKIE
JAMES

Bump

let's vote

[Uniqueorn]

The issue Uniqueorn raised makes us admit that we are actually concerned about Nxts future, which we have been trying not to think about and act as if we are 100% confident. I have no doubt most of us believe in Nxts promised features and this community, we just need a clear picture so devs can be sure they are in the right way.

And in my opinion today is a healthy day for NXT.
We would be a bunch of idiots if we just blindly believe and have faith in something with little intel to go on.

I see it as a sign of health in the community that these questions are asked, it means that we all want to ENSURE NXTs succes and not just passively gamble on it.

[Come-from-Beyond]

What's up with the worm-virus-blabbering?

We can do nothing about it.

[l8orre]

what date do you have in mind?

What about 7th of Feb?

February 7th is a GO!

Go for what?

testnet....the AE client is ready....its not the most pretty.....I'll let the dev post about it....he has been working like a dog since last 3-4 weeks....HE IS GOOD he built HF prototype for Nasdaq.

I think he has a bot module inside the client...if im not mistaken.

Cool do you have more info somewhere?

I have a scalable high performance implementation of the api. Facilities for Use Case logic are there, and it should not be too difficult to put some basic functions in.

Right now I have a button for every API call, and I can shoot requests to the NRS from an apiBroker class that puts the requests into threads from the QThreadpool object.

ATM, the replies are dumped onto a QTextwidget. But there is a total of seven windows already in the app, and when someone wants more, it is a piece of cake to add them.

Also, the signals from the apiBroker can be connected to as many widgets on as many windows as desired. i.e. when you call or poll 'getBalance' and you have the balance displayed on multiple windows,
the displays on ALL the windows get updated automatically by the same signal.


Regarding the AE testnet. I have actually already been using it while testing my client, i.e. I have all the functions actually tested. This also means that I have created some assets, place and cancelled bid and ask orders, transferred assets, and sent messages.
The only function that I have not tested is the 'decodeToken', I had no time for that yet.


I'll need to put some basic use cases in - I can not promise to release the client on Feb7. but I'll see what I can do.
 



I'll post some code samples and more explanations on the client dev thread.

[martismartis]

The issue Uniqueorn raised makes us admit that we are actually concerned about Nxts future, which we have been trying not to think about and act as if we are 100% confident. I have no doubt most of us believe in Nxts promised features and this community, we just need a clear picture so devs can be sure they are in the right way.

And in my opinion today is a healthy day for NXT.
We would be a bunch of idiots if we just blindly believe and have faith in something with little intel to go on.

I see it as a sign of health in the community that these questions are asked, it means that we all want to ENSURE NXTs succes and not just passively gamble on it.

+1

I think my provocation with question about payment module has worked

[msin]

We would be a bunch of idiots if we just blindly believe and have faith in something with little intel to go on.

Isn't that what the stakeholders did.  

[Uniqueorn]

We would be a bunch of idiots if we just blindly believe and have faith in something with little intel to go on.

Isn't that what the stakeholders did.  

At the price they had to pay the potential profit was more than enough to justify investing.

[Jean-Luc]

In the meantime, I wish to report that 0.7.0 is running successfully with an H2 database backend, no more serialized java object files. No need to keep all blocks and transactions in memory anymore.

great, any ETA already?

First CfB should port the Asset Exchange bugfixes and new APIs to 0.6.0, and at the same time I plan to do some profiling and optimizations of 0.7.0 if needed, and then merge the 0.6.0 and 0.7.0 branches. I wrote most of the db code yesterday and today, and I am running it for the first time now. Let's see how many stack traces I find in the log tomorrow morning. Hope to have it ready for release by the end of the week.

[msin]

We would be a bunch of idiots if we just blindly believe and have faith in something with little intel to go on.

Isn't that what the stakeholders did.  

At the price they had to pay the potential profit was more than enough to justify investing.

I would say the exact same thing right now.

[google98]

In the meantime, I wish to report that 0.7.0 is running successfully with an H2 database backend, no more serialized java object files. No need to keep all blocks and transactions in memory anymore.

great, any ETA already?

First CfB should port the Asset Exchange bugfixes and new APIs to 0.6.0, and at the same time I plan to do some profiling and optimizations of 0.7.0 if needed, and then merge the 0.6.0 and 0.7.0 branches. I wrote most of the db code yesterday and today, and I am running it for the first time now. Let's see how many stack traces I find in the log tomorrow morning. Hope to have it ready for release by the end of the week.

wow, that's good news Thank you for your efforts !

[gs02xzz]

(\__/)
(='.'=)
(")_(")

As some guys who reviewed Nxt code already noticed it's quite easy to add new features to Nxt core. All that required is to add a new type/subtype and some code that processes it. After we start testing Asset Exchange I'll have a couple of weeks when I'll be fixing possible bugs mostly. It's quite a boring task and I have to switch to other (more interesting) things time to time to keep working at near-100% effectiveness. We (community) could add our own (not BCNext's one) feature to Nxt. I'm thinking of cloning main Ethereum feature - contracts powered with Turing-complete language. I ask the community if there is anyone who understands Ether concept deeply enough and could consult us.

PS: If Turing-complete language is a too tough task then we could pick some other feature.

Lets try  

I propose a TURING - COMPLETE COMMITTEE:

CFB
ANON
NXTCHG
BLOODYROOKIE
JAMES

Bump

sorry and RICOT, SMARAGDA

& A PORTION OF COMMUNITY FUNDS BE SET ASIDE IF THEY DECIDE TO PROCEED.

+1.

[Come-from-Beyond]

Well, what about an imperative language ran in a virtual machine? The machine shouldn't be stack-based though, it's quite difficult to comprehend workflow if stack is used.

[pinarello]

In the meantime, I wish to report that 0.7.0 is running successfully with an H2 database backend, no more serialized java object files. No need to keep all blocks and transactions in memory anymore.

great, any ETA already?

First CfB should port the Asset Exchange bugfixes and new APIs to 0.6.0, and at the same time I plan to do some profiling and optimizations of 0.7.0 if needed, and then merge the 0.6.0 and 0.7.0 branches. I wrote most of the db code yesterday and today, and I am running it for the first time now. Let's see how many stack traces I find in the log tomorrow morning. Hope to have it ready for release by the end of the week.

wow, that's good news Thank you for your efforts !

Why is that good news?

[Mistafreeze]

In the meantime, I wish to report that 0.7.0 is running successfully with an H2 database backend, no more serialized java object files. No need to keep all blocks and transactions in memory anymore.

great, any ETA already?

First CfB should port the Asset Exchange bugfixes and new APIs to 0.6.0, and at the same time I plan to do some profiling and optimizations of 0.7.0 if needed, and then merge the 0.6.0 and 0.7.0 branches. I wrote most of the db code yesterday and today, and I am running it for the first time now. Let's see how many stack traces I find in the log tomorrow morning. Hope to have it ready for release by the end of the week.

Out of curiosity, is it still going to be just a zip file that we drop into a folder and create a batch script to run, or are there prerequisites that will need to be installed?

[Come-from-Beyond]

If we fit all functionality into 50 instructions then it would be great.

[Jean-Luc]

Out of curiosity, is it still going to be just a zip file that we drop into a folder and create a batch script to run, or are there prerequisites that will need to be installed?

Yes, same zip file for now. The H2 database is a single 1.6 MB jar file that I put in webapps/root/WEB-INF/lib/. The blocks.nxt and transactions.nxt (and .bak) files will not be needed anymore. Instead, the database is kept under nxt_db subdirectory, currently takes 99 MB (compared to the blocks+transactions.nxt files taking 30 MB total).

The next step I consider, but haven't decided for sure yet, will be to switch to embedded jetty. Then the configuration of the Nxt server will be done using properties file, not the web.xml file. And it may require more reorganization of the whole zip file. But this is 0.8.0 stuff at least.

[msin]

In the meantime, I wish to report that 0.7.0 is running successfully with an H2 database backend, no more serialized java object files. No need to keep all blocks and transactions in memory anymore.

great, any ETA already?

First CfB should port the Asset Exchange bugfixes and new APIs to 0.6.0, and at the same time I plan to do some profiling and optimizations of 0.7.0 if needed, and then merge the 0.6.0 and 0.7.0 branches. I wrote most of the db code yesterday and today, and I am running it for the first time now. Let's see how many stack traces I find in the log tomorrow morning. Hope to have it ready for release by the end of the week.

wow, that's good news Thank you for your efforts !

Why is that good news?

In bold