Topic: BTCD is no more - page 83. (Read 1328507 times)

Quote from: Cassius on Today at 12:10:10 am

    Folks - just had a long chat with James on Slack. Given the mud that's been slung around here the past few days, he doesn't want to make a personal appearance right now but wanted to clear up a few things:

    Backwards compatibility is obviously a huge issue for maintaining working software. There's a lot of understandable upset around that whole situation still, but the bottom line is that without it, some functionality will end up moving to BTCD. James will be working on that now. Bc on Nxt may or may not be a resolvable issue - that's very uncertain at the moment. That is a dialogue that needs to continue within the community.

    As has always been the case, Nxt will remain the financial platform for SuperNET, so all the jl777 assets will continue to be hosted on Nxt.

.

Define 'abandon' in this context please.

Anyway, the first effect of all this is that ALL of my projects will be delayed. I will wait for NXT API to stabilize before I waste my time. The most likely scenario is that I will just remove all dependency on NXT and put whatever functions I need into BTCD.
 

nope - jl777 is not threatening to 'abandon' NXT, and he never has.
what he is doing is implementing some NXT functionality that SuperNET uses into SuperNET/BTCD.

it is a long story and much hyperbole, so please don't jump to hysterical conclusions.

What happens is that SuperNET/BTCD tech gets more streamlined.

There was no discussion with the SuperNET team about the 1.6.2 breaking all the installed base. The only "discussion" happened after I complained about it not being backward compatible. And this "discussion" was basically a confirmation that the promise of backward compatibility that was made last year is not being honored.

There have been many customer support issues due to the breaking of the API and a lot of unreported cases where the customers just stop using SuperNET (and NXT)

I have been assured that with each NXT release that there will likely NOT be any backward compatibility of the API, which means anything that uses it will likely break and need unknown amounts of testing, requalification and of course customer support and field update issues.

It is not possible to deploy a large scale system using a "platform" that isnt backward compatible due to the breaking of all the ALREADY installed and running systems. With decentralized systems it is not possible for centrally force an update on users. Just look at some of the versions NXT peers are still running. Therefore anything that is guaranteed to break is certainly not worth spending marketing dollars to acquire the installed base for.

The NXT devs lack a fundamental understanding about business reality and I am extremely disappointed in the breaking of the promise to keep things backward compatible. The ONLY exception is if there is an attack vector. Local node performance is not any excuse.

Due to this, I am rethinking my reliance on NXT for SuperNET. I have quite a lot of code that takes all my time to create and to be assured that I will have to keep reworking it forever due to backward compatibility breaking with each release. This is not practical for me.

So, NXT will have a more efficient API with much fewer users. That is the effect of this breaking of the backward compatibility promise.

Anyway, the first effect of all this is that ALL of my projects will be delayed. I will wait for NXT API to stabilize before I waste my time. The most likely scenario is that I will just remove all dependency on NXT and put whatever functions I need into BTCD.

James

tl:dr it is a MAJOR breach of trust as far as I am concerned that the API backward compatibility promise has been violated and I cannot rely on NXT for any important SuperNET functions.

Pro tip for jl777: port your project(s) to ETH.  ETH is a general purpose distributed computer that makes obsolete scripted environments such as NXT look like "pocket calculators" (quoting Nick Szabo).

Sure, jl777 is fuming because the latest NXT update broke his SuperNET and he's threatening to abandon NXT. You can find out more here:

https://nxtforum.org/nrs-releases/nrs-v1-6-2/

so the best advice is to sit tight and expect they won't f.... us with sand paper

Sure, jl777 is fuming because the latest NXT update broke his SuperNET and he's threatening to abandon NXT. You can find out more here:

https://nxtforum.org/nrs-releases/nrs-v1-6-2/

can someone explain why there such a drop

if that it  then just follow me on all the coin and when I get on the coin cell everything
otherwise you will lose your money like me Lollll

Lol,
came true my prediction  earlier than expected.

All money of SuperNET community has gone to the NXT side, because they think this is the last dump of LSUM, but I think NXT come down to 0.00001xxx, in end of 2015 or the beginning of 2016.
time will tell.

As others suggested here before, You send the whole amount to yourself.
I have tried it with some coins including BTCD and it worked.
two years ago, I tried it with another coin and it didn't work. The amount never confirmed.

Another option is if you have two computers with BTCD wallet, send the amount from one wallet to the other and then back to the first.

I am not sure about the orphans. I think you write repairwallet in your wallet console (Help / Debug window / Console)

You don't. They're a valuable indicator. A few orphans per day are normal but if you get lots of them then something is wrong.

how do you remove orphans from the transaction list

Hi guys

Time for 2 dumb questions

I'm running v1.0.0.0-g32a928e of the wallet on Windows 7.  Can anyone tell me how to combine unspent outputs, I have some that have 20 different small amounts in the one address. I would like to be able to have a

total amount for each address.

The other one is how do you remove orphans from the transaction list

Anyhow thanks in advance and cheers to all.

Jon