What Is Bitcoin Block Size and Why Does It Matter ...

What if Bitcoin increases the block size by just 25%?

What if Bitcoin increases the block size by just 25%?
What if block sizes are 1.25MB? Would the change in block size be worth it, considering the increase in transaction capacity?
How fruitful is it to be fearful of change? Cheers and Limitless Peace
submitted by MichaelTen to Bitcoin [link] [comments]

05-25 12:36 - '[Satoshi literally posted on the early bitcoin forums that the block size could be changed later on and gave an example in code] / [quote] [quote] Satoshi literally just didn't consider that there would be people dumb enough to bu...' by /u/Smarag removed from /r/Bitcoin within 0-7min

'''
[Satoshi literally posted on the early bitcoin forums that the block size could be changed later on and gave an example in code]1
In response to Satoshi’s comment that the limit could always be removed if necessary to support higher transaction capacity, Jeff Garzik pointed out:
“IMO it's a marketing thing. It's tough to get people to buy into a system, if the network is technically incapable of supporting high transaction rates.”
Satoshi literally just didn't consider that there would be people dumb enough to buy into the idea that you "need to keep the code pure"
Satoshi's proposed change:
“It can be phased in, like:
if (blocknumber > 115000)
maxblocksize = largerlimit
It can start being in versions way ahead, so by the time it reaches that block number and goes into effect, the older versions that don't have it are already obsolete.
When we're near the cutoff block number, I can put an alert to old versions to make sure they know they have to upgrade.”
This is the internet, we have first hand original sources for all of this.
'''
Context Link
Go1dfish undelete link
unreddit undelete link
Author: Smarag
1: coi*tel*grap*.c*m/new*/sato*his-*e*t-kept-se*re*-*hy-*s-t**re-a-1-m*-limi**to-*i*co****lock-siz*
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

On June 25, 2015 Gavin Andersen tried to increase the Bitcoin BTC block size through a hard fork. The developers purposely modified Bitcoin Trunk to break his comimts and prevent his code from working.

Here is BIP101, Gavin's proposal for a hard fork block size increase:
https://github.com/bitcoin/bips/blob/mastebip-0101.mediawiki
And here is Gavin's commit to implement it:
https://github.com/bitcoin/bitcoin/pull/6341
His last comment before he closed his pull was:
Closing for now; too painful to try to keep up with the movement of code from main.h to policy/policy.h.
Gaving was writing BCH before it was cool to write BCH.
EDIT: He tried to write code to allow a hard fork with a larger block size. And the other devs made sue his code would not merge back into the main development tree. The title is a little misleading. Apologies. I can't edit it.
submitted by plazman30 to btc [link] [comments]

04-08 16:25 - '[quote] You and the quarter million others who've been silenced for asking questions. The war isn't over the block size. The war is over the right to talk about the block size.' by /u/alwaysAn0n removed from /r/Bitcoin within 44-54min

'''
I really want to understand the BTC side to come to my own conclusion of it.
You and the quarter million others who've been silenced for asking questions. The war isn't over the block size. The war is over the right to talk about the block size.
'''
Context Link
Go1dfish undelete link
unreddit undelete link
Author: alwaysAn0n
submitted by removalbot to removalbot [link] [comments]

Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft] | Upal Chakraborty | Aug 25 2015

Upal Chakraborty on Aug 25 2015:
Github: https://github.com/UpalChakraborty/bips/blob/masteBIP-DynamicMaxBlockSize.mediawiki
BIP: 1xx
Title: Dynamically Controlled Bitcoin Block Size Max Cap
Author: Upal Chakraborty <bitcoin at upalc.com>
Status: Draft
Type: Standards Track
Created: 2015-08-24
==Abstract==
This BIP proposes replacing the fixed one megabyte maximum block size
with a dynamically controlled maximum block size that may increase or
decrease with difficulty change depending on various network factors.
I have two proposals regarding this...
i. Depending only on previous block size calculation.
ii. Depending on previous block size calculation and previous Tx fee
collected by miners.
==Motivation==
With increased adoption, transaction volume on bitcoin network is
bound to grow. If the one megabyte max cap is not changed to a
flexible one which changes itself with changing network demand, then
adoption will hamper and bitcoin's growth may choke up. Following
graph shows the change in average block size since inception...
https://blockchain.info/charts/avg-block-size?timespan=all&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=
==Specification==
===Proposal 1 : Depending only on previous block size calculation===
If more than 50% of block's size, found in the first 2000 of the
last difficulty period, is more than 90% MaxBlockSize
 Double MaxBlockSize 
Else if more than 90% of block's size, found in the first 2000 of
the last difficulty period, is less than 50% MaxBlockSize
 Half MaxBlockSize 
Else
 Keep the same MaxBlockSize 
===Proposal 2 : Depending on previous block size calculation and
previous Tx fee collected by miners===
TotalBlockSizeInLastButOneDifficulty = Sum of all Block size of
first 2008 blocks in last 2 difficulty period
TotalBlockSizeInLastDifficulty = Sum of all Block size of second
2008 blocks in last 2 difficulty period (This actually includes 8
blocks from last but one difficulty)
TotalTxFeeInLastButOneDifficulty = Sum of all Tx fees of first 2008
blocks in last 2 difficulty period
TotalTxFeeInLastDifficulty = Sum of all Tx fees of second 2008
blocks in last 2 difficulty period (This actually includes 8 blocks
from last but one difficulty)
If ( ( (Sum of first 4016 block size in last 2 difficulty
period)/4016 > 50% MaxBlockSize) AND (TotalTxFeeInLastDifficulty >
TotalTxFeeInLastButOneDifficulty) AND (TotalBlockSizeInLastDifficulty
TotalBlockSizeInLastButOneDifficulty) )
 MaxBlockSize = TotalBlockSizeInLastDifficulty * MaxBlockSize / 
TotalBlockSizeInLastButOneDifficulty
Else If ( ( (Sum of first 4016 block size in last 2 difficulty
period)/4016 < 50% MaxBlockSize) AND (TotalTxFeeInLastDifficulty <
TotalTxFeeInLastButOneDifficulty) AND (TotalBlockSizeInLastDifficulty
< TotalBlockSizeInLastButOneDifficulty) )
 MaxBlockSize = TotalBlockSizeInLastDifficulty * MaxBlockSize / 
TotalBlockSizeInLastButOneDifficulty
Else
 Keep the same MaxBlockSize 
==Rationale==
These two proposals have been derived after discussion on
[https://bitcointalk.org/index.php?topic=1154536.0 BitcoinTalk] and
[http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010285.html
bitcoin-dev mailing list]. The original idea and its evolution in the
light of various arguements can be found
[http://upalc.com/maxblocksize.php here].
===Proposal 1 : Depending only on previous block size calculation===
This solution is derived directly from the indication of the problem.
If transaction volume increases, then we will naturally see bigger
blocks. On the contrary, if there are not enough transaction volume,
but maximum block size is high, then only few blocks may sweep the
mempool. Hence, if block size is itself taken into consideration, then
maximum block size can most rationally be derived. Moreover, this
solution not only increases, but also decreases the maximum block
size, just like difficulty.
===Proposal 2 : Depending on previous block size calculation and
previous Tx fee collected by miners===
This solution takes care of stable mining subsidy. It will not
increase maximum block size, if Tx fee collection is not increasing
and thereby creating a Tx fee pressure on the market. On the other
hand, though the block size max cap is dynamically controlled, it is
very difficult to game by any party because the increase or decrease
of block size max cap will take place in the same ratio of average
block size increase or decrease.
==Compatibility==
This is a hard-forking change to the Bitcoin protocol; anybody running
code that fully validates blocks must upgrade before the activation
time or they will risk rejecting a chain containing
larger-than-one-megabyte blocks.
==Other solutions considered==
[http://gtf.org/garzik/bitcoin/BIP100-blocksizechangeproposal.pdf
Making Decentralized Economic Policy] - by Jeff Garzik
[https://bitcointalk.org/index.php?topic=1078521.0 Elastic block cap
with rollover penalties] - by Meni Rosenfeld
[https://github.com/bitcoin/bips/blob/mastebip-0101.mediawiki
Increase maximum block size] - by Gavin Andresen
[https://gist.github.com/sipa/c65665fc360ca7a176a6 Block size
following technological growth] - by Pieter Wuille
[https://lightning.network/lightning-network-paper.pdf The Bitcoin
Lightning Network: Scalable Off-Chain Instant Payments] - by Joseph
Poon & Thaddeus Dryja
==Deployment==
If consensus is achieved, deployment can be made at a future block
number at which difficulty will change.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150825/89d505e5/attachment.html>
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010640.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

09-25 05:41 - 'I thought the whole point of small block sizes was that you can participate fully in the Bitcoin ecosystem even if all you have is a toaster with satellite internet in the middle of the Australian outback.' by /u/Harfatum removed from /r/Bitcoin within 5-15min

'''
I thought the whole point of small block sizes was that you can participate fully in the Bitcoin ecosystem even if all you have is a toaster with satellite internet in the middle of the Australian outback.
'''
Context Link
Go1dfish undelete link
unreddit undelete link
Author: Harfatum
submitted by removalbot to removalbot [link] [comments]

08-25 22:52 - 'Enough. How many BTC are you willing to bet that Segwit will not significantly increase effective block size/tx count within the coming months? / If you'd like to put up at least 5 BTC, please message me until I answer, so we ca...' by /u/Varakari removed from /r/Bitcoin within 0-4min

'''
Enough. How many BTC are you willing to bet that Segwit will not significantly increase effective block size/tx count within the coming months?
If you'd like to put up at least 5 BTC, please message me until I answer, so we can try to work out terms and escrow. Otherwise, please go be a troll somewhere else.
'''
Context Link
Go1dfish undelete link
unreddit undelete link
Author: Varakari
submitted by removalbot to removalbot [link] [comments]

05-14 20:42 - '* Where I said I don't want SegWit? * Where did I say I don't want Lightning? * Where did I say I want unlimited block sizes? / I was just stating that since u/metalzip is already running at maximum capacity, with SegWit he...' by /u/DianaQWERTY removed from /r/Bitcoin within 25-35min

'''
I was just stating that since metalzip is already running at maximum capacity, with SegWit he will have to shut down his full node. With or without the 2MB fork he will have to shut down the node or buy more storage.
You're imagining things, wrote a bunch of shit which I never even touched, and insulted me.
'''
Context Link
Go1dfish undelete link
unreddit undelete link
Author: DianaQWERTY
submitted by removalbot to removalbot [link] [comments]

08-25 22:31 - 'Assuming even a modest rate of growth compared to Bitcoin, Monero craps out at 3 transactions per second, even with futuristic computing technology. Proof that "larger block size" doesn't create scalability.' (imgur.com) by /u/Rudd-X removed from /r/Bitcoin within 1095-1100min

Assuming even a modest rate of growth compared to Bitcoin, Monero craps out at 3 transactions per second, even with futuristic computing technology. Proof that "larger block size" doesn't create scalability.
Go1dfish undelete link
unreddit undelete link
Author: Rudd-X
submitted by removalbot to removalbot [link] [comments]

05-25 19:16 - 'Not with current block-size that's for damn sure.' by /u/BA13CR12BA0016 removed from /r/Bitcoin within 148-153min

'''
Not with current block-size that's for damn sure.
'''
Context Link
Go1dfish undelete link
unreddit undelete link
Author: BA13CR12BA0016
submitted by removalbot to removalbot [link] [comments]

[August 25, 2015] Block Size and Hard Fork Dialog /r/Bitcoin

[August 25, 2015] Block Size and Hard Fork Dialog /Bitcoin submitted by coincrazyy to BitcoinAll [link] [comments]

Proposed BIP: Maximum block size consensus rule based on median block size (adaptive block size) | Chris Kleeschulte | Mar 25 2016 /r/bitcoin_devlist

Proposed BIP: Maximum block size consensus rule based on median block size (adaptive block size) | Chris Kleeschulte | Mar 25 2016 /bitcoin_devlist submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft] | Upal Chakraborty | Aug 25 2015 /r/bitcoin_devlist

Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft] | Upal Chakraborty | Aug 25 2015 /bitcoin_devlist submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft] | Upal Chakraborty | Aug 25 2015 /r/bitcoin_devlist

Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft] | Upal Chakraborty | Aug 25 2015 /bitcoin_devlist submitted by coincrazyy to BitcoinAll [link] [comments]

Is this math right? Would increasing the block size by 100x get us a third of the way to having the capacity of visa from 25 years ago? /r/Bitcoin

Is this math right? Would increasing the block size by 100x get us a third of the way to having the capacity of visa from 25 years ago? /Bitcoin submitted by BitcoinAll to BitcoinAll [link] [comments]

[HALVING MEGATHREAD] Block 630000 has been mined. Mining subsidy is now 6.25 BTC per block. The third Bitcoin Halving is now complete!

As of now, 630,000 blocks have been mined on the Bitcoin network, and the block reward has successfully halved for the second THIRD time. The previous block reward was 12.5 BTC, and the new block reward is now 6.25 BTC. Since the previous halving at Block 420000, monetary inflation decreased from 4.17%% to 3.57%. Block 630000 signals an immediate 50% reduction to 1.79%. The next halving will occur at Block 840000 in approximately four years. Godspeed, Bitcoin!
Here's Block 630000 in all its glory!
{ "hash": "000000000000000000024bead8df69990852c202db0e0097c1a12ea637d7e96d", "confirmations": "1", "strippedsize": "1186930", "weight": "3993250", "height": "630000", "version": "536870912", "merkleroot": "b191f5f973b9040e81c4f75f99c7e43c92010ba8654718e3dd1a4800851d300d", "tx": "3134", "time": "1589225023", "nonce": "2302182970", "bits": "387021369", "difficulty": "16104807485529", "previousblockhash": "0000000000000000000d656be18bb095db1b23bd797266b0ac3ba720b1962b1e", } 
coinbase transaction: 6.25 BTC + 0.90968084 BTC in fees
block size: 1186.93 KB
transactions: 3134
total bitcoins: 18,375,000
remaining bitcoins: ~2,625,000
previous halving: 3 years 10 months 2 days 2 hours 37 minutes 30 seconds ago
[Monetary Inflation Chart] [Controlled Supply] [Bitcoin Clock]
[blockstream.info] [insight.io] [tradeblock.com] [mempool.space] [btc.com] [blockchain.com]
submitted by BashCo to Bitcoin [link] [comments]

Proposal: The Sia Foundation

Vision Statement

A common sentiment is brewing online; a shared desire for the internet that might have been. After decades of corporate encroachment, you don't need to be a power user to realize that something has gone very wrong.
In the early days of the internet, the future was bright. In that future, when you sent an instant message, it traveled directly to the recipient. When you needed to pay a friend, you announced a transfer of value to their public key. When an app was missing a feature you wanted, you opened up the source code and implemented it. When you took a picture on your phone, it was immediately encrypted and backed up to storage that you controlled. In that future, people would laugh at the idea of having to authenticate themselves to some corporation before doing these things.
What did we get instead? Rather than a network of human-sized communities, we have a handful of enormous commons, each controlled by a faceless corporate entity. Hey user, want to send a message? You can, but we'll store a copy of it indefinitely, unencrypted, for our preference-learning algorithms to pore over; how else could we slap targeted ads on every piece of content you see? Want to pay a friend? You can—in our Monopoly money. Want a new feature? Submit a request to our Support Center and we'll totally maybe think about it. Want to backup a photo? You can—inside our walled garden, which only we (and the NSA, of course) can access. Just be careful what you share, because merely locking you out of your account and deleting all your data is far from the worst thing we could do.
You rationalize this: "MEGACORP would never do such a thing; it would be bad for business." But we all know, at some level, that this state of affairs, this inversion of power, is not merely "unfortunate" or "suboptimal" – No. It is degrading. Even if MEGACORP were purely benevolent, it is degrading that we must ask its permission to talk to our friends; that we must rely on it to safeguard our treasured memories; that our digital lives are completely beholden to those who seek only to extract value from us.
At the root of this issue is the centralization of data. MEGACORP can surveil you—because your emails and video chats flow through their servers. And MEGACORP can control you—because they hold your data hostage. But centralization is a solution to a technical problem: How can we make the user's data accessible from anywhere in the world, on any device? For a long time, no alternative solution to this problem was forthcoming.
Today, thanks to a confluence of established techniques and recent innovations, we have solved the accessibility problem without resorting to centralization. Hashing, encryption, and erasure encoding got us most of the way, but one barrier remained: incentives. How do you incentivize an anonymous stranger to store your data? Earlier protocols like BitTorrent worked around this limitation by relying on altruism, tit-for-tat requirements, or "points" – in other words, nothing you could pay your electric bill with. Finally, in 2009, a solution appeared: Bitcoin. Not long after, Sia was born.
Cryptography has unleashed the latent power of the internet by enabling interactions between mutually-distrustful parties. Sia harnesses this power to turn the cloud storage market into a proper marketplace, where buyers and sellers can transact directly, with no intermediaries, anywhere in the world. No more silos or walled gardens: your data is encrypted, so it can't be spied on, and it's stored on many servers, so no single entity can hold it hostage. Thanks to projects like Sia, the internet is being re-decentralized.
Sia began its life as a startup, which means it has always been subjected to two competing forces: the ideals of its founders, and the profit motive inherent to all businesses. Its founders have taken great pains to never compromise on the former, but this often threatened the company's financial viability. With the establishment of the Sia Foundation, this tension is resolved. The Foundation, freed of the obligation to generate profit, is a pure embodiment of the ideals from which Sia originally sprung.
The goals and responsibilities of the Foundation are numerous: to maintain core Sia protocols and consensus code; to support developers building on top of Sia and its protocols; to promote Sia and facilitate partnerships in other spheres and communities; to ensure that users can easily acquire and safely store siacoins; to develop network scalability solutions; to implement hardforks and lead the community through them; and much more. In a broader sense, its mission is to commoditize data storage, making it cheap, ubiquitous, and accessible to all, without compromising privacy or performance.
Sia is a perfect example of how we can achieve better living through cryptography. We now begin a new chapter in Sia's history. May our stewardship lead it into a bright future.
 

Overview

Today, we are proposing the creation of the Sia Foundation: a new non-profit entity that builds and supports distributed cloud storage infrastructure, with a specific focus on the Sia storage platform. What follows is an informal overview of the Sia Foundation, covering two major topics: how the Foundation will be funded, and what its funds will be used for.

Organizational Structure

The Sia Foundation will be structured as a non-profit entity incorporated in the United States, likely a 501(c)(3) organization or similar. The actions of the Foundation will be constrained by its charter, which formalizes the specific obligations and overall mission outlined in this document. The charter will be updated on an annual basis to reflect the current goals of the Sia community.
The organization will be operated by a board of directors, initially comprising Luke Champine as President and Eddie Wang as Chairman. Luke Champine will be leaving his position at Nebulous to work at the Foundation full-time, and will seek to divest his shares of Nebulous stock along with other potential conflicts of interest. Neither Luke nor Eddie personally own any siafunds or significant quantities of siacoin.

Funding

The primary source of funding for the Foundation will come from a new block subsidy. Following a hardfork, 30 KS per block will be allocated to the "Foundation Fund," continuing in perpetuity. The existing 30 KS per block miner reward is not affected. Additionally, one year's worth of block subsidies (approximately 1.57 GS) will be allocated to the Fund immediately upon activation of the hardfork.
As detailed below, the Foundation will provably burn any coins that it cannot meaningfully spend. As such, the 30 KS subsidy should be viewed as a maximum. This allows the Foundation to grow alongside Sia without requiring additional hardforks.
The Foundation will not be funded to any degree by the possession or sale of siafunds. Siafunds were originally introduced as a means of incentivizing growth, and we still believe in their effectiveness: a siafund holder wants to increase the amount of storage on Sia as much as possible. While the Foundation obviously wants Sia to succeed, its driving force should be its charter. Deriving significant revenue from siafunds would jeopardize the Foundation's impartiality and focus. Ultimately, we want the Foundation to act in the best interests of Sia, not in growing its own budget.

Responsibilities

The Foundation inherits a great number of responsibilities from Nebulous. Each quarter, the Foundation will publish the progress it has made over the past quarter, and list the responsibilities it intends to prioritize over the coming quarter. This will be accompanied by a financial report, detailing each area of expenditure over the past quarter, and forecasting expenditures for the coming quarter. Below, we summarize some of the myriad responsibilities towards which the Foundation is expected to allocate its resources.

Maintain and enhance core Sia software

Arguably, this is the most important responsibility of the Foundation. At the heart of Sia is its consensus algorithm: regardless of other differences, all Sia software must agree upon the content and rules of the blockchain. It is therefore crucial that the algorithm be stewarded by an entity that is accountable to the community, transparent in its decision-making, and has no profit motive or other conflicts of interest.
Accordingly, Sia’s consensus functionality will no longer be directly maintained by Nebulous. Instead, the Foundation will release and maintain an implementation of a "minimal Sia full node," comprising the Sia consensus algorithm and P2P networking code. The source code will be available in a public repository, and signed binaries will be published for each release.
Other parties may use this code to provide alternative full node software. For example, Nebulous may extend the minimal full node with wallet, renter, and host functionality. The source code of any such implementation may be submitted to the Foundation for review. If the code passes review, the Foundation will provide "endorsement signatures" for the commit hash used and for binaries compiled internally by the Foundation. Specifically, these signatures assert that the Foundation believes the software contains no consensus-breaking changes or other modifications to imported Foundation code. Endorsement signatures and Foundation-compiled binaries may be displayed and distributed by the receiving party, along with an appropriate disclaimer.
A minimal full node is not terribly useful on its own; the wallet, renter, host, and other extensions are what make Sia a proper developer platform. Currently, the only implementations of these extensions are maintained by Nebulous. The Foundation will contract Nebulous to ensure that these extensions continue to receive updates and enhancements. Later on, the Foundation intends to develop its own implementations of these extensions and others. As with the minimal node software, these extensions will be open source and available in public repositories for use by any Sia node software.
With the consensus code now managed by the Foundation, the task of implementing and orchestrating hardforks becomes its responsibility as well. When the Foundation determines that a hardfork is necessary (whether through internal discussion or via community petition), a formal proposal will be drafted and submitted for public review, during which arguments for and against the proposal may be submitted to a public repository. During this time, the hardfork code will be implemented, either by Foundation employees or by external contributors working closely with the Foundation. Once the implementation is finished, final arguments will be heard. The Foundation board will then vote whether to accept or reject the proposal, and announce their decision along with appropriate justification. Assuming the proposal was accepted, the Foundation will announce the block height at which the hardfork will activate, and will subsequently release source code and signed binaries that incorporate the hardfork code.
Regardless of the Foundation's decision, it is the community that ultimately determines whether a fork is accepted or rejected – nothing can change that. Foundation node software will never automatically update, so all forks must be explicitly adopted by users. Furthermore, the Foundation will provide replay and wipeout protection for its hard forks, protecting other chains from unintended or malicious reorgs. Similarly, the Foundation will ensure that any file contracts formed prior to a fork activation will continue to be honored on both chains until they expire.
Finally, the Foundation also intends to pursue scalability solutions for the Sia blockchain. In particular, work has already begun on an implementation of Utreexo, which will greatly reduce the space requirements of fully-validating nodes (allowing a full node to be run on a smartphone) while increasing throughput and decreasing initial sync time. A hardfork implementing Utreexo will be submitted to the community as per the process detailed above.
As this is the most important responsibility of the Foundation, it will receive a significant portion of the Foundation’s budget, primarily in the form of developer salaries and contracting agreements.

Support community services

We intend to allocate 25% of the Foundation Fund towards the community. This allocation will be held and disbursed in the form of siacoins, and will pay for grants, bounties, hackathons, and other community-driven endeavours.
Any community-run service, such as a Skynet portal, explorer or web wallet, may apply to have its costs covered by the Foundation. Upon approval, the Foundation will reimburse expenses incurred by the service, subject to the exact terms agreed to. The intent of these grants is not to provide a source of income, but rather to make such services "break even" for their operators, so that members of the community can enrich the Sia ecosystem without worrying about the impact on their own finances.

Ensure easy acquisition and storage of siacoins

Most users will acquire their siacoins via an exchange. The Foundation will provide support to Sia-compatible exchanges, and pursue relevant integrations at its discretion, such as Coinbase's new Rosetta standard. The Foundation may also release DEX software that enables trading cryptocurrencies without the need for a third party. (The Foundation itself will never operate as a money transmitter.)
Increasingly, users are storing their cryptocurrency on hardware wallets. The Foundation will maintain the existing Ledger Nano S integration, and pursue further integrations at its discretion.
Of course, all hardware wallets must be paired with software running on a computer or smartphone, so the Foundation will also develop and/or maintain client-side wallet software, including both full-node wallets and "lite" wallets. Community-operated wallet services, i.e. web wallets, may be funded via grants.
Like core software maintenance, this responsibility will be funded in the form of developer salaries and contracting agreements.

Protect the ecosystem

When it comes to cryptocurrency security, patching software vulnerabilities is table stakes; there are significant legal and social threats that we must be mindful of as well. As such, the Foundation will earmark a portion of its fund to defend the community from legal action. The Foundation will also safeguard the network from 51% attacks and other threats to network security by implementing softforks and/or hardforks where necessary.
The Foundation also intends to assist in the development of a new FOSS software license, and to solicit legal memos on various Sia-related matters, such as hosting in the United States and the EU.
In a broader sense, the establishment of the Foundation makes the ecosystem more robust by transferring core development to a more neutral entity. Thanks to its funding structure, the Foundation will be immune to various forms of pressure that for-profit companies are susceptible to.

Drive adoption of Sia

Although the overriding goal of the Foundation is to make Sia the best platform it can be, all that work will be in vain if no one uses the platform. There are a number of ways the Foundation can promote Sia and get it into the hands of potential users and developers.
In-person conferences are understandably far less popular now, but the Foundation can sponsor and/or participate in virtual conferences. (In-person conferences may be held in the future, permitting circumstances.) Similarly, the Foundation will provide prizes for hackathons, which may be organized by community members, Nebulous, or the Foundation itself. Lastly, partnerships with other companies in the cryptocurrency space—or the cloud storage space—are a great way to increase awareness of Sia. To handle these responsibilities, one of the early priorities of the Foundation will be to hire a marketing director.

Fund Management

The Foundation Fund will be controlled by a multisig address. Each member of the Foundation's board will control one of the signing keys, with the signature threshold to be determined once the final composition of the board is known. (This threshold may also be increased or decreased if the number of board members changes.) Additionally, one timelocked signing key will be controlled by David Vorick. This key will act as a “dead man’s switch,” to be used in the event of an emergency that prevents Foundation board members from reaching the signature threshold. The timelock ensures that this key cannot be used unless the Foundation fails to sign a transaction for several months.
On the 1st of each month, the Foundation will use its keys to transfer all siacoins in the Fund to two new addresses. The first address will be controlled by a high-security hot wallet, and will receive approximately one month's worth of Foundation expenditures. The second address, receiving the remaining siacoins, will be a modified version of the source address: specifically, it will increase the timelock on David Vorick's signing key by one month. Any other changes to the set of signing keys, such as the arrival or departure of board members, will be incorporated into this address as well.
The Foundation Fund is allocated in SC, but many of the Foundation's expenditures must be paid in USD or other fiat currency. Accordingly, the Foundation will convert, at its discretion, a portion of its monthly withdrawals to fiat currency. We expect this conversion to be primarily facilitated by private "OTC" sales to accredited investors. The Foundation currently has no plans to speculate in cryptocurrency or other assets.
Finally, it is important that the Foundation adds value to the Sia platform well in excess of the inflation introduced by the block subsidy. For this reason, the Foundation intends to provably burn, on a quarterly basis, any coins that it cannot allocate towards any justifiable expense. In other words, coins will be burned whenever doing so provides greater value to the platform than any other use. Furthermore, the Foundation will cap its SC treasury at 5% of the total supply, and will cap its USD treasury at 4 years’ worth of predicted expenses.
 
Addendum: Hardfork Timeline
We would like to see this proposal finalized and accepted by the community no later than September 30th. A new version of siad, implementing the hardfork, will be released no later than October 15th. The hardfork will activate at block 293220, which is expected to occur around 12pm EST on January 1st, 2021.
 
Addendum: Inflation specifics
The total supply of siacoins as of January 1st, 2021 will be approximately 45.243 GS. The initial subsidy of 1.57 GS thus increases the supply by 3.47%, and the total annual inflation in 2021 will be at most 10.4% (if zero coins are burned). In 2022, total annual inflation will be at most 6.28%, and will steadily decrease in subsequent years.
 

Conclusion

We see the establishment of the Foundation as an important step in the maturation of the Sia project. It provides the ecosystem with a sustainable source of funding that can be exclusively directed towards achieving Sia's ambitious goals. Compared to other projects with far deeper pockets, Sia has always punched above its weight; once we're on equal footing, there's no telling what we'll be able to achieve.
Nevertheless, we do not propose this change lightly, and have taken pains to ensure that the Foundation will act in accordance with the ideals that this community shares. It will operate transparently, keep inflation to a minimum, and respect the user's fundamental role in decentralized systems. We hope that everyone in the community will consider this proposal carefully, and look forward to a productive discussion.
submitted by lukechampine to siacoin [link] [comments]

Why Bitcoin is Superior to Gold

There is a constant war being fought between goldbugs, like Peter Schiff, and Bitcoin enthusiasts so I decided to make an outline, with links, comparing and contrasting gold and Bitcoin. I made this in November of 2019 (thus the information therein is based on figures from that time) but, being scatter brained, neglected to post this for the Bitcoin community to see. The yardsticks I used to compare the two assets included the following: shipping/transactions costs, storage costs, censorship factor, settlement time, stock to flow, blockchain vs clearing house, validation, etc. I will also touch on Roosevelt's gold confiscation executive order in 1933, transporting gold during the Spanish Civil War in 1936, and the hypothetical cost for Venezuela to repatriate its gold more recently.
I will provide a brief summary first then follow that with the outline I made. This information can be used as a tool for the Bitcoin community to combat some of the silly rhetoric coming from goldbugs such as Peter Schiff and James Rickards. I would like to make it clear, however, that I am not against gold and think that it performed its role as money very well in a technologically inferior era, namely Victorian times but I think Bitcoin performs the functions of money better than gold does in the current environment.
I have been looking to make a contribution to the Bitcoin community and I hope this is a useful and educational tool for everyone who reads this.
Summary:
Shipping/transaction costs: 100 ounces of gold could be shipped for 315 dollars; the comparable dollar value in Bitcoin could be sent for 35 dollars using a non-segwit address. Using historical precendent, it would cost an estimated $32,997,989 to transport $1 billion in gold using the 3.3% fee that the Soviets charged the Spaniards in 1936; a $1 billion Bitcoin transaction moved for $690 last year by comparison. Please note that the only historic example we can provide for moving enormous sums of gold was when the government of Spain transported gold to Moscow during the Spanish Civil War in 1936. More information on this topic will be found in the notes section.
Storage costs: 100 ounces of gold would require $451 per year to custody while the equivalent value of Bitcoin in dollar terms could be stored for the cost of a Ledger Nano S, $59.99. $1 billion USD value of gold would cost $2,900,000 per year while an Armory set up that is more secure would run you the cost of a laptop, $200-300.
Censorship factor: Gold must pass through a 3rd party whenever it is shipped, whether for a transaction or for personal transportation. Gold will typically have to be declared and a customs duty may be imposed when crossing international borders. The key take-away is gatekeepers (customs) can halt movement of gold thus making transactions difficult. $46,000 of gold was seized in India despite the smugglers hiding it in their rectums.
Settlement time: Shipping gold based on 100 ounces takes anywhere from 3-10 days while Bitcoin transactions clear in roughly 10 minutes depending on network congestion and fee size.
Historic confiscation: Franklin Roosevelt confiscated and debased the paper value of gold in 1933 with Executive Order 6102. Since gold is physical in nature and value dense, it is often stored in custodial vaults like banks and so forth which act as a honeypot for rapacious governments.
Stock to flow: Plan B's stock to flow model has become a favorite on twitter. Stock to flow measures the relationship between the total stock of an asset against the amount that is produced in a given year. Currently gold still has the highest value at 62 while Bitcoin sits at 50 in 2nd place. Bitcoin will overtake gold in 2024 after the next halving.
Blockchain vs clearing house: gold payments historically passed through a 3rd party (clearinghouse) in order to be validated while Bitcoin transactions can be self validated through the use of a node.
Key Takeaway from above- Bitcoin is vastly superior to gold in terms of cost, speed, and censorship resistance. One could theoretically carry around an enormous sum of Bitcoin on a cold card while the equivalent dollar value of gold would require a wheelbarrow...and create an enormous target on the back of the transporter. With the exception of the stock to flow ratio (which will flip in Bitcoin's favor soon), Bitcoin is superior to gold by all metrics covered.
Notes:
Shipping/transaction costs
Gold
100 oz = 155,500. 45 x 7 = $315 to ship 100 oz gold.
https://seekingalpha.com/instablog/839735-katchum/2547831-how-much-does-it-cost-to-ship-silver-and-gold
https://www.coininvest.com/en/shipping-prices/
211 tonnes Venezuela; 3.3% of $10.5 billion = 346,478,880 or 32,997,989/billion usd
http://blogs.reuters.com/felix-salmon/2011/08/23/how-to-get-12-billion-of-gold-to-venezuela/ (counter party risk; maduro; quotes from article)
Bitcoin
18 bitcoin equivalent value; 35 USD with legacy address
https://blockexplorer.com/
https://bitcoinfees.info/
1 billion; $690 dollars
https://arstechnica.com/tech-policy/2019/09/someone-moved-1-billion-in-a-single-bitcoin-transaction/
Storage costs
Gold
.29% annually; https://sdbullion.com/gold-silver-storage
100 oz – $451/year
$1 billion USD value – $2,900,000/year
Bitcoin
Ledger Nano S - $59.00 (for less bitcoin)
https://shop.ledger.com/products/ledger-nano-s/transparent?flow_country=USA&gclid=EAIaIQobChMI3ILV5O-Z5wIVTtbACh1zTAwqEAQYASABEgJ5SPD_BwE
Armory - $200-300 cost of laptop for setup
https://www.bitcoinarmory.com/
Censorship factor (must pass through 3rd party)
Varies by country
Gold will typically have to be declared and a customs duty may be imposed
Key take-away is gatekeepers (customs) can halt movement of gold thus making transactions difficult
$46,000 seized in India
https://www.foxnews.com/travel/indian-airport-stops-29-passengers-smuggling-gold-in-their-rectums
Settlement time
Gold
For 100 oz transaction by USPS 3-10 days (must pass through 3rd party)
Bitcoin
Roughly 10 minutes to be included in next block
Historic confiscation-roosevelt 1933
Executive Order 6102 (forced spending, fed could ban cash, go through and get quotes)
https://en.wikipedia.org/wiki/Executive_Order_6102
“The stated reason for the order was that hard times had caused "hoarding" of gold, stalling economic growth and making the depression worse”
Stock to flow; https://medium.com/@100trillionUSD/modeling-bitcoins-value-with-scarcity-91fa0fc03e25 (explain what it is and use charts in article)
Gold; SF of 62
Bitcoin; SF of 25 but will double to 50 after May (and to 100 in four years)
Blockchain vs clearing house
Transactions can be validated by running a full node vs. third party settlement
Validation
Gold; https://www.goldismoney2.com/threads/cost-to-assay.6732/
(Read some responses)
Bitcoin
Cost of electricity to run a full node
Breaking down Venezuela conundrum; http://blogs.reuters.com/felix-salmon/2011/08/23/how-to-get-12-billion-of-gold-to-venezuela/
“The last (and only) known case of this kind of quantity of gold being transported across state lines took place almost exactly 75 years ago, in 1936, when the government of Spain removed 560 tons of gold from Madrid to Moscow as the armies of Francisco Franco approached. Most of the gold was exchanged for Russian weaponry, with the Soviet Union keeping 2.1% of the funds in the form of commissions and brokerage, and an additional 1.2% in the form of transport, deposit, melting, and refining expenses.”
“Venezuela would need to transport the gold in several trips, traders said, since the high value of gold means it would be impossible to insure a single aircraft carrying 211 tonnes. It could take about 40 shipments to move the gold back to Caracas, traders estimated. “It’s going to be quite a task. Logistically, I’m not sure if the central bank realises the magnitude of the task ahead of them,” said one senior gold banker.”
“So maybe Chávez intends to take matters into his own hands, and just sail the booty back to Venezuela on one of his own naval ships. Again, the theft risk is obvious — seamen can be greedy too — and this time there would be no insurance. Chávez is pretty crazy, but I don’t think he’d risk $12 billion that way.”
“Which leaves one final alternative. Gold is fungible, and people are actually willing to pay a premium to buy gold which is sitting in the Bank of England’s ultra-secure vaults. So why bother transporting that gold at all? Venezuela could enter into an intercontinental repo transaction, where it sells its gold in the Bank of England to some counterparty, and then promises to buy it all back at a modest discount, on condition that it’s physically delivered to the Venezuelan central bank in Caracas. It would then be up to the counterparty to work out how to get 211 tons of gold to Caracas by a certain date. That gold could be sourced anywhere in the world, and transported in any conceivable manner — being much less predictable and transparent, those shipments would also be much harder to hijack. How much of a discount would a counterparty require to enter into this kind of transaction? Much more than 3.3%, is my guess. And again, it’s not entirely clear who would even be willing to entertain the idea. Glencore, perhaps?”
“But here’s one last idea: why doesn’t Chávez crowdsource the problem? He could simply open a gold window at the Banco Central de Venezuela, where anybody at all could deliver standard gold bars. In return, the central bank would transfer to that person an equal number of gold bars in the custody of the Bank of England, plus a modest bounty of say 2% — that’s over $15,000 per 400-ounce bar, at current rates. It would take a little while, but eventually the gold would start trickling in: if you’re willing to pay a constant premium of 2% over the market price for a good, you can be sure that the good in question will ultimately find its way to your door. And the 2% cost of acquiring all that gold would surely be much lower than the cost of insuring and shipping it from England. It would be an elegant market-based solution to an artificial and ideologically-driven problem; I daresay Chávez might even chuckle at the irony of it. He’d just need to watch out for a rise in Andean banditry, as thieves tried to steal the bars on their disparate journeys into Venezuela.”
submitted by cornish_roots to Bitcoin [link] [comments]

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

Dragonchain Great Reddit Scaling Bake-Off Public Proposal

Dragonchain Great Reddit Scaling Bake-Off Public Proposal

Dragonchain Public Proposal TL;DR:

Dragonchain has demonstrated twice Reddit’s entire total daily volume (votes, comments, and posts per Reddit 2019 Year in Review) in a 24-hour demo on an operational network. Every single transaction on Dragonchain is decentralized immediately through 5 levels of Dragon Net, and then secured with combined proof on Bitcoin, Ethereum, Ethereum Classic, and Binance Chain, via Interchain. At the time, in January 2020, the entire cost of the demo was approximately $25K on a single system (transaction fees locked at $0.0001/txn). With current fees (lowest fee $0.0000025/txn), this would cost as little as $625.
Watch Joe walk through the entire proposal and answer questions on YouTube.
This proposal is also available on the Dragonchain blog.

Hello Reddit and Ethereum community!

I’m Joe Roets, Founder & CEO of Dragonchain. When the team and I first heard about The Great Reddit Scaling Bake-Off we were intrigued. We believe we have the solutions Reddit seeks for its community points system and we have them at scale.
For your consideration, we have submitted our proposal below. The team at Dragonchain and I welcome and look forward to your technical questions, philosophical feedback, and fair criticism, to build a scaling solution for Reddit that will empower its users. Because our architecture is unlike other blockchain platforms out there today, we expect to receive many questions while people try to grasp our project. I will answer all questions here in this thread on Reddit, and I've answered some questions in the stream on YouTube.
We have seen good discussions so far in the competition. We hope that Reddit’s scaling solution will emerge from The Great Reddit Scaling Bake-Off and that Reddit will have great success with the implementation.

Executive summary

Dragonchain is a robust open source hybrid blockchain platform that has proven to withstand the passing of time since our inception in 2014. We have continued to evolve to harness the scalability of private nodes, yet take full advantage of the security of public decentralized networks, like Ethereum. We have a live, operational, and fully functional Interchain network integrating Bitcoin, Ethereum, Ethereum Classic, and ~700 independent Dragonchain nodes. Every transaction is secured to Ethereum, Bitcoin, and Ethereum Classic. Transactions are immediately usable on chain, and the first decentralization is seen within 20 seconds on Dragon Net. Security increases further to public networks ETH, BTC, and ETC within 10 minutes to 2 hours. Smart contracts can be written in any executable language, offering full freedom to existing developers. We invite any developer to watch the demo, play with our SDK’s, review open source code, and to help us move forward. Dragonchain specializes in scalable loyalty & rewards solutions and has built a decentralized social network on chain, with very affordable transaction costs. This experience can be combined with the insights Reddit and the Ethereum community have gained in the past couple of months to roll out the solution at a rapid pace.

Response and PoC

In The Great Reddit Scaling Bake-Off post, Reddit has asked for a series of demonstrations, requirements, and other considerations. In this section, we will attempt to answer all of these requests.

Live Demo

A live proof of concept showing hundreds of thousands of transactions
On Jan 7, 2020, Dragonchain hosted a 24-hour live demonstration during which a quarter of a billion (250 million+) transactions executed fully on an operational network. Every single transaction on Dragonchain is decentralized immediately through 5 levels of Dragon Net, and then secured with combined proof on Bitcoin, Ethereum, Ethereum Classic, and Binance Chain, via Interchain. This means that every single transaction is secured by, and traceable to these networks. An attack on this system would require a simultaneous attack on all of the Interchained networks.
24 hours in 4 minutes (YouTube):
24 hours in 4 minutes
The demonstration was of a single business system, and any user is able to scale this further, by running multiple systems simultaneously. Our goals for the event were to demonstrate a consistent capacity greater than that of Visa over an extended time period.
Tooling to reproduce our demo is available here:
https://github.com/dragonchain/spirit-bomb

Source Code

Source code (for on & off-chain components as well tooling used for the PoC). The source code does not have to be shared publicly, but if Reddit decides to use a particular solution it will need to be shared with Reddit at some point.

Scaling

How it works & scales

Architectural Scaling

Dragonchain’s architecture attacks the scalability issue from multiple angles. Dragonchain is a hybrid blockchain platform, wherein every transaction is protected on a business node to the requirements of that business or purpose. A business node may be held completely private or may be exposed or replicated to any level of exposure desired.
Every node has its own blockchain and is independently scalable. Dragonchain established Context Based Verification as its consensus model. Every transaction is immediately usable on a trust basis, and in time is provable to an increasing level of decentralized consensus. A transaction will have a level of decentralization to independently owned and deployed Dragonchain nodes (~700 nodes) within seconds, and full decentralization to BTC and ETH within minutes or hours. Level 5 nodes (Interchain nodes) function to secure all transactions to public or otherwise external chains such as Bitcoin and Ethereum. These nodes scale the system by aggregating multiple blocks into a single Interchain transaction on a cadence. This timing is configurable based upon average fees for each respective chain. For detailed information about Dragonchain’s architecture, and Context Based Verification, please refer to the Dragonchain Architecture Document.

Economic Scaling

An interesting feature of Dragonchain’s network consensus is its economics and scarcity model. Since Dragon Net nodes (L2-L4) are independent staking nodes, deployment to cloud platforms would allow any of these nodes to scale to take on a large percentage of the verification work. This is great for scalability, but not good for the economy, because there is no scarcity, and pricing would develop a downward spiral and result in fewer verification nodes. For this reason, Dragonchain uses TIME as scarcity.
TIME is calculated as the number of Dragons held, multiplied by the number of days held. TIME influences the user’s access to features within the Dragonchain ecosystem. It takes into account both the Dragon balance and length of time each Dragon is held. TIME is staked by users against every verification node and dictates how much of the transaction fees are awarded to each participating node for every block.
TIME also dictates the transaction fee itself for the business node. TIME is staked against a business node to set a deterministic transaction fee level (see transaction fee table below in Cost section). This is very interesting in a discussion about scaling because it guarantees independence for business implementation. No matter how much traffic appears on the entire network, a business is guaranteed to not see an increased transaction fee rate.

Scaled Deployment

Dragonchain uses Docker and Kubernetes to allow the use of best practices traditional system scaling. Dragonchain offers managed nodes with an easy to use web based console interface. The user may also deploy a Dragonchain node within their own datacenter or favorite cloud platform. Users have deployed Dragonchain nodes on-prem on Amazon AWS, Google Cloud, MS Azure, and other hosting platforms around the world. Any executable code, anything you can write, can be written into a smart contract. This flexibility is what allows us to say that developers with no blockchain experience can use any code language to access the benefits of blockchain. Customers have used NodeJS, Python, Java, and even BASH shell script to write smart contracts on Dragonchain.
With Docker containers, we achieve better separation of concerns, faster deployment, higher reliability, and lower response times.
We chose Kubernetes for its self-healing features, ability to run multiple services on one server, and its large and thriving development community. It is resilient, scalable, and automated. OpenFaaS allows us to package smart contracts as Docker images for easy deployment.
Contract deployment time is now bounded only by the size of the Docker image being deployed but remains fast even for reasonably large images. We also take advantage of Docker’s flexibility and its ability to support any language that can run on x86 architecture. Any image, public or private, can be run as a smart contract using Dragonchain.

Flexibility in Scaling

Dragonchain’s architecture considers interoperability and integration as key features. From inception, we had a goal to increase adoption via integration with real business use cases and traditional systems.
We envision the ability for Reddit, in the future, to be able to integrate alternate content storage platforms or other financial services along with the token.
  • LBRY - To allow users to deploy content natively to LBRY
  • MakerDAO to allow users to lend small amounts backed by their Reddit community points.
  • STORJ/SIA to allow decentralized on chain storage of portions of content. These integrations or any other are relatively easy to integrate on Dragonchain with an Interchain implementation.

Cost

Cost estimates (on-chain and off-chain) For the purpose of this proposal, we assume that all transactions are on chain (posts, replies, and votes).
On the Dragonchain network, transaction costs are deterministic/predictable. By staking TIME on the business node (as described above) Reddit can reduce transaction costs to as low as $0.0000025 per transaction.
Dragonchain Fees Table

Getting Started

How to run it
Building on Dragonchain is simple and requires no blockchain experience. Spin up a business node (L1) in our managed environment (AWS), run it in your own cloud environment, or on-prem in your own datacenter. Clear documentation will walk you through the steps of spinning up your first Dragonchain Level 1 Business node.
Getting started is easy...
  1. Download Dragonchain’s dctl
  2. Input three commands into a terminal
  3. Build an image
  4. Run it
More information can be found in our Get started documents.

Architecture
Dragonchain is an open source hybrid platform. Through Dragon Net, each chain combines the power of a public blockchain (like Ethereum) with the privacy of a private blockchain.
Dragonchain organizes its network into five separate levels. A Level 1, or business node, is a totally private blockchain only accessible through the use of public/private keypairs. All business logic, including smart contracts, can be executed on this node directly and added to the chain.
After creating a block, the Level 1 business node broadcasts a version stripped of sensitive private data to Dragon Net. Three Level 2 Validating nodes validate the transaction based on guidelines determined from the business. A Level 3 Diversity node checks that the level 2 nodes are from a diverse array of locations. A Level 4 Notary node, hosted by a KYC partner, then signs the validation record received from the Level 3 node. The transaction hash is ledgered to the Level 5 public chain to take advantage of the hash power of massive public networks.
Dragon Net can be thought of as a “blockchain of blockchains”, where every level is a complete private blockchain. Because an L1 can send to multiple nodes on a single level, proof of existence is distributed among many places in the network. Eventually, proof of existence reaches level 5 and is published on a public network.

API Documentation

APIs (on chain & off)

SDK Source

Nobody’s Perfect

Known issues or tradeoffs
  • Dragonchain is open source and even though the platform is easy enough for developers to code in any language they are comfortable with, we do not have so large a developer community as Ethereum. We would like to see the Ethereum developer community (and any other communities) become familiar with our SDK’s, our solutions, and our platform, to unlock the full potential of our Ethereum Interchain. Long ago we decided to prioritize both Bitcoin and Ethereum Interchains. We envision an ecosystem that encompasses different projects to give developers the ability to take full advantage of all the opportunities blockchain offers to create decentralized solutions not only for Reddit but for all of our current platforms and systems. We believe that together we will take the adoption of blockchain further. We currently have additional Interchain with Ethereum Classic. We look forward to Interchain with other blockchains in the future. We invite all blockchains projects who believe in decentralization and security to Interchain with Dragonchain.
  • While we only have 700 nodes compared to 8,000 Ethereum and 10,000 Bitcoin nodes. We harness those 18,000 nodes to scale to extremely high levels of security. See Dragonchain metrics.
  • Some may consider the centralization of Dragonchain’s business nodes as an issue at first glance, however, the model is by design to protect business data. We do not consider this a drawback as these nodes can make any, none, or all data public. Depending upon the implementation, every subreddit could have control of its own business node, for potential business and enterprise offerings, bringing new alternative revenue streams to Reddit.

Costs and resources

Summary of cost & resource information for both on-chain & off-chain components used in the PoC, as well as cost & resource estimates for further scaling. If your PoC is not on mainnet, make note of any mainnet caveats (such as congestion issues).
Every transaction on the PoC system had a transaction fee of $0.0001 (one-hundredth of a cent USD). At 256MM transactions, the demo cost $25,600. With current operational fees, the same demonstration would cost $640 USD.
For the demonstration, to achieve throughput to mimic a worldwide payments network, we modeled several clients in AWS and 4-5 business nodes to handle the traffic. The business nodes were tuned to handle higher throughput by adjusting memory and machine footprint on AWS. This flexibility is valuable to implementing a system such as envisioned by Reddit. Given that Reddit’s daily traffic (posts, replies, and votes) is less than half that of our demo, we would expect that the entire Reddit system could be handled on 2-5 business nodes using right-sized containers on AWS or similar environments.
Verification was accomplished on the operational Dragon Net network with over 700 independently owned verification nodes running around the world at no cost to the business other than paid transaction fees.

Requirements

Scaling

This PoC should scale to the numbers below with minimal costs (both on & off-chain). There should also be a clear path to supporting hundreds of millions of users.
Over a 5 day period, your scaling PoC should be able to handle:
*100,000 point claims (minting & distributing points) *25,000 subscriptions *75,000 one-off points burning *100,000 transfers
During Dragonchain’s 24 hour demo, the above required numbers were reached within the first few minutes.
Reddit’s total activity is 9000% more than Ethereum’s total transaction level. Even if you do not include votes, it is still 700% more than Ethereum’s current volume. Dragonchain has demonstrated that it can handle 250 million transactions a day, and it’s architecture allows for multiple systems to work at that level simultaneously. In our PoC, we demonstrate double the full capacity of Reddit, and every transaction was proven all the way to Bitcoin and Ethereum.
Reddit Scaling on Ethereum

Decentralization

Solutions should not depend on any single third-party provider. We prefer solutions that do not depend on specific entities such as Reddit or another provider, and solutions with no single point of control or failure in off-chain components but recognize there are numerous trade-offs to consider
Dragonchain’s architecture calls for a hybrid approach. Private business nodes hold the sensitive data while the validation and verification of transactions for the business are decentralized within seconds and secured to public blockchains within 10 minutes to 2 hours. Nodes could potentially be controlled by owners of individual subreddits for more organic decentralization.
  • Billing is currently centralized - there is a path to federation and decentralization of a scaled billing solution.
  • Operational multi-cloud
  • Operational on-premises capabilities
  • Operational deployment to any datacenter
  • Over 700 independent Community Verification Nodes with proof of ownership
  • Operational Interchain (Interoperable to Bitcoin, Ethereum, and Ethereum Classic, open to more)

Usability Scaling solutions should have a simple end user experience.

Users shouldn't have to maintain any extra state/proofs, regularly monitor activity, keep track of extra keys, or sign anything other than their normal transactions
Dragonchain and its customers have demonstrated extraordinary usability as a feature in many applications, where users do not need to know that the system is backed by a live blockchain. Lyceum is one of these examples, where the progress of academy courses is being tracked, and successful completion of courses is rewarded with certificates on chain. Our @Save_The_Tweet bot is popular on Twitter. When used with one of the following hashtags - #please, #blockchain, #ThankYou, or #eternalize the tweet is saved through Eternal to multiple blockchains. A proof report is available for future reference. Other examples in use are DEN, our decentralized social media platform, and our console, where users can track their node rewards, view their TIME, and operate a business node.
Examples:

Transactions complete in a reasonable amount of time (seconds or minutes, not hours or days)
All transactions are immediately usable on chain by the system. A transaction begins the path to decentralization at the conclusion of a 5-second block when it gets distributed across 5 separate community run nodes. Full decentralization occurs within 10 minutes to 2 hours depending on which interchain (Bitcoin, Ethereum, or Ethereum Classic) the transaction hits first. Within approximately 2 hours, the combined hash power of all interchained blockchains secures the transaction.

Free to use for end users (no gas fees, or fixed/minimal fees that Reddit can pay on their behalf)
With transaction pricing as low as $0.0000025 per transaction, it may be considered reasonable for Reddit to cover transaction fees for users.
All of Reddit's Transactions on Blockchain (month)
Community points can be earned by users and distributed directly to their Reddit account in batch (as per Reddit minting plan), and allow users to withdraw rewards to their Ethereum wallet whenever they wish. Withdrawal fees can be paid by either user or Reddit. This model has been operating inside the Dragonchain system since 2018, and many security and financial compliance features can be optionally added. We feel that this capability greatly enhances user experience because it is seamless to a regular user without cryptocurrency experience, yet flexible to a tech savvy user. With regard to currency or token transactions, these would occur on the Reddit network, verified to BTC and ETH. These transactions would incur the $0.0000025 transaction fee. To estimate this fee we use the monthly active Reddit users statista with a 60% adoption rate and an estimated 10 transactions per month average resulting in an approximate $720 cost across the system. Reddit could feasibly incur all associated internal network charges (mining/minting, transfer, burn) as these are very low and controllable fees.
Reddit Internal Token Transaction Fees

Reddit Ethereum Token Transaction Fees
When we consider further the Ethereum fees that might be incurred, we have a few choices for a solution.
  1. Offload all Ethereum transaction fees (user withdrawals) to interested users as they wish to withdraw tokens for external use or sale.
  2. Cover Ethereum transaction fees by aggregating them on a timed schedule. Users would request withdrawal (from Reddit or individual subreddits), and they would be transacted on the Ethereum network every hour (or some other schedule).
  3. In a combination of the above, customers could cover aggregated fees.
  4. Integrate with alternate Ethereum roll up solutions or other proposals to aggregate minting and distribution transactions onto Ethereum.

Bonus Points

Users should be able to view their balances & transactions via a blockchain explorer-style interface
From interfaces for users who have no knowledge of blockchain technology to users who are well versed in blockchain terms such as those present in a typical block explorer, a system powered by Dragonchain has flexibility on how to provide balances and transaction data to users. Transactions can be made viewable in an Eternal Proof Report, which displays raw data along with TIME staking information and traceability all the way to Bitcoin, Ethereum, and every other Interchained network. The report shows fields such as transaction ID, timestamp, block ID, multiple verifications, and Interchain proof. See example here.
Node payouts within the Dragonchain console are listed in chronological order and can be further seen in either Dragons or USD. See example here.
In our social media platform, Dragon Den, users can see, in real-time, their NRG and MTR balances. See example here.
A new influencer app powered by Dragonchain, Raiinmaker, breaks down data into a user friendly interface that shows coin portfolio, redeemed rewards, and social scores per campaign. See example here.

Exiting is fast & simple
Withdrawing funds on Dragonchain’s console requires three clicks, however, withdrawal scenarios with more enhanced security features per Reddit’s discretion are obtainable.

Interoperability Compatibility with third party apps (wallets/contracts/etc) is necessary.
Proven interoperability at scale that surpasses the required specifications. Our entire platform consists of interoperable blockchains connected to each other and traditional systems. APIs are well documented. Third party permissions are possible with a simple smart contract without the end user being aware. No need to learn any specialized proprietary language. Any code base (not subsets) is usable within a Docker container. Interoperable with any blockchain or traditional APIs. We’ve witnessed relatively complex systems built by engineers with no blockchain or cryptocurrency experience. We’ve also demonstrated the creation of smart contracts within minutes built with BASH shell and Node.js. Please see our source code and API documentation.

Scaling solutions should be extensible and allow third parties to build on top of it Open source and extensible
APIs should be well documented and stable

Documentation should be clear and complete
For full documentation, explore our docs, SDK’s, Github repo’s, architecture documents, original Disney documentation, and other links or resources provided in this proposal.

Third-party permissionless integrations should be possible & straightforward Smart contracts are Docker based, can be written in any language, use full language (not subsets), and can therefore be integrated with any system including traditional system APIs. Simple is better. Learning an uncommon or proprietary language should not be necessary.
Advanced knowledge of mathematics, cryptography, or L2 scaling should not be required. Compatibility with common utilities & toolchains is expected.
Dragonchain business nodes and smart contracts leverage Docker to allow the use of literally any language or executable code. No proprietary language is necessary. We’ve witnessed relatively complex systems built by engineers with no blockchain or cryptocurrency experience. We’ve also demonstrated the creation of smart contracts within minutes built with BASH shell and Node.js.

Bonus

Bonus Points: Show us how it works. Do you have an idea for a cool new use case for Community Points? Build it!

TIME

Community points could be awarded to Reddit users based upon TIME too, whereas the longer someone is part of a subreddit, the more community points someone naturally gained, even if not actively commenting or sharing new posts. A daily login could be required for these community points to be credited. This grants awards to readers too and incentivizes readers to create an account on Reddit if they browse the website often. This concept could also be leveraged to provide some level of reputation based upon duration and consistency of contribution to a community subreddit.

Dragon Den

Dragonchain has already built a social media platform that harnesses community involvement. Dragon Den is a decentralized community built on the Dragonchain blockchain platform. Dragon Den is Dragonchain’s answer to fake news, trolling, and censorship. It incentivizes the creation and evaluation of quality content within communities. It could be described as being a shareholder of a subreddit or Reddit in its entirety. The more your subreddit is thriving, the more rewarding it will be. Den is currently in a public beta and in active development, though the real token economy is not live yet. There are different tokens for various purposes. Two tokens are Lair Ownership Rights (LOR) and Lair Ownership Tokens (LOT). LOT is a non-fungible token for ownership of a specific Lair. LOT will only be created and converted from LOR.
Energy (NRG) and Matter (MTR) work jointly. Your MTR determines how much NRG you receive in a 24-hour period. Providing quality content, or evaluating content will earn MTR.

Security. Users have full ownership & control of their points.
All community points awarded based upon any type of activity or gift, are secured and provable to all Interchain networks (currently BTC, ETH, ETC). Users are free to spend and withdraw their points as they please, depending on the features Reddit wants to bring into production.

Balances and transactions cannot be forged, manipulated, or blocked by Reddit or anyone else
Users can withdraw their balance to their ERC20 wallet, directly through Reddit. Reddit can cover the fees on their behalf, or the user covers this with a portion of their balance.

Users should own their points and be able to get on-chain ERC20 tokens without permission from anyone else
Through our console users can withdraw their ERC20 rewards. This can be achieved on Reddit too. Here is a walkthrough of our console, though this does not show the quick withdrawal functionality, a user can withdraw at any time. https://www.youtube.com/watch?v=aNlTMxnfVHw

Points should be recoverable to on-chain ERC20 tokens even if all third-parties involved go offline
If necessary, signed transactions from the Reddit system (e.g. Reddit + Subreddit) can be sent to the Ethereum smart contract for minting.

A public, third-party review attesting to the soundness of the design should be available
To our knowledge, at least two large corporations, including a top 3 accounting firm, have conducted positive reviews. These reviews have never been made public, as Dragonchain did not pay or contract for these studies to be released.

Bonus points
Public, third-party implementation review available or in progress
See above

Compatibility with HSMs & hardware wallets
For the purpose of this proposal, all tokenization would be on the Ethereum network using standard token contracts and as such, would be able to leverage all hardware wallet and Ethereum ecosystem services.

Other Considerations

Minting/distributing tokens is not performed by Reddit directly
This operation can be automated by smart contract on Ethereum. Subreddits can if desired have a role to play.

One off point burning, as well as recurring, non-interactive point burning (for subreddit memberships) should be possible and scalable
This is possible and scalable with interaction between Dragonchain Reddit system and Ethereum token contract(s).

Fully open-source solutions are strongly preferred
Dragonchain is fully open source (see section on Disney release after conclusion).

Conclusion

Whether it is today, or in the future, we would like to work together to bring secure flexibility to the highest standards. It is our hope to be considered by Ethereum, Reddit, and other integrative solutions so we may further discuss the possibilities of implementation. In our public demonstration, 256 million transactions were handled in our operational network on chain in 24 hours, for the low cost of $25K, which if run today would cost $625. Dragonchain’s interoperable foundation provides the atmosphere necessary to implement a frictionless community points system. Thank you for your consideration of our proposal. We look forward to working with the community to make something great!

Disney Releases Blockchain Platform as Open Source

The team at Disney created the Disney Private Blockchain Platform. The system was a hybrid interoperable blockchain platform for ledgering and smart contract development geared toward solving problems with blockchain adoption and usability. All objective evaluation would consider the team’s output a success. We released a list of use cases that we explored in some capacity at Disney, and our input on blockchain standardization as part of our participation in the W3C Blockchain Community Group.
https://lists.w3.org/Archives/Public/public-blockchain/2016May/0052.html

Open Source

In 2016, Roets proposed to release the platform as open source to spread the technology outside of Disney, as others within the W3C group were interested in the solutions that had been created inside of Disney.
Following a long process, step by step, the team met requirements for release. Among the requirements, the team had to:
  • Obtain VP support and approval for the release
  • Verify ownership of the software to be released
  • Verify that no proprietary content would be released
  • Convince the organization that there was a value to the open source community
  • Convince the organization that there was a value to Disney
  • Offer the plan for ongoing maintenance of the project outside of Disney
  • Itemize competing projects
  • Verify no conflict of interest
  • Preferred license
  • Change the project name to not use the name Disney, any Disney character, or any other associated IP - proposed Dragonchain - approved
  • Obtain legal approval
  • Approval from corporate, parks, and other business units
  • Approval from multiple Disney patent groups Copyright holder defined by Disney (Disney Connected and Advanced Technologies)
  • Trademark searches conducted for the selected name Dragonchain
  • Obtain IT security approval
  • Manual review of OSS components conducted
  • OWASP Dependency and Vulnerability Check Conducted
  • Obtain technical (software) approval
  • Offer management, process, and financial plans for the maintenance of the project.
  • Meet list of items to be addressed before release
  • Remove all Disney project references and scripts
  • Create a public distribution list for email communications
  • Remove Roets’ direct and internal contact information
  • Create public Slack channel and move from Disney slack channels
  • Create proper labels for issue tracking
  • Rename internal private Github repository
  • Add informative description to Github page
  • Expand README.md with more specific information
  • Add information beyond current “Blockchains are Magic”
  • Add getting started sections and info on cloning/forking the project
  • Add installation details
  • Add uninstall process
  • Add unit, functional, and integration test information
  • Detail how to contribute and get involved
  • Describe the git workflow that the project will use
  • Move to public, non-Disney git repository (Github or Bitbucket)
  • Obtain Disney Open Source Committee approval for release
On top of meeting the above criteria, as part of the process, the maintainer of the project had to receive the codebase on their own personal email and create accounts for maintenance (e.g. Github) with non-Disney accounts. Given the fact that the project spanned multiple business units, Roets was individually responsible for its ongoing maintenance. Because of this, he proposed in the open source application to create a non-profit organization to hold the IP and maintain the project. This was approved by Disney.
The Disney Open Source Committee approved the application known as OSSRELEASE-10, and the code was released on October 2, 2016. Disney decided to not issue a press release.
Original OSSRELASE-10 document

Dragonchain Foundation

The Dragonchain Foundation was created on January 17, 2017. https://den.social/l/Dragonchain/24130078352e485d96d2125082151cf0/dragonchain-and-disney/
submitted by j0j0r0 to ethereum [link] [comments]

Symbol Platform by NEM - Tokenomics

First of all, remember that, you can get 1 XYM for 1 NEM you have.
Tokenomics
The Symbol public chain is a self-sustaining economic ecosystem involving node operators, harvesters, investors, users, and the XYM token. In this way, it’s similar to many decentralized blockchains, but there are important differences that make it easier for anyone to earn rewards. Here are the basics of the system.
XYM Supply and Inflation
XYM has a fixed maximum supply of approximately 9 billion tokens. At public chain release, the supply will consist of about 7.3 billion XYM, allocated to users based on their holdings of XEM on the NEM blockchain. Another 1.7 billion XYM will be created as inflationary rewards over time. The inflation rate is closely mapped to that of bitcoin, extending out over the next 100 years. Similar to mining rewards, Symbol’s rewards will be released to each block creator, but based on a POS+ (Proof of Stake+) system.
Proof of Stake
POS+ lets nodes create blocks based on their XYM stakes, which are holdings. Symbol uses the term harvesting instead of mining. The more tokens held by a node operator, the higher the chances of creating the next block and earning harvesting rewards. POS is a well-known system in the blockchain industry, but Symbol adds some improvements. POS+ calculates a score for each node operator based on the size of their stake AND other factors, such as recent network activity and the stakes that other users may delegate to them (see Delegated Harvesting below.) In this way, POS+ attempts to incentivize usage, competition for low fees, and other desirable behavior. You can read details on how POS+ is calculated in the Symbol whitepaper.
Nodes
Node operators all over the world keep the Symbol protocol robust and decentralized. For keeping the system running, node owners earn rewards from four sources.
Node operators can set up their nodes locally or on cloud services. For details on how to set up a node, refer to the developer documentation.
Block Rewards
Since Symbol’s blocks are confirmed several times per minute, rewards are frequent. Block rewards consist of inflation rewards and transaction fees. The chances of earning a block reward are based mainly on the operator’s XYM stake, as well as other factors like network activity. Both node operators and anyone else with a XYM wallet can earn block rewards.
The higher an account’s XYM balance, the higher the chance of it earning a block reward. Even those who don’t run a node can earn block rewards by delegating their stake to a node.
Delegated Harvesting
XYM owners who don’t operate nodes can also earn block rewards by delegating their stake to a node. Holders who delegate their stake retain full ownership of their coins and never expose their private keys. No funds have ever been lost from delegated harvesting. When delegated harvesters earn a block reward, the node operator who processed it earns 25% and the delegated harvester earns 75%. In this way, a node operator can greatly increase their earned rewards, and all holders can participate in rewards whether or not they run a node.
Transaction Fees
Node operators can set their own minimum fees for which they wish to process transactions. The lower the fees accepted, the more transactions they will be able to process. Generous node operators may even choose to process transactions for free if they wish. This creates competition among node operators.
Node Bonus Program
In order to incentivize stability in the number of nodes and circulating supply after launch, bonus rewards will be paid to node operators who maintain nodes with minimum balances of 1 million, 2 million, or 3 million XYM, with higher bonus rates for each tier. These rewards will draw from a fixed pool of reserves and gradually ramp down over six years.
Total Node Income
To summarize, node operators will earn income from block rewards (inflation + transaction fees) based on their own stakes and a 25% share of delegated stake block rewards. Estimates place these combined node rewards at approximately 5% or 6% for the first year, though this is not guaranteed. Operators can also earn bonuses for maintaining minimum stakes of over 1 million XYM.
Inflation Rate
Symbol’s inflation is mapped to bitcoin’s inflation with one difference. Bitcoin halves its rewards every four years. Symbol also drops its reward rate by half every four years, but instead of a single big drop, these reductions are spaced out to occur every quarter. This gives the same overall inflation as bitcoin, but with a more gradual decline.
Team Reserves
The Symbol Core Team will hold approximately 22% of XYM supply for funding future development, marketing, and partner projects. Historically, Core Team funds have not been used for harvesting and there are no plans to begin, meaning more block rewards available for other harvesters.
https://symbolplatform.com/
submitted by waterbottles4 to nem [link] [comments]

August / September monthly report from v1docq47 (CCS + XRM.RU)

This is my monthly progress report (CCS.html) + XMR.RU).
Below is a list of what has been done and translated into Russian for two months of my work.

Monero Video (YouTube)

The following video posted on Monero Russian Community YouTube Channel.

Weekly News:

Short Q&A about Monero:

Monero into Russian (Translation)

The following articles / guides have been translated into Russian and posted on the XMR.RU website and my Github repository.
Note: If you would like to read the original article in English, then, open the article you are interested in, and at the end of each article you will find a link to the source.

Critical Decentralisation Cluster 36c3 (transcriptions (EN + RU) + translation (RU)):

01 - Monero Introduction (Diego "rehrar" Salazar) | Transcriptions - EN.md) / RU.md) / XMR.RU 02 - RIAT Introduction (parasew) | Transcriptions - EN.md) / RU.md) / XMR.RU 03 - Swiss Cryptoeconomics Assembly (polto, Ome) | Transcriptions - EN.md) / RU.md) / XMR.RU 04 - Namecoin Introduction (Jeremy Rand) | Transcriptions - EN.md) / RU.md) / XMR.RU 05 - Open Hardware developed at FOSSASIA (Mario Behling) | Transcriptions - EN.md) / RU.md) / XMR.RU 06 - Paralelni Polis (Juraj Bednar) | Transcriptions - EN.md) / RU.md) / XMR.RU 07 - Introduction to Replicant (dllud, Denis ‘GNUtoo’ Carikli)​ | Transcriptions - EN.md) / RU.md) / XMR.RU 08 - Open Source Hardware and OSHWA (Drew Fustini) | Transcriptions - EN.md) / RU.md) / XMR.RU 09 - ImplicitCAD (Juila Longtin) | Transcriptions - EN.md) / RU.md) / XMR.RU 10 - Program in Detail | Transcriptions - EN / RU / XMR.RU 11 - about:freedom (Bonnie Mehring, Blipp)​ | Transcriptions - EN.md) / RU.md) / XMR.RU 13 - Funding Models of FOSS (Diego “rehrar” Salazar) | Transcriptions - EN.md) / RU.md) / XMR.RU 14 - The Sharp Forks We Follow​ | Transcriptions - EN / RU / XMR.RU 16 - P2P Trading in Cryptoanarchy | Transcriptions - EN / RU / XMR.RU 17 - Monero’s Adaptive Blockweight Approach to Scaling | Transcriptions - EN / RU / XMR.RU 18 - Nym (Harry Halpin)​ | Transcriptions - EN.md) / RU.md) / XMR.RU 19 - Digital Integrity of the Human Person | Transcriptions - EN / RU / XMR.RU 20 - cyber~Congress (Sergey Simanovsky) | Transcriptions - EN.md) / RU.md) / XMR.RU 21 - KYC & Crypto-AML Tools (polto) | Transcriptions - EN.md) / RU.md) / XMR.RU 22 - Parallel Polis, Temporary Autonomous Zones and Beyond | Transcriptions - EN / RU 23 - MandelBot:HAB - Open Source Ecotecture and Horizontalism | Transcriptions - EN / RU 24 - Adventures and Experiments Adding Namecoin to Tor Browser | Transcriptions - EN / RU 25 - Fair Data Society (Gregor Zavcer) | Transcriptions - EN.md) / RU.md) / XMR.RU 45 - Designing a Communal Computing Interface | Transcriptions - EN / RU / XMR.RU 47 - Hackatoshi’s Flying Circuit | Transcriptions - EN / RU / XMR.RU

Zero to Monero - Second Edition

https://www.overleaf.com/read/hcmqnvgtfmyh - Chapter 00 - Abstract - Chapter 01 - Introduction - Chapter 02 - Basic Concepts - Chapter 03 - Advanced Schnorr-like Signatures

Monero Outreach Articles

Getmonero.org Posts Blog

LocalMonero Articles

Note: You need "Change Language" to Russian - Why Monero Has A Tail Emission - How CLSAG Will Improve Monero's Efficiency - How Monero Solved the Block Size Problem That Plagues Bitcoin - How Ring Signatures Obscure Monero's Outputs - Monero Best Practices for Beginners - Monero Outputs Explained

Monero Meeting logs

CCS Result / Report

Monero News

Other Articles

Pull / Merge Request

Monero Project Translations (Weblate)

Thanks for your support!
submitted by v1docq47 to Monero [link] [comments]

When Will Bitcoin Raise the Block Size Limit? Bitcoin Sidechains & SPV Proofs Blockchain/Bitcoin for beginners 8: Bitcoin addresses, public key hash, P2PKH transactions Bitcoin Block Size: Larger or smaller blocks? #Bitcoin #MCC2019 Luke Dashjr

Waiting for the next block... Unknown: 71.0%: taal.com: 12.9% These blocks are commonly addressed by their block height —the number of blocks between them and the first Bitcoin block (block 0, most commonly known as the genesis block). For example, block 2016 is where difficulty could have first been adjusted. Common And Uncommon Block Chain Forks ¶ Multiple blocks can all have the same block height, as is common when two or more miners each produce a ... The next Bitcoin halving event is due in May 2020. The Bitcoin block reward will halve, rewarding miners with 6.25 BTC for each block. A Short History of Bitcoin Block Size. In mid-2015, the then-lead Bitcoin developer, Gavin Andresen, issued a warning that the Bitcoin block size was an impending issue for the Bitcoin network. Height Age Version Miner Coin Base Text Transactions Block Size (kB) Weight; 654341: 4 minutes ago: 0x20000000: NovaBlock ޠ_/NovaBlock/mm)P mŢ W܁ mO[5$!w h:eqɈnj q'alW Block Size: 873.666 KBytes: Blocks last 24h : 122: Blocks avg. per hour (last 24h) 5: Reward Per Block: 6.25+0.5332 BTC ($88,929.66 USD) next halving @ block 840000 (in 185688 blocks ~ 1276 days) Reward (last 24h) 762.50+65.05 BTC ($10,849,418.32 USD) Fee in Reward (Average Fee Percentage in Total Block Reward) 8.2%: Difficulty: 19.997 T next retarget @ block 657216 (in 2904 blocks ~ 21 days ...

[index] [9677] [34076] [10209] [45397] [25185] [14116] [47585] [14017] [13830] [39628]

When Will Bitcoin Raise the Block Size Limit?

Researcher at Open Bitcoin Privacy Project and developer of BIP47, Justus Ranvier chats with Amanda about implications of artificial scarcity on blockchains,... Stephanie, Andreas and Adam speak first with Bitcoin Foundation Chief Scientist Gavin Andresen about the Bitcoin Block Size debate, where it came from, why it matters and what he thinks we should ... A talk on the Bitcoin block size debate and a discussion of arguments for both larger and smaller block sizes give by Leonhard Weese on 18 November, 2015 at Tuspark's Causeway Bay location in Hong ... The capacity of the bitcoin network is limited by a hard-coded limit inside its protocol. As technology advances, this limit becomes increasingly absurd. When will it be updated to be more ... Luke Dashjr summarises the reasons big blocks are harmful to Bitcoin.

#