Bitcoin-fr — Bitcoin Wiki

Bitcoin - The Currency of the Internet

A community dedicated to Bitcoin, the currency of the Internet. Bitcoin is a distributed, worldwide, decentralized digital money. Bitcoins are issued and managed without any central authority whatsoever: there is no government, company, or bank in charge of Bitcoin. You might be interested in Bitcoin if you like cryptography, distributed peer-to-peer systems, or economics. A large percentage of Bitcoin enthusiasts are libertarians, though people of all political philosophies are welcome.
[link]

BitcoinAustin

News surrounding Bitcoin in the Austin, TX area.
[link]

BetterBitcoin

BetterBitcoin is a subreddit for news, discussion and jokes about the currency of the internet (or the internet of currency): Bitcoin.
[link]

freenode/

freenode.net
[13:47:03] The guide is divided into sections, each with a specific section of activity and a cause for why I should work on that area.
[13:47:03] Those are still facts
[13:47:08] So there is still a little more work to do.
[13:47:15] I need to add all the pages to the wiki.
[13:47:18] After that, I'll start putting more resources up, including some images and if I'm doing it right, some story sections.
[13:47
freenode/ip.92.189.211.175) has joined #/cicada3302
[17:37] O_O
[17:37] damnit
[17:37] dude who's running said server?
[17:37] anyone?
[17:37] I'm at work... http://www.reddit.com/cicada3302/comments/1s3wwz/found_the_code_has_been_decoded_everything_is/cdtr0oa
[17:38]
freenode/ip.50.212.6.250) has joined #bitcoin24
ekdudez: your p2pool network is really part of your bitcoin.dat (A link to your wallet can be found here: https://www.reddit.com/bitcoin/comments/2pq3nx/live_updates_on_the_relay_problem/).
* LQbot (~[email protected]) Quit (Ping timeout: 192 seconds)
ekdudez: your node is NOT part of the bitcoin.dat file, and if it were it wouldn't have a
freenode/ip.39.149.160.167) has joined #/cicada3302
[21:18] or uh, scribe great, wtf?
[21:18] He's come into this room, perhaps from the dark house? So we should return the greeting?
[21:18] (We can't go there. I don't think. He's been there before, but on a cloudy day.)
[21:18] <@shecalledmepaul> no it's been such a while since youve heard anything that I don't think you'll remember
[21:18] <@shecalledmepaul
freenode/ip.54.232.161.153) Quit (Ping timeout: 245 seconds)
[10:47] how about talk about the XP drop rate in general?
[10:47] also
[10:47] <@dine909> wait wtf
[10:47] <@dine909> X is 75%
[10:47] <@dine909> of XP
[10:47] i think you have to have very high level to get 95% in dungeons
[10:47] <@dine909> yeah i guess
[10:48] but yeah
[10:48] maybe it has something
freenode/ip.68.56.156.96] has joined #/cicada3302
[01:45] and yes, we have /vaspool/cicada3302/daemon/rules also. anything is possible, we know that
[01:45] not everything though
[01:45] well, some of the entries do not exist
[01:45] So this new detective in the thread goes by "ricardo75"?
[01:46] Hi everyone, I am new here, but I'm quite convinced that whoever made this 2.
submitted by ObsidianMinor to talktotransformer [link] [comments]

Questionable Decisions

Facts
linustechtips.com:
In 2017 Knapp sold CyberGhost to an Israeli company called Crossrider for €9.2 million.
Crossrider changed its name to “Kape Technologies” in 2018 – for reasons that we’ll explain below.
Now here’s where things get interesting. When you research the company Crossrider (now Kape) you learn it is a company known for infecting devices with malware.
When you research the company Crossrider, you find numerous articles about Crossrider malware and adware, such as this article from Malwarebytes:
Crossrider offers a highly configurable method for its clients to monetize their software. The common method to infect end-users is software bundlers. The installers usually resort to browser hijacking. Targeted browsers are Internet Explorer, Firefox, Chrome, and sometimes Opera. Crossrider not only targets Windows machines but Macs as well.
PUP.Optional.Crossrider installs are typically triggered by bundlers that offer software you might be interested in and combine them with adware or other monetizing methods.
According to Malwarebytes and many other reputable online security websites, Crossrider was hiding malware in software bundlers, which would then infect the user’s computer with “adware or other monetizing methods”.
Trust takes years to build, second to break and Forever to repair.
submitted by KSOFM to PrivateInternetAccess [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]

Velkommen til BitcoinDK

Følgende videoer er et godt udgangspunkt til at forstå, hvordan Bitcoin virker og en lille smule om dets potentiale på lang sigt:
Tjek video wikisiden eller BitcoinTV.
Køb/Sælg bitcoins
Webshops med Bitcoin betaling
Webshops i EU med Bitcoin betaling
Webshops i med Bitcoin betaling * Newegg - Elektronik mm.
Lightning Network
LN on IOS
LN on Android
Hvad kan man med LN?
Steder hvor du kan bruge bitcoins, dog ikke nødvendigvis uden dialog
Donér
Info
Skat
Hanne Søgaard Hansen:
Men man er nødt til at set på den konkrete situation. Er det for at sælge eller for at bruge bitcoins som betalingsmiddel? * skat.dk - Guide * skat.dk - Skattefri gevinst * Børsens fortolkning * Spekulations beskatning Hvis du købte bitcoins for at sælge dem igen, og hvis de er faldet i værdi så kan du få fradrag. * Skattefri gevinst ved anvendelse som betalingsmiddel (Bindende personlig svar fra skat)
Moms
Reddit
Gode banker
Onde banker
Danske kryptonyheder
Ramt af ransomware
Nyttige sider
Chat
Via IRC - irc.freenode.net
submitted by bitcoinDKbot to BitcoinDK [link] [comments]

Beginner's Guide: Where to start & FAQ!

Welcome to /Litecoin!

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
Kraken
247Exchange
Bittrex
Quadrigacx
 

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 Generator
 
If you're a fan of mobile devices, then Loafwallet is the wallet for you. Developed by a Litecoin community member, losh11, this mobile wallet works great!
 
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 now the sixth-largest true cryptocurrency by market capitalization. Websites are rapidly adopting Litecoin as a method of payment, if you would like to explore websites that accept Litecoin, head over to /AcceptingLTC.
Here are several of our favorite merchants accepting Litecoin:
Merchant
EGifter
Cheap Air
Bitfly
All Things Luxury
AFK Apparel
Many more!
 

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
 

Litecoin Statistics

Find them here
 

Additional Resources and Help

If you have more questions, or are genuinely interested in learning more about Litecoin then be sure to check out the Litecoin Wiki. 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 Sparkswont to litecoin [link] [comments]

Surae's (me) end-of-November (2017!) update.

You can check it out on the forums here. Here's a copypasta:
Surae's End of November (2017!) Update
Hello, everyone! Sarang posted his update a few days ago to give the community time to review his work before the end of the month. I was hoping to finish multisig off before the end of this month... so I held off on writing this update until then... but it looks like I'm somewhere between 2 days and a week behind on that estimate.
MRL Announcements
Meetings. We are holding weekly meetings on Mondays at 17:00 UTC. Logs are to be posted on my github soon(tm). Usually we alternate between "office hours" and "research meetings." At office hours, we want members of the community to come in and be able to ask questions, so we are considering opening up a relay to the freenode channel during office hours times, unless things get out of hand.
POW-Difficulty Replacement Contest. Some time in December, I am going to formalize an FFS "idea" to open up a multiple-round contest for possible replacements for our proof of work game. The first round would have a 3- or 6-month deadline. Personally, I would love it if this FFS could have an unbounded reward amount. If the community is extremely generous, we could easily whip up a large enough reward to spur lots and lots of interest across the world.
The Bitcoin POW game uses SHA256 to find nonces that produce hashes with sufficiently small digests according to the Bitcoin difficulty metric. Our current POW game uses CryptoNight to find nonces that produce hashes with sufficiently small digests according to the CryptoNote difficulty metric. The winner need not be proof of work. My current thoughts are roughly this:
All submissions will be public. Submissions that minimize incentives for centralized mining (or maximize disincentives) will be preferred over submissions that do not. Submissions that are elegant will be preferred over submissions that are not. Submissions that have provable claims about desirable properties will be preferred over submissions that do not (e.g. for either the Bitcoin or the Monero POW games, the necessary and sufficient network conditions for these games to produce blocks in a Poisson process have not been identified, to my understanding). Submissions that have a smaller environmental impact will be preferred over submissions that have a larger impact. And so on. I would like as many ideas as possible about a judging rubric for the first round. Especially if a large amount of money will be put up as a prize.
The details of the next round would be announced along with the winners of the first round. The reward funds should be released when a set of judges agree on a winner. MRL and Monero Core should each have representation on the panel of judges, and there ought to be at least one independent judge not directly associated with the Monero Project, like Peter Todd, Tim Ruffing, or someone along those lines. But, again, this is just an idea. If the community doesn't like it, we can drop it.
Here is a rundown for November
Multisig. Almost done. I know, I know, it's been forever. We, as a community, have recently come to see how important it is to carefully and formally ensure the correctness of our schemes before proceeding. Multisig is a delicate thing because a naively implemented multisig can reveal information about the participants.
I'm finishing vetting key creation today, finishing signatures tomorrow and the next day. Then I'm passing the result off to moneromooo and luigi to ensure that my description of their code is accurate up to their understanding. Then onto Sarang for final reviews before submission, hopefully by the end of the month. I have my life until Sunday evening blocked off to finish this. A copy of the document will be made available to the community ASAP (an older version is on my github), after more checking and writing is completed.
This whitepaper on multisig will be broken into two papers: one will be intended for peer review describing multi-ring signatures, and one will be a Monero Standard. More about that later...
RTRS RingCT column-linkability and amortization. You may say "what? I thought we were putting RTRS RingCT on the back burner?" Well, I'm still think ing about amortization of signatures. I'm thinking it will be possible (although perhaps not feasible) for miners to include amortized signatures upon finding new blocks. This would allow users to cite an amortized signature for fast verification, but has some possible drawbacks. But more exciting, I'm also chatting with Tim Ruffing, one of the authors on the RTRS RingCT papers: he thinks he has a solution to our "linkability by columns" problem with MLSAG and RingCT. Currently we try to avoid using more than one ring signature per recipient. This avoids linking distinct outputs based on bundling of these ring signatures. Ruffing believes RTRS RingCT can be tweaked to prove several commitments in a vector of commitments; this would allow a single RTRS RingCT to be computed and checked for each output being spent.
Once all the details are checked, I'll write up a document and make a copy of it available to the community. If it works, of course.
Consequences of bulletproofs. In my last end-of-month update I hinted at issues with an exponential space-time trade-off in RTRS RingCT. Due to the speed and space savings with bulletproofs, it may now be feasible to implement RTRS RingCT. With improved verification time savings with bulletproofs we can relax our requirements for verification times for signatures. This will allow the slightly longer verification times of RTRS RingCT to be counter-acted. Solving the problem "what ring sizes can we really get away with?" involves some modeling and solving some linear programming problems (linear programming, or linear optimization, is an anachronistically named area of applied mathematics involved with optimizing logistic problems... see here for more information).
Hence, we will be inserting bulletproofs into Monero with low friction, and then we will look into the logistics of moving to RTRS RingCT.
Monero Standards. Right now, we don't have a comprehensive list of how Monero works, all the various primitives and how they all fit together. Sarang and I have begun working on some Monero Standards that are similar to the original Cryptonote Standards (see here for more information). For each standard, from our hash function on upward, we will describe the standard, provide a justification for Monero's choices in those standards (complete with references), as well as a list of possible replacement standards. For example, our Monero RingCT Standard should describe the RingCT scheme described by shen, which is essentially a ring signature with linear combinations of signing keys + amount commitments. Under the "possible replacements" section, we would describe both the RTRS RingCT scheme and the doubly efficient zk-snark technology as two separate options.
These standards may take awhile to complete, and will be living documents as we change the protocol over the years. In the meantime, it will make it dramatically easier for future researchers to step into MRL and pick up where previous researchers have left off.
Hierarchical view keys. Exploiting the algebra we currently use for computing one-time keys, the sub-address scheme plays with view keys in a certain way, allowing a user to have one single view key for many wallets. Similarly, we may split a view key into several shares, where each subset of shares can be used to grant partial view access to the wallet. A receiver can request that a sender use a particular basepoint in their transaction key where different subsets of shares of the view key grant access to transactions with different basepoints in their transaction keys. None of these are protocol-level observations, they are wallet-level observations. Moreover, these require only that a receiver optionally specify a basepoint.
In other words: hierarchical view keys are a latent feature of our one-time address scheme that has not seen specific development yet. It's a rather low priority compared to the other projects under development; it grants users fine-grained control over their legal compliance, but Monero Standards will have great long-term impact on development and research at Monero.
Criticisms. Monero has suffered some recent criticisms about our hash function. I want to briefly address them.
First, I believe part of the criticism came from a confusion between Keccak3, SHA-3, and Keccak: we have never claimed to use SHA-3 as our hash function, we have only used the Keccak3 hash function, which is a legacy choice inherited from the original CryptoNote reference code. Many developers confuse the two, but Keccak3 was the hash function on which SHA-3 is based. In particular, the Keccak sponge construction can be used to fashion lots and lots of primitives, all of which could fairly be called "Keccak:" both Keccak3 and SHA-3 are Keccak constructions. This may be a subtle nomenclature issue, but it's important because a good portion of our criticisms say "Hey, they aren't using SHA-3!"
Second, I believe part of the criticism also comes from our choice of library, which in my opinion isn't a big deal as long as the library does what it says on the tin. In this case, our hash function is a valid implementation of Keccak3 according to the Keccak3 documentation. The most important criticism, from my point of view, is our choice of pre-SHA-3 Keccak3 as our hash function. Keccak3 underwent lots of analysis during the SHA contest, and Keccak3 is a well-vetted hash funtion. However, it has not been chosen as an international standard. There is a sentiment in the cryptocurrency community to distrust standards, which is probably a healthy sentiment. In this case, however, it means that our choice of hash function is not likely to be supported in common, well-vetted libraries in the future. Moreover, since SHA-3 is an international standard, it shall be undergoing heavy stress testing over the coming decades, a benefit Keccak3 shall not enjoy.
Last month, after some discussions, we made changes to our choice of PRNG in Monero to match the PRNG for Bitcoin. There has since been some discussions instantiated by anonimal about this choice of PRNG. We at MRL are doing our best to assist the core team in weighing the relative costs and benefits of switching to a library like crypto++, and so we believe these criticisms fall into the same category. We intend to address these issues and make formal recommendations in the aforementioned Monero Standards. Sorry for using the word aforementioned.
Things that didn't move much include a) educational outreach, b) SPECTRE, c) anti-ASIC roadmap, d) refund transactions. Most of which was on hold to complete multisig.
As far as educational outreach, I contacted a few members of a few math/cs depts at universities around me, but I haven't gotten anything hopeful yet. I wanted to go local (with respect to me) to make it easier to organize, but that's looking less likely. No matter how enthusiastic of a department we find, garnering participation from faculty members, beginning an application process for new students, squirelling up funding, working out logistics of getting teachers or lecturers/speakers from point A to point B, where to stash students, etc would be a challenge to finish before, say, July. And some schools start their fall semesters in mid-August. So I'm thinking that Summer 2019 is reasonable as the first Monero Summer School... and would be a real fun way to finish off a two-year post-doc!
December plan. I am going to finish multisig, and then finish the zk-lit review with Jeffrey Quesnelle, since these are both slam dunks. Any other time in December I have will be devoted to a) looking into the logistics of using the bulletproofs + RTRS RingCT set-up, b) reading the new zk-stark paper and assessing its importance for Monero, c) beginning work on Monero Standards, which includes addressing our hash function criticisms, our PRNG, etc.
Thank you again! This is an incredible opportunity, and this community is filled with some smart cookies. Every day is a challenge, and I couldn't ask for a more fun thing to be doing with my life right now. I'm hoping that my work ends up making Monero better for you.
submitted by snoether to Monero [link] [comments]

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

[14:05] <@wolfsokta> Hello Everybody, sorry we're a bit late getting started
[14:05] == block_338778 [[email protected]/web/freenode/ip.72.214.222.226] has joined #ravencoin-dev
[14:06] <@wolfsokta> Here are the topics we would like to cover today • 2.0.4 Need to upgrade - What we have done to communicate to the community • Unique Assets • iOS Wallet • General Q&A
[14:06] == Chatturga changed the topic of #ravencoin-dev to: 2.0.4 Need to upgrade - What we have done to communicate to the community • Unique Assets • iOS Wallet • General Q&A
[14:06] <@wolfsokta> Daben, could you mention what we have done to communicate the need for the 2.0.4 upgrade?
[14:07] == hwhwhsushwban [[email protected]/web/freenode/ip.172.58.37.35] has joined #ravencoin-dev
[14:07] <@wolfsokta> Others here are free to chime in where they saw the message first.
[14:07] == hwhwhsushwban [[email protected]/web/freenode/ip.172.58.37.35] has quit [Client Quit]
[14:08] Whats up bois
[14:08] hi everyone
[14:08] hi hi
[14:08] <@wolfsokta> Discussing the 2.0.4 update and the need to upgrade.
[14:08] <@Chatturga> Sure. As most of you are aware, the community has been expressing concerns with the difficulty oscillations, and were asking that something be done to the difficulty retargeting. Many people submitted suggestions, and the devs decided to implement DGW.
[14:09] <@Tron> I wrote up a short description of why we're moving to a new difficulty adjustment. https://medium.com/@tronblack/ravencoin-dark-gravity-wave-1da0a71657f7
[14:09] <@Chatturga> I have made posts on discord, telegram, bitcointalk, reddit, and ravencointalk.org from testnet stages through current.
[14:10] <@Chatturga> If there are any other channels that can reach a large number of community members, I would love to have more.
[14:10] <@wolfsokta> Thanks Tron, that hasn't been shared to the community at large yet, but folks feel free to share it.
[14:10] When was this decision made and by whom and how?
[14:10] <@Chatturga> I have also communicated with the pool operators and exchanges about the update. Of all of the current pools, only 2 have not yet updated versions.
[14:11] <@wolfsokta> The decision was made by the developers through ongoing requests for weeks made by the community.
[14:12] <@wolfsokta> Evidence was provided by the community of the damages that could be caused to projects when the wild swings continue.
[14:12] So was there a meeting or vote? How can people get invited
[14:12] <@Tron> It was also informed by my conversations with some miners that recommended that we make the change before the coin died. They witnessed similar oscillations from which other coins never recovered.
[14:13] only two pools left to upgrade is good, what about the exchanges? Any word on how many of those have/have not upgraded?
[14:13] <@wolfsokta> We talked about here in our last meeting Bruce_. All attendees were asked if they had any questions or concerns.
[14:13] == blondfrogs [[email protected]/web/freenode/ip.185.245.87.219] has joined #ravencoin-dev
[14:13] == roshii [[email protected]/web/freenode/ip.41.251.25.100] has joined #ravencoin-dev
[14:13] sup roshii long time no see
[14:14] <@Chatturga> Bittrex, Cryptopia, and IDCM have all either updated or have announced their intent to update.
[14:14] == wjcgiwgu283ik3cj [[email protected]/web/freenode/ip.172.58.37.35] has joined #ravencoin-dev
[14:15] sup russki
[14:15] what's the status here?
[14:15] I don’t think that was at all clear from the last dev meeting
[14:15] I can’t be the only person who didn’t understand it
[14:15] <@wolfsokta> Are there any suggestions on how to communicate the need to upgrade even further? I am concerned that others might also not understand.
[14:17] I’m not sold on the benefit and don’t understand the need for a hard fork — I think it’s a bad precedent to simply go rally exchanges to support a hard fork with little to no discussion
[14:17] so just to note, the exchanges not listed as being upgraded or have announced their intention to upgrade include: qbtc, upbit, and cryptobridge (all with over $40k usd volume past 24 hours according to coinmarketcap)
[14:18] <@wolfsokta> I don't agree that there was little or no discussion at all.
[14:19] <@wolfsokta> Looking back at our meeting notes from two weeks ago "fork" was specifically asked about by BrianMCT.
[14:19] If individual devs have the power to simple decide to do something as drastic as a hard fork and can get exchanges and miners to do it that’s got a lot of issues with centralization
[14:19] <@wolfsokta> It had been implemented on testnet by then and discussed in the community for several weeks before that.
[14:19] == under [[email protected]/web/freenode/ip.72.200.168.56] has joined #ravencoin-dev
[14:19] howdy
[14:19] Everything I’ve seen has been related to the asset layer
[14:19] I have to agree with Bruce_, though I wasn't able to join the last meeting here. That said I support the fork
[14:20] Which devs made this decision to do a fork and how was it communicated?
[14:20] well mostly the community made the decision
[14:20] Consensus on a change is the heart of bitcoin development and I believe the devs have done a great job building that consensus
[14:20] a lot of miners were in uproar about the situation
[14:20] <@wolfsokta> All of the devs were supporting the changes. It wasn't done in isolation at all.
[14:21] This topic has been a huge discussion point within the RVN mining community for quite some time
[14:21] the community and miners have been having issues with the way diff is adjusted for quite some time now
[14:21] Sure I’m well aware of that -
[14:21] Not sold on the benefits of having difficulty crippled by rented hashpower?
[14:21] The community saw a problem. The devs got together and talked about a solution and implemented a solution
[14:21] I’m active in the community
[14:22] So well aware of the discussions on DGW etc
[14:22] Hard fork as a solution to a problem community had with rented hashpower (nicehash!!) sounds like the perfect decentralized scenario!
[14:23] hard forks are very dangerous
[14:23] mining parties in difficulty drops are too
[14:23] <@wolfsokta> Agreed, we want to keep them to an absolute minimum.
[14:23] But miners motivation it’s the main vote
[14:24] What would it take to convince you that constantly going from 4 Th/s to 500 Gh/s every week is worse for the long term health of the coin than the risk of a hard fork to fix it?
[14:24] == Tron [[email protected]/web/freenode/ip.173.241.144.77] has quit [Ping timeout: 252 seconds]
[14:24] This hardfork does include the asset layer right? if so why is it being delayed in implementation?
[14:24] <@wolfsokta> Come back Tron!
[14:24] coudl it have been implement through bip9 voting?
[14:24] also hard fork is activated by the community! that's a vote thing!
[14:24] @mrsushi to give people time to upgrade their wallet
[14:25] @under, it would be much hard to keep consensus with a bip9 change
[14:25] <@wolfsokta> We investigated that closely Under.
[14:25] == Tron [[email protected]/web/freenode/ip.173.241.144.77] has joined #ravencoin-dev
[14:25] <@wolfsokta> See Tron's post for more details about that.
[14:25] <@spyder_> Hi Tron
[14:25] <@wolfsokta> https://medium.com/@tronblack/ravencoin-dark-gravity-wave-1da0a71657f7
[14:25] Sorry about that. Computer went to sleep.
[14:26] I'm wrong
[14:26] 2 cents. the release deadline of october 31st puts a bit of strain on getting code shipped. (duh). but fixing daa was important to the current health of the coin, and was widely suppported by current mining majority commuity. could it have been implemented in a different manner? yes . if we didnt have deadlines
[14:27] == wjcgiwgu283ik3cj [[email protected]/web/freenode/ip.172.58.37.35] has quit [Quit: Page closed]
[14:27] sushi this fork does not include assets. it's not being delayed though, we're making great progress for an Oct 31 target
[14:28] I don’t see the urgency but my vote doesn’t matter since my hash power is still CPUs
[14:28] <@wolfsokta> We're seeing the community get behind the change as well based on the amount of people jumping back in to mine through this last high difficulty phase.
[14:28] So that will be another hardfork?
[14:28] the fork does include the asset code though set to activate on oct 30th
[14:28] yes
[14:29] <@wolfsokta> Yes, it will based on the upgrade voting through the BIP9 process.
[14:29] I wanted to ask about burn rates from this group: and make a proposal.
[14:29] we're also trying hard to make it the last for awhile
[14:29] Can you clear up the above — there will be this one and another hard fork?
[14:29] <@wolfsokta> Okay, we could discuss that under towards the end of the meeting.
[14:30] If this one has the asset layer is there something different set for October
[14:30] <@wolfsokta> Yes, there will be another hard fork on October 31st once the voting process is successful.
[14:31] <@wolfsokta> The code is in 2.0.4 now and assets are active on testnet
[14:31] Bruce, the assets layer is still being worked on. Assets is active on mainnet. So in Oct 31 voting will start. and if it passes, the chain will fork.
[14:31] this one does NOT include assets for mainnet Bruce -- assets are targeted for Oct 31
[14:31] not***
[14:31] not active****
[14:31] correct me if I'm wrong here, but if everyone upgrades to 2.0.4 for this fork this week, the vote will automatically pass on oct 31st correct? nothing else needs to be done
[14:31] Will if need another download or does this software download cover both forks?
[14:31] <@wolfsokta> Correct Urgo
[14:32] thats how the testnet got activated and this one shows "asset activation status: waiting until 10/30/2018 20:00 (ET)"
[14:32] Will require another upgrade before Oct 31
[14:32] thank you for the clarification wolfsokta
[14:32] <@wolfsokta> It covers both forks, but we might have additional bug fixes in later releases.
[14:32] So users DL one version now and another one around October 30 which activates after that basically?
[14:33] I understand that, but I just wanted to make it clear that if people upgrade to this version for this fork and then don't do anything, they are also voting for the fork on oct 31st
[14:33] Oh okay — one DL?
[14:33] Bruce, Yes.
[14:33] Ty
[14:33] well there is the issue that there maybe some further consensus bugs dealing with the pruneability of asset transactions that needs to be corrected between 2.0.4 and mainnet. so i would imagine that there will be further revisions required to upgrade before now and october 31
[14:33] @under that is correct.
[14:34] I would highly recommend bumping the semver up to 3.0.0 for the final pre 31st release so that the public know to definitely upgrade
[14:34] @under +1
[14:35] out of curiosity, have there been many bugs found with the assets from the version released in july for testnet (2.0.3) until this version? or is it solely a change to DGW?
[14:35] <@wolfsokta> That's not a bad idea under.
[14:35] <@spyder_> @under good idea
[14:35] @urgo. Bugs are being found and fixed daily.
[14:35] Any time the protocol needs to change, there would need to be a hard fork (aka upgrade). It is our hope that we can activate feature forks through the BIP process (as we are doing for assets). Mining pools and exchanges will need to be on the newest software at the point of asset activation - should the mining hash power vote for assets.
[14:35] blondfrogs: gotcha
[14:35] There have been bugs found (and fixed). Testing continues. We appreciate all the bug reports you can give us.
[14:36] <@wolfsokta> Yes! Thank you all for your help in the community.
[14:37] (pull requests with fixes and test coverage would be even better!)
[14:37] asset creation collision is another major issue. current unfair advantage or nodes that fore connect to mining pools will have network topologies that guarantee acceptance. I had discussed the possibility of fee based asset creation selection and i feel that would be a more equal playing ground for all users
[14:38] *of nodes that force
[14:38] <@wolfsokta> What cfox said, we will always welcome development help.
[14:38] So just to make sure everyone know. When assets is ready to go live on oct 31st. Everyone that wants to be on the assets chain without any problems will have to download the new binary.
[14:39] <@wolfsokta> The latest binary.
[14:39] under: already in the works
[14:39] excellent to hear
[14:39] == UserJonPizza [[email protected]/web/freenode/ip.24.218.60.237] has joined #ravencoin-dev
[14:39] <@wolfsokta> Okay, we've spent a bunch of time on that topic and I think it was needed. Does anybody have any other suggestions on how to get the word out even more?
[14:40] maybe preface all 2.0.X releases as pre-releases... minimize the number of releases between now and 3.0 etc
[14:41] <@wolfsokta> Bruce_ let's discuss further offline.
[14:41] wolfsokta: which are the remaining two pools that need to be upgraded? I've identified qbtc, upbit, and cryptobridge as high volume exchanges that haven't said they were going to do it yet
[14:41] so people can help reach out to them
[14:41] f2pool is notoriously hard to contact
[14:41] are they on board?
[14:42] <@wolfsokta> We could use help reaching out to QBTC and Graviex
[14:42] I can try to contact CB if you want?
[14:42] <@Chatturga> The remaining pools are Ravenminer and PickAxePro.
[14:42] <@Chatturga> I have spoken with their operators, the update just hasnt been applied yet.
[14:42] ravenminer is one of the largest ones too. If they don't upgrade that will be a problem
[14:42] okay good news
[14:42] (PickAxePro sounds like a Ruby book)
[14:43] I strongly feel like getting the word out on ravencoin.org would be beneficial
[14:44] that site is sorely in need of active contribution
[14:44] Anyone can volunteer to contribute
[14:44] <@wolfsokta> Okay, cfox can you talk about the status of unique assets?
[14:44] sure
[14:45] <@wolfsokta> I'll add website to the end of our topics.
[14:45] code is in review and will be on the development branch shortly
[14:45] would it make sense to have a page on the wiki (or somewhere else) that lists the wallet versions run by pools & exchanges?
[14:45] will be in next release
[14:45] furthermore, many sites have friendly link to the standard installers for each platform, if the site linked to the primary installers for each platform to reduce github newb confusion that would be good as well
[14:46] likely to a testnetv5 although that isn't settled
[14:46] <@wolfsokta> Thanks cfox.
[14:46] <@wolfsokta> Are there any questions about unique assets, and how they work?
[14:47] after the # are there any charachters you cant use?
[14:47] will unique assets be constrained by the asset alphanumeric set?
[14:47] ^
[14:47] <@Chatturga> @Urgo there is a page that tracks and shows if they have updated, but it currently doesnt show the actual version that they are on.
[14:47] a-z A-Z 0-9
[14:47] <@Chatturga> https://raven.wiki/wiki/Exchange_notifications#Pools
[14:47] There are a few. Mostly ones that mess with command-line
[14:47] you'll be able to use rpc to do "issueunique MATRIX ['Neo','Tank','Tank Brother']" and it will create three assets for you (MATRIX#Neo, etc.)
[14:47] @cfox - No space
[14:48] @under the unique tags have an expanded set of characters allowed
[14:48] Chatturga: thank you
[14:48] @UJP yes there are some you can't use -- I'll try to post gimmie a sec..
[14:49] Ok. Thank you much!
[14:49] 36^36 assets possible and 62^62 uniques available per asset?
[14:49] <@spyder_> std::regex UNIQUE_TAG_CHARACTERS("^[[email protected]$%&*()[\\]{}<>_.;?\\\\:]+$");
[14:50] regex UNIQUE_TAG_CHARACTERS("^[[email protected]$%&*()[\\]{}<>_.;?\\\\:]+$")
[14:50] oh thanks Mark
[14:51] <@wolfsokta> Okay, next up. I want to thank everybody for helping test the iOS wallet release.
[14:51] <@wolfsokta> We are working with Apple to get the final approval to post it to the App Store
[14:51] @under max asset length is 30, including unique tag
[14:51] Does the RVN wallet have any other cryptos or just RVN?
[14:52] == BruceFenton [[email protected]/web/freenode/ip.67.189.233.170] has joined #ravencoin-dev
[14:52] will the android and ios source be migrated to the ravenproject github?
[14:52] I've been adding beta test users. I've added about 80 new users in the last few days.
[14:52] <@wolfsokta> Just RVN, and we want to focus on adding the asset support to the wallet.
[14:53] == Bruce_ [[email protected]/web/freenode/ip.67.189.233.170] has quit [Ping timeout: 252 seconds]
[14:53] <@wolfsokta> Yes, the code will also be freely available on GitHub for both iOS and Android. Thank you Roshii!
[14:53] Would you consider the iOS wallet to be a more secure place for one's holdings than say, a Mac connected to the internet?
[14:53] will there be a chance of a more user freindly wallet with better graphics like the iOS on PC?
[14:53] the android wallet is getting updated for DGW, correct?
[14:53] <@wolfsokta> That has come up in our discussion Pizza.
[14:54] QT framework is pretty well baked in and is cross platform. if we get some qt gurus possibly
[14:54] Phones are pretty good because the wallet we forked uses the TPM from modern phones.
[14:54] Most important is to write down and safely store your 12 word seed.
[14:54] TPM?
[14:54] <@wolfsokta> A user friendly wallet is one of our main goals.
[14:55] TPM == Trusted Platform Module
[14:55] Ahhh thanks
[14:55] just please no electron apps. they are full of security holes
[14:55] <@spyder_> It is whats makes your stuffs secure
[14:55] not fit for crypto
[14:55] under: depends on who makes it
[14:55] The interface screenshots I've seen look like Bread/Loaf wallet ... I assume that's what was forked from
[14:55] ;)
[14:56] <@wolfsokta> @roshii did you see the question about the Android wallet and DGW?
[14:56] Yes, it was a fork of breadwallet. We like their security.
[14:56] chromium 58 is the last bundled electron engine and has every vuln documented online by google. so unless you patch every vuln.... methinks not
[14:56] Agreed, great choice
[14:57] <@wolfsokta> @Under, what was your proposal?
[14:58] All asset creation Transactions have a mandatory OP_CHECKLOCKTIMEVERIFY of 1 year(or some agreed upon time interval), and the 500 RVN goes to a multisig devfund, run by a custodial group. We get: 1) an artificial temporary burn, 2) sustainable community and core development funding for the long term, after OSTK/Medici 3) and the reintroduction of RVN supply at a fixed schedule, enabling the removal of the 42k max cap of total As
[14:58] *im wrong on the 42k figure
[14:58] <@wolfsokta> Interesting...
[14:59] <@wolfsokta> Love to hear others thoughts.
[14:59] Update: I posted a message on the CryptoBridge discord and one of their support members @stepollo#6276 said he believes the coin team is already aware of the fork but he would forward the message about the fork over to them right now anyway
[14:59] Ifs 42 million assets
[14:59] yep.
[15:00] I have a different Idea. If the 500 RVN goes to a dev fund its more centralized. The 500 RVN should go back into the unmined coins so miners can stay for longer.
[15:01] *without a hardfork
[15:01] <@wolfsokta> lol
[15:01] that breaks halving schedule, since utxos cant return to an unmined state.
[15:01] @UJP back into coinbase is interesting. would have to think about how that effects distribution schedule, etc.
[15:01] only way to do that would be to dynamicaly grow max supply
[15:02] and i am concerned already about the max safe integer on various platforms at 21 billion
[15:02] js chokes on ravencoin already
[15:02] <@wolfsokta> Other thoughts on Under's proposal? JS isn't a real language. ;)
[15:02] Well Bitcoin has more than 21 bn Sats
[15:02] Is there somebody who wants to volunteer to fix js.
[15:02] hahaha
[15:03] I honestly would hate for the coins to go to a dev fund. It doesn't seem like Ravencoin to me.
[15:03] Yep, but we're 21 billion x 100,000,000 -- Fits fine in a 64-bit integer, but problematic for some languages.
[15:03] <@wolfsokta> Thanks UJP
[15:04] <@wolfsokta> We're past time but I would like to continue if you folks are up for it.
[15:04] Yeah no coins can go anywhere centrality contorted like a dev fund cause that would mean someone has to run it and the code can’t decide that so it’s destined to break
[15:05] currently and long term with out the financial backing of development then improvements and features will be difficult. we are certainly thankful for our current development model. but if a skunkworks project hits a particular baseline of profitability any reasonable company would terminate it
[15:05] Yes let’s contibue for sure
[15:05] the alternative to a dev fund in my mind would be timelocking those funds back to the issuers change address
[15:06] But we can’t have dev built in to the code — it has to be open source like Bitcoin and monero and Litecoin - it’s got drawbacks but way more advantages- it’s the best model
[15:06] Dev funding
[15:06] i highly reccommend not reducing the utility of raven by removing permanently the supply
[15:07] == BW_ [[email protected]/web/freenode/ip.138.68.243.202] has joined #ravencoin-dev
[15:07] timelocking those funds accompllishes the same sacrifice
[15:07] @under timelocking is interesting too
[15:07] How exactly does timelocking work?
[15:07] <@wolfsokta> ^
[15:07] I mean you could change the price of assets with the Block reward halfing.
[15:07] == Roshiix [[email protected]/web/freenode/ip.105.67.2.212] has joined #ravencoin-dev
[15:08] funds cant be spent from an address until a certain time passes
[15:08] but in a what magical fairy land do people continue to work for free forever. funding development is a real issue... as much as some might philosphically disagree. its a reality
[15:08] You’d still need a centralized party to decide how to distribute the funds
[15:08] even unofficially blockstream supports bitcoin devs
[15:08] on chain is more transparent imho
[15:09] == Tron_ [[email protected]/web/freenode/ip.173.241.144.77] has joined #ravencoin-dev
[15:09] @UJP yes there are unlimited strategies. one factor that I think is v important is giving application developers a way to easily budget for projects which leads to flat fees
[15:09] If the project is a success like many of believe it will be, I believe plenty of people will gladly done to a dev fund. I don't think the 500 should be burned.
[15:09] *donate
[15:09] centralized conservatorship, directed by community voting process
[15:10] == Tron [[email protected]/web/freenode/ip.173.241.144.77] has quit [Ping timeout: 252 seconds]
[15:10] <@wolfsokta> Thanks Under, that's an interesting idea that we should continue to discuss in the community. You also mentioned the existing website.
[15:10] It would need to be something where everyone with a QT has a vote
[15:10] think his computer went to sleep again :-/
[15:10] I agree UJP
[15:10] with the website
[15:10] No that’s ico jargon — any development fund tied to code would have to be centralized and would therefor fail
[15:11] ^
[15:11] ^
[15:11] ^
[15:11] dashes model for funding seems to be pretty decentralized
[15:11] community voting etc
[15:11] Once you have a dev fund tied to code then who gets to run it? Who mediates disputes?
[15:11] oh well another discussion
[15:11] Dash has a CEO
[15:12] <@wolfsokta> Yeah, let's keep discussing in the community spaces.
[15:12] Dash does have a good model. It's in my top ten.
[15:12] having the burn go to a dev fund is absolute garbage
[15:12] These dev chats should be more target than broad general discussions — changing the entire nature of the coin and it’s economics is best discussed in the RIPs or other means
[15:13] <@wolfsokta> Yup, let's move on.
[15:13] just becuase existing implementation are garbage doesnt mean that all possible future governance options are garbage
[15:13] <@wolfsokta> To discussing the website scenario mentioned by under.
[15:13] the website needs work. would be best if it could be migrated to github as well.
[15:13] What about this: Anyone can issue a vote once the voting feature has been added, for a cost. The vote would be what the coins could be used for.
[15:14] features for the site that need work are more user friendly links to binaries
[15:14] <@wolfsokta> We investigated how bitcoin has their website in Github to make it easy for contributors to jump in.
[15:14] that means active maintenance of the site instead of its current static nature
[15:15] <@wolfsokta> I really like how it's static html, which makes it super simple to host/make changes.
[15:15] the static nature isn’t due to interface it’s due to no contributors
[15:15] no contribution mechanism has been offered
[15:15] github hosted would allow that
[15:16] We used to run the Bitcoin website from the foundation & the GitHub integration seemed to cause some issues
[15:16] its doesnt necessarily have to be hosted by github but the page source should be on github and contributions could easily be managed and tracked
[15:17] for example when a new release is dropped, the ability for the downlaods section to have platform specific easy links to the general installers is far better for general adoption than pointing users to github releases
[15:18] <@wolfsokta> How do people currently contribute to the existing website?
[15:18] they dont?
[15:18] We did that and it was a complete pain to host and keep working — if someone wants to volunteer to do that work hey can surely make the website better and continually updated — but they could do that in Wordpress also
[15:19] I’d say keep an eye out for volunteers and maybe we can get a group together who can improve the site
[15:19] == digitalvap0r-xmr [[email protected]/web/cgi-irc/kiwiirc.com/ip.67.255.25.134] has joined #ravencoin-dev
[15:19] And they can decide best method
[15:20] I host the source for the explorer on github and anyone can spin it up instantly on a basic aws node. changes can be made to interface etc, and allow for multilingual translations which have been offered by some community members
[15:20] there are models that work. just saying it should be looked at
[15:20] i gotta run thank you all for your contributions
[15:20] <@wolfsokta> I feel we should explore the source for the website being hosted in GitHub and discuss in our next dev meeting.
[15:21] <@Chatturga> Thanks Under!
[15:21] == under [[email protected]/web/freenode/ip.72.200.168.56] has quit [Quit: Page closed]
[15:21] <@wolfsokta> Thanks, we also need to drop soon.
[15:21] There is no official site so why care. Someone will do better than the next if RVN is worth it anyway. That's already the case.
[15:21] <@wolfsokta> Let's do 10 mins of open Q&A
[15:22] <@wolfsokta> Go...
[15:23] <@Chatturga> Beuller?
[15:24] No questions ... just a comment that the devs and community are great and I'm happy to be a part of it
[15:24] I think everyone moved to discord. I'll throw this out there. How confident is the dev team that things will be ready for oct 31st?
[15:24] <@wolfsokta> Alright! Thanks everybody for joining us today. Let's plan to get back together as a dev group in a couple of weeks.
[15:25] thanks block!
[15:25] <@wolfsokta> Urgo, very confident
[15:25] Please exclude trolls from discord who havent read the whitepaper
[15:25] great :)
[15:25] "things" will be ready..
[15:25] Next time on discord right?
[15:25] woah why discord?
[15:25] some of the suggestions here are horrid
[15:25] this is better less point
[15:25] == blondfrogs [[email protected]/web/freenode/ip.185.245.87.219] has quit [Quit: Page closed]
[15:25] Assets are working well on testnet. Plan is to get as much as we can safely test by Sept 30 -- this includes dev contributions. Oct will be heavy testing and making sure it is safe.
[15:26] people
[15:26] <@wolfsokta> Planning on same time, same IRC channel.
[15:26] == BW_ [[email protected]/web/freenode/ip.138.68.243.202] has quit [Quit: Page closed]
[15:26] @xmr any in particular?
[15:27] (or is "here" discord?)
[15:27] Cheers - Tron
[15:27] "Cheers - Tron" - Tron
submitted by Chatturga to Ravencoin [link] [comments]

[Very long, very serious] Development summary week ending 18th April 2014

When I got my first full time job, I used to try implementing requests from everyone as they came in, and for a while people really loved that I listened to their requests. Over time, however, things started to go wrong. I’d apply a change someone asked for, and in doing so would break something elsewhere in the code, in some subtle way that was missed in short-term testing. I’d fix that second bug and reveal a third. I’d fix that just in time for a new request to come in, and the process repeat. This led to the term “Bug whack-a-mole”, wherein I was spending time mostly fixing bugs introduced to live systems through rushing through earlier bug fixes.
So this week, we’ve had a lot of people asking about changes to proof-of-work, especially X11, or even moving to proof of stake, primarily in an attempt to address risk of a 51% attack. A 51% attack is where one actor (person, group, organisation, whatever) gains control of enough resources to be able to create their own blockchain, isolated from the main blockchain, at a rate at least as quickly as the main blockchain is being created. They can then spend Dogecoins on the main blockchain, before releasing their fake blockchain; if their fake blockchain is longer than the existing blockchain, nodes will switch to the new blockchain (as they would when repairing a fork), and essentially the spent Dogecoin on the main blockchain are reversed and can be spent again. This is mostly of consequence to exchanges and payment processors (such as Moolah), who are most likely to end up holding the loss from the double-spend.
The concern about a 51% attack stems from a couple of weeks ago now, when Wafflepool was around 50% of the network hashrate (mining power). It’s still high (at the time of wring about 32GH/s out of almost 74GH/s, or about 43%), but it is diminishing as a proportion.
Lets talk about proof of stake first, as this one’s simpler. Proof of stake has been suggested as a way of avoiding the risk of Wafflepool having control of too many mining resources by itself, by changing from securing the blockchain through computational resources (work), to using number of Dogecoin held. The theory is that those with most Dogecoins have most to lose, and will act in their own interests. Major examples of proof of stake coins include Peercoin, Mintcoin and more recently Blackcoin.
However, this essentially means we take control from Wafflepool, and hand it to Cryptsy (who are considered most likely to be the holder of some of the huge Dogecoin wallets out there). I by no means expect either organisation to attempt a 51% attack, but hopefully it’s clear that simply switching risks isn’t actually improving things. I’ve also had significant concerns raised from the merchant/payment processor community about potential impact of proof of stake, and that it may encourage hoarding (as coins are awarded for holding coins, rather than for mining). The price instability of Mintcoin and Blackcoin (and that Peercoin appears to only avoid this through very high transaction fees to keep the entire network inert) does not encourage confidence, either. For now, proof of stake remains something we’re keeping in mind, primarily in case price does not react as anticipated to mining reward decreases over time, but certainly we’re not eager to rush into such a change.
Before I get into a discussion on proof of work, let me summarise this quickly; right now, uncertainty about changes is holding back our community from adopting ASICs. It’s high risk to spend hundreds, thousands or in some cases significantly more on ASIC hardware which could be left useless if we move. Those who have already purchased ASICs to support the Dogecoin hashrate would most likely have to mine Litecoin to recover sunk costs, if we did move. ASICs are virtually inevitable, and in our assessment we are better off pushing for rapid adoption, rather than expending resources delaying a problem which will re-occur later.
At the time of writing the development team has no plans to change proof of work algorithm outside of the eventuality of a major security break to Scrypt. We are focusing on mitigation approaches in case of a 51% attack, and adoption of the coin as the most sustainable approaches to dealing with this risk.
The X11 algorithm has been proposed as an alternative proof of work algorithm. X11, for those unaware, was introduced with Darkcoin. It’s a combination of 11 different SHA-3 candidate algorithms, using multiple rounds of hashing. The main advantage championed for Darkcoin is that current implementations run cooler on GPU hardware. Beyond that, there’s a lot of confusion over what it does and does not do. As I’m neither an algorithms or electronics specialist, I recruited a colleague who previously worked on the CERN computing grid to assist, and the following is primarily his analysis. A full technical report is coming for anyone who really likes detail, this is just a summary:
A lot of people presume X11 is ASIC resistant; it’s not. Candidate algorithms for SHA-3 were assessed on a number of criteria, including simplicity to implement in hardware. All 11 algorithms have been implemented in FPGA hardware, and several in ASIC hardware already. The use of multiple algorithms does significantly complicate ASIC development, as it means the resulting chip would likely be extremely large. This has consequences for production, as the area of a chip is the main determining factor for likelihood of an error in the chip.
The short version being that while yes it would take significant resources to make an efficient ASIC for X11, for a long time Scrypt was considered infeasible to adapt to ASICs. As stated earlier, any move would most likely be nothing more than an extremely expensive and risky delaying manoeuvre. ASIC efficiency would also depend heavily on ability to optimise the combination of the algorithms; a naive implementation would run at around the rate of the slowest hashing algorithm, however if any common elements could be found amongst the algorithms, it may be that this could be improved upon significantly
There are also significant areas of concern with regards to X11. The “thermal efficiency” is most likely a result of the algorithm being a poor fit for GPU hardware. This means that GPU mining is closer to CPU mining (the X11 Wiki article suggests a ratio of 3:1 for GPU/CPU mining performance), however it also means that if a way of was found to improve performance there could be significantly faster software miners, leading to an ASIC-like edge without any of the hardware development costs. The component algorithms are all relatively new, and several were rejected during the SHA-3 competition for security concerns (see http://csrc.nist.gov/groups/ST/hash/sha-3/Round2/documents/Round2_Report_NISTIR_7764.pdf for full details). Security criteria for SHA-3 algorithms was also focused on ability to generate collisions, rather than on producing hashes with specific criteria (such as number of leading 0s, which is how proof of work is usually assessed).
X11 is a fascinating algorithm for new coins, however I would consider it exceptionally high risk for any existing coin to adopt.
Beyond algorithm analysis, this week has been mostly about testing 1.7. Last weekend Patrick raised the issue that we had been incorrectly running the automated tests, which had led to several automated test failures being missed earlier. This led to other tasks being dropped as we quickly reworked the tests to match Dogecoin parameters instead of Bitcoin. So far, all tests have passed successfully once updated to match Dogecoin, however this work continues. On the bright side, it turns out we have a lot more automated tests than we realised, which is very useful for later development.
The source code repository for Dogecoin now also uses Travis CI, which sanity-checks patches submitted to the project, to help us catch any potential problems earlier, thanks to Tazz for leading the charge on that. This is particularly important as of course we’re developing on different platforms (Windows, OS X, Linux) and what works on one, may not work on others. Over time, this should be a significant time saver for the developers. For anyone wanting to help push Dogecoin forward, right now the most productive thing to be doing is testing either Dogecoin, or helping Bitcoin Core test pull requests. Feel free to drop by our Freenode channel for guidance on getting started with either.
Right now, I’m working on the full technical report on X11, and will then be back working on the payment protocol for Dogecoin. I’ve approached a few virus scanning software companies about offering their products for Dogecoin, with so far no response, but will update you all if I hear more.
Lastly, the next halvening (mining reward halving) is currently expected late on the 27th or early on the 28th, both times GMT. Given that it was initially expected on the 25th, we’re obviously seeing some slippage in estimates, and a total off the top of my head guess would be that we’ll see it around 0500 GMT on the 28th at this rate. I have taken the 28th off from the day job, and will be around both before and after in case of any problems (love you guys, not getting up at 5am to check on the blockchain, though!)
submitted by rnicoll to dogecoin [link] [comments]

Monero at the 35C3 – 35th Chaos Communication Congress, 27.-30.December 2018, Leipzig, Germany

As in 2017 there will also a Monero Assembly during 35C3 in Leipzig, Germany (here is a bit of historic background).
tldr; go to the taiga workgroup wiki on taiga.getmonero.org to see the current status
The Chaos Computer Club (CCC) is the largest (and oldest) hacker association in europe (see Wikipedia). Originating from Germany, it has spread over Europe and organizes numerous events. Most important the annual Chaos Communication Congress between christmas and new years eve. It is considered one of the largest (over 13,000 attendees) events of this kind, alongside the DEF CON in Las Vegas. Besides the top-class Main Talks, which all get recorded there are other formats such as assemblies and so called “self organized sessions”.
In 2016 the RIAT Crypto Assembly (see 33C3 Wiki and cache) featured crypto-based workshops with Monero, and Tomu 2FA devices and was the initial (mini) implementation of Monero at C3. IN 2016 the Bitcoin Assembly was the only other “Cryptocurrency” Assembly. In 2017 we had a combined RIAT/Monero/Bitcoin “Village”. The Monero December meetup in Vienna served as a real-life meeting in order to prepare the Monero Assembly. Communication and organisation was via hackpad and reddit.
This year we are using the taiga wiki on taiga.getmonero.org to and the IRC channel #monero-ccc to coordinate. The next IRC meeting of the workgroup will be on 2018-11-07 17:00 UTC on "monero-community".
What happened so far:

submitted by parasew to Monero [link] [comments]

PSA: Clearing up some misconceptions about full nodes

It's time to clear up some misconceptions floating around about full nodes.
Myth: There are only about 5500 full nodes worldwide
This number comes from this site and it measured by trying to probe every nodes on their open ports.
Problem is, not all nodes actually have open ports that can be probed. Either because they are behind firewalls or because their users have configured them to not listen for connections.
Nobody knows how many full nodes there are, since many people don't know how to forward ports behind a firewall, and bandwidth can be costly, its quite likely that the number of nodes with closed ports is at least another several thousand.
Nodes with open ports are able to upload blocks to new full nodes. In all other ways they are the same as nodes with closed ports. But because open-port-nodes can be measured and closed-port-nodes cannot, some members of the bitcoin community have been mistaken into believing that open-port-nodes are that matters.
Myth: This number of nodes matters and/or is too low.
Nodes with open ports are useful to the bitcoin network because they help bootstrap new nodes by uploading historical blocks, they are a measure of bandwidth capacity. Right now there is no shortage of bandwidth capacity, and if there was it could be easily added by renting cloud servers.
The problem is not bandwidth or connections, but trust, security and privacy. Let me explain.
Full nodes are able to check that all of bitcoin's rules are being followed. Rules like following the inflation schedule, no double spending, no spending of coins that don't belong to the holder of the private key and all the other rules required to make bitcoin work (e.g. difficulty)
Full nodes are what make bitcoin trustless. No longer do you have to trust a financial institution like a bank or paypal, you can simply run software on your own computer. To put simply, the only node that matters is the one you use
Myth: There is no incentive to run nodes, the network relies on altruism
It is very much in the individual bitcoin's users rational self interest to run a full node and use it as their wallet.
Using a full node as your wallet is the only way to know for sure that none of bitcoin's rules have been broken. Rules like no coins were spent not belonging to the owner, that no coins were spent twice, that no inflation happens outside of the schedule and that all the rules needed to make the system work are followed (e.g. difficulty.) All other kinds of wallet involve trusting a third party server.
All these checks done by full nodes also increase the security. There are many attacks possible against lightweight wallets that do not affect full node wallets.
This is not just mindless paranoia, there have been real world examples where full node users were unaffected by turmoil in the rest of the bitcoin ecosystem. The 4th July 2015 accidental chain fork effected many kinds of wallets. Here is the wiki page on this event https://en.bitcoin.it/wiki/July_2015_chain_forks#Wallet_Advice
Notice how updated node software was completely unaffected by the fork. All other wallets required either extra confirmations or checking that the third-party institution was running the correct version.
Full nodes wallets are also currently the most private way to use Bitcoin, with nobody else learning which bitcoin addresses belong to you. All other lightweight wallets leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, lightweight wallets based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet or wiretappers.
For many use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.
Myth: I can just set up a node on a cloud server instance and leave it
To get the benefits of running a full node, you must use it as your wallet, preferably on hardware you control.
Most people who do this do not use a full node as their wallet. Unfortunately because Bitcoin has a similar name to Bittorrent, some people believe that upload capacity is the most important thing for a healthy network. As I've explained above: bandwidth and connections are not a problem today, trust, security and privacy are.
Myth: Running a full node is not recommended, most people should use a lightweight client
This was common advice in 2012, but since then the full node software has vastly improved in terms of user experience.
If you cannot spare the disk space to store the blockchain, you can enable pruning. In Bitcoin Core 0.12, pruning being enabled will leave the wallet enabled. Altogether this should require less than 900MB of hard disk space.
If you cannot spare the bandwidth to upload blocks to other nodes, there are number of options to reduce or eliminate the bandwidth requirement. These include limiting connections, bandwidth targetting and disabling listening. Bitcoin Core 0.12 has the new option -blocksonly, where the node will not download unconfirmed transaction and only download new blocks. This more than halves the bandwidth usage at the expense of not seeing unconfirmed transactions.
Synchronizing the blockchain for a new node has improved since 2012 too. Features like headers-first and libsecp256k1 have greatly improved the initial synchronization time.
It can be further improved by setting -dbcache=3000 which keeps more of the UTXO set in memory. It reduces the amount of time reading from disk and therefore speeds up synchronization. Tests showed that the entire blockchain can now be synchronized in less than 3 and a half hours (Note that you'll need Bitcoin Core 0.12 or later to get all these efficiency improvements) Another example with 2h 25m
How to run a full node as your wallet.
I think every moderate user of bitcoin would benefit by running a full node and using it as their wallet. There are several ways to do this.
So what are you waiting for? The benefits are many, the downsides are not that bad. The more people do this, the more robust and healthy the bitcoin ecosystem is.
Further reading: http://www.truthcoin.info/blog/measuring-decentralization/
submitted by belcher_ to Bitcoin [link] [comments]

IRC Log from Ravencoin Open Developer Meeting - Sept 21, 2018

[14:04] Topics for the chat today: 1. Bitcoin double spend bug. 2. Max reorg depth changes.
[14:04] I think that will take most of the hour. We'll then open it up for questions.
[14:05] == blondfrogs changed the topic of #ravencoin-dev to: Topics for the chat today: 1. Bitcoin double spend bug. 2. Max reorg depth changes.
[14:05] == wolfsokta changed the topic of #ravencoin-dev to: Bitcoin Bug/Max Reorg
[14:05] Hi! I'm Forest... Forest Gump, do you want a ravencoin?
[14:05] Hi all
[14:05] == blondfrogs changed the topic of #ravencoin-dev to: Topics for the chat today: 1. Bitcoin double spend bug. 2. Max reorg depth changes.
[14:05] Topic fight
[14:05] as far as i know the double spending bug could inflate the bitcoin supply right?
[14:05] like make more bitcoin that possible
[14:05] than
[14:06] is this correct?
[14:06] it's more that the danger is crashing all the nodes
[14:07] 1. Raven is also affected by the bitcoin bug. Which is what we want to discus.
[14:08] blondfrogs can you tell us what you're planning to address the bug?
[14:08] So, we have updated our codebase to have the bitcoin bug fix. This is going to be implemented in 2.0.4.1. We are currently making binaries and should have an annoucment by end of day today to the community. We are urging the community to update their wallets to 2.0.4.1
[14:09] ...
[14:10] BTC patched it though. Wouldnt the "same" patch work for RVN?
[14:10] Spot on!
[14:10] No, it would not since we forked a while back.
[14:10] Exactly. We patched it in the same way but we still need to get our wallets that contain the fix out so the community can upgrade
[14:10] is there a todo somewhere to add auto-update functionality to the wallet?
[14:11] So, we need to get the word out to get people to update.
[14:11] YES
[14:12] How does the patch affect future LN implementation?
[14:12] Any changes that were made to bitcoin to get LN to integrate would need to be merged into Raven.
[14:12] Any risks?
[14:13] Fair comment.
[14:13] We would love any developers that are interested in doing that work to jump in.
[14:13] The fix is just changing a 'false' to 'true' to tell the node to scan for dup tx in the block.
[14:14] So the auto update feature implementation is being discussed through OS stores, as a second option for wallet download ... @lsji07
[14:14] The comment in the Bitcoin code said it was slow to scan the transactions. So it will be a bit slower.
[14:14] slower is better than being vulnerable
[14:16] Agreed
[14:16] lets talk about the maxreorg depth, people in the discord have been asking "why isnt it lower" what do you guys think
[14:16] once we finish with the first one we will russk
[14:16] k
[14:16] no russk
[14:16] lol
[14:17] I saw it went back to 60.
[14:17] 2.0.4.1 will be built and uploaded today.
[14:18] Once the binaries are ready, Ill get it out to all of the social sites, exchanges, and pool operators
[14:18] We changed the voting date for 2.0.4.1
[14:19] So it will not interfere with 2.1 release.
[14:19] We would prefer that 2.0.4 and 2.0.4.1 assets do not activate as they're not 100% compatible with 2.1 assets.
[14:19] == Zaaaab [[email protected]/web/cgi-irc/kiwiirc.com/ip.174.211.21.7] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
[14:20] We also need the communities help to get people to upgrade to 2.0.4.1
[14:20] The protocol layer for assets changed just a bit.
[14:20] Unique assets can be 31 chars instead of 30
[14:20] We saved a byte on asset creation by not encoding the IPFS length twide.
[14:20] We saved a byte on asset creation by not encoding the IPFS length twice.
[14:21] ipfs will be implemented natively later right?
[14:21] YEs
[14:21] I hope so.
[14:21] awesome
[14:21] So vulnerabilty patch first, then the asset layer. Same 31/10 date though for starting asset activation on 2.1
[14:21] It makes sense for us to integrate with IPFS when messaging is available.
[14:22] Yes lsji07
[14:22] Until then, the IPFS hashes will be embedded and we'll "pin" the files so they stay around.
[14:22] == HansSchmidt [[email protected]/web/cgi-irc/kiwiirc.com/ip.173.239.232.46] has joined #ravencoin-dev
[14:22] == Hans_Schmidt [[email protected]/web/cgi-irc/kiwiirc.com/ip.173.239.232.56] has left #ravencoin-dev []
[14:22] == corby_ [[email protected]/web/freenode/ip.207.135.150.17] has joined #ravencoin-dev
[14:23] do you guys have anyone working on RSK yet?
[14:23] hi
[14:23] sup
[14:23] Any other questions about 2.0.4.1?
[14:23] @russk Thats a great question for the open QA at the end :)
[14:23] K, let's cover the Max Re-Org depth changes.
[14:24] No, but it can be implemented with RVN the same way as Bitcoin - as a side chain.
[14:24] Tron posted an article that discusses the options that were discussed.
[14:24] https://medium.com/@tronblack/ravencoin-building-the-immune-system-23d077b65f71
[14:24] Hope you all had a chance to read through it.
[14:25] im still voting for the lake of fire method
[14:25] I think the lake of fire was my favorite too.
[14:25] Agreed
[14:25] I'm with ya russk
[14:25] I have sourced the lake part.
[14:25] We found a burning pit in Utah, but no lake.
[14:25] aw
[14:26] Must try harder.
[14:26] The code has moved to 60 blocks.
[14:26] The reason for 55 was to have "buffer"
[14:26] https://en.wikipedia.org/wiki/Darvaza_gas_crater
[14:26] I would love to hear thoughts about the solution being proposed.
[14:26] Buffer isn't needed if we get all the >= and the counts right.
[14:27] Or questions/suggestions.
[14:27] Exchanges don't go by time, but by confirmations. Confirmations are the block count, so if it can't re-org at 60, then 60 should be a safe level.
[14:27] Plus 60 is easier to explain to people than 55 because the timing is in line with bitcoin.
[14:27] It might be lower, but we opted for a more conservative number.
[14:27] The downside risk is a chain split on an honest/honest split.
[14:28] With years of data, we could look at all the chain splits and determine the probability of a long split.
[14:29] For instance, a network cable between China and the rest of the world is cut, and then comes back on line later.
[14:29] I think the code decision is sound. The only way a chain split would occur is splitting the hardware links around the world. Wartime scenario?
[14:29] say if 50% of nodes upgrade to the new maxreorg client and someone tries to reorg the chain there will be a big split right?
[14:30] Yes.
[14:30] == Raven-Fam|21005 [[email protected]/web/cgi-irc/kiwiirc.com/ip.65.23.49.44] has joined #ravencoin-dev
[14:30] Most exchanges today give access to bitcoin funds long before 6 confirmations, so you wouldn't expect exchanges to require 60 confirms either, correct?
[14:30] Although that risk exists primarily between now and early Nov. After that, we hope 90%+ will be on the asset aware software.
[14:31] which is why you all need to upgrade your wallets and vote for the correct chain and tell your friends.
[14:31] got it, 2.1 will be the actual client for the hardfork, correct?
[14:31] The exchanges are welcome to take on additional risk. The risk decreases as the hashpower goes up.
[14:31] 2.1 is the planned version number.
[14:32] also, say if i am still on 2.0.3-4 will i still be able to use assets after the hardfork?
[14:32] how incompatible are the clients
[14:32] At that point 2.0.3-4 clients would be on a different fork I believe.
[14:34] any node with version < 2.1 will fork when assets are active.
[14:34] Assets activate when 90% of the blocks are mined with 2.1+
[14:34] We'll work hard to ensure exchanges and pools have updated to 2.0.4.1 first and then to 2.1 when it's available.
[14:34] awesome
[14:35] But we want the community to help get the word out as well. Raven needs you!
[14:35] We need a raven with a US Army hat guy to get people to update.
[14:35] lol
[14:36] Ill ping Pathfinder and get him on it.
[14:36] Only you can help assure upgrades
[14:36] Any other questions/comments/suggestions on Max Re-Org?
[14:37] So just to be clear- the max reorg is included in 2.0.4.1 of not?
[14:37] No, it is not.
[14:37] Only the bitcoin bug fix is in 2.0.4.1
[14:38] Okay, open Q&A then!
[14:38] Russk go!
[14:38] lol
[14:39] when are you guys going to implement native bech32?
[14:39] Is there time to talk about asset_name token burning? There has been a proposal for RPC commands to let an asset_token owner burn them in order to clean out unwanted asset names and reduce UTXO. That appears to be easy and relatively uncontroversial.
[14:39] also anyone working on RSK yet
[14:40] Bech 32 was deprecated.
[14:40] Honestly don't know much about it.
[14:41] is the block size going to increase to 2mb when we fork?
[14:41] russk tell me more.
[14:41] I thought it was the new btc address format...
[14:41] it is
[14:41] it allows native segwit addresses
[14:41] https://github.com/bitcoin/bips/blob/mastebip-0173.mediawiki
[14:41] Ravencoin forked in the middle of implementation of segwit, it's planned to be added with Segwit.
[14:41] Raven is already 2mb
[14:41] really?
[14:42] i thought it was 1mb
[14:42] It's part of the vote coming up on Oct 31
[14:42] ah ok
[14:42] It's in there, but BIP9 has to activate first.
[14:42] Yes. We've also tested that it is possible to fill a 2MB block
[14:42] Or rather BIP9 voting will activate RIP2 which will increase the block size.
[14:43] https://i.imgflip.com/2igmj7.jpg
[14:43] do you guys have a timeframe of when segwit is being fully added?
[14:43] I want you. Nice one.
[14:44] and for when they have done it, you can use https://i.imgflip.com/2igmml.jpg
[14:44] lol
[14:44] Wow, we have a meme master in the community!
[14:44] @HansSchmidt any new code would be appreciated, if you have the ability to code the rpc called please submit an PR to the repo
[14:44] I can't even open Photoshop that fast
[14:45] We are talking about adding anti-spam features into the wallet.
[14:45] Basically, if somebody sends an asset to an address that has been already used it could be an unwanted asset.
[14:45] == vap0r-XMR [[email protected]/web/cgi-irc/kiwiirc.com/ip.67.255.25.134] has joined #ravencoin-dev
[14:46] One more meme from the master: ttps://i.imgflip.com/2igmtd.jpg
[14:46] https://i.imgflip.com/2igmtd.jpg
[14:46] == Raven-Fam|1781 [[email protected]/web/freenode/ip.181.215.110.161] has joined #ravencoin-dev
[14:46] Understood. I'll look at it, but I'm more python than C
[14:47] == SweetAndLow [~[email protected]] has joined #ravencoin-dev
[14:47] Perfect
[14:47] That would still be great Hans.
[14:47] im looking into implementing RSK
[14:48] @HansSchmidt You don't need C
[14:48] it doesnt look crazy hard, just some java stuff
[14:48] == Zaaaab [[email protected]/web/cgi-irc/kiwiirc.com/ip.174.211.21.7] has joined #ravencoin-dev
[14:48] c++
[14:48] more like c--
[14:49] == Raven-Fam|21005 [[email protected]/web/cgi-irc/kiwiirc.com/ip.65.23.49.44] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
[14:49] when ravencoin client coded in assembly
[14:49] == Zaaaab [[email protected]/web/cgi-irc/kiwiirc.com/ip.174.211.21.7] has quit [Client Quit]
[14:49] I was referring to @blondfrog new RPCs
[14:49] == Zaaaab [[email protected]/web/cgi-irc/kiwiirc.com/ip.174.211.21.7] has joined #ravencoin-dev
[14:49] I'd like to help with RSK
[14:49] We would love you to help!
[14:50] if you know java you can probably do it @vap0r
[14:50] https://github.com/rsksmart
[14:50] fork rskj and bitcoinj
[14:50] Thanks
[14:51] RSK would be extremely useful for bond-like implementations
[14:51] assets would probably mess RSK up tho
[14:51] Im off now thanks for the hard work guys!
[14:52] It might be a fun merge for sure.
[14:52] Thanks for joining!
[14:52] == AlsoSushi [[email protected]/web/cgi-irc/kiwiirc.com/ip.185.220.101.33] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
[14:52] the bitcoinj client doesnt look crazy hard to port over to ravencoin
[14:52] == lsji07 [~[email protected]] has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )]
[14:52] you would just need to change the diff algo to DGW and make an x16r java implementation
[14:53] It shouldn't be too hard.
[14:53] Which channel can I disclose a vulnerability?
[14:53] is it the bitcoin double spend vulnerability?
[14:53] or something new
[14:53] DM Chatturga on discord.
[14:53] == dudeman [[email protected]/web/cgi-irc/kiwiirc.com/ip.65.23.49.44] has joined #ravencoin-dev
[14:53] No, on Testnet
[14:53] ahh ok yea dm chatturga
[14:54] Either way, you can send it to me and I can make surfe it gets where it needs to go.
[14:54] sure*
[14:54] Do you have a suggested fix?
[14:54] Not currently, need more time
[14:55] Just give Chatturga a ping, and we can talk about it
[14:55] Thank you vap0r!
[14:55] i am extremely curious to see what this vulnerability is
[14:55] Does not impact supply
[14:56] assets related?
[14:56] On second thought vap0r just share it here if you don't mind.
[14:56] this is testnet so its meant to be bug tested
[14:57] If it's a testnet only bug then please feel free to share.
[14:58] We're now on pins and needles vap0r.
[14:58] :)
[14:59] Any other questions while we wait?
[14:59] Or another meme? ;)
[15:00] Do you all like these open developer meetings?
[15:00] == Mixed [[email protected]/web/freenode/ip.50.1.102.108] has joined #ravencoin-dev
[15:00] yea they are nice
[15:00] no
[15:00] lol
[15:00] hahaha!!! to bad blondy
[15:00] if they were on discord it would be nicer
[15:01] == vap0r-XMR [[email protected]/web/cgi-irc/kiwiirc.com/ip.67.255.25.134] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
[15:01] lol
[15:01] there he goes
[15:01] Vap0r left...
[15:01] +1 on Discord
[15:01] Is anyone using testnet6 yet? I built develop2 branch to get 2.0.6 to play with, but had to modify it back to testnet5 in order to be useful. Even on testnet5 there has been only one person sometimes cpu mining.
[15:01] Is anyone using testnet6 yet? I built develop2 branch to get 2.0.6 to play with, but had to modify it back to testnet5 in order to be useful. Even on testnet5 there has been only one person sometimes cpu mining.
[15:01] Is anyone using testnet6 yet? I built develop2 branch to get 2.0.6 to play with, but had to modify it back to testnet5 in order to be useful.
[15:01] We're setting up seed nodes for testnet6.
[15:02] Seed nodes are being updated.
[15:02] wierd echo...
[15:02] Love that you're pulling the code Hans!
[15:02] im not on testnetv6 yet, i could compile the binaries and then we could play around @hans
[15:02] We expect testnet6 consensus rules to be the final ones.
[15:03] when are we getting testnetv20?
[15:03] lol
[15:03] We're working on it russk
[15:03] cant wait
[15:04] how can I find the seed nodes? they're added into the code updates?
[15:04] == Spyder [[email protected]/web/freenode/ip.174.128.245.122] has quit [Quit: Page closed]
[15:04] We're done, thanks everybody.
[15:04] russk -- 14 mistakes from now.
[15:04] Roshii is done. :)
[15:04] Did I see a request for one more meme?
[15:04] https://i.imgflip.com/2igof3.jpg
[15:04] one last question, when moon?
[15:04] == Zaaaab [[email protected]/web/cgi-irc/kiwiirc.com/ip.174.211.21.7] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
[15:05] lol @chatt
[15:05] == Mixed [[email protected]/web/freenode/ip.50.1.102.108] has quit [Ping timeout: 256 seconds]
[15:05] == Sat_Roshii [[email protected]/web/freenode/ip.173.241.144.77] has quit [Quit: Page closed]
[15:05] Seed nodes are behind 3 DNS entries
[15:05] Thanks all. Tron out.
[15:05] == Tron_ [[email protected]/web/freenode/ip.173.241.144.77] has quit [Quit: Page closed]
[15:05] Peace
[15:06] == blondfrogs [[email protected]/web/freenode/ip.91.207.175.238] has quit [Quit: Page closed]
[15:06] == Raven-Fam|1781 [[email protected]/web/freenode/ip.181.215.110.161] has quit [Quit: Page closed]
[15:06] Peace
[15:06] == HansSchmidt [[email protected]/web/cgi-irc/kiwiirc.com/ip.173.239.232.46] has left #ravencoin-dev []
[15:06] 3 domains Ravencoin.org, Ravencoin.com, bitactivate.com
[15:06] 4 dns entries per domain so a total of 12 nodes.
[15:07] Alright, everybody left me. Thanks all for joining this week!
[15:07] I'll never let go, Wolf
[15:07] I think we'll try discord two weeks from now.
[15:07] good shit guys, keep up the good work
[15:08] Thank you all! We have the best community!
[15:08] And definitely the best Memes!
[15:08] == Zaaaab [[email protected]/web/cgi-irc/kiwiirc.com/ip.174.211.21.7] has joined #ravencoin-dev
[15:09] Have a great weekend.
submitted by Chatturga to Ravencoin [link] [comments]

Welcome to the FLO subreddit! Here you can learn about FLO and its use as a worldwide public record in many blockchain-based applications

FLO: a worldwide public record

http://flo.cash

What is FLO?
FLO is a cryptocurrency that introduces a worldwide public record for storing information. FLO coins are needed to pay for storage capacity, and coins are issued to reward participants for their work to secure and distribute information.
FLO is used to send payments and store data. This encourages building applications because anyone has the ability to write data into FLO.
How does FLO work?
FLO is a network similar to bitcoin where the open ledger is secured by miners competing to find proof-of-work. FLO has its own ledger, called the FLO blockchain, that can be thought of as a digital public space for storing information.

Download

0.15.1.1
Release files https://github.com/floblockchain/flo/releases

Features

Technical Specifications

Block target spacing: 40 seconds
Difficulty retargets every blocks
Block reward: 100 FLO, halving every 800,000 blocks (about 1 year)
Maximum coins: 160 million FLONetwork port: 7312RPC port: 7313

Mining Information

See our mining guide here: https://forum.flo.cash/t/mining-guide-antminer-l3/36

Block explorers

http://flocha.in/
http://network.flo.cash/

Exchanges

Bittrex https://bittrex.com/Market/Index?MarketName=BTC-FLO
Nova https://novaexchange.com/market/BTC_FLO/
OpenBazaar https://openbazaar.org/
Komodo https://komodoplatform.com/decentralized-exchange/
Blocknet https://www.blocknet.co/block-dx/
Indacoin https://indacoin.com/
Thecoin.pw Exchange https://trade.thecoin.pw
Coin swap services https://coinswitch.co/http://changenow.io

Social

Twitter http://twitter.com/FLOblockchain
Telegram https://t.me/FLOblockchain
Alexandria Rocket Chat https://chat.alexandria.io
YouTube https://www.youtube.com/channel/UCDAELSdJelys5VkE1FuXo2A
Medium Blog https://medium.com/flo-cash
Reddit http://www.reddit.com/FLOblockchain
IRC channel Join #florincoin on http://webchat.freenode.net/
FLO Slack https://florincoin.slack.com/shared_invite/MTgzNDk0MzYxMjY5LTE0OTQ4MTgzMDEtNGIwYzI4NjkwNw

Merchants

http://cryptocloudhosting.org/order
https://cointopay.com/

Notable Partnerships:

California Institute of Technology- https://etdb.caltech.edu/
Overstock's tZERO - https://www.tzero.com/
Open Index Protocol Working Group- https://github.com/oipwg / http://oip.wiki/
Medici Ventures- www.mediciventures.com

Apps running on top of the FLO blockchain:

https://flo.cash/dapps.html
OIP apps
Open Index Protocol - https://oip.wiki/
Alexandria - https://alexandria.io/browse
California Institute of Technology - https://etdb.caltech.edu/browse
Medici Ventures - https://www.mediciventures.com/
Block Header - https://t.me/blockheader
FLO native apps
Overstock's tZERO - https://www.tzero.com/
Shared Secret - http://www.sharedsecret.net/
Notarize with Flotorizer - http://flotorizer.net/
World Mood - http://worldmood.io/
Aterna Love - https://github.com/metacoin/aternaloveXcertify - https://github.com/akhil2015/Xcertify

Links

Official web site http://www.flo.cash
Github links for Alexandria, OIP, Ranchi, and FLO
https://github.com/floblockchain
https://github.com/oipwg
https://github.com/dloa
https://github.com/RanchiMall
FLO Foundation http://flo.foundation
Roadmap https://trello.com/b/jFlPhrzW/florincoin-roadmap
Florincoin and Alexandria presentation @ BitDevs NYC 5/24/17 https://twitter.com/Official_Florin/status/867614281868726273
Florincoin @ CryptoCurrency Convention NYC 4/9/14 https://www.youtube.com/watch?v=0U7MXAYCXGc
Florin article @ bitcoinist http://bitcoinist.net/exclusive-qa-with-joseph-fiscella-florincoin-and-decentralized-applications/
Blockchain bootstrap from http://cryptochainer.com/dihttps://mega.nz/#!u15HSADT!nstJ67-mKnWZbMPwddeRJoxEnNneS_94yTfLHoeNQyg
FLO market data read from FLO blockchain visualised http://iquidus.io:5000/
The Decentralized Library of Alexandria - San Diego Bitcoin Meetup 08/15 https://www.youtube.com/watch?v=XiZnjM7Y7Cs
Blocktech Project Alexandria v0.4 alpha Intro and Walkthrough https://www.youtube.com/watch?v=z_u-ndscZjY
Alexandria v0.5.1 alpha demo https://www.youtube.com/watch?v=zcuj_xILct0
FLO History
Launched June 17th 2013, the first coin with a metadata field on the blockchain for the purpose of building blockchain applications.
2013 * Jun 17th: FLO released with no pre-mine and no ICO https://bitcointalk.org/index.php?topic=236742.0 * Jul 9th: Florincoin is the 61st coin added to Cryptsy, the first major altcoin exchange * Sep 9th: Created the first block explorer, florinexchange.com/explorer, an open source explorer which is later replaced with https://florincoin.info * Nov 27th: Coordinated with Skyangel on a hard-fork (required update) to increase the transaction comment size to 528 bytes https://bitcointalk.org/index.php?topic=236742.msg3731680#msg3731680 * Dec 10th: Started work on new website * Dec 16th: Songs of Love, a charity for children based in NYC, beings accepting FLO donations to make customized songs for children in need
2014 * Feb 1st: Created the FLO twitter account https://twitter.com/floblockchain (Originally @Official_Florin) * Feb 1st: Created a website, Aterna Love, to store valentine's day messages in the blockchain. Those messages still exist today * Feb 12th: Promoted FLO at the bitcoin center in NYC, with interview by Naomi Brockwell https://www.youtube.com/watch?v=BbeYJID7Ewg * Mar 2nd: Launched new florincoin.org website * Mar 20th: Florincoin subreddit created https://reddit.com/floblockchain (originally /florincoin) * Apr 9th: Presentation about Florincoin at the 1st Cryptocurrency Convention at the scholastic auditorium in NYC https://www.youtube.com/watch?v=giUL0Wiaz1M * Apr 12th: skyangel releases Florin v0.6.5.13, a hard fork at block 426000, causing FLO to start adjusting difficulty every block https://bitcointalk.org/index.php?topic=236742.msg6191701#msg6191701 * Jun 21st: skyangel releases Florin v0.8.7.2, up to date with the latest Litecoin codebase https://bitcointalk.org/index.php?topic=236742.msg7440510#msg7440510 * Jun 22nd: bitcoinist.net article: exclusive Q&A with Joseph Fiscella http://bitcoinist.com/exclusive-qa-with-joseph-fiscella-florincoin-and-decentralized-applications/ * Sep 20th: Alexandria team meets in San Diego to work on the project as a team for the first time * Oct 4th: Inside Bitcoins Las Vegas conference with the Alexandria Booth
2015 * Jan 1st: FLO and Alexandria mentioned in a chapter about blockchain applications in Melanie Swan's book Blockchain: A Blueprint for a New Economy http://shop.oreilly.com/product/0636920037040.do * Mar 3rd: Released the first golang SDK for Florincoin, foundation, on github: - https://github.com/metacoin/foundation - https://github.com/metacoin/flojson * Mar 11th: FLO is open for trading on Bittrex * Mar 11th: FLO is open for trading on Poloniex * Apr 17th: Alexandria 0.4 walkthrough video: https://www.youtube.com/watch?v=z_u-ndscZjY * Jun 10th: n-o-d-e.net interview with Alexandria https://n-o-d-e.net/alexandria.html * Jun 25th: Alexandria historian is born and begins recording historic data on the blockchain * Jun 29th: VICE article about Alexandria released: Could Cyberwar Cause a Library of Alexandria Event? https://motherboard.vice.com/en_us/article/ae3p4p/could-cyberwar-cause-a-library-of-alexandria-event * Aug 5th: LA times article about Blockchain Technology Group / Alexandria http://www.latimes.com/business/la-fi-cutting-edge-blockchain-20150809-story.html * Sep 24th: CoinTelegraph article about Alexandria https://cointelegraph.com/news/a-glimpse-into-the-future-of-decentralized-media * Dec 9th: Alexandria v0.5.1 alpha demo https://www.youtube.com/watch?v=zcuj_xILct0 * Dec 16th: Alexandria booth at Inside Bitcoins San Diego https://i.imgur.com/zZWi31F.jpg
2016 * Mar 25th: FLO 0.10.4.0 released by Bitspill and the Alexandria team, as well as a pool mining historian blocks https://bitcointalk.org/index.php?topic=236742.msg14314984#msg14314984 * Apr 8th: FLO used to store Libertarian Party votes in blockchain https://www.coindesk.com/libertarian-party-texas-logs-votes-presidential-electors-blockchain/ * May 3rd: Alexandria meetup in NYC (video URL missing) * Jun 19th: FLO 0.10.4.4 recommended update to latest Litecoin codebase * Nov 27: Alexandria presentation at DAppHack Berlin 2016 https://www.youtube.com/watch?v=qwqkmK9aTXs
2017 * May 15th: FLO meetup in NYC, Telegram channel created https://bitcointalk.org/index.php?topic=236742.1560 * May 25th: FLO/Alexandria presentation lived streamed from BitDevs NYC: https://twitter.com/FLOblockchain/status/867614281868726273 * July 12th: Introducing Alexandria and the Open Index Protocol https://steemit.com/cryptocurrency/@m3ta/introducing-alexandria-and-the-open-index-protocol * July 28th: Amy's blog post about the Alexandria team's visit to San Diego https://medium.com/@amyellajames/build-faster-51712d0ed51d * Aug 20th: Valentin Jesse creates a FLO touchbar app for the 2017 MacBookPro https://bitcointalk.org/index.php?topic=236742.msg21047455#msg21047455 * Nov 29th: New logo and new website concept released and revealed to community in the rebranding initiative https://bitcointalk.org/index.php?topic=236742.msg25431477#msg25431477 * Dec 22nd: New website launched: https://flo.cash * Dec 22nd: Flotorizer launched at flotorizer.net, Medium article written by Davi Ortega describing the creation of a FLO blockchain application as a non-programmer https://medium.com/@ortega_science/flotorizer-an-experiment-on-blockchain-for-noobs-5dfb3aa6bbd2 * Dec 24th: FLO Community Update https://steemit.com/cryptocurrency/@m3ta/flo-community-update-december-2017 * Dec 31st: SharedSecret.net, the first blockchain-based implementation of Shamir's Secret Sharing algorithm, is live (again created by Davi Ortega)
2018 * Jan 13th: Live-streaming FLO dev on twitch.tv https://www.youtube.com/watch?v=AAbk8FrbF7k * Jan 18th: FLO python SDK released https://github.com/metacoin/flo-python-sdk * Jan 18th: FLO added to brainwalletX https://github.com/brainwalletX/brainwalletX.github.io/pull/5/files * Jan 18th: FLO C# SDK released https://github.com/adreno-abhi/Flo-CSharp-SDK * Feb 23th: FLO partners with YBF Ventures http://ybfventures.com/worlds-first-web-3-0-hub-ybf-mesh/ * Mar 20th: FLO releases version 0.15 with segwit support, up-to-date with current Bitcoin and Litecoin codebases: https://github.com/floblockchain/flo/releases * May 1st: SPV wallet floj is open-sourced by Alexandria and Medici teams https://github.com/floj-org/floj * July 17th: FLO summit 2018 held in San Diego https://twitter.com/FLOblockchain/status/1018858384534179842 * July 26th: Website updated with dapps dashboard https://twitter.com/flo_development/status/1022534376226213890
submitted by metacoin to floblockchain [link] [comments]

As requested: I trade bitcoins on a regular basis, AMA

in response to: http://www.reddit.com/IAmA/comments/holkw/ama_request_someone_who_trades_in_bitcoins_on_a/
I've been trading bitcoins for a while now, I bought my first 400 BTC back when the prices were around 0.20/USD per BTC.
Didn't know this subject was so interesting, but anyway, AMA.
Edit: I have to go attend a lecture in about 30 mins but I'll be back on later this afternoon! I had no idea there was such an interest in bitcoins! Anyway, if you have burning questions that need to be answered while I'm gone, you can always hit up #bitcoin-otc or #bitcoin on freenode IRC. See you guys in a few hours!
edit #2: I'm back... trying to get caught up... seems that a lot of people don't know what bitcoin is, so I'll add this link that will hopefully clear things up: http://www.weusecoins.com/
edit #3: Verification... ok, so someone wanted verification... I have clearsigned the post asking for verification using my GPG key here: http://pastebin.com/nxNRmegA
I used the gpg key I use for bitcoin-otc: http://bitcoin-otc.com/viewgpg.php You'll notice I"m user 23... they swapped to a new gpg system back in march... If you look at my rating, you'll see my first was back in december of 2010... before the new ratings came along and bitcoin exploded, my gpg key was registered with the OLD system... which was just listed in the wiki: http://wiki.bitcoin-otc.com/wiki/User_GPG_keys
Anyway, my nickname (nick2day) is also the same nickname I use for btc stuff... so it should be fairly easy to verify everything with the information I've given...
Does that work?
submitted by nick2day to IAmA [link] [comments]

What is Bitcoin - Team Queen Wiki BITCOIN BREAKOUT IMMINENT!!!  $7,000,000,000,000 PRINTED BY THE FED!! BRRRRR New BTC Earning Site  Claim Free Bitcoin  Earn Free Bitcoin 2020  Claim & Earn Free Bitcoin How to get Started With Bitcoin What Does Bitcoin Become?

The bitcoin protocol requires 100 network blocks to pass after a new coin has been created to see any transaction which contains it as valid. If you check the source bitcoin addresses on your transaction on blockchain.info and click 'output' next to it, you can see if its a new coin and which block it was created in. Search Bitcoin in the channels list of IRC network freenode and get informed about freenode's users and topics! Current Chat Rooms: bitcoin, bitcoin-pricetalk, bitcoin-core-dev, bitcoin-otc, bitcoinsoftware, electrum, lightning-dev, talos-workstation, bitcoin-dev, #bitcoin This page was last edited on 31 May 2011, at 04:54. Content is available under Creative Commons Attribution 3.0 unless otherwise noted.; Privacy policy; About Bitcoin the note about bitcoin-otc promote on a more appropriate place in this page? reference to trading and IRC. Conducting business using Bitcoin-OTC can be done more anonymously when directly connected to a Freenode IRC hidden service. bitcoind . Run Bitcoind with -proxy=127.0.0.1:9050 (or whatever your SocksPort is). De Bitcoin Wiki. Aller à : navigation, rechercher. Présentation. Le chan #bitcoin-fr sur Freenode permet aux francophones de discuter et de partager autour du Bitcoin. rejoindre le chan #bitcoin-fr; rejoindre le chan #bitcoin-fr (webchat)

[index] [4468] [14508] [29474] [19366] [2110] [2089] [3414] [21908] [21632] [11017]

What is Bitcoin - Team Queen Wiki

Bitcoin, también Bitcóin (signo: ฿; abr.: BTC, XBT4 ), es una criptodivisa concebida en 2009 por Satoshi Nakamoto. El término se aplica también al protocolo y a la red P2P que lo sustenta ... Team Queen Wiki is the fastest growing team in CFX! Earn Bitcoin while you Learn Forex! Cash FX Group has strategic alliances with the most recognized institutions in the financial markets. Bitcoin is a cryptocurrency and a digital payment system invented by an unknown programmer or a group of programmers under the name Satoshi Nakamoto It was released as open source software in The s... BITCOIN TODAY: In this video, I'll go through the Bitcoin news today & I'll make a Bitcoin price analysis. The BTC news & analysis can be inspiration for your own Bitcoin trading or investing, but ... The Of Bitcoin - Wikipedia Here are three actions to help you get started utilizing Bitcoin Money right now: A Bitcoin wallet is an app or program that enables you send and receive BCH. Wallets ...

Flag Counter