Is there a method to limit target from overflowing?
if you mean base target, it won't overflow. check is done inside calculateBaseTarget ...
long twofoldCurBaseTarget = curBaseTarget * 2;
if (twofoldCurBaseTarget < 0) {
twofoldCurBaseTarget = maxBaseTarget;
}
if (newBaseTarget > twofoldCurBaseTarget) {
newBaseTarget = twofoldCurBaseTarget;
}
if you mean hit target, computation is done using BigInteger, so that won't overflow. BigInteger target = BigInteger.valueOf(Block.getBaseTarget()).multiply(BigInteger.valueOf(account.getEffectiveBalance())).multiply(BigInteger.valueOf(elapsedTime));
BigInteger hit = ...
if (hit.compareTo(target) >= 0) {
added code fragments |
|
|
|
Does anybody know what percentage of hallmarked nodes have 1Mbps+
What about normal nodes?
James
I hope you're aware, that a) tx size currently is much bigger than 128 bytes... b) we're quite far from 1000TPS |
|
|
|
I can see that ages ago I sent a very small amount of BTC to the NXT address but can't remember what else I did. I've tried a bunch of my longest passwords but none have any balance... what might be my next steps to figure out how to recover any coins?
what do you mean by "sending BTC to NXT address"? and how did you do that? |
|
|
|
then give me time please a simple installer! I can not do not know how to make a bath file/java to me is too much! in nxt there is not even a simple one click installer.
I have many coins and such a crap as with nxt I have never experienced before. ok then I can not enter halt or next must be a simple installer get as it also dodge or any other altcoin has
that annoys me really!
There's light client for android, you could try that. https://play.google.com/store/apps/details?id=org.nextcoin.nxtclientPS If that's showstopper for you, why do you invest in NXT? o0 |
|
|
|
I suppose line 5873 if (peer.state == peer.STATE_DISCONNECTED) {should be if (peer.state == Peer.STATE_DISCONNECTED) {  1st one is ugly, but compiler will accept that |
|
|
|
Finally been able to buy my first NXT!  , it's only 2k but still awesome  What's your acct number? |
|
|
|
@CfB, @JeanLucPicard: Server part, should have some configuration option in web.xml, that would disallow communication with hosts running version lower than required i.e: <init-param>
<param-name>minimumVersion</param-name>
<param-value>0.5.11</param-value>
</init-param>
I still see hosts with 0.5.3, 0.5.5, 0.5.7, 0.5.8, sending or receiving data from <0.5.10 is waste of timeThis won't work when we have more implementations of the core. It could be combination of both core + version, so <init-param>
<param-name>minimumVersion</param-name>
<param-value>NRS 0.5.11; .NXT 0.0.5.0</param-value>
</init-param>
(second one is minusbalancer's dotNXT) if app is not specified default actiot would be to "accept" |
|
|
|
@CfB, @JeanLucPicard: Server part, should have some configuration option in web.xml, that would disallow communication with hosts running version lower than required i.e: <init-param>
<param-name>minimumVersion</param-name>
<param-value>0.5.11</param-value>
</init-param>
I still see hosts with 0.5.3, 0.5.5, 0.5.7, 0.5.8, sending or receiving data from <0.5.10 is waste of time |
|
|
|
Push. R U working on nxtion? someone here mentioned quite cool list of features. If nxtion would have them, I believe it could beat both nxtcoin and nxtcrypto forums  Oh, I've found it: There's a lot that could be done to help with communication. Instead of just a traditional forum (section -> thread -> post), there could additionally be support for the following, e.g. -instead of giant quote pyramids, there could be slashdot/reddit tree-style threads. -people like salsa, pin and joefox are making regular aggregator link posts, which is great. Even better if these could be stickied. Better still imo, if the most important links and their description could be displayed directly, instead of having to go into the stickied post to find them. Basically, the more important and/or the more people it involves, the more visible it should be. -more options to customize what you want to follow than just a watchlist. Maybe a reddit style way of assembling favourite subreddits. Maybe topic tags for threads and posts. - I've mentioned summary and definitions of technical terms before. Maybe a small, fixed frame/window for summary of the ongoing discussion (update permissions decided by topic starter say?) Mouseover technical terms/acronyms to get definitions (maybe these could be databased in our wiki? What do you think joe?) - maybe integration of real-time communication tools like gdocs or the old Google Wave, or at least a chatbox. - personally, I'd love LaTeX support so that I can write math using less English Lots of possibilities. But most importantly, the site admins and devs need to experiment with ideas like this and interfaces. Find out what works best for most folks. nxtcrypto, are you guys (or anyone else) up for this? I don't know web coding, so even though I suggest all this, I can't help with the implementation  I can do interface mockups though. And the LaTeX support part, if you guys are interested in adding that, I can help. Let me know. |
|
|
|
Could anybody here explain what could be done with a perfectly working asset exchange? Some concrete examples? I still dont get the idea
Selling games for example |
|
|
|
Neer.g has paid me for 5 vps for 3 months. Should expire by end of march. I was also provided 100k and have used that for another 7 vps.
I've started 1 new vps, from well known provider (~1btc for a year), I hope it won't run out of ram, before that. |
|
|
|
3. ‘normal’ client - for users, that want to participate in the network, but don’t want to deal with DB setup. This one would keep blockchain in memory, BUT it would rely on “snapshots”
a. snapshot would be created every X days (I was thinking about X=10)
b. they would contain information about state (of accounts), but would drop all the history
c. snapshots (for new clients) could be propagated in torrent-like fashion.
1.3 In principle I would agree, snapshots which get propagate are open for attacks and easy targets to fake snapshots not to repeat myself, read what's below and think about it, I think it would be possible to do that (and do that securely):
Do I understand this correctly that the blockchain would only be stored on the "server version" of the client and not by every client ? I'm not sure that's a good idea. I don't know how people would feel about that and also doesn't that make the whole thing less secure especially in the beginning where fewer servers are running ? Say 10 servers are runnin initially. What if i whip up 20 VMs on my computer and make them servers....could I then not controll the network ? Not to mention that if the client doesn't hold the blockchain mim attackes could to a crapload of damage especially if coordinated well.
What's the point of having outdated snapshots in the client ? So the update from the DBs won't take as long ?
Nope, you don't need whole chain for security purposes. Also 'normal' clients would also be part of the network. They just wouldn't store whole history, only those snapshots + blockchain history since last snapshot till present. Most people don't need whole history anyway (i.e. compare to btc, where download of whole the blockchain takes days if not weeks...) When you would receive initial snapshot, there would be additional step of verification, that the snapshot you've received is actually CORRECT one (there are number of ways this could be done), to make sure the peers from which you've received it are not EVIL ones. Sorry for uber long quote, but I've just noticed CfB in specific aspect has similar opinion to mine: It sounds like we can't go much past 100TPS, thats 100KB of bandwidth. If a node every falls behind, how will it catch up?
This sounds like a fundamental limitation if the total TPS is limited by the slowest node. Or maybe only a few nodes can keep up with the 1000TPS and there is a way for slower nodes to catch up somehow? If BCNext solved this, it will be total NXT domination.
Lightweight clients don't need full blockchain. That's why we need public nodes that will become Service Providers in the future. |
|
|
|
I got no idea what's going on with Nxt. I hear people talking [...] But, that's just what I hear, I got no real clue of what really is happening to this coin.
So you're not even running NRS, just being a gossip girl, did I get that correctly? |
|
|
|
Well, I would like to know how Nxt handles a fork. That's what I'm trying to understand here.
I don't see u trying. I don't see you with an explanation. I don't see how you are handling the current Nxt fork that is happening right now. WHAT FORK IS HAPPENING NOW? U MAD? fork that was mentioned in this thread happens to people using OLD version of NRS? Are you really that ignorant or do you just want to spread chaos and misinformation? |
|
|
|
So you are saying that it can maintain availability (which I agree) and survive partitioning ( which I don't think so).
What is in the algorithm for Nxt that makes it tolerant to partitioning?
U confuse partitioning of network with partitioning of data storage. Nxt has very high Availability coz all the data is stored in the blockchain. The blockchain can't be partitioned, that's why Partition tolerance issue doesn't arise at all. Partition tolerance is important for other data storage schemes, for example, DHT. Are you brain dead.... the block chain is a global ledger! In short, if you got a fork, you got an inconsistent ledger or in other words and inconsistend database. It will survive it... Ok, It actually won't survive partition, if some government decides to cut off "teh internetz" (i.e. think of Great Firewall of China) Then folks on behind that firewall will obviously end-up on a fork (but there's no coin that would solve that) |
|
|
|
So you are saying that it can maintain availability (which I agree) and survive partitioning ( which I don't think so).
What is in the algorithm for Nxt that makes it tolerant to partitioning?
You'll find the answer to that question in the source... (yes even the published flawed one) If you don't know the answer, then don't pretend the answer is somewhere else. I know the answer, I could give you line numbers inside this file: https://bitbucket.org/JeanLucPicard/nxt-public/src/4073c21098076d3469b3f74d49e73ffabe3a2001/Nxt.java?at=masterbut tell me, why would I possibly want to do that? |
|
|
|
So you are saying that it can maintain availability (which I agree) and survive partitioning ( which I don't think so).
What is in the algorithm for Nxt that makes it tolerant to partitioning?
You'll find the answer to that question in the source... (yes even the published flawed one) |
|
|
|
Ur model is way too simplified. This is better one (but also doesn't match reality): king/pawn in this sample gives 12, and that's also result of second float printed after both loops > foo.py
12
0.12333879483 12.2624434389
"doesn't match reality" I was referring to the fact, that in reality, the king might not be "fastest", and there's chance for pawns connected to large number of peers. P.S. but ofc, what you've written also matters, but CfB already replied to that. |
|
|
|
You actually made a useful post or two, thats progress! Then you went back to your old self...
You clearly have a lot of energy and now a lot of NXT, so why not work to make NXT increase in value? It will only help you add to your NXT that you have been "borrowing" from the poor newbies with weak password and your NEX suckers
Just BUILD on NXT and that would add value. You don't need to be a troll anymore now that you have so much NXT in your pockets.
yuriygeorge converted (where are his nice orderbook charts?) maybe you can too?
darkNXT is what I called the NXT that is in an account without any public password. Kind of like dark matter. Only 64 bit protection so you can easily crack the publicly accessible NXT. I think you said you can crack any such acct in a few hours instead of the years it is supposed to take so clearly you are the master cryptographer we need to bow down to.
James
What is this aboud darkNxt? Sounds interesting, what exactly happened and how much bounty is in those accounts? There's 100000 nxt (~ 7btc now) waiting on account 100000: http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=100000 |
|
|
|
|
Show Posts
