Topic: NXT :: descendant of Bitcoin - Updated Information - page 873. (Read 2761624 times)

This is all normal, works as intended. It is telling you exactly what is happening - popping off a block, doing a rescan because alias assignment cannot be simply undone in a pop-off. The block generation attempt failed because in the meantime another block arrived and was accepted.

Yes, it is designed to be possible to upgrade without having to delete the nxt_db directory, that's the reason I bother with applying those SQL statements.

If too slow for Raspberries, do whichever is faster, upgrade or download from scratch.

Did I manage to improve the Raspberry performance with the last release?

How much does a single crypto cost? One that is .0000000013 BTC? I just want to be able to not have to worry about bundling very small valued things so we dont have the quantization problem.

The GUI can hide the extra precision. I am not talking about display. I am talking about what the low level protocol supports.

I am also not talking about reducing the fee to .00000001 NXT. The fee should be reduced an order of magnitude at a time as we find that it is a problem.

Reworking the code to add precision is the time where we can figure out how to add the most digits without adding too much overhead. We dont have to use or display that precision, but if we can get it essentially for free, why not?

James

I don't have problems downloading the whole blockchain with my RPi (not overclocked), no crashes, no restarts. It takes hours... hmm yes maybe 1-2 hours, but you don't have to do that on every update. The last time i did was when i switched to 0.7.2. From then i always copied the db to my new nxt-folder.


I didn't overclock mine. To what CPU-rate did you overclock it? Do you use some kind of cooling? My RPi is just in an ordinary plastic-case, no cooling at all...

Agreed. We might as well be the best in all areas.

Hi ErosLp, you can use the faucet at http://nxtra.org/faucet to get your first Nxt
or take a look at http://mynxt.org/#nxt
or use exchanges to buy some Nxt: http://mynxt.org/#exchanges

Jean-Luc?

NRS signs SHA256 of a message.

1 signature takes 100 times more CPU ticks than SHA256(32_random_bytes). Signing of a transaction that is 100 times longer ~ 2 ordinary signatures.

I prefer to trust a peer reviewed algo by Matt Green than any ad hoc mixing technique. We dont have to run faster than the bear, we just have to run faster than the slowest guy.

What I mean is that currently everything is totally open and correlatable. ANYTHING is better than that. That being said, we might as well go with the theoretically best solution and that in my opinion and many others is zerocoin's approach. Also, if it does get cracked, then it becomes the same as it is now.

All of the performance and storage issues are said to be solved with zerocoin2, which we will incorporate as soon as it is available to us. Hopefully in a prerelease. Validation times are ~10 milliseconds, size is 288 bytes

The trusted party is a onetime thing. My plan was to ask Anon to be videoed creating the initial dataset on a totally isolated computer. Then we copy the data onto portable storage put it in a faraday cage and detonate an EMP to erase everything on the computer that generated the initial data. Just dont tell Anon about this plan!

As far as issues with accumulators, that is part of the blackbox maths. I will have to defer to Matt Green to address such issues. We have a very talented community, if there comes a time that we need to take corrective action for issues like you are talking about I am confident that we will solve them

James

What do you mean exactly? Where will the confusion come from?

What does -856xmx do?

even if Nxt goes to $1000, 0.00001 would be 1 cent

Too many decimal points bring confusion.

I partly agree with you.

Still want to add something: we should be able to increase the precision step by step.

However, higher precision goes with lower fees possible.

If we lower the fees possible too fast, many forgers would certainly stop to forge. This would make the NXT network extremely insecure. We need time until the first services are build on top of NXT.

Thanks! I am reluctant about the overclocking, but I run it with -856xmx ...

well I guess now we have more time for discussion of number of decimal places and also more on fees.  Maybe we want to start with 4 decimal places and allow us options to 'split' in the future (something that hasnt been done in crypto before, they just go with eight and done) or we could just go 8 and done.

Im  still torn on using percentage-based fees on ordinary transfers, or for  my other suggestion for fees based on byte-size of each transaction.  if you do a %, then what about AM/alias?  Do we hard-set fees for aliases/AM? or just leave that for future debate, as fee-changing is apt to take a lot of work/testing anyways.

Sorry to disagree Eadeqa, we always seem at odds...
We need as much precision as possible. I am already seeing some issues with pricing things in AE. BCNext's vision is to run an entire economy on top of NXT. Assets are the key, that is why it is the only thing that costs more than minimum transaction, eg. 1000 NXT

We will need milliNXT and microNXT and maybe even nanoNXT so people can transact for things without quantization problems

James

P.S. I am trying to make sure that even after NXT goes above $1000 we can still buy a lollipop at a precise price.

Oh, yes. Therefore, compression is better for the first period until we need more.

Looking at their history they have done a lot of selling and probably would sell more if the price went back above a dime.

binary encoding and dynamic max TPS too

No, no. It does not. Just overclock it at medium level. Works like a charm for me.

And yes, you can re-use the db of 0.7.4.

In fact the nxt.log above shows the migration from 0.7.4 to 0.7.5.