Satoshi – BitcoinWiki

Cryptocurrency News & Discussion

The official source for CryptoCurrency News, Discussion & Analysis.
[link]

r/Cryptocurrency testing

For testing out CSS changes to CryptoCurrency.
[link]

Cryptocurrency & Blockchain

CryptoCurrency Cryptocurrencies Blockchain Crypto Currency Bitcoin Ethereum News Price Market Cap Coinbase Ripple Exchange Wallet Mining Reddit New USD Value Top List Best Invest BTC ETH BCH XRP DASH LTC XMR MIOTA NEO XEM ETC QTUM LSK EOS ZEC OMG ADA XLM HSR USDT BCC WAVES PPT STRAT BTS POWR ARK ARDR REP KMD BCN DCR STEEM PAY MONA FCT MAID VERI GNT GAS SALT RDN DOGE PIVX VTC BAT SCAE GBYTE BNB TRX DGD KNC BTCD
[link]

Ciao! Sono Matteo Vena, uno degli organizzatori della Blockchain Week Rome e studioso di criptovalute, AMA!

Ciao a tutti!

Sono Matteo Vena. Sono un informatico ed un grande appassionato di tecnologia. Attualmente lavoro a tempo pieno nel settore della blockchain e delle criptovalute, uno dei più vivaci negli ultimi anni. All'inizio della mia attività professionale mi sono occupato di elettronica di consumo, prevalentemente di provenienza asiatica. Ho avuto la possibilità di fare test di varia natura su hardware e software, principalmente smartphone. Ho anche avuto la fortuna di visitare, durante un viaggio di lavoro, Huaqiangbei, nella città cinese di Shenzhen, da molti ritenuto il più grande mercato dell'elettronica al mondo. Un vero paradiso per geek.
Ho iniziato a scrivere di tecnologia prima ancora di iniziare il mio percorso universitario. Oggi sono il responsabile di Cointelegraph Italy. Cointelegraph è il più grande portale al mondo dedicato a blockchain e criptovalute, disponibile in 10 lingue.
Il mio percorso di studio di questo settore è iniziato molti anni fa, ovviamente con Bitcoin, grazie ad una piccola conferenza tenuta da un gruppo di ricerca di Banca d'Italia. Da allora non ho mai smesso di approfondire ed informarmi.
Sono inoltre uno degli organizzatori della Blockchain Week Rome, il più grande evento in Italia dedicato alla tecnologia blockchain, alle criptovalute ed alla decentralizzazione.
Nonostante il mio giudizio sia, ovviamente, "di parte", posso affermare con sincerità che l'evento rappresenta un'occasione più unica che rara per entrare in questo mondo. I cinque giorni di durata comprendono un corso di formazione che copre le basi del settore (tre giorni) ed un Summit, ovvero un mix di conferenze, esposizioni, workshop ed altre attività (due giorni). L'edizione 2020 avrà luogo dal 17 al 21 marzo, ovviamente a Roma.
Linkedin ha inserito "Blockchain" al primo posto delle hard skill più desiderate nel 2020. Questo è davvero un momento perfetto per approfondire.
Abbiamo inoltre preparato il codice sconto "ITALYINFO", da usare per l'acquisto di qualsiasi tipologia di biglietto, che vi offrirà il 15% di sconto (usare senza virgolette)!
Ringrazio Fen0x per l'opportunità!
OT: sono un appassionato di software libero. Parteciperò a questo AMA principalmente dal mio PC fisso con OS Manjaro Linux, progetto che supporto.
Edit: L'AMA finisce qui, grazie mille a tutti per aver partecipato!
submitted by yagamix to ItalyInformatica [link] [comments]

Subreddit Stats: CryptoTechnology top posts from 2017-12-23 to 2020-01-20 15:51 PDT

Period: 758.36 days
Submissions Comments
Total 956 13660
Rate (per day) 1.26 18.01
Unique Redditors 584 3144
Combined Score 21553 44566

Top Submitters' Top Submissions

  1. 1166 points, 43 submissions: Neophyte-
    1. "Do you need a Blockchain?" - this paper is fantastic, everyone should read this before evaluating a coin and if requires a block chain to solve a solution the coin is promising to solve. (136 points, 41 comments)
    2. Do any of you foresee a crypto being widely adopted as a general purpose payment coin? nano, btc, btccash etc (take your pick). I think it won't happen for reasons in this post. What do you think? (59 points, 54 comments)
    3. Noticed the huge rise of EOS lately what does it have over NEO and ethereum and to a lesser extent Cardano? I tried researching it, but wasn't sold. (54 points, 55 comments)
    4. Hard Problems in Cryptocurrency: Five Years Later ~Vitalik (46 points, 1 comment)
    5. I had a Q&A with Bruno head architect / CEO of oyster, thought you guys might like it. (45 points, 2 comments)
    6. A good article that explains in simple terms how Eth2 works, how it will be rolled out and migrated from eth1 (42 points, 4 comments)
    7. DAI the stablecoin can now be transferred GAS free (article explaining how it works via new MCD DAI contract). This holds alot of promise for the so called "Web3" (40 points, 8 comments)
    8. Veriblock is consuming 27% of bitcoins block space - what does this mean for bitcoins future? (39 points, 16 comments)
    9. Vitalik: Alternative proposal for early eth1 <-> eth2 merge (38 points, 3 comments)
    10. Is launching a PoW permissionless blockchain still possible today? or would it be too susceptible to a 51% attack? (37 points, 37 comments)
  2. 578 points, 16 submissions: crypto_ha
    1. Why is Ripple considered a cryptocurrency (by many)? (109 points, 63 comments)
    2. So reportedly there are serious vulnerabilities found in EOS’ code. And it seems like those are more than just random software bugs. (97 points, 29 comments)
    3. Guide: How to get started with Blockchain development? (60 points, 6 comments)
    4. A newly found vulnerability in Nano's Android wallet (44 points, 12 comments)
    5. The history and state of Ethereum's Casper research - Vitalik Buterin (39 points, 4 comments)
    6. What is the difference between Sidechain vs Child Chain vs Off Chain? (39 points, 12 comments)
    7. EOS mainnet is official live (finally), but... (36 points, 24 comments)
    8. Bitcoin's "doomsday" economics - Bank of International Settlements (34 points, 23 comments)
    9. How Wall Street’s embrace could undermine Bitcoin (30 points, 9 comments)
    10. Ethereum ERC 1497: DApp Dispute Evidence Standard (24 points, 0 comments)
  3. 513 points, 20 submissions: ndha1995
    1. Ethereum Classic is currently being 51% attacked (103 points, 31 comments)
    2. Why are there so many garbage posts the past 24 hours? (58 points, 10 comments)
    3. Google Unveils 72-Qubit Quantum Processor With Low Error Rates (48 points, 24 comments)
    4. IOTA's Network-Bound PoW consensus, is it feasible? (42 points, 13 comments)
    5. The Challenges of Investigating Cryptocurrencies and Blockchain Related Crime (29 points, 7 comments)
    6. Deep dive into zk-STARKs with Vitalik Buterin's blog posts (26 points, 3 comments)
    7. Tether discussion thread (26 points, 21 comments)
    8. Vitalik Buterin Proposes a Consensus Algorithm That Requires Only 1% to Be Honest (24 points, 8 comments)
    9. Can somebody compare Qtum vs. NEO, technology-wise? (E.g. PoS vs. PoW; smart contract protocols...) (21 points, 15 comments)
    10. Introduction to Non Fungible Tokens (NFTs) (21 points, 9 comments)
  4. 377 points, 16 submissions: turtleflax
    1. Around 13% of DASH's privateSends are traceable to their origin (69 points, 3 comments)
    2. "Big Bang" attack could leverage Monero's dynamic blocksize to bloat the blockchain to 30TB in only 36 hours (52 points, 3 comments)
    3. The case for the obsolescence of Proof of Work and why 2018 will be the year of Proof of Stake (41 points, 29 comments)
    4. Monero vs PIVX: The First Scheduled Privacy Coin Debate Thread on /CryptoCurrency (38 points, 12 comments)
    5. Introducing the Privacy Coin Matrix, a cross-team collaboration comparing 20 privacy coins in 100 categories (26 points, 25 comments)
    6. Do permissioned blockchains have any merits? (25 points, 23 comments)
    7. The State of Hashing Algorithms — The Why, The How, and The Future (21 points, 4 comments)
    8. How Zerocoin Works in 5 Minutes (19 points, 5 comments)
    9. Errors made by Satoshi (17 points, 8 comments)
    10. How Much Privacy is Enough? Threats, Scaling, and Trade-offs in Blockchain Privacy Protocols - Ian Miers (Cornell Tech, Zerocoin, Zerocash) (17 points, 4 comments)
  5. 321 points, 6 submissions: Qwahzi
    1. Technical comparison of LIGHTNING vs TANGLE vs HASHGRAPH vs NANO (133 points, 37 comments)
    2. Addressing Nano's weaknesses (bandwidth usage and disk IO). Nano voting traffic to be reduced by 99.9% by implementing vote by hash, lazy bootstrapping, and reduced vote rebroadcasting (x-post CryptoCurrency) (78 points, 8 comments)
    3. Emergent centralization due to economies of scale (PoW vs DPoS) – Colin LeMahieu (52 points, 37 comments)
    4. Nano community member developing a distributed "mining" service to pay people to do PoW for third-parties (e.g. exchanges, light wallet services, etc) (32 points, 20 comments)
    5. What do you think about OpenCAP, the cryptocurrency alias protocol that mirrors traditional email addresses? (15 points, 12 comments)
    6. Bitcoin would be a calamity, not an economy (11 points, 52 comments)
  6. 256 points, 4 submissions: rockyrainy
    1. Bitcoin Gold hit by Double Spend Attack (51% attack). The Attacker reversed 22 blocks. (179 points, 102 comments)
    2. ZK-starks white paper published (44 points, 16 comments)
    3. [Q] How does a network reach consensus on what time it is? (21 points, 17 comments)
    4. Stateless (no history) Cryptocurrency via snapshots? (12 points, 7 comments)
  7. 244 points, 3 submissions: HSPremier
    1. From a technical standpoint: Why does every blockchain projects need their own coins? (181 points, 50 comments)
    2. What is Reddit's obsession with REQ? (61 points, 43 comments)
    3. What is the technological difference between a privacy coin and a privacy coin platform? Won't a privacy coin platform be more superior than a privacy coin? (2 points, 3 comments)
  8. 234 points, 2 submissions: Realness100
    1. A Guided Reading of Bitcoin’s Original White Paper (202 points, 10 comments)
    2. A Guided Reading of Ethereum's Original White Paper! (32 points, 5 comments)
  9. 185 points, 4 submissions: tracyspacygo
    1. My brief observation of most common Consensus Algorithms (159 points, 49 comments)
    2. What are the main Trends/Challenges for Bitcoin and whole crytpocurrencies industry? (12 points, 33 comments)
    3. Guideline for Newbies: Trying out Bitcoin transactions with TESTNET (7 points, 1 comment)
    4. Most advanced Cryptocurrencies Comparison Table (7 points, 8 comments)
  10. 177 points, 9 submissions: benmdi
    1. What's the best argument against cryptotechnology? I.e. Steelman the cryptocurrency skeptic (43 points, 42 comments)
    2. Would there be interest from this community in crypto resources aimed at developers? If so, what topics? (29 points, 14 comments)
    3. Has the window for bootstrapping a new PoW coin closed? (24 points, 57 comments)
    4. What can we, as a community, learn from the rise & acquisition of GitHub (23 points, 8 comments)
    5. 🍱 Rollup Roundup: Understanding Ethereum's Emerging Layer 2 (19 points, 1 comment)
    6. Video Tutorial: Introducing An Experience Dev To Smart Contract Coding (17 points, 3 comments)
    7. Do we need a blockchain to be decentralized? What questions would you ask a self described fan of decentralization, but blockchain skeptic? (11 points, 19 comments)
    8. ETH Block Rewards And Second Order Effects On Hardware Availability (7 points, 8 comments)
    9. Which Of The Big Tech Companies Is Most Likely To Bring Crypto Mainstream? Here's Why I Think It's Apple (4 points, 7 comments)
  11. 175 points, 9 submissions: galan77
    1. Is the Lightning Network a massive threat to the blockchain? (49 points, 66 comments)
    2. TPS of Lightning Network vs. Sharding, which one does better? (28 points, 7 comments)
    3. Are there any major downsides to sharding? (21 points, 33 comments)
    4. What's the difference between trustlessness and permissionlessness (19 points, 7 comments)
    5. Which consensus algorithm is the best, PoW, PoS, PoAuthority, PoAsset? (18 points, 57 comments)
    6. How can XRP reach 50,000 TPS when they have no sharding and every node has to validate every single transaction. (15 points, 14 comments)
    7. A few questions about the Lightning Network (14 points, 6 comments)
    8. Pascalcoin can do 72,000 tps apparently. Is this legit? The new Nano? (8 points, 39 comments)
    9. How does Ripple's (XRB's) consensus algorithm Proof of Correctness work, are there any downsides? (3 points, 23 comments)
  12. 175 points, 1 submission: ilielezi
    1. Why white papers in crypto world are so unprofessional? (175 points, 88 comments)
  13. 165 points, 6 submissions: CryptoMaximalist
    1. Facebook's Libra (48 points, 55 comments)
    2. “Fake Stake” attacks on some Proof-of-Stake cryptocurrencies responsibly disclosed by researchers from the Decentralized Systems Lab at UIUC (31 points, 9 comments)
    3. Quantum Computing and the Cryptography in Crypto (27 points, 14 comments)
    4. PING and REJECT attacks on ZCash (Patch available) | Stanford Applied Crypto Group (22 points, 1 comment)
    5. Introduction to Cryptography: Part 1 - Jinglan Wang (19 points, 1 comment)
    6. New site howmanyconfs.com shows the amount of time and confirmations of Proof of Work coins to match 6 confirmations on Bitcoin (18 points, 11 comments)
  14. 163 points, 10 submissions: GainsLean
    1. Videos For Developers Who Want To Learn Blockchain In A Practical Way (36 points, 17 comments)
    2. What Do You Want To Learn? (32 points, 20 comments)
    3. Get Involved With The Smart Contract Coding Challenge (25 points, 4 comments)
    4. Solution To $10K Art Prize (25 points, 3 comments)
    5. Blockchain Course Outline Has Been Released - Feedback warranted (22 points, 12 comments)
    6. Introduction To Distributed Systems And Consensus Protocols (9 points, 2 comments)
    7. Are there any closed source crypto wallets? (4 points, 19 comments)
    8. Are there any successful proof of identity projects? (4 points, 8 comments)
    9. SPV Wallets Vs API Wallets (4 points, 1 comment)
    10. 12 Popular Consensus Algorithms - Explained (2 points, 0 comments)
  15. 163 points, 7 submissions: QRCollector
    1. Part 5. I'm writing a series about blockchain tech and possible future security risks. This is the fifth part of the series talking about an advanced vulnerability of BTC. (43 points, 43 comments)
    2. I'm writing a series about blockchain tech and possible future security risks. This is the third part of the series introducing Quantum resistant blockchains. (36 points, 4 comments)
    3. Part 4B. I’m writing a series about blockchain tech and possible future security risks. This is the fourth part of the series explaining the special quality of going quantum resistant from genesis block. (25 points, 21 comments)
    4. Part 6. (Last part) I'm writing a series about blockchain tech and possible future security risks. Failing shortcuts in an attempt to accomplish Quantum Resistance (24 points, 38 comments)
    5. I'm writing a series about blockchain tech and possible future security risks. This is the first part of the series introducing the basic concept of blockchain and what makes it reliable. (23 points, 10 comments)
    6. I'm writing a series about blockchain tech and possible future security risks. This is the fourth part of the series explaining the special quality of going quantum resistant from genesis block. (7 points, 1 comment)
    7. Part 2. I'm writing a series about blockchain tech and possible future security risks. This is the second part of the series: An accessible description of hashing and signature schemes. (5 points, 0 comments)
  16. 162 points, 3 submissions: FashionistaGuru
    1. How do we change the culture around cryptocurrency? (118 points, 54 comments)
    2. Which cryptos have the best new user experience? (30 points, 34 comments)
    3. Why does Apple prevent many crypto apps from entering the App Store? (14 points, 8 comments)
  17. 157 points, 7 submissions: SamsungGalaxyPlayer
    1. Breaking Monero Episodes 1-3: Introduction, Ring Signatures, 0-Decoy and Chain Reactions (45 points, 1 comment)
    2. "No, dPoW Isn't a Perfect Solution" (35 points, 48 comments)
    3. Breaking Mimblewimble’s Privacy Model - Dragonfly Research (27 points, 10 comments)
    4. Breaking Monero (and Zcash) Episodes 7-9: Remote Nodes, Timing Attacks, Poisoned Outputs (EAE Attack) (21 points, 2 comments)
    5. "Attacker Collection of IP Metadata" (18 points, 10 comments)
    6. "Tracing Transactions Across Cryptocurrency Ledgers" Using Shapeshift and Changelly (6 points, 4 comments)
    7. Breaking Monero Episodes 4-6: Chain Splits (Key Image Attack), Input Selection Algorithm, Unusual Ringsize (5 points, 2 comments)
  18. 147 points, 1 submission: shunsaitakahashi
    1. Proof-of-Approval: Stake Based, 1 Block Finality & History Attack Defense (147 points, 4 comments)
  19. 146 points, 6 submissions: themoderndayhercules
    1. "The selfish mining fallacy" explained and debunked (60 points, 8 comments)
    2. A Discussion of Stable coins and Decentralized Oracles (35 points, 8 comments)
    3. A Selfish Mining Double Spending attack Simulator (25 points, 2 comments)
    4. Why reputation systems don't work (15 points, 12 comments)
    5. A better incentivization for Swarm (6 points, 0 comments)
    6. When Mises met Szabo - A Discussion of the value of Bitcoin (5 points, 16 comments)
  20. 143 points, 7 submissions: KomodoWorld
    1. Komodo Platform's core developer and founder jl777 has started his own blog on Medium. The blog is aimed for senior developers who want to learn about blockchain. (46 points, 15 comments)
    2. Delayed Proof of Work (dPoW) security explained (36 points, 46 comments)
    3. Proof-of-Gameplay (19 points, 3 comments)
    4. Good guide for getting started with the Custom Consensus tech for Komodo-based blockchains (17 points, 0 comments)
    5. Cross-chain migration of coins with Crypto Conditions - by smk762 (12 points, 0 comments)
    6. A step-by-step example of working with a Crypto Conditions based Oracle - by smk762 (10 points, 0 comments)
    7. Changing consensus rules on the fly with Crypto Conditions (3 points, 0 comments)
  21. 141 points, 8 submissions: Stormy1997
    1. What technical/business advantages does a private blockchain have over a SQL server? (49 points, 79 comments)
    2. Is sharding to scale bad? (24 points, 28 comments)
    3. How would one create a fiat gateway theoretically? (19 points, 19 comments)
    4. Looking for Stellar smart contract/side chain code examples (16 points, 1 comment)
    5. Question - Securing personal information on a centralized server with user-owned keys (13 points, 3 comments)
    6. How do blockchains/smart contracts communicate with oracles? (10 points, 4 comments)
    7. Bandwidth scaling for TPS (8 points, 2 comments)
    8. Best method to transmit detailed data between two parties via existing platforms (2 points, 1 comment)
  22. 141 points, 3 submissions: seventyfiver
    1. Why does Ethereum use Solidity while other ecosystems like NEO stick with popular ones like Java and C#? (94 points, 26 comments)
    2. Chainlink's initial Go implementation went live this morning. Has anyone reviewed the code and can comment on it's quality? (40 points, 3 comments)
    3. What are some great books on cryptoeconomics or blockchain technology? (7 points, 4 comments)
  23. 134 points, 6 submissions: johnny_milkshakes
    1. Sub dedicated to DAG based coins (42 points, 8 comments)
    2. Thoughts on this? (28 points, 38 comments)
    3. This is very interesting (24 points, 19 comments)
    4. Educational presentation by Clara Shikhelman (18 points, 0 comments)
    5. Ethics question. (12 points, 40 comments)
    6. How to scale on chain? (10 points, 30 comments)
  24. 127 points, 4 submissions: sukitrebek
    1. What are you currently obsessed with, and why? (58 points, 150 comments)
    2. Crypto-based social network without a cryptocurrency. (42 points, 23 comments)
    3. How does underlying architecture affect what kinds of applications are possible? (17 points, 3 comments)
    4. Holochain vs. Radix DLT (10 points, 11 comments)
  25. 126 points, 1 submission: RufusTheFirefly
    1. Everytime I try to investigate the technology behind Cardano(Ada), I come across the words "scientific" and "peer-reviewed" over and over but almost no actual details. Can someone fill how this coin actually works and where they are in development? (126 points, 49 comments)
  26. 112 points, 1 submission: rocksolid77
    1. Can we have a real debate about the Bitcoin scaling issue? (112 points, 89 comments)
  27. 110 points, 4 submissions: kelluk
    1. What one can learn from browsing 30 million Ethereum addresses (72 points, 21 comments)
    2. I wanted to categorize all coins/tokens, and this is my proposal (23 points, 33 comments)
    3. Should whitepapers be understood by ordinary people? (10 points, 41 comments)
    4. Querying the Ethereum blockchain: how to & what to? (5 points, 5 comments)
  28. 107 points, 1 submission: NewDietTrend
    1. Outside of currency and voting, blockchain is awful and shouldnt be used. Can anyone explain where blockchain is worth the cost? (107 points, 166 comments)
  29. 105 points, 1 submission: insette
    1. /CryptoTech PSA: there are broadly TWO TYPES of Decentralized Exchanges. Which type are you investing in? (105 points, 55 comments)
  30. 103 points, 3 submissions: dtheme
    1. How to accept crypto payments for digital downloads if you are a small business? Solutions, e-commerce sites are lacking (46 points, 38 comments)
    2. How many 24 letter seeds and "Bitcoin" keys can there be? (34 points, 24 comments)
    3. Is there any reason why the big tech companies are not getting into crypto? (23 points, 36 comments)
  31. 103 points, 3 submissions: dvnielng
    1. Why do so many of these businesses need a token? (Unsure) (61 points, 86 comments)
    2. DAPPS - Only coins that have intrinsic value? Ethereum , Neo? (31 points, 10 comments)
    3. How could blockchain work for expensive purchases/escrow? (11 points, 2 comments)
  32. 101 points, 1 submission: kickso
    1. Is NANO everything it says it is? (101 points, 96 comments)
  33. 98 points, 3 submissions: heart_mind_body
    1. How can we breathe some life into this sub? (56 points, 22 comments)
    2. Can anyone give an example for a technology that provides a "public permissioned blockchain"? (28 points, 16 comments)
    3. Can we do a discussion on ICON and "clusters of private chains connected to a public chain" ? (14 points, 13 comments)
  34. 97 points, 8 submissions: kelraku
    1. Thoughts on Mimblewimble? (23 points, 13 comments)
    2. Has anyone looked at the lelantus protocol? (18 points, 6 comments)
    3. How much control do developers have over the coins (18 points, 6 comments)
    4. Lesser known protocols? (11 points, 17 comments)
    5. Zerocoin and Blockchain Analysis (9 points, 5 comments)
    6. Zerocoin vs Cryptonote (7 points, 14 comments)
    7. Lightning network privacy (6 points, 13 comments)
    8. Integrity of the DAG (5 points, 17 comments)
  35. 96 points, 6 submissions: blockstasy
    1. How to Get to One Million Devs (32 points, 12 comments)
    2. The Decade in Blockchain — 2010 to 2020 in Review (27 points, 4 comments)
    3. Ethereum by the Numbers – The Year of 2019 (26 points, 9 comments)
    4. Knowledge Drop: Mining and the role it plays with the Ethereum blockchain (5 points, 0 comments)
    5. A great article that explains Ethereum’s Muir Glacier Update (4 points, 0 comments)
    6. Youtube Silences Crypto Community (2 points, 6 comments)
  36. 93 points, 3 submissions: OneOverNever
    1. Which is the last WHITE PAPER you've read that's truly impacted you? (77 points, 81 comments)
    2. [CMV] Bitcoin's intrinsic technological value. (14 points, 29 comments)
    3. What are some weak points that still hold XVG back from becoming a top player in crypto? (Technically speaking, not marketing and etc.) (2 points, 19 comments)
  37. 93 points, 3 submissions: ryano-ark
    1. (ARK) ACES Completes Integration of ARK Channels for Two-way Transfers for Easy ICOs When Paired With ARK Deployer (Push-Button-Blockchains) (57 points, 5 comments)
    2. (ARK) ACES Releases Fast (Ansible) Deployments for all ACES Applications. (23 points, 4 comments)
    3. A Future of Cryptocurrencies and Blockchains (13 points, 3 comments)
  38. 92 points, 2 submissions: BobUltra
    1. Our blockchains are all centralized! (51 points, 34 comments)
    2. List of qualities needed to dethrone Bitcoin. (41 points, 43 comments)
  39. 90 points, 1 submission: refreshx2
    1. CMV: It doesn't make sense for (crypto)companies to create coins linked to their tech (90 points, 18 comments)
  40. 89 points, 1 submission: perceptron01
    1. What does Nano do better than Steem? (89 points, 55 comments)
  41. 87 points, 1 submission: Shuk
    1. How does one begin to develop an employable skill in blockchain development? (87 points, 25 comments)
  42. 87 points, 1 submission: conorohiggins
    1. I spent three weeks researching and writing a huge guide to stablecoins. Enjoy! (87 points, 36 comments)
  43. 86 points, 1 submission: Bacon_Hero
    1. ELI5: Why did it take so long for blockchain technology to be created? (86 points, 66 comments)
  44. 85 points, 3 submissions: theFoot58
    1. If crypto now is like 'the Internet' of the past, where are we? (65 points, 53 comments)
    2. If the Internet had its Genesis Block, what would it be? (14 points, 9 comments)
    3. Coin grouping - ruby and CryptoCompare API (6 points, 1 comment)
  45. 85 points, 1 submission: youngm2
    1. Which decentralised exchange has the most promise for 2018? (85 points, 89 comments)
  46. 84 points, 4 submissions: bLbGoldeN
    1. On Mass Adoption of Cryptocurrencies (28 points, 68 comments)
    2. Join the Bloom team for our first tech AMA tomorrow (Tuesday, March 13th) at 7 PM GMT! (23 points, 2 comments)
    3. Join the Decred team for an AMA - Friday, June 1st from 19:00 to 22:00 UTC (17 points, 10 comments)
    4. Join the district0x team for an AMA Monday, April 2nd at 5:00 PM (GMT) (16 points, 0 comments)
  47. 82 points, 2 submissions: SubsequentDownfall
    1. Has a 51% attack ever been witnessed? (45 points, 46 comments)
    2. Is a DAG coin like RaiBlocks able to be private like Monero? (37 points, 40 comments)
  48. 82 points, 2 submissions: guidre
    1. Tron and other source Code (42 points, 24 comments)
    2. Why Will companies adopt blockchain, the user interface is complex and i'm not sure that many companies want all their internal dealings made public. (40 points, 19 comments)
  49. 81 points, 4 submissions: solar128
    1. New Atomic Swap Tools Released (35 points, 4 comments)
    2. Using Blockchain to make a censorship-resistant Reddit (28 points, 14 comments)
    3. Best security practices for addressing Spectre & Meltdown (13 points, 0 comments)
    4. Influence of on-chain governance weighted by wealth - good or bad? (5 points, 2 comments)
  50. 81 points, 2 submissions: Blockchainsapiens
    1. Blockchain study finds 0.00% success rate and vendors don't call back when asked for evidence (47 points, 30 comments)
    2. The elephant in the room: would the public ever use a volatile currency over a stable currency? (34 points, 45 comments)
  51. 81 points, 1 submission: Mycryptopedia
    1. Understanding the Tech Behind RaiBlocks (81 points, 7 comments)
  52. 81 points, 1 submission: davidvanbeveren
    1. Article thoroughly analysing / comparing IOTA and RaiBlocks (x-post /CryptoCurrency) (81 points, 10 comments)
  53. 77 points, 4 submissions: DeleteMyOldAccount
    1. HD Wallets Explained: What they are, and how to make them coin agnostic (28 points, 11 comments)
    2. Bitcoin Cash May 15th fork (23 points, 22 comments)
    3. So you want to build a Bitcoin HD wallet? Part 1 (23 points, 3 comments)
    4. Applications of Blockchain in Supply Chain (3 points, 9 comments)
  54. 76 points, 3 submissions: kryptofinger
    1. Why would anyone bother using any DPOS coins for dapps like Eos over normal systems like AWS? (44 points, 104 comments)
    2. Could a state backed privacy coin work? (22 points, 32 comments)
    3. Thoughts on Elastos? (10 points, 8 comments)
  55. 76 points, 1 submission: francohab
    1. 55% of the Nano representative nodes are "official representatives", presumably held by developers. How big of an issue is that? (76 points, 46 comments)
  56. 75 points, 2 submissions: MerkleChainsaw
    1. The biggest challenge for cryptocurrencies and how to mitigate it (73 points, 37 comments)
    2. Short and long term design tradeoffs in crypto (2 points, 2 comments)
  57. 75 points, 1 submission: jatsignwork
    1. Raiblocks & Spam (75 points, 60 comments)
  58. 74 points, 1 submission: behindtext
    1. Hello, this is Jake Yocom-Piatt. Ask me anything about Decred! (74 points, 49 comments)
  59. 73 points, 2 submissions: TexasRadical83
    1. Why use a new "currency" at all? (40 points, 48 comments)
    2. Why are big price increases for crypto a good thing? (33 points, 41 comments)

Top Commenters

  1. Neophyte- (1649 points, 746 comments)
  2. ndha1995 (583 points, 98 comments)
  3. turtleflax (406 points, 116 comments)
  4. senzheng (326 points, 193 comments)
  5. holomntn (294 points, 40 comments)
  6. manly_ (286 points, 43 comments)
  7. signos_de_admiracion (250 points, 18 comments)
  8. fgiveme (231 points, 77 comments)
  9. crypto_kang (222 points, 45 comments)
  10. jatsignwork (220 points, 37 comments)
  11. GainsLean (218 points, 76 comments)
  12. benthecarman (211 points, 48 comments)
  13. rockyrainy (200 points, 39 comments)
  14. hungryforitalianfood (197 points, 58 comments)
  15. rocksolid77 (190 points, 20 comments)
  16. bannercoin (189 points, 11 comments)
  17. insette (181 points, 47 comments)
  18. DiogenicOrder (175 points, 41 comments)
  19. islanavarino (173 points, 51 comments)
  20. behindtext (172 points, 14 comments)
  21. takitus (171 points, 25 comments)
  22. sukitrebek (170 points, 42 comments)
  23. UnknownEssence (170 points, 31 comments)
  24. crypto_ha (170 points, 26 comments)
  25. AlexCoventry (167 points, 17 comments)
  26. DragonWhsiperer (165 points, 38 comments)
  27. stop-making-accounts (164 points, 57 comments)
  28. KnifeOfPi2 (157 points, 13 comments)
  29. Edgegasm (156 points, 42 comments)
  30. ippond (152 points, 15 comments)
  31. dontlikecomputers (151 points, 61 comments)
  32. QRCollector (150 points, 46 comments)
  33. alexrecuenco (145 points, 18 comments)
  34. BobUltra (144 points, 88 comments)
  35. SpamCamel (135 points, 22 comments)
  36. InterdisciplinaryHum (133 points, 107 comments)
  37. theglitteringone (132 points, 10 comments)
  38. ChocolateSunrise (128 points, 23 comments)
  39. PM_ME_UR_QUINES (125 points, 4 comments)
  40. narwhale111 (122 points, 15 comments)
  41. pepe_le_shoe (121 points, 47 comments)
  42. Darius510 (119 points, 39 comments)
  43. glen-hodl (118 points, 21 comments)
  44. HOG_ZADDY (117 points, 23 comments)
  45. coranos2 (116 points, 44 comments)
  46. etherenvoy (116 points, 15 comments)
  47. johnny_milkshakes (115 points, 55 comments)
  48. galan77 (115 points, 52 comments)
  49. hybridsole (113 points, 40 comments)
  50. funciton (113 points, 8 comments)
  51. Mr0ldy (110 points, 24 comments)
  52. Corm (109 points, 42 comments)
  53. cryptoscopia (109 points, 7 comments)
  54. ReportFromHell (106 points, 39 comments)
  55. broscientologist (105 points, 26 comments)
  56. straytjacquet (104 points, 28 comments)
  57. Quadling (101 points, 24 comments)
  58. BlockEnthusiast (101 points, 17 comments)
  59. thats_not_montana (99 points, 37 comments)
  60. TheRealMotherOfOP (98 points, 27 comments)
  61. yarauuta (96 points, 11 comments)
  62. pegasuspect93 (96 points, 1 comment)
  63. andrew_bao (93 points, 40 comments)
  64. samdotla (93 points, 6 comments)
  65. melodious_punk (91 points, 34 comments)
  66. Mquantum (91 points, 31 comments)
  67. TJ_Hooker15 (91 points, 27 comments)
  68. NoFaptain99 (91 points, 3 comments)
  69. ilielezi (87 points, 10 comments)
  70. Raapop (87 points, 2 comments)
  71. Allways_Wrong (86 points, 36 comments)
  72. bLbGoldeN (86 points, 19 comments)
  73. ResIpsaLoquiturrr (86 points, 15 comments)
  74. kabelman93 (85 points, 29 comments)
  75. no_pants_gamer (84 points, 9 comments)
  76. AnkurTechracers (83 points, 16 comments)
  77. ric2b (83 points, 11 comments)
  78. Big_Goose (83 points, 10 comments)
  79. Lifeistooshor1 (82 points, 21 comments)
  80. vornth (82 points, 11 comments)
  81. Sargos (81 points, 25 comments)
  82. refreshx2 (81 points, 16 comments)
  83. Qwahzi (78 points, 27 comments)
  84. StupidRandomGuy (77 points, 35 comments)
  85. WikiTextBot (77 points, 24 comments)
  86. SnootyEuropean (77 points, 5 comments)
  87. cryptogainz (76 points, 14 comments)
  88. frequentlywrong (76 points, 4 comments)
  89. the_defiant (76 points, 4 comments)
  90. BrangdonJ (75 points, 28 comments)
  91. hendrik_v (75 points, 7 comments)
  92. solar128 (74 points, 18 comments)
  93. foobazzler (74 points, 8 comments)
  94. ginger_beer_m (73 points, 35 comments)
  95. kAhmij (73 points, 25 comments)
  96. DeleteMyOldAccount (73 points, 20 comments)
  97. sn0wr4in (73 points, 9 comments)
  98. Dyslectic_Sabreur (72 points, 5 comments)
  99. X7spyWqcRY (71 points, 8 comments)
  100. Krapser (70 points, 5 comments)

Top Submissions

  1. A Guided Reading of Bitcoin’s Original White Paper by Realness100 (202 points, 10 comments)
  2. From a technical standpoint: Why does every blockchain projects need their own coins? by HSPremier (181 points, 50 comments)
  3. Bitcoin Gold hit by Double Spend Attack (51% attack). The Attacker reversed 22 blocks. by rockyrainy (179 points, 102 comments)
  4. Why white papers in crypto world are so unprofessional? by ilielezi (175 points, 88 comments)
  5. My brief observation of most common Consensus Algorithms by tracyspacygo (159 points, 49 comments)
  6. Proof-of-Approval: Stake Based, 1 Block Finality & History Attack Defense by shunsaitakahashi (147 points, 4 comments)
  7. "Do you need a Blockchain?" - this paper is fantastic, everyone should read this before evaluating a coin and if requires a block chain to solve a solution the coin is promising to solve. by Neophyte- (136 points, 41 comments)
  8. Technical comparison of LIGHTNING vs TANGLE vs HASHGRAPH vs NANO by Qwahzi (133 points, 37 comments)
  9. Everytime I try to investigate the technology behind Cardano(Ada), I come across the words "scientific" and "peer-reviewed" over and over but almost no actual details. Can someone fill how this coin actually works and where they are in development? by RufusTheFirefly (126 points, 49 comments)
  10. How do we change the culture around cryptocurrency? by FashionistaGuru (118 points, 54 comments)

Top Comments

  1. 160 points: holomntn's comment in ELI5: Why did it take so long for blockchain technology to be created?
  2. 121 points: KnifeOfPi2's comment in How do we change the culture around cryptocurrency?
  3. 105 points: theglitteringone's comment in Outside of currency and voting, blockchain is awful and shouldnt be used. Can anyone explain where blockchain is worth the cost?
  4. 102 points: benthecarman's comment in If crypto now is like 'the Internet' of the past, where are we?
  5. 96 points: pegasuspect93's comment in If crypto now is like 'the Internet' of the past, where are we?
  6. 95 points: bannercoin's comment in Realistically, why would anybody expect the startup crypto platforms to beat out the corporate giants who are developing their own Blockchain as a Service (BaaS) solutions? Ex. IBM, SAP, JP Morgan...
  7. 83 points: AlexCoventry's comment in Ethereum private key with all zeroes leads to an account with 5000$ on it
  8. 82 points: deleted's comment in Is blockchain really useful ?
  9. 81 points: signos_de_admiracion's comment in Why white papers in crypto world are so unprofessional?
  10. 78 points: NoFaptain99's comment in Why do so many of these businesses need a token? (Unsure)
Generated with BBoe's Subreddit Stats
submitted by subreddit_stats to subreddit_stats [link] [comments]

Best $100-$300 FPGA development board in 2018?

Hello, I’ve been trying to decide on a FPGA development board, and have only been able to find posts and Reddit threads from 4-5 years ago. So I wanted to start a new thread and ask about the best “mid-range” FGPA development board in 2018. (Price range $100-$300.)
I started with this Quora answer about FPGA boards, from 2013. The Altera DE1 sounded good. Then I looked through the Terasic DE boards.
Then I found this Reddit thread from 2014, asking about the DE1-SoC vs the Cyclone V GX Starter Kit: https://www.reddit.com/FPGA/comments/1xsk6w/cyclone_v_gx_starter_kit_vs_de1soc_board/‬ (I was also leaning towards the DE1-SoC.)
Anyway, I thought I better ask here, because there are probably some new things to be aware of in 2018.
I’m completely new to FPGAs and VHDL, but I have experience with electronics/microcontrollers/programming. My goal is to start with some basic soft-core processors. I want to get some C / Rust programs compiling and running on my own CPU designs. I also want to play around with different instruction sets, and maybe start experimenting with asynchronous circuits (e.g. clock-less CPUs)
Also I don’t know if this is possible, but I’d like to experiment with ternary computing, or work with analog signals instead of purely digital logic. EDIT: I just realized that you would call those FPAAs, i.e. “analog” instead of “gate”. Would be cool if there was a dev board that also had an FPAA, but no problem if not.
EDIT 2: I also realized why "analog signals on an FPGA" doesn't make any sense, because of how LUTs work. They emulate boolean logic with a lookup table, and the table can only store 0s and 1s. So there's no way to emulate a transistor in an intermediate state. I'll just have play around with some transistors on a breadboard.
UPDATE: I've put together a table with some of the best options:
Board Maker Chip LUTs Price SoC? Features
icoBoard Lattice iCE40-HX8K 7,680 $100 Sort of A very simple FPGA development board that plugs into a Raspberry Pi, so you have a "backup" hard-core CPU that can control networking, etc. Supports a huge range of pmod accessories. You can write a program/circuit so that the Raspberry Pi CPU and the FPGA work together, similar to a SoC. Proprietary bitstream is fully reverse engineered and supported by Project IceStorm, and there is an open-source toolchain that can compile your hardware design to bitstream. Has everything you need to start experimenting with FPGAs.
iCE40-HX8K Breakout Board Lattice iCE40-HX8K-CT256 7,680 $49 No 8 LEDs, 8 switches. Very similar to icoBoard, but no Raspberry Pi or pmod accessories.
iCE40 UltraPlus Lattice iCE40 UltraPlus FPGA 5280 $99 No Chip specs. 4 switchable FPGAs, and a rechargeable battery. Bluetooth module, LCD Display (240 x 240 RGB), RGB LED, microphones, audio output, compass, pressure, gyro, accelerometer.
Go Board Lattice ICE40 HX1K FPGA 1280 $65 No 4 LEDs, 4 buttons, Dual 7-Segment LED Display, VGA, 25 MHz on-board clock, 1 Mb Flash.
snickerdoodle Xilinx Zynq 7010 28K $95 Yes Xilinx Zynq 7-Series SoC - ARM Cortex-A9 processor, and Artix-7 FPGA. 125 IO pins. 1GB DDR2 RAM. Texas Instruments WiLink 8 wireless module for 802.11n Wi-Fi and Bluetooth 4.1. No LEDs or buttons, but easy to wire up your own on a breadboard. If you want to use a baseboard, you'll need a snickerdoodle black ($195) with the pins in the "down" orientation. (E.g. The "breakyBreaky breakout board" ($49) or piSmasher SBC ($195)). The snickerdoodle one only comes with pins in the "up" orientation and doesn't support any baseboards. But you can still plug the jumpers into the pins and wire up things on a breadboard.
numato Mimas A7 Xilinx Artix 7 52K $149 No 2Gb DDR3 RAM. Gigabit Ethernet. HDMI IN/OUT. 100MHz LVDS oscillator. 80 IOs. 7-segment display, LEDs, buttons. (Found in this Reddit thread.)
Ultra96 Xilinx Zynq UltraScale+ ZU3EG 154K $249 Yes Has one of the latest Xilinx SoCs. 2 GB (512M x32) LPDDR4 Memory. Wi-Fi / Bluetooth. Mini DisplayPort. 1x USB 3.0 type Micro-B, 2x USB 3.0 Type A. Audio I/O. Four user-controllable LEDs. No buttons and limited LEDs, but easy to wire up your own on a breadboard
Nexys A7-100T Xilinx Artix 7 15,850 $265 No . 128MiB DDR2 RAM. Ethernet port, PWM audio output, accelerometer, PDM microphone, microphone, etc. 16 switches, 16 LEDs. 7 segment displays. USB HID Host for mice, keyboards and memory sticks.
Zybo Z7-10 Xilinx Zynq 7010 17,600 $199 Yes Xilinx Zynq 7000 SoC (ARM Cortex-A9, 7-series FPGA.) 1 GB DDR3 RAM. A few switches, push buttons, and LEDs. USB and Ethernet. Audio in/out ports. HDMI source + sink with CEC. 8 Total Processor I/O, 40 Total FPGA I/O. Also a faster version for $299 (Zybo Z7-20).
Arty A7 Xilinx Artix 7 15K $119 No 256MB DDR3L. 10/100 Mbps Ethernet. A few switches, buttons, LEDs.
DE10-Standard (specs) Altera Cyclone V 110K $350 Yes Dual-core Cortex-A9 processor. Lots of buttons, LEDs, and other peripherals.
DE10-Nano Altera Cyclone V 110K $130 Yes Same as DE10-Standard, but not as many peripherals, buttons, LEDs, etc.

Winner:

icoBoard ($100). (Buy it here.)
The icoBoard plugs into a Raspberry Pi, so it's similar to having a SoC. The iCE40-HX8K chip comes with 7,680 LUTs (logic elements.) This means that after you learn the basics and create some simple circuits, you'll also have enough logic elements to run the VexRiscv soft-core CPU (the lightweight Murax SoC.)
The icoBoard also supports a huge range of pluggable pmod accessories:
You can pick whatever peripherals you're interested in, and buy some more in the future.
Every FPGA vendor keeps their bitstream format secret. (Here's a Hacker News discussion about it.) The iCE40-HX8K bitstream has been fully reverse engineered by Project IceStorm, and there is an open-source set of tools that can compile Verilog to iCE40 bitstream.
This means that you have the freedom to do some crazy experiments, like:
You don't really have the same freedom to explore these things with Xilinx or Altera FPGAs. (Especially asynchronous circuits.)

Links:

Second Place:

iCE40-HX8K Breakout Board ($49)

Third Place:

numato Mimas A7 ($149).
An excellent development board with a Xilinx Artix 7 FPGA, so you can play with a bigger / faster FPGA and run a full RISC-V soft-core with all the options enabled, and a much higher clock speed. (The iCE40 FPGAs are a bit slow and small.)
Note: I've changed my mind several times as I learned new things. Here's some of my previous thoughts.

What did I buy?

I ordered a iCE40-HX8K Breakout Board to try out the IceStorm open source tooling. (I would have ordered an icoBoard if I had found it earlier.) I also bought a numato Mimas A7 so that I could experiment with the Artix 7 FPGA and Xilinx software (Vivado Design Suite.)

Questions

What can I do with an FPGA? / How many LUTs do I need?

submitted by ndbroadbent to FPGA [link] [comments]

Subreddit Stats: ItalyInformatica top posts from 2016-08-25 to 2019-02-25 09:37 PDT

Period: 914.09 days
Submissions Comments
Total 1000 14232
Rate (per day) 1.09 15.57
Unique Redditors 449 1815
Combined Score 19223 38406

Top Submitters' Top Submissions

  1. 935 points, 46 submissions: fen0x
    1. Ho trovato questo su un sito di un'azienda che fa web-marketing e mi ha fatto sorridere (122 points, 2 comments)
    2. Then... (73 points, 1 comment)
    3. Pubblicato exploit per grave vulnerabilità nel kernel Linux (46 points, 2 comments)
    4. Arrestato per truffa il capo di Eolo, uso illecito di frequenze non assegnate (44 points, 8 comments)
    5. Un saluto al sub dalla Mecca del nerdismo mondiale (35 points, 14 comments)
    6. Ma quale coding, a scuola serve la vera informatica: per innovare il Paese (34 points, 48 comments)
    7. Informatica, il coding non basta. Formeremmo solo operai digitali (33 points, 47 comments)
    8. Difesa e attacco a Las Vegas, sfida tra hacker da tutto il mondo. Italiani favoriti (32 points, 6 comments)
    9. [Questi mi pare di conoscerli] Giovani e breakdancer, ecco la nazionale italiana di hacker che ci difenderà nella guerra informatica (30 points, 2 comments)
    10. Una collezione di bash script per gli usi più disparati (29 points, 5 comments)
  2. 445 points, 23 submissions: Mte90
    1. Wikipedia in Italiano è chiusa per la legge sul copyright europea! (66 points, 3 comments)
    2. How I developed a captcha cracker for my University's website (40 points, 0 comments)
    3. Italian Anti-Corruption Authority (ANAC) Adopts Onion Services (31 points, 1 comment)
    4. Come Firefox è tornato ad essere veloce e meglio di prima [Inglese] (25 points, 43 comments)
    5. Siti italiani che salvano la tua password in chiaro o la inviano via email [3 giorni dopo] (25 points, 25 comments)
    6. Sono Mte90 alias Daniele Scasciafratte e siccome mi annoiavo ho deciso di diventare un contributor open source, AMA! (24 points, 50 comments)
    7. Cos'è la licenza EUPL e perché dovresti sapere della sua esistenza - Industria Italiana del Software Libero (23 points, 7 comments)
    8. Come contribuire alla comunità open source? - Industria Italiana del Software Libero (21 points, 5 comments)
    9. Industria Italiana del Software Libero aderisce alla campagna "Public Money, Public Code" (20 points, 0 comments)
    10. Il buono, il brutto e il cattivo #digitale — AD 2018 era #postPiacentini (19 points, 1 comment)
  3. 325 points, 20 submissions: Jianlucah
    1. [timendum] I testi generati, ovvero le catene di Markov (29 points, 18 comments)
    2. [denvit, blackdev1l, CapacitorSet] L’ascesa di Mastodon, il social network FOSS e decentralizzato (26 points, 11 comments)
    3. [zolixes] Crackare password? Facciamolo! (24 points, 6 comments)
    4. Dopo Stockisti chiuso anche Taocomputer: evasione di 2,5 milioni per il sito triestino (21 points, 16 comments)
    5. TL;DR inizia così (20 points, 20 comments)
    6. [GTKplusplus] La stampa 3D in ambito consumer, vista da un appassionato (20 points, 19 comments)
    7. Dopo qualche giorno di lavoro posso finalmente dirlo: è nato /ItalyGames! (19 points, 19 comments)
    8. E finalmente, Flash, ce lo siamo tolti di mezzo! (18 points, 16 comments)
    9. ULTIME NOTIZIE! TL;DR HA BISOGNO DI VOI! (15 points, 9 comments)
    10. [nierro] Clight, demone utente per linux scritto in C (15 points, 14 comments)
  4. 322 points, 16 submissions: vitalijzad
    1. Definizione di backup (92 points, 5 comments)
    2. Mickey Mouse Hacks a Military Computer (25 points, 3 comments)
    3. Quando ti mettono fretta prima di fare un rilascio in produzione (23 points, 14 comments)
    4. Ubuntu 18.04 sarà basato su Gnome e non Unity (23 points, 10 comments)
    5. We' waglio', vuoi venire a lavorare nella mia startup? (22 points, 5 comments)
    6. [ENG] Il quotidiano Guardian passa da MongoDB a PostgreSQL (19 points, 28 comments)
    7. Kotlin è ora ufficialmente supportato su Android come linguaggio di programmazione (17 points, 25 comments)
    8. Sedicenne irrompe nei server Apple e ruba 90 GB di dati sensibili (16 points, 6 comments)
    9. Spiò per 13 anni le vite degli altri via computer. Studente dell’Ohio accusato di aver infettato i dispositivi di centinaia di persone per spiarne ogni attività (16 points, 4 comments)
    10. WikiLeaks svela tre tool sviluppati dalla CIA per controllare Mac e Linux (16 points, 2 comments)
  5. 305 points, 11 submissions: mlazzarotto
    1. Massiccia lista di password violate rese pubbliche. Sono più di 1 miliardo di combinazioni username/password. (59 points, 45 comments)
    2. This is how the VPN works (53 points, 5 comments)
    3. Bohemian Rhapsody suonata da Floppy Drives e HDD (42 points, 3 comments)
    4. [x-post from /programmerhumor] Slick WPA2 workaround (35 points, 1 comment)
    5. Ci sono 9 milioni di telecamere Xiongmai accessibili a chiunque (25 points, 8 comments)
    6. Hard coding (20 points, 1 comment)
    7. Buon Sysadmin Day a tutti! (18 points, 0 comments)
    8. DuckDuck Go, cresce il motore di ricerca che non ti spia - Tom's Hardware (18 points, 3 comments)
    9. ODROID-GO è una console portatile programmabile e compatibile con Arduino (14 points, 4 comments)
    10. Amazon vuole le chiavi di casa. Ecco Key: il fattorino apre, consegna e se ne va - Repubblica.it (11 points, 11 comments)
  6. 277 points, 21 submissions: KarlFiabeschi
    1. You can't just code a gif (41 points, 7 comments)
    2. Public Money, Public Code (21 points, 9 comments)
    3. Rtv: Browse Reddit from your terminal (18 points, 11 comments)
    4. Why does man print "gimme gimme gimme" at 00:30? (16 points, 0 comments)
    5. Automate the Boring Stuff with Python (15 points, 3 comments)
    6. Best Vim Configuration and Plug-ins for Web Development (13 points, 3 comments)
    7. EU Will Vote on a Motion That Recommends Banning Kaspersky Products From Official EU Networks (13 points, 1 comment)
    8. Interactive Vim tutorial (13 points, 3 comments)
    9. AMD to consider Coreboot/Libreboot support. Contact AMD!!! Let them know there is demand. (x-post linux) (12 points, 2 comments)
    10. Pi-Hole - a black hole for internet adv (12 points, 16 comments)
  7. 262 points, 8 submissions: ilfabri
    1. Who really is AI. (85 points, 6 comments)
    2. Non ho resistito a questa stupidata. (80 points, 6 comments)
    3. Deploy in production made in RAI. (40 points, 4 comments)
    4. Referendum Lombardia, i tablet per il voto inutilizzabili per gli alunni: "Sono voting machine e pesano due chili" (17 points, 27 comments)
    5. [1969] Margaret Hamilton, lead software engineer of the Apollo Project, stands next to the code she wrote by hand and that was used to take humanity to the moon. (14 points, 3 comments)
    6. Che font usate nel vostro IDE? (10 points, 14 comments)
    7. Microsoft joins the Linux Foundation (9 points, 9 comments)
    8. Cosa ne pensate di Snap? (7 points, 8 comments)
  8. 253 points, 9 submissions: gioxx_it
    1. TNTVillage spiegato bene (le indagini, gli approfondimenti, ecc.) (111 points, 29 comments)
    2. Thunderbird offrirà tante nuove funzionalità nel corso del 2019 (36 points, 29 comments)
    3. How I hacked hundreds of companies through their helpdesk (27 points, 3 comments)
    4. Scoperte due app nel Play Store di Google che rubavano dati bancari (22 points, 18 comments)
    5. mkcert: valid HTTPS certificates for localhost (16 points, 3 comments)
    6. Di video compromettenti, riscatti Bitcoin e ondate di phishing (Aggiornato) (14 points, 1 comment)
    7. (Mail in stile "meglio tardi che mai"): 2014 Trakt Data Breach (11 points, 2 comments)
    8. Cinque fornitori di hosting web soffrivano di gravi vulnerabilità (8 points, 2 comments)
    9. Do Not Track: la funzionalità è morta e vi spieghiamo perché (8 points, 5 comments)
  9. 251 points, 5 submissions: timendum
    1. 10 year challenge per i siti (182 points, 10 comments)
    2. La nuova versione di Google Chrome potrebbe bloccare gli Ad Block (29 points, 75 comments)
    3. L'avvento del codice 2018 (14 points, 144 comments)
    4. SistemaTS: Inserimento spese sanitarie 730 in Python [OC] (14 points, 1 comment)
    5. C'è un effetto collaterale del Gdpr: rende Google sempre più forte (12 points, 8 comments)
  10. 249 points, 8 submissions: Chobeat
    1. Guida anti-inculata per laureandi italiani in Informatica e Ingegneria informatica (125 points, 9 comments)
    2. Il Machine Learning spiegato ad una giraffa (34 points, 24 comments)
    3. Aether: tipo Reddit, ma completamente Peer To Peer (rilasciata questo weekend la prima build) (32 points, 12 comments)
    4. I Tech Worker americani si stanno sindacalizzando (14 points, 0 comments)
    5. Il Machine Learning spiegato ad una giraffa (13 points, 9 comments)
    6. Gocce di Big Data: Spark (12 points, 1 comment)
    7. Our 2019 Developer Survey is Open to Coders Everywhere! - Stack Overflow Blog (12 points, 0 comments)
    8. Gocce di Big Data: Hadoop. Breve introduzione per neofiti al software che ha fatto la storia dei Big Data. (7 points, 5 comments)

Top Commenters

  1. fen0x (1149 points, 431 comments)
  2. alerighi (559 points, 241 comments)
  3. toyg (449 points, 160 comments)
  4. Chobeat (442 points, 110 comments)
  5. lormayna (421 points, 181 comments)
  6. JackHeuston (367 points, 99 comments)
  7. LelixSuper (333 points, 143 comments)
  8. lestofante (326 points, 143 comments)
  9. KarlFiabeschi (325 points, 149 comments)
  10. mhackeroni (320 points, 48 comments)

Top Submissions

  1. DOSTUPNO l'anti Whatsapp: una storia surreale by Lo_acker (233 points, 73 comments)
  2. [AMA] Siamo i mHACKeroni: la squadra italiana di hacker etici che quest'anno si è qualificata ed ha partecipato al DEF CON CTF. Ask Us Anything! by mhackeroni (206 points, 129 comments)
  3. 10 year challenge per i siti by timendum (182 points, 10 comments)
  4. Guida anti-inculata per laureandi italiani in Informatica e Ingegneria informatica by Chobeat (125 points, 9 comments)
  5. Ho trovato questo su un sito di un'azienda che fa web-marketing e mi ha fatto sorridere by fen0x (122 points, 2 comments)
  6. Una illusione ottica (con spiegazione e codice) by mapio (121 points, 8 comments)
  7. DOSTUPNO: Perché devilapp by d3vil401 (120 points, 49 comments)
  8. Un suggerimento: LAVATEVI! by napolux (113 points, 32 comments)
  9. TNTVillage spiegato bene (le indagini, gli approfondimenti, ecc.) by gioxx_it (111 points, 29 comments)
  10. Quanto guadagna ItalyInformatica? by fabio1618 (98 points, 47 comments)

Top Comments

  1. 80 points: zanzabros's comment in Come scrivete le vostre competenze con linguaggi di programmazione nel CV?
  2. 57 points: fen0x's comment in Apple controlla una scuola?
  3. 54 points: send_me_a_naked_pic's comment in Italia paese peggiore per sviluppatori
  4. 53 points: MonsieurCellophane's comment in Esistono programmatori non nerd?
  5. 52 points: GrimGrumbler's comment in Italia paese peggiore per sviluppatori
  6. 51 points: BifrostBOT's comment in La risposta di Dostupno (comunicato stampa in fondo all'articolo)
  7. 51 points: IceStationZebra93's comment in Oggi ho visto cose che voi umani... (pt2)
  8. 51 points: mhackeroni's comment in [AMA] Siamo i mHACKeroni: la squadra italiana di hacker etici che quest'anno si è qualificata ed ha partecipato al DEF CON CTF. Ask Us Anything!
  9. 48 points: edomindful's comment in Scoperte due app nel Play Store di Google che rubavano dati bancari
  10. 45 points: ajanty's comment in 90K al mese?
Generated with BBoe's Subreddit Stats
submitted by subreddit_stats to subreddit_stats [link] [comments]

Mercoin (MRN) La criptomoneda mas importante de la región Latinoamericana

Proyecto MERCOIN (2018)
WEBSITE Y CANALES
Canal de Telegram: http://t.me/mercointalk/

MERCOIN #MRN $MRN #MercoinUne #MERCOINSHOP

https://www.mercoin.org/ -- Pagina Web Oficial de Mercoin
https://mercointalk.org/ -- Foro Oficial de Mercoin
Canales oficiales:
https://www.facebook.com/Mercoin-MRN-125650824848037/
https://twitter.com/MercoinMRN
https://plus.google.com0/112887633537551844668
https://www.youtube.com/channel/UCRe..._t6vWR_9M1wAZg
https://ar.pinterest.com/mercoin/
https://www.instagram.com/mercoinweb/
MERCOIN es un proyecto lanzado en finales de Junio de 2017.
Basado en la tecnologia del algoritmo Scrypt
FILOSOFIA MERCOIN ( MRN ), Denominada así en honor al MERCOSUR, es una nueva altcoin que a diferencia de las demás criptomonedas, que salen al mundo y ya, fue pensada para que su uso sea destinado pura y exclusivamente en la región latinoamericana. Esto no quiere decir que se impidan transacciones al resto del globo, sino más bien que la región sea la primera en adoptarla como criptomoneda oficial. De eso se trata, de que haya nacido para que los ciudadanos de la comunidad tengan sentido de pertenencia en ella.
Dado que en Latinoamérica suelen sucederse medidas económicas de restricción y prohibición de divisas extranjeras, el equipo de MERCOIN consideró que una nueva criptodivisa, con una dificultad inferior a la del Bitcoin, podría imponerse de manera eficiente. Demás está decir, que los ciudadanos latinoamericanos, en su mayoría, no poseen recursos ni equipos de gran potencia como para minar BTC u otra moneda ya conocida de similares características, pero tampoco siente la razón de establecerse con una altcoin. Por este motivo y con esta nueva criptomoneda convocamos a la comunidad latinoamericana que quede atenta al lanzamiento del MRN porque si todos juntos creemos en esta altcoin, todos juntos le daremos el valor que le corresponde. Ni más ni menos. Depende de nosotros y por nosotros MERCOIN llegará a ser la moneda de gran valor en la región.
Proyecciones y objetivos -El equipo de desarrollo de MERCOIN.org junto con aquellos que se vayan integrando, tendrán como objetivo: -Establecer a MERCOIN como moneda regional, encontrándose en las principales plataformas de turismo virtual, sitios de compra venta, comercios gastronómicos y otra índole -Finalizar con el desarrollo del MERCOIN físico (MRN-F) el cual trabaja a través de un software permitiendo imprimir tanto en papel como en formato 3D (Moneda), el saldo que el usuario desee, contemplando la seguridad y desarrollando una encriptación que impida clones y/o duplicados. -Desarrollar plataformas de pago innovadoras y prácticas auto gestionadas, entre ellas la MRN card y anillo MRN. Ambos trabajarán con tecnología NFC (por cercanía) y será autogestionada por el usuario. Es decir, cada individuo podrá realizar la carga del saldo que desee en su tarjeta sin intermediarios. -Desarrollar equipos de minería con hardware de bajo costo y de bajo consumo con gran eficiencia y rendimiento, basados en las tarjetas Udoo x86 starter y Ultra. -Financiar desarrollos tecnológicos que contribuyan al bien de la comunidad y el medio ambiente.
Principales características MERCOIN está basado en el algoritmo POW/POS Scrypt.
Permite su minería a través de ordenadores de bajo recursos por medio de CPU y tambien la minería por GPU
Es multiplataforma (Mac, Windows, Linux) proximamente: Android y IOs.
Permite el formato papel y moneda 3D para quienes prefieren el formato físico por sobre el virtual. [2]
Se la podrá encontrar en las principales plataformas de cambio (exchange) y sitios de turismo y compras online, entre otros.
DATOS TECNICOS
Nombre: MERCOIN Ticker / Abreviatura: MRN Algoritmo: Scrypt Tipo: Pow / PoS Letra: M Máximo suministro: 100.000.000 (Max. Supply) Preminado: 20% (10% stake 10% ICO) Recompensa del bloque POW: 2 Puerto RCP: 23880 Puerto P2P: 23879 Ultimo bloque POW: 100000 Porcentaje PoS: 5% anual Tiempo minimo para stake: 8 hs
(a) - Consulte políticas de emisión en el whitepaper
WHITEPAPER https://drive.google.com/file/d/1aHErn3PtSLEzsScAv2nOcXUdEwJcVRpm/view
VERSIONES
Mercoin 1.0 (Cryptonote) Mercoin 1.2 (Nist5) Mercoin 1.3 (Scrypt) Mercoin 1.4 (Scrypt) -el unico cambio fue en parametros de recompensa- Mercoin 1.5 (Scrypt) -cambios en parametros y entorno grafico-
Lea más https://wiki.mercoin.org//versiones
MINERIA La mineria de MERCOIN es un recurso fundamental para sostener el funcionamiento de nuestra red, entérate como leyendo el articulo
Leer más https://wiki.mercoin.org//mineria
DESARROLLOS Mercoinshop Plataforma web integramente creada para el intercambio de bienes y servicios con MERCOIN
Lea más https://wiki.mercoin.org//mercoin-shop
Juegos / Games La comunidad MERCOIN (MRN) tambien cuenta con juegos para ocio y adquirir algunos MRN si es que la suerte está de tu lado.
Lea más https://wiki.mercoin.org//juegos
MercoinOS Sistema operativo propio de MERCOIN.org basado en una distro de linux para Raspberry (Pixel)
Lea más https://wiki.mercoin.org//mercoin-os
RECURSOS Codigo fuente / Source https://github.com/MERCOINMRN/Mercoin
Monederos / Wallets Por favor para informacion detallada sobre los monederos/wallets disponibles oficiales de MERCOIN.org por favor le el articulo del siguiente enlace:
Lea más https://wiki.mercoin.org//wallets-y-monederos
Guias de uso y videotutoriales Puede acceder a una completa lista de guias de ayuda paso a paso, escritas y tambien realizadas en video por el equipo oficial de MERCOIN.org
Lea más https://wiki.mercoin.org//guias-y-tutoriales
Explorador de bloques / Block explorer El explorador de bloques de MERCOIN es una aplicacion web de alta tecnologia que nos permite ver el estado en riempo real de la red. Tanto transacciones, como nodos conectados, mineria con su emision diaria y dificultad para obtener recompesas
http://explorer.mercoin.org:3001/
DIFUSION Y PRENSA Roadmap En el roadmap de MERCOIN podrá encontrar lo planificado por el equipo oficial, en sus comienzos. Objetivos propuestos, cuales fueron alcanzados y cuales aun se encuentran en pleno desarrollo.
Lea más https://wiki.mercoin.org//roadmap
FAQ (PREGUNTAS FRECUENTES) Si uste es un nuevo usuario de la comunidad MERCOIN le recomendamos leer el siguiente articulo publicado con las preguntas frecuentes
Lea más https://wiki.mercoin.org//faq
Bounties Campañas de recompensas https://bitcointalk.org/index.php?to...29#msg21173929
ENGLISH https://bitcointalk.org/index.php?topic=2102168.0
PORTUGUÉS https://bitcointalk.org/index.php?topic=2108990.0
submitted by MRNMercoin to u/MRNMercoin [link] [comments]

Bitcoin Core 0.10.0 released | Wladimir | Feb 16 2015

Wladimir on Feb 16 2015:
Bitcoin Core version 0.10.0 is now available from:
https://bitcoin.org/bin/0.10.0/
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
The whole distribution is also available as torrent:
https://bitcoin.org/bin/0.10.0/bitcoin-0.10.0.torrent
magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn;=0.10.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrading warning
Because release 0.10.0 makes use of headers-first synchronization and parallel
block download (see further), the block files and databases are not
backwards-compatible with older versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.
Notable changes

Faster synchronization
Bitcoin Core now uses 'headers-first synchronization'. This means that we first
ask peers for block headers (a total of 27 megabytes, as of December 2014) and
validate those. In a second stage, when the headers have been discovered, we
download the blocks. However, as we already know about the whole chain in
advance, the blocks can be downloaded in parallel from all available peers.
In practice, this means a much faster and more robust synchronization. On
recent hardware with a decent network link, it can be as little as 3 hours
for an initial full synchronization. You may notice a slower progress in the
very first few minutes, when headers are still being fetched and verified, but
it should gain speed afterwards.
A few RPCs were added/updated as a result of this:
  • getblockchaininfo now returns the number of validated headers in addition to
the number of validated blocks.
  • getpeerinfo lists both the number of blocks and headers we know we have in
common with each peer. While synchronizing, the heights of the blocks that we
have requested from peers (but haven't received yet) are also listed as
'inflight'.
  • A new RPC getchaintips lists all known branches of the block chain,
including those we only have headers for.
Transaction fee changes
This release automatically estimates how high a transaction fee (or how
high a priority) transactions require to be confirmed quickly. The default
settings will create transactions that confirm quickly; see the new
'txconfirmtarget' setting to control the tradeoff between fees and
confirmation times. Fees are added by default unless the 'sendfreetransactions'
setting is enabled.
Prior releases used hard-coded fees (and priorities), and would
sometimes create transactions that took a very long time to confirm.
Statistics used to estimate fees and priorities are saved in the
data directory in the fee_estimates.dat file just before
program shutdown, and are read in at startup.
New command line options for transaction fee changes:
  • -txconfirmtarget=n : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting
is over-ridden by the -paytxfee option.
  • -sendfreetransactions : Send transactions as zero-fee transactions if possible
(default: 0)
New RPC commands for fee estimation:
  • estimatefee nblocks : Returns approximate fee-per-1,000-bytes needed for
a transaction to begin confirmation within nblocks. Returns -1 if not enough
transactions have been observed to compute a good estimate.
  • estimatepriority nblocks : Returns approximate priority needed for
a zero-fee transaction to begin confirmation within nblocks. Returns -1 if not
enough free transactions have been observed to compute a good
estimate.
RPC access control changes
Subnet matching for the purpose of access control is now done
by matching the binary network address, instead of with string wildcard matching.
For the user this means that -rpcallowip takes a subnet specification, which can be
  • a single IP address (e.g. 1.2.3.4 or fe80::0012:3456:789a:bcde)
  • a network/CIDR (e.g. 1.2.3.0/24 or fe80::0000/64)
  • a network/netmask (e.g. 1.2.3.4/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address
matches one of them.
For example:
| 0.9.x and before | 0.10.x |
|--------------------------------------------|---------------------------------------|
| -rpcallowip=192.168.1.1 | -rpcallowip=192.168.1.1 (unchanged) |
| -rpcallowip=192.168.1.* | -rpcallowip=192.168.1.0/24 |
| -rpcallowip=192.168.* | -rpcallowip=192.168.0.0/16 |
| -rpcallowip=* (dangerous!) | -rpcallowip=::/0 (still dangerous!) |
Using wildcards will result in the rule being rejected with the following error in debug.log:
 Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). 
REST interface
A new HTTP API is exposed when running with the -rest flag, which allows
unauthenticated access to public node data.
It is served on the same port as RPC, but does not need a password, and uses
plain HTTP instead of JSON-RPC.
Assuming a local RPC server running on port 8332, it is possible to request:
In every case, EXT can be bin (for raw binary data), hex (for hex-encoded
binary) or json.
For more details, see the doc/REST-interface.md document in the repository.
RPC Server "Warm-Up" Mode
The RPC server is started earlier now, before most of the expensive
intialisations like loading the block index. It is available now almost
immediately after starting the process. However, until all initialisations
are done, it always returns an immediate error with code -28 to all calls.
This new behaviour can be useful for clients to know that a server is already
started and will be available soon (for instance, so that they do not
have to start it themselves).
Improved signing security
For 0.10 the security of signing against unusual attacks has been
improved by making the signatures constant time and deterministic.
This change is a result of switching signing to use libsecp256k1
instead of OpenSSL. Libsecp256k1 is a cryptographic library
optimized for the curve Bitcoin uses which was created by Bitcoin
Core developer Pieter Wuille.
There exist attacks[1] against most ECC implementations where an
attacker on shared virtual machine hardware could extract a private
key if they could cause a target to sign using the same key hundreds
of times. While using shared hosts and reusing keys are inadvisable
for other reasons, it's a better practice to avoid the exposure.
OpenSSL has code in their source repository for derandomization
and reduction in timing leaks that we've eagerly wanted to use for a
long time, but this functionality has still not made its
way into a released version of OpenSSL. Libsecp256k1 achieves
significantly stronger protection: As far as we're aware this is
the only deployed implementation of constant time signing for
the curve Bitcoin uses and we have reason to believe that
libsecp256k1 is better tested and more thoroughly reviewed
than the implementation in OpenSSL.
[1] https://eprint.iacr.org/2014/161.pdf
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know
all addresses (or scripts), even without the private keys.
This can be used to track payments without needing the private keys online on a
possibly vulnerable system. In addition, it can help for (manual) construction
of multisig transactions where you are only one of the signers.
One new RPC, importaddress, is added which functions similarly to
importprivkey, but instead takes an address or script (in hexadecimal) as
argument. After using it, outputs credited to this address or script are
considered to be received, and transactions consuming these outputs will be
considered to be sent.
The following RPCs have optional support for watch-only:
getbalance, listreceivedbyaddress, listreceivedbyaccount,
listtransactions, listaccounts, listsinceblock, gettransaction. See the
RPC documentation for those methods for more information.
Compared to using getrawtransaction, this mechanism does not require
-txindex, scales better, integrates better with the wallet, and is compatible
with future block chain pruning functionality. It does mean that all relevant
addresses need to added to the wallet before the payment, though.
Consensus library
Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library.
The purpose of this library is to make the verification functionality that is
critical to Bitcoin's consensus available to other applications, e.g. to language
bindings such as [python-bitcoinlib](https://pypi.python.org/pypi/python-bitcoinlib) or
alternative node implementations.
This library is called libbitcoinconsensus.so (or, .dll for Windows).
Its interface is defined in the C header [bitcoinconsensus.h](https://github.com/bitcoin/bitcoin/blob/0.10/src/script/bitcoinconsensus.h).
In its initial version the API includes two functions:
  • bitcoinconsensus_verify_script verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
  • bitcoinconsensus_version returns the API version, currently at an experimental 0
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface
for existing methods should remain stable.
Standard script rules relaxed for P2SH addresses
The IsStandard() rules have been almost completely removed for P2SH
redemption scripts, allowing applications to make use of any valid
script type, such as "n-of-m OR y", hash-locked oracle addresses, etc.
While the Bitcoin protocol has always supported these types of script,
actually using them on mainnet has been previously inconvenient as
standard Bitcoin Core nodes wouldn't relay them to miners, nor would
most miners include them in blocks they mined.
bitcoin-tx
It has been observed that many of the RPC functions offered by bitcoind are
"pure functions", and operate independently of the bitcoind wallet. This
included many of the RPC "raw transaction" API functions, such as
createrawtransaction.
bitcoin-tx is a newly introduced command line utility designed to enable easy
manipulation of bitcoin transactions. A summary of its operation may be
obtained via "bitcoin-tx --help" Transactions may be created or signed in a
manner similar to the RPC raw tx API. Transactions may be updated, deleting
inputs or outputs, or appending new inputs and outputs. Custom scripts may be
easily composed using a simple text notation, borrowed from the bitcoin test
suite.
This tool may be used for experimenting with new transaction types, signing
multi-party transactions, and many other uses. Long term, the goal is to
deprecate and remove "pure function" RPC API calls, as those do not require a
server round-trip to execute.
Other utilities "bitcoin-key" and "bitcoin-script" have been proposed, making
key and script operations easily accessible via command line.
Mining and relay policy enhancements
Bitcoin Core's block templates are now for version 3 blocks only, and any mining
software relying on its getblocktemplate must be updated in parallel to use
libblkmaker either version 0.4.2 or any version from 0.5.1 onward.
If you are solo mining, this will affect you the moment you upgrade Bitcoin
Core, which must be done prior to BIP66 achieving its 951/1001 status.
If you are mining with the stratum mining protocol: this does not affect you.
If you are mining with the getblocktemplate protocol to a pool: this will affect
you at the pool operator's discretion, which must be no later than BIP66
achieving its 951/1001 status.
The prioritisetransaction RPC method has been added to enable miners to
manipulate the priority of transactions on an individual basis.
Bitcoin Core now supports BIP 22 long polling, so mining software can be
notified immediately of new templates rather than having to poll periodically.
Support for BIP 23 block proposals is now available in Bitcoin Core's
getblocktemplate method. This enables miners to check the basic validity of
their next block before expending work on it, reducing risks of accidental
hardforks or mining invalid blocks.
Two new options to control mining policy:
  • -datacarrier=0/1 : Relay and mine "data carrier" (OP_RETURN) transactions
if this is 1.
  • -datacarriersize=n : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs.
The relay policy has changed to more properly implement the desired behavior of not
relaying free (or very low fee) transactions unless they have a priority above the
AllowFreeThreshold(), in which case they are relayed subject to the rate limiter.
BIP 66: strict DER encoding for signatures
Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new
consensus rule, which prohibits non-DER signatures. Such transactions have been
non-standard since Bitcoin v0.8.0 (released in February 2013), but were
technically still permitted inside blocks.
This change breaks the dependency on OpenSSL's signature parsing, and is
required if implementations would want to remove all of OpenSSL from the
consensus code.
The same miner-voting mechanism as in BIP 34 is used: when 751 out of a
sequence of 1001 blocks have version number 3 or higher, the new consensus
rule becomes active for those blocks. When 951 out of a sequence of 1001
blocks have version number 3 or higher, it becomes mandatory for all blocks.
Backward compatibility with current mining software is NOT provided, thus miners
should read the first paragraph of "Mining and relay policy enhancements" above.
0.10.0 Change log

Detailed release notes follow. This overview includes changes that affect external
behavior, not code moves, refactors or string updates.
RPC:
  • f923c07 Support IPv6 lookup in bitcoin-cli even when IPv6 only bound on localhost
  • b641c9c Fix addnode "onetry": Connect with OpenNetworkConnection
  • 171ca77 estimatefee / estimatepriority RPC methods
  • b750cf1 Remove cli functionality from bitcoind
  • f6984e8 Add "chain" to getmininginfo, improve help in getblockchaininfo
  • 99ddc6c Add nLocalServices info to RPC getinfo
  • cf0c47b Remove getwork() RPC call
  • 2a72d45 prioritisetransaction
  • e44fea5 Add an option -datacarrier to allow users to disable relaying/mining data carrier transactions
  • 2ec5a3d Prevent easy RPC memory exhaustion attack
  • d4640d7 Added argument to getbalance to include watchonly addresses and fixed errors in balance calculation
  • 83f3543 Added argument to listaccounts to include watchonly addresses
  • 952877e Showing 'involvesWatchonly' property for transactions returned by 'listtransactions' and 'listsinceblock'. It is only appended when the transaction involves a watchonly address
  • d7d5d23 Added argument to listtransactions and listsinceblock to include watchonly addresses
  • f87ba3d added includeWatchonly argument to 'gettransaction' because it affects balance calculation
  • 0fa2f88 added includedWatchonly argument to listreceivedbyaddress/...account
  • 6c37f7f getrawchangeaddress: fail when keypool exhausted and wallet locked
  • ff6a7af getblocktemplate: longpolling support
  • c4a321f Add peerid to getpeerinfo to allow correlation with the logs
  • 1b4568c Add vout to ListTransactions output
  • b33bd7a Implement "getchaintips" RPC command to monitor blockchain forks
  • 733177e Remove size limit in RPC client, keep it in server
  • 6b5b7cb Categorize rpc help overview
  • 6f2c26a Closely track mempool byte total. Add "getmempoolinfo" RPC
  • aa82795 Add detailed network info to getnetworkinfo RPC
  • 01094bd Don't reveal whether password is <20 or >20 characters in RPC
  • 57153d4 rpc: Compute number of confirmations of a block from block height
  • ff36cbe getnetworkinfo: export local node's client sub-version string
  • d14d7de SanitizeString: allow '(' and ')'
  • 31d6390 Fixed setaccount accepting foreign address
  • b5ec5fe update getnetworkinfo help with subversion
  • ad6e601 RPC additions after headers-first
  • 33dfbf5 rpc: Fix leveldb iterator leak, and flush before gettxoutsetinfo
  • 2aa6329 Enable customising node policy for datacarrier data size with a -datacarriersize option
  • f877aaa submitblock: Use a temporary CValidationState to determine accurately the outcome of ProcessBlock
  • e69a587 submitblock: Support for returning specific rejection reasons
  • af82884 Add "warmup mode" for RPC server
  • e2655e0 Add unauthenticated HTTP REST interface to public blockchain data
  • 683dc40 Disable SSLv3 (in favor of TLS) for the RPC client and server
  • 44b4c0d signrawtransaction: validate private key
  • 9765a50 Implement BIP 23 Block Proposal
  • f9de17e Add warning comment to getinfo
Command-line options:
  • ee21912 Use netmasks instead of wildcards for IP address matching
  • deb3572 Add -rpcbind option to allow binding RPC port on a specific interface
  • 96b733e Add -version option to get just the version
  • 1569353 Add -stopafterblockimport option
  • 77cbd46 Let -zapwallettxes recover transaction meta data
  • 1c750db remove -tor compatibility code (only allow -onion)
  • 4aaa017 rework help messages for fee-related options
  • 4278b1d Clarify error message when invalid -rpcallowip
  • 6b407e4 -datadir is now allowed in config files
  • bdd5b58 Add option -sysperms to disable 077 umask (create new files with system default umask)
  • cbe39a3 Add "bitcoin-tx" command line utility and supporting modules
  • dbca89b Trigger -alertnotify if network is upgrading without you
  • ad96e7c Make -reindex cope with out-of-order blocks
  • 16d5194 Skip reindexed blocks individually
  • ec01243 --tracerpc option for regression tests
  • f654f00 Change -genproclimit default to 1
  • 3c77714 Make -proxy set all network types, avoiding a connect leak
  • 57be955 Remove -printblock, -printblocktree, and -printblockindex
  • ad3d208 remove -maxorphanblocks config parameter since it is no longer functional
Block and transaction handling:
  • 7a0e84d ProcessGetData(): abort if a block file is missing from disk
  • 8c93bf4 LoadBlockIndexDB(): Require block db reindex if any blk*.dat files are missing
  • 77339e5 Get rid of the static chainMostWork (optimization)
  • 4e0eed8 Allow ActivateBestChain to release its lock on cs_main
  • 18e7216 Push cs_mains down in ProcessBlock
  • fa126ef Avoid undefined behavior using CFlatData in CScript serialization
  • 7f3b4e9 Relax IsStandard rules for pay-to-script-hash transactions
  • c9a0918 Add a skiplist to the CBlockIndex structure
  • bc42503 Use unordered_map for CCoinsViewCache with salted hash (optimization)
  • d4d3fbd Do not flush the cache after every block outside of IBD (optimization)
  • ad08d0b Bugfix: make CCoinsViewMemPool support pruned entries in underlying cache
  • 5734d4d Only remove actualy failed blocks from setBlockIndexValid
  • d70bc52 Rework block processing benchmark code
  • 714a3e6 Only keep setBlockIndexValid entries that are possible improvements
  • ea100c7 Reduce maximum coinscache size during verification (reduce memory usage)
  • 4fad8e6 Reject transactions with excessive numbers of sigops
  • b0875eb Allow BatchWrite to destroy its input, reducing copying (optimization)
  • 92bb6f2 Bypass reloading blocks from disk (optimization)
  • 2e28031 Perform CVerifyDB on pcoinsdbview instead of pcoinsTip (reduce memory usage)
  • ab15b2e Avoid copying undo data (optimization)
  • 341735e Headers-first synchronization
  • afc32c5 Fix rebuild-chainstate feature and improve its performance
  • e11b2ce Fix large reorgs
  • ed6d1a2 Keep information about all block files in memory
  • a48f2d6 Abstract context-dependent block checking from acceptance
  • 7e615f5 Fixed mempool sync after sending a transaction
  • 51ce901 Improve chainstate/blockindex disk writing policy
  • a206950 Introduce separate flushing modes
  • 9ec75c5 Add a locking mechanism to IsInitialBlockDownload to ensure it never goes from false to true
  • 868d041 Remove coinbase-dependant transactions during reorg
  • 723d12c Remove txn which are invalidated by coinbase maturity during reorg
  • 0cb8763 Check against MANDATORY flags prior to accepting to mempool
  • 8446262 Reject headers that build on an invalid parent
  • 008138c Bugfix: only track UTXO modification after lookup
P2P protocol and network code:
  • f80cffa Do not trigger a DoS ban if SCRIPT_VERIFY_NULLDUMMY fails
  • c30329a Add testnet DNS seed of Alex Kotenko
  • 45a4baf Add testnet DNS seed of Andreas Schildbach
  • f1920e8 Ping automatically every 2 minutes (unconditionally)
  • 806fd19 Allocate receive buffers in on the fly
  • 6ecf3ed Display unknown commands received
  • aa81564 Track peers' available blocks
  • caf6150 Use async name resolving to improve net thread responsiveness
  • 9f4da19 Use pong receive time rather than processing time
  • 0127a9b remove SOCKS4 support from core and GUI, use SOCKS5
  • 40f5cb8 Send rejects and apply DoS scoring for errors in direct block validation
  • dc942e6 Introduce whitelisted peers
  • c994d2e prevent SOCKET leak in BindListenPort()
  • a60120e Add built-in seeds for .onion
  • 60dc8e4 Allow -onlynet=onion to be used
  • 3a56de7 addrman: Do not propagate obviously poor addresses onto the network
  • 6050ab6 netbase: Make SOCKS5 negotiation interruptible
  • 604ee2a Remove tx from AlreadyAskedFor list once we receive it, not when we process it
  • efad808 Avoid reject message feedback loops
  • 71697f9 Separate protocol versioning from clientversion
  • 20a5f61 Don't relay alerts to peers before version negotiation
  • b4ee0bd Introduce preferred download peers
  • 845c86d Do not use third party services for IP detection
  • 12a49ca Limit the number of new addressses to accumulate
  • 35e408f Regard connection failures as attempt for addrman
  • a3a7317 Introduce 10 minute block download timeout
  • 3022e7d Require sufficent priority for relay of free transactions
  • 58fda4d Update seed IPs, based on bitcoin.sipa.be crawler data
  • 18021d0 Remove bitnodes.io from dnsseeds.
Validation:
  • 6fd7ef2 Also switch the (unused) verification code to low-s instead of even-s
  • 584a358 Do merkle root and txid duplicates check simultaneously
  • 217a5c9 When transaction outputs exceed inputs, show the offending amounts so as to aid debugging
  • f74fc9b Print input index when signature validation fails, to aid debugging
  • 6fd59ee script.h: set_vch() should shift a >32 bit value
  • d752ba8 Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) (test only)
  • 698c6ab Add SCRIPT_VERIFY_MINIMALDATA (BIP62 rules 3 and 4) (test only)
  • ab9edbd script: create sane error return codes for script validation and remove logging
  • 219a147 script: check ScriptError values in script tests
  • 0391423 Discourage NOPs reserved for soft-fork upgrades
  • 98b135f Make STRICTENC invalid pubkeys fail the script rather than the opcode
  • 307f7d4 Report script evaluation failures in log and reject messages
  • ace39db consensus: guard against openssl's new strict DER checks
  • 12b7c44 Improve robustness of DER recoding code
  • 76ce5c8 fail immediately on an empty signature
Build system:
  • f25e3ad Fix build in OS X 10.9
  • 65e8ba4 build: Switch to non-recursive make
  • 460b32d build: fix broken boost chrono check on some platforms
  • 9ce0774 build: Fix windows configure when using --with-qt-libdir
  • ea96475 build: Add mention of --disable-wallet to bdb48 error messages
  • 1dec09b depends: add shared dependency builder
  • c101c76 build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix
  • e432a5f build: add option for reducing exports (v2)
  • 6134b43 Fixing condition 'sabotaging' MSVC build
  • af0bd5e osx: fix signing to make Gatekeeper happy (again)
  • a7d1f03 build: fix dynamic boost check when --with-boost= is used
  • d5fd094 build: fix qt test build when libprotobuf is in a non-standard path
  • 2cf5f16 Add libbitcoinconsensus library
  • 914868a build: add a deterministic dmg signer
  • 2d375fe depends: bump openssl to 1.0.1k
  • b7a4ecc Build: Only check for boost when building code that requires it
Wallet:
  • b33d1f5 Use fee/priority estimates in wallet CreateTransaction
  • 4b7b1bb Sanity checks for estimates
  • c898846 Add support for watch-only addresses
  • d5087d1 Use script matching rather than destination matching for watch-only
  • d88af56 Fee fixes
  • a35b55b Dont run full check every time we decrypt wallet
  • 3a7c348 Fix make_change to not create half-satoshis
  • f606bb9 fix a possible memory leak in CWalletDB::Recover
  • 870da77 fix possible memory leaks in CWallet::EncryptWallet
  • ccca27a Watch-only fixes
  • 9b1627d [Wallet] Reduce minTxFee for transaction creation to 1000 satoshis
  • a53fd41 Deterministic signing
  • 15ad0b5 Apply AreSane() checks to the fees from the network
  • 11855c1 Enforce minRelayTxFee on wallet created tx and add a maxtxfee option
GUI:
  • c21c74b osx: Fix missing dock menu with qt5
  • b90711c Fix Transaction details shows wrong To:
  • 516053c Make links in 'About Bitcoin Core' clickable
  • bdc83e8 Ensure payment request network matches client network
  • 65f78a1 Add GUI view of peer information
  • 06a91d9 VerifyDB progress reporting
  • fe6bff2 Add BerkeleyDB version info to RPCConsole
  • b917555 PeerTableModel: Fix potential deadlock. #4296
  • dff0e3b Improve rpc console history behavior
  • 95a9383 Remove CENT-fee-rule from coin control completely
  • 56b07d2 Allow setting listen via GUI
  • d95ba75 Log messages with type>QtDebugMsg as non-debug
  • 8969828 New status bar Unit Display Control and related changes
  • 674c070 seed OpenSSL PNRG with Windows event data
  • 509f926 Payment request parsing on startup now only changes network if a valid network name is specified
  • acd432b Prevent balloon-spam after rescan
  • 7007402 Implement SI-style (thin space) thoudands separator
  • 91cce17 Use fixed-point arithmetic in amount spinbox
  • bdba2dd Remove an obscure option no-one cares about
  • bd0aa10 Replace the temporary file hack currently used to change Bitcoin-Qt's dock icon (OS X) with a buffer-based solution
  • 94e1b9e Re-work overviewpage UI
  • 8bfdc9a Better looking trayicon
  • b197bf3 disable tray interactions when client model set to 0
  • 1c5f0af Add column Watch-only to transactions list
  • 21f139b Fix tablet crash. closes #4854
  • e84843c Broken addresses on command line no longer trigger testnet
  • a49f11d Change splash screen to normal window
  • 1f9be98 Disable App Nap on OSX 10.9+
  • 27c3e91 Add proxy to options overridden if necessary
  • 4bd1185 Allow "emergency" shutdown during startup
  • d52f072 Don't show wallet options in the preferences menu when running with -disablewallet
  • 6093aa1 Qt: QProgressBar CPU-Issue workaround
  • 0ed9675 [Wallet] Add global boolean whether to send free transactions (default=true)
  • ed3e5e4 [Wallet] Add global boolean whether to pay at least the custom fee (default=true)
  • e7876b2 [Wallet] Prevent user from paying a non-sense fee
  • c1c9d5b Add Smartfee to GUI
  • e0a25c5 Make askpassphrase dialog behave more sanely
  • 94b362d On close of splashscreen interrupt verifyDB
  • b790d13 English translation update
  • 8543b0d Correct tooltip on address book page
Tests:
  • b41e594 Fix script test handling of empty scripts
  • d3a33fc Test CHECKMULTISIG with m == 0 and n == 0
  • 29c1749 Let tx (in)valid tests use any SCRIPT_VERIFY flag
  • 6380180 Add rejection of non-null CHECKMULTISIG dummy values
  • 21bf3d2 Add tests for BoostAsioToCNetAddr
  • b5ad5e7 Add Python test for -rpcbind and -rpcallowip
  • 9ec0306 Add CODESEPARATOFindAndDelete() tests
  • 75ebced Added many rpc wallet tests
  • 0193fb8 Allow multiple regression tests to run at once
  • 92a6220 Hook up sanity checks
  • 3820e01 Extend and move all crypto tests to crypto_tests.cpp
  • 3f9a019 added list/get received by address/ account tests
  • a90689f Remove timing-based signature cache unit test
  • 236982c Add skiplist unit tests
  • f4b00be Add CChain::GetLocator() unit test
  • b45a6e8 Add test for getblocktemplate longpolling
  • cdf305e Set -discover=0 in regtest framework
  • ed02282 additional test for OP_SIZE in script_valid.json
  • 0072d98 script tests: BOOLAND, BOOLOR decode to integer
  • 833ff16 script tests: values that overflow to 0 are true
  • 4cac5db script tests: value with trailing 0x00 is true
  • 89101c6 script test: test case for 5-byte bools
  • d2d9dc0 script tests: add tests for CHECKMULTISIG limits
  • d789386 Add "it works" test for bitcoin-tx
  • df4d61e Add bitcoin-tx tests
  • aa41ac2 Test IsPushOnly() with invalid push
  • 6022b5d Make script_{valid,invalid}.json validation flags configurable
  • 8138cbe Add automatic script test generation, and actual checksig tests
  • ed27e53 Add coins_tests with a large randomized CCoinViewCache test
  • 9df9cf5 Make SCRIPT_VERIFY_STRICTENC compatible with BIP62
  • dcb9846 Extend getchaintips RPC test
  • 554147a Ensure MINIMALDATA invalid tests can only fail one way
  • dfeec18 Test every numeric-accepting opcode for correct handling of the numeric minimal encoding rule
  • 2b62e17 Clearly separate PUSHDATA and numeric argument MINIMALDATA tests
  • 16d78bd Add valid invert of invalid every numeric opcode tests
  • f635269 tests: enable alertnotify test for Windows
  • 7a41614 tests: allow rpc-tests to get filenames for bitcoind and bitcoin-cli from the environment
  • 5122ea7 tests: fix forknotify.py on windows
  • fa7f8cd tests: remove old pull-tester scripts
  • 7667850 tests: replace the old (unused since Travis) tests with new rpc test scripts
  • f4e0aef Do signature-s negation inside the tests
  • 1837987 Optimize -regtest setgenerate block generation
  • 2db4c8a Fix node ranges in the test framework
  • a8b2ce5 regression test only setmocktime RPC call
  • daf03e7 RPC tests: create initial chain with specific timestamps
  • 8656dbb Port/fix txnmall.sh regression test
  • ca81587 Test the exact order of CHECKMULTISIG sig/pubkey evaluation
  • 7357893 Prioritize and display -testsafemode status in UI
  • f321d6b Add key generation/verification to ECC sanity check
  • 132ea9b miner_tests: Disable checkpoints so they don't fail the subsidy-change test
  • bc6cb41 QA RPC tests: Add tests block block proposals
  • f67a9ce Use deterministically generated script tests
  • 11d7a7d [RPC] add rpc-test for http keep-alive (persistent connections)
  • 34318d7 RPC-test based on invalidateblock for mempool coinbase spends
  • 76ec867 Use actually valid transactions for script tests
  • c8589bf Add actual signature tests
  • e2677d7 Fix smartfees test for change to relay policy
  • 263b65e tests: run sanity checks in tests too
Miscellaneous:
  • 122549f Fix incorrect checkpoint data for testnet3
  • 5bd02cf Log used config file to debug.log on startup
  • 68ba85f Updated Debian example bitcoin.conf with config from wiki + removed some cruft and updated comments
  • e5ee8f0 Remove -beta suffix
  • 38405ac Add comment regarding experimental-use service bits
  • be873f6 Issue warning if collecting RandSeed data failed
  • 8ae973c Allocate more space if necessary in RandSeedAddPerfMon
  • 675bcd5 Correct comment for 15-of-15 p2sh script size
  • fda3fed libsecp256k1 integration
  • 2e36866 Show nodeid instead of addresses in log (for anonymity) unless otherwise requested
  • cd01a5e Enable paranoid corruption checks in LevelDB >= 1.16
  • 9365937 Add comment about never updating nTimeOffset past 199 samples
  • 403c1bf contrib: remove getwork-based pyminer (as getwork API call has been removed)
  • 0c3e101 contrib: Added systemd .service file in order to help distributions integrate bitcoind
  • 0a0878d doc: Add new DNSseed policy
  • 2887bff Update coding style and add .clang-format
  • 5cbda4f Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope
  • b4a72a7 contrib/linearize: split output files based on new-timestamp-year or max-file-size
  • e982b57 Use explicit fflush() instead of setvbuf()
  • 234bfbf contrib: Add init scripts and docs for Upstart and OpenRC
  • 01c2807 Add warning about the merkle-tree algorithm duplicate txid flaw
  • d6712db Also create pid file in non-daemon mode
  • 772ab0e contrib: use batched JSON-RPC in linarize-hashes (optimization)
  • 7ab4358 Update bash-completion for v0.10
  • 6e6a36c contrib: show pull # in prompt for github-merge script
  • 5b9f842 Upgrade leveldb to 1.18, make chainstate databases compatible between ARM and x86 (issue #2293)
  • 4e7c219 Catch UTXO set read errors and shutdown
  • 867c600 Catch LevelDB errors during flush
  • 06ca065 Fix CScriptID(const CScript& in) in empty script case
Credits

Thanks to everyone who contributed to this release:
  • 21E14
  • Adam Weiss
  • Aitor Pazos
  • Alexander Jeng
  • Alex Morcos
  • Alon Muroch
  • Andreas Schildbach
  • Andrew Poelstra
  • Andy Alness
  • Ashley Holman
  • Benedict Chan
  • Ben Holden-Crowther
  • Bryan Bishop
  • BtcDrak
  • Christian von Roques
  • Clinton Christian
  • Cory Fields
  • Cozz Lovan
  • daniel
  • Daniel Kraft
  • David Hill
  • Derek701
  • dexX7
  • dllud
  • Dominyk Tiller
  • Doug
  • elichai
  • elkingtowa
  • ENikS
  • Eric Shaw
  • Federico Bond
  • Francis GASCHET
  • Gavin Andresen
  • Giuseppe Mazzotta
  • Glenn Willen
  • Gregory Maxwell
  • gubatron
  • HarryWu
  • himynameismartin
  • Huang Le
  • Ian Carroll
  • imharrywu
  • Jameson Lopp
  • Janusz Lenar
  • JaSK
  • Jeff Garzik
  • JL2035
  • Johnathan Corgan
  • Jonas Schnelli
  • jtimon
  • Julian Haight
  • Kamil Domanski
  • kazcw
  • kevin
  • kiwigb
  • Kosta Zertsekel
  • LongShao007
  • Luke Dashjr
  • Mark Friedenbach
  • Mathy Vanvoorden
  • Matt Corallo
  • Matthew Bogosian
  • Micha
  • Michael Ford
  • Mike Hearn
  • mrbandrews
  • mruddy
  • ntrgn
  • Otto Allmendinger
  • paveljanik
  • Pavel Vasin
  • Peter Todd
  • phantomcircuit
  • Philip Kaufmann
  • Pieter Wuille
  • pryds
  • randy-waterhouse
  • R E Broadley
  • Rose Toomey
  • Ross Nicoll
  • Roy Badami
  • Ruben Dario Ponticelli
  • Rune K. Svendsen
  • Ryan X. Charles
  • Saivann
  • sandakersmann
  • SergioDemianLerner
  • shshshsh
  • sinetek
  • Stuart Cardall
  • Suhas Daftuar
  • Tawanda Kembo
  • Teran McKinney
  • tm314159
  • Tom Harding
  • Trevin Hofmann
  • Whit J
  • Wladimir J. van der Laan
  • Yoichi Hirai
  • Zak Wilcox
As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
Also lots of thanks to the bitcoin.org website team David A. Harding and Saivann Carignan.
Wladimir
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007480.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Escribi dos posts de Facebook (largos) explicando tanto el concepto de "Moneda" como las BitCoins. Si gente ducha en el alguno de los temas me dice si le pifio feo en algo, agradezco. [X-Post de /r/argentina]

Buscaria apoyo en los subreddits relevantes pero la verdad es que es un trabajo de traduccion largo y bastante molesto, asi que decidi probar suerte aca. Desde ya gracias por el feedback, sorry por el TL;DR, y espero lo disfruten.
MONEDA:
Una "Moneda" tiene dos fuentes de valor bien diferenciadas:
Veamos dos casos EXTREMOS de lo que constituye el respaldo para diferentes monedas: El Dolar y el Peso.
El DOLAR cuenta con un respaldo "abstracto" o "infraestructural", o sea, el dolar no esta respaldado por una cantidad de divisa que constituye su valor. Al contrario, el valor del dolar esta constituido por una compleja serie de deudas entre diferentes acreedores, entre los cuales estan la FED, el Gobierno de Estados Unidos, sus ciudadanos, y otros gobiernos internacionales. El dolar vale porque un monton de gente es acreedora o deudora de dolares y esta compleja red, en conjuncion con la "fuerza institucional" de la FED y del Gobierno Estadounidense constituyen un sistema de "confianza mutua" en la cual todos los interesados estan "comprometidos" con la manutencion convencional de un valor estable del Dolar. El dolar, en definitiva, esta respaldado por la confianza de que las deudas de la FED y del Gobierno Estadounidense seran pagadas.
EL PESO, en total oposicion, cuenta con un respaldo casi totalmente concreto en divisas. O sea, el valor del peso es una funcion de la cantidad de divisas que tiene el banco central dividido por la cantidad de pesos en circulacion, con una influencia casi nula del factor "CONFIANZA" Por que? Porque no se dan las condiciones institucionales para poder respaldar con CONFIANZA el valor del Peso, por lo tanto hay que recurrir al respaldo de divisas puro y duro.
Entre estos dos casos se encuentran casi todas las monedas del mundo: la mayoria de las monedas no tienen un "valor flotante" dependiendo de la cantidad de divisas que tiene un gobierno, porque muchos gobiernos cuentan con la confianza de que pueden mantener el valor de su moneda a futuro mas alla de sus divisas en existencias. O sea, el mundo confia en su capacidad de generar divisas a futuro.
EN RESUMEN:
BITCOIN:
En el caso de BitCoin estamos ante una situacion identica. BitCoin tiene un valor flotante de mercado equivalente en dolares. Pero ese valor de mercado flotante descansa sobre la CONFIANZA en la "BitCoin Network", que es la "institucion" o "entidad" que respalda la moneda.
Que es esa "institucion"? Como funciona? Por que genera confianza?
BitCoin esta respaldada por una red mundial de procesadores criptograficos o "Farms". Esto son computadoras que tienen poder de procesamiento dedicado a resolver ecuaciones matematicas criptograficas enormemente complejas. Sobre este poder de procesamiento descansan los principales factores de confianza del BitCoin: que es matematicamente imposible falsificarla, y que es matematicamente imposible falsificar una transaccion. O sea, si usuario A le hace una transmision de BitCoin a B, tanto A como B estan 100% seguros sin ningun lugar a dudas, es certeza matematica, que B esta recibiendo exactamente lo que A le dice que le dio.
Esta infraestructura informatica realizando operaciones matematicas de altisimo nivel, para asegurar la infalsibilidad de la moneda, es lo que le brinda a BitCoin el factor "CONFIANZA". Pero para hacer eso se necesita una cantidad ENORME de capacidad de procesamiento.
Que recompensa se le brinda a la gente que contribuye este poder de procesamiento? Son dos:
  1. Las transacciones en BitCoin son GRATUITAS, nadie cobra comision, A MENOS QUE vos quieras que tu transaccion tenga efecto inmediato. O sea, imaginemos una cola de transacciones: yo le quiero dar 2 BitCoins a Lucas. Ok, hacemos esa transaccion, y va a una cola de transacciones a resolver. Si la queremos hacer gratis, esa transaccion puede tomar un tiempo, generalmente entre horas y unos dias. Ahora, si quisieramos que esa transaccion tome prioridad, o sea, que se adelante en la cola, podemos ELEGIR pagar una pequena comision para que sea inmediata. Esa pequena comision es destinada a la "Farm" que sale primero al cruce de realizar esa transaccion, asi recompensandola.
  2. El "Farm" tambien realiza, con creciente dificultad, un proceso que genera nuevas BitCoins muy lentamente. Esto se llama "Minar" en la jerga. Una granja de BitCoins produce, solo por contribuir poder de procesamiento a la red, una cantidad de BitCoins cada tanto tiempo.
Mientras mas va avanzando el tiempo, y mas aceptada se vuelve BitCoin, mas importante se vuelve el metodo de recompensa 1, ya que la demanda de transacciones inmediatas aumenta. En oposicion, como BitCoin escala negativamente, y cada vez cuesta mas producir una BitCoin, el metodo de recompensa 2 va perdiendo importancia.
En resumen, donde una moneda nacional esta respaldada por una estructura de produccion de confianza y con bienes que son divisas, BitCoin esta respaldada por un nucleo "Matematico" o de "Software" que determina su "Infalsificabilidad Algoritimica" y muchisimo Hardware, millones y millones de dolares en Hardware que contribuyen a llevar adelante esos algoritmos.
Link al original
Posts a otros subreddits no se enlazan directamente. Explicado en el wiki.
submitted by elMatadero_bot to elMatadero [link] [comments]

LE BITCOIN EST MORT - VIVE LE BITCOIN (CRYPTO HEBDO n°19) Bitcoin, c'est quoi exactement ? MINARE BITCOIN  Vale la pena farlo? - YouTube J'AI REÇU MA MACHINE DE BITCOIN ! feat. Hasheur - YouTube Bitcoins Erklärung: In nur 12 Min. Bitcoin verstehen ...

Satoshi è una parte strutturale della criptovaluta Bitcoin, che è cento milionesimo di bitcoin. Tali piccole unità facilitano le transazioni con BTC. Il componente strutturale totale di 1 bitcoin (BTC) equivale a 1000 millibit (mBTC), 1.000.000 microbo (mkBTC) o 100.000.000 Satoshi. Data esatta è sc... From Bitcoin Wiki. Jump to: navigation, search. A home-made "mining rig" Contents. 1 Introduction; 2 Difficulty. 2.1 The Computationally-Difficult Problem; 2.2 The Difficulty Metric; 2.3 Reward; 3 The mining ecosystem. 3.1 Hardware. 3.1.1 CPU Mining; 3.1.2 GPU Mining; 3.1.3 FPGA Mining; 3.1.4 ASIC Mining; 3.1.5 Mining services (Cloud mining) 3.2 Pools; 3.3 History; 4 Staking; 5 See Also ... Pour une liste plus complète des cartes graphiques et de leurs performances, consultez le Wiki Bitcoin: Comparaison du matériel de minage. De la même manière que la transition CPU vers GPU, le monde du minage a évolué vers l'usage des Field Programmable Gate Arrays (FPGA) comme plateforme de minage. Bien que les FPGAs n'offraient pas une ... Bitcoin is a decentralized digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: transaction management and money issuance are carried out collectively by the network. The original Bitcoin software by Satoshi Nakamoto was released under the MIT license. . Most client software, derived or "from ... BitLox Bitcoin Hardware wallet is the Rolls Royce of Bitcoin wallets with its wealth of features and high levels of bespoke security coming encased in titanium if you so wish. Although difficult to use in terms of getting to grips with all its features - the Bitlox wallet is treasure trove for those keen on privacy and security.

[index] [12102] [22501] [51405] [20993] [49053] [2128] [38492] [28777] [24980] [6535]

LE BITCOIN EST MORT - VIVE LE BITCOIN (CRYPTO HEBDO n°19)

Thanks to Away for sponsoring this video! Go to https://www.awaytravel.com/techquickie and use promo code techquickie to get $20 off your next order! Bitcoin... ( Le 29 novembre 2013, la valeur d'un bitcoin dépasse celle de l'once d'or ) je peut vous vendre une petite quantité de Bitcoin (0,01) via un paiement paypal de $ 9,99 ca a : bitcoinsatochi ... Secure your crypto with a Ledger hardware wallet: ... Pourquoi INVESTIR dans le BITCOIN et dans les CRYPTOMONNAIES ! (Litecoin, Ripple, Dash, Ethereum) - Duration: 13:19. ALTI TRADING - Alexandre ... Le bitcoin et crypto sont-ils morts. Calme plat avant potentiel signal et explosion ? On revoit ça ensemble. Qu'en pensez-vous ? Posez-moi vos questions en commentaire et ABONNEZ-VOUS. Onecoin promised the world, but only proved to be a trail of destruction. --- About ColdFusion --- ColdFusion is an Australian based online media company ind...

#