Topic: NXT :: descendant of Bitcoin - Updated Information - page 1050. (Read 2761644 times)

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??
 

welcome Back Sir 

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).

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.

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.

Why would someone need SHA256 in a script?

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

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!

While its possible for someone to secretly add something inside for his own selfish need BUT in this case, its Jean-Luc and CfB for crying out loud.. im sure they would not try to do anything that is bad for nxt, it would be in their best interest to do what is right. If they don't the whole eco would collapse over night. They are the lead devs, from what i know they are probably the only ones coding nxt for what it is today.
If you won't trust the only core developers, i don't know who else is there to trust in such situation.

I'm pretty damn sure they are pushing this update for one reason, that is to prevent exploitation of the said critical bug.
And to me, it sounds pretty serious when they are not saying the specifics of the actual bug, maybe they are hoping for majority to update and be on the 0.6.0 chain before such bug is exploited thus not providing such details.

To sum up: ITS SAFE TO UPDATE to 0.6.0 so please everyone upgrade as soon as possible before someone finds such exploit mentioned.
CRITICAL MANDATORY UPDATE
http://download.nxtcrypto.org/nxt-client-0.6.0.zip

I don't think a low-memory device like a RaspberryPi would need a full blockchain to forge.  It would only need just over 1440 blocks.  If it needs to consult blocks that it doesn't have because they're too far in the past, it can get them by querring the API of a public node -- or several public nodes.

It can keep a list of SHA256 hashes of the blocks it deletes to check that the ones it gets from a public node are correct.

Or am I missing something?

Upd: 0.6.0 template compatibility

Found in "Get Peers" of https://localhost:7875/admin.html



Perhaps should better control of peers.
It could even prevent connecting to very old versions.

Speaking of aliases, another way to "preserve" your account would be simply registering an alias. You have to send out a transaction anyways to get your public key, so if you're interested in making some "back-up" empty accounts, you just register an alias as you would have anyways. In the merchant example, the merchant simply just makes up an alias for the customer (maybe an ID #) on that account, and the account won't be erased during pruning.

In general fee, 0.1 is fine!

I just wanted to describe various fee in different functions.


which is what is new in web.xml from 0.6.0?

PS: API would be very useful to reload web.xml while running. besides being able to read the hallmark of oneself from admin.html.

The merchant one was just an example of one possible attack.  I wouldn't be surprised if there were many others.


Speaking of attack, I'm very disappointed in Emule.  I guess it's time to cancel my 0.00005 buy order and move it up.  

Ah.

I can give you a copy of my blocks.nxt and transactions.nxt.  You trust me?  

Might want to try deleting and re-downloading the blockchain on one node.

Here's a diff of web.xml:

I think we should seriously consider forcing this behavior so we can prune public keys of accounts with no balance and no aliases

I am guessing so too - although I think it would make things rather complicated (as you would have to keep a "count" of how many accounts have that balance and then "remove" that balance when that count goes to zero, etc.).

To my thinking a simple B+Tree keyed on "account id" is much easier to picture and to work with (even if it takes a lot more storage).

Guess a trade-off between simplicity and size will have to be made in order to come up with an "optimal" solution.

well thats why im in this mess now, due to the upgrade to 0.6.0


yesthe first thing I checked was the good ole manual "stare and compare" of the new/old web.xml All I noticed was the  removal of the blockchain.nrs blurb at the beginning I removed that but I must have missed something big.  ill do it again

eta: found it, was up at almost the top too.  change Nxt to nxt.Nxt under servlet

yesthe first thing I checked was the good ole manual "stare and compare"  All I noticed was the  removal of the blockchain.nrs blurb at the beginning.  I must have missed something big.