EDIT - Please ignore, figured it out I was missing some dependencies after the fresh install. Anyone who may read this please run this command to fix -

EDIT 2 - added libevent-dev libncurses5-dev to cmd above, was getting missing libevent error.

Trying to upgrade to the latest version but getting a lot of errors. After cloning the git and running ./autogen.sh I get the following output -


After editing configure.ac and adding AC_PROG_CXX to it below AC_INIT I get the same errors, and right above it I get the following errors -


I just upgraded my PI 2 to Jessie, 5/10 and did a apt-get update/upgrade before trying to install so the pi is fully up to date. Hopefully one of you wizards can help me as my linux is rusty

I

Perhaps someone can clue me into the controversy.

After reading all 18 pages (phew), what I have concluded so far is:

1) CoinWallet.eu is attempting to avoid legal ramifications of the 'stress test' by allowing users to claim btc from priv keys with thousands of unspent addresses
2) People are up in arms over this as its possibly limiting the function of the network
3) No proof has been provided that it actually IS limiting the network
4) Proof has been provided by several users that normal transactions are going through fine without delayed confirmations
5) Proof has been provided by several users that the 'spam' coinwallet.eu tx's are getting backlogged and creating a large UTXO (approx 100-160mb at time of writing)
6) This has not effected nodes ....yet

I see others have mentioned bc.i blocking the spam outputs, but....can anyone confirm that the other block explorers are more accurate outside of blocking these spam tx's ? If bc.i is doing a good job of filtering *just* the spam tx's, then their current active count of 9k unconfirmed tx's seems right in line with the normal transactional volume.

I am running a raspberry pi 2 which is currently at 30%cpu 20% mem avg reported by top. This is definitely a higher load than normal, but surprisingly this little buddy is handling it just fine.

I understand actions that could potentially put unbearable load on the network would be seen as negative, but frankly if the network cannot handle one single companies attack vector, then how could we possibly fight off a determined actor who wishes nothing but negative harm to the network? And more importantly, how can we progress forward to harden the network without staging exactly these types of 'attacks' so that we can test against them, determine the health and robustness of the network, and use that data to make cohesive decisions on how to move forward in anticipation of future 'attacks' ?

Send me a PM!

Looking to purchase myself a Casascius orig loaded coin, series 1 or 2 MS65. Only from someone with high rep of course!

Thank you very much.

If GenTarkin or anyone else could provide input, I would appreciate it.

I have a two titans that were working solid, one was 330 the other 320, 1 die dead on one 2 dies dead on the 2nd. After shipment, there are 4 dead die's, 1 half working die @ 200mhz, and 2-3 dies that work when reset, but slowly gain in amperage from standard area around 38-42 (300-325) all the way up to around 52(and over 100C) when they cutoff and everything goes 0.00. I am unsure how this occurred as everything was working fine prior to shipping. I thought at first it was the diff brand PSU's being used, but they are excellent brand/models and should not be causing any issues.

Is the die's slowly gaining amperage a possibility of heatsinks getting knocked loose in shipping, or do you suspect something else?

I will be able to test your fw on the units tomorrow and provide results. In the mean time I would like to brainstorm possibilities for resolutions.

Ahh, that makes sense. Thanks for the confirmation, looks like I wont be able to remote upgrade this.

If I wanted to update my pi to your firmware without win32diskimager flashing the full image, what would be my commands?

git pull
./update-webgui.sh

thats it? How do I specify your git repository? Im a little confused as TXSteve added that 'didnt need this line on all rigs' comment so not sure if I need that git stash line or not.

I need to upgrade a remote box to test with this fw but dont have physical access. Im assuming this will work?

Oops, I accidentally stated root.root in OP, but it was really supposed to be pi:pi

All files are owned by pi.

BTW I think I have it fixed thanks to:

https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=48958

Which covers permissions and ownership very thoroughly.

Now im retransferring the BC and will hopefully have this resolved.

http://pastebin.com/NUQS91sx

Added a few other dirs output incase needed.

Im trying to get a node going on a raspberry pi 2 and synced the blockchain on my windows box after getting fedup with the pi taking weeks to sync.

I used paragon ext2fs to copy the blocks and chainstate directories to my /home/pi/.bitcoin dir on my SD card.

Upon running bitcoind I get the following output:

http://pastebin.com/6m0UXiJF

At first it couldnt open LevelDB saying permission denied and i noticed that the dir's were owned by root.root. So I did 'sudo chown pi:pi -R *' while in the .bitcoin dir and got the LevelDB permission error gone, but now its doing the same thing just later saying "Error opening block database." and wont allow me to rebuild if I do bitcoind -reindex

Could someone please let me know what I can do to correct the situation and get this running?

thanks!

I have a titan that I used for about 2 months when I got it, and then it became no longer economical. Now that the prices have jumped, I thought perhaps there might be some interested parties in buying one from me. I live in California and its hot enough in the summer time without these things running, I dont need my house burning down.

The unit runs great, I was averaging 300+ MH/S consistently on ghash. No lemons. Most recent difficulty checked at market price shows about $1500 per month in revenue.

PM or respond, thanks!

FYI, I heard back from both.

Magnus Darr seems like he just wants to profit off the situation and rip off everyone thats already been ripped off by KNC. He wanted $1500 USD for the group lawsuit and $5,000 USD for a individual suit with 200 per hour for junior and 400 per hour for a senior representative for when they go to court.

RAPE.

Joakim Strignert only wanted $1500 and 250 per hour for individual representation.

I will not be feeding some greedy lawyer money for no reason, so I will be going with Joakim. He responded to me within 24 hours of submitting information on the contact form listed 2 posts up from me.

Going through that massive thread I did find one lawyer, which lead me to another. Both of their names/contact is here for anyone who in the future is searching and comes across this thread:

http://kncnews.org/legal

Joakim Strignert
his contact page (in sweedish, but fill in the blanks and put your question in and im sure he will contact you)
http://dinratt.se/#kontakt

The guy doing the group lawsuit against KNC seems like he might just be trying to profit off the situation. He wants $1500 to join the group lawsuit and does not seem to be providing much in terms of support.

magnus.daar at nova.se

is his email.

Im contacting Joakim and will move forward.

Thanks for the response, it helped me find what I needed!

Does anyone have any advice, or legal referrals/references to a legal representative in the EU? I have received a broken Titan, had it RMA'd, received back another malfunctioning titan, and am getting played with for months now by keith at KNC. I am over trying to get them to honor their business agreement to provide me functional equipment....I have requested a RMA over a dozen times and gone through their troubleshooting again and again with no resolution, and no resolution offered by KNC.

I wish to sue them for the cost of the titan.