NXT :: descendant of Bitcoin - Updated Information

[Come-from-Beyond]

Bitcoin with the current block size has an ability to process ~7 transactions per second.

What about NXT? Haven't see this info anywhere posted.

Current limit is 255 payments per minute.

[1714319168]

1714319168

[1714319168]

1714319168

[1714319168]

1714319168

[laowai80]

Current limit is 255 payments per minute.

Can this be raised in the future? Would this be easy to do?

[nelisky]

How does one safely detect orphans?

If I have the block at tip it will not have a 'nextblock', so checking 'nextblock' on that block's 'previousblock' will detect if it got orphaned, but what if the last two blocks get orphaned, i.e. a blockchain reorg? Is that even possible to happen in NXT?

If all orphaned blocks get stripped of 'nextblock' then I can safely walk back until I find one that has that property, but with 2 orphans in a row will the older one still point to the next?

[Come-from-Beyond]

Current limit is 255 payments per minute.

Can this be raised in the future? Would this be easy to do?

Yes. As easy as changing "255" to some other value.

[Come-from-Beyond]

How does one safely detect orphans?

If I have the block at tip it will not have a 'nextblock', so checking 'nextblock' on that block's 'previousblock' will detect if it got orphaned, but what if the last two blocks get orphaned, i.e. a blockchain reorg? Is that even possible to happen in NXT?

If all orphaned blocks get stripped of 'nextblock' then I can safely walk back until I find one that has that property, but with 2 orphans in a row will the older one still point to the next?

Yes, a blockchain reorg will produce orphans. To check if it's an orphaned block, simply compare "lastBlock" returned by "getState" and id of the checked block.

Yes, 2 orphans in a row will be "double-linked" via "previousBlock" and "nextBlock".

[Come-from-Beyond]

Without complicating the network in any noticeable way? What exactly would the peripheral effects of this be?

If u "just" change this value, ur block will be rejected by the others. If it's legit changes then blockchain will be growing faster, fees will be smaller, people will be happier.

[Come-from-Beyond]

Without complicating the network in any noticeable way? What exactly would the peripheral effects of this be?

If u "just" change this value, ur block will be rejected by the others. If it's legit changes then blockchain will be growing faster, fees will be smaller, people will be happier.

With blockchain pruning seems like we could have a very healthy, scalable, flexible network. Esp Vs. BTC.

It's not pruning. BCNext called this "shrinking". Is there any difference btw? I'm not a native English speaker.

[Come-from-Beyond]

Hmm, couldn't say without a white paper/ source code. I would assume its similar to pruning, but "shrinking" could be interpreted as a type of compression.

Actually it's supposed to be such a way:

1. Take all non-zero balances.
2. Generate a new genesis block.
3. Start a new blockchain.
4. Put old blockchain to somewhere for those who wish to check that new genesis block is legit.

[Come-from-Beyond]

Version 0.3.16 - https://dl.dropboxusercontent.com/u/67242472/nxt.zip

Enabled "allowedUserHosts"

Added "logPeerCommunication" in web.xml

Added http://localhost:7874/nxt?requestType=getPeer&peer=88.198.210.245 to get peer info

Added http://localhost:7874/nxt?requestType=getConstants to get peer state values with description

Disabled blacklisting (to test changes in peer picking mechanism)

Added peer weight visualization

PS: Guys, don't forget about the hallmark! Only a few peers added it.

[Come-from-Beyond]

Edit: I believe you posted earlier that this shrinking mechanism would be up to a POS vote. Is it automated or is someone expected to steward the blockchain?

I don't know details, sorry.

[xibeijan]

Version 0.3.16 - https://dl.dropboxusercontent.com/u/67242472/nxt.zip

Enabled "allowedUserHosts"

Added "logPeerCommunication" in web.xml

Added http://localhost:7874/nxt?requestType=getPeer&peer=88.198.210.245 to get peer info

Added http://localhost:7874/nxt?requestType=getConstants to get peer state values with description

Disabled blacklisting (to test changes in peer picking mechanism)

Added peer weight visualization

PS: Guys, don't forget about the hallmark! Only a few peers added it.

What is the hallmark?

How's colored coins debugging coming along?

[Come-from-Beyond]

What is the hallmark?

Version 0.3.15 - https://dl.dropboxusercontent.com/u/67242472/nxt.zip

Some major changes, so read it carefully.


The list of well-known peers is not hardcoded in 0.3.15. Look at "wellKnownPeers" in nxt/webapps/root/WEB-INF/web.xml. Feel free to change it.


Added "myHallmark" in web.xml. If u r an owner of non-trivial amounts in NXT u should run ur own node(s) accessible on the Internet to protect the network. Hallmark is used to mark such nodes. More on this below:

1. Launch ur node.

2. Do http://88.198.210.245:7874/nxt?requestType=getMyInfo request to any other node to get ur host value. The request must be sent from the host that runs Nxt soft. U can bypass this step if u already know ur host.

3. Do such a request: http://localhost:7874/nxt?requestType=markHost&secretPhrase=MY_SECRET&host=MY_HOST&weight=HOST_WEIGHT&date=CURRENT_DATE

MY_SECRET should be replaced with the secret phrase of ur account (more coins it has - better it is)
MY_HOST - ur host
HOST_WEIGHT - "weight" of the host, u can have a lot of hosts marked with the same account, weight defines what part of the balance will be used (weight/Sum_of_all_weights). If u have only 1 node then it will use 100% of the balance
CURRENT_DATE - a date in "yyyy-mm-dd" notation. Use the same date for all ur nodes. If u use other date then all hallmarks set in the past will be invalidated.

An example:
http://localhost:7874/nxt?requestType=markHost&secretPhrase=123&host=88.198.210.245&weight=1000&date=2013-12-07

4. Copy hallmark value into "myHallmark" in web.xml.

U can decode ur hallmark by doing such a request: http://localhost:7874/nxt?requestType=decodeHallmark&hallmark=HEX_STRING. The hallmark does NOT contain ur private key (only public one and signature).

NB: U should update to 0.3.15 within next 2 days!

How's colored coins debugging coming along?

No idea, BCNext works on that.

[DiCE1904]

when I'm putting in my hallmark code do i need to have {"hallmark":"  in from the code?

[Jean-Luc]

when I'm putting in my hallmark code do i need to have {"hallmark":"  in from the code?

No, just the very long string of characters after that. Without the quotes.

[DiCE1904]

when I'm putting in my hallmark code do i need to have {"hallmark":"  in from the code?

No, just the very long string of characters after that. Without the quotes.

Done, thanks. I see my IP shows, how do I get my dns to be the one thats showing instead of my IP?

Can you explain the weighted thing more? Should I transfer more of my coins to my dedicated VPS for whatever the weighted reason might be?

[Jean-Luc]

Version 0.3.16 - https://dl.dropboxusercontent.com/u/67242472/nxt.zip

Enabled "allowedUserHosts"

Added "logPeerCommunication" in web.xml

Added http://localhost:7874/nxt?requestType=getPeer&peer=88.198.210.245 to get peer info

Added http://localhost:7874/nxt?requestType=getConstants to get peer state values with description

Disabled blacklisting (to test changes in peer picking mechanism)

Added peer weight visualization

PS: Guys, don't forget about the hallmark! Only a few peers added it.

I had to clear the browser cache to get to see the peer weights. Indeed too few have added it.

Clearing the peers.nxt file may also be a good idea at this release, to remove the blacklisted.

The disappearing balance bug is unfortunately still present.

[gnuberg]

What is the tietoiseen and why the http://nextcoin.org waiting for secure connection on the 80th port with self-singned cert from by tietoiseen 

[Jean-Luc]

Done, thanks. I see my IP shows, how do I get my dns to be the one thats showing instead of my IP?

I just put the hostname there instead of the IP. Both under myAddress in the web.xml file, and also when generating the hallmark.

Can you explain the weighted thing more? Should I transfer more of my coins to my dedicated VPS for whatever the weighted reason might be?

Not sure what you mean transfer the coins. You never need to unlock your account at the VPS. If you have several accounts, and only one public IP (the VPS), use the account with the highest balance when generating the hallmark. I don't know if CfB provided a way to combine the balance of several accounts to vouch for one node, probably not.

[gnuberg]

What is the tietoiseen and why the http://nextcoin.org waiting for secure connection on the 80th port with self-singned cert from by tietoiseen  

Now all looks fine. I don't know what it was that...

But still on 443 port I see self-singned cert from by tietoiseen. Is it normal?

[DiCE1904]

Done, thanks. I see my IP shows, how do I get my dns to be the one thats showing instead of my IP?

I just put the hostname there instead of the IP. Both under myAddress in the web.xml file, and also when generating the hallmark.

Can you explain the weighted thing more? Should I transfer more of my coins to my dedicated VPS for whatever the weighted reason might be?

Not sure what you mean transfer the coins. You never need to unlock your account at the VPS. If you have several accounts, and only one public IP (the VPS), use the account with the highest balance when generating the hallmark. I don't know if CfB provided a way to combine the balance of several accounts to vouch for one node, probably not.

great I see the dns now on the active peers. Thank You