Topic: NXT :: descendant of Bitcoin - Updated Information - page 659. (Read 2761642 times)

Let me make a suggestion to keep this ball rolling.  We should ask the Cryptsy folks to document what was required to get NXT plugged into their system.  Then we should turn right around to allwelder or some of the other Chinese NXT members and see that this info from Cryptsy gets communicated to BTX38.com in China.  We need to be on both of these exchanges as soon as possible.  It is the only way we are going to get exposure to a new pool of capital to buy NXT and get our exchange volume back up.  

Expect some posts like


 

not exactly see you in maths
...

this I don't understand at all - what exactly was your algorithm for calculating weights?

That's why WE need to start spreading the Nxt even in cities, in schools and in every place.

there really isnt much point in this mechanism.  what you are describing is basically a rube goldberg contraption that produces the exact result of current NXT account/network forging

Received this from Bittrex, please don't bother signing up any more until we have clarification they can add Nxt.

"Sigh, we just hit a huge technical hurdle that is going to delay this;  I'm not sure we have an easy way around this without doing a lot of core engine restructuring which is super scary.  

I will keep you updated "

I've asked them for more specifics.

We are in war with Ethereum (for those who have not understood it yet).

We need them engaged!

That's why WE need to start spreading the Nxt even in cities, in schools and in every place.

People have been wondering about some of the figures that my simulator has come up with so far - but there is actually a much worse picture here than I have so far shown as my simulator has been using "log(balance)" rather than just "balance" as the "stake multiplier".

So get ready for something that approaches more closely how Nxt actually works as it does not use log(balance):

blocks = 1440
a: 10
b: 10
c: 10
d: 10
e: 10
f: 50
wins( a ) = 48
wins( b ) = 50
wins( c ) = 50
wins( d ) = 41
wins( e ) = 52
wins( f ) = 1199
best_streak( a ) = 2
best_streak( b ) = 2
best_streak( c ) = 2
best_streak( d ) = 2
best_streak( e ) = 2
best_streak( f ) = 49
best_combined_streak = 3

In particular pay attention to the figure for "f" in regards to both "wins" and its "best streak".

I think that how you choose the winner is irrelevant - it is only the probabilities that matter here.

That's not how the nxt forging algorithm works.
You are looking for the maximum of random number * balance to get the winner where you really should calculate the minimum of random number / balance and let the minimum win.

Version 0.3.4 of Nxs is how up on GitHub

All API / UI server requests are now done through POST (with a config option for GET for backwards compatibility with Nxt versions prior to 0.8 ).

Nxs now has a sidebar for navigation (similar to the nxtra.org NXT Wallet's) because the advanced Nxt features such as Messages, Aliases, Asset Exchange, etc. won't fit into the navigation bar at the top. Aliases have now been implemented and can be registered and updated on the Aliases page. If you choose "Nxt Account" as your type, the Nxt account number URI will automatically be wrapped with "acct:" and "@nxt" so the full URI is something like "acct:0000000000000000@nxt". This is an attempt to help push a standard for Nxt account number alias URIs in solidarity with wesley's NXT Wallet app. In the future, these account numbers will be able to be entered as the recipient in a transaction as well.

Also, aliases now show up in their registering and updating transactions on the Transactions page.

Along with the new side bar, the pages interface has been completely revamped to show only one page at a time instead of the old navigation system where you could toggle widgets on and off and display multiple widgets at a time. The initial version with toggling widgets made too much of an attempt to emulate Nxt's default NRS GUI instead of rethinking the interface altogether.

Rate of requests for new data is now adjustable in "assets/js/config.js" allowing Nxs to potentially run more smoothly on older computers. Repo available here along with installation instructions and the full change log can be found here. New screenshots can be found here.

mine doesnt fork, but every few hours my 0.8.1e forging NRS node just hangs on a block and stops receiving new blocks.  I upgraded to 0.8.2e, same thing.

I run public node on Android TV stick

Why my node on Panasonic microwave oven forges so little blocks? Should I upgrade it to Zanussi?

exact!

But it is very important to keep alive the interest of forging every day because we want two things;

every day we must keep network secure
every day we must keep maximum decentralized network

The idea is that all forgers repeatedly get small incentives for trying to forge. It is a pure psychological reason.

In the end, the fee distribution is the same.