MtGox/IRC mtgox - Bitcoin Wiki

Cryptography news and discussions

Cryptography is the art of creating mathematical assurances for who can do what with data, including but not limited to encryption of messages such that only the key-holder can read it. Cryptography lives at an intersection of math and computer science. This subreddit covers the theory and practice of modern and *strong* cryptography, and it is a technical subreddit focused on the algorithms and implementations of cryptography.
[link]

rEvolution Reddit

We are an activist hivemind based on the principles of **equality, freedom and democracy**. Fighting for the [free flow of information](https://youtu.be/iY57ErBkFFE), we will operate as a free and open subreddit.
[link]

StableCoin

This subreddit is dedicated to inform and discuss the revolutionary cryptocurrency Stablecoin.
[link]

AgainstHateSubreddits FAQ - Answers to Frequently Asked Questions, both sincere and disingenuous.

What is /AgainstHateSubreddits?

The purpose of this community is to draw attention to - and elicit meaningful action upon - instances of the growing problem of radicalization on Reddit.

We call for moderators and admins to take responsibility for their roles in the meme-ification & normalization of:

• bigotry

• hate

• harassment

&

• violence

"Hate Subreddit" is defined here in AHS as:
Reddit communities that exist primarily and materially for the purpose of incitement to hatred --
hatred against a group of persons, or a specific person, on the basis of:
• race • ethnicity • national origin • gender • religion • sexual orientation • other inherent characteristics.
Hate subreddits regularly show disdain for human rights and emotions, the results of academic research, and, of course, basic human decency.

What does /AgainstHateSubreddits DO?

"In a racist society, it is not enough to be non-racist, we must be antiracist.” — Angela Davis

• We organise resources for moderators to help them be educated about hatred and harassment - how to identify and combat it.

• We organise a community to :

• Identify subreddits which host or promote cultures of hatred

&

• Report items (posts / comments) in those subreddits which violate the Reddit Content Policies. Hate speech is a violation of the Reddit Content Policy against Harassment.

• Act in Good Faith - We take /AgainstHateSubreddits' mission seriously, and you should, too.

Irony poisons sincerity, and bigots rely on tiring people out by making them wonder "is this person just joking or are they sincere?". Irony provides a shield for bigots.

• Follow ALL the sitewide Content Policies.

Don't ask people to vote on items. Don't ask people to go to hate subreddits and dogpile comments on them.
We don't do those things - because they are violations of the content policies, and because they serve the goals of bigots.
We will ban accounts that do these things.

What does /AgainstHateSubreddits NOT do?

"When these people come for you, they cannot be reasoned with. When well-intentioned people fall for bad-faith tactics, bad-faith people continue to employ them."** -- Lindsay Ellis

• We DO NOT organise offsite. We do not, and never have had, a Discord for AHS.

We have a Slack channel, where we organise our moderation team and only our moderation team.
If someone tells you that they've seen an AHS Discord / IRC Channel / Pinterest / Tumblr / whatever - that person is lying to you to smear our moderators and users, and is probably a neoNazi. Those are not the first time they've tried to fake evidence of moderators being paedophiles, and it will not be the last time either.

• We DO NOT participate in posts / threads / comments in hate subreddits. We don't vote; We don't comment; We don't feed the trolls.

Engagement and recruitment is Priority #1 of bigots - they don't want to debate you sincerely -- they want you to get angry, and bring your friends, and have those friends bring their friends - so they get lots and lots of attention and an audience and a list of potential recruits. They want to steal time and peace of mind from us, divide us and fracture our united front. Don't fall for it.

• We DO NOT amplify the hate messages of the bigots.

Censor slurs in your posts and comments wherever possible. Use the NSFW tag on your posts if submitting material that is patently offensive, hateful, pornographic, unsuitable for a work environment, etc. Use an archive service to submit posts wherever possible to make it inconvenient to join the bigot's efforts.
If you are a bigot, and you want to participate here, you must do so in Good Faith -- if you come here to platform your bigotry, recruit, proselytise, or abuse people: you will be promptly banned. Your only reason to participate here is to help you find a way to get away from the people reinforcing your bigotry.

• We DO NOT Debate Economic Theory

There are other venues, of varying quality, and varying effectiveness, to recruit people to defend or critique capitalism / communism / barter / mutualism / welfare / Bitcoin / the Dahrendorf hypothesis / Bayesian regret. THIS IS NOT THE PLACE FOR THOSE.

• We DO NOT delete or retroactively radically edit comments.

That's Bad Faith.

• We are NOT your Personal Army.

If the members of one demographic are traditionally vilifying / vilified by another demographic, we will not "take sides" "for" the representatives of either demographic using their respective subreddits as proxies - No International Political Slapfighting.
We do make exceptions for subreddits, named for a demographic or international geographic compartment (i.e. country), that are clearly being operated to platform hatred. Those require substantial, objectively evaluatable evidence of a pattern of hatred, bigotry, harassment, or violence, and the misfeasance of the moderators of the subreddit. We do not want submissions of 4-month old comments by suspended users that never went live or which received no upvotes, in innocent / well-moderated subreddits.

• We DO NOT focus on "joke" or "troll" or "meme" subreddits -- unless they are effectively unmoderated and therefore serve as platforms and recruitment for hate movements. Hatred is independent of medium.

• We DO NOT accept posts about Child Sexual Exploitation material on Reddit.

Because of legal and ethical considerations, we do not allow the use of /AgainstHateSubreddits to direct attention to sexual or suggestive content involving minors on Reddit -- nor for making allegations that any content on Reddit is sexual or suggestive content involving minors.
Please report any content which you reasonably believe to be sexual or suggestive content involving minors using this link:
https://www.reddit.com/report?reason=its-sexual-or-suggestive-content-involving-minors
Please do not solicit other people to view such material, nor direct others as to where to locate it. That can be distribution of obscene material. It's also traumatic for people exposed to it. Don't share links to it with anyone but the Reddit admins, your attorney where applicable, and law enforcement!
You can also use the resources of the FBI via this webpage: https://www.fbi.gov/investigate/violent-crime/cac
and the US Department of Justice via this webpage: https://www.justice.gov/actioncentereport-crime#child
This has been our long-standing policy - we refuse to amplify child sexual exploitation.

• We DO NOT back down and we DO NOT compromise.

Bigots want to run Reddit "from the bottom", Mafia-style -- by spreading Fear, Uncertainty, and Doubt.
They have a track record of smearing people, harassing people, trying to ruin people's lives, trying to run them off Reddit, mocking and ridiculing them, wasting people's time and resources, extorting them into compromising their community's identity and boundaries, falsely threatening vexatious legal action or account suspension / moderator privilege revocation as retaliation for banning bigots or removing posts and comments which compromise the integrity of a community or which violate a Content Policy. They maliciously spread misinformation, rumour, innuendo, propaganda, lies, and scams.

We give bigots NOTHING.

NOT. ONE. INCH.

And if you don't think you're a bigot -- but you feel that you can "peacefully coexist" with violent white supremacists, neo-Nazis, the Khmer Rouge, the KKK, the "alt-Right"?
... Historians have a word for the people who went along with the Nazis. That's "Nazi". Or, sadly, "Victim of the Nazis". Als sie die Juden holten, habe ich geschwiegen; ich war ja kein Jude
Ask good faith questions not addressed here in the comments below.
submitted by Bardfinn to AgainstHateSubreddits [link] [comments]

"but if I got it right, he has mass enslavement-genocidal plans, and setting up a feudal system"

https://www.reddit.com/Bitcoin/comments/eiskr6/i_was_reading_saifedeans_book_and_saw_mircea/?utm_source=amp&utm_medium=&utm_content=post_body
Some fun quotes
Looks like he has a blog and I've been reading. It's a bit of a word salad headache, but if I got it right, he has mass enslavement-genocidal plans, and setting up a feudal system on BTC in which people that don't meet a certain level of IQ are sold, raped, killed....
...
Unless he's a troll and likes to play this villain persona, from what I've read he's defending rape, sending death treats over not agreeing with something, mass genocidal plans unless you can pass a fucking test...
...
If you weren't around to see people trying to buy/sell slaves online or whatever (when they weren't busy ripping people off) then it can be really hard to imagine how shitty people could actually be in public.
It looks like this is talking about Mircea Popescu who I've run across before. Supposedly he was rich before Bitcoin & claimed to own 1mil of them at different points.
submitted by Johnroberts95000 to Buttcoin [link] [comments]

Beginner's Guide: Where to start & FAQ!

New Flair Rule

We've been overwhelmed with newcomer posts. In light of this, we created a bot that will PM people without flairs various pertinent information to read through when they post. In order to stop receiving these, simply add a flair to your name. Thanks!

Scam Warning

Hey guys. There have been numerous scammers lately who have been private messaging redditors. Their goal is for you to send Litecoins to their address. So far, they've followed the same writing template. It looks something like this: https://imgur.com/0UZczuz
If someone is telling you to send to a Litecoin address they are providing, DON'T. They're trying to steal your Litecoins. If you're not sure, read the wealth of knowledge below or comment below and I will eventually get to you.

Welcome to /Litecoin!

(Re-post of u/Sparkswont cuz it was archived)
Whether you're new to cryptocurrency and have no clue what a 'litecoin' is, or a seasoned investor in cryptocurrencies, the resources below will answer all your questions. If you still have questions, feel free to ask below in the comments!
 

What is Litecoin?

Litecoin (LTC or Ł) is a peer-to-peer cryptocurrency and open source software project released under the MIT/X11 license. Litecoin is one of the largest, oldest, and most used cryptocurrencies in the world. Similar to Bitcoin, Litecoin uses blockchain technology to process transactions.
So what's the difference? To process a block, Litecoin takes 2.5 minutes rather than Bitcoins 10 minutes. This allows for faster processing times. Litecoin also has the capability to produce a total of 84 million units, compared to Bitcoins 21 million. In addition, Litecoin uses scrypt in its proof-of-work algorithm, a sequential memory-hard function requiring asymptotically more memory than an algorithm which is not memory-hard.
Still confused? Take a look at this video!
 

Where can I buy Litecoin?

There are many websites and applications where you can buy and sell Litecoin, but make sure the exchange you are using is trusted and secure. Here are some exchanges that are trusted in the cryptocurrency community:
Exchange
Coinbase USD/Euro/GBP
Quadrigacx CAD
Coinsquare CAD
Bithump KRW
OKCoin Euro/Yen/USD
OKex CNY
Btcmarkets.net AUD
Bitso MXN
Zebpay INR
 

Where can I securely store Litecoin?

Litecoin (and other cryptocurrencies) is stored in a digital wallet. When storing Litecoin, you want to make sure you trust the place you store them. This is why it is best to store them yourself through the electrum wallet. It is highly suggested to not store your Litecoin in an exchange (such as Coinbase, Poloniex, Bittrex, etc.) because you don't control the private keys. If the exchange ever goes offline, or becomes insolvent, your Litecoin essentially disappear.
Some other options are:
Wallet
Electrum Lightweight Wallet
Official Core Wallet
LiteVault Secure Web Wallet
Paper Wallet Instructions
 
If you're a fan of mobile devices, then Loafwallet is the wallet for you. Developed by a Litecoin Foundation Dev, losh11, this mobile wallet works great! And remember to always make sure to write down your seedkeys.
 
Hardware wallets are another great option, in fact, they are said to be the most secure way to store cryptocurrencies. Below is a list of the litecoin flexible hardware wallets.
Wallet
Ledger
Trezor
Keepkey
 

Where can I spend Litecoin?

Litecoin is in the top ten of all cryptocurrencies by market capitalization. Websites are rapidly adopting Litecoin as a method of payment as well. If you yourself want to accept LTC as a business, you can refer to these merchant manuals. Alternatively, if you would like to explore websites that accept Litecoin, head over to /AcceptingLTC.
Here are also several of our favorite merchants accepting Litecoin.
 

Where can I discuss Litecoin?

The Litecoin community is extremely kind and robust. There are many forums and places where you can discuss Litecoin with others who are interested in the currency. Here are the main ones:
Platform
Reddit
Litecoin Markets Subreddit
Discord
Official Forum
IRC
 

Additional Resources and Help

If you have more questions, or are genuinely interested in learning more about Litecoin then be sure to read this series. If you have a specific question that you can't seem to find the answer too, ask below and someone will help you out!
submitted by ecurrencyhodler to litecoin [link] [comments]

⚡ Lightning Network Megathread ⚡

Last updated 2018-01-29
This post is a collaboration with the Bitcoin community to create a one-stop source for Lightning Network information.
There are still questions in the FAQ that are unanswered, if you know the answer and can provide a source please do so!

⚡What is the Lightning Network? ⚡

Explanations:

Image Explanations:

Specifications / White Papers

Videos

Lightning Network Experts on Reddit

  • starkbot - (Elizabeth Stark - Lightning Labs)
  • roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
  • stile65 - (Alex Akselrod - Lightning Labs)
  • cfromknecht - (Conner Fromknecht - Lightning Labs)
  • RustyReddit - (Rusty Russell - Blockstream)
  • cdecker - (Christian Decker - Blockstream)
  • Dryja - (Tadge Dryja - Digital Currency Initiative)
  • josephpoon - (Joseph Poon)
  • fdrn - (Fabrice Drouin - ACINQ )
  • pmpadiou - (Pierre-Marie Padiou - ACINQ)

Lightning Network Experts on Twitter

  • @starkness - (Elizabeth Stark - Lightning Labs)
  • @roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
  • @stile65 - (Alex Akselrod - Lightning Labs)
  • @bitconner - (Conner Fromknecht - Lightning Labs)
  • @johanth - (Johan Halseth - Lightning Labs)
  • @bvu - (Bryan Vu - Lightning Labs)
  • @rusty_twit - (Rusty Russell - Blockstream)
  • @snyke - (Christian Decker - Blockstream)
  • @JackMallers - (Jack Mallers - Zap)
  • @tdryja - (Tadge Dryja - Digital Currency Initiative)
  • @jcp - (Joseph Poon)
  • @alexbosworth - (Alex Bosworth - yalls.org)

Medium Posts

Learning Resources

Books

Desktop Interfaces

Web Interfaces

Tutorials and resources

Lightning on Testnet

Lightning Wallets

Place a testnet transaction

Altcoin Trading using Lightning

  • ZigZag - Disclaimer You must trust ZigZag to send to Target Address

Lightning on Mainnet

Warning - Testing should be done on Testnet

Atomic Swaps

Developer Documentation and Resources

Lightning implementations

  • LND - Lightning Network Daemon (Golang)
  • eclair - A Scala implementation of the Lightning Network (Scala)
  • c-lightning - A Lightning Network implementation in C
  • lit - Lightning Network node software (Golang)
  • lightning-onion - Onion Routed Micropayments for the Lightning Network (Golang)
  • lightning-integration - Lightning Integration Testing Framework
  • ptarmigan - C++ BOLT-Compliant Lightning Network Implementation [Incomplete]

Libraries

Lightning Network Visualizers/Explorers

Testnet

Mainnet

Payment Processors

  • BTCPay - Next stable version will include Lightning Network

Community

Slack

IRC

Slack Channel

Discord Channel

Miscellaneous

⚡ Lightning FAQs ⚡

If you can answer please PM me and include source if possible. Feel free to help keep these answers up to date and as brief but correct as possible
Is Lightning Bitcoin?
Yes. You pick a peer and after some setup, create a bitcoin transaction to fund the lightning channel; it’ll then take another transaction to close it and release your funds. You and your peer always hold a bitcoin transaction to get your funds whenever you want: just broadcast to the blockchain like normal. In other words, you and your peer create a shared account, and then use Lightning to securely negotiate who gets how much from that shared account, without waiting for the bitcoin blockchain.
Is the Lightning Network open source?
Yes, Lightning is open source. Anyone can review the code (in the same way as the bitcoin code)
Who owns and controls the Lightning Network?
Similar to the bitcoin network, no one will ever own or control the Lightning Network. The code is open source and free for anyone to download and review. Anyone can run a node and be part of the network.
I’ve heard that Lightning transactions are happening “off-chain”…Does that mean that my bitcoin will be removed from the blockchain?
No, your bitcoin will never leave the blockchain. Instead your bitcoin will be held in a multi-signature address as long as your channel stays open. When the channel is closed; the final transaction will be added to the blockchain. “Off-chain” is not a perfect term, but it is used due to the fact that the transfer of ownership is no longer reflected on the blockchain until the channel is closed.
Do I need a constant connection to run a lightning node?
Not necessarily,
Example: A and B have a channel. 1 BTC each. A sends B 0.5 BTC. B sends back 0.25 BTC. Balance should be A = 0.75, B = 1.25. If A gets disconnected, B can publish the first Tx where the balance was A = 0.5 and B = 1.5. If the node B does in fact attempt to cheat by publishing an old state (such as the A=0.5 and B=1.5 state), this cheat can then be detected on-chain and used to steal the cheaters funds, i.e., A can see the closing transaction, notice it's an old one and grab all funds in the channel (A=2, B=0). The time that A has in order to react to the cheating counterparty is given by the CheckLockTimeVerify (CLTV) in the cheating transaction, which is adjustable. So if A foresees that it'll be able to check in about once every 24 hours it'll require that the CLTV is at least that large, if it's once a week then that's fine too. You definitely do not need to be online and watching the chain 24/7, just make sure to check in once in a while before the CLTV expires. Alternatively you can outsource the watch duties, in order to keep the CLTV timeouts low. This can be achieved both with trusted third parties or untrusted ones (watchtowers). In the case of a unilateral close, e.g., you just go offline and never come back, the other endpoint will have to wait for that timeout to expire to get its funds back. So peers might not accept channels with extremely high CLTV timeouts. -- Source
What Are Lightning’s Advantages?
Tiny payments are possible: since fees are proportional to the payment amount, you can pay a fraction of a cent; accounting is even done in thousandths of a satoshi. Payments are settled instantly: the money is sent in the time it takes to cross the network to your destination and back, typically a fraction of a second.
Does Lightning require Segregated Witness?
Yes, but not in theory. You could make a poorer lightning network without it, which has higher risks when establishing channels (you might have to wait a month if things go wrong!), has limited channel lifetime, longer minimum payment expiry times on each hop, is less efficient and has less robust outsourcing. The entire spec as written today assumes segregated witness, as it solves all these problems.
Can I Send Funds From Lightning to a Normal Bitcoin Address?
No, for now. For the first version of the protocol, if you wanted to send a normal bitcoin transaction using your channel, you have to close it, send the funds, then reopen the channel (3 transactions). In future versions, you and your peer would agree to spend out of your lightning channel funds just like a normal bitcoin payment, allowing you to use your lightning wallet like a normal bitcoin wallet.
Can I Make Money Running a Lightning Node?
Not really. Anyone can set up a node, and so it’s a race to the bottom on fees. In practice, we may see the network use a nominal fee and not change very much, which only provides an incremental incentive to route on a node you’re going to use yourself, and not enough to run one merely for fees. Having clients use criteria other than fees (e.g. randomness, diversity) in route selection will also help this.
What is the release date for Lightning on Mainnet?
Lightning is already being tested on the Mainnet Twitter Link but as for a specific date, Jameson Lopp says it best
Would there be any KYC/AML issues with certain nodes?
Nope, because there is no custody ever involved. It's just like forwarding packets. -- Source
What is the delay time for the recipient of a transaction receiving confirmation?
Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. -- Source
How does the lightning network prevent centralization?
Bitcoin Stack Exchange Answer
What are Channel Factories and how do they work?
Bitcoin Stack Exchange Answer
How does the Lightning network work in simple terms?
Bitcoin Stack Exchange Answer
How are paths found in Lightning Network?
Bitcoin Stack Exchange Answer
How would the lightning network work between exchanges?
Each exchange will get to decide and need to implement the software into their system, but some ideas have been outlined here: Google Doc - Lightning Exchanges
Note that by virtue of the usual benefits of cost-less, instantaneous transactions, lightning will make arbitrage between exchanges much more efficient and thus lead to consistent pricing across exchange that adopt it. -- Source
How do lightning nodes find other lightning nodes?
Stack Exchange Answer
Does every user need to store the state of the complete Lightning Network?
According to Rusty's calculations we should be able to store 1 million nodes in about 100 MB, so that should work even for mobile phones. Beyond that we have some proposals ready to lighten the load on endpoints, but we'll cross that bridge when we get there. -- Source
Would I need to download the complete state every time I open the App and make a payment?
No you'd remember the information from the last time you started the app and only sync the differences. This is not yet implemented, but it shouldn't be too hard to get a preliminary protocol working if that turns out to be a problem. -- Source
What needs to happen for the Lightning Network to be deployed and what can I do as a user to help?
Lightning is based on participants in the network running lightning node software that enables them to interact with other nodes. This does not require being a full bitcoin node, but you will have to run "lnd", "eclair", or one of the other node softwares listed above.
All lightning wallets have node software integrated into them, because that is necessary to create payment channels and conduct payments on the network, but you can also intentionally run lnd or similar for public benefit - e.g. you can hold open payment channels or channels with higher volume, than you need for your own transactions. You would be compensated in modest fees by those who transact across your node with multi-hop payments. -- Source
Is there anyway for someone who isn't a developer to meaningfully contribute?
Sure, you can help write up educational material. You can learn and read more about the tech at http://dev.lightning.community/resources. You can test the various desktop and mobile apps out there (Lightning Desktop, Zap, Eclair apps). -- Source
Do I need to be a miner to be a Lightning Network node?
No -- Source
Do I need to run a full Bitcoin node to run a lightning node?
lit doesn't depend on having your own full node -- it automatically connects to full nodes on the network. -- Source
LND uses a light client mode, so it doesn't require a full node. The name of the light client it uses is called neutrino
How does the lightning network stop "Cheating" (Someone broadcasting an old transaction)?
Upon opening a channel, the two endpoints first agree on a reserve value, below which the channel balance may not drop. This is to make sure that both endpoints always have some skin in the game as rustyreddit puts it :-)
For a cheat to become worth it, the opponent has to be absolutely sure that you cannot retaliate against him during the timeout. So he has to make sure you never ever get network connectivity during that time. Having someone else also watching for channel closures and notifying you, or releasing a canned retaliation, makes this even harder for the attacker. This is because if he misjudged you being truly offline you can retaliate by grabbing all of its funds. Spotty connections, DDoS, and similar will not provide the attacker the necessary guarantees to make cheating worthwhile. Any form of uncertainty about your online status acts as a deterrent to the other endpoint. -- Source
How many times would someone need to open and close their lightning channels?
You typically want to have more than one channel open at any given time for redundancy's sake. And we imagine open and close will probably be automated for the most part. In fact we already have a feature in LND called autopilot that can automatically open channels for a user.
Frequency will depend whether the funds are needed on-chain or more useful on LN. -- Source
Will the lightning network reduce BTC Liquidity due to "locking-up" funds in channels?
Stack Exchange Answer
Can the Lightning Network work on any other cryptocurrency? How?
Stack Exchange Answer
When setting up a Lightning Network Node are fees set for the entire node, or each channel when opened?
You don't really set up a "node" in the sense that anyone with more than one channel can automatically be a node and route payments. Fees on LN can be set by the node, and can change dynamically on the network. -- Source
Can Lightning routing fees be changed dynamically, without closing channels?
Yes but it has to be implemented in the Lightning software being used. -- Source
How can you make sure that there will be routes with large enough balances to handle transactions?
You won't have to do anything. With autopilot enabled, it'll automatically open and close channels based on the availability of the network. -- Source
How does the Lightning Network stop flooding nodes (DDoS) with micro transactions? Is this even an issue?
Stack Exchange Answer

Unanswered Questions

How do on-chain fees work when opening and closing channels? Who pays the fee?
How does the Lightning Network work for mobile users?
What are the best practices for securing a lightning node?
What is a lightning "hub"?
How does lightning handle cross chain (Atomic) swaps?

Special Thanks and Notes

  • Many links found from awesome-lightning-network github
  • Everyone who submitted a question or concern!
  • I'm continuing to format for an easier Mobile experience!
submitted by codedaway to Bitcoin [link] [comments]

Day 3: I will repost this guide daily until available solutions like SegWit & order batching are mass adopted, the mempool is empty once again, and transaction fees are low. ARE YOU PART OF THE SOLUTION? News: Unconfirmed TX's @ 274K, more exchanges adding SegWit, Core prioritizes SegWit GUI

BACKGROUND
Subhan Nadeem has pointed out that:
If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
A few thousand bitcoin users from /Bitcoin switching to making their next transactions SegWit transactions will help take pressure off the network now, and together we can encourage exchanges/wallets to rapidly deploy SegWit for everyone ASAP. Let's make it happen. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin
IMPORTANT NOTE: The mempool is currently overflowing. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange
SELECTED TOP EXCHANGES BY SEGWIT & BATCHING STATUS
Exchange Segwit Status Batching Status
Binance ? NOT READY Yes
Bitfinex Ready ?
Bitonic Ready ?
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Ready Deployed Yes
Huboi ? ?
Kraken Ready Yes
LocalBitcoins Ready ?
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
Source 1(https://web.archive.org/web/20171212214514/https://bitcoincore.org/en/SegWit_adoption/)
Source 2
WALLETS
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
TODAY's NEWS/DEVELOPMENTS/VICTORIES
MEMPOOL/SEGWIT STATISTICS
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
  • No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unneccessary transactions for now.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
  • The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download Electrum v3.0.3 to generate a SegWit address.
    A transaction between two SegWit addresses is a SegWit transaction.
    A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
    A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
    Source
What wallet are you using to "batch your sends"? And how can I do that?
  • Using Electrum, the "Tools" menu option: "Pay to many".
    Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
  • The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
Edit: Updated Segwit Exchange Status for Binance and HitBTC
submitted by Bastiat to Bitcoin [link] [comments]

Has billionaire Mircea Popescu lost his sauce?

Some time ago priapic psychopath polymath Mircea Popescu claimed he had one million butts. Then he was all like 'I divested some'. Months back he said 'I r a billionaire', meaning in terms of God's own money, the US dollar. Now, while the Magic the Gathering cards have gone up 4x or so since then, he still claims he's only got a billion. http://log.mkj.lt/trilema/20170819/#154 . So what, he's only got a quarter million butts to dump on all these gavincoins, let alone rule the world? Pfft
submitted by 21mil to Buttcoin [link] [comments]

Beginner's Guide: Where to start & FAQ!

New Flair Rule

We've been overwhelmed with newcomer posts. In light of this, we created a bot that will PM people without flairs various pertinent information to read through when they post. In order to stop receiving these, simply add a flair to your name. Thanks!

Welcome to /Litecoin!

(Re-post of u/Sparkswont cuz it was archived)
Whether you're new to cryptocurrency and have no clue what a 'litecoin' is, or a seasoned investor in cryptocurrencies, the resources below will answer all your questions. If you still have questions, feel free to ask below in the comments!
 

What is Litecoin?

Litecoin (LTC or Ł) is a peer-to-peer cryptocurrency and open source software project released under the MIT/X11 license. Litecoin is one of the largest, oldest, and most used cryptocurrencies in the world. Similar to Bitcoin, Litecoin uses blockchain technology to process transactions.
So what's the difference? To process a block, Litecoin takes 2.5 minutes rather than Bitcoins 10 minutes. This allows for faster processing times. Litecoin also has the capability to produce a total of 84 million units, compared to Bitcoins 21 million. In addition, Litecoin uses scrypt in its proof-of-work algorithm, a sequential memory-hard function requiring asymptotically more memory than an algorithm which is not memory-hard.
Still confused? Take a look at this video!
 

Where can I buy Litecoin?

There are many websites and applications where you can buy and sell Litecoin, but make sure the exchange you are using is trusted and secure. Here are some exchanges that are trusted in the cryptocurrency community:
Exchange
Coinbase USD/Euro/GBP
Bithump KRW
OKCoin Euro/Yen/USD
OKex CNY
Btcmarkets.net AUD
Bitso MXN
Zebpay INR
 

Where can I securely store Litecoin?

Litecoin (and other cryptocurrencies) is stored in a digital wallet. When storing Litecoin, you want to make sure you trust the place you store them. This is why it is best to store them yourself through the electrum wallet. It is highly suggested to not store your Litecoin in an exchange (such as Coinbase, Poloniex, Bittrex, etc.) because you don't control the private keys. If the exchange ever goes offline, or becomes insolvent, your Litecoin essentially disappear.
Some other options are:
Wallet
Electrum Lightweight Wallet
Official Core Wallet
LiteVault Secure Web Wallet
Paper Wallet Instructions
 
If you're a fan of mobile devices, then Loafwallet is the wallet for you. Developed by a Litecoin Foundation Dev, losh11, this mobile wallet works great! And remember to always make sure to write down your seedkeys.
 
Hardware wallets are another great option, in fact, they are said to be the most secure way to store cryptocurrencies. Below is a list of the litecoin flexible hardware wallets.
Wallet
Ledger
Trezor
Keepkey
 

Where can I spend Litecoin?

Litecoin is in the top ten of all cryptocurrencies by market capitalization. Websites are rapidly adopting Litecoin as a method of payment as well. If you yourself want to accept LTC as a business, you can refer to these merchant manuals. Alternatively, if you would like to explore websites that accept Litecoin, head over to /AcceptingLTC.
Here are also several of our favorite merchants accepting Litecoin.
 

Where can I discuss Litecoin?

The Litecoin community is extremely kind and robust. There are many forums and places where you can discuss Litecoin with others who are interested in the currency. Here are the main ones:
Platform
Reddit
Litecoin Markets Subreddit
Discord
Official Forum
IRC
 

Additional Resources and Help

If you have more questions, or are genuinely interested in learning more about Litecoin then be sure to read this series. If you have a specific question that you can't seem to find the answer too, ask below and someone will help you out!
submitted by ecurrencyhodler to litecoin [link] [comments]

Help preserve Dota 2 history: your assistance is requested in downloading (and hosting) Twitch broadcasts

As you may or may not have known already, in addition to Twitch implementing a content ID system of their own, videos are now going to be deleted after 2 months for partners, whereas it was previously unlimited storage.
Valuable content is at risk of deletion, including Dota 2 matches and events (such as all Internationals, many LANs, etc) within 3 weeks.

Meet the Archive Team

The wiki states this:
Archive Team is a loose collective of rogue archivists, programmers, writers and loudmouths dedicated to saving our digital heritage. Since 2009 this variant force of nature has caught wind of shutdowns, shutoffs, mergers, and plain old deletions - and done our best to save the history before it's lost forever. Along the way, we've gotten attention, resistance, press and discussion, but most importantly, we've gotten the message out: IT DOESN'T HAVE TO BE THIS WAY.
The Archive Team is loosely friends with, but is not officially affiliated with the Internet Archive, which stores a whole bunch of stuff (audio, video, even vintage books!).

You can help!

Want to help? Great! Hop on #burnthetwitch on EFNet (#archiveteam too if you want to be informed of future projects) with your IRC client of choice so you can stay informed as to what's happening. Users that are op'ed (including myself) will usually be the ones knowing what's going on. If you have questions, shout them in the channel, or ask one of those ops.

If you're some average Joe:

Head for this section on the wiki. In summary:
  • Grab a Warrior VM
  • Get VirtualBox/VMWare/similar virtualization program
  • Set up the Warrior file in your virtualization program of choice
  • Run the Warrior VM
  • Set it up (use 1 concurrent item if you have a rather poor connection)
  • Select "Twitch Phase 2" in the projects list
  • You're now helping!
If you notice high pings in games while you have your Warrior running, consult this section for how to limit bandwidth use: http://archiveteam.org/index.php?title=Warrior#Help.21_The_warrior_is_eating_all_my_bandwidth.21

If you're some average Joe in Kansas City:

Great! We could use a few Google Fiber lines. It helps massively. Even better if you have multiple lines that have a Fiber installation. See the above section.

If you're data capped:

Chances are, if you're this type of person, you're stuck with an ISP with an insane data cap. You might not be able to help directly, but you can still help: share the project with your friends. If you might not be able to help, your friends might be able to. Get them to share too: the more people involved, the better.

If you feel like observing the project:

We have a real-time tracker running for the project: http://tracker.archiveteam.org/twitchtv/

The Internet Archive will need help too

The Internet Archive is where a majority of AT grabs are currently stored, including MobileMe, various Yahoo! sites, Friendster, a bunch of Google Video, and more. However, due to the sheer size of Twitch, some content will likely have to be sacrificed. We're currently prioritizing more historic events, but if you want to help store more of Twitch, send the Archive a message through donating.
There's a very good possibility you've used one of their services in the past: now is the time for you to give back. Even if it's just a one-time donation of $5, it still adds up. Not only does it cost to help store Twitch in the first place, it also costs to keep that storage up, redundant (with a EU location for redundancy), and running. The Archive is a non-profit organization. You can also even donate with Bitcoins too!
Your support will help ensure that Dota 2 history is preserved for future players many years later.
TLDR: historic Dota 2 content is at risk of deletion by Twitch. If you want to help efforts to save it, go for the "If you're some average Joe" section.
submitted by wickedplayer494 to DotA2 [link] [comments]

Beginner's Guide: Where to start & FAQ!

Subreddit Flair Rule

we created a bot that will PM people without flairs various pertinent information to read through when they post. In order to stop receiving these, simply add a flair to your name. Thanks!

Welcome to /Litecoin!

(Re-post of u/Sparkswont cuz it was archived)
Whether you're new to cryptocurrency and have no clue what a 'litecoin' is, or a seasoned investor in cryptocurrencies, the resources below will answer all your questions. If you still have questions, feel free to ask below in the comments!

What is Litecoin?

Litecoin (LTC or Ł) is a peer-to-peer cryptocurrency and open source software project released under the MIT/X11 license. Litecoin is one of the largest, oldest, and most used cryptocurrencies in the world. Similar to Bitcoin, Litecoin uses blockchain technology to process transactions.
So what's the difference? To process a block, Litecoin takes 2.5 minutes rather than Bitcoins 10 minutes. This allows for faster processing times. Litecoin also has the capability to produce a total of 84 million units, compared to Bitcoins 21 million. In addition, Litecoin uses scrypt in its proof-of-work algorithm, a sequential memory-hard function requiring asymptotically more memory than an algorithm which is not memory-hard.
Still confused? Take a look at this video!

Where can I buy Litecoin?

There are many websites and applications where you can buy and sell Litecoin, but make sure the exchange you are using is trusted and secure. Here are some exchanges that are trusted in the cryptocurrency community:
Exchange
Coinbase USD/Euro/GBP
Bithump KRW
OKCoin Euro/Yen/USD
OKex CNY
Btcmarkets.net AUD
Bitso MXN
Zebpay INR

Where can I securely store Litecoin?

Litecoin (and other cryptocurrencies) is stored in a digital wallet. When storing Litecoin, you want to make sure you trust the place you store them. This is why it is best to store them yourself through the electrum wallet. It is highly suggested to not store your Litecoin in an exchange (such as Coinbase, Poloniex, Bittrex, etc.) because you don't control the private keys. If the exchange ever goes offline, or becomes insolvent, your Litecoin essentially disappear.
Some other options are:
Wallet
Electrum Lightweight Wallet
Official Core Wallet
LiteVault Secure Web Wallet
Paper Wallet Instructions

If you're a fan of mobile devices, then Loafwallet is the wallet for you. Developed by a Litecoin Foundation Dev, losh11, this mobile wallet works great! And remember to always make sure to write down your seedkeys.

Hardware wallets are another great option, in fact, they are said to be the most secure way to store cryptocurrencies. Below is a list of the litecoin flexible hardware wallets.
Wallet
Ledger
Trezor
Keepkey

Where can I spend Litecoin?

Litecoin is in the top ten of all cryptocurrencies by market capitalization. Websites are rapidly adopting Litecoin as a method of payment as well. If you yourself want to accept LTC as a business, you can refer to these merchant manuals. Alternatively, if you would like to explore websites that accept Litecoin, head over to /AcceptingLTC.
Here are also several of our favorite merchants accepting Litecoin.

Where can I discuss Litecoin?

The Litecoin community is extremely kind and robust. There are many forums and places where you can discuss Litecoin with others who are interested in the currency. Here are the main ones:
Platform
Reddit
Litecoin Markets Subreddit
Discord
Official Forum
IRC

Additional Resources and Help

If you have more questions, or are genuinely interested in learning more about Litecoin then be sure to read this series. If you have a specific question that you can't seem to find the answer too, ask below and someone will help you out!
submitted by ecurrencyhodler to litecoin [link] [comments]

Help us archive the Steam Users' Forum (AKA SPUF): you can help download all of SPUF before it goes away on June 5th

As you may or may not have known already, Valve's going to be killing off the Steam Users' Forums, AKA SPUF, on June 5th.
After this date, SPUF and its contents such as obscure fixes for legacy platforms (like http://forums.steampowered.com/forums/showthread.php?t=1774666), general discussions, and everything else will no longer be accessible.

Meet the Archive Team

The wiki states this:
Archive Team is a loose collective of rogue archivists, programmers, writers and loudmouths dedicated to saving our digital heritage. Since 2009 this variant force of nature has caught wind of shutdowns, shutoffs, mergers, and plain old deletions - and done our best to save the history before it's lost forever. Along the way, we've gotten attention, resistance, press and discussion, but most importantly, we've gotten the message out: IT DOESN'T HAVE TO BE THIS WAY.
The Archive Team is loosely friends with, but is not officially affiliated with the Internet Archive, which stores a whole bunch of stuff (audio, video, even vintage books!).

You can help!

Want to help? Great! Hop on #outofsteam on EFNet (#archiveteam too if you want to be informed of future projects) with your IRC client of choice so you can stay informed as to what's happening. Users that are op'ed will usually be the ones knowing what's going on. If you have questions, shout them in the channel, or ask one of those ops.

If you're some average Joe:

Head for this section on the wiki. In summary:
  • Grab a Warrior VM
  • Get VirtualBox/VMWare/similar virtualization program
  • Set up the Warrior file in your virtualization program of choice
  • Run the Warrior VM
  • Set it up (use 1 or 2 concurrent items if you have a rather poor connection)
  • Select "Steam Users' Forum" in the projects list
  • You're now helping!
If you notice high pings in games while you have your Warrior running, consult this section for how to limit bandwidth use: http://archiveteam.org/index.php?title=Warrior#Help.21_The_warrior_is_eating_all_my_bandwidth.21

If you're data capped:

Chances are, if you're this type of person, you're stuck with an ISP with an insane data cap. You might not be able to help to the fullest potential (as each individual item is quite small, but it still adds up), but you can still help in other ways: share the project with your friends. If you might not be able to help, your friends might be able to. Get them to share too: the more people aware and even involved, the better.

If you feel like observing the project:

We have a real-time tracker running for the project: http://tracker.archiveteam.org/spuf/

The Internet Archive could use your help too

The Internet Archive is where a majority of AT grabs are currently stored, including MobileMe, various Yahoo! sites, Friendster, a bunch of Twitch, and more. It takes quite a bit of funds to be able to reliably store even a single TB at the Archive. If you'd like to help keep the lights running, the disks spinning, and the Petaboxes blinking, show your support for the Internet Archive through donating.
There's a very good possibility you've used one of their services in the past, whether it be for recovering lost content, or holding people accountable for their bets about video cards. Even if it's just a one-time donation of $5, it still adds up. Not only does it cost to help store the forums in the first place, it also costs to keep that storage up, redundant (with a EU location for redundancy), and running. The Archive is a non-profit organization. You can even donate with Bitcoins too!
Your support will help ensure that SPUF in its entirety is preserved for future players many years later.
TLDR: Valve's killing off SPUF on June 5th. If you want to help efforts to save it before it goes down for good, go for the "If you're some average Joe" section.
submitted by wickedplayer494 to tf2 [link] [comments]

Dogecoin 1.5.1 Released - Upgrade Now!

We’re happy to announce the release of Dogecoin version 1.5.1!
This release incorporates a range of updates from community contributors, some much needed bug fixes, plus some cool treats brought down-stream from the recent Bitcoin 0.9 release candidate.
Thanks to everyone who helped make this release possible, the entire community appreciates it. We recommend all users update to the latest version and please report any issues you may encounter. As always, backup your wallet.dat file before updating (just to be safe).
Downloads: Windows Installer Windows Archive Mac OS X App
Release highlights: - Switched to Boost 1.55 to fix network connectivity issues on Windows - Removal of reliance on IRC for discovering nodes - Support for URL protocol, eg. dogecoin:addr?amount=xxx&(see Bitcoin’s implementation) - Ability to automatically look up transactions on Dogechain from your client - Working Windows setup script and installer - Opt-in debug logging via -debuglog (to save disk space and stop constant writing) - Fixed Mac Splashscreen’s greedy desktop behavior - Reimplemented testnet, fixing RPC crash due to no genesis block being present - Allow user to load any wallet from data directory specified using -wallet=mywallet.dat - Updated to LevelDB 1.15 to address blockchain database corruption issues - Allow user to send change only to specified address(es) using -change= (one -change parameter per address) - Fixed RPC difficulty look up
Troubleshooting
If anyone experiences issues, delete all 1.4 data (apart from your backed up wallet.dat file) and do a fresh 1.5.1 install.
Enjoy!
submitted by Laika1954 to dogecoin [link] [comments]

Help us archive the Steam Users' Forum (AKA SPUF): you can help download all of SPUF before it goes away on June 5th

As you may or may not have known already, Valve's going to be killing off the Steam Users' Forums, AKA SPUF, on June 5th.
After this date, SPUF and its contents such as obscure fixes for legacy platforms, general discussions, and everything else will no longer be accessible.

Meet the Archive Team

The wiki states this:
Archive Team is a loose collective of rogue archivists, programmers, writers and loudmouths dedicated to saving our digital heritage. Since 2009 this variant force of nature has caught wind of shutdowns, shutoffs, mergers, and plain old deletions - and done our best to save the history before it's lost forever. Along the way, we've gotten attention, resistance, press and discussion, but most importantly, we've gotten the message out: IT DOESN'T HAVE TO BE THIS WAY.
The Archive Team is loosely friends with, but is not officially affiliated with the Internet Archive, which stores a whole bunch of stuff (audio, video, even vintage books!).

You can help!

Want to help? Great! Hop on #outofsteam on EFNet (#archiveteam too if you want to be informed of future projects) with your IRC client of choice so you can stay informed as to what's happening. Users that are op'ed will usually be the ones knowing what's going on. If you have questions, shout them in the channel, or ask one of those ops.

If you're some average Joe:

Head for this section on the wiki. In summary:
  • Grab a Warrior VM
  • Get VirtualBox/VMWare/similar virtualization program
  • Set up the Warrior file in your virtualization program of choice
  • Run the Warrior VM
  • Set it up (use 1 or 2 concurrent items if you have a rather poor connection)
  • Select "Steam Users' Forum" in the projects list
  • You're now helping!
If you notice high pings in games while you have your Warrior running, consult this section for how to limit bandwidth use: http://archiveteam.org/index.php?title=Warrior#Help.21_The_warrior_is_eating_all_my_bandwidth.21

If you're data capped:

Chances are, if you're this type of person, you're stuck with an ISP with an insane data cap. You might not be able to help to the fullest potential (as each individual item is quite small, but it still adds up), but you can still help in other ways: share the project with your friends. If you might not be able to help, your friends might be able to. Get them to share too: the more people aware and even involved, the better.

If you feel like observing the project:

We have a real-time tracker running for the project: http://tracker.archiveteam.org/spuf/

The Internet Archive could use your help too

The Internet Archive is where a majority of AT grabs are currently stored, including MobileMe, various Yahoo! sites, Friendster, a bunch of Twitch, and more. It takes quite a bit of funds to be able to reliably store even a single TB at the Archive. If you'd like to help keep the lights running, the disks spinning, and the Petaboxes blinking, show your support for the Internet Archive through donating.
There's a very good possibility you've used one of their services in the past, whether it be for recovering lost content, or holding people accountable for their bets about video cards. Even if it's just a one-time donation of $5, it still adds up. Not only does it cost to help store the forums in the first place, it also costs to keep that storage up, redundant (with a EU location for redundancy), and running. The Archive is a non-profit organization. You can even donate with Bitcoins too!
Your support will help ensure that SPUF in its entirety is preserved for future players many years later.
TLDR: Valve's killing off SPUF on June 5th. If you want to help efforts to save it before it goes down for good, go for the "If you're some average Joe" section.
submitted by wickedplayer494 to Steam [link] [comments]

What are some tips for torrent site operators?

In light of the recent shutdown of KAT and Torrentz, I thought it'd be pertinent to start a collection of tips and advice for potential future operators of trackers / torrent index sites. So, asking the /trackers community, what steps would you guys take to avoid being shutdown?
Practices:
Is this a decent list? What should be added or corrected?
Resources:
Credits:
  1. cuddle-buddy - link
  2. sillycyco - link
  3. NytronX - link
  4. trackersec_throw - link
  5. pjcnet - link
  6. mildlyincoherent - link
  7. itsmecire - link
submitted by Mal_Dovah to trackers [link] [comments]

Help preserve CS:GO history: your assistance is requested in downloading (and hosting) Twitch broadcasts

As you may or may not have known already, in addition to Twitch implementing a content ID system of their own, videos are now going to be deleted after 2 months for partners, whereas it was previously unlimited storage.
Valuable content is at risk of deletion, including CS:GO matches and events (such as Katowice 2014, ESEA LANs, etc) within 3 weeks.

Meet the Archive Team

The wiki states this:
Archive Team is a loose collective of rogue archivists, programmers, writers and loudmouths dedicated to saving our digital heritage. Since 2009 this variant force of nature has caught wind of shutdowns, shutoffs, mergers, and plain old deletions - and done our best to save the history before it's lost forever. Along the way, we've gotten attention, resistance, press and discussion, but most importantly, we've gotten the message out: IT DOESN'T HAVE TO BE THIS WAY.
The Archive Team is loosely friends with, but is not officially affiliated with the Internet Archive, which stores a whole bunch of stuff (audio, video, even vintage books!).

You can help!

Want to help? Great! Hop on #burnthetwitch on EFNet (#archiveteam too if you want to be informed of future projects) with your IRC client of choice so you can stay informed as to what's happening. Users that are op'ed (including myself) will usually be the ones knowing what's going on. If you have questions, shout them in the channel, or ask one of those ops.

If you're some average Joe:

Head for this section on the wiki. In summary:
  • Grab a Warrior VM
  • Get VirtualBox/VMWare/similar virtualization program
  • Set up the Warrior file in your virtualization program of choice
  • Run the Warrior VM
  • Set it up (use 1 concurrent item if you have a rather poor connection)
  • Select "Twitch Phase 2" in the projects list
  • You're now helping!
If you notice high pings in games while you have your Warrior running, consult this section for how to limit bandwidth use: http://archiveteam.org/index.php?title=Warrior#Help.21_The_warrior_is_eating_all_my_bandwidth.21

If you're some average Joe in Kansas City:

Great! We could use a few Google Fiber lines. It helps massively. Even better if you have multiple lines that have a Fiber installation. See the above section.

If you're data capped:

Chances are, if you're this type of person, you're stuck with an ISP with an insane data cap. You might not be able to help directly, but you can still help: share the project with your friends. If you might not be able to help, your friends might be able to. Get them to share too: the more people involved, the better.

If you feel like observing the project:

We have a real-time tracker running for the project: http://tracker.archiveteam.org/twitchtv/

The Internet Archive will need help too

The Internet Archive is where a majority of AT grabs are currently stored, including MobileMe, various Yahoo! sites, Friendster, a bunch of Google Video, and more. However, due to the sheer size of Twitch, some content will likely have to be sacrificed. We're currently prioritizing more historic events, but if you want to help store more of Twitch, send the Archive a message through donating.
There's a very good possibility you've used one of their services in the past: now is the time for you to give back. Even if it's just a one-time donation of $5, it still adds up. Not only does it cost to help store Twitch in the first place, it also costs to keep that storage up, redundant (with a EU location for redundancy), and running. The Archive is a non-profit organization. You can also even donate with Bitcoins too!
Your support will help ensure that CS:GO history is preserved for future players many years later.
TLDR: historic CS:GO content is at risk of deletion by Twitch. If you want to help efforts to save it, go for the "If you're some average Joe" section.
submitted by wickedplayer494 to GlobalOffensive [link] [comments]

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

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

Interested in contributing to the BTC network? Here is the steps to get a full node up and running in Linux.

These instructions will work both on a VPS cloud server or a personal computer. You may find cheap VPS somewhere online for rent.
What Is A Full Node?
A full node is a program that fully validates transactions and blocks. Almost all full nodes also help the network by accepting transactions and blocks from other full nodes, validating those transactions and blocks, and then relaying them to further full nodes.
Most full nodes also serve lightweight clients by allowing them to transmit their transactions to the network and by notifying them when a transaction affects their wallet. If not enough nodes perform this function, clients won’t be able to connect through the peer-to-peer network—they’ll have to use centralized services instead.
Many people and organizations volunteer to run full nodes using spare computing and bandwidth resources—but more volunteers are needed to allow Bitcoin to continue to grow. This document describes how you can help and what helping will cost you.
Costs And Warnings
Running a Bitcoin full node comes with certain costs and can expose you to certain risks. This section will explain those costs and risks so you can decide whether you’re able to help the network.
Special Cases
Miners, businesses, and privacy-conscious users rely on particular behavior from the full nodes they use, so they will often run their own full nodes and take special safety precautions. This document does not cover those precautions—it only describes running a full node to help support the Bitcoin network in general.
Please consult an expert if you need help setting up your full node correctly to handle high-value and privacy-sensitive tasks.
Secure Your Wallet
It’s possible and safe to run a full node to support the network and use its wallet to store your bitcoins, but you must take the same precautions you would when using any Bitcoin wallet. Please see the securing your wallet page for more information.
Minimum Requirements
Bitcoin Core full nodes have certain requirements. If you try running a node on weak hardware, it may work—but you’ll likely spend more time dealing with issues. If you can meet the following requirements, you’ll have an easy-to-use node.
Note: many operating systems today (Windows, Mac, and Linux) enter a low-power mode after the screensaver activates, slowing or halting network traffic. This is often the default setting on laptops and on all Mac OS X laptops and desktops. Check your screensaver settings and disable automatic “sleep” or “suspend” options to ensure you support the network whenever your computer is running.
Possible Problems
Legal: Bitcoin use is prohibited or restricted in some areas.
Bandwidth limits: Some Internet plans will charge an additional amount for any excess upload bandwidth used that isn’t included in the plan. Worse, some providers may terminate your connection without warning because of overuse. We advise that you check whether your Internet connection is subjected to such limitations and monitor your bandwidth use so that you can stop Bitcoin Core before you reach your upload limit.
Anti-virus: Several people have placed parts of known computer viruses in the Bitcoin block chain. This block chain data can’t infect your computer, but some anti-virus programs quarantine the data anyway, making it more difficult to run a full node. This problem mostly affects computers running Windows.
Attack target: People who want to disrupt the Bitcoin network may attack full nodes in ways that will affect other things you do with your computer, such as an attack that limits your available download bandwidth or an attack that prevents you from using your full node’s wallet for sending transactions.
Linux Instructions
The following instructions describe installing Bitcoin Core on Linux systems.
Ubuntu 14.10 Instructions for Bitcoin Core 0.10.0.
If you use Ubuntu Desktop, click the Ubuntu swirl icon to start the Dash and type “term” into the input box. Choose any one of the terminals listed:
Alternatively, access a console or terminal emulator using another method, such as SSH on Ubuntu Server or a terminal launcher in an alternative desktop environment.
Type the following line to add the Bitcoin Personal Package Archive (PPA) to your system:
sudo apt-add-repository ppa:bitcoin/bitcoin
You will be prompted for your user password. Provide it to continue. Afterwards, the following text will be displayed:
Stable Channel of bitcoin-qt and bitcoind for Ubuntu, and their dependencies
More info: https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin
Press [ENTER] to continue or ctrl-c to cancel adding it
Press enter to continue. The following text (with some variations) will be displayed and you will be returned to the command line prompt:
gpg: keyring /tmp/tmpixuqu73x/secring.gpg' created gpg: keyring/tmp/tmpixuqu73x/pubring.gpg' created gpg: requesting key 8842CE5E from hkp server > > > >keyserver.ubuntu.com gpg: /tmp/tmpixuqu73x/trustdb.gpg: trustdb created gpg: key 8842CE5E: public key "Launchpad PPA for Bitcoin" imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 pg: imported: 1 (RSA: 1) OK
Type the following line to get the most recent list of packages:
sudo apt-get update
A large number of lines will be displayed as different update files are downloaded. This step may take several minutes on a slow Internet connection.
To continue, choose one of the following options
sudo apt-get install bitcoin-qt
sudo apt-get install bitcoind
sudo apt-get install bitcoin-qt bitcoind
After choosing what packages to install, you will be asked whether you want to proceed. Press enter to continue.
If you’re logged in as an administrative user with sudo access, you may log out. The steps in this section should be performed as the user you want to run Bitcoin Core. (If you’re an expert administrator, you can make this a locked account used only by Bitcoin Core.)
Before using the Bitcoin Core daemon, bitcoind, you need to create its configuration file with a user name and password. First create the .bitcoin directory, create (touch) the file, and set the file’s permissions so that only your user account can read it. From the terminal, type:
mkdir ~/.bitcoin touch ~/.bitcoin/bitcoin.conf chmod 600 ~/.bitcoin/bitcoin.conf
Then you can run the command bitcoind. It will print output similar to this:
bitcoind Error: To use the "-server" option, you must set a rpcpassword in the configuration file: /home/bitcoinorg/.bitcoin/bitcoin.conf It is recommended you use the following random password: rpcuser=bitcoinrpc rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions. It is also recommended to set alertnotify so you are notified of problems; for example: alertnotify=echo %s | mail -s "Bitcoin Alert" [email protected] The “rpcpassword” displayed will be unique for your system. You can copy the rpcuser and rpcpassword lines into your configuration file using the following commands. Note that in most Ubuntu terminals, you need to press Ctrl-Shift-C to copy and Ctrl-Shift-V to paste because Ctrl-C and Ctrl-V have different meanings in a Unix-style terminal.
echo rpcuser=bitcoinrpc >> ~/.bitcoin/bitcoin.conf echo rpcpassword=XXXXXX >> ~/.bitcoin/bitcoin.conf (Warning: Don’t use XXXXXX as your RPC password. Copy the rpcpassword displayed by bitcoind for your system.)
Now you can start Bitcoin Core daemon for real. Type the following command:
bitcoind -daemon
It will print a message that Bitcoin Core is starting. To interact with Bitcoin Core daemon, you will use the command bitcoin-cli (Bitcoin command line interface). Note: it may take up to several minutes for Bitcoin Core to start, during which it will display the following message whenever you use bitcoin-cli:
error: {"code":-28,"message":"Verifying blocks..."}
After it starts, you may find the following commands useful for basic interaction with your node:
to safely stop your node, run the following command:
bitcoin-cli stop
A complete list of commands is available in the Bitcoin.org developer reference.
When Bitcoin Core daemon first starts, it will begin to download the block chain. This step will take at least several hours, and it may take a day or more on a slow Internet connection or with a slow computer. During the download, Bitcoin Core will use a significant part of your connection bandwidth. You can stop Bitcoin Core at any time using the stop command; it will resume from the point where it stopped the next time you start it.
Optional: Start Your Node At Boot
Starting your node automatically each time your computer boots makes it easy for you to contribute to the network. The easiest way to do this is to start Bitcoin Core daemon from your crontab. To edit your crontab, run the following command:
crontab -e
@reboot bitcoind -daemon Save the file and exit; the updated crontab file will be installed for you. Now Bitcoin Core daemon will be automatically started each time your reboot your computer.
If you’re an Ubuntu expert and want to use an init script instead, see this Upstart script.
You have now completed installing Bitcoin Core. If you have any questions, please ask in one of Bitcoin’s many communities, such as Bitcoin StackExchange, BitcoinTalk technical support, or the #bitcoin IRC chatroom on Freenode.
To support the Bitcoin network, you also need to allow incoming connections. Please read the Network Configuration section for details.
Network Configuration
If you want to support the Bitcoin network, you must allow inbound connections.
When Bitcoin Core starts, it establishes 8 outbound connections to other full nodes so it can download the latest blocks and transactions. If you just want to use your full node as a wallet, you don’t need more than these 8 connections—but if you want to support lightweight clients and other full nodes on the network, you must allow inbound connections.
Servers connected directly to the Internet usually don’t require any special configuration. You can use the testing instructions below to confirm your server-based node accepts inbound connections.
Home connections are usually filtered by a router or modem. Bitcoin Core will request your router automatically configure itself to allow inbound connections to Bitcoin’s port, port 8333. Unfortunately many routers don’t allow automatic configuration, so you must manually configure your router. You may also need to configure your firewall to allow inbound connections to port 8333. Please see the following subsections for details.
Testing Connections
The BitNodes project provides an online tool to let you test whether your node accepts inbound connections. To use it, start Bitcoin Core (either the GUI or the daemon), wait 10 minutes, and then visit the GetAddr page (https://getaddr.bitnodes.io/). The tool will attempt to guess your IP address—if the address is wrong (or blank), you will need to enter your address manually.
For more instruction and reviews based off BTC please follow my subreddit /BTC_Reviews
all material from this post was found here --> https://bitcoin.org/en/full-node
submitted by Mattjhagen to Bitcoin [link] [comments]

Bitcoin dev meeting in layman's terms (2015-10-8)

Once again my attempt to summarize and explain the weekly bitcoin developer meeting in layman's terms. Link to last weeks summarization
Disclaimer
Please bare in mind I'm not a developer and I'd have problems coding "hello world!", so some things might be incorrect or plain wrong. Like any other write-up it likely contains personal biases, although I try to stay as neutral as I can. There are no decisions being made in these meetings, so if I say "everyone agrees" this means everyone present in the meeting, that's not consensus, but since a fair amount of devs are present it's a good representation. The dev IRC and mailinglist are for bitcoin development purposes. If you have not contributed actual code to a bitcoin-implementation, this is probably not the place you want to reach out to. There are many places to discuss things that the developers read, including this sub-reddit.
link to this week logs link to meeting minutes
Main topics discussed this week where:
Mempool limiting: chain limits Low-S change CLTV & CSV review Creation of bitcoin discuss mailing list
off-topic but important notice
This issue has made most JS bitcoin software vulnerable to generating incorrect public keys. "This is an ecosystem threat with the potential to cause millions of dollars in losses that needs higher visibility; though it's not a bitcoin core / bitcoin network issue. Common, critical, JS code is broken that may cause the generation of incorrect pubkeys (among other issues). Anyone who cares for a JS implementation should read that PR."
Mempool limiting: chain limits
(c/p from last week) Chain in this context means connected transactions. When you send a transaction that depends on another transaction that has yet to be confirmed we talk about a chain of transactions. Miners ideally take the whole chain into account instead of just every single transaction (although that's not widely implemented afaik). So while a single transaction might not have a sufficient fee, a depending transaction could have a high enough fee to make it worthwhile to mine both. This is commonly known as child-pays-for-parent. Since you can make these chains very big it's possible to clog up the mempool this way. The first unconfirmed transaction is called the ancestor and the transactions depending on it the descendants. The total amount of transactions is reffered to as "packages".
As said in "Chain limits" last week Morcos did write a proposal about lowering the default limits for transaction-chains. 2 use cases came up which are currently in use or happened before: As example: someone buys bitcoin from a website and can spend those bitcoin in the marketplace of the same website without waiting for confirmation in order to improve the bitcoin user-experience. This leaves a sequential transaction chain. They don't need to chain more than 5 transactions deep for this, and it falls within the proposed limits. What's not within the proposed limits is the chain of +/- 100 transactions a company had during the spam-attacks. These where simply increased activities by end-users while not enough UTXO's where available (3 to be precise)(UTXO: unspent transaction output, an output that can be used as input for a new transaction). Notably this is with the best practices of using confirmed transactions first. Ways this can be solved from the company's end is to have more UTXO's available before hand, bundling transactions (which requires delaying customer's request) or using replace-by-fee to add payees (which saves blockchain space, is cheaper in fees and gets transactions through quicker, but is not widely deployed by miners atm). Bare in mind these proposals are for default values for the memorypool, not in any way hard limits.
Sense of urgency. Quoting sipa: "my mempool is 2.5G... we better get some solution!" Current attack analysis assumes child-pays-for-parent mining, it should probably be done again without. Higher limits on number of transactions increase attack-vectors. Proposed number of transactions gets some push-back, total size limit not. Mixing default values (for example having a 50% of a 10/10 limit and 50% of a 100/100 limit) wastes bandwidth while there are too many factors that limit utility of long chains as well. 25 transaction limit ought to be enough for everyone (for now).
Review & test Limit mempool by throwing away the cheapest txn and setting min relay fee to it Provide support for Lower default limits for tx chains aka convince people 25 should be enough.
Low-S change
This is in regards to the recent malleability attack. Which is caused by a value 'S' in the ECDSA signature which can be 2 values, a high and low value and still be valid. Resulting in different transaction id's. more info A solution for this is to require nodes to have the "low-s" encoding for signatures. Downside is that it will block most transactions made by sufficiently out of date software (+/- pre-march 2014) This does not replace the need for BIP62, it only eliminates the cheap DOS attack.
95% of transactions already confirm to this, and more fixes have been applied since. BlueMatt has a node which several people are running that auto-malleates to low-s transactions. Questions whether we release it ASAP or wait for the next release and get it to a couple of miners in the meantime (possibly with auto-lowS-malleating)
Contact miners about "Test LowS in standardness, removes nuisance malleability vector" Release scheduled for the end of the month, together with likely check-lock-time-verify and possibly check-sequence-verfiy.
CLTV & CSV backport review
CLTV: checkLockTimeVerify CSV: checkSequenceVerify Both new time-related OP-codes. Been discussed heavily last week.
Concerns whether CSV will be ready enough for release later this month. There's no clarity on how things look when all 3 time related pull-requests are merged. There's a number of people still reviewing the pull-requests. Uncertainty and confusion about whether the semantics are final or not (in regards to using bits from nSequence). nSequence are 4 bytes intended for sequencing time-locked transactions, but this never got used. Now these bytes are being repurposed for a mixture of things. Currently the plan is: " bits 0..15 are the relative locktime, bit 30 determines units (0: height, 1: time w/ 512s granularity), and bit 31 toggles BIP 68 (0: on, 1: off). bits 16..29 are masked off and can take any value."
Clarification from maaku regarding nSequence for BIP68. (after the meeting he explained he was waiting for opinions, but not enough people seemed to know the issue at hand) Continue review of pull requests 6312, 6564 and 6566
Creation of bitcoin discuss mailing list
The bitcoin-dev mailing list is intented for technical discussions only. There's things that don't belong there but need to be discussed anyway. Now this is done in bitcoin-dev, but the volume of this is getting too big. There's recently also an influx of really inappropriate posts, level kindergarden.
No clarity about who are the moderators. Next week there'll be a bitcoin-discuss list created. Decisions are needed as to who'll become the moderators for that and bitcoin-dev. Decisions are needed as to what will be the list and moderation policies.
The bitcoin-discuss list will be created as well as a simple website listing all the lists and corresponding policies. A meeting is scheduled on monday to discuss the moderation and policies of said lists.
Participants
morcos Alex Morcos gmaxwell Gregory Maxwell wumpus Wladimir J. van der Laan sipa Pieter Wuille BlueMatt Matt Corallo btcdrak btcdrak petertodd Peter Todd warren Warren Togami phantomcircuit Patrick Strateman dstadulis Daniel Stadulis GreenIsMyPepper Joseph Poon bsm117532 Bob McElrath
submitted by G1lius to Bitcoin [link] [comments]

Why is there so much excitement for treechains when the core devs don't like the idea?

I'm an investor doing my due dilligence for a possible big Viacoin investment. I just lurk on reddit, so sorry if the below isn't appropriate. Cryptocurrency is somewhat new to me but technology isn't, and often I find what the community thinks is valuable is at odds with what the experts do, often due to good marketing of bad ideas. When I heard Viacoin hired Peter Todd to add treechains to Viacoin I looked to see what the core dev experts on the bitcoin-wizards IRC channel were saying, and it was really negative:
03:11:11 justanotheruser: gmaxwell: do you think treechains will decentralize mining more as a side effect?
03:11:32 justanotheruser: at least mining pools
03:11:59 gmaxwell: I can't figure out what treechains is, it doesn't make much sense to me...
03:12:44 gmaxwell: (or at least to the extent it makes sense to me it doesn't seem worthwhile in the slighest— e.g. results having to hand people oob payment data which is quasi-exponential in size.)
03:16:57 gmaxwell: tacotime: The first part buys you nothing unless you assume participants will not view everything... and then it's not clear how to produce compact proofs that a payment to someone is valid. (PT calls this 'linear' size, but I think thats misleading. If you extract the history of most coins in bitcoin it's enormous, and exponential in the age of the coins due to splits and merges)
03:20:47 gmaxwell: I don't understand why anyone would see it as attractive... esp with how really hard it's been to get people to keep their transaction metadata out of band already.
...and the above is the nicest things they're saying. In fact I could hardly find any mentions of treechains at all in the archives, or Peter's work in general, other than some jokes: (from today)
20:09:17 jgarzik: Peter Todd's employment status is in a state of quantum superposition. He simultaneously works at multiple organizations but if he is ever observed at work it collapses.
...or what sounds like suspicions of wrongdoing: (!)
20:22:47 jgarzik: In any case, altcoins and protocoins and metacoins and whatnot are all potentially nutso investment schemes that are easy to manipulate, if not pre-manipulate. "the world's easiest pump-n-dump scheme" as I've said.
20:22:58 jgarzik: contracting for multiple such entities complicates the trust waters
Finally, all Gavin has to say about the idea is that "Tree chains are a half-baked idea that Peter is excited about." Meanwhile there's lots and lots of discussion about sidechains from all the core devs in the archives, they seem on board with the idea and excited to make it happen. Sounds like a bunch of them are working on sidechains right now even. (am I right?)
Also, why does Peter keep calling himself a core developer? He's not listed as one on the official website, and github shows hardly any contributions from him. Just 33 commits, almost all of which are minor things like adding testcases, trivial one-line features, and documentation tweaks. Granted, Mike Hearn's record is even less substantial, 7 commits, and he's a core dev, so maybe the term means something I don't know.
So what's the deal here? Is this all just another alt-coin pump-n-dump scam backed by clever marketing? (Peter Todd is a fine arts graduate apparently, he doesn't have a comp-sci degree or any other real qualifications!) Or are all the actual core devs wrong?
edit: formatting - sorry, new to reddit!
edit2: Some remarkable replies by btcdrak basically showing Viacoin to be a scam, and probably a pump-n-dump scam. They really should just undo the presale and give all the money back. Simple as that.
Anyway, that's enough for me with treechains.
submitted by treeorsidechains to Bitcoin [link] [comments]

Bitcoin dev IRC meeting in layman's terms (2015-11-12)

Once again my attempt to summarize and explain the weekly bitcoin developer meeting in layman's terms. Link to last weeks summarization Note that I crosspost this to Voat, bitcoin.com and the bitcoin-discuss mailing list every week. I can't control what's being talking about in the meeting, if certain things come up I might not be able to post here because of "guidelines".
Disclaimer
Please bear in mind I'm not a developer and I'd have problems coding "hello world!", so some things might be incorrect or plain wrong. Like any other write-up it likely contains personal biases, although I try to stay as neutral as I can. There are no decisions being made in these meetings, so if I say "everyone agrees" this means everyone present in the meeting, that's not consensus, but since a fair amount of devs are present it's a good representation. The dev IRC and mailinglist are for bitcoin development purposes. If you have not contributed actual code to a bitcoin-implementation, this is probably not the place you want to reach out to. There are many places to discuss things that the developers read, including this sub-reddit.
link to this week logs Meeting minutes by meetbot
Main topics discussed where:
transaction priority for 0.12 Opt-in replace-by-fee Versionbits Chain limits
transaction priority for 0.12
Each transaction is assigned a priority, determined by the age, size, and number of inputs. Which currently makes some transactions free. This currently has a large amount of code, which makes it harder to maintain, and is not that optimal since you can't expect miners to include 0-fee transactions.
Most people seem fine with removing priority in the mempool, but people should be notified ahead of time this is coming. sdaftuar proposed a staggered approach, setting the default value for priority to 0, and remove it entirely in the next release. petertodd notes there will be a natural staggered process since not everyone will upgrade to 0.12 instantly and some implementations might not remove priority at all. Most wallet-software outside of bitcoin-core don't implement priority calculations. As fee estimation becomes more important and many wallet providers use the bitcoin-core fee estimation, improvements on that are welcome. Luke-Jr doesn't agree with removing priority, particularly with changing the mining code to use the priority a transaction has when it enters the mempool. Sipa has the idea to add a small fraction of bitcoin days destroyed divided by the average UTXO age to the fee, so that non-spam-attack transactions are viewed as if they have a larger fee.
While most agree with the proposal to remove the current priority, there's still much debate on whether it needs to be replaced for 0.13, and if so, how.
Review "Improve usage of fee estimation code" BlueMatt will mail the developer mailinglist announcing the changes. ( https://www.mail-archive.com/[email protected]/msg02790.html )
Opt-in replace-by-fee
Currently when a node sees a transaction that spends the same output it ignores it. With replace-by-fee it replaces the current transaction in the mempool if it has a higher fee. This allows for things like spending "stuck" transactions, adding more recipients to a transaction in order to prevent chaining, etc.
Since there are people that accept 0-confirmation transactions and this would make it extremely easy to double spend them, this is made opt-in. The sender can choose to opt-in to replace-by-fee by changing an input in the nSequence field.
Peter Todd wrote some tools to use replace-by-fee. link It would be nice to have opt-in per output instead of the whole transaction, however that would be very hard to implement and would have some privacy concerns. Luke-Jr would like to see an option to toggle between first-seen-safe/full RBF and neveopt-in/always. Since there are possibly some objections with the "always" toggle it should be a separate pull-request.
review and merge nSequence-based Full-RBF opt-in Peter Todd will write a mail to the list to explain how it works and how people can not accept opt-in transactions.
Versionbits
BIP 9 Currently softforks have been done by the isSuperMajority mechanism, meaning when 95% of the last X blocks has a version number higher than Y the fork is deployed. A new way of doing this is currently being worked on and that uses all bits of the version number, appropriately being called versionbits. So instead of a fork happening when the version is larger than (for example) 00000000011 (3), a fork happens when (for example) the 3rd bit is up (so 00100000011). This way softforks can be deployed simultaneous and independent of each other.
There are 2 different implementations. One from Codeshark and one from Rusty jtimon thinks both implementations are more complicated than they need to be. There needs to be a minor revision namely a starting time for proposals. In general we'd like to get this in soon, but existing softforks need to complete first.
CodeShark adds a starting time to versionbits.
Chain limits
Chain in this context means connected transactions. When you send a transaction that depends on another transaction that has yet to be confirmed we talk about a chain of transactions. Miners ideally take the whole chain into account instead of just every single transaction (although that's not widely implemented afaik). So while a single transaction might not have a sufficient fee, a depending transaction could have a high enough fee to make it worthwhile to mine both. This is commonly known as child-pays-for-parent. Since you can make these chains very big it's possible to clog up the mempool this way. With the recent malleability attacks, anyone who made transactions going multiple layers deep would've already encountered huge problems doing this (beautifully explained in let's talk bitcoin #258 from 13:50 onwards) Proposal and github link.
Wumpus doesn't feel comfortable with merging it because there's some controversy from companies who exceed the limits (or could be/want to). jgarzik does feel comfortable with it, and many think it should be merged as it's easy to revert if needed. There's little choice as it's not safe from attacks without limits. We should communicate the replace-by-fee sendmany alternative to long chains (adding new recipients on existing non-confirmed transactions), although it won't show up in users wallet yet and block-explorers probably aren't ready to display it correctly. Emphasis on the fact it's a change in default values, not a consensus change, however default values have a lot of power. The final limits are 25 transactions and 101kb total size for both ancestor and descendant packages.
jgarzik will merge the pull-request. Morcos will mail the list once it's merged.
Participants
BlueMatt Matt Corallo petertodd Peter Todd morcos Alex Morcos jgarzik Jeff Garzik gmaxwell Gregory Maxwell wumpus Wladimir J. van der Laan Luke-Jr Luke Dashjr jtimon Jorge Timón btcdrak btcdrak phantomcircuit Patrick Strateman sipa Pieter Wuille CodeShark Eric Lombrozo sdaftuar Suhas Daftuar jg_taxi jg_taxi gavinandresen Gavin Andresen cfields Cory Fields bsm1175321 Bob McElrath 
Comic relief
19:53 sipa new topic? 19:53 wumpus any other topics? 19:53 petertodd  19:53 jgarzik did we cover jonas while I was in the taxi? 19:54 sdaftuar ? 19:54 jtimon ? 19:54 CodeShark not sure I want to know 19:54 jgarzik proposal for new GUI maintainer 19:54 CodeShark sounds kinky, though 19:54 petertodd CodeShark: GUI's are pretty kinky 19:56 BlueMatt ok, end meeting? 19:56 btcdrak if we can remember the command this week :-) 19:56 wumpus #meetingend 19:56 gmaxwell #destroymeeting 19:56 wumpus #endmeeting 19:56 Luke-Jr #endmeeting 19:56 lightningbot Meeting ended Thu Nov 12 19:56:42 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 19:56 BlueMatt #magicmeetbotincantation 19:57 petertodd #DoWhatIMean 
submitted by G1lius to Bitcoin [link] [comments]

Bitcoin Origins

Afternoon, All.
Today marks the eighth anniversary of the publication of the Bitcoin white paper.
As a special tribute, I will provide you with a short story on the origins of the Bitcoin tech.
I've been out of the game for many years, however now I find myself drawn back - in part due to the energy that's being added by the incumbents, in part due to information that's become public over the past year.
I haven't followed the Bitcoin and alt coin tech for the past five or six years. I left about six months before (2).
My last communication with (2) was five years ago which ended in my obliteration of all development emails and long-term exile. Every mention of Bitcoin made me turn the page, change the channel, click away - due to a painful knot of fear in my belly at the very mention of the tech.
As my old memories come back I'm jotting them down so that a roughly decent book on the original Bitcoin development may be created.
The following are a few of these notes.
This is still in early draft form so expect the layout and flow to be cleaned up over time.
Also be aware that the initial release of the Bitcoin white paper and code was what we had cut down to from earlier ideas.
This means that some of the ideas below will not correspond to what would end up being made public.
Bitcoin Logo
BitCoin Origins
Six Months In A Leaky Boat
Introduction
I have always found that there’s a vast gulf between knowledge and understanding.
Wherever I looked I’ve found very intelligent folks who had immense knowledge in their subject but with little understanding of what to do with it, how to mould it, how to create something new.
They could only ever iterate incrementally to improve the knowledge in their given field.
Understanding comes from experiences outside of knowledge in a particular subject.
The following story is about a most unique project and the understanding that was used and applied to the e-cash problem which resulted in the experiment called Bitcoin.
It is to show the thought process, stream of consciousness, arguments, examples, concerns and fears that went through our minds has we tussled with this beast and hammered out something that may actually work.
There is no verification of truth here. There is absolutely no evidential proof that I had any part in the project. All evidence was purged in late 2011 - the reason will become apparent. Only (2) should know of my involvement (until now). Take this as just a fictional story if you wish.
Who am I ? I went by the ‘net handle Scronty back then.
scrontsoft.com
I have always been interested in computer and electronic technology since the age of eleven. Seeing what others had made these machines do, and then trying to push it a little bit further out.
Whenever there was a problem to be figured out I would always begin with what the current state of knowledge was - after all, we all stand on the shoulders of all those who have gone before.
Quite often I found that the assumptions folks hold for a particular problem are the things that are holding them back from figuring out a new solution.
So I would begin by questioning peoples basic assumptions on various subjects
This usually resulted in annoying all of these knowledgable folks.
You get the idea.
You see it on every single message board since the mid-nineties onwards.
There’re also a lot of egotistical chips on folks shoulders where you’d find that they’d look down on others and belittle them on topics that they themselves had only just learned a few weeks earlier.
This is particularly true in programming and crypto forums.
Start
A couple of guys worked with an online betting company.
They had a problem.
For punters to use their service they had to provide credit card details and pay for chip tokens.
However, many times a punter would play the online pokey machines, lose all of their money and then reverse the credit card charge saying “It’s unauthorised. It wasn’t me”.
Sometimes the company’s network would not record the funds transfer correctly and so the punters funds were removed from their credit account into the company’s account but no record of it was made on the company’s end - so the punter didn’t receive any play tokens and, again, tried to reverse the charges.
The large credit card issuing companies also actively stopped allowing credit cards to be used for online gambling and began refusing to reverse the charges.
What these guys needed was a way to transfer funds between punters and the online betting companies so that both parties could trust that everything was above board.
That a payment could not be made by mistake and once a payment went through it was unchangeable, irreversible.
(2) had been on the periphery of the cypherpunks group since the mid 1990’s. When I entered the project in early 2008 he had been working on the problem part-time over the past five years. Over the previous year or so he’d been working on the problem full-time. He was writing a white paper for an e-cash system for the online betting/gambling company to use ( or to license out the solution to multiple companies ) plus writing the code for it.
He was attempting to implement a working example of electronic cash.
There were other cryptographers who he was communicating with however it just wouldn’t “work”. There were always too many attack vectors with the solution and even though, from a cryptographic point-of-view, the white paper and code was appropriate, he found it unsatisfactory.
After talking to his friend (3) it was decided that maybe they had their noses too close to the grindstone and that they should find someone who wasn’t a cryptographer to look over the ideas.
The problem is that to find such a person is very difficult. He’d have to be smart enough to understand cryptography (or learn it), also be interested in the subject but also not currently be a cryptographer.
Usually the folks who were smart enough and had an interest were already cryptographers.
Through various IRC (Internet Relay Chat) channels (3) came across me and I ended up being put in touch with (2).
With my work in the Win32 Asm community I’d shown I was smart enough and could figure out the solutions to difficult problems.
Plus I’d made sure my public profile was always dealing with grey-to-white topics (no online gambling stuff).
Request For Help
I was asked to take a look over what had been written in the white paper and see what needed to be changed as the code implementing it just wasn’t working - the pieces wouldn’t fit together or the whole thing would fail if certain pre-conditions in the network weren’t met.
(2) wanted to publish the white paper before the end of the year (2008).
I began reading through the document - understanding very little.
Hashing and encrypting and decrypting and private keys and public keys.
Different types of hashing algorithms, encrypting then hashing and hashing then encrypting.
Oh my!
“Just tell me what I need to change to make it work” - (2) kept asking me.
“I dunno what the [redacted] I’m reading here” - I replied.
(2) thought that maybe he’d made a mistake and he’ll just try and find someone else.
I told him that he’s going about fixing it the wrong way.
“How should it be fixed ?”, he asked.
“Well, first I need to know what I’m reading. So you’re going to have to give me info on the various crypto stuff in here”, I said.
“No no no”, he said. “ If you learn the meaning of the cryptographic jargon you will be influenced by it and would no-longer be the “non-cryptographer” that we need to look over the white paper”.
I told him that without learning the jargon I cannot read the paper in the first place.
Also - as I learn I will understand more and will be able to tell you what you need to change.
If or when it got to the stage that I’d learned too much and also had my nose too close to the grindstone then I could leave the project and he could find someone else to replace me.
He agreed that having me learn a bit about cryptography may be a good idea (:roll-eyes:).
He told me to get started.
I asked where the information was.
He said “Google it”.
I said “Nope. You’ve been working in this area for the past few years so you can give me a link to the websites with the info."
He returned with a list of website links and said to go through that and look at the white paper.
The list had about 109 links in it - bloody [redacted].
One-by-one I began going through the information.
After a few weeks I’d gone through about half-a-dozen papers/websites which hadn’t cleared up anything.
Once three or four weeks had gone by I threw my hands up in disgust and told him “At this rate I’ll be here all year and still not understand all the pieces. You’ve got to filter this down for me. You’ve already read all of these documents and websites so give me a list of the most important docs/websites you think would be helpful in understanding your white paper”.
He came back with a list of about 23 white papers and websites.
“Now list them in the order you think I should read them in”.
He came back with a sorted and filtered list of crypto-docs and websites.
I began reading through them - starting at the first.
Transactions
Given a computer network there had to be transactions sent to a recipient.
The initial white paper was pretty much a shuffling of the various cryptographic e-cash white papers at the time. We knew that when someone wanted to send a payment to another person it would have to be transmitted across a network securely.
But how to solve the double-spend problem ?
A piece of physical paper cash can only be in one place at a time - you cannot double-spend a physical currency note. All current electronic cash solutions relied upon a central server to control the allocation of coin and to make sure no coin could be double-spent.
But if that server went down, or was unaccessible due to a DDOS attack or government intervention ( or someone just tripping over a power cord ) then no more money.
We knew that a coin would initially be minted somehow.
I found most of the methods written in white papers and on websites were rubbish ( Personal opinion here. No disrespect to those who wrote those white papers ).
They either tried to pretend to act as central banks or tried to allow a “mates club” whereby they all agreed who's going to get coin at a particular time.
Kind of like politicians using an "independent" third party to give themselves a pay rise.
We knew that a piece of electronic cash would be minted somehow, however once it was minted how could it be sent to someone else ?
(2) and I went back and forth with a few ideas, going through the physical process of different transaction types one by one and adjusting how a transaction data package would look like.
We began with a single piece of e-cash.
Like a piece of gold, it should be able to cut smaller pieces off of it.
That means by starting with one item we’d end up with two - the piece going to the recipient and the change coming back to the original owner.
I told (2) that when drawn into a diagram it looks like electronic or computer logic gates.
Logic Gates
Except sometimes there can be more outputs than inputs. And in the end it looks like a neural network.
If we had a large piece and were paying that entire amount to someone then the input and output pieces would be the same.
If we had a large piece and were paying a small amount to someone then the input would be the large piece and the outputs would be the amount being paid plus a small piece as change.
As more people are paid we’d end up with a lot of small pieces in our wallet.
If we had a small piece and needed to pay someone a large amount then we could combine multiple small pieces to be equal or larger than the amount to be paid, and refund back to ourselves any change left over.
This means a transaction would have to allow multiple inputs and multiple outputs, with each input signed by the current owners private key and the outputs being the new owners public key.
Transaction Types
One day he came back to me saying his friend (3) wanted to communicate directly with me but he was a super-paranoid fella and I had to encrypt any messages using private/public keys.
It was a [redacted] nightmare.
I had to:
This was all so he could confirm that the message was indeed from me and had not been intercepted or changed.
Then he decided that I’d also have to generate new private/public keys for every single email just in case a previous email had been intercepted.
I told (2) that this just wasn’t going to happen.
I’ve always disliked using command line programs directly and always thought that they should always be executed from a GUI ( Graphical User Interface).
I said “You’re going to be my filter for this project and main conduit in this team. I send emails to you, you communicate with whoever you need to and send their replies back to me. Or you send their requests to me and I reply back through you.
And what’s this annoying command line proggy anyway? What the [redacted] is it doing?
(2) gave me the link to the information - it was in that list of 109 docs/websites but not in the filtered list of 23.
It was to Hal's website where he very clearly explained how something called "Hashcash" worked.
Hals RPOW
From there I went on to Adam's site:
Hashcash
(which was not even in the original list at all).
I read the Hashcash white paper sections until I hit the calculations and my eyes begun to glaze over.
Hashcash
I read the first few paragraphs and knew this was something interesting.
I asked (2) if he could check whether this document was the final version or if there had been improvements/ amendments/ updates to it.
He said he thought I was wasting my time with this and I should continue with the other docs/websites in the list he’d provided me.
I told him that I’m the only one who would know what info is important and to look into the Hashcash origin for me. He came back a couple of days later and said it was confirmed that the public document linked was the final version of the Hashcash paper.
I asked how he could confirm it?
He told me that he’d contacted the original website author Hal and asked him for any updated document and Hal had replied back with the exact same public link.
He’d even copy/pasted Hal’s reply in the email to me.
I said “Wait… What ? …”
“You actually contacted the original author of the reference material ?”
He said “Yep. Who else would I go to to confirm the document, except to the author themselves ?”
I told him it was really quite rare to have someone check with the original author or sources. Most folks read something and take that as fact, or read the reference documents and take those as fact.
If someone read about the Boyer-Moore search algorithm they take it as fact that what they’ve read is the official final solution. I haven’t heard of anyone contacting Boyer or Moore to check for any updates/ improvements/ amendments.
The Boyer-Moore search algorithm is something that went through the rounds on the Win32Asm community forum for a while.
I found this quite intriguing. Even with (2)’s occasional grating personality it would be very useful to have someone who’s prepared to hunt down the original authors like this.
I asked him if he'd contacted the Hashcash author and he said he'd sent emails to every single author of all of the websites/ white papers and only about a dozen or so had ever replied back to him.
I had begun to write up a list of what the various problems were for creating an e-cash system from the other e-cash system white papers and websites I had been studying.
I was still referring back to the white paper (2) had supplied me however it was really just a mishmash of what everyone else had been doing over the years.
Hence why it failed like all of the others.
One of the problems was a trusted time stamp so that folks would know that funds hadn’t been double-spent. Another was the minting of the tokens in the system and trusting the minting source.
If I recall - practically every single white paper out there ( including the one suppled to me ) used a trusted third party as the source for a time stamp and a convoluted method to check it hadn’t been tampered with.
And the minting either used a trusted third party to generate coins on a regular basis or had a network of nodes agree on how many tokens to generate and give to each other.
(2) said that we need to use the trusted third parties because how else can we trust the time stamp and the minting of the tokens.
I told him he was thinking of it in the wrong way.
You’re assuming a trusted third party is needed, just because every single other cryptographic white paper says that’s how you do it.
But you’re also saying that you can’t rely on a trusted third party because that makes a single point attack vector that can bring the whole system down to its knees.
“Remember Sherlock Holmes” I said. “ ‘When you have eliminated the impossible, whatever remains, however improbable, must be the truth ?’.
The assumption of a trusted third party in an functioning e-cash system must be eliminated as impossible for this to work.
So if we cannot have a trusted third party for this, what are our other options ?”
“I have no idea”, (2) replied. “Do you believe this proof-of-work thing you’re looking into can be used for this somehow ?”.
“I dunno. It definitely has some possibilities. It’s made for making sure the data being sent and received comes from a known trusted source and that it hasn’t been tampered with”.
It forces the user computer to generate a hash of the data to find a hash with a prepended number of zeroes. If the hash isn’t found it increments a value and hashes again. It just keeps repeating until a hash is found with the correct number of prepended zeroes.
This means that the user computer has to spend time working on the hashes until it finds one and only then can it stop.
It was designed to eliminate the email spam problem that we all have because a spam-sender would need to use a lot of computing resources to generate hashes for all the emails sent out ( the data that’s hashed includes the recipients email address so a new hash is required for every single email recipient ).
It also has a throttle so that the difficulty in generating a hash can be increased over time as the general computing hardware improves.
The minting problem is also sorted due to the electricity used in generating a hash can be used to mint the e-cash and put it into circulation.
Effectively - the real fiat-currency cost (via electricity consumed) of generating the valid hash is how much e-cash is given to that minter.
It also sets what the price of the minted e-cash should be, as there is a direct correlation between a real-world electricity bill and the digital e-cash amount minted.
Taking the time used to generate the hash with how much energy the cpu used during the generation ( only the time spent on hashing - not other computing resources ) with the local electricity costs of the suburb/county/province/state/nation the minter resides within, then each minter could have a locally-adjusted e-cash value added to their account.
It would mean that someone minting in a country with cheap electricity due to state-subsidised support would receive less e-cash because less real-world fiat currency was expended in the generation of the hash.
So now we had a mechanism in which this e-cash would work.
I'll stop this story here for now and post a follow-up depending upon its reception.
The follow-up will contain some of the details of how the idea of a chain of blocks came about, plus some of the tech that was left out of the initial white paper and public code release ( it was, after all, just the first experiment to check whether this tech would actually work ).
Bitcoin Origins - part 2
As a side-note:
When you read the Bitcoin white paper again, the Introduction, Calculation, Conclusion and References sections were written and edited by (2) and (3).
The Transactions, Timestamp Server, Proof-of-Work, Network, Incentive, Reclaiming Disk Space, Simplified Payment Verification, Combining and Splitting Value and Privacy sections were from text copy/ pasted from emails from me to (2) explaining how each part worked as they were being figured out.
I wrote the Abstract text when (2) asked me to write the Introduction. (2) used it as the Abstract section because he found it too terse for an introduction.
(2) and (3) edited the entire document and removed any double-spaces from it, adding titles to the various sections and adjusting between 2% and 5% for spelling errors and gramma sentence structure.
You can see the original Abstract with double-spacing here: Public Mailing-list Posting
There was a huge misunderstanding between us all during the formation of the white paper which I'll mention next time.
Cheers,
Phil
(Scronty)
vu.hn
submitted by Scronty to Bitcoin [link] [comments]

Block Digest #228 - Gief Loan Please - YouTube Best Bitcoin Mining Software That Work in 2020 FORTNITE HACK ⚡ FREE CHEAT ⚡ AIMBOT ⚡ WALLHACK ⚡ ESP ⚡ MORE ⚡ UNDETECTED 2020 Best Bitcoin Miner Machine Free download ❤️ Best BTC Miners in 2020 Bitcoin Mining Software 2020 For PC Free Download

A Bitcoin IRA is a special investment because it is not linked to the other investment options such as finance, bonds and stock. In times of global economic crisis, bitcoin isn’t infected with the toxicity of the markets. The factors that influence its price are different, which adds to its value as an option to spreads your risks. ↑ Tutorial: Bitcoin Core on a Raspberry Pi, retrieved 26 August 2015 ↑ How to build a Bitcoin node on the Raspberry Pi 2, archive.org copy 09 September 2015 ↑ 3.0 3.1 #bitcoin IRC log 9 May 2015 Bitcoin history for 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019. Bitcoin price chart since 2009 to 2019. The historical data and rates of BTC Less formal development discussion happens on irc.freenode.net #bitcoin-core-dev (web interface, logs). To report an issue, please see the bug reporting page. Code Review. Bitcoin Core is security software that helps protect assets worth billions of dollars, so every code change needs to be reviewed by experienced developers. This will create the directory bitcoin-0.20.0 within your current working directory. We will install the contents of its bin subdirectory into the /usr/local/bin directory using the the install command. The install command is part of the GNU coreutils available on nearly every Linux distribution, and the /usr/local/bin directory is a standard location for self-installed executables (you may

[index] [46248] [38905] [8471] [1515] [37117] [47057] [7527] [31510] [14563] [5959]

Block Digest #228 - Gief Loan Please - YouTube

Bitcoin and Cardanos' ADA - Weekly Technical Analysis – July 13th, 2020. Weekly Crypto Tech Review with Bob Mason, FX Empire. Key support resistance levels. It’s a bullish start to the week ... #bitcoin #twitter #crypto #interest #stockmarket #recession #bearmarket #bullmarket #davincij15 #mmcrypto #btc #bitcoinprice #bitcointoday #crash #economy #inflation #ecb #fed #federalreserve # ... qbot botnet scanner, qbot botnet files, qbot botnet setup, qbot botnet tutorial, qbot botnet download, qbot botnet setup tut, qbot botnet source, qbot botnet github mirai botnet source, mirai ... Beyond elite capture: Promoting livelihoods and jobs in South Africa’s land reform - Duration: 57:17. Institute for Poverty, Land and Agrarian Studies 208 views. New To use Bitcoin Miner Machine download the latest version from the link above, open it and extract the archive to anywhere on your PC (we recommend your Desktop so you can easily access it), then ...