Topic: NXT :: descendant of Bitcoin - Updated Information - page 555. (Read 2761624 times)

Voted

Guys, here needs help:

http://cryptocrimson.com/poll-which-alt-coin-will-see-the-most-growth-in-2014.html

Hey guys,

great work regarding the testnet. This is what I call a community!

Cheers.

Hi,

I'm pretty new in NXT but I'm looking it since a while.

I bought some of them 1 month ago (50k) in order to forge more.

What I notice after 1 month of forging is:
 - I have a chance to forge only once per week
 - I forged nothing

I did something wrong maybe ?

edit:
checking my node:
"you can generate the next block in 39 days".

:-/

Step 1: Finishing Asset Exchange
Step 2: Set up a deadline when it will be in production. Don't bring it online immediatly.
Step 3: Let the countdown begin at www.nxtcountdown.com
Step 4: Create Buzz / Make the video what I described above (We need a bounty) (It's important to tell how to create an account at the beginning)
Step 5: Spam everyone after finishing the marketing materials.
Step 6: Enjoy the fireworks.

I see no panic. I see an exchange owner communicating in an open manner with his users and trying to do the right thing.

Which is a rare thing these days... 

There was another exchange hacking incident today. Poor Poloniex seems to be involved in all these, but that is probably because it has all the hot coins. Last week a hacker withdrew a large amount of BTC from c-cex, bought ALL the DRK on the orderbook quadrupling the price to .007 and deposited it in Poloniex crashing the price of DRK by 90% to .0002!

https://bitcointalksearch.org/topic/c-cex-has-frozen-your-btc-not-to-be-trusted-485029


Today, a hacker exploited a weakness in Poloniex's withdraw system. It was actually the first time Poloniex was responsible for its involvement in an incident.

https://bitcointalksearch.org/topic/btc-stolen-from-poloniex-499580

For those concerned about how the gateway would have done, I do not have the balance checking in, but I am pretty sure I would have checked for positive balances. Also, I serialize ALL withdrawals from all customers. This actually could create a performance bottleneck, but I went the safer path. It is much safer to have just one withdrawal going at a time, especially if you have only one acct being withdrawn from.


In a separate incident, XCP protocol itself was hacked!

https://poloniex.com/correspondence.pdf

The fact that the hack used 2 of 3 multisig is kind of a spooky coincidence, but the vulnerability was due to how XCP credited and debited accounts, apparently hardcoding the withdrawal from the first input. Rest assured, that I validate each txout used as an input with the associated account. Plus what I am doing is MUCH simpler than what XCP is doing.

Now these events make me reiterate that before we go live with my gateway code, we must have it reviewed by an expert. I think it is in the community's interest to hire "Guy Fawkes" for this review!

Kudos to busoni who keeps weathering these attacks and does as good as anybody could expected to.

James

P.S. I have never been in Brazil!

The same problem




_______________________________________________________________________________ _________________________________
Next Coin Lite - Fair Distribution

I understand, but at the moment for connection problems can not Download version 0.8.4e.

And then I could not send the TestNxt, such as Jean-Luc wrote:

For me I see errors, which one of them starts with:

DEBUG: Invalid peer address: nxt3.boxedhosts.info java.net.UnknownHostException: nxt3.boxedhosts.info: Name or service not known
bla
bla
bla
bla

Hey... Poloniex just got hacked..... panic https://bitcointalksearch.org/topic/btc-stolen-from-poloniex-499580

Yes, see Jean-Luc's post :-)


I did read it, thanks, but some people missed it. The perils of not having a separate thread dedicated to testnet...


How can transactions broadcasted to testnet be replayed on the real blockchain? Isn't the point of testnet to work as an alternative blockchain? I'm probably missing something here.

@jean-luc
How do I send API calls to the 8.4e?
If you have curl syntax, I can take it from there

James

Edit: details https://bitcointalksearch.org/topic/m.5497889

Never crashed for me. What do you see in nxt.log when they crash?

Yes , at the moment i'm using the testclient on holms ...

I have always used this to send TestNxt. Now Are you connected with local 0.8.4e?

Holms.cloudapp.net is not on the current testnet blockchain (at least until somebody updates it).

Read the change log for 0.8.4e about how to join the testnet that I have seeded from bug.airdns.org. I have forged more blocks on it so now the test blockchain is growing.

It is safe to forge with real accounts on test net, provided you do it on localhost only. It is NOT SAFE to send any transactions with real accounts on test net, because those transactions can be replayed on the real blockchain. So for testing transactions, you need to use those test Nxt that were distributed some time ago (I don't have any of those myself yet).

Yes, I'm using local NRS and connected to bug.airdns.org. It finally updated successfully to latest blocks. But redsn0w uses holms.cloudapp.net, which doesn't work anymore.

I dont think that is the testnet anymore
You need to use the localhost after making the preference changes

https://holms.cloudapp.net:6875/ doesn't show any active peers btw.

The 5K you sent a while ago has not showed up yet.

858492554429534417 Pouncer