Debian -- Details of source package bitcoin in sid

Whonix lead developer wants to maintain a debian repository for the Monero GUI for two years. Comment on the proposal!

Whonix lead developer wants to maintain a debian repository for the Monero GUI for two years. Comment on the proposal! submitted by Rehrar to Monero [link] [comments]

Best Dedicated Server in Miami

https://hostingultraso.com/dedicated-serveMiami

Business and Technology around Miami

This is the city in Florida and the main economical and financial hub. It has emerged as one of the strongest international business community. The leading business trend makes it so special and popular among other countries in the South USA. The technology is too sound to suit the business culture and modern lifestyle here.
Hosting Ultraso is looking to provide a best-dedicated server hosting service to enhance the performance of business websites in a more convincing way.
Our long tail of dedicated servers spread everywhere across the globe including more than 119 countries.

Why do you need a Dedicated Server in Miami?

As your business expands more with higher traffic each day, it unfolds the demand for a dedicated hosting. A dedicated server can make your website continue to grow with more clients engagement and have a huge success.
Our dedicated server in Miami is so way configured that it can easily meet your business plans and ideas. We are providing ample hardware resources with our dedicated server in Miami and a smarter CPanel loaded with advance software packages and tools which are fully customizable.
We are providing the finest security management technology with our dedicated server in Miami to protect all resources from intrinsic cyber-attacks and the dedicated IP address keeps the website free from SEO issues. The latest IPMI or Intelligent Platform Monitoring Interface monitors the server’s physical health frequently.
Our assurance is for the lowest latency rate and high-speed rendering. Our data centers are effectively managing the load balancing.
We have an expert technical team well trained and skilled to help you in your problems and without any delay serve you all 24/7.

Different Operating Systems that we provide in Miami

What are the different Dedicated Servers we provide in Miami?

We are mainly providing unmanaged dedicated servers that needed to be self-managed and on some special business needs, we do provide a managed dedicated server.
We have demand for our Linux dedicated server, Windows dedicated server, and an Unmetered dedicated server. We are here to make you avail a cheap dedicated server as well.

Configurations of our Dedicated Servers

Our dedicated server in Miami has smart and super-fast Intel Xeon E5 processors with a 1 Gbps 10 TB bandwidth capacity. There are RAMs with 16 to 128 GB capacities. The hard drives are SSD SATA based on several storage capacities. For more details, you can check the configuration server link on our website.
We are providing an extra free IP address with the chargeless installation. We do support both IPV4 and IPV6 address formats. We are providing the option for the clustering of servers.

The benefits you get from Hosting Ultraso with our Dedicated Server in Miami

Buy a dedicated server from us and become the lucky getter of amazing benefits with an affordable dedicated hosting plan.
submitted by Hosting_Ultraso1 to u/Hosting_Ultraso1 [link] [comments]

Best Dedicated Server in Germany

https://hostingultraso.com/dedicated-serveGermany

Why Is Dedicated Server Needed?

Dedicated Servers are one of the strong and powerful servers that can be a very good and effective server hosting solution for different businesses regardless of business size and scale. Dedicated hosting comes with various options including Customized Cpanel loaded with highly efficient tools and services with various resources and security management technology that will fully be dedicated to you. No sharing will be done like Shared servers.

Business and Technology In Germany

This is a Western Europe Country with states and cities that are professionally rich as business centers and with the trending business culture, Germany has become one of the world’s largest business hubs. From every aspect, Germany has participated in its large business tradition and now continuously growing and evolving.
The main aim of Hosting Ultraso is to build a strong bond with this business culture and be the local international hosting provider of yours. We have our dedicated servers spread over 119 cities all around the world including cities Frankfurt, Dusseldorf, Berlin, etc in Germany. There are large and well-managed data centers spread in Europe and Dusseldorf in Germany is having a highly efficient Data Center. The load balancing capability of the data center in Dusseldorf and dedicated servers in Germany gives any website the first rendering speed.

Why Choose a Dedicated server in Germany?

Germany maintains a rich tradition in its business. Depending upon the size and scale of any business in Germany, the Dedicated servers provided by us in Germany are well capable of giving services that will be solely dedicated to the business. Germany Dedicated Servers are so built with enhanced technology and configuration that is suitable for any business in Germany.
All highly optimized and configured software and hardware resources come with a dedicated server hosting plan. In addition, the Control panel facility loaded with quality tools and services and skilled technical team will be dedicated to you. Everything will not be shared as it happens in the case of Shared servers. A unique IP address will keep you safe and secure which will not let your website face any SEO issue as well.
The business website with dedicated servers in Germany will run fluently and smoothly with enhanced customer engagement to the website which will turn in large business growth.
There will be low latency rates and that we are 100% sure about giving you the most satisfaction.
We have a skilled and smart technical team and the other management team is there to help you anyway at any point in time all 24 hours. We have several dedicated servers hosting plans like Cheap server hosting, a Basic dedicated server plan, Advanced dedicated servers, unmanaged dedicated hosting, etc. It’s entirely up to you for choosing any plan that is suitable for your business and whatever be it our assurance comes with all the plans you will choose.

What are the Types Of Operating System Provided in Germany?

What Are The Different Dedicated Servers We Provide in Germany?

Germany has more than 28 optimized and top performed dedicated servers. They are in high demand too and various businesses are opting to pre-book our servers and we highly recommend you too.

Dedicated Servers In Germany

The Dedicated hosting in Germany includes different Intel Xeon, Ryzen, Atom versions, and core series.
Intel Xeon D-1520 2.2 GHz 4 cores, Intel Xeon E3-1230 v6 3.5 GHz 4 cores, Intel Xeon E5-2609 v3 1 GHz 6 cores, Intel Atom S1260 2 GHs 2 Cores, etc are the processor’s option available in Germany data centers.
You will be having different RAMS as well like 16,32,64 GB DDR3 and DDR4. Bandwidth will be in the range of 1 Gbps unmetered fair usage to 1 Gbps 5 TB and several other options. Hard Drives have different capacities and have HDD SATA and SSD SATA labeling that performs best in the current market. For more details, Do view our dedicated server configuration page on our website.
Two types of IP addresses we provide are IPV4 and IPV6 and bundling or clustering different servers to make a full new package server is also easy for you. You will get from us an additional IP address which is fully unique for every website and that will be absolutely free of cost even we do not charge for setup. Since we mainly provide the unmanaged dedicated servers in Germany, therefore, you need to do all the basic levels of the setup yourself or in that case, you should have an expert technical team to handle all the management of the servers.

What Are The Benefits Of Buying Dedicated Servers in Germany From Hosting Ultrso?

Hosting Ultraso provides all suitable plans for buying Dedicated Servers in Germany. There are budget Dedicated servers available that can give you effective configuration maintaining high quality and well-built too. The Dedicated hosting plan we provide, can give your business website the extra boost by more customers engagements and they are long-lasting in nature. Choosing dedicated servers in Germany that we provide will open up a new horizon definitely for your extended business.
  1. Additional IP: You will be having an extra IP address or Internet Protocol address for your site. Every active website has a unique IP.
  2. Managed Dedicated Servers: There are both basic and advanced management services, We have for you depending on what you need.
  3. Guarantee for Money-Back: We provide you a money-back guarantee on the time left on your subscription if you are not satisfied with our service that we care for your money too.
  4. Bitcoin Payment Availability: We accept all types of payments including Bitcoin payment.
  5. 24/7 Support team: Our technical team is there to help you in all possible ways and will be active all 24 hours a day.
  6. IPMI Access facility: Our Dedicated servers in Germany have IPMI (Intelligent Platform Management Interface) with each of them
    https://hostingultraso.com/dedicated-serveGermany
submitted by Hosting_Ultraso1 to u/Hosting_Ultraso1 [link] [comments]

[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]

When the bubble pops, those with strong fundamentals rise.

When the crypto space is a bubble, it's a total lemon market: hardly any buyers can tell what is and isn't a good investment, and ICOs and altcoin scammers sell off their tokens in exchange for good coins, while others also hold the coins with fundamentals. This is largely because the value of these currencies are so unpredictable during the bubble (people invest in coins because they think it'll go up in value, not because of any fundamentals) and more importantly: there are a bunch of new people who don't understand the value proposition of decentralized cryptocurrencies.
When the market is crashing, like it has been, the new people slowly leave the scene, stop buying, and sell. This leaves the people who DO understand the fundamental value proposition of cryptocurrencies, and are here for different reasons, beyond just trying to get rich. It leaves the passionate cypherpunks, crypto-anarchists and liberty minded people.
They know cryptocurrencies aren't easier or cheaper to use, or even really better as a currency just yet: their value fluctuates so much its impractical to use for most things. They instead see that they have utility in being subversive and permissionless, and hope that one day scaling, usability, and price fluctuations are solved - and that is why they hodl.
Of all the coins, the one that best serves the real value proposition of decentralized cryptocurrencies is undoubtedly Monero. Every other coin is either poorly designed and suffer from a variety of issues, such as the miners tragedy of the commons, not fungible/private, or rely on trust.
Around the peak of the bubble, I posted this: https://www.reddit.com/xmrtradecomments/7o9t58/if_youre_a_monero_hodler_dont_even_worry_this_is/
Monero was #14 in marketcap and I eluded to the idea that it was falling behind because of the irrational and inexperienced buyers, and that it gains in marketcap as the market crashes.
We're now at #10, with only a few shitcoins still ahead of us, and others only because people haven't realized yet that fungible cryptocurrencies are a requirement to be a real currency, which is what gives it value, and in turn what secures the blockchain.
We're near our ATH when compared against our price in Bitcoin.
This is great. It doesn't totally confirm what I was saying: that Monero's ratio to market cap increases during a crash, but it does provide some supporting evidence.
We haven't even released the fork that adds multisig, bulletproofs, and subaddresses. the Debian package project, while almost done isn't yet added to Debian (or Tails), and the hardware wallet isn't yet finished on a commercial level. There's a ton of other stuff, despite the end of the crypto mania phase, still being developed for Monero, including my Annularis project which is an open source silkroad project. Me and a few others have been working hard on it, and soon we'll have a nice surprise. :)
submitted by Vespco to xmrtrader [link] [comments]

Homelab collective ressources post!

Hey guys!
I'm fairly new to this sub and to having a home lab in general and I found this community to be so kind and helping, I wanted to give back what I've learned. I'm seeing a lot of questions asked around on improvements and on what to do with x extra hardware so I thought it would be nice to have a thread to regroup that.
 
I'll put here some stuff I gathered and the most common questions I've seen, feel free to contribute and i'll update the post along.
 
Latest Additions
 
Homelab Dashboard
Posts about dashboards have been growing lately and here are some of the best that were kind enough to provide us with their sources.
User Screenshot Source
yours truly http://imgur.com/a/GhCNH https://github.com/Gabisonfire/dashboard-q
lastditchefrt http://i.imgur.com/5zQdao4.png https://github.com/d4rk22/Network-Status-Page
_SleepingBag_ http://i.imgur.com/Ql9ZM4W.png https://github.com/jsank/homelabdash
NiknakSi https://niknak.org/extras/sysinfo TBA
DainBramaged http://imgur.com/jYNlUEQ https://github.com/gordonturneBigBoard
michaelh4u https://i.imgur.com/XkZwMKj.png https://github.com/michaelh4u/homelabfrontpage
spigotx http://imgur.com/a/1zMht https://github.com/spigotx/HomeLab2
SirMaster https://nicko88.com/ https://github.com/dashbad/plex-server-status
yourofl10 http://imgur.com/a/AyROa TBA
TheBobWiley http://imgur.com/a/oU6d3 https://github.com/TheBobWiley/ManageThis-LandingPages
0110010001100010 http://i.imgur.com/iwtQcsL.jpg https://github.com/danodemano/monitoring-scripts
mescon & SyNiK4L https://i.imgur.com/gqdVM6p.jpg https://github.com/mescon/Muximux
ak_rex http://i.imgur.com/a/RJkrT https://github.com/ak-rex/homelab-dashboard
 
Or build yours from scratch: PRTG API, ELK, Grafana, freeboard, JumpSquares
 
Some other resources: Custom Monitoring Scripts by 0110010001100010
 
Credits to apt64 for his original post
= Pi specific =
 
= Download Automation =
 
= Virtualization =
 
= Monitoring =
 
= Media Center =
 
= Remote access =
 
= VOIP =
 
= Networking =
 
= File Servers/Storage/RAID =
 
= Cameras =
 
= Documentation =
 
= Dynamic DNS =
 
= Backup =
 
= Creating network diagrams =
 
= Guides =
 
= Misc =
 
That's all I could come up with on top of my head + some research, passing over to you guys so we can get a nice complete list!
 
Let's try and stick with free(or mostly) softwares, let me know if you guys feel otherwise.
submitted by Gabisonfire to homelab [link] [comments]

Monero Subreddit Stats from last year.

Submissions Comments
Total 994 49530
Rate (per day) 2.73 135.74
Unique Redditors 582 8080
Combined Score 161184 231580

Top Submitters' Top Submissions

  1. 5300 points, 33 submissions: dEBRUYNE_1
    1. Monero GUI 0.12.0.0 "Lithium Luna" Megathread - Download links, instructions for upgrading, guide on how to get started, and guides to resolve common issues (missing a transaction / zero balance, freezing / buggy GUI, transaction stuck as pending, and GUI using all bandwidth) (386 points, 833 comments)
    2. [Reminder] monero is not the appropriate place to discuss the BTC/BCH debate (319 points, 73 comments)
    3. General information regarding the upcoming scheduled network upgrade and a call for community action (305 points, 223 comments)
    4. GUI v0.12.2.0 released! (299 points, 243 comments)
    5. Announcement - Proof-of-Work tweak and a note on key reuse (295 points, 250 comments)
    6. GUI v0.12.3.0 (with direct Ledger support) released! (280 points, 386 comments)
    7. Bitfinex reduces Monero withdrawal fees from 0.04 to 0.0001 XMR! (272 points, 9 comments)
    8. Poloniex also reduces Monero withdrawal fees to 0.0001 XMR! (220 points, 17 comments)
    9. Preliminary information thread regarding the scheduled protocol upgrade of October 18 (214 points, 208 comments)
    10. CLI v0.12.3.0 released! (195 points, 78 comments)
  2. 4228 points, 24 submissions: OsrsNeedsF2P
    1. Saying you don't need privacy because you have nothing to hide is like saying you don't need free speech because you have nothing to say. It's a right to everyone - It's a right to you, me, and even Mark Zuckerberg. (581 points, 138 comments)
    2. The official Fortnite Merch Store is accepting exclusively Monero as a cryptocurrency payment option... (445 points, 80 comments)
    3. Can we stop being assholes to newbies? (359 points, 94 comments)
    4. With all this Monero "is less untraceable than previously thought" FUD, let's all remember that huge fucking bounty of $$$ for anyone who can trace the origin of one of the devs transactions.. (343 points, 131 comments)
    5. Ever wanted to know how Monero is still around today? Well now you don't have to! This post has it all =D (297 points, 66 comments)
    6. Coinmarketcap shows Freewallet as a Monero wallet. Guys, whatever you do.. Don't use Freewallet. It's a scam. (286 points, 93 comments)
    7. SEC wants decentralized exchange creators to register as exchanges. Lol (182 points, 111 comments)
    8. "Please do your part in demanding exchanges to lower their XMR withdraw fee. I am submitting a complaint to Coinex who currently charge 0.04 XMR" - [x-post from /xmrtrader] (169 points, 43 comments)
    9. Can we get some appreciation for the people who maintain the Monero packages on Arch Linux? There are so many available, and every single one I've checked either make the package from source or validate the checksum. Amazing work <3 (156 points, 19 comments)
    10. [WARNING] DROPIL recently made a post announcing support for Monero. MOVE YOUR FUNDS if you used them!!! (119 points, 5 comments)
  3. 3954 points, 13 submissions: KnifeOfPi2
    1. Did John McAfee just sell all of his Monero?? (1277 points, 107 comments)
    2. We need to stop thinking about Monero as a “privacy coin.” (511 points, 200 comments)
    3. Selsta and I just completed the first Ledger-to-Ledger mainnet transactions ever. He sent me 0.1 XMR and I sent 0.4 XMR back. (482 points, 103 comments)
    4. Monero network hashrate just hit 1GH/s! (463 points, 166 comments)
    5. An upcoming Monero project: Render the entire blockchain. Here's a selection of blocks that we've done so far, in an early stage. (224 points, 31 comments)
    6. In Stunning Move, Bitmain Announces It's Launching A Doorstopper Business (193 points, 48 comments)
    7. Another red flag for X Wallet: The source code is incomplete. (190 points, 63 comments)
    8. MONERO IS DEAD! LONG LIVE MONERO! (155 points, 25 comments)
    9. Lithium Luna GUI released! (118 points, 66 comments)
    10. Cake Wallet - introducing Zendesk support! (100 points, 13 comments)
  4. 2421 points, 22 submissions: SamsungGalaxyPlayer
    1. Kasisto POS in 22 seconds (366 points, 76 comments)
    2. "Kudelski Security completed their [bulletproof] report. They found only a few minor issues that are trivial to correct, and no major issues." Overall, a huge win for Monero, bulletproofs, and privacy. Full report will be published soon. (338 points, 100 comments)
    3. Network upgrade scheduled for block 1544555 on 28 March (210 points, 56 comments)
    4. Fungibility is determined by the LOWEST common denominator of privacy, NOT the highest. Monero absolutely excels here. (103 points, 37 comments)
    5. [Discussion] Move to a Fixed Ringsize (102 points, 85 comments)
    6. The Monero Malware Response workgroup website is up! Direct people whose machines have been compromised here! (101 points, 22 comments)
    7. MoneroV: A Trap Laid for Monero Users? (93 points, 45 comments)
    8. Want to get the GUI point release faster? Help translate! (91 points, 18 comments)
    9. Introducing the Breaking Monero Series! (86 points, 26 comments)
    10. ShapeShift is moving to a membership model and will require personal information soon (83 points, 86 comments)
  5. 2295 points, 16 submissions: pinkphloid
    1. Cake Wallet - OPEN SOURCE - Here it is! (383 points, 167 comments)
    2. Our Monero wallet called CAKEWALLET for iOS is live! Please check the link to the Apple App Store below. (347 points, 379 comments)
    3. [MANDATORY UPDATE] Cake Wallet Version 3.0.9 - Network Upgrade Ready! (227 points, 19 comments)
    4. [UPDATE] Cake Wallet version 3.1.4, now with XMR.TO for exchanging XMR to BTC! (133 points, 15 comments)
    5. Cake Wallet - 10,000 unique downloads! (132 points, 29 comments)
    6. Thank for the positive feedback on Cake Wallet! (127 points, 62 comments)
    7. The new Cake Wallet Update version 3.0.1 is out now! (120 points, 50 comments)
    8. [UPDATE] CAKE WALLET 3.1.1 with Monero v0.13.0.4 and other stuff (118 points, 32 comments)
    9. Cake Wallet - UPDATE! (108 points, 75 comments)
    10. CAKE WALLET - new version live now with NEW FEATURES! (102 points, 97 comments)
  6. 2042 points, 16 submissions: Rehrar
    1. Core Team Announcement (344 points, 45 comments)
    2. Project FOSS (212 points, 37 comments)
    3. Write down your seed (200 points, 93 comments)
    4. Bulletproof audit needs some more funding. Details in the comments. (170 points, 55 comments)
    5. Extremely thorough introduction to Monero by cypherperro. Take a look. (122 points, 18 comments)
    6. Defcon Monero Village Update and Summary (116 points, 22 comments)
    7. MRL Bulletproof audit FFS request (115 points, 30 comments)
    8. I, rehrar,went on a YouTube show to talk about Morono (113 points, 28 comments)
    9. Fund the fundings! (107 points, 16 comments)
    10. The anonimal appreciation thread! (107 points, 21 comments)
  7. 1978 points, 15 submissions: Vespco
    1. Edward Snowden on Bitcoin Interview 2018 (at 50 minutes, he says that a traceable public ledger is a bigger problem then scalability) (362 points, 88 comments)
    2. Putting this on my invoices seems like a good way for me to promote Monero, give my customers a discount, & help me acquire more Monero. (325 points, 101 comments)
    3. It's fun to be a part of the Monero economy! (179 points, 26 comments)
    4. Honest Government Ad | Anti Encryption Law (178 points, 32 comments)
    5. Jeez, not much real conversation in here. Just junky news links. (129 points, 76 comments)
    6. The New York State Department of Financial Services just approved the trading of privacy-protecting cryptocurrency. | Coin Center (124 points, 11 comments)
    7. A good way to explain the importance of fungibility to the laymen: Bitcoin Roulette (99 points, 45 comments)
    8. Why I love Botnet & Browser Mining. (86 points, 39 comments)
    9. This needs more praise & attention: An Open Source, Client Side JS implementation that makes monero multisig fairly easy. Github link in comments. (82 points, 14 comments)
    10. Could we get even more cryptographers researching for Monero? (77 points, 31 comments)
  8. 1846 points, 14 submissions: SarangNoether
    1. Bulletproofs: let's raise some funds! (295 points, 94 comments)
    2. January monthly report from Sarang Noether (237 points, 39 comments)
    3. Bulletproofs: The Paper Strikes Back (153 points, 32 comments)
    4. July monthly report from Sarang Noether (142 points, 20 comments)
    5. March monthly report from Sarang Noether (129 points, 22 comments)
    6. August monthly report from Sarang Noether (122 points, 33 comments)
    7. February monthly report from Sarang Noether (119 points, 27 comments)
    8. Sarang is up for three more months! (107 points, 30 comments)
    9. October monthly report from Sarang Noether (102 points, 26 comments)
    10. September monthly report from Sarang Noether (99 points, 25 comments)
  9. 1470 points, 4 submissions: TheFuzzStone
    1. "I do not have any Bitcoin" (1182 points, 96 comments)
    2. Fluffypony at Consensus 2018 (134 points, 33 comments)
    3. Time for Monero "killers"! :-) (91 points, 34 comments)
    4. XMR.RU-report (March) (63 points, 14 comments)
  10. 1468 points, 5 submissions: philkode
    1. Overstock.com accepting Monero (and ETH, BCH, LTC, DASH) (499 points, 36 comments)
    2. Happy 4th Birthday Monero! 🎂🎉🎁 (455 points, 62 comments)
    3. Monero has been added to Debian unstable repo as of yesterday. (321 points, 52 comments)
    4. “Unhackable” BitFi wallet just got hacked (xpost /cryptocurrency) (130 points, 41 comments)
    5. X Wallet to App Store (Soon™) (63 points, 67 comments)

Top Commenters

  1. dEBRUYNE_1 (3762 points, 1243 comments)
  2. KnifeOfPi2 (3311 points, 347 comments)
  3. OsrsNeedsF2P (3189 points, 505 comments)
  4. fluffyponyza (3027 points, 272 comments)
  5. gingeropolous (2554 points, 320 comments)
  6. cryptochangements34 (2522 points, 261 comments)
  7. SarangNoether (2269 points, 185 comments)
  8. SamsungGalaxyPlayer (2108 points, 221 comments)
  9. john_alan (1993 points, 218 comments)
  10. smooth_xmr (1944 points, 279 comments)

Top Submissions

  1. Did John McAfee just sell all of his Monero?? by KnifeOfPi2 (1277 points, 107 comments)
  2. Paypal shares your personal data with over 600 companies! That's why we need Monero! by 0xf3e (1184 points, 146 comments)
  3. "I do not have any Bitcoin" by TheFuzzStone (1182 points, 96 comments)
  4. Found In Warsaw - Don't Buy Monero: Cryptocurrencies harm the banking system and can weaken the government by SecretApe (1114 points, 110 comments)
  5. Monero transactions are about to get 80% cheaper and faster. by WillMTB (1056 points, 120 comments)
  6. Bye bye ASICs by Swericor (874 points, 380 comments)
  7. Upvote if you would like to see @fluffyponyza as a guest on Joe Rogan Podcast by xmr_karnal (840 points, 44 comments)
  8. All right, my cat had kittens and I just realised one of them has Monero-like logo on its head 😂😂 by JNKO266 (817 points, 79 comments)
  9. Credit, where credit is due! by Experts-say (796 points, 53 comments)
  10. Yesterday I thought it might be fun to create some vintage crypto posters for a handful of coins. This was the first one I came up with. Bonus points if you spot similarities from an old movie by Beemoe4 (722 points, 67 comments)

Top Comments

  1. 495 points: mr670wl's comment in Found In Warsaw - Don't Buy Monero: Cryptocurrencies harm the banking system and can weaken the government
  2. 474 points: kieranc001's comment in Monero Zero looks like a scam, can you please confirm?
  3. 380 points: deleted's comment in Found In Warsaw - Don't Buy Monero: Cryptocurrencies harm the banking system and can weaken the government
  4. 356 points: deleted's comment in Ledger Hardware Wallet - Monero integration : some news #6
  5. 331 points: last_of_the_romans's comment in Monero transactions are about to get 80% cheaper and faster.
  6. 323 points: svenroy777's comment in "I do not have any Bitcoin"
  7. 311 points: deleted's comment in Did John McAfee just sell all of his Monero??
  8. 255 points: KnifeOfPi2's comment in Monero transactions are about to get 80% cheaper and faster.
  9. 237 points: live9free1or1die's comment in Banning privacy coins because of terrorism/drugs/laundering is like banning people from being allowed to have sex in privacy because pedophiles also like privacy.
  10. 203 points: fluffyponyza's comment in Botnets are Ruining the Integrity of the Monero Network
Generated with BBoe's Subreddit Stats (Donate)
Inspired by a post I found on /Pivx by turtleflax.
submitted by OsrsNeedsF2P to Monero [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]

Let's build an army of Ethereum nodes!

Hi everyone!
I ran into Ethereum several months ago while reading about bitcoin and the blockchain and was quite impressed by some videos explaining the project (most of them by Vitalik himself). During this time I've tried to educate myself on this breakthrough technology. And at this point, I'd like to get a little more involved. I think that one easy way to contribute to this fascinating project is by running a full Ethereum node, so let me share some stuff of my experience of setting up an Ethereum node on Raspberry Pi 3.
While doing some research about the best Ethereum client for my raspberry Pi 3 I realized that pretty much there are no ARM nodes on the network (according to ethernodes.org). Shouldn't be precisely the opposite? ARM devices such as Raspberry Pi have a good performance, are cheap and power-efficient.
I looked into "EthEmbedded" [1] (great project, by the way) but it is mainly focused on Geth and Eth clients and you need to run the Ethereum clients manually. It's built on top of Ubuntu mate (and we need to keep things light). Besides, I was looking something more Flash & Play :-).
So, I compiled Parity from source on my raspberry Pi 3 (which is the most efficient Ethereum client out there [2]) and gave it a try. I was really surprised with the overall performance and thought that it would be great to get an Ethereum node up and running easiest way possible.
So, I built a custom Raspbian image which runs Parity as a boot up service and starts syncing the blockchain with no user interaction. This is what I got so far:
A custom [3] Raspbian [4] image with Ethcore Parity 1.3 [5] integrated. The image is generated using pi-gen [6] (plus a couple of files for Parity installation)
Some remarks:
Final thoughts:
I think there are several reasons to try to increase Ethereum ARM nodes in the coming months:
You can download the Custom Raspbian Image here:
http://www.ethraspbian.com/downloads/2016-09-09-ethraspbian.img.zip
For further installation instructions please visit:
https://github.com/diglos/pi-gen
Let me know your comments.
Let's do this. Mine is up and running :-)
TL;DR: If you want to contribute to the Ethereum network, get a Raspberry pi 3, install the OS image into your microSD card, connect the ethernet cable and power on your device. This is it, flash and play :-), you are already running an Ethereum node!
submitted by diglos76 to ethereum [link] [comments]

Headlines for week 06 of 2019

Listen to the Headlines for week 06

​Show notes for Security Endeavors Headlines for Week 5 of 2019
InfoSec Week 6, 2019 (link to original Malgregator.com posting)
The Zurich American Insurance Company says to Mondelez, a maker of consumer packaged goods, that the NotPetya ransomware attack was considered an act of cyber war and therefore not covered by their policy. According to Mondelez, its cyber insurance policy with Zurich specifically covered “all risks of physical loss or damage” and “all risk of physical loss or damage to electronic data, programs or software” due to “the malicious introduction of a machine code or instruction.” One would think that the language in the cyber insurance policy was specifically designed to be broad enough to protect Mondelez in the event of any kind of cyber attack or hack. And NotPetya would seem to fit the definition included in the cyber insurance policy – it was a bit of malicious code that effectively prevented Mondelez from getting its systems back up and running unless it paid out a hefty Bitcoin ransom to hackers. Originally, Zurich indicated that it might pay $10 million, or about 10 percent of the overall claim. But then Zurich stated that it wouldn't pay any of the claim by invoking a special “cyber war” clause. According to Zurich, it is not responsible for any payment of the claim if NotPetya was actually “a hostile or warlike action in time of peace or war.” According to Zurich, the NotPetya cyber attack originated with Russian hackers working directly with the Russian government to destabilize the Ukraine. This is what Zurich believes constitutes "cyber war." https://ridethelightning.senseient.com/2019/01/insurance-company-says-notpetya-is-an-act-of-war-refuses-to-pay.html
Reuters reports that hackers working on behalf of Chinese intelligence breached the network of Norwegian software firm Visma to steal secrets from its clients. According to investigators at cyber security firm Recorded Future, the attack was part of what Western countries said in December is a global hacking campaign by China’s Ministry of State Security to steal intellectual property and corporate secrets. Visma took the decision to talk publicly about the breach to raise industry awareness about the hacking campaign, which is known as Cloudhopper and targets technology service and software providers in order reach their clients.
https://www.reuters.com/article/us-china-cyber-norway-visma/china-hacked-norways-visma-to-steal-client-secrets-investigators-idUSKCN1PV141
A new vulnerability has been discovered in the upcoming 5G cellular mobile communications protocol. Researchers have described this new flaw as more severe than any of the previous vulnerabilities that affected the 3G and 4G standards. Further, besides 5G, this new vulnerability also impacts the older 3G and 4G protocols, providing surveillance tech vendors with a new flaw they can abuse to create next-gen IMSI-catchers that work across all modern telephony protocols.
This new vulnerability has been detailed in a research paper named "New Privacy Threat on 3G, 4G, and Upcoming5G AKA Protocols," published last year.
According to researchers, the vulnerability impacts AKA, which stands for Authentication and Key Agreement, a protocol that provides authentication between a user's phone and the cellular networks.The AKA protocol works by negotiating and establishing keys for encrypting the communications between a phone and the cellular network. Current IMSI-catcher devices target vulnerabilities in this protocol to downgrade AKA to a weaker state that allows the device to intercept mobile phone traffic metadata and track the location of mobile phones. The AKA version designed for the 5G protocol --also known as 5G-AKA-- was specifically designed to thwart IMSI-catchers, featuring a stronger authentication negotiation system But the vulnerability discovered last year allows surveillance tech vendors to create new models of IMSI-catchers hardware that, instead of intercepting mobile traffic metadata, will use this new vulnerability to reveal details about a user's mobile activity. This could include the number of sent and received texts and calls, allowing IMSI-catcher operators to create distinct profiles for each smartphone holder. https://www.zdnet.com/article/new-security-flaw-impacts-5g-4g-and-3g-telephony-protocols/
The Debian Project is recommending the upgrade of golang-1.8 packages after a vulnerability was discovered in the implementation of the P-521 and P-384 elliptic curves, which could result in denial of service and in some cases key recovery. In addition this update fixes two vulnerabilities in the “go get” command, which could result in the execution of arbitrary shell commands. https://www.debian.org/security/2019/dsa-4380
It is possible to trick user’s of the Evolution email application into trusting a phished mail via adding a forged UID to a OpenPGP key that has a previously trusted UID. It's because Evolution extrapolates the trust of one of OpenPGP key UIDs into the key itself. The attack is based on using the deficiency of Evolution UI when handling new identifiers on previously trusted keys to convince the user to trust a phishing attempt. More details about how the flaw works, along with examples are included in the article, which is linked in the show notes. Let’s take a minute to cover a bit of background on Trust Models and how validating identities work in OpenPGP and GnuPG:
The commonly used OpenPGP trust models are UID-oriented. That is, they are based on establishing validity of individual UIDs associated with a particular key rather than the key as a whole. For example, in the Web-of-Trust model individuals certify the validity of UIDs they explicitly verified.
Any new UID added to the key is appropriately initially untrusted. This is understandable since the key holder is capable of adding arbitrary UIDs to the key, and there is no guarantee that new UID will not actually be an attempt at forging somebody else's identity. OpenPGP signatures do not provide any connection between the signature and the UID of the sender. While technically the signature packet permits specifying UID, it is used only to facilitate finding the key, and is not guaranteed to be meaningful. Instead, only the signing key can be derived from the signature in cryptographically proven way.
GnuPG (as of version 2.2.12) does not provide any method of associating the apparent UID against the signature. In other words, from e-mail's From header. Instead, only the signature itself is passed to GnuPG and its apparent trust is extrapolated from validity of different UIDs on the key. Another way to say this is that the signature is considered to be made with a trusted key if at least one of the UIDs has been verified. https://dev.gentoo.org/~mgorny/articles/evolution-uid-trust-extrapolation.html
If you’re up for some heavy reading about manipulation and deceit being perpetrated by cyber criminals, it may be worth checking out a piece from buzzfeednews. It tells a woeful and dark tale that does not have a happy ending. A small excerpt reads: “As the tools of online identity curation proliferate and grow more sophisticated, so do the avenues for deception. Everyone’s familiar with the little lies — a touch-up on Instagram or a stolen idea on Twitter. But what about the big ones? Whom could you defraud, trick, ruin, by presenting false information, or information falsely gained? An infinite number of individual claims to truth presents itself. How can you ever know, really know, that any piece of information you see on a screen is true? Some will find this disorienting, terrifying, paralyzing. Others will feel at home in it. Islam and Woody existed purely in this new world of lies and manufactured reality, where nothing is as it seems.” https://www.buzzfeednews.com/article/josephbernstein/tomi-masters-down-the-rabbit-hole-i-go
Security researchers were assaulted by a casino technology vendor Atrient after responsibly disclosed critical vulnerabilities to them. Following a serious vulnerability disclosure affecting casinos globally, an executive of one casino technology vendor Atrient has allegedly assaulted the security researcher who disclosed the vulnerability at the ICE conference in London. The article covers the story of a vulnerability disclosure gone bad, one involving the FBI, a vendor with a global customer base of casinos and a severe security vulnerability which has gone unresolved for four months without being properly addressed. https://www.secjuice.com/security-researcher-assaulted-ice-atrient/
Article 13, the new European Union copyright law is back and it got worse, not better. In the Franco-German deal, Article 13 would apply to all for-profit platforms. Upload filters must be installed by everyone except those services which fit all three of the following extremely narrow criteria:
Available to the public for less than 3 years Annual turnover below €10 million Fewer than 5 million unique monthly visitors Countless apps and sites that do not meet all these criteria would need to install upload filters, burdening their users and operators, even when copyright infringement is not at all currently a problem for them. https://juliareda.eu/2019/02/article-13-worse/
Researchers from Google Project Zero evaluated Apple's implementation of Pointer Authentication on the A12 SoC used in the iPhone XS. There are bypasses possible, but the conclusion says it is still a worthwhile exploitation mitigation technique. Among the most exciting security features introduced with ARMv8.3-A is Pointer Authentication, a feature where the upper bits of a pointer are used to store a Pointer Authentication Code (PAC), which is essentially a cryptographic signature on the pointer value and some additional context. Special instructions have been introduced to add an authentication code to a pointer and to verify an authenticated pointer's PAC and restore the original pointer value. This gives the system a way to make cryptographically strong guarantees about the likelihood that certain pointers have been tampered with by attackers, which offers the possibility of greatly improving application security. There’s a Qualcomm white paper which explains how ARMv8.3 Pointer Authentication was designed to provide some protection even against attackers with arbitrary memory read or arbitrary memory write capabilities. It's important to understand the limitations of the design under the attack model the author describes: a kernel attacker who already has read/write and is looking to execute arbitrary code by forging PACs on kernel pointers.
Looking at the specification, the author identifies three potential weaknesses in the design when protecting against kernel attackers with read/write access: reading the PAC keys from memory, signing kernel pointers in userspace, and signing A-key pointers using the B-key (or vice versa). The full article discusses each in turn. https://googleprojectzero.blogspot.com/2019/02/examining-pointer-authentication-on.html
There is a dangerous, remote code execution flaw in the LibreOffice and OpenOffice software. While in the past there have been well documented instances where opening a document would result in the executing of malicious code in paid office suites. This time LibreOffice and Apache’s OpenOffice are the susceptible suites. The attack relies on exploiting a directory traversal flaw, identified as CVE-2018-16858, to automatically execute a specific python library bundled within the software using a hidden onmouseover event. To exploit this vulnerability, the researcher created an ODT file with a white-colored hyperlink (so it can't be seen) that has an "onmouseover" event to trick victims into executing a locally available python file on their system when placing their mouse anywhere on the invisible hyperlink. According to the researcher, the python file, named "pydoc.py," that comes included with the LibreOffice's own Python interpreter accepts arbitrary commands in one of its parameters and execute them through the system's command line or console. https://thehackernews.com/2019/02/hacking-libreoffice-openoffice.html
Nadim Kobeissi is discontinuing his secure online chat Cryptocat. The service began in 2011 as an experiment in making secure messaging more accessible. In the eight ensuing years, Cryptocat served hundreds of thousands of users and developed a great story to tell. The former maintainer explains on the project’s website that other life events have come up and there’s no longer available time to maintain things. The coder says that Cryptocat users deserve a maintained secure messenger, recommends Wire.
The Cryptocat source code is still published on GitHub under the GPL version 3 license and has put the crypto.cat domain name up for sale, and thanks the users for the support during Cryptocat's lifetime. https://twitter.com/i/web/status/1092712064634753024
Malware For Humans is a conversation-led, independent documentary about fake news, big data, electoral interference, and hybrid warfare. Presented by James Patrick, a retired police officer, intelligence analyst, and writer, Malware For Humans covers the Brexit and Trump votes, the Cambridge Analytica scandal, Russian hybrid warfare, and disinformation or fake news campaigns.
Malware For Humans explains a complex assault on democracies in plain language, from hacking computers to hacking the human mind, and highlights the hypocrisy of the structure of intelligence agencies, warfare contractors, and the media in doing so. Based on two years of extensive research on and offline, Malware For Humans brings the world of electoral interference into the light and shows that we are going to be vulnerable for the long term in a borderless, online frontier. A complete audio companion is available as a separate podcast, which can be found on iTunes and Spotify as part of The Fall series and is available for free, without advertisements. https://www.byline.com/column/67/article/2412
Security Endeavors Headlines is produced by SciaticNerd & Security Endeavors with the hope that it provides value to the wider security community. Some sources adapted for on-air readability.
Special thanks to our friends at malgregator dot com, who allow us to use their compiled headlines to contribute to show’s content. Visit them at Malgregator.com.
Additional supporting sources are also be included in our show notes
More information about the podcast is available at SecurityEndeavors.com/SEHL
Thanks for listening and we'll see you next week!
submitted by SecurityEndeavors to SEHL [link] [comments]

Subreddit Stats: Monero top posts from 2018-01-03 to 2019-01-02 13:47 PDT

Period: 364.01 days
Submissions Comments
Total 994 49530
Rate (per day) 2.73 135.74
Unique Redditors 582 8080
Combined Score 161184 231580

Top Submitters' Top Submissions

  1. 5300 points, 33 submissions: dEBRUYNE_1
    1. Monero GUI 0.12.0.0 "Lithium Luna" Megathread - Download links, instructions for upgrading, guide on how to get started, and guides to resolve common issues (missing a transaction / zero balance, freezing / buggy GUI, transaction stuck as pending, and GUI using all bandwidth) (386 points, 833 comments)
    2. [Reminder] monero is not the appropriate place to discuss the BTC/BCH debate (319 points, 73 comments)
    3. General information regarding the upcoming scheduled network upgrade and a call for community action (305 points, 223 comments)
    4. GUI v0.12.2.0 released! (299 points, 243 comments)
    5. Announcement - Proof-of-Work tweak and a note on key reuse (295 points, 250 comments)
    6. GUI v0.12.3.0 (with direct Ledger support) released! (280 points, 386 comments)
    7. Bitfinex reduces Monero withdrawal fees from 0.04 to 0.0001 XMR! (272 points, 9 comments)
    8. Poloniex also reduces Monero withdrawal fees to 0.0001 XMR! (220 points, 17 comments)
    9. Preliminary information thread regarding the scheduled protocol upgrade of October 18 (214 points, 208 comments)
    10. CLI v0.12.3.0 released! (195 points, 78 comments)
  2. 4228 points, 24 submissions: OsrsNeedsF2P
    1. Saying you don't need privacy because you have nothing to hide is like saying you don't need free speech because you have nothing to say. It's a right to everyone - It's a right to you, me, and even Mark Zuckerberg. (581 points, 138 comments)
    2. The official Fortnite Merch Store is accepting exclusively Monero as a cryptocurrency payment option... (445 points, 80 comments)
    3. Can we stop being assholes to newbies? (359 points, 94 comments)
    4. With all this Monero "is less untraceable than previously thought" FUD, let's all remember that huge fucking bounty of $$$ for anyone who can trace the origin of one of the devs transactions.. (343 points, 131 comments)
    5. Ever wanted to know how Monero is still around today? Well now you don't have to! This post has it all =D (297 points, 66 comments)
    6. Coinmarketcap shows Freewallet as a Monero wallet. Guys, whatever you do.. Don't use Freewallet. It's a scam. (286 points, 93 comments)
    7. SEC wants decentralized exchange creators to register as exchanges. Lol (182 points, 111 comments)
    8. "Please do your part in demanding exchanges to lower their XMR withdraw fee. I am submitting a complaint to Coinex who currently charge 0.04 XMR" - [x-post from /xmrtrader] (169 points, 43 comments)
    9. Can we get some appreciation for the people who maintain the Monero packages on Arch Linux? There are so many available, and every single one I've checked either make the package from source or validate the checksum. Amazing work <3 (156 points, 19 comments)
    10. [WARNING] DROPIL recently made a post announcing support for Monero. MOVE YOUR FUNDS if you used them!!! (119 points, 5 comments)
  3. 3954 points, 13 submissions: KnifeOfPi2
    1. Did John McAfee just sell all of his Monero?? (1277 points, 107 comments)
    2. We need to stop thinking about Monero as a “privacy coin.” (511 points, 200 comments)
    3. Selsta and I just completed the first Ledger-to-Ledger mainnet transactions ever. He sent me 0.1 XMR and I sent 0.4 XMR back. (482 points, 103 comments)
    4. Monero network hashrate just hit 1GH/s! (463 points, 166 comments)
    5. An upcoming Monero project: Render the entire blockchain. Here's a selection of blocks that we've done so far, in an early stage. (224 points, 31 comments)
    6. In Stunning Move, Bitmain Announces It's Launching A Doorstopper Business (193 points, 48 comments)
    7. Another red flag for X Wallet: The source code is incomplete. (190 points, 63 comments)
    8. MONERO IS DEAD! LONG LIVE MONERO! (155 points, 25 comments)
    9. Lithium Luna GUI released! (118 points, 66 comments)
    10. Cake Wallet - introducing Zendesk support! (100 points, 13 comments)
  4. 2421 points, 22 submissions: SamsungGalaxyPlayer
    1. Kasisto POS in 22 seconds (366 points, 76 comments)
    2. "Kudelski Security completed their [bulletproof] report. They found only a few minor issues that are trivial to correct, and no major issues." Overall, a huge win for Monero, bulletproofs, and privacy. Full report will be published soon. (338 points, 100 comments)
    3. Network upgrade scheduled for block 1544555 on 28 March (210 points, 56 comments)
    4. Fungibility is determined by the LOWEST common denominator of privacy, NOT the highest. Monero absolutely excels here. (103 points, 37 comments)
    5. [Discussion] Move to a Fixed Ringsize (102 points, 85 comments)
    6. The Monero Malware Response workgroup website is up! Direct people whose machines have been compromised here! (101 points, 22 comments)
    7. MoneroV: A Trap Laid for Monero Users? (93 points, 45 comments)
    8. Want to get the GUI point release faster? Help translate! (91 points, 18 comments)
    9. Introducing the Breaking Monero Series! (86 points, 26 comments)
    10. ShapeShift is moving to a membership model and will require personal information soon (83 points, 86 comments)
  5. 2295 points, 16 submissions: pinkphloid
    1. Cake Wallet - OPEN SOURCE - Here it is! (383 points, 167 comments)
    2. Our Monero wallet called CAKEWALLET for iOS is live! Please check the link to the Apple App Store below. (347 points, 379 comments)
    3. [MANDATORY UPDATE] Cake Wallet Version 3.0.9 - Network Upgrade Ready! (227 points, 19 comments)
    4. [UPDATE] Cake Wallet version 3.1.4, now with XMR.TO for exchanging XMR to BTC! (133 points, 15 comments)
    5. Cake Wallet - 10,000 unique downloads! (132 points, 29 comments)
    6. Thank for the positive feedback on Cake Wallet! (127 points, 62 comments)
    7. The new Cake Wallet Update version 3.0.1 is out now! (120 points, 50 comments)
    8. [UPDATE] CAKE WALLET 3.1.1 with Monero v0.13.0.4 and other stuff (118 points, 32 comments)
    9. Cake Wallet - UPDATE! (108 points, 75 comments)
    10. CAKE WALLET - new version live now with NEW FEATURES! (102 points, 97 comments)
  6. 2042 points, 16 submissions: Rehrar
    1. Core Team Announcement (344 points, 45 comments)
    2. Project FOSS (212 points, 37 comments)
    3. Write down your seed (200 points, 93 comments)
    4. Bulletproof audit needs some more funding. Details in the comments. (170 points, 55 comments)
    5. Extremely thorough introduction to Monero by cypherperro. Take a look. (122 points, 18 comments)
    6. Defcon Monero Village Update and Summary (116 points, 22 comments)
    7. MRL Bulletproof audit FFS request (115 points, 30 comments)
    8. I, rehrar,went on a YouTube show to talk about Morono (113 points, 28 comments)
    9. Fund the fundings! (107 points, 16 comments)
    10. The anonimal appreciation thread! (107 points, 21 comments)
  7. 1978 points, 15 submissions: Vespco
    1. Edward Snowden on Bitcoin Interview 2018 (at 50 minutes, he says that a traceable public ledger is a bigger problem then scalability) (362 points, 88 comments)
    2. Putting this on my invoices seems like a good way for me to promote Monero, give my customers a discount, & help me acquire more Monero. (325 points, 101 comments)
    3. It's fun to be a part of the Monero economy! (179 points, 26 comments)
    4. Honest Government Ad | Anti Encryption Law (178 points, 32 comments)
    5. Jeez, not much real conversation in here. Just junky news links. (129 points, 76 comments)
    6. The New York State Department of Financial Services just approved the trading of privacy-protecting cryptocurrency. | Coin Center (124 points, 11 comments)
    7. A good way to explain the importance of fungibility to the laymen: Bitcoin Roulette (99 points, 45 comments)
    8. Why I love Botnet & Browser Mining. (86 points, 39 comments)
    9. This needs more praise & attention: An Open Source, Client Side JS implementation that makes monero multisig fairly easy. Github link in comments. (82 points, 14 comments)
    10. Could we get even more cryptographers researching for Monero? (77 points, 31 comments)
  8. 1846 points, 14 submissions: SarangNoether
    1. Bulletproofs: let's raise some funds! (295 points, 94 comments)
    2. January monthly report from Sarang Noether (237 points, 39 comments)
    3. Bulletproofs: The Paper Strikes Back (153 points, 32 comments)
    4. July monthly report from Sarang Noether (142 points, 20 comments)
    5. March monthly report from Sarang Noether (129 points, 22 comments)
    6. August monthly report from Sarang Noether (122 points, 33 comments)
    7. February monthly report from Sarang Noether (119 points, 27 comments)
    8. Sarang is up for three more months! (107 points, 30 comments)
    9. October monthly report from Sarang Noether (102 points, 26 comments)
    10. September monthly report from Sarang Noether (99 points, 25 comments)
  9. 1470 points, 4 submissions: TheFuzzStone
    1. "I do not have any Bitcoin" (1182 points, 96 comments)
    2. Fluffypony at Consensus 2018 (134 points, 33 comments)
    3. Time for Monero "killers"! :-) (91 points, 34 comments)
    4. XMR.RU-report (March) (63 points, 14 comments)
  10. 1468 points, 5 submissions: philkode
    1. Overstock.com accepting Monero (and ETH, BCH, LTC, DASH) (499 points, 36 comments)
    2. Happy 4th Birthday Monero! 🎂🎉🎁 (455 points, 62 comments)
    3. Monero has been added to Debian unstable repo as of yesterday. (321 points, 52 comments)
    4. “Unhackable” BitFi wallet just got hacked (xpost /cryptocurrency) (130 points, 41 comments)
    5. X Wallet to App Store (Soon™) (63 points, 67 comments)

Top Commenters

  1. dEBRUYNE_1 (3762 points, 1243 comments)
  2. KnifeOfPi2 (3311 points, 347 comments)
  3. OsrsNeedsF2P (3189 points, 505 comments)
  4. fluffyponyza (3027 points, 272 comments)
  5. gingeropolous (2554 points, 320 comments)
  6. cryptochangements34 (2522 points, 261 comments)
  7. SarangNoether (2269 points, 185 comments)
  8. SamsungGalaxyPlayer (2108 points, 221 comments)
  9. john_alan (1993 points, 218 comments)
  10. smooth_xmr (1944 points, 279 comments)

Top Submissions

  1. Did John McAfee just sell all of his Monero?? by KnifeOfPi2 (1277 points, 107 comments)
  2. Paypal shares your personal data with over 600 companies! That's why we need Monero! by 0xf3e (1184 points, 146 comments)
  3. "I do not have any Bitcoin" by TheFuzzStone (1182 points, 96 comments)
  4. Found In Warsaw - Don't Buy Monero: Cryptocurrencies harm the banking system and can weaken the government by SecretApe (1114 points, 110 comments)
  5. Monero transactions are about to get 80% cheaper and faster. by WillMTB (1056 points, 120 comments)
  6. Bye bye ASICs by Swericor (874 points, 380 comments)
  7. Upvote if you would like to see @fluffyponyza as a guest on Joe Rogan Podcast by xmr_karnal (840 points, 44 comments)
  8. All right, my cat had kittens and I just realised one of them has Monero-like logo on its head 😂😂 by JNKO266 (817 points, 79 comments)
  9. Credit, where credit is due! by Experts-say (796 points, 53 comments)
  10. Yesterday I thought it might be fun to create some vintage crypto posters for a handful of coins. This was the first one I came up with. Bonus points if you spot similarities from an old movie by Beemoe4 (722 points, 67 comments)

Top Comments

  1. 495 points: mr670wl's comment in Found In Warsaw - Don't Buy Monero: Cryptocurrencies harm the banking system and can weaken the government
  2. 474 points: kieranc001's comment in Monero Zero looks like a scam, can you please confirm?
  3. 380 points: deleted's comment in Found In Warsaw - Don't Buy Monero: Cryptocurrencies harm the banking system and can weaken the government
  4. 356 points: deleted's comment in Ledger Hardware Wallet - Monero integration : some news #6
  5. 331 points: last_of_the_romans's comment in Monero transactions are about to get 80% cheaper and faster.
  6. 323 points: svenroy777's comment in "I do not have any Bitcoin"
  7. 311 points: deleted's comment in Did John McAfee just sell all of his Monero??
  8. 255 points: KnifeOfPi2's comment in Monero transactions are about to get 80% cheaper and faster.
  9. 237 points: live9free1or1die's comment in Banning privacy coins because of terrorism/drugs/laundering is like banning people from being allowed to have sex in privacy because pedophiles also like privacy.
  10. 203 points: fluffyponyza's comment in Botnets are Ruining the Integrity of the Monero Network
Generated with BBoe's Subreddit Stats (Donate)
submitted by OsrsNeedsF2P to subreddit_stats [link] [comments]

Anatomy of crypto data destruction and RNG

Ever since the post-credits scene in season 2, I've been thinking about how the stage 1 "payload" that encrypted all of the E-Corp systems might have been built, and how it might be flawed enough to permit data recovery. No sci-fi time-travel magic required for this theory.
We never get a direct look at the malware, but we do get a smattering of references to what it is throughout the episodes so far. Not enough to get a totally clear picture, but it's somewhere to start with educated guesses.
In S01E01, Mr. Robot is explicit about the aims:
If we hit their data center just right, we could systematically format all the servers, including backup. It would be impossible to enforce outdated paper records. It would all be gone.
Okay. They want to irreversibly delete the data on all of E-Corp's servers and backups.
In S01E02, when tasking Elliot with blowing up the Comet electric natural gas plant to take out the tape backups at Steel Mountain, Mr. Robot elaborates:
Once we blow up the pipeline, Darlene's worm will kick into high gear at the US datacenter, which you helped us to install. Thank you very much. The redundant backups at their eastern datacenter in China? The dark army is covering us on that.
Okay, we've learned the way they'll do it is with a worm, which Darlene wrote. A worm is malware that is designed to replicate itself and carry a payload.
In S01E08, after successfully entering the work order to remove the honeypot around CS30, Elliot states:
In 43 hours, exactly, our server will no longer be a honeypot, and that rootkit you wrote will take down Evil Corp. We did it Darlene. It's going to happen.
Despite what Lloyd might have said, rootkits are not serial rapists with very big dicks. They're malicious code designed to hide the presence of an attacker (inc. processes they might be running, alterations to system login and authentication modes to accept a backdoor credential) and their tools on a system once it has been compromised. Unqualified, the term "rootkit" commonly refers to kernel-mode rootkits, which operate directly within the context of the operating system, and frequently loaded through the same facilities provided for installing new device drivers. They can hide files/directories, running processes, network connections, and themselves (e.g. in the list of loaded drivers) from scanning entities on the same system. One way to detect a rootkit is to look for discrepancies between what tools on the system report (e.g. in terms of active network connections) versus what is observed externally (e.g. on a network monitoring device).
That makes the discussion of "honeypots" a little bit strange. A honeypot usually refers to a target on a network that's designed to be enticing to attackers, so that they try to hack it, but isn't "real" in the sense that it processes real data. It might be instrumented such that probing and reconnaissance activities targeting the honeypot are tied to network hacking alerts.
I can think of one of three interpretations of what turning server cs30 into a honeypot might mean:
  1. They've installed additional monitoring software on cs30.
  2. They've replaced cs30 with a totally different system that looks like cs30 to an outsider.
  3. They've installed additional network monitoring around cs30.
But none of these interpretations really make sense. If it's #1, if the rootkit was written properly, it's likely that additional monitoring would be fruitless, and the attack could be carried out without the whole Whiterose meeting riddles.
If it's #2, then the rootkit would probably not have been copied over to the clone, and fscociety would have noticed their server misbehaving. Unless, of course, E-Corp discovers the rootkit on cs30 as part of this process, in which case, they could have just cleaned it up, and closed off fsociety access to the internal server.
If it's #3, then the periodic use of the backdoored access to cs30 by fsociety should have been noticed by looking at that network monitoring data, likewise leading to a server cleanup and removal of the backdoor.
I'll chalk this up to somewhat cavalier and imprecise use of technical terminology by a TV show, and press on.
What have we learned so far?
In S01E09, after Tyrell coerces Elliot into showing him the fsociety arcade:
Tyrell: What is it that you're doing exactly?
Elliot: Encrypting all the files. All of Evil-Corp's financial records will be impossible to access. The encryption key will self-delete after the process completes.
Wait a second? Encryption? Encryption key? I thought we were after data deletion.
Of course, there's a perfectly plausible explanation: deleting data takes time. If you go around rm -rf'ing servers, there's a good chance that recoverable data will be scattered around those hosts. By performing bulk encryption, you overwrite all data on the target systems once, can still permit access to everything on the system while the encryption is occurring, and then destroy the key once the encryption process is completed. This lowers the length of the window in which someone can realize that something has gone terribly wrong. The key is small (tens of bytes, not to gigabytes or hundreds of gigabytes), and can be deleted almost instantaneously.
Several full disk encryption systems, including FileVault in macOS, and the now-defunct TrueCrypt have the ability to do this: you start encrypting the drive, but can continue working while the data is read, encrypted, and overwritten unnoticed in the background.
Some ransomware strains also follow this practice, so it's not an unreasonable approach. However, cryptography is a loaded foot cannon for the unwary, and it's surprisingly easy to make a small mistake that unravels the whole thing.
In S01E10, as Elliot looks for Tyrell at the E-Corp building, in voice-over he says:
A simple program: a worm that can make data unreadable. Malware that took Darlene maybe 2 hours to code. Is that all it takes to kill the world?
And follows with:
I wonder what stage they're at. Denial? Muttering to themselves "no, this can be fixed." Maybe bargaining? Forcing their techs to work overtime to try to decrypt our data. Or have they come to the realization yet that Darlene encrypted everything with 256-bit AES, and it would take an incomprehensible amount of time to crack? That all of their data is actually gone, for good.
AES is a symmetric encryption algorithm in wide use. It's stood the test of time since its standardization in 2000, and lots of people trying to find weaknesses in the last 2 decades. At a 256-bit key length, it would take many multiples of lifetimes of the universe to break, at least so long as computers are still made out of atoms. A quantum computer would not meaningfully assist in this kind of attack, as Grover's algorithm would still require 2128 quantum operations, and this is still going to take many multiplies of lifetimes of the universe to break.
But it does raise questions about cryptographic hygiene. Mechanically: what mode of operation is AES being used in to encrypt files? Let's assume Darlene has heard of the ECB penguin and has picked something better like CBC with per-file random initialization vectors.
More importantly: where is that key coming from? The right answer is to read it from a operating system provided cryptographically secure random number generator like /dev/urandom on UNIX-like systems, or the equivalent on Microsoft Windows CryptGenRandom. Ideally, perform this random key generation process individually (resulting in unique keys) on every single target system. There have been cases where CryptGenRandom has produced sub-par quality randomness on earlier versions of Windows, but not since Windows XP SP2 or older.
My theory is that this is where the fsociety worm went wrong.
In S02E01, we see the night of the hack for the first time, and in the terminal we see:
[email protected]:~# ssh -l root bkuw300ps345672-cs30.serverfarm.evil-corp-usa.com [email protected] password: The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usshare/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Thu May 8 16:26:57 2015 from cs30.serverfarm.evil-corp-usa.com [email protected]:~# cd /opt/2/task/2/fd1nfo/fsociety/hscripts/ [email protected]:/opt/2/task/2/fd1nfo/fsociety/hscripts# ls fuxsocy.py loadmod.py rootkitctrl sniff-out.pcap kernel_modules nuke.py sn1ff worm.py [email protected]:/opt/2/task/2/fd1nfo/fsociety/hscripts# ./fuxsocy.py 
And then:
Executing FuxSocy Loading Source of Entropy ####################### COMPLETE Generating Keys ####################### COMPLETE Locating target files. beginning crypto operations Encrypting /bin Encrypting /boot Encrypting /dev Encrypting /etc 
"Loading Source of Entropy" you say? That sounds awfully like a userspace random number generator. If the entropy pool is too small, or if the random number generation process is otherwise flawed, the key fed into the AES encryption process might be much more predictable than the 256-bit key length would suggest.
There was a major incident of this type discovered in 2006, where the Debian GNU/Linux package maintainers for OpenSSL (a popular, and widely used, though terrible) cryptography library commented out some lines that were generating code safety warnings when packaging it for the Debian distribution. Turns out these lines were essential to introducing any kind of real randomness for uses by the library, and this includes key generation and certain signing operations.
The fallout was that the affected versions of OpenSSL on Debian GNU/Linux would only generate 32,768 or 214 distinct keys. This also affected things like ECDSA signing, which was mirrored in 2013 when a similar vulnerability in Android led to the theft of about 56 Bitcoins.
You would have to know how the flawed key generation was implemented, and it would not necessarily be obvious looking at the keys from the outside, but if there was a flaw of this magnitude, you could break that "256-bit" key almost instantly with e.g. 14-bits of effort.
The use of Debian on the E-Corp servers might be a suggestive hint to this historical fiasco too.
The screen output also suggests that there might have been a single key generated at the start of the process that was copied as part of the data destruction payload to all of the E-Corp servers. Not ideal from a cryptographic hygiene standpoint.
In the post-credits scene of S02E12, Trenton and Mobley discuss:
Trenton: Have you given any more thought to what I said?
Mobley: I don't want to discuss this.
Trenton: Mobley...
Mobley: Fredrick.
Trenton: Seriously, Fredrick, what if we could? This might work.
Mobley: And also, it might not. I've taken enough risks for one lifetime, I don't want to discuss it anymore.
Trenton: But what if we could generate the keys...
Mobley: Tanya... will you just please shut up?
Trenton: What? This is important. We need to talk about it.
...
Trenton: Please, just look at it.
Mobley: Okay, so what? Say I did. Then what?
Trenton: If what I discovered is real, do you know what that means?
Mobley: Yeah, I know exactly what it means.
Trenton: Yeah, it means we could potentially undo this whole thing. Put everything back the way it was.
Mobley: I know. I know.
Trenton: Please. Just look at what I found.
I bet they've looked over the fsociety data destruction payload code and discovered a way to reproduce the key, precisely because there's this kind of flaw in it.
Finally, during Tyrell's AMA, a.k.a. S03E03, we get another shot of stage 1 running:
Thread #7 - 233 hosts online, initiating SCP transfer Waiting on thread updates ... Thread #2 - SCP complete. launched encryption tasks Thread #6 - SCP complete. launched encryption tasks Waiting on thread updates Thread #2 - Encryption tasks completed & verified Updating process log Thread #2 - Obtaining next hosts ... read 256 addresses Waiting on thread updates Thread #6 - SCP complete. launched encryption tasks Waiting on thread updates Thread #2 - Starting tasks on 10.0.0.29/24 
I interpret this as cs30 copying (via SCP) the data destruction payload to every server on the E-Corp network. The 10.0.0.0/8 IP addresses are designated internal network addresses, and are common for large internal business networks. It's odd that E-Corp would have a totally flat network, and also odd that cs30 itself seems to be copying the payload everywhere (not very worm-like), but perhaps this is just artistic license from the VFX guys.
Given how little we see of this screen, and how it was effective at wiping out E-Corp, I think it's safe to assume that the payload being transferred over SCP is both a propagator (i.e. the worm) and a data destruction payload, which would also address it spreading over the entire E-Corp network, even if it isn't flat. It is still suggestive of the single-key possibility though.
So, did Darlene fuck up the crypto? I think so. There's a few more suggestive quotes.
In S01E06, after dropping USB flash drives in the police parking lot for Elliot, the malware is blocked by antivirus.
Elliot: Did you write that exploit yourself?
Darlene: I had an hour.
Elliot: So what? You just pulled code from Rapid9 or some shit? Since when did you become a script kiddie?
Darlene: I repeat: I had an hour.
We learn that Darlene can be sloppy when doing things quickly, and re-iterating Elliot's voice-over in S01E10:
Malware that took Darlene maybe 2 hours to code.
And another off-hand remark in S01E08:
Elliot: How'd it go with the climate control hack?
Darlene: Handled. I happen to be really smart and good at things. Not like you give a shit.
There's a lot of ways that subtle faults in a cryptographic implementation can lead to the entire system coming tumbling down. Darlene might be an expert malware coder, but that's not a universal skill that necessarily translates over to other aspects of information security.
If you're curious about not falling into "bad noob practices" with crypto, there's a great set of cryptography building and breaking challenges that don't require much more than basic algebra, statistics, and coding skills.
Wildly speculating now:
submitted by DrElectolight to MrRobot [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]

[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]

Electrum will be in the next Ubuntu release in ~1 month. Please help test it now.

Hello, I am magicfab posting from the Bitcoin Embassy account.
Yesterday I shared here why I thought it was excellent news that Electrum was recently made available to all Debian GNU/Linux users and its derivatives and how it was so recent that it had missed the time window to be included automatically in one of its derivatives, Ubuntu.
I filed a bug report to make an exception and include electrum in Ubuntu now instead of waiting another 6 months, and it was quickly accepted. The package is already available for testing. Don't download it directly! If you're using Ubuntu 13.10 already you can search for electrum with your package manager or just sudo apt-get install electrum.
This is the ideal time to install Ubuntu 13.10 and test its functionality and this includes Electrum. Ubuntu "Saucy Salamander" is still in beta, and beta freeze is today. For all intents and purposes, the beta version is very close to what will be released in ~1 month, stable enough to use daily, and specially to test and file important bugs reports. If you find a bug in Ubuntu for Electrum or Debian, this is an excellent time to report it.
As the Chief Ambassador here at the Bitcoin Embassy, this is one of the more technical aspects in my role of Bitcoin advocacy that I believe is important to help with. If anyone files a bug report, has similar ideas or other technical requests regarding use of Bitcoin with free open source software / operating systems, PM me at magicfab or Bitcoin_Embassy.
tl;dr: Electrum will be in the final Ubuntu 13.10 release :) PM me if you have technical suggestions/requests related to Bitcoin + free software.
submitted by Bitcoin_Embassy to Bitcoin [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]

Easy UASF Node in Debian VM tutorial

So if you have a moderately powerful gaming desktop with a Quad-Core CPU like an i5 or better and 8+GB of RAM, you can easily run your own little UASF node in the background. Once it's done syncing with the network, you won't even notice it's there. Here's how.
You will need :
The following assumes you know how to install Linux in a Virtual Machine
Step I. - Installation. Go through expert install and set up a base system with only ssh server enabled. For partitioning, you can do just one big disk and everything in one partition, but if you happen to have a computer that has both SSD's and HDD's, it would be optimal to create two virtual disks and use a small one for the OS on the SSD and a larger one on the HDD in a custom mount point for the blockchain. Reboot and ssh into the server.
Step II. - Build requirements. A few things need to be taken care of. First, you'll want to edit the /etc/network/interfaces file and set up a static IP. Once that's done, stop by your router and make sure that traffic on port 8333 is forwarded to your debian VM. Then, install some packages we need :
apt update apt upgrade apt install build-essential autoconf libssl-dev libboost-dev libboost-chrono-dev libboost-filesystem-dev libboost-program-options-dev libboost-system-dev libboost-test-dev libboost-thread-dev libevent-dev git libtool pkg-config 
The next one is a bit more annoying. We need Berkeley DB 4.8, and it's a little old. It's packages are in the Debian Squeeze archives, so in the /etc/apt/sources.list file, we need to add :
deb http://archive.debian.org/debian/ squeeze main 
Then remember to update again, and install the thing :
apt install libdb4.8++-dev libdb4.8-dev 
If you intend to also throw on xorg and a UI, you will want Qt as well. Otherwise skip this last step.
install libqt4-dev libprotobuf-dev protobuf-compiler libqrencode-dev 
Step III. - Build time
#Starting from /home/yourUser git clone https://github.com/UASF/bitcoin.git -b 0.14-BIP148 cd bitcoin ./autogen.sh ./configure make make install 
That's it! Well, mostly. Start it with
bitcoind -daemon -disablewallet -datadir=/whereveyou/want/youblockchain 
...and wait about thirty hours to sync with the network. You may want to visit the /whereveyou/want/youblockchain directory and create a permanent bitcoin.conf in there. To enable RPC calls to the server and get it to accept bitcoin-cli commands you'll want to use it to create a usepassword and copy that to your user's /.bitcoin/bitcoin.conf.
Minimal bitcoin.conf example
daemon=1 listen=1 disablewallet=1 server=1 rpcuser=bob rpcpassword=bob's password 
Security I recommend you disable password login and use private key authentication only on ssh, and also restrict iptables rules to the bare minimum that must be allowed for this application. You will need this in your iptables script :
# Allows BITCOIN traffic from anywhere -A INPUT -p tcp --dport 8333 -j ACCEPT # Allows RPC calls to the bitcoin server from localhost -A INPUT -p tcp -s 127.0.0.1 --dport 8332 -j ACCEPT 
Useful ressources :
submitted by the_bolshevik 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]

Compiling Bitcoin Core Source Code - 2017 debian/ubuntu/linux with Music The Debian sources list generator! How to setup debian repository's! Bitcoin Faucet: Silver Moon BTC - 5 to 50 satoshis every 15 minutes (Faucetpay) How Buy To Bitcoin Vault Packages With Mining City Bitcoin Mining on Ubuntu 18.10 - Bitcoin Mining Software 2019

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.4.0 instead of 3.9.5). problems The package is severely out of date with respect to the Debian Policy. The following binary packages are built from this source package: bitcoin-qt peer-to-peer network based digital currency - GUI bitcoin-tx peer-to-peer network based digital currency - transaction tool bitcoind peer-to-peer network based digital currency - daemon All versions of bitcoin source in Debian; Versions published Release. The package versions that were published when the distribution release was made. bitcoin 0.18.1~dfsg-1.2 (main) View changelog; View copyright; bitcoin information. Current version: 0.18.1~dfsg-1.2 peer-to-peer network based digital currency - GUI. This package provides Bitcoin Core tool Bitcoin-Qt, a graphical user interface for Bitcoin. Bitcoin (₿) is the world's first cryptocurrency, a form of electronic cash sent peer-to-peer without the need for a financial intermediary. Bug sid Description; CVE-2019-15947: vulnerable: In Bitcoin Core 0.18.0, bitcoin-qt stores wallet.dat data unencrypted CVE-2018-20587: vulnerable: Bitcoin Core 0.12.0 through 0.17.1 and Bitcoin Knots 0.12.0 through 0.

[index] [2111] [31083] [7368] [25198] [10330] [29083] [23473] [1868] [17977] [8190]

Compiling Bitcoin Core Source Code - 2017 debian/ubuntu/linux with Music

Joining Link: https://www.crowd1.com/signup/khanali PACKAGE INFORMATION 01 euro equal to 190 pkr 01 euro equal to 84.04 Indian. PACKAGE PRICE IN EURO PRICE I... Bitcoin is a new technology that functions as a digital currency. It is a peer-based, decentralized way to hold, store, send, and receive value. It does this by maintaining a cryptographic ... This is the first step towards complete Bitcoin Core integration. ... + Added debian package. ... Wasabi is an open-source, non-custodial, privacy focused Bitcoin wallet, that implements trustless ... This short video shows how to compile the bitcoin source code on linux (ubunu). an easy task to do but it take some time (around 15 min) please read the instruction in the official github https ... Disclaimer! I'm not a financial advisor! What ever I'm sharing on my videos is based on my own personal experience and speculations! Sign up for Mining City ...

Flag Counter