Debian Package Tracking System - libbitcoin

[IDEA] [PROPOSAL] Monero Debian (deb) packages / Debian package repository deb.getmonero.org (I can do)

I have the skills to implement this if wanted.
Possible User Experience
This is a proposal, i.e. not implemented yet. Instructions for users, simplified.
How to install monero using apt-get
Download the repository signing key.
wget https://www.getmonero.org/monero.asc
Add the signing key.
sudo apt-key --keyring /etc/apt/trusted.gpg.d/monero.gpg add ~/monero.asc
Add APT repository.
echo "deb https://deb.getmonero.org buster main" | sudo tee /etc/apt/sources.list.d/monero.list
Update your package lists.
sudo apt-get update
Install monero.
sudo apt-get install monero
A few technical implementation details
I would simply grab the binaries provided by getmonero.org, download them, check software (gpg) signatures, put these into deb packages, add these to a repository, and upload the repository.
What I would not do is creating the binaries during package creation. While this is nice to have, it doesn't help user experience and blocks the progress on reaching this goal. See next chapter.
Why simply put the pre-build Monero binaries into a deb package?
1) After bitcoin existing for more than 10 years, being popular and being in Debian unstable (sid) it still never made its way into Debian testing, let alone stable. Reason being explained that a difference in underlying libraries (even just security fixes) during compilation may result in a network split. Binaries compiled during packaging on different versions of Linux distributions might have different libraries that might cause a network fork / chain split.
References:
(Note: above website saying Tags: fixed-upstream is probably a mistake as discussion at bottom says.)
2) The github issue of packaging monero stalled.
3) By shipping the same binaries as provided by getmonero.org reduces the chances of introducing a backdoor.
Many Options
Timeline
Doable quickly. The electrum (bitcoin) AppImage was recently added to a Debian package (binaries-freedom) by me and is now easily installable in Whonix. Pre-installed in testers version of Whonix already.
About Me
I am the founder of Whonix, which I am maintaining at present for more than 7 years.
Whonix (formerly TorBOX) is a Debian GNU/Linux–based security-focused Linux distribution. It aims to provide privacy, security and anonymity on the internet.
You can see an overview of packages I am maintaining on my github profile.
To proof that this forum account adrelanos corresponds the same person maintaining whonix.org, it is added here.
Questions
What happened to, what is the successor of the forum funding system?
submitted by adrelanos to Monero [link] [comments]

Just a warning about the electrum bitcoin wallet on debian sid

I installed electrum from the repository today and when I tried to send some bitcoin I received an extremely convincing pop-up in the client with pictures and everything saying that my client was out of date and that I needed to visit the site to update. Of course the site linked was electrum.la as opposed to the official electrum.org. Luckily I noticed this pretty fast, but this is definitely one of the most advanced phishing schemes I have seen to date. The electrum package seriously needs updating, I even found a bug report about it from 3 months that hasn't been resolved. Over $3m has been stolen using this phishing scheme and that number is increasing every day.
tl;dr install electrum from source on the official site, do NOT use the package right now
submitted by voidsource0 to debian [link] [comments]

Interesting technical facts about Groestlcoin that might explain price rise

Disclaimer: After doing some research, I own a small amount of Groestlcoin and no Vertcoin (I rkn VTC is overvalued currently). Might buy some VTC after it corrects. Here's why...
Original text: Posted by posted [–]jackielove4u 4 days ago https://www.reddit.com/groestlcoin/comments/78258z/is_grs_possibly_threatened_by_bitcoin_gold/dormg88/
Our selling points are:
submitted by enozym111 to CryptoCurrency [link] [comments]

Dogecoin on Linux - The Complete Beginner's Guide

I'm writing this because I couldn't find a single condensed guide on compiling the wallet and running mining software on linux, specficially Ubuntu/Linux Mint. I combed Bitcoin and Litecoin forums for similar problems I was running into and eventually got everything nailed down, so here it is in one place, for new Shibes.
If you want to make a Dogecoin directory in your downloads folder to keep things organized, you will need to modify these commands to refelct the change. So instead of going to ~/Downloads/ you will need to go to ~/Downloads/Dogecoin and be sure to put the zipped files there when you download them, but the commands will be the same otherwise.
cwayne18 put in the work to make a PPA for the QT client here.
Ubunutu/Mint/Debian users should be able to install the client with the following commands:
sudo add-apt-repository ppa:cwayne18/doge sudo apt-get update && sudo apt-get install dogecoin-qt 
To update using this method, run
sudo apt-get update && sudo apt-get upgrade dogecoin-qt 
Compiling the Wallet Manually
I suggest using the PPA above, but if you want to compile manually, here you go.
1)Download the newest source from here. If you want to check out the Github page, click here
2)Unzip the package with the native client OR, navigate to your downloads and unzip
cd ~/Downloads unzip dogecoin-master.zip 
3)Now it's time to compile. You will need to install the dependencies, just copy and paste the following code. It will be a fairly large download and could take some time. It is always important to update before installing any new software, so we'll do that first and then install the dependencies.
sudo apt-get update sudo apt-get upgrade sudo apt-get install libssl-dev libdb-dev libdb++-dev libqrencode-dev qt4-qmake libqtgui4 libqt4-dev sudo apt-get install libminiupnpc-dev libminiupnpc8 libboost-all-dev build-essential git libboost1.53-all-dev 
4)Once that is done, go to the doge-coin master directory and compile:
cd ~/Downloads/dogecoin-maste sed -i 's/-mgw46-mt-sd-1_53//g' dogecoin-qt.pro qmake USE_UPNP=- USE_QRCODE=0 USE_IPV6=0 make -j3 
After running the qmake command you will likely see some text similar to
Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target language has less forms. If this sounds wrong, possibly the target language is not set or recognized. 
It's perfectly normal, so don't worry about that.
Your Dogewallet is ready to go! The executable is in ~/Downloads/dogecoin-maste and called dogecoin-qt. Your wallet information is in ~/.dogecoin. You can run the wallet at any time by opening terminal and typing
cd ~/Downloads/dogecoin-maste ./dogecoin-qt 
Future upgrades to dogewallet are easy. Back up your wallet.dat, and simply follow the same directions above, but you'll be unzipping and building the newer version. You will likely need to rename the old dogecoin-master directory in ~/Downloads before unzipping the newest version and building. Also, it is likely that you will not need to install the dependencies again.
Alternate Method For Installing Dogecoin Wallet from Nicebreakfast
After installing the dependencies listed in step 3, open terminal, then navigate to where you want Dogecoin Wallet stored and run:
git clone https://github.com/dogecoin/dogecoin ./autogen.sh ./configure make 
then when the wallet is updated just run
git pull 
from the dogecoin directory.
GPU Mining
GPU mining requires CGminer. My suggestion is to get the executable already built. The creator of cgminer has removed the built file from his website, but I've uploaded it here
sudo apt-get install pkg-config opencl-dev libcurl4-openssl-dev autoconf libtool automake m4 ncurses-dev cd ~/Downloads tar -xvf cgminer-3.7.2-x86_64-built.tar.bz2 
Don't use anything newer than 3.7.2. The newer versions of CGMiner don't support GPU mining.
That's it! You have cgminer ready to go! You will run cgminer with the following syntax
cd ~/Downloads/cgminer-3.7.2-x86_64-built/ ./cgminer --scrypt -o stratum+tcp://SERVERNAME:PORT -u WORKER.ID -p PASS 
A good guide for fine tuning cgminer can be found here; follow the litecoin example.
EDIT
I had trouble getting cgminer running with a single line command, but running it via an executable .sh file works. This is covered in the cgminer setup guide I posted above but I'll put it here too. In the same directory that has the cgminer executable, you need to make a file called cgminer.sh and make it executable. It should contain the follwing:
export GPU_USE_SYNC_OBJECTS=1 export GPU_MAX_ALLOC_PERCENT=100 export DISPLAY=:0 find *.bin -delete sleep 5 ./cgminer 
Then you can call cgminer in terminal by doing ./cgminer.sh You will need a cgminer.conf file containing all your options. All of this is covered in the guide that is linked above.
A quick note about AMD drivers: They used to be a huge PITA to install and get working, but the newest Catalyst drivers are great. There's a GUI installer, everything works out of the box, and there is a lot of documentation. You can download them here: AMD Catalyst 14.6 Beta Linux
CPU Mining
For CPU mining I use minerd because it doesn't require any work to get running, simply download it and get to work. Download the built file for your machine 32-bit or 64-bit, and then unzip it and you're ready to go!
cd ~/Downloads tar -xvf pooler-cpuminer-2.3.2-linux-x86.tar.gz 
The executable is called minerd and it will be in ~/Downloads but you can move it to wherever you like. To run it, pull up terminal and do
cd ~/Downloads minerd --url=stratum+tcp://SERVER:PORT --userpass=USERNAME.WORKERNAME:WORKERPASSWORD 
You're done! Happy mining!
Common Issues
I ran into this and I've seen others with this problem as well. Everything installs fine but there is a shared library file that isn't where it should be. In fact, it isn't there at all.
 libudev.so.1: cannot open shared object file: No such file or directory 
In terminal, do
sudo updatedb locate libudev.so.0.13.0 
And it will probably return a path /lib/x86_64-linux-gnu. Inside that directory there's a library file called libudev.so.0.13.0. You'll need to make a symlink (aka shortcut) that links libudev.so.1 to libudev.so.0.13.0 So, assuming you're working with libudev.so.0.13.0 do this
cd /lib/x86_64-linux-gnu sudo ln -s libudev.so.0.13.0 libudev.so.1 
Now if you do
ln -l 
You should see
libudev.so.1 -> ./libudev.so.0.13.0 
Meaning you've made the symlink. Also, the text for libudev.so.1 will be blue.
submitted by Boozybrain to dogecoin [link] [comments]

Mega FAQ (Or: Please come here for your questions first)

Qbundle Guide (Step by step setup & Bootstrap) https://burstwiki.org/wiki/QBundle
1( I want to mine or activate My account. Where do find the multiple coins?
You only need 1, an outgoing transaction or reward reassignment will set the public key. Get them from:
https://www.reddit.com/burstcoinmining/comments/7q8zve/initial_burstcoin_requests/
Or (Faucet list)
https://faucet.burstpay.net/ (if this is empty, come back later)
http://faucet.burst-coin.es
Or
https://forums.getburst.net/c/new-members-introductions/getting-started-initial-burstcoin-requests
2( I bought coins on Bittrex and want to move to my new wallet, but can't. Why?
Bittrex will only send to accounts with a public key (not a Burst requirement) so see number 1 and either set the name on the account (IF you will not mine) or set the reward recipient to the pool. Either action will enable the account and allow for transfers from Bittrex.
3( I sent coins from Poloniex/anywhere to Bittrex and they don’t show up after a considerable time. Why?
You need to set an unencrypted message on the transaction, informing Bittrex which account to send the funds to (this is in the directions on Bittrex). Did you do this? Contact Bittrex support with all the details and eventually you will get your funds.
4( How much can I make on Burst?
https://explore.burst.cryptoguru.org/tool/calculate
Gives you an average over time assuming a few things like: Average luck/100% uptime/no overlapping/fees on pool/good plot scan time (<20 seconds) if you do not have all of these, you may not see that number.
5( If I use SSD’s would I make more money?
No, it’s 95% capacity and 5% scan time that determine success. More plot area = better deadlines = better chance of forging a block, or better rates from a pool.
6( What is ‘solo’ and ‘pool’ (wasn’t his name Chewbacca?)
Solo is where you attempt to ‘forge’ (mine) a block by yourself; you get 100% of the block reward and fees. But you only receive funds if you forge, no burst for coming in second place.
Pools allow a group of miners to ‘pool’ together their resources and when a miner wins, they give the pool the winnings (this is done by the reward assignment you completed earlier), it is then divided according to different percentages and methods and burst is sent out according to pool rules (minimum pay-out, time, etc.)
7( I have been mining for 2 days and my wallet doesn’t show any Burst WHY?
Mining solo: it is win-or-lose, nothing in between, and wining is luck and plot size. Pool mining: because it costs 1 burst to send burst, the pools have either a time requirement (every X days) or a minimum amount (100 burst +) so you need to research your pool. Some pools allow for you to set the limit (cryptoGuru and similar) to be met before sending
8( How do I see what I have pending?
On CryptoGuru, based pools, it’s the ‘Pending (burst)’ column, other pools, look for the numbers next to your burst ID. One is Paid and the other pending.
9( I’m part of a pool and I forged a block, but I didn’t recieve the total value of the block, why?
A pool has 2 basic numbers that denote the pay-out method, in the format ‘XX-XX’ (i.e. 50-50) The first number is the % paid to the block forger (miner) and the second is the retained value, which is paid to historic ‘shares’ (or, past blocks that the pool didn’t win, but had a miner that was ‘close’ to winning with a good submitted deadline)
Examples of pools:
0-100 (good for <40TB)
20-80 (30-80TB)
50-50 (60-200TB)
80-20 (150-250)
100-0 (solo mine, 150+ TB)
Please note that there is an overlap as this is personal preference and just guidance; a higher historical share value means a smoother pay-out regime, which some people prefer. If fees are not factored in, or are the same on different pools, the pay-out value will be the same over a long enough period.
10( Is XXX model of hard drive good? Which one do you recommend?
CHEAP is best. If you have 2 new hard drives, both covered by warranty, get the one with the lowest cost per TB (expressed as $/TB , calculated by dividing the cost by the number of terabytes) because plot size is KING,
11( How many drives can I have on my machine?
For best performance, you can have up to 2 drives per thread (3 on a new fast AVX2 CPU). So that quad-core core-2-quad can have up to 8 drives, but a more modern i7 with 4 cores + hyper threading can squeeze 8 * 3 or 24 drives. (Performance while scanning will suffer)
12( Can I game while I mine?
Some people have done so, but you cannot have the ‘maximum’ number of drives and play games generally.
13( Can I mine Burst and GPU mine other coins?
Yes, if you CPU Mine Burst.
14( I’m GPU plotting Burst and GPU mining another coin, my plots are being corrupted, why?
My advice is dedicating a GPU to either mining or plotting, don’t try to do both.
15( What is a ‘plot’?
A plot is a file that contains Hashes, these hashes are used to mine burst. A plot is tied to an account, but they can be created (with the same account ID) on other machines and connected back to your miner(s).
16( Where can I trade/buy/sell Burst?
A list of exchanges is maintained on https://www.reddit.com/burstcoin/ (on the right, ‘Exchanges’ tab) the biggest at the moment are Bittrex and Poloniex, some offer direct Fiat-to-Burst purchase (https://indacoin.com for example)
17( Do I have to store my Burst off the exchange?
No, but it’s safer from hackers who target exchanges, if you cannot guarantee the safety or security of your home computer from Trojans etc, then it might be best to leave on an exchange (but enable 2FA security on your account PLEASE!)
18( What security measures can I take to keep my coin safe?
When you create an account, sign out and back in to your wallet (to make sure you have copied the pass phrase correctly) and keep multiple copies of the key (at least one physically printed or written down and in a safe place, better in 2 places) do not disclose the passphrase to anyone. Finally use either a local wallet or a trusted web wallet (please research before using any web wallet)
19( How can I help Burst?
Run a wallet, which will act as a node (or if you’re a programmer, contact the Dev team Bring attention to burst (without ‘shilling’ or trying to get people to buy) And help translate into your local language
Be a productive member of the community and contribute experience and knowledge if you can, or help others get into Burst.
20( Will I get coins on the fork(s) and where will they be?
There will be no new coin, and no new coins to be given/air dropped etc, the forks are upgrades to burst and there will not be a ‘classic’ or ‘new’ burst.
21( Will I need to move my Burst off of the exchange for the fork?
No, your transactions are on the block chain, which will be used on the fork, they will be visible after the move; nothing will need to be done on your side.
22( Where can I read about the progress of Burst and news in general on the community?
There is no finer place than https://www.burstcoin.ist/
23( What are the communities for Burst and the central website?
Main website: https://www.burst-coin.org/
Reddit: https://www.reddit.com/burstcoin and https://www.reddit.com/burstcoinmining/
Burstforum.net: https://www.burstforum.net/
Getburst forum: https://forums.getburst.net/
Official Facebook channel: https://m.facebook.com/groups/398967360565392
(these are the forums that are known to be supporting the current Dev Team)
Other ways to talk to the community:
Discord: https://discordapp.com/invite/RPhpjVv
Telegram (General): https://t.me/burstcoin
Telegram (Mining): https://t.me/BurstCoinMining
24( When will Burst partner up with a company?
Burst is a currency, the USD does not ‘partner up’ with a company, the DEV team will not partner up and give over to special interests.
25( Why is the DEV team anonymous?
They prefer anonymity, as it allows them to work without constant scrutiny and questions unless they wish to engage, plus the aim is for Burst to become a major contender, and this brings issues with security. They will work and produce results, they owe you nothing and if you cannot see the vision they provide then please do not ‘invest’ for short term gain.
26( When moon/Lambo/$100/make me rich?
My crystal ball is still broken, come back to the FAQ later for answer (seriously, this is a coin to hold, if you want to day-trade, good luck to you)
27( How can I better educate myself and learn about Dymaxion?
Read about the Dymaxion here: https://www.reddit.com/burstcoin/wiki/dymaxion
28( My reads are slow, why?
There are many reasons for this, if your computer has a decent spec it’s likely due to USB3 hub issues, or plugging into a USB2 hub, but other reasons can be multiple plots in the same folder, but it’s best to visit the mining subreddit. They can help more than an simple FAQ https://www.reddit.com/burstcoinmining/
29( I have a great idea for Burst (not proof of stake related)?
Awesome! Please discuss with the DEV team on discord https://discordapp.com/invite/RPhpjVv
(Please be aware that this is a public forum, you need to find who to ask/tell)
30( I have a great idea for Burst (Proof of stake related)?
No. if you want a POS, find a POS coin. On the tangle which is being implemented a POS/POW/POC coin can be created, but BURST will always be POC mined. You are welcome to implement a proof of stake coin on this!
31( Will the Dev team burn any coins?
Burst is not an ICO, so any coins will need to be bought to be burnt. You are welcome to donate, but the DEV team have no intention of burning any coins, or increasing the coin cap.
32( When will there be an IOS wallet?
IOS wallet is completed; we are waiting for it to go on the app store. Apple is the delaying factor.
33( Why do overlapping plots matter?
Plots are like collections of lottery tickets (and if only one ticket could win). Having 2 copies is not useful, and it means that you have less coverage of ‘all’ the possible numbers. It’s not good, avoid.
34( My local wallet used to run, I synchronised it before and now it says ‘stopped’. when I start it, it stops after a few seconds, what should I do?
I suggest that you change the database type to portable MariaDB (on Qbundle, at the top, ‘Database’ select, ‘change database’) and then re-import the database from scratch (see 35)
35( Synchronising the block chain is slow and I have the patience of a goldfish. What can I do?
On Qbundle , ‘Database’ select ‘Bootstrap chain’ and make sure the CryptoGuru repository is selected, then ‘start Import’ this will download and quickly stuff the local database (I suggest Portable MariaDB, see 34) (lol, loop)
36( What will the block reward be next month/will the block rewards run out in 6 months?
https://www.ecomine.earth/burstblockreward/ Rewards will carry on into 2026, but transaction fees will be a bigger % by then, and so profitable mining will continue.
37( How can I get started with Burst (wallet/mining/everything) and I need it in a video
https://www.youtube.com/watch?v=LJLhw37Lh_8 Watch and be enlightened.
38( Can I mine on multiple machines with the same account?
Yes, if you want to pool mine this can be done (but be prepared for small issues like reported size being incorrect. Just be sure to keep question 33 in mind.)
39( Why do some of my drives take forever to plot?
Most likely they are SMR drives, it’s best to plot onto another SSD and then move the finished plot/part of a plot across to the SMR drive as this is much quicker. SMR drives are fine on the read, just random writes that are terrible.
So plot an SMR drive quickly, plot to a non SMR or better still SSD drive, in as big a chunk as possible (fewer files better) and move. a version of Xplotter, called Splotter, can do this easily.
https://github.com/NoParamedic/SPlotter
40( I have a great idea; why not get listed on more exchanges!!
Exchanges list coins because of 2 reasons:
  1. Clients email and REQUESTING Burst and provide details like:
    i. https://www.burst-coin.org/information-for-exchanges
  2. The coin pays (often A LOT, seriously we’ve been asked for 50 BTC)
I suggest you speak with your exchange and ask ‘when will they offer Burst?’
41( Do you have a roadmap?
https://www.burst-coin.org/roadmap
42( Why is the price of Burst going up/down/sideways/looping through time?
The price of burst is still quite dependent upon Bitcoin, meaning that if Bitcoin gains, the value of Burst gains, if Bitcoin drops then Burst also drops. If there is news for Burst then we will see something independent of Bitcoin moving. Variations can be because of people buying in bulk or selling in bulk. There are also ‘pump and dump’ schemes that we detest, that can cause spikes in price that have nothing to do with news or Bitcoin, just sad people taking advantage of others.
43( Where is the best place to go with my mining questions?
https://www.reddit.com/burstcoinmining/
or https://t.me/BurstCoinMining
44( What hardware do you advise me to buy, is this computer good?
See question 43 for specific questions on hardware, it depends on so many variables. The ‘best’ in my opinion is a 36 bay Supermicro storage server, usually they have dual 6-core CPU’s and space for 36 drives. No USB cables, plotting and mining monster, anything else, DYOR.
45( Where do you buy your hard drives?
I have bought most from EBay in job lots, and some refurbished drives with short warranties. Everything else I have bought, from Amazon.
46( Can I mine on my Google drive/cloud based storage?
In short: no. If you want to try, and get to maybe 1 TB and then find that your local connection isn’t fast enough, or that shortly after, your account is blocked for various reasons. Please be my guest.
47( Can I mine on my NAS?
Some you can mine with the NAS (if it can run the miner, it can scan locally) but generally they’re not very fast. good for maybe 16 TB? Having a plot on a NAS and mining from another computer depends on the network speed between the NAS and scanning computer. I believe you can scan about 8 TB (maybe a bit more) and keep the scan times to within acceptable, but YMMV.
48( How can I set up a node?
No need to set up a node, just set up a wallet (version 2.0.4) or Qbundle (2.2) and it will do the rest
49( Are the passphrases secured?
I’ll leave the effort to a few people to show how secure a 12-word passphrase is: https://burstforum.net/topic/4766/the-canary-burst-early-warning-system Key point: brute forcing it will be around 13,537,856,339,904,134,474,012,675,034 years.
50( I logged into my account (maybe with a different burst ID) and see no balance!!
I have dealt with this very issue multiple times, and there are only 3 options:
  1. You have typed in the password incorrectly
  2. You have copy-pasted the password incorrectly
  3. You are trying to log into a ‘local wallet’ which the block chain has not finished updating
The last one generally leaves the burst ID the same, but old balances will show. No, this is not a security problem, and yes, windows loves to add spaces after the phrase you enter when copied, and that space is important in getting to your account.
51( Are there channels for my language?
Telegram:
Spanish: https://t.me/burstcoin_es
German: https://t.me/Burstcoinde
Italian: https://t.me/BurstCoinItalia
Forum:
Spanish: https://burst-coin.es/index.php/forum/index
Discord:
Spanish: https://discordapp.com/invite/RaaGna9
Bulgarian: https://discord.gg/r4uzTd
(there are others, please contact me to put up)
52( I am mining in a pool, and it says that my effective capacity is lower than I actually have, why?
  1. If you've not been mining for >48 hours, or just added additional capacity, it will take time.
  2. The value fluctuates (normally, +-5% but can be up to 10% at times)
  3. Read on the ‘Quick info’ tab about adjusting your deadline to compensate for changes i. revisit once a month for best results
  4. If you have overlapping plots it will also be lower so be aware of this (see question 33)
53( What pool should I join?
First of all, read question 9, after you have understood that it depends on the size (and how patient you are) select from the following list: https://www.ecomine.earth/burstpools/
54( What miner to use?
I use Blago’s miner, there are many out there but Blago’s works for me on CPU mining, it can be found in Qbundle.
55( What Wallet to use (I use windows)?
Qbundle: https://github.com/PoC-Consortium/Qbundle/releases/ guide: https://burstwiki.org/wiki/QBundle
56( What Wallet to use (Linux)?
https://package.cryptoguru.org/ for Debian and Ubuntu, for Mac. read:
https://www.ecomine.earth/macoswalletinstallguide/
57( Will i need to 'replot' after POC2 (second fork) happens?
No, there will be a tool which will optimise, but it is not CPU intensive (it basically re-shuffles your plot) and is just IO intensive. You do not need to replot.
TurboPlotter and https://github.com/PoC-Consortium/Utilities/tree/mastepoc1to2.pl are tools that will/can be used to actuate optimization, but PLEASE wait with optimization until after the hard fork.
58( Will the transaction fee always be 1 burst?
No, dynamic fees are coming in the next fork.
submitted by dan_dares to burstcoin [link] [comments]

Bitcoin dev IRC meeting in layman's terms (2016-01-14)

Once again my attempt to summarize and explain the weekly bitcoin developer meeting in layman's terms. Link to last summarisation
Disclaimer
Please bear in mind I'm not a developer so some things might be incorrect or plain wrong. There are no decisions being made in these meetings, but since a fair amount of devs are present it's a good representation. Copyright: Public domain

Logs

Main topics

Versionbits

background

BIP 9 Currently softforks have been done by the isSuperMajority mechanism, meaning when 95% of the last 1000 blocks have a version number higher than X the fork is deployed. A new way of doing this is currently being worked on and that uses all bits of the version number, appropriately being called versionbits. So instead of a fork happening when the version is larger than (for example) 00000000011 (3), a fork happens when (for example) the 3rd bit is up (so 00100000011). This way softforks can be deployed simultaneous and independent of each other.

meeting comments

Morcos is volunteering to take over championing this proposal as CodeShark and Rusty are busy on other things. He'll review both implementations and then decide on which implementation he'll base his work upon. He notes that if non-core implementations are trying to do something else (and are using nVersion for their signaling) while segregated witness is being deployed, not conflicting will be important so users of other versions can also support segregated witness. If there's an agreement with this approach it's necessary that versionbits is ready before the segregated witness deployment. jtimon has some suggestions to make the implementation less complicated and more flexible.

meeting conclusion

Morcos will champion the new reference implementation for BIP9: Versionbits.

Status of segregated witness

background

Segregated witness changes the structure of transactions so that the signatures can be separated from the rest of the transactions. This allows for bandwidth savings for relay, pruning of old signatures, softforking all future script changes by introducing script versions and solves all unintentional forms of malleability. During the last scaling bitcoin conference Pieter Wuille presented a way of doing this via a softfork, and proposed increasing the maximum amount of transactions in a block by discounting signature data towards the total blocksize. Segregated witness is part of the capacity increase roadmap for bitcoin-core. More detailed explanations: - By Pieter Wuille at the San Francisco bitcoin developer meetup (more technical) - By Andreas Antonopoulos in the let's talk bitcoin podcast (less technical)

meeting comments

Segnet, the testnet for segregated transactions, will be going to it's 3rd version soon. Luke-Jr has assigned all the segregated witness BIPs to a 14x range. Currently there are 4 BIPs: 141, 142, 143 and 144.

Status of 0.12 bitcoin-core release

background

Bitcoin Core 0.12 is scheduled for release around February and introduces a lot of fixes and improvements. (release notes) There's a release candidate 0.12rc1 available at https://bitcoin.org/bin/bitcoin-core-0.12.0/test/

meeting comments

Luke-Jr feels PR's #7149, #7339 and #7340 should have been in 0.12, but are now really late and possibly impractical to get in. For gitian builders: 0.12rc1's osx sig attach descriptor fails due to a missing package (that's not actually needed). Rather than using the in-tree descriptor, use the one from #7342. This is fixed for rc2. "fundrawtransaction" and "setban" should be added to the release notes. At some point it makes more sense to document these commands elsewhere and link to it in the release notes, as they've become very lengthy. Wumpus thinks the release notes have too much details, they're not meant to be a substitute for documentation.

meeting conclusion

Close PR #7142 as it's now part of #7148 Everyone is free to improve on the release notes, just submit a PR.

consensus code encapsulation (libconsensus)

background

Satoshi wasn't the best programmer out there, which leaves a pretty messy code. Ideally you'd have the part of the code that influences the network consensus separate, but in bitcoin it's all intertwined. Libconsensus is what eventually should become this part. This way people can more easily make changes in the non-consensus part without fear of causing a network fork. This however is a slow and dangerous project of moving lots of code around.

meeting comments

jtimon has 4 libconsensus related PRs open, namely #7091 #7287 #7311 and #7310 He thinks any "big picture branch" will be highly unreadable without merging something like #7310 first. The longest "big picture branch" he currently has is https://github.com/jtimon/bitcoin/commits/libconsensus-f2 He'll document the plan and "big picture" in stages: 1. have something to call libconsensus: expose verifyScript. (Done) 2. put the rest of the consensus critical code, excluding storage in the same building package (see #7091) 3. discuss a complete C API for libconsensus 4. separate it into a sub-repository Wumpus notes he'd like to start with 3 as soon as possible as an API would be good to guide this.

meeting conclusion

review #7091 #7287 #7311 and #7310

Locktime PRs

background

BIP 68 Consensus-enforced transaction replacement signaled via sequence numbers. BIP 112 CHECKSEQUENCEVERIFY. BIP 113 Median time-past as endpoint for lock-time calculations. In short: BIP 68 changes the meaning of the sequence number field to a relative locktime. BIP 112 makes that field accessible to the bitcoin scripting system. BIP 113 enables the usage of GetMedianTimePast (the median of the previous 11 blocks) from the prior block in lock-time transactions.

meeting comments

We need to make a choice between 2 implementations, namely #6312 and #7184. PR #7184 is a result of the CreateNewBlock optimisations not being compatible with #6312. jtimon thinks it could be merged relatively soon as #7184 is based on #6312 which has plenty of testing and review.

meeting conclusion

Close #6312 in favor of #7184. Morcos will fix the open nits on #7184 btcdrak will update the BIP-text

Participants

wumpus Wladimir J. van der Laan btcdrak btcdrak morcos Alex Morcos jtimon Jorge Timón Luke-Jr Luke Dashjr MarcoFalke Marco Falke jonasshnelli Jonas Schnelli cfields Cory Fields sipa Pieter Wuille kanzure Bryan Bishop droark Douglas Roark sdaftuar Suhas Daftuar Diablo-D3 Patrick McFarland 

Comic relief

19:54 wumpus #meetingstop 19:54 wumpus #stopmeeting 19:54 btcdrak haha 19:54 MarcoFalke #closemeeting 19:54 wumpus #endmeeting 19:54 lightningbot` Meeting ended Thu Jan 14 19:54:26 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 
submitted by G1lius to Bitcoin [link] [comments]

[Reupload][Tutorial] Install Armory Wallet 0.96.4 on Fedora Workstation 29

note: I had to reupload this because reddit is banning my original account for no reason. I appealed but I thought maybe someone wanted to have this content online.
Armory is a very cool open source bitcoin wallet for the power user. You can do neat things with it, read here: https://www.bitcoinarmory.com/
Disclaimer: follow these steps at your own risk. I am not responsible for any damage / loss of funds you might face for following or not following correctly my instructions here. I may have made a typo somewhere or be wrong so do your own research and learn for yourself what I am doing at each step, and what consequences may have for you, at your own risk. These instructions may be wrong somewhere. It worked for me, it doesn't mean it has to work for you.
Requirements for this tutorial:
We are going to build the code from source.
Install dependencies.
I followed these instructions to find the equivalent Fedora packages:
Open the terminal app and run this command:
sudo dnf install git nano qt qt-devel python-devel libtool pyqt4 pyqt4-devel lmdb swig 
And more python packages that I had to install:
sudo pip install twisted qt4reactor psutil 
Importing the signing key to verify the software
Install KGPG to easily manage keys.
sudo dnf install kgpg 
Go to
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x8C5211764922589A
and copy paste the code below the title from
-----BEGIN PGP PUBLIC KEY BLOCK-----
to
-----END PGP PUBLIC KEY BLOCK-----
both included. Then open KGPG from terminal with
kgpg -k 
and click 'Import Key...' > Clipboard > Ok . You should see a confirmation message. Double check the info and close the dialog.
Repeat the process with this other key:
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xA4FC919E85C595BA
You can verify both keys are mentioned at the Armory webpage.
Clone and compile the code plus some edits
Before, we installed some dependencies that are named differently than the equivalent Ubuntu/Debian package specified at the Armory documentation. The build process fails for Fedora as the name for the dependency during checks won't match the Fedora version. There's this pull request addressing that, but the code is not part of any release yet.
So the fastest workaround (maybe a bit dirty) was to edit the build config file and correct the name for my Fedora install. Let's begin.
Clone the Armory repository
git clone https://github.com/goatpig/BitcoinArmory.git 
Enter the BitcoinArmory dir
cd BitcoinArmory 
Switch to release code
git checkout 'v0.96.4' 
Verify commit signature
git tag -v 'v0.96.4' 
you should see the following message:
> object fee1f91a3137ef1056e15cc606a186b0e508f84c > type commit > tag v0.96.4 > tagger goatpig  1522530739 +0200 > > v0.96.4 > gpg: Signature made Sat 31 Mar 2018 11:12:19 PM CEST > gpg: using RSA key 8C5211764922589A > gpg: Good signature from "goatpig (Offline signing key for Armory releases) " > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the owner. > Primary key fingerprint: 745D 707F BA53 968B DF63 AA8D 8C52 1176 4922 589A 
if it looks the same, everything is ok.
Edit the file 'Makefile' file with
gedit Makefile 
And click the three dot menu > Find and Replace...
Configure the options as follows:
https://i.imgur.com/hpS01Kd.png
Click Replace All and close.
Go back to the terminal and run the following commands in order from inside the BitcoinArmory dir. Wait for the previous one to finish before running the next one:
./autogen.sh 
...
./configure 
...
make 
if everything finishes without error you are all done! Run this to start Armory:
python ./ArmoryQt.py 
you are all set. Please let me know if I missed something.
submitted by RedditShadowbangedMe to Bitcoin [link] [comments]

GUIDE: How to use Electrum with your Ledger Nano S on Tails 3.7

TL;DR

The official guide doesn’t provide useful info. Moreover, Tails has some restrictions for security and privacy reasons. This guide uses only well-documented features of Tails and doesn’t require any additional stuff (usb-sticks, other OS etc).

Preconditions

This guide assumes both features are activated on Tails Greeter every startup:

Problem

Tails is based on Debian GNU/Linux. And to detect the Ledger Nano S we need the python library provided by python3-btchip package. This package is available on sid, but it depends on python3 (>= 3.6~). Tails has python 3.5.3 installed. So…

Solution

… we’ll install btchip-python library by means of the python’s pip tool. To make this library persistently installed you should activate Tails “Dotfiles” Persistence feature and restart Tails.
I don’t know how to configure the pip tool to go through Tor. So this guide suggests to use GitHub repositories.
Open terminal in the Home folder and download git repositories:
git clone https://github.com/LedgerHQ/btchip-python.git git clone --recursive https://github.com/trezocython-hidapi.git 
Open root terminal and enter the following commands:
apt update apt install --install-recommends python3-pip apt install cython3 apt install libusb-1.0-0-dev apt install libudev-dev/stretch-backports pip3 install --user /home/amnesia/cython-hidapi/ pip3 install --user /home/amnesia/btchip-python/ cp -a ~/.local/ /live/persistence/TailsData_unlocked/dotfiles/ chown -R amnesia /live/persistence/TailsData_unlocked/dotfiles/.local/ chgrp -R amnesia /live/persistence/TailsData_unlocked/dotfiles/.local/ 
Restart Tails.

Results

To check installation open the folder in terminal:
ls ~/.local/lib/python3.5/site-packages/ 

Usage

Don’t forget every login update udev rules.
Start electrum… and get an error:
Firmware version (or “Bitcoin” app) too old for Segwit support.
Actually the Electrum 3.0.6 is too old for the latest Ledger Nano S firmware. So download Electrum-3.1.3.tar.gz from the official site and untar it. In the electrum directory, run: 'python3 electrum'.
Your feedback is welcome.
HODL!
EDIT_1: fixed typo.
EDIT_2: libudev-dev=237-3~bpo9+1 libudev-dev/stretch-backports
EDIT_3: works for Electrum-3.2.2 on Tails 3.8 as well.
submitted by hebasto to Electrum [link] [comments]

Tested, step-by-step tutorial to run a 21 Bitcoin Computer as a virtual machine

Many thanks to ButtcoinEE and ecafyelims for initial pointers, but if I understood correctly, both users said they hadn't actually tried it themselves. So here comes a tutorial based on something I actually tried. Best of all: You don't even need a Raspberry Pi! We'll run it as a virtual machine.
The first step is to get a Debian 8 (Jessie) installation up and running. You might want to install that inside a VMWare/Virtualbox machine. I'll be using Vagrant here ( https://www.vagrantup.com/ ) which makes it easy to manage virtual machines like that and already has a Debian 8 image in the catalog. So get Vagrant for your platform and then do something like this:
vagrant init ARTACK/debian-jessie vagrant up 
You should now be able to SSH into the machine:
vagrant ssh 
Now that we have a Debian up and running, let's first get some packages we'll need later:
sudo su # become root apt-get update apt-get upgrade apt-get install apt-transport-https git cython3 python3-setuptools 
Add the 21 Debian repository:
echo "deb https://apt.21.co stable main" > /etc/apt/sources.list.d/twentyone.list apt-get update 
It'll complain about a missing GPG key, but you can just ignore that.
We should be able to do 'apt-get install two1' now, but it complains about a missing package 'python3-sha256'. The reason for that is probably, that we are doing this on a x86 architecture, where the packages are slightly different than the Raspberry Pi's ARM architecture. So we'll just manually install the package and have it ignore the dependency errors:
aptitude download two1 dpkg -i two1_1.0.0-1_all.deb 
Now let it try to fetch as many of the dependencies as possible:
apt-get -f install 
And try to install again (had to do this again, not sure why):
dpkg -i two1_1.0.0-1_all.deb 
The 21 binary should now be available:
which 21 # => /usbin/21 
Before we can run it, we'll need that missing python-256 package. We can install it manually from https://github.com/cloudtools/sha256 :
git clone https://github.com/cloudtools/sha256.git cd sha256 python3 setup.py sdist python3 setup.py install 
Now try to get a status report via the 21 tool:
21 status 
If everything worked out, you should see something like:
You do not have a Bitcoin wallet configured. Let's create one. Press any key ... 
and will also be asked to pick a username for a 21.co account.
All 21 Bitcoin computers are networked together into a VPN using the tool ZeroTier ( https://www.zerotier.com ). Let's also set that up:
wget https://download.zerotier.com/dist/zerotier-one_1.1.0_amd64.deb dpkg -i zerotier-one_1.1.0_amd64.deb 
We'll have to extract the credentials for the specific network they use from 21's zerotier package:
mkdir credentials cd credentials wget https://apt.21.co/pool/z/ze/zerotier-one_1.1.0-1_armhf.deb ar x zerotier-one_1.1.0-1_armhf.deb tar xf data.tar.xz cp valib/zerotier-one/updates.d/ZeroTierOneInstaller-linux-armv6l-1_1_0 /valib/zerotier-one/updates.d/ 
Before we join the network, we need to lock down our machine. That's actually a bit tricky, as these Vagrant images aren't really designed with security in mind, but rather only to be used for local testing. I think it should be enough to do:
passwd vagrant rm /home/vagrant/.ssh/authorized_keys 
Note that you won't be able to use 'vagrant ssh' any longer afterwards, as we just deleted the standard Vagrant key-based login. You'll have to use 'ssh [email protected]' instead. Now we are ready to join the network:
wget https://gist.githubusercontent.com/balajis/6d495bb40fb157a58677/raw/21-join.py python3 21-join.py python3 21-join.py # might have to try this twice as well ifconfig zt0 # will show your new IP within the VPN 
The 21 tools have a concept of both an on-chain balance and an off-chain balance - the latter being managed by 21's server. You can deposit to your on-chain balance, but currently the only way to increase the off-chain balance is by mining or by receiving payments from others. Without the mining chip it's therefore a bit tricky to increase that off-chain balance. I hear that a feature request is being considered, to allow moving funds from on-chain to off-chain.
That's all! If you want to give it a shot, you should probably move fast, as 21 has some DRM in the works, as per this comment: https://www.reddit.com/Bitcoin/comments/3tnjz7/tutorial_turn_your_35_raspberry_pi_into_a_21/cx7tih3 .
This was brought to you by https://coinado.io/ - cloud torrenting for command line fans. Check us out - we are also big on micropayments! ;-)
submitted by coinadoio to Bitcoin [link] [comments]

[Tutorial] Install Armory Wallet 0.96.4 on Fedora Workstation 29

Armory is a very cool open source bitcoin wallet for the power user. You can do neat things with it, read here: https://www.bitcoinarmory.com/
Disclaimer: follow these steps at your own risk. I am not responsible for any damage / loss of funds you might face for following or not following correctly my instructions here. I may have made a typo somewhere or be wrong so do your own research and learn for yourself what I am doing at each step, and what consequences may have for you, at your own risk. These instructions may be wrong somewhere. It worked for me, it doesn't mean it has to work for you.
Requirements for this tutorial:
We are going to build the code from source.
Install dependencies.
I followed these instructions to find the equivalent Fedora packages:
Open the terminal app and run this command:
sudo dnf install git nano qt qt-devel python-devel libtool pyqt4 pyqt4-devel lmdb swig 
And more python packages that I had to install:
sudo pip install twisted qt4reactor psutil 
Importing the signing key to verify the software
Install KGPG to easily manage keys.
sudo dnf install kgpg 
Go to
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x8C5211764922589A
and copy paste the code below the title from
-----BEGIN PGP PUBLIC KEY BLOCK-----
to
-----END PGP PUBLIC KEY BLOCK-----
both included. Then open KGPG from terminal with
kgpg -k 
and click 'Import Key...' > Clipboard > Ok . You should see a confirmation message. Double check the info and close the dialog.
Repeat the process with this other key:
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xA4FC919E85C595BA
You can verify both keys are mentioned at the Armory webpage.
Clone and compile the code plus some edits
Before, we installed some dependencies that are named differently than the equivalent Ubuntu/Debian package specified at the Armory documentation. The build process fails for Fedora as the name for the dependency during checks won't match the Fedora version. There's this pull request addressing that, but the code is not part of any release yet.
So the fastest workaround (maybe a bit dirty) was to edit the build config file and correct the name for my Fedora install. Let's begin.
Clone the Armory repository
git clone https://github.com/goatpig/BitcoinArmory.git 
Enter the BitcoinArmory dir
cd BitcoinArmory 
Switch to release code
git checkout 'v0.96.4' 
Verify commit signature
git tag -v 'v0.96.4' 
you should see the following message:
> object fee1f91a3137ef1056e15cc606a186b0e508f84c > type commit > tag v0.96.4 > tagger goatpig  1522530739 +0200 > > v0.96.4 > gpg: Signature made Sat 31 Mar 2018 11:12:19 PM CEST > gpg: using RSA key 8C5211764922589A > gpg: Good signature from "goatpig (Offline signing key for Armory releases) " > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the owner. > Primary key fingerprint: 745D 707F BA53 968B DF63 AA8D 8C52 1176 4922 589A 
if it looks the same, everything is ok.
Edit the file 'Makefile' file with
gedit Makefile 
And click the three dot menu > Find and Replace...
Configure the options as follows:
https://i.imgur.com/hpS01Kd.png
Click Replace All and close.
Go back to the terminal and run the following commands in order from inside the BitcoinArmory dir. Wait for the previous one to finish before running the next one:
./autogen.sh 
...
./configure 
...
make 
if everything finishes without error you are all done! Run this to start Armory:
python ./ArmoryQt.py 
you are all set. Please let me know if I missed something.
edit: cd git dir.
submitted by AmbitiousSpeed0 to Bitcoin [link] [comments]

GRS development status (facts)

From the GRS discord:
BCG came and people discoverd that is has the same qualities as VTC
But then not premined and ASIC resistent Then people started looking for more ASIC resistent coins and came to GRS VTC has a great dev team and now people are seeing that GRS has developed a lot further then VTC Then this list came with GRS
First coin with SegWit
Only coin that has succesfully ported Bitcoin Armory
Only coin that have over 40 Electrum servers.
One of the few coins that have a Ubuntu PPA available
One of the few coins that is officially maintained by the Bitcoin Debian packaging team
Only coin that has succesfully ported Multibit HD We have 10 different Android wallets. Most struggle to have just 1.
We have 9 different Blackberry wallets. Most dont have any.
One of the few coins that have an ios wallet
We have over 10 different desktop wallets
Only coin that has ported Samourai and thus succesfully implemented BIP147. You can work with payment channels with Groestlcoin.
One of the few coins where you can play with OP_HOLD, RBF and other new features
Only coin that has ported electrum client to java
One of the few coins that has ported rushwallet.com
Only coin with over 100 repositories with developed work.
Only coin that is capable of sending GRS over SMS
Only coin that has wallets which can use NFC tags as encryption key.
Only coin that has ported Msigna.
Only coin that has ported sentinel.
Only coin that is still being compiled with Visual Studio (like Satoshi himself did)
We got now also 2 ios wallets
We got 1 more android and 1 more blackberry wallet
We have a working testnet
We got a testnet android and blackberry wallet
We got a chrome os wallet
We got 2 new webwallets
We got tor support for our electrum since january 2017
We got 40 tor servers
VTC jumped from 0.60 usd to 4usd in two weeks (my guess is partially thanks to the btc fork)
GRS is now only 0.12usd And all these have SW, LN and AS
TLDR: GRS is very well developed.
submitted by johnturtle to CryptoCurrency [link] [comments]

Electrum was recently added to the main repositories in Debian testing. If you'd like to see it added to Ubuntu in the next release, read this.

I noticed Electrum recently got included in the "Testing" repository in Debian GNU/Linux, which is excellent news. This means that Debian users will most probably get Electrum in the next Debian stable release, but most importantly, all its derivatives will too. That's a lot of people!
To have an idea of the significance of any package making it into Debian, consider this graphic of the Debian derivatives family.
As Bitcoin user we need to have as many stable, secure, trusted platforms as possible to use our wallet software. GNU/Linux is often mentioned in security threads here. Trisquel and Debian are my choice distributions, but I know many use Ubuntu too.
Ubuntu will eventually also get this software packaged and available by default to all its users, with feature + security updates. Unfortunately there is a schedule for automatic inclusion of new Debian packages in Ubuntu, and the arrival of Electrum into Debian Testing happened after the "Debian import freeze" date.
I filed a bug report to request a sync anyways, hoping for an exception, so Electrum makes it ASAP into Ubuntu.
Please don't login to Launchpad to post "I'd love to see this" or "me too!" comments. I'll be monitoring this thread and adding any appropriate and constructive reasons mentioned. Hit the "This bug affects me too" while logged in if you must.
tl;dr: I believe it's important to make an exception to the Debian import freeze (as noted in the bug report) and sync Electrum into Ubuntu ASAP, if you can think of others I'd like to hear them here.
submitted by magicfab to Bitcoin [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]

Groestlcoin development questions.

I have some questions regarding this circulating sales pitch about Groestlcoin.
  1. First coin with SegWit
  2. Only coin that has succesfully ported Bitcoin Armory
  3. Only coin that have over 40 Electrum servers.
  4. One of the few coins that have a Ubuntu PPA available
  5. One of the few coins that is officially maintained by the Bitcoin Debian packaging team
  6. Only coin that has succesfully ported Multibit HD We have 10 different Android wallets. Most struggle to have just 1.
  7. We have 9 different Blackberry wallets. Most dont have any.
  8. One of the few coins that have an ios wallet
  9. We have over 10 different desktop wallets
  10. Only coin that has ported Samourai and thus succesfully implemented BIP147. You can work with payment channels with Groestlcoin.
  11. One of the few coins where you can play with OP_HOLD, RBF and other new features
  12. Only coin that has ported electrum client to java
  13. One of the few coins that has ported rushwallet.com
  14. Only coin with over 100 repositories with developed work.
  15. Only coin that is capable of sending GRS over SMS
  16. Only coin that has wallets which can use NFC tags as encryption key.
  17. Only coin that has ported Msigna.
  18. Only coin that has ported sentinel.
  19. Only coin that is still being compiled with Visual Studio (like Satoshi himself did)
  20. We got now also 2 ios wallets
  21. We got 1 more android and 1 more blackberry wallet
  22. We have a working testnet
  23. We got a testnet android and blackberry wallet
  24. We got a chrome os wallet
  25. We got 2 new webwallets
  26. We got tor support for our electrum since january 2017
  27. We got 40 tor servers
10, 17, 18 - For those that are less tech savvy, what are the implications of porting Samourai, Msigma and sentinel?
15 - What is the app that allows to send groestlcoin via SMS?
Thanks.
submitted by johnturtle to groestlcoin [link] [comments]

Bitcoin dev IRC meeting in layman's terms (2016-01-14)

Once again my attempt to summarize and explain the weekly bitcoin developer meeting in layman's terms. Link to last summarisation
Disclaimer
Please bear in mind I'm not a developer so some things might be incorrect or plain wrong. There are no decisions being made in these meetings, but since a fair amount of devs are present it's a good representation. Copyright: Public domain

Logs

Main topics

Versionbits

background

BIP 9 Currently softforks have been done by the isSuperMajority mechanism, meaning when 95% of the last 1000 blocks have a version number higher than X the fork is deployed. A new way of doing this is currently being worked on and that uses all bits of the version number, appropriately being called versionbits. So instead of a fork happening when the version is larger than (for example) 00000000011 (3), a fork happens when (for example) the 3rd bit is up (so 00100000011). This way softforks can be deployed simultaneous and independent of each other.

meeting comments

Morcos is volunteering to take over championing this proposal as CodeShark and Rusty are busy on other things. He'll review both implementations and then decide on which implementation he'll base his work upon. He notes that if non-core implementations are trying to do something else (and are using nVersion for their signaling) while segregated witness is being deployed, not conflicting will be important so users of other versions can also support segregated witness. If there's an agreement with this approach it's necessary that versionbits is ready before the segregated witness deployment. jtimon has some suggestions to make the implementation less complicated and more flexible.

meeting conclusion

Morcos will champion the new reference implementation for BIP9: Versionbits.

Status of segregated witness

background

Segregated witness changes the structure of transactions so that the signatures can be separated from the rest of the transactions. This allows for bandwidth savings for relay, pruning of old signatures, softforking all future script changes by introducing script versions and solves all unintentional forms of malleability. During the last scaling bitcoin conference Pieter Wuille presented a way of doing this via a softfork, and proposed increasing the maximum amount of transactions in a block by discounting signature data towards the total blocksize. Segregated witness is part of the capacity increase roadmap for bitcoin-core. More detailed explanations: - By Pieter Wuille at the San Francisco bitcoin developer meetup (more technical) - By Andreas Antonopoulos in the let's talk bitcoin podcast (less technical)

meeting comments

Segnet, the testnet for segregated transactions, will be going to it's 3rd version soon. Luke-Jr has assigned all the segregated witness BIPs to a 14x range. Currently there are 4 BIPs: 141, 142, 143 and 144.

Status of 0.12 bitcoin-core release

background

Bitcoin Core 0.12 is scheduled for release around February and introduces a lot of fixes and improvements. (release notes) There's a release candidate 0.12rc1 available at https://bitcoin.org/bin/bitcoin-core-0.12.0/test/

meeting comments

Luke-Jr feels PR's #7149, #7339 and #7340 should have been in 0.12, but are now really late and possibly impractical to get in. For gitian builders: 0.12rc1's osx sig attach descriptor fails due to a missing package (that's not actually needed). Rather than using the in-tree descriptor, use the one from #7342. This is fixed for rc2. "fundrawtransaction" and "setban" should be added to the release notes. At some point it makes more sense to document these commands elsewhere and link to it in the release notes, as they've become very lengthy. Wumpus thinks the release notes have too much details, they're not meant to be a substitute for documentation.

meeting conclusion

Close PR #7142 as it's now part of #7148 Everyone is free to improve on the release notes, just submit a PR.

consensus code encapsulation (libconsensus)

background

Satoshi wasn't the best programmer out there, which leaves a pretty messy code. Ideally you'd have the part of the code that influences the network consensus separate, but in bitcoin it's all intertwined. Libconsensus is what eventually should become this part. This way people can more easily make changes in the non-consensus part without fear of causing a network fork. This however is a slow and dangerous project of moving lots of code around.

meeting comments

jtimon has 4 libconsensus related PRs open, namely #7091 #7287 #7311 and #7310 He thinks any "big picture branch" will be highly unreadable without merging something like #7310 first. The longest "big picture branch" he currently has is https://github.com/jtimon/bitcoin/commits/libconsensus-f2 He'll document the plan and "big picture" in stages: 1. have something to call libconsensus: expose verifyScript. (Done) 2. put the rest of the consensus critical code, excluding storage in the same building package (see #7091) 3. discuss a complete C API for libconsensus 4. separate it into a sub-repository Wumpus notes he'd like to start with 3 as soon as possible as an API would be good to guide this.

meeting conclusion

review #7091 #7287 #7311 and #7310

Locktime PRs

background

BIP 68 Consensus-enforced transaction replacement signaled via sequence numbers. BIP 112 CHECKSEQUENCEVERIFY. BIP 113 Median time-past as endpoint for lock-time calculations. In short: BIP 68 changes the meaning of the sequence number field to a relative locktime. BIP 112 makes that field accessible to the bitcoin scripting system. BIP 113 enables the usage of GetMedianTimePast (the median of the previous 11 blocks) from the prior block in lock-time transactions.

meeting comments

We need to make a choice between 2 implementations, namely #6312 and #7184. PR #7184 is a result of the CreateNewBlock optimisations not being compatible with #6312. jtimon thinks it could be merged relatively soon as #7184 is based on #6312 which has plenty of testing and review.

meeting conclusion

Close #6312 in favor of #7184. Morcos will fix the open nits on #7184 btcdrak will update the BIP-text

Participants

wumpus Wladimir J. van der Laan btcdrak btcdrak morcos Alex Morcos jtimon Jorge Timón Luke-Jr Luke Dashjr MarcoFalke Marco Falke jonasshnelli Jonas Schnelli cfields Cory Fields sipa Pieter Wuille kanzure Bryan Bishop droark Douglas Roark sdaftuar Suhas Daftuar Diablo-D3 Patrick McFarland 

Comic relief

19:54 wumpus #meetingstop 19:54 wumpus #stopmeeting 19:54 btcdrak haha 19:54 MarcoFalke #closemeeting 19:54 wumpus #endmeeting 19:54 lightningbot` Meeting ended Thu Jan 14 19:54:26 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 
submitted by G1lius to btc [link] [comments]

RetroShare Feature List

Information directly from Team Retroshare DevBlog:
RetroShare Features:
HowTo test RetroShare
ChatServer / IntroServer for making new Friends
RetroShare on Embedded Devices
From Unofficial Wiki
RetroShare on FreenodeIRC
RetroShare on Twitter
RetroShare on GitHub and SourceForge
Plugin Structure
How to Contribute
If you have questions, feel free to ask!
submitted by cavebeat to retroshare [link] [comments]

Installing software outside of the package manager

Hello all.
I've recently taken an interest in Bitcoins (/bitcoins), and so I've naturally decided to try them out using Bitcoin's own bitcoin-qt wallet software. Unfortunately, debian-qt only appears to be available in the sid (unstable) repositories and I'm running wheezy (stable), so I've had to download the binaries from bitcoin.org and work it out from there.
I've pretty much got everything working, but I'm not sure if there's a preferred standard way to do what I'm doing. I have done a fair bit of research, and it has lead me to believe that /opt or /uslocal is the best place to home user installed programs.
Pretty much, the steps I've taken so far are: 1. Download the tarball from bitcoin.org. 2. Verify it to make sure it's authentic and all that jazz. 3. Extract it (which leaves me with a directory called bitcoin-0.8.6-linux). 4. Find the 64 bit binaries in bitcoin-0.8.6-linux (which are located at bitcoin-0.8.6-linux/bin/64/) and copy them to /uslocal/bin.
That's what I've done as far as installation goes. I have, of course, set up a menu in the application menu for XFCE that leads to the bitcoin-qt executable that's in /uslocal/bin, but other than that, that's all. One issue that is remaining is that in the applications menu, the application for the bitcoin wallet has no icon. Now, I know how to implement icons, but I'm not sure where the standard place for housing icons/pngs is on debian/linux systems, so I haven't bothered yet.
So, my main question is: have I done this right? Is this the standard way to do things, as far as installing outside of the package manager goes?
All of the software I have previously installed has been through the package manager, so this is new territory to me. I'd love to hear your advice -- thank you for reading. :)
submitted by Mint_Apple_Pie to debian [link] [comments]

[FOR HIRE] Junior Devops Engineer / Infrastructure Automation / Linux Geek

Hello there!
I am a twenty-something GNU/Linux geek, currently looking for a job. I am looking for a position
At the moment, these are my core competences:
  1. General Linux administration (Mostly ubuntu/debian: repositories, package, apt-pinning, cron-jobs etc)
  2. Shell scripting
  3. Python/Perl scripting (basic-medium)
  4. Iptables/OpenVPN (basic firewalling and/or natting)
  5. Familiar with Apache2/LigHTTPd (very willing to learn nginx)
  6. Docker (basic application dockerization, programmatically spawn/stop/delete containers)
  7. Mailserver setup (Postfix/Dovecot)
  8. Can use GNU Emacs, Vim, nano. Don't have strong preferences.
  9. Experience developing fodeploying to Herok and Dokku
  10. Other stuff (golang, Java, python/flask, C language and some other stuff)
  11. Git (enough to know the difference between push and pull, why rebasing is good for you and how to use bisect)
EU-resident, but very willing to work for US-based companies as long as I can be paid via wire transfer (bitcoin might be an option).
My ideal position would be "Junior Cloud Engineer". I would like to learn and grow as a Devops Engineer, using Amazon AWS or Google Cloud Platform.
submitted by znpy to devopsjobs [link] [comments]

Debian Package Add Repository Kali Linux 2020.3 - YouTube How to Create .deb Packages for Debian, Ubuntu and Linux ... Debian ver. 10 - Installing packages - Part 1 - Using unofficial repository Debian: Is it possible/safe to install packages from an ... The Debian sources list generator! How to setup debian repository's!

The libbitcoin/secp256k1 repository is forked from bitcoin-core/secp256k1 in order to control for changes and to incorporate the necessary Visual Studio build. The original repository can be used directly but recent changes to the public interface may cause build breaks. The --enable-module-recovery switch is required. Debian/Ubuntu. Libbitcoin requires a C++11 compiler, currently minimum GCC ... Debian Bitcoin Team , Jonas Smedegaard (u) std-ver 3.9.5 VCS Git . versions o-o-stable 2.0-2.2. binaries . libbitcoin-dev (0 bugs: 0, 0, 0, 0) Bitcoin toolkit library for asynchronous apps - development headers; libbitcoin0 (0 bugs: 0, 0, 0, 0) Bitcoin toolkit library for asynchronous apps; libbitcoin0-dbg (0 bugs: 0, 0, 0, 0) Bitcoin toolkit library for asynchronous apps - debugging symbols ... Packages. Introductory notes; View package lists; Search package directories; Search the contents of packages; Introductory notes. All packages that are included in the official Debian distribution are free according to the Debian Free Software Guidelines.This assures free use and redistribution of the packages and their complete source code. This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug. This package will soon be part of the auto-protobuf transition. vcswatch reports that the current version of the package is not in its VCS. Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be ...

[index] [34296] [14119] [16549] [30630] [11946] [1430] [51480] [35597] [19232] [26702]

Debian Package Add Repository Kali Linux 2020.3 - YouTube

Unix & Linux: Why did adding the Debian testing repository create so many package dependencies? Helpful? Please support me on Patreon: https://www.patreon.co... how to fix repository in Debian 9 Stretch Solucion A Los Repositorios De Debian 9 Stretch Estable Zatiel Stay Connected:→ https://goo.gl/Y9FrtP Donate Through Paypal.Me → https://t.co ... Welcome To Tom Hat Channel Today going on how to Add Repo Debian Package Kali Linux 2020.3 attackers any time online so be safe dear brothers and sisters OK ... How to setup debian repository's! ... Debian Package Management #1 - APT Basics - Duration: 17:37. highvoltage 8,881 views. 17:37. The APT Package Manager in Debian and Ubuntu - Duration: 12:04 ... Unix & Linux: Debian: Is it possible/safe to install packages from an older version of the repository? Helpful? Please support me on Patreon: https://www.pat...

#