[ANN] Nxt :: descendant of Bitcoin

[cunicula]

I will be quite suprised if this turns out to be a scam. But our innovator is clearly a bit of an oddball.

[Come-from-Beyond]

I will be quite suprised if this turns out to be a scam. But our innovator is clearly a bit of an oddball.

It's hard to scam in proposed scheme. He promised to launch Nxt. All main features r completed and Nxt can be launched even today. I can do it by myself after I figure out how to create Genesis block. Disassembled code is quite ugly but readable. This coin is the most innovative among all other coins I supported, so if bcnext is hit by bus I will launch it.

Btw autists are the best innovators

[cunicula]

I will be quite suprised if this turns out to be a scam. But our innovator is clearly a bit of an oddball.

It's hard to scam in proposed scheme. He promised to launch Nxt. All main features r completed and Nxt can be launched even today. I can do it by myself after I figure out how to create Genesis block. Disassembled code is quite ugly but readable. This coin is the most innovative among all other coins I supported, so if bcnext is hit by bus I will launch it.

Good to hear. Anyway I like oddballs.

[Come-from-Beyond]

Good to hear.

That's funny. I spent a few hours trying to get how to create Genesis block. I assumed that, like Bitcoin, Nxt doesn't contain code for Genesis block generation, so I was digging thru the code backwards starting from block validation upon its receipt... And found the code that creates the very 1st block!
Next time I will start from the very beginning and will move forwards.

[neer.g]

Did you hear anything from BCnext or his crew?

[haightst]

Well surely that is for you to determine the right use-cases and worst-case scenarios to test for, not for me to tell you, your code works different to eMunie, so different test cases are needed.

Simply, you want to test it to destruction!!  You want to MAKE it break, WAAAAAAY above any load that it will ever receive, then you fix that weak spot and test it to destruction again...keep doing that until either it doesn't break, OR the breaking point is so far outside of normal use it's irrelevant.

For example, for one entire week with eMunie, we generated 70k transactions per day, on a 10 node network....it took it all, just about.  This was after many iterations of the same test, pushing the failure point out further and further.

That will NEVER happen in real world scenarios where 10 machines are creating 70k transactions per day even at VISA scale levels (I know you don't like VISA scale references but you gotta think about it).

Other things, connectivity issues you cant control, so, pull the plug at a crucial moment and make sure that it continues with no errors, any DB's you use kill the drive halfway through a write and make sure it recovers etc etc

You're a software engineer right?  You should know this stuff!

you need me to break(test) something?LOLL 

[Fuserleer]

Well surely that is for you to determine the right use-cases and worst-case scenarios to test for, not for me to tell you, your code works different to eMunie, so different test cases are needed.

Simply, you want to test it to destruction!!  You want to MAKE it break, WAAAAAAY above any load that it will ever receive, then you fix that weak spot and test it to destruction again...keep doing that until either it doesn't break, OR the breaking point is so far outside of normal use it's irrelevant.

For example, for one entire week with eMunie, we generated 70k transactions per day, on a 10 node network....it took it all, just about.  This was after many iterations of the same test, pushing the failure point out further and further.

That will NEVER happen in real world scenarios where 10 machines are creating 70k transactions per day even at VISA scale levels (I know you don't like VISA scale references but you gotta think about it).

Other things, connectivity issues you cant control, so, pull the plug at a crucial moment and make sure that it continues with no errors, any DB's you use kill the drive halfway through a write and make sure it recovers etc etc

You're a software engineer right?  You should know this stuff!

you need me to break(test) something?LOLL 

Lol you can have a go, it's been through the mill already, join the forum and put your name in the beta tester waiting list (we add more about twice a week), lets see what damage you can do

[Come-from-Beyond]

Did you hear anything from BCnext or his crew?

Yes, he stopped using his 2nd BitcoinTalk account but I still get requests how to develop the client. I'm sure he is reading this thread using his main account. He could be anyone, even neer.g.

[neer.g]

even neer.g.

I'm flattered

[haightst]

Well surely that is for you to determine the right use-cases and worst-case scenarios to test for, not for me to tell you, your code works different to eMunie, so different test cases are needed.

Simply, you want to test it to destruction!!  You want to MAKE it break, WAAAAAAY above any load that it will ever receive, then you fix that weak spot and test it to destruction again...keep doing that until either it doesn't break, OR the breaking point is so far outside of normal use it's irrelevant.

For example, for one entire week with eMunie, we generated 70k transactions per day, on a 10 node network....it took it all, just about.  This was after many iterations of the same test, pushing the failure point out further and further.

That will NEVER happen in real world scenarios where 10 machines are creating 70k transactions per day even at VISA scale levels (I know you don't like VISA scale references but you gotta think about it).

Other things, connectivity issues you cant control, so, pull the plug at a crucial moment and make sure that it continues with no errors, any DB's you use kill the drive halfway through a write and make sure it recovers etc etc

You're a software engineer right?  You should know this stuff!

you need me to break(test) something?LOLL  

Lol you can have a go, it's been through the mill already, join the forum and put your name in the beta tester waiting list (we add more about twice a week), lets see what damage you can do

how much money and time have you put into this? LMAO
~ i can crush it if you really want me to!!!!  

[Fuserleer]

a year of time and $80k so far on just development

You are welcome to join up, I want to find any weaknesses whatsoever, otherwise whats the point?

[Come-from-Beyond]

I updated my server (http://88.198.210.245:7875/) to show BCNext the stock exchange interface. U can take a look and post ur suggestions/improvements. Tomorrow the development will be continued.
Click "Apple" icon in the bottom to open the exchange. If u log with "1" secret phrase u can see an asset issued by this account.

[Aggrophobia]

so bcnext is gone? :/

[Come-from-Beyond]

so bcnext is gone? :/

No, he just stopped to use BCNext BitcoinTalk account.

[bahamapascal]

I updated my server (http://88.198.210.245:7875/) to show BCNext the stock exchange interface. U can take a look and post ur suggestions/improvements. Tomorrow the development will be continued.
Click "Apple" icon in the bottom to open the exchange. If u log with "1" secret phrase u can see an asset issued by this account.

Soo, that means you are BCNext? Or you are just part of his team?

[Come-from-Beyond]

Soo, that means you are BCNext? Or you are just part of his team?

I wouldn't say I'm in his team. One of my employe is developing Nxt client. But I do have some BTC "invested" into NXT.

[Kyune]

so bcnext is gone? :/

No, he just stopped to use BCNext BitcoinTalk account.

Why?

[Come-from-Beyond]

so bcnext is gone? :/

No, he just stopped to use BCNext BitcoinTalk account.

Why?

I think the main cause was that someone got his IP he logged to this forum with. He used Tor but it's known that traffic analysis lets to reveal the real IP. So surfing BitcoinTalk as a guest or as another user is the only secure way.

Below I quoted a post that explains the situation a little.

Important

15 minutes ago I had a talk with a man (or a woman) who said he is a police officer. We were chatting via Skype, he asked me to make him a phone call because he has important information for me. I refused to do so and closed Skype.
Some things to think about:
- I always use Tor surfing the Internet.
- How is it possible to get my Skype number which was created for Nxt project? It was known by 3 people only who are working on Nxt project.
- The phone number was +194... It's the USA and it's a night in there right now. Was it a joke?
- I have checked the computer, no malware found.

I will reinstall OS on my computer and will disapear for a couple of days until I find other ways to surf anonymously but without Tor.

PS: This message was posted by a member of my team.

I posted this message using his BitcoinTalk account. This also adds some headache to CIA/FBI, coz now they are not sure if BCNext wasn't me actually. So they have to spend a lot of resources to figure this out, coz I live in a country that is out of the USA reach.

[milly6]

so you randomly send BTC to someone to get a stack of a coin that probably wont even exist? Am I missing something?

[Come-from-Beyond]

so you randomly send BTC to someone to get a stack of a coin that probably wont even exist? Am I missing something?

U are missing:
1. Nxt core is ready, it can be launched even today.
2. If BCNext doesn't launch Nxt then I'll do it following the plan.
3. BCNext keeps working on advanced features.