I didn't, it was more the posts where they said they didn't trust my motives that I had a reaction to.

CfB, I am looking up datz's profile next, I remember it on the API thread

Of course ripple isn't perfect, NXT isn't perfect, nothing is. If there are specific technical concerns, I can try to get an answer for it, I even have contacts within ripple labs. That does not make me a ripple controlled zombie.

I am not saying for everyone to use ripple. If you don't want to no need to. I just was really hurt by accusations by a couple of people against me for providing an alternative to dgex. Just because you don't like ripple, don't flame me. Fair enough?

James

P.S. I asked people to trade NXT/BTC, but the only real orderbook is NXT/XRP. What this means is that you need to look at the price of BTC/XRP which is around 31000 now, take reciprocal -> 0.000032258064516 per XRP, so 2 XRP is double that = ~.0000645, 3 XRP = ~.0000968
If you are not comfortable holding XRP, then as soon as you sell your NXT and have XRP you can simply send BTC directly to your bitcoin address using the Send page in ripple wallet. It will automatically covert XRP to bitcoin and make sure you confirm the exchange rate before sending. You will only have to taint your acct with XRP for a minute or two.

peercover -> ripple. Big trades can be handled

James

datz is the owner of peercover, the peercover main NXT address is 2269220637361284198

During development (before jan 3rd) peercover had too close encounter with darkNXT and 100000 is now darkNXT

I personally sent peercover the 100000 NXT to make sure all withdrawals would be covered since dgex at the time not responsive and no way to get real NXT transferred to peercover any other way. Sorry, nxtchg.com is not financed enough to be considered for large NXT exchange.

I spent full day during dgex created emergency so that NXT will have a place to trade. Remember it was not even working, simultaneously with src release. Strategically, it is unacceptable for there to be no way to trade NXT in large volumes. I sent XRP to fund people's accts and all of them returned back, showing the honesty of NXT'ers. People can and have traded NXT on ripple enabled by peercover. Peercover also has a direct trade page that allows for trading without using ripple wallet. Still need ripple acct.

However, for my efforts to create an alternative to dgex, I am accused of taking advantage of people somehow. dgex screws everyone and I am accused of bad faith? Covering 100000 NXT gives me super big advantage? I also was told to stop posting here, something I don't remember even yuriygeorge was told to do

As I reviewed the voting, I didn't find a single mention of the peercover solution, until CfB did.

WHY ARE PEOPLE AFRAID OF RIPPLE?

NXT and ripple have one feature in common, payment. Ripple will do a far better job in the gateway space especially for foreign currency conversion and to corporate payments processing (until TF). This is less than 10% of NXT feature set scheduled for April. For this you are still paying dgex horrible fees? For this you accuse my actions of hidden agenda?

I have been honest that I am working with peercover, we are working in ripple space together. peercover is one of most respected companies in ripple space, ask 2Kewl4Skewl. I convinced datz to add NXT support and to not charge any fees and use forging revenue model. I am to eventually receive share of forging revenues from deposited NXT. Considering that only ~200000 NXT has been deposited, I probably have to wait for several years to recoup my 100000 NXT.

If it weren't for the support of aldrin, klee and bidji29 and many others who PM'ed me I would have simply gone away and made all the ripple haters happy. Many people are afraid to voice their support for me publicly due to this anti-ripple sentiment.

Ripple will not kill NXT and NXT will not kill ripple. This means it makes sense to take the best from each and utilize ripple for NXT benefit and vice versa. If you want to keep paying dgex fees and trust him to not increase them at next critical moment and to redeem all your money, fine. If you don't want automatic deposit and withdrawal and distributed servers doing the exchange, fine. If you want to call me an idiot or disagree with my analysis, fine.

PLEASE just give me the respect that I feel I have earned and certainly more than the pre-pretty charts yuriygeorge!! PLEASE do not accuse me of being dishonest, that really hurts me.

James

P.S. Has anybody checked whether the stolen NXT is in darkNXT accts? If it is darkNXT, then we can believe the thief but then the problem becomes that we misanalyzed the entire episode. darkNXT is the biggest threat to NXT right now, it must be fixed in all ways. I feel this 100000 ways.

The trust amount needs to match the amount you want to deposit. Actually the amount that will be in your account after you deposit. You can peek around the order book, etc. without having any NXT deposited

James

The active orderbook on ripple is in NXT/XRP for now. Wow over 250,000 NXT active! The spread is bid 2.7, ask 2.8 XRP per NXT. Currently BTC is right around 30000 XRP, so 3 XRP = ~.0001 BTC

this makes the effective spread .00009 vs .00009333 BTC, actually not that bad considering this is the first day and people are just starting to get used to the whole ripple thing and a lot of people are still in the process of funding their ripple wallets.

Notice this is a significant premium over dgex so regardless of your feelings about ripple, you can get 15% more for your NXT on ripple. Unless you are millionaire and don't need extra 15%, it is usually worth a little extra effort to make that 15%.

All you need is a ripple wallet, which doesn't require registration or anything, just a handle and password. just go to ripple.com and create wallet from the wallet link in upper right corner.

Once you have a ripple acct, you will need 30 XRP to get going. This is ripple's answer to darkNXT, or in this case darkXRP. A account without minimum XRP can't be a destination for anything except XRP.  Send me your ripple address and I will send you 30XRP.

Now you can go to the simpleGateway (URL in my sig) and just follow directions for deposit, etc.

After you are all setup, you can send me 10 NXT or the 30 XRP or even .001 BTC, whatever is easiest.

James

The problem was caused by 4.7 crashing and so the automatic processing stopped. Updating to non-memory leak version and getting synced to the blockchain fixed things nicely

James

this is called darkNXT, we know it exists but it cannot interact with anything, short of cracking the password.

James

From hand optimized large number math operations to peer to peer synchronization with blacklist and hallmarking to hardcoded genesis block with founders acct #s and starting NXT, all included in 6800 lines.
No obvious bugs, feels like trying so solve a rubiks cube, but this cube is a sphere and a triangle at the same time. High level, low level and everything in between all interconnected. This will take a team of experts to fully understand and find the flaws. My guess is that it will be along the lines of allowing tainted data into a validated block by some mechanism like trusting a node that shouldn't be or some such thing.

James

frictionless,

Unfortunately (for us), the answers to your questions are indeed in the source code as released and the live version uses the identical or bug fixed version.

CfB is not the author, he was one of the founders who BCNext convinced to deal with the forum while he kept coding

Conceptual framework for the algorithm is in the original BCNext thread (https://bitcointalk.org/index.php?topic=303898.160), you just have to read through it or the source code or wait for the white paper

James

Frictionless

Did you even read the code?
The proof of stake is hard coded in with the founder's acct numbers and the number of NXT they started with. The genesis block is created from scratch and the blockchain starts from there.

By starting with 100% of the NXT issued to the founders in the hardcoded block, as long as every transfer of NXT is accounted for properly the proof of stake is maintained.

James

I have been looking at the source and ignoring the formatting style (everyone hates any formatting that is not their own) the code is quite clever.

In several places I thought I found an off by one error, or control flow problem, but so far the code is written to run efficiently and cleverly. Not much waste within the context of JAVA that will run on everything, which is quite a big requirement for something like NXT.

People complain about one it just being one file, but I myself do that until it gets to 10000 lines or so. It helps the compiler generate more optimized code, at least for C, if it is all in one file as linking is only to libraries. It is also much easier to make a release, just one file instead of many.

I am not familiar with all the JAVA built in classes, but there appears to be very little code for what NXT does and usage of the built in classes is part of the reason. I can see why jean-luc wanted to refactor the code. My impression is that this was written by a single person, not a team, but I have no basis for that other than a gut feel.

James

P.S. For those of you worried that the trolls will announce some sort of "source code is rotten" tirade with any merit, you can rest easy. Source code appears to be the work of a super-genius with a strange formatting style (indentation, spacing, eg. doesn't affect any actual code)

sendToAllPeers line 2833:
for (Peer peer : peers)
{
    if ( enableHallmarkProtection && peer.getWeight() < pushThreshold )
    {
        break;
    }
    if (peer.blacklistingTime == 0 && peer.state == Peer.STATE_CONNECTED && peer.announcedAddress.length() > 0)
    {
        peer.send(request);
    }   
}

I am not sure if code flaws include config and network configurations that are not handled properly. If so, the code will not send to any peers if hallmark protection is enabled and pushThreshold is set to be higher than the "heaviest" peer. I might have the sort direction wrong, in that case if all peers have weight of 0 and pushThreshold is set to 1, it will terminate without sending to any peer.

This might be by design, but having sendToAllPeers sending to nobody doesn't seem correct.

James

intel, the person with handle not company, had a theory that memory corruption in the JAVA could cause the destination acct to get corrupted. Another theory is that it could be a race condition of some sort that exposes an uninitialized variable, basically stuff that is outside the realm of what the client can do.

WE need to refuse to create darkNXT in the client and independently refuse to create it in the JAVA and ideally refuse to create it in the protocol. What purpose does darkNXT serve other than to piss people off because they lost small to large amounts of money. In alpha test, ok. In beta test, maybe ok but not really. After formal launch we can never create darkNXT, unless we are willing to reimburse, which does not seem likely.

Ripple does this better than NXT. Can we really allow that to stand?

Nexern, there is only so much you can do in the client.

James

P.S. Sorry CfB, we might even need a "allow darkNXT creation" API call. That is how difficult it needs to be. No laughing matter extinguishing peoples money.

Yes, not insignificant percentage of people are color blind. We need a specific dialog box in the red case, defaulted to NOT send.

James

P.S. What version should peercover run? 4.8 or 4.9, if 4.9 where is it?

This is why I addressed my request to jean-luc also. We need to PREVENT darkNXT for all except the most motivated API users. darkNXT has no real world benefit as far as I can think of, in fact it could attract NXT miners who will look at 64 bits and their petahash ASICS and start drooling when NXT gets to $1

James

please send me the acct number you sent the NXT to. Did you set a trustline big enough to handle the deposit amount?

James

CfB + jean-luc + nexern,

There are millions of darkNXT and more being created all the time. darkNXT is NXT sent to an address that doesn't belong to anybody. I am assuming this is something we don't want the end user to be able to do easily. Anyone with direct API access could do whatever they wanted, but end users should NOT be allowed to create darkNXT, especially when all it takes is a typo or memory corruption.

The solution to this is so simple I am at a loss as to why it has not been implemented. NXT sent to an acct without key will create darkNXT, there is a call to detect if an acct has a key. Why has this simple guard not been implemented?

This is a very serious flaw and even ripple has a solution to this by not allowing money to an unfunded acct. We can't let horrible flawed useless ripple be better than NXT in this area can we?

James

P.S. For those not in the real world, EVERYTIME and end user creates darkNXT, it will create at least a support incident at worst lawsuits against a vendor supporting NXT. Need I remind people that we need widespread NXT adoption.

I will have this investigated. Something seems wrong as the deposits are automated.

James