litecoin - Compiling litecoind on Ubuntu 15.04 - Bitcoin ...

Correcting r/bitcoin's misinformation: I just fully verified the entire ethereum blockchain on a 2+ years old desktop and it only took 25 hours (full log included)

In a recent bitcoin's thread thieflar claims that with 'a very nice machine' he was unable to finish validation of the ethereum blockchain and that the near impossibility of it is apparently an accepted fact even among ethereum's developers:
The developers of Ethereum know that this is an issue, they are fully aware that their network relies on trust at this point, and they don't even try to deny it.
nullc comments with:
without being able to count on nodes verifying the history even ethereum seems unable to make a proposal complex enough to hide its insecurity.
I tested the truth of these statements - the result: full block-per-block syncing completed in 25 hours 25 minutes.
Software: Parity at commit 2586eaef929cadcd5ebccdf2d484f1cf6bb14917, compiled with "target-cpu=native", performance options: --tracing off --cache-size 4096 Ubuntu 16.04
Hardware: i7-6700K, 16GB ram, Samsung 850 EVO 256GB. Not bad but definitely not 'very nice' either.
To remove the network speed from the performance equation I downloaded the bare blockchain separately and synced the node from disk. As it's only 20GB at the moment there would be no noticeable difference. 23k most recent blocks were downloaded after that.
The fully synced node with all historical blocks + recent state (ie. exactly like a full bitcoin node) uses 44.3GB.
Parity log.
Syncing from disk: 2017-12-30 20:15:50 Import completed in 87903 seconds, 4803128 blocks, 54 blk/s, 112578528 transactions, 1280 tx/s, 5273835 Mgas, 59 Mgas/s
Downloading the tip: 2017-12-30 20:33:53 Syncing #4803139 d21c…7352 0 blk/s 115 tx/s 5 Mgas/s 0+ 19 Qed #4803162 5/25 peers 365 KiB chain 72 MiB db 2 MiB queue 898 KiB sync RPC: 0 conn, 0 req/s, 0 µs ... 2017-12-30 21:33:43 Syncing #4825928 b3cb…6ec9 4 blk/s 720 tx/s 29 Mgas/s 0+ 15 Qed #4825945 7/25 peers 305 MiB chain 609 MiB db 3 MiB queue 3 MiB sync RPC: 0 conn, 0 req/s, 0 µs
Conclusion: any pc that can run a modern game can easily fully sync (no state snapshot downloading, only blocks) and run a full ethereum node.
edit: apparently reddit immediately deletes posts with links to mega
submitted by nootropicat to ethereum [link] [comments]

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B

Intro

This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
 
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
 
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
 
The updates
 
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
     

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

https://www.youtube.com/watch?v=Snr5e8bzftI
This video shows how long it takes to start Reddcoin Core.   TL;DR:
     

Extra

Backup
Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
 
 
   
Boot with only 1 USB drive plugged in:
Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly.   If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
   
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
   
Start Reddcoin Core easier
Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
   
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
   
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
 
   
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
   
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  
     

Credits:

   
Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

IRC Log from Ravencoin Open Developer Meeting - Aug 10, 2018

[16:01] <@Wolfsokta> Todays topics: DGW implementation, segfault, Q&A, feedback on IRC
[16:01] <@Wolfsokta> Just to set the stage here, this is a developer meeting where developers that have contributed source code to the Ravencoin project can meet and chat about items they are working on. Please be respectful to one another. For the sake of staying on target, please limit interactions to questions and comments on code or projects that you are working on. Any time left over at the end can be opened up for general Q&A.
[16:02] <@Wolfsokta> FYI - I'm RavencoinDev, and lets get started.
[16:03] <@Wolfsokta> @Tron, can you talk about where we are at with DGW on testnet and mainnet?
[16:03] <@Tron> Sure.
[16:03] can someone volunteer to take notes and post also?
[16:03] <@Tron> We are building binaries that will activate DGW-180 at block 338778
[16:04] <@Tron> It looks back 180 blocks to calculate the diff.
[16:04] I will copy the text from the meeting into a file that can be archived later. I can also make summary notes after like BTC core does.
[16:04] I'll save a log of the whole meeting and can post it on the subreddit thread.
[16:04] <@Wolfsokta> We have setup testnet4 in order to test the new binaries.
[16:04] great
[16:05] <@Wolfsokta> We plan to release the binaries later today.
[16:05] @Tron have you looked into the timestamp attack concerns of DGW?
[16:05] https://github.com/zawy12/difficulty-algorithms/issues/30
[16:06] <@Tron> Yes. And for that reason, we've tightened up the timestamps that will be accepted for valid blocks.
[16:06] <@Tron> Moved from 2h to 12 minutes.
[16:06] nice
[16:06] Oh wow okay
[16:06] <@Tron> Its also the reason we went from 60 blocks (lookback) to 180 blocks.
[16:07] why would 2h ever be acceptable? lol
[16:07] 2h was originally used for daylight savings shenanigans I believe
[16:07] <@Tron> It was from bitcoin, and it factors in clock skew, and variance in finding blocks on 10 minute intervals, and block propagation time.
[16:07] makes sense
[16:08] what about the segmentation fault when reindexing?
[16:08] any fix yet?
[16:08] @Tron 12 minutes seems to be pretty small window for clock skew
[16:08] I assume it was chosen due to 1/10th scaling from BTC?
[16:09] <@Wolfsokta> Not yet ruski, we'll cover that in a bit.
[16:09] <@Tron> We did divide existing by 10.
[16:10] <@Wolfsokta> Any further questions about DGW on testnet or on mainnet?
[16:10] What block is it activating on mainnet?
[16:10] <@Wolfsokta> 338778
[16:11] And will there be the need to update binaries twice (for DGW fork and asset layer fork)?
[16:11] <@Tron> We are activating DGW by block height because headers sync first, and the BIP9 activation flag sets a flag, and we need to look at either block height or version to know which diff algo.
[16:11] <@Wolfsokta> Calculated to be near the end of the month so we have some time with DGW on testnet.
[16:11] Someone on discord asked this a while back, but why Was DGW chosen over something like digishield or anyother algo
[16:11] <@Tron> And block version can be changed (tampering) and still make it on the chain.
[16:12] Binaries will need to be updated as more asset layer stuff get completed and tested. Not by the end of the month though.
[16:12] <@Tron> We looked at DGW and LWMA. LWMA has a lot of constants that must be tuned right.
[16:13] <@Tron> We were impressed with the amount of work on LWMA to analyze how it responds, but it wasn't straightforward to understand the nuances of how/why it works.
[16:13] zawy was in the #development channel on Discord. He's an expert on DAAs. I'm sure he would help with tuning LWMA if you asked.
[16:14] <@Tron> Either will be much better that what we have. Even at the extremes, it will adjust smoothly.
[16:14] Are there any issues or comments on the DGW code that should be addressed?
[16:14] @devs in general
[16:15] <@Wolfsokta> Thanks @brianmct, we did look extensively at the DGW code to ensure we weren't going to see the same issues that happened to Verge.
[16:16] so i guess you would have to make way more blocks with false timestamps to be able to exploit our version of dgw right?
[16:16] because of the 12 minute timestamp thing?
[16:16] <@Wolfsokta> With X16R, and with the changes Tron talked about we feel confident that this will address the swings without being able to be exploited.
[16:17] nice
[16:17] @russki Yeah, pretty much.
[16:17] verge is a different type of situation - but overall asics and mining are a risk always
[16:18] <@Wolfsokta> Okay, anything else on the difficulty targeting change?
[16:19] <@Wolfsokta> Cool, blondfrogs wanted to talk about subassets that were added.
[16:19] ooh yeah i saw those github commits
[16:19] looking good
[16:19] We also want to let everyone know that you can now create sub assets with the new binaries that will be posted soon. You can create these subassets using the issue rpc call. Qt will be built shortly. This will allow users to make an asset PARENT
[16:20] <@Wolfsokta> Basic overview. If you own an asset you can create sub-assets by including a '/
[16:20] nice
[16:20] And then make any of the following PARENT/A PARENT/B .... PARENT/Z
[16:20] <@Tron> We'll post a FAQ on assets later today.
[16:21] <@Wolfsokta> And it only is 100 Raven for a subasset
[16:21] on testnetv4 it still says asset activation status: waiting
[16:21] why?
[16:21] <@Tron> Yep, it needs to be voted in.
[16:21] <@Wolfsokta> We wanted to test the BIP9 activation process again as well. The more testing the better.
[16:21] We wanted to make sure that we follow the same process the Mainnet is going to go through.
[16:21] ok nice
[16:22] <@Wolfsokta> Any questions about subassets?
[16:23] are they unique?
[16:23] <@Tron> No
[16:23] <@Wolfsokta> Yes, they behave the same way as a normal asset, just live under an owned asset.
[16:23] <@Tron> Maybe I misunderstood the question. Unique with parent.
[16:23] Each subasset can have their own number issued? So PARENT/A can have 1,000 and PARENT/B can be 50?
[16:23] yes
[16:23] oooh ok that makes more sense
[16:23] <@Wolfsokta> Exactly thanks traysi
[16:24] <@Tron> And, not the same thing as "Unique Assets"
[16:24] <@Wolfsokta> The individual unique asset support is included in an upcoming phase.
[16:25] Moving onto the Segfault issue ----------------------->>>>>>>>>>> SEGFAULT
[16:25] Are we able to changes the properties of subassets after they have been created? Or is something like that specified when creating them?
[16:25] <@Tron> Yes
[16:25] can sub-assets be reassigned to other addresses while retaining control of the parent asset elsewhere?
[16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace?
[16:25] satoshi corbie @russkidooski
[16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace?
[16:26] <@Tron> Sub-assets are identical to assets after creation.
[16:26] <@Tron> Just cheaper to create, and in your "owned" namespace.
[16:26] Okay cool
[16:26] will subassets eventually have a unqiue tag? eg ASSET/SUB:1
[16:26] We have found an issue with our testnet binaries and are still looking to the issue. The issue presents itself when a user performs a reindexing of the chain. We think we have pinpointed the where the problem is and are currently working a fix. This fix will be out shortly.
[16:26] plan is to make default reissue=true and units=0 and allow increase in units on reissue
[16:26] How much is it going to be for a sub-asset?
[16:27] 100
[16:27] <@Wolfsokta> Okay, let's now focus on the SegFault issue that was discovered by Under.
[16:28] do you know what the issue was?
[16:28] <@Wolfsokta> It seems to be a build problem with the boost library.
[16:28] Still looking into though. :)
[16:29] <@Wolfsokta> We have been able to reproduce it on linux internally with 2.0.3
[16:29] yea i get the same issue on windows 10
[16:30] I saw a Bitcoin thread a while back about the seg fault error. I had it because I had conflicting versions of BDB
[16:30] static compiled on ubuntu 18.04
[16:30] <@Wolfsokta> We really appreciate you guys pulling down master and helping test.
[16:30] @Trap we will look into that also
[16:30] no problem, im just curious lol
[16:32] <@Wolfsokta> We haven't been able to build a windows version that doesn't have the segfault issue.
[16:32] <@Tron> We're dropping Windows support ;)
[16:32] lol
[16:33] Just finished setting up a new Windows test environment so we can test and validate the solution as we are working on it.
[16:33] The bdb issue is a known issue that has been around for some time. We are pretty certain it is a boost library issue, and are working quickly to get a windows build that fixes the issue.
[16:34] what did you guys do to fix the linux version?
[16:34] Once we have binaries for all supported platforms ready, hopefully tonight. No promises. We will make an announcement
[16:34] The issue has been fixed on Linux and Mac though?
[16:34] (oops sorry already answered)
[16:34] <@Wolfsokta> If anybody else gets there first with Windows please let us know what you found.
[16:34] Built the binairies on a Ubuntu 16.04 box.
[16:34] that was it?
[16:35] Yeah, we think so. 16.04 has boost 1.58 which seems to fix the issue. The build on 18.04 use boost 1.67 which seems to cause the issue.
[16:35] is there a boost 1.58 repo on 18.04?
[16:35] 18.04 used 1.65***
[16:36] I've built with boost 1.68 on arch Linux
[16:36] It worked
[16:37] wallet 2.0.x?
[16:37] @Trap, the issue is when -reindex is used.
[16:37] Oh sorry my bad
[16:37] Wallet 2.0.3
[16:38] <@Wolfsokta> For those that joined late we're discussing https://github.com/RavenProject/Ravencoin/issues/208
[16:38] 1 sec im going to boot into ubuntu and try compiling with 1.58 on 18.04
[16:39] Any other questions pertaining to the segfault?
[16:40] <@Wolfsokta> Alright, thanks everybody. Before we start the Q&A I would like to get some quick feedback on using IRC for this meeting.
[16:41] If we're going to use IRC we should take some measures to at least hide people's IPs when they join
[16:42] Yea. It is very hard to read this back.
[16:42] Also no message history
[16:42] If you disconnect and reconnect
[16:42] <@Tron> I'll throw in a vote for Discord.
[16:43] <@Wolfsokta> If you use a decent IRC client instead of the website it's not bad.
[16:43] Some of us used a VPN before we connected to IRC
[16:43] If needed we can restrict channel to Developer roles, etc for the developer meeting and open it up for general Q&A
[16:43] https://www.strawpoll.me/16247952
[16:43] poll
[16:43] Make a discord when only mods can submit links
[16:43] Where*
[16:45] Discord won the poll 5 to 2
[16:45] <@Wolfsokta> There are also a lot of IRC tools that can be used to track the meetings.
[16:45] we know
[16:46] <@Wolfsokta> We also want any developer to be able to speak.
[16:48] <@Wolfsokta> We're open to try Discord next week.
[16:48] <[kai]> perhaps you could even get a feed from this irc to discord?
[16:49] <[kai]> a feed would enable discordians to view the chat, but only contribute if they take the extra steps to come here.
[16:49] <@Wolfsokta> That's a good idea kai... Has anybody seen that working?
[16:50] <[kai]> https://github.com/reactiflux/discord-irc
[16:50] <[kai]> im sure you could make this a one way deal.
[16:51] <@Wolfsokta> I like that idea, let's try that for next week. So we'll meet here in IRC again, but it should be broadcast to Discord.
[16:53] <@Wolfsokta> Okay, we'll go with IRC next week with the broadcast to discord and re-visit for next week.
[16:54] <@Wolfsokta> Okay, let's do open Q&A for the next few mins.
[16:54] <[kai]> just a quickey, more for my curioisty, did you look at digishield?
[16:54] <[kai]> DGW solution seems solid.
[16:55] <[kai]> was just curious if it was one of the four solutions you looked at.
[16:55] <@Wolfsokta> Tron is answering... Any others Q?
[16:55] <@Tron> We briefly looked at Digishield, but our analysis was between DGW and LWMA.
[16:55] <[kai]> right on.
[16:56] <[kai]> cheers guys, see you next time.
[16:56] OPen the gates for the last 4 minutes for any other questions?
[16:58] <@Wolfsokta> Alright, thank you all for being here today and please join the development effort with us. If you have an idea, or a fix for an issue write it up and submit a pull request.
[16:59] <@Wolfsokta> Thanks again for all those that have contributed their time and effort to make Ravencoin successful. We have the BEST community.
[16:59] ^
6:59] You devs are pretty cool
[16:59] did the burn get discussed?
[16:59] <@Wolfsokta> Special thanks to Bruce, really glad you could make it with the short notice.
[17:00] <@Tron> Thanks everyone!
submitted by __pathfinder__ to Ravencoin [link] [comments]

Zeus/Gaw ASIC Setup Guide for Linux/Raspberry Pi

So I recently I became quite interested in mining and cyptocurrencies in general. So interested in fact that I bit the bullet and decided to buy myself a GAW Fury.
I then spent some time doing research on how to set up a GAW or Zeus ASIC on Linux, in particular on a Raspberry Pi, and have found most guides to be awful. The reason they are so bad IMHO is that they assume quite a bit of prior knowledge, either with Linux or mining, and give very little instructions. So I have tried to put together a guide that requires very little prior knowledge.
It is my aim that anyone could get their shiny new asic up and mining in no time using this guide. Anyway, I present...

The Complete Noobs Guide to Setting Up a Zeus or Gaw ASIC on Debian/Ubuntu/Raspberry Pi

Resources

About Cyrptocurrencies and Their Jargon

If you are new to cryptocurrencies and how they work I suggest taking a look at this series of KhanAcademy videos. They are for Bitcoin but the theory is the same. I found them very helpful when it came to understanding what mining actually does and the mechanics of cyrptocurrencies.
Also take a look at sircamm22 his info found here, is great and breaks down a large number of concepts. I slightly disagree with no. 21 regarding preordering. Just exercise common sense.

Linux

If you are new to Linux you could follow along by simply typing in the commands. However I highly recommend taking the time to learn what you are doing. This course is a great place to start.

Computer Setup

By the end of this section you will have your device turned on, fully setup and connected to the internet with.
Note: Commands to be typed into the command line will be displayed like this:
echo Hello World

Desktop/Laptop

For laptops and desktops already running Ubuntu or Debian I will assume you have setup your internet setup as part of the installation.
If not: There are plenty of guides out there and the installation/setup process is very easy. A good place to start for Ubuntu is here.
Now open up a terminal window. Ctrl + alt + t on a standard Ubuntu installation.
If you plan on using this PC without a monitor I would suggest installing an SSH Server.
These commands will be discussed later on in the guide.
sudo apt-get -y install openssh-server
sudo service openssh-server start

Raspberry Pi

The Raspberry Pi Foundation has put together a great guide in PDF format.
Use NOOBS it will save you a lot of trouble. NB: Some SD cards don't support NOOBs but will work fine if the image is put on using a different method.
Here is a great guide for setting up the Raspberry Pi SD card from Elinux.org. In fact it's a great place to start for anything RPi related. Raspberry Pi hub at Elinux.
Once the SD card is setup you will need to insert it into the Raspberry Pi and boot. Install Raspbian from the NOOBs menu and wait.
Follow this guide by Adafruit for first time setup. You will need to enable SSH Server.
I suggest not starting the desktop on boot. It can be easily run from the command line by typing startx.
Follow this guide by Adafruit to setup your network. Found here. No need to do this if you set up previously in the first time config.
We will also at this point want to setup ssh. Again I will point you to an Adafruit guide.
Once done exit back to a standard command line interface. This can be done in LXDE by using the power off menu located in the bottom right corner.

Miner Setup

Installing BFGMiner

If you want to the Raspberry Pi or PC without a monitor go ahead and SSH into your device.
So now you should be staring at a command line interface whether on the device with a monitor or via SSH.
First things first lets make sure we are all up to date. This will update our package list from the repositories and upgrade them to the newest version. "-y" Will simply say yes to any prompts.
sudo apt-get update && sudo apt-get -y upgrade
We are going to need to install some useful tools. Git-core is how we will clone and download BFGMiner from GitHub and Screen allows multiple command line instances and means if we exit out of ssh session or quit Terminal on Ubuntu, BFGMiner will continue to run.
sudo apt-get install git-core screen
We also need to download some other tools/dependencies to ensure that BFGMiner will compile successfully.
sudo apt-get -y install build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev libc-bin
Ok now change into your home directory.
cd ~
And clone BFGMiner by Darkwinde.
git clone https://github.com/Darkwinde/bfgminer.git
Once the download has completed move into the bfgminer directory.
cd bfgminer
The following steps may take a while.
Now run autogen.sh
sudo ./autogen.sh
You will need to make the configure script execuitable.
sudo chmod +x ./configure
Now configure bfgminer
sudo ./configure CFLAGS="-O3" --enable-scrypt
Now lets make!
sudo make
Install BFGMiner
sudo make install
One more thing...
sudo ldconfig

Running BFGMiner

If you haven't already plug in your ASIC.
Just confirm your system is recognising the ASIC.
lsusb
Its output should look similar to this (no need to type this in):
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Yep there it is our ASIC listed as device 005. There is no need to install any drivers, unlike in windows, as they come in the kernel.
Now lets actually start BFGMiner.
You will want to start a screen session to ensure BFGMiner doesn't quite when you exit.
"-S" is the option for starting a new screen session. You can replace "miner" with anything you like.
screen -S miner
Now you can run the commands below.
Here is a sample of what you should type. You will need to replace somethings with your own values.
sudo bfgminer --scrypt -o stratum+tcp://URL:PORT -u USERNAME -p PASSWORD --zeus-cc CHIPCOUNT --zeus-clk 328 -S zeus:/dev/ttyUSB0
Where:
URL:PORT is the address and port of the pool you wih to use. Now I won't suggest a pool. I will leave that decision up to you. If you do wish to mine DOGE take a look at this site for a list of pools and comparisons.
USERNAME this is the username you use on the pool. Every pool is different. Check your pool's website for details. PASSWORD same as above. Specific to your pool, not every pool requires one.
CHIPCOUNT this is specific to which ASIC you are using.
For GAWMiner ASIC's:
  • War Machine: 256
  • Falcon: 128
  • Black Widow: 64
  • Fury: 6
For ZeusMiner ASIC's:
  • Blizzard: 6
  • Cyclone: 96
  • Hurricane X2: 48
  • Hurricane X3: 64
  • Thunder X2: 96
  • Thunder X3: 128
Now to make sure you don't stop mining when you exit ssh or terminal. Press:
ctrl + a + d
To come back to the BFGMiner screen simply run:
screen -r miner
You're done!!

Start on Boot

First off you will want to make sure you have BFGMiner running correctly. Ensure you have the miners set up properly and your pool correctly configured.
Start a BFGMiner instance, detailed above.
Once the instance has started and you are happy with how everything is working press "s" on your keyboard to enter the settings menu.
Now press the "w" key. Don't press enter. We want to specify where our config will go. Type:
/home/USERNAME/bfgminer.conf
Substitute USERNAME for your user. On a standard RPI install its pi. On ubuntu it's what you set during the instillation.
Now press the enter key to return back to the main BFGMiner screen. Press "q" on your keyboard to exit BFGMiner. You should now be back in the command line.
Now we want to edit a file called rc.local. Any commands in this file will be executed on boot.
sudo nano /etc/rc.local
Depending on your system this file may already contain some commands. Be careful not to delete them.
After the last command and before "exit 0" type the following on one line:
sudo -u USERNAME screen -d -m sudo bfgminer --config /home/USERNAME/bfgminer.conf
Where USERNAME = your username
Hit ctrl + x then y to save and exit nano.
The above command will create a new screen session and run bfgminer using the config we created earlier. All while as our username so that we can easily reattach.
Lets reboot to ensure it is working correctly:
sudo reboot
Once rebooted and logged in, show all running screen sessions:
screen -ls
Reattach to the session. You only need to use the numbers before the first dot.
e.g Mine looks like: 2480..hostname (13/07/14 12:02:09) (Detached). So I type:
screen -r 2480
Verify everything worked as expected. Then ctrl + a + d to exit.
You have now setup BFGMiner to restart on reboot.

Power Failure

If you are using a Raspberry Pi and it loses power it will automatically reboot on receiving power again.
For standard desktop PCs there is an option in some BIOS/UEFI to turn the computer on when it receives power. Consult your motherboard's manual and manufacturer's website.

Sources

Here is where I got my info from.
And of course /dogemining

Wrap Up

Congrats you've done it. You have managed to successfully get your shiny new asic mining away.
I do plan to make another guide detailing how to setup and use StarMiner a ready to go RPi mining distro.
So I hope this is helpful for you guys. I have seen lots of posts asking the exact same questions again and again and I have tried to answer these as best I can. I am still learning about this stuff so if there is something I have missed or a mistake I have made please tell me.
Anyway good luck. And I'll see you at the moon.
Cheers Frogsiedoodle
Edit 1: Layout and formatting.
Edit 2: Added instructions for screen which I initially forgot.
Edit 3: Removed 1 unneeded dependency
Edit 4: Added section on start on reboot and power failure.
submitted by Frogsiedoodle to dogemining [link] [comments]

Compiling on linux and how do exchanges handle multiple cryptonote wallets?

My big question, how do exchanges handle per user XMR addresses? Simplewallet and the docs I found suggest that it is impossible to handle multiple addresses at the same time. So how can major exchanges handle seemingly 100s of monero users depositing to XMR addresses. Is the suggestion to instead use Payment ID to identify transactions/crediting of incomming users? Anyone know any other tricks that can enable per user addresses? I am a novice programer and I would like to play with some projects on the test net.
I can't see running monero in a non sandboxed environment until I can compile from source, has this been a show stopper for anyone else? I have attempted to build with debian 6,7 and ubuntu 12.04,14.04,14.10, has anyone had success with this(for me it dies during make)? Considering attempting a build on BSD. I will write a guide and post it once I can figure it out. It seems like the defacto method for installation is a shellscript, which dies for me like compiling from hand. This is the second time I have spent the better part of a few days trying to get involved with monero. The first time was during the summer - unfortunately not much has changed, I should have bit the bullet then and just used the provided binaries.
Reminds me of when I got into bitcoin - took me forever to figure out those pesky wx libraries. next thought.. is there purpose when devs choose such obscure libraries?
submitted by freeborn to Monero [link] [comments]

Code Audit by @jyap

This is cut and paste from jyaps post in the thread.
https://bitcointalk.org/index.php?topic=624017.msg7042831#msg7042831
I was invited to perform a code audit of the Pinkcoin source code (code repository http://github.com/bigman7788/pinkcoin) by Twitter user @CryptoCayce. I have not received any compensation of any kind for this audit.
Initially I wasn't impressed as the code uploaded to the Github repository was just one big commit which did not show any code history. From prior coin history I could see that Pinkcoin looked like it was a clone of Novacoin (code repository https://github.com/novacoin-project/novacoin). The main difference is Novacoin uses Scrypt is its proof of work algorithm whereas Pinkcoin uses X11.
I downloaded both coin repositories and copied the Pinkcoin source code over the Novacoin source code.
The Pinkcoin source code has some newer features such as adding the 'getstakinginfo' and additional GUI controls for staking and unlocking your wallet.
In future, the security of the Pinkcoin code and daemon would benefit with an update of their code which adds some block hash checkpoints as well as stake modifier checkpoints. None of these currently exist.
I can confirm from inspecting the block chain and code Pinkcoin does not have a premine (hidden or otherwise).
Pinkcoin does have some amount of instamine where the address PTVSVbWVUAgfWAx2u1cmBfiNR85kEhCMzC has the reward for the first 186 blocks (4,650,000 Pinkcoins). According to @CryptoCayce, this address belongs to the original developer "bigman" on Bitcoin Talk Forums (https://bitcointalk.org/index.php?action=profile;u=324234). He mentions the coins for this address have been dumped onto the Bittrex exchange weeks ago and that "bigman" is mutually agreed upon as no longer a member of the project.
I was satisfied that the Proof of Stake, Block time, Block reward and other parameters matches their announcement details.
Pinkcoin does not appear to have any hidden, obfuscated or malicious code. No core functions or RPC commands were modified that I could find.
I was able to compile the Pinkcoin daemon and download the blockchain on a Linux virtual machine running Ubuntu 12.04.4 LTS.
This statement does NOT constitute a public endorsement of Pinkcoin nor does it guarantee that Pinkcoin does not or will not have any issues.
FULL DISCLOSURE: I often invest in coins from time to time and have recently tweeted the coins I own on my Twitter account @jyap. I liked that Pinkcoin did not have a premine and the transparency of the group when questions were brought up. I personally bought 1,000,000 Pinkcoins at market rate directly from @CryptoCayce since I liked the group's outreach plans and projects mentioned in their annoucement.
INFO: My Twitter account is https://twitter.com/jyap (@jyap). I am an IT professional with over 12 years experience. My released contributions to cryptocurrency involve block explorers, Mac OS X wallets and a mailing list Cryptocurrency Weekly.
submitted by fayoling to pinkcoin [link] [comments]

" Bitcoin bad " [ participating ] Heartbleed vulnerability affects bitcoins ... ( Chinese hackers published technical affirm ) - Transfer from Bitcoin first Chinese community -

weibo: http://weibo.com/5107450688/B0Kv8hLAk
BBS: http://bbs.btcman.com/forum.php?mod=viewthread&tid=17782&page=1&extra=#pid82563#0-tsina-1-83270-397232819ff9a47a7b7e80a40613cfe1
Heartbleed vulnerability affects bitcoin ... let the brother in person to tell you how dangerous loophole Heartbleed
Disclaimer: This article caused by subsequent exposure , at your own liability .
Author : btcrobot
Contribute BTC: 1NDnnWCUu926z4wxA3sNBGYWNQD3mKyes8 Originally wanted to write articles related articles side chains , but feel deep enough , the other seems a bit of a MM Frank wrote , brother does not like re- nonsense, direct point of security-related today . . . . .
Evil octal dividing line . . . . . . . . . . . .
About Heartbleed loopholes, as a bit of people , must be sensitive to , ah, brother of the first time I felt vulnerability unlimited , ideas unlimited , unlimited play , as to get rid of xxx, it needs Martian guts , brother still relatively conservative , but in another way detour and the line, this is just to let you experience the next :
Steps are as follows :
1 find various bits coins, currency cottage client IP address , find a specific port, which enable SSL
Get bitcoin client ip installed two ways :
1 Download a qt-bitcoin client, open debug.log, ok it collects inside IP
2014-04-21 01:53:27 init message: loading is complete 2014-04-21 01:53:27 Initialization result: 1 2014-04-21 01:53:28 ERROR: GetMyExternalIP (): connection closed 2014-04-21 01:53:28 receive version message: / Satoshi: 0.8.5 /: version 70001, blocks = 296904, us = 219.147.23.114:1650, them = 58.64.155.69:8333, peer = 58.64.155.69 : 8333 2014-04-21 01:53:28 Added time data, samples 2, offset -6 (+0 minutes) 2014-04-21 01:53:33 ERROR: GetMyExternalIP (): connection to 74.208.43.192:80 failed 2014-04-21 01:53:35 receive version message: / Satoshi: 0.8.2.2 /: version 70001, blocks = 296904, us = 219.147.23.114:1657, them = 192.155.81.62:8333, peer = 192.155.81.62 : 8333 2014-04-21 01:53:35 Added time data, samples 3, offset -13 (+0 minutes) 2014-04-21 01:53:35 No valid UPnP IGDs found 2014-04-21 01:53:35 upnp thread exit 2014-04-21 01:53:36 receive version message: / Satoshi: 0.8.5 /: version 70001, blocks = 296904, us = 219.147.23.114:1659, them = 194.71.109.94:8333, peer = 194.71.109.94 : 8333 2014-04-21 01:53:36 Added time data, samples 4, offset +12 (+0 minutes) 2014-04-21 01:53:36 socket recv error 10054 2014-04-21 01:53:41 ERROR: GetMyExternalIP (): connection closed 2014-04-21 01:53:48 receive version message: / Satoshi: 0.9.99 /: version 70002, blocks = 296904, us = 219.147.23.114:1680, them = 71.13.251.162:8333, peer = 71.13.251.162 : 8333 2014-04-21 01:53:48 Added time data, samples 5, offset -12 (+0 minutes) 2014-04-21 01:53:48 nTimeOffset = -6 (+0 minutes) 2014-04-21 01:53:48 ERROR: GetMyExternalIP (): connection to 212.117.175.194:80 failed 2014-04-21 01:53:48 ext-ip thread exit 2014-04-21 01:53:49 receive version message: / Satoshi: 0.9.1 /: version 70002, blocks = 296904, us = 219.147.23.114:1681, them = 68.151.120.205:8333, peer = 68.151.120.205 : 8333 2014-04-21 01:53:49 Added time data, samples 6, offset -13 (+0 minutes) 2014-04-21 01:53:50 receive version message: / Satoshi: 0.9.0 /: version 70002, blocks = 296904, us = 219.147.23.114:1682, them = 88.178.92.109:8333, peer = 88.178.92.109 : 8333 2014-04-21 01:53:50 Added time data, samples 7, offset -12 (+0 minutes) 2014-04-21 01:53:50 nTimeOffset = -12 (+0 minutes)
Look at these IP right, gather next :)
2 Use blockchain, this can cause huge point , opening https://blockchain.info/zh-cn/connected-nodes
Not only know the IP, and intuitively know the client version used for those versions vulnerable , silent, huh. .
file :/ / / C: \ DOCUME ~ 1 \ ADMINI ~ 1 \ LOCALS ~ 1 \ Temp \ ksohtml \ wps_clip_image-28929.png
3 write a small crawler , automated constantly crawl the IP, NG saved as a file in the following format , do not ask me to code. . . Their play to 193.109.68.62 212.3.147.37 Xxx Yyy . . . .
4 Improved bleed procedures through the entire document , well, to the point code
func readLines (path string) ([] string, error) { file, err: = os.Open (path) if err! = nil { return nil, err .... 00000580 32 32 2d 31 33 39 32 38 39 37 31 31 31 30 30 30 | 22-1392897111000 | ........
| onnection: keep-| | alive .. If-Modifi | | ed-Since: Fri, 1 | | 1 Apr 2014 10:35 | |: 05 GMT ........; | | `...... ~ 9D .. X. .. |
https://5.9.121.236/login/
If 443 , if it is a server , I rely on you regularly collect it, pattern matching. . . . Bypass to the other , web springboard , and the like . . . If ssl + rpc, broken rpc, if not set the wallet password, and then send a command transfer bitcoins , oh, my god ...
Bitcoins are so cottage currency would not have said that if there is 443 loopholes still be out of every minute . . .
heartbleed bitcoin client to attack , in the case of open rpc protocol , using ssl certification, can be attacked . This is the vast majority of the server program will open options. Individual users should not panic. . . .
Well, not much to say , and you figure it out , and quickly upgrade it, rose no harm ! ! ! ! The key is to site users , exchanges, router port mapping is also careful. .
Disclaimer: purely technical discussion, in fact, I guess black circle know. . . Sent to run the risk of being accused of a two-way . . . You feel for it. .
https://bitcoin.org/en/alert/2014-04-11-heartbleed
OpenSSL Heartbleed vulnerability 11 April 2014What happened The version of OpenSSL used by Bitcoin Core software version 0.9.0 and earlier contains a bug that can reveal memory to a remote attacker. See http://heartbleed.com/ for details. What you should do Immediately upgrade to Bitcoin Core version 0.9.1 which is linked against OpenSSL version 1.0.1g. If you use the official binaries, you can verify the version of OpenSSL being used from the Bitcoin Core GUI's Debug window (accessed from the Help menu). If you compiled Bitcoin Core yourself or use the Ubuntu PPA, update your system's OpenSSL. Linux users should also upgrade their system's version of OpenSSL. Android Android version 4.1.1 is vulnerable to Heartbleed. Try if you can upgrade to at least Android 4.1.2. If you are using Bitcoin Wallet on an Android phone, you should upgrade the app to at least version 3.45. How serious is the risk If you are using the Windows version of the Bitcoin Core GUI without a wallet passphrase, it is possible that your wallet could be compromised by clicking on a bitcoin:. Payment request link If you are using bitcoind (on Linux, OSX, or Windows) , have enabled the-rpcssl option, and allow RPC connections from the Internet, an attacker from a whitelisted (-allowip) IP address can very likely discover the rpcpassword and the last rpc request. It is possible (but unlikely) private keys could be sent to the attacker.
submitted by 51btc to Bitcoin [link] [comments]

How to compile and run VanityGen Bitcoin tool in Ubuntu 14.04 How to build an altcoin or bitcoin on Ubuntu Linux Server Shell How to Bitcoin Miner with Ubuntu VPS - Setup Nicehash Miner via Ubuntu VPS Java Programming using Terminal in Ubuntu 12.04(compile and run) -1 Installing CM compiler using PPA on Ubuntu 12.04

Compile Bitcoin Classic on Ubuntu 16.04 x64. The example shows how to compile current github version of on Bitcoin Classic (i.e., 0.12) on Ubuntu 16.04 x64.. More information about compilation of Bitcoin Classic can be found here.The official Bitcoin Classic's binaries can be download from here.. Dependencies Dismiss Join GitHub today. GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together. Compile Bitcoin on Ubuntu 14.04. GitHub Gist: instantly share code, notes, and snippets. Bitcoin has now an officially maintained PPA with a release candidate version of the peer-to-peer daemon and the client.. Bitcoin has a launchpad project i.e. same project status as Unity/Docky/Openshot etc. The maintainer - Matt Corallo - is a major contributor to the official bitcoin.org website.. This will upgrade all versions from 10.04 and later. I am trying to compile litecoind on Ubuntu 15.04 and I stuck here: /litecoin/src$ make -f makefile.unix USE_UPNP=- make: makefile.unix: No such file or directory make: *** No rule to make target 'makefile.unix'. Stop. I found some a little bit different ways to compile litecoind, but every time I have problems with "makefile.unix". Can someone ...

[index] [9001] [10710] [28256] [51133] [40671] [19513] [7088] [4348] [19951] [940]

How to compile and run VanityGen Bitcoin tool in Ubuntu 14.04

Create , Compile, Execute any (dot).Java file using Terminal and Gedit 1- Create file using vi filename.java 2- Press ESC key and Type :wq(save and exit) 3- Type gedit filename.java 4- Type your ... Installing g95 on ubuntu 12.04 Helpful? Please support me on Patreon: https://www.patreon.com/roelvandepaar With thanks & praise to God, and with thanks to t... This video Shows how to Compile Bitcoin Source Code on Linux operating systems. it covers almost everything on how to compile bitcoin source code. Build Bitc... Use the VanityGen tool to generate a Bitcoin address that stands out from the others. Decide for yourself the first part of the address, and have an address ... How to build an altcoin or bitcoin on Ubuntu Linux Server Shell ... How create altcoin pool - InflationCoin - Ubuntu 16.04 - Duration: 1:07:13. Rafael Vieira 14,618 views. 1:07:13. Linux File ...

#