Bitcoin Integration With Distributed Hash Tables Idea
Lately, I have been thinking about distributed hash tables, and how to incentivize the nodes who are running and maintaing nodes with Bitcoin. Currently, the basics of the idea: Nodes:
Have bitcoin address associated with them
Keep list of addresses, which have donated to themselves (or all nodes)
Priorize accesses/storing/bandwidth based on how much the requesting client has donated Bitcoins within time
Further priorize storage etc per certain key/value pair so that it keeps track how much buck does it make for storing certain item
Cache keys/values based on who requests/stores them, giving priority access to big donators
Can also serve nodes which haven't donated, however could have bandwidth/request amount/storage limitations
Require authentication of requests via bitcoin address signing, but also can
Send periodically donation transactions to the nodes they primarily want to use/have used
Send the donations from certain bitcoin addresses
Authenticate by singing request with Bitcoin address they send the donations from
Initially there would be a chicken-egg problem, but in the long run the system would probably converge in a way that honest nodes get good storage/bandwidth/etc, while newcomers get limited access with limited bandwidth. Optimally the node would not care whether the data uploader or downloader pays to keep the information in the cloud. It would just keep track how much dough it makes per certain key/value pair. I believe also that incentivization would allow storing much larger values in this kind of system, up to several megabytes at least. So instead of using the DHT for storing metadata for torrent files, the DHT could actually be used to store directly any data. What are you opinions for this? Any fatal flaws? Would you be willing to develop initial open source prototype for a bitcoin bounty, or would you know someone who could? About distributed hash tables: http://en.wikipedia.org/wiki/Distributed_hash_table Reference implementation of kademlia DHT: https://github.com/bmullekademlia Prototype could be built quite easily with pybitcointools + kademlia (or with electrum)
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.
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.
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.
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.
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.
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.
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.
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 postsper 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 onYouTube. 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.
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.
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 (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.
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.
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.
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 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
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...
Download Dragonchain’s dctl
Input three commands into a terminal
Build an image
More information can be found in our Get started documents.
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.
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.
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
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 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.
Offload all Ethereum transaction fees (user withdrawals) to interested users as they wish to withdraw tokens for external use or sale.
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).
In a combination of the above, customers could cover aggregated fees.
Integrate with alternate Ethereum roll up solutions or other proposals to aggregate minting and distribution transactions onto Ethereum.
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
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 Points: Show us how it works. Do you have an idea for a cool new use case for Community Points? Build it!
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.
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
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.
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).
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
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
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
The dichotomy is between computationally infeasible vs informationally-theoretic infeasible. Basically:
Something is computationally infeasible if it could in theory be done, but you would not be able to build a practical computer to do it within the age of the universe and using only the power available in just one galaxy or thereabouts.
Something is informationally-theoretic infeasible if even if you had any arbitrarily large amount of time, space, and energy, you cannot do it.
Quantum breaks represent a possible reduction in computational infeasibility of certain things, but not information-theoretic infeasibility. For example, suppose you want to know what 256-bit preimages map to 256-bit hashes. In theory, you just need to build a table with 2256 entries and start from 0x0000000000000000000000000000000000000000000000000000000000000000 and so on. This is computationally infeasible, but not information-theoretic infeasible. However, suppose you want to know what preimages, of any size, map to 256-bit hashes. Since the preimages can be of any size, after finishing with 256-bit preimages, you have to proceed to 257-bit preimages. And so on. And there is no size limit, so you will literally never finish. Even if you lived forever, you would not complete it. This is information-theoretic infeasible.
How does this relate to confidential transactions? Basically, every confidential transaction simply hides the value behind a homomorphic commitment. What is a homomorphic commitment? Okay, let's start with commitments. A commitment is something which lets you hide something, and later reveal what you hid. Until you reveal it, even if somebody has access to the commitment, they cannot reverse it to find out what you hid. This is called the "hiding property" of commitments. However, when you do reveal it (or "open the commitment"), then you cannot replace what you hid with some other thing. This is called the "binding property" of commitments. For example, a hash of a preimage is a commitment. Suppose I want to commit to something. For example, I want to show that I can predict the future using the energy of a spare galaxy I have in my pocket. I can hide that something by hashing a description of the future. Then I can give the hash to you. You still cannot learn the future, because it's just a hash, and you can't reverse the hash ("hiding"). But suppose the future event occurs. I can reveal that I did, in fact, know the future. So I give you the description, and you hash it and compare it to the hash I gave earlier. Because of preimage resistance, I cannot retroactively change what I hid in the hash, so what I gave must have been known to me at the time that I gave you the commitment i..e. hash ("binding").
A homomorphic commitment simply means that if I can do certain operations on preimages of the commitment scheme, there are certain operations on the commitments that would create similar ("homo") changes ("morphic") to the commitments. For example, suppose I have a magical function h() which is a homomorphic commitment scheme. It can hide very large (near 256-bit) numbers. Then if h() is homomorphic, there may be certain operations on numbers behind the h() that have homomorphisms after the h(). For example, I might have an operation <+> that is homomorphic in h() on +, or in other words, if I have two large numbers a and b, then h(a + b) = h(a) <+> h(b). + and <+> are different operations, but they are homomorphic to each other. For example, elliptic curve scalars and points have homomorphic operations. Scalars (private keys) are "just" very large near-256-bit numbers, while points are a scalar times a standard generator point G. Elliptic curve operations exist where there is a <+> between points that is homomorphic on standard + on scalars, and a <*> between a scalar and a point that is homomorphic on standard * multiplication on scalars. For example, suppose I have two large scalars a and b. I can use elliptic curve points as a commitment scheme: I can take a <*> G to generate a point A. It is hiding since nobody can learn what a is unless I reveal it (a and A can be used in standard ECDSA private-public key cryptography, with the scalar a as the private key and the point A as the public key, and the a cannot be derived even if somebody else knows A). Thus, it is hiding. At the same time, for a particular point A and standard generator point G, there is only one possible scalar a which when "multiplied" with G yields A. So scalars and elliptic curve points are a commitment scheme, with both hiding and binding properties. Now, as mentioned there is a <+> operation on points that is homomorphic to the + operation on corresponding scalars. For example, suppose there are two scalars a and b. I can compute (a + b) <*> G to generate a particular point. But even if I don't know scalars a and b, but I do know points A = a <*> G and B = b <*> G, then I can use A <+> B to derive (a + b) <*> G (or equivalently, (a <*> G) <+> (b <*> G) == (a + b) <*> G). This makes points a homomorphic commitment scheme on scalars.
Confidential Transactions: A Sketch
This is useful since we can easily use the near-256-bit scalars in SECP256K1 elliptic curves to easily represent values in a monetary system, and hide those values by using a homomorphic commitment scheme. We can use the hiding property to prevent people from learning the values of the money we are sending and receiving. Now, in a proper cryptocurrency, a normal, non-coinbase transaction does not create or destroy coins: the values of the input coins are equal to the value of the output coins. We can use a homomorphic commitment scheme. Suppose I have a transaction that consumes an input value a and creates two output values b and c. That is, a = b + c, i.e. the sum of all inputs a equals the sum of all outputs b and c. But remember, with a homomorphic commitment scheme like elliptic curve points, there exists a <+> operation on points that is homomorphic to the ordinary school-arithmetic + addition on large numbers. So, confidential transactions can use points a <*> G as input, and points b <*> G and c <*> G as output, and we can easily prove that a <*> G = (b <*> G) <+> (c <*> G) if a = b + c, without revealing a, b, or c to anyone.
Actually, we cannot just use a <*> G as a commitment scheme in practice. Remember, Bitcoin has a cap on the number of satoshis ever to be created, and it's less than 253 satoshis, which is fairly trivial. I can easily compute all values of a <*> G for all values of a from 0 to 253 and know which a <*> G corresponds to which actual amount a. So in confidential transactions, we cannot naively use a <*> G commitments, we need Pedersen commitments. If you know what a "salt" is, then Pedersen commitments are fairly obvious. A "salt" is something you add to e.g. a password so that the hash of the password is much harder to attack. Humans are idiots and when asked to generate passwords, will output a password that takes less than 230 possibilities, which is fairly easy to grind. So what you do is that you "salt" a password by prepending a random string to it. You then hash the random string + password, and store the random string --- the salt --- together with the hash in your database. Then when somebody logs in, you take the password, prepend the salt, hash, and check if the hash matches with the in-database hash, and you let them log in. Now, with a hash, even if somebody copies your password database, the can't get the password. They're hashed. But with a salt, even techniques like rainbow tables make a hacker's life even harder. They can't hash a possible password and check every hash in your db for something that matches. Instead, if they get a possible password, they have to prepend each salt, hash, then compare. That greatly increases the computational needs of a hacker, which is why salts are good. What a Pedersen commitment is, is a point a <*> H, where a is the actual value you commit to, plus <+> another point r <*> G. H here is a second standard generator point, different from G. The r is the salt in the Pedersen commitment. It makes it so that even if you show (a <*> H) <+> (r <*> G) to somebody, they can't grind all possible values of a and try to match it with your point --- they also have to grind r (just as with the password-salt example above). And r is much larger, it can be a true near-256-bit number that is the range of scalars in SECP256K1, whereas a is constrained to "reasonable" numbers of satoshi, which cannot exceed 21 million Bitcoins. Now, in order to validate a transaction with input a and outputs b and c, you only have to prove a = b + c. Suppose we are hiding those amounts using Pedersen commitments. You have an input of amount a, and you know a and r. The blockchain has an amount (a <*> H) <+> (r <*> G). In order to create the two outputs b and c, you just have to create two new r scalars such that r = r + r. This is trivial, you just select a new random r and then compute r = r - r, it's just basic algebra. Then you create a transaction consuming the input (a <*> H) <+> (r <*> G) and outputs (b <*> H) <+> (r <*> G) and (c <*> H) <+> (r <*> G). You know that a = b + c, and r = r + r, while fullnodes around the world, who don't know any of the amounts or scalars involved, can just take the points (a <*> H) <+> (r <*> G) and see if it equals (b <*> H) <+> (r <*> G) <+> (c <*> H) <+> (r <*> G). That is all that fullnodes have to validate, they just need to perform <+> operations on points and comparison on points, and from there they validate transactions, all without knowing the actual values involved.
What does this mean? It's just a measure of how "impossible" binding vs hiding is. Pedersen commitments are computationally binding, meaning that in theory, a user of this commitment with arbitrary time and space and energy can, in theory, replace the amount with something else. However, it is information-theoretic hiding, meaning an attacker with arbitrary time and space and energy cannot figure out exactly what got hidden behind the commitment. But why? Now, we have been using a and a <*> G as private keys and public keys in ECDSA and Schnorr. There is an operation <*> on a scalar and a point that generates another point, but we cannot "revrese" this operation. For example, even if I know A, and know that A = a <*> G, but do not know a, I cannot derive a --- there is no operation between A G that lets me know a. Actually there is: I "just" need to have so much time, space, and energy that I just start counting a from 0 to 2256 and find which a results in A = a <*> G. This is a computational limit: I don't have a spare universe in my back pocket I can use to do all those computations. Now, replace a with h and A with H. Remember that Pedersen commitments use a "second" standard generator point. The generator points G and H are "not really special" --- they are just random points on the curve that we selected and standardized. There is no operation H G such that I can learn h where H = h <*> G, though if I happen to have a spare universe in my back pocket I can "just" brute force it. Suppose I do have a spare universe in my back pocket, and learn h = H G such that H = h <*> G. What can I do in Pedersen commitments? Well, I have an amount a that is committed to by (a <*> H) <+> (r <*> G). But I happen to know h! Suppose I want to double my money a without involving Elon Musk. Then:
(a <*> H) <+> (r <*> G)
== (a <*> (h <*> G)) <+> (r <*> G)
== ((a * h) <*> G) <+> (r <*> G); remember, <*> is also homomorphic on multiplication *.
== ((a * h + a * h - a * h) <*> G) <+> (r <*> G); just add 0.
== ((a * h + a * h) <*> G) <+> ((-a * h) <*> G) <+> (r <*> G)
== ((2 * a * h) <*> G) <+> ((r - a * h) <*> G)
== ((2 * a) <*> (h <*> G)) <+> ((r - a * h) <*> G)
== ((2 * a) <*> H) <+> ((r - a * h) <*> G); TADA!! I doubled my money!
That is what we mean by computationally binding: if I can compute h such that H = h <*> G, then I can find another number which opens the same commitment. And of course I'd make sure that number is much larger than what I originally had in that address! Now, the reason why it is "only" computationally binding is that it is information-theoretically hiding. Suppose somebody knows h, but has no money in the cryptocurrency. All they see are points. They can try to find what the original amounts are, but because any amount can be mapped to "the same" point with knowledge of h (e.g. in the above, a and 2 * a got mapped to the same point by "just" replacing the salt r with r - a * h; this can be done for 3 * a, 4 * a etc.), they cannot learn historical amounts --- the a in historical amounts could be anything. The drawback, though, is that --- as seen above --- arbitrary inflation is now introduced once somebody knows h. They can multiply their money by any arbitrary factor with knowledge of h. It is impossible to have both perfect hiding (i.e. historical amounts remain hidden even after a computational break) and perfect binding (i.e. you can't later open the commitment to a different, much larger, amount). Pedersen commitments just happen to have perfect hiding, but only computationally-infeasible binding. This means they allow hiding historical values, but in case of anything that allows better computational power --- including but not limited to quantum breaks --- they allow arbitrary inflation.
Changing The Tradeoffs with ElGamal Commitments
An ElGamal commitment is just a Pedersen commitment, but with the point r <*> G also stored in a separate section of the transaction. This commits the r, and fixes it to a specific value. This prevents me from opening my (a <*> H) <+> (r <*> G) as ((2 * a) <*> H) <+> ((r - a * h) <*> G), because the (r - a * h) would not match the r <*> G sitting in a separate section of the transaction. This forces me to be bound to that specific value, and no amount of computation power will let me escape --- it is information-theoretically binding i.e. perfectly binding. But that is now computationally hiding. An evil surveillor with arbitrary time and space can focus on the r <*> G sitting in a separate section of the transaction, and grind r from 0 to 2256 to determine what r matches that point. Then from there, they can negate r to get (-r) <*> G and add it to the (a <*> H) <+> (r <*> G) to get a <*> H, and then grind that to determine the value a. With massive increases in computational ability --- including but not limited to quantum breaks --- an evil surveillor can see all the historical amounts of confidential transactions.
This is the source of the tradeoff: either you design confidential transactions so in case of a quantum break, historical transactions continue to hide their amounts, but inflation of the money is now unavoidable, OR you make the money supply sacrosanct, but you potentially sacrifice amount hiding in case of some break, including but not limited to quantum breaks.
How much help can Hierarchical Deterministic trees of keys help with key management for non-expert users?
I've recently been made aware of BIP32, which was invented to make "Hierarchical Deterministic Wallets" (HD wallets) in BitCoin. I was wondering what uses this could have outside crypto currencies most notably for your "regular" cypherpunk using tools like GPG or Age to communicate with their web of trust. A deterministic tree of key pairs basically works like this: you start with a root key pair, that must be generated once and never lost or compromised. Then you generate sub-keys by hashing that root key with an easily remembered index). If a sub-key is lost, it can be re-generated from the root key. Now, BIP32 has two ways of generating sub keys, each with their own tradeofs. Note: I'll use the following names from now on:
G -- Generator of the group (public constant) a -- root private key A = a.G -- root public key b -- child private key B = b.G -- child public key. i -- public index (each child key has its own unique index)
Hardened keys are generated from the private half of the root key (over-simplified for clarity):
b = KDF(a, i) B = b.G
Key derivation can't be reversed, so if the child key b happens to be compromised, the root key a is still safe. The advantage of the deterministic generation is that if you lose the child key (you dumped your cell phone, your hard drive fried…) you can re-generate it from the root key, and pretend you never lost it. Non-hardened keys are generated from the public half of the root key, such that even third parties can generate it:
z = KDF(A, i) Z = z.G b = a + z -- modulo group order B = A + Z B = a.G + z.G B = (a+z).G B = b.G
Anyone can generate the public key, but generating the private key requires knowledge of the root private key. As far as I know, this is safe, because breaking this scheme would mean that we have solved the Discrete Logarithm Problem. However, if a non-hardened child key b is compromised, so is the root key. z is public (derived from the public root key), so knowing b easily reveals a:
b = a + z a = b - z
Unless I'm missing something, this means we should not store non-hardened key pairs less securely than we store the root key itself.
Is there a compelling use case?
I was wondering how useful those could be, compared to a simple hierarchy of certified keys, where child keys are generated randomly, and simply signed by their parent key? With those simple hierarchies, you'd simply rotate keys from time to time, and other people would know to trust the new key based on certificate from the parent (or chain of ancestors). If you lose a key, you simply rotate (and sign) a new one. One obvious advantage of deterministic hardened keys is that we can achieve continuity without relying on a certificate. We can afford to lose them even if we don't have an easy way to rotate them. But… aren't we supposed to rotate keys to begin with? Then there are the deterministic non hardened keys. I'm not sure what they bring to the table exactly: with Bitcoin, they help you make wallets on the fly without giving your root key to the wallet factory. If I understand correctly, compromising the wallet factory may compromise your identity (we can link its generated keys with your own public key by knowing the indices), but it won't compromise your money (the private halves are still safe, so only you can transfer the coins away from those wallets). Outside of crypto currencies however, I'm not sure: there's little point sending a message to a non-hardened child key instead of its parent key, since a compromise of the child key is just as bad as compromise of its aren't. One could still generate child keys without revealing the indices, but if you're anonymous, why not just generate a one-time key pair? Simply put: What a reasonable key management for the paranoid private citizen should look like?
This is how I've been doing things in my Digital Perdition chronicle / narrative for Shadowrun for years. If this is useful, feel free to steal it. I assume this probably isn't a new idea, but in my world, Nuyen is a form of cryptocurrency, like bitcoin or ethereum. It's also a "smart" currency, in that it can autonomously do things, all by itself. Any "nuyen app" on any comlink can, with a very simple user-facing interface, create things like escrows, trusts, provisional holdings, task verified transactions, etc. As long as the system can autonomously verify the information some how in the outside world, it can interact with it. (This also means the system is somewhat fallible and can be hacked / spoofed / fooled, which can lead to interesting emergent narratives / plots all on its own). The fact that it's a cryptocurrency also informs the logic of what happens if Nuyen is copied. Ordinarily, this doesn't happen, and "naked nuyen" (nucoin outside of a wallet app or not encrypted on a credstick) is very suspicious, and if you're going to accept it, you need to be able to verrify it in real time, like right now, and transfer it to your account before you leave this dark alley / a abandoned warehouse transaction, or not accept it at all if you don't have signal. But if you do some how manage to clone some Nuyen, then just like crypto, and there's two of the exact same nucoin, then it's whoever syncs it to their account first. The other is considered the forgery. So that can create a "race against the clock" scenario if two opposing forces have the bag, the same bag, and need to get back to civilization before the other guy does. (This might not even come up in your games, but I play in a lot of areas like, in the middle of the ocean, pirates and atolls, as well as extremely rural northern Canada, South American jungles, and sub-Saharian Africa, exploring ancient blood mage / cultist desert ruins, etc, so often, "spotty signal" is an environmental hurdle / plot point.) We also have "credcoins" in addition to regular old credsticks. A "credcoin" is basically like an SD card, but with a poker-chip style plastic housing around it, to make it more handleable. The chip holds the actual encrypted nucoin (like a credstick) so they're not naked nuyen (see above), but they've also got an optical code, like a QR code, printed on them. They can be used in vending machines in 3rd world areas where signal might be spotty, or traded in physical transactions. The way they work, is that we've written into the narrative that a certain block of numbers in the "nuyen hash" of each nucoin, maybe like the last five digits or something, who knows, but that there's a world wide industry standard number to indicate that these nuyen are dedicated for physical use. Sort of like how some IP addresses are reserved for localhost or LAN. If any system, any wallet app, sees these digits, it wont let them be "deposited". Only a physical bank can do it. This prevents someone from just scanning a credcoin, depositing the nuyen, and now the coins still look valid, but are useless. If you wanted to "deposit" them, you'd take them to a bank, they would scan them and verify, add them to your account, and remove those coins from circulation immediately by physically destroying them (or feeding them into a hopper to be able to 3d print new ones). They'd also charge you a fee for the overhead of the cost of actually producing currency, sort of like those CoinStar machines at Walmart that charge you a fee for counting all your change. Speaking of counting change... That there's an optical code on credcoins makes that easy, too. Anyone with AR (augmented reality -- so basically, anyone, even if it's only through a hand held comlink screen, but usually AR contact lenses, glasses, goggles, or cybereyes) can just look at a credcoin and immediately know how much it is. You can also dump them out on the table, stand back so you get them all in frame, and just see a total for how much the value of all of them are. Each credcoin already has an ARO, but if there's a shit load of them together in close proximity, the AROs just merge together into a single one so as not to be "spammy". If you want to block the AROs, you can store your credcoins in signal blocking bags, containers, or metal coin rolls. Credcoins are also slightly different sizes and colors to tell the denomination at a glance, as well. Anyway, I hope some of those ideas are useful for your games. :)
https://preview.redd.it/nnuhfz6q01t51.png?width=700&format=png&auto=webp&s=15ce35581f2ebad02af140180f5a8b1fe7931f00 Technology & Products Public Chain Development · WASM AMPL contract debugging (100%) · Research on WASM zero-knowledge proof anonymous transfer (50%) · WASM Sushi contract coding (100%) · WASM RPC iOS asynchronous library commissioning (100%) · Verification of the signature push public key algorithm and testing its codability (C++, go) through RPC (100%) · The new lock-up airdrop contract function: lock-up users can claim the unlocked assets by entering RegID (100%) · Porting ASWAP contract to public chain 3.0, adding platform fee processing (100%) · Optimization of Yield Farming contract reward distribution (100%) · Optimization of Yield Farming contract penalty distribution mechanism (100%) · Yield Farming contract testing (100%) · Deployment and initial configuration of WICC and WGRT yield farming contracts and Wayki-X contract completed (100%) · Ownership of issuance and transfer rights of the bottom-level token ROG transferred to Wayki-X contract (100%) · The initial generation of ROG completed. 10.08M ROG entered the WICC pool, 2.52M ROG entered the WGRT pool (100%) · The first 189,000 ROG was minted in Wayki-X contract for rewards by inflation (12.6M × 1.5%) (100%) · Transfer of 70,000 ROG to AEX for Ecosystem Yield Farming completed (100%) · WASM developer documentation: added detailed WASM table (Simplified Chinese) (100%) · WASM developer documentation: added call of multiple contracts and multisignature transactions in WASM contract (Simplified Chinese) (100%) Application Development · Yield Farming back end API (100%) · Yield Farming front end page optimization (100%) · Yield Farming front end localization (100%) · Yield Farming pre-release initial API docking (100%) · Yield Farming application testing (100%) · Yield Farming application release (100%) · xUSD & ROG added to Instant in WaykiTimes Android (100%) · Memory leak issue fixed in Instant in WaykiTimes (100%) · Data loading error when swiping in Discover fixed in WaykiTimes (100%) · Data display optimized in Getting Started in WaykiTimes · UI debugging of several pages in WaykiTimes (100%) · WaykiTimes 3.0.4 released (100%) · WaykiTimes Help Center released (100%) · WaykiTimes Getting Started released (100%) · WaykiTimes remember password function released (100%) · WaykiTimes iOS App Store version tested (100%) · Google crash analysis and testing added to WaykiTimes Android (100%) · Solved the data loading issue when swiping in Wayki-X Synths (100%) · Wayki-X price feed delay fixed (100%) · Amount issue in the plug-in wallet fixed (100%) · Display error of release contract type of universal transactions fixed on the blockchain explorer (100%) · WASM contract display specifications for the blockchain explorer completed (100%) · Development of the Coinbase integration project (wicc-rosetta-api) (85%) Plan for October Public Chain Development · Research on WASM zero-knowledge proof anonymous transfer · Correction of ASWAP contract proof of liquidity token generation rules · ASWAP contract testing · Docking of ASWAP contract with third parties · Continuous updating of coind RPC interface documentation Application Development · Trade — transaction details HTML5 page to native page transfer in WaykiTimes · Development of the Coinbase integration project (wicc-rosetta-api) Market International Market · On September 4, Russian volunteers opened the second WaykiChain Russian group in Telegram: https://t.me/waykichainrussian. · On September 6, WaykiChain opened the official community in Discord: https://discord.gg/XyAkqa. · On September 6, WaykiChain CTO Richard Chen was invited to the Blockchain + Innovative Service and Industrial Application Conference and the China Chamber of International Commerce Blockchain Innovation Service Industry Committee Establishment Conference as a member of the expert group. · On September 11, the famous US blockchain TV program Exploring the Block tweeted about WaykiChain, showing it is optimistic about the future development of the integrated DeFi ecology of WaykiChain. · On September 11, the famous business platform Yahoo Finance released WaykiChain project information and announced that WaykiChain CEO Gordon Gao gives an interview to NASDAQ MarketSite’s Jane King on September 12. · At 7:00 PM EDT on September 12, world’s largest financial channel Bloomberg TV reported that WaykiChain CEO Gordon Gao was interviewed by Jane King of NASDAQ MarketSite. The interview aired on Fox Business Network at 10:30 PM EDT on September 14. · On September 12, cryptocurrency Twitter account Crypto Catalog tweeted about WaykiChain, showing it is optimistic about the future development of the integrated DeFi ecology of WaykiChain. · On September 13, DeFi List added WaykiChain governance token WGRT. · On September 13, WaykiChain reached market cooperation with the Indian blockchain influencer Gmadvice who started to serve as WaykiChain community manager in India. · On September 16, WaykiChain released “WaykiChain Launches Phoenix Yield Farming with WICC/WGRT Dual-pool for ROG Genesis Issuance” on Twitter. Up to September 21, the news hit 2,400+ retweets. · On September 17, the cryptocurrency influencer DeFi List retweeted “WaykiChain Launches Phoenix Yield Farming with WICC/WGRT Dual-pool for ROG Genesis Issuance”. · On September 18, WaykiChain reached strategic market cooperation with the Korean crypto influencer Pantera who will help WaykiChain establish a broad and strong consensus in Korea. · On September 19, “WaykiChain Dual-pool ROG Yield Farming Korean Group” community established. · On September 20, the influencer Crypto Wendy retweeted “WaykiChain Launches Phoenix Yield Farming with WICC/WGRT Dual-pool for ROG Genesis Issuance”. · On September 21, 130+ Korean media outlets published “WaykiChain Launches Phoenix Yield Farming with WICC & WGRT Dual-pool for ROG Genesis Issuance”. · On September 23, WaykiChain co-founder and CEO Gordon Gao was invited to an AMA session with ICO Pantera Group, Korea’s top Telegram group (stats by u/combot), where he shared his insights into DeFi with 4,000+ Korean users and introduced WaykiChain’s ROG Genesis Yield Farming. · On September 24, WaykiChain tweeted “ROG Genesis Yield Farming FAQ” and “Leave your question/problem toward WaykiTimes/Wayki-X/ROG Genesis Yield Farming in the Google forms below to share 800 WICC Giveaway!”, the number of engagements is 1,500+. · On September 24, WaykiChain global partner Vincent Lionheart was invited to an AMA session to D’va Community. · On September 24, The Business Telegraph, Bitcoin Garden, and other media published “WaykiChain Launches Phoenix Yield Farming with WICC & WGRT Dual-pool”. · On September 24, WaykiChain tweeted the ROG Genesis Yield Farming Countdown. The news hit 1,000+ retweets. · On September 25, ROG Genesis Yield Farming news was the day’s hit in Korea with 5,000+ views on Korean cryptocurrency forums. National Market · On September 1, CoinTiger listed WaykiChain governance token WGRT and opened the WGRT/USDT pair. WGRT net buy & hold competition started and the CoinTiger community joined a series of WGRT-themed challenges. · On September 1, WaykiChain governance token WGRT successfully mapped to Ethereum and ERC-20 WGRT was created. The world’s largest DEX Uniswap officially supported it and listed the WGRT/USDT pair. · On September 2, WaykiChain Strategic Analyst Jing Tao gave the speech “WGRT Dragon, Fly, Tiger, and Leap: Community Governance Upstart” to the MXC community and distributed 3 gold bars to the event participants. · On September 7, WaykiChain Strategy Analyst Jing Tao attended [This Is Coin Coffee] live DeFi contest co-sponsored by Coinka, fogwu.com, and tuoniaox.com. WEDEX founder & CEO, Loopring co-founder Chen Xiaoliang and ChainNews Research Director Pan Zhixiong joined the event. · On September 9, Gate.io selected WaykiChain governance token WGRT for the Listing Vote. Each voter had a chance to share an airdrop of 420,875.43 WGRT. WGRT passed the voting with 53,293,775 votes and was successfully listed on Gate.io. · On September 10, WGRT/USDT trading pair and WGRT withdrawals opened on Gate.io. · On September 10, WaykiChain released WaykiChain Governance Token WGRT Information and Addresses. The team announced that before July 1, 2021, WGRT circulating supply will be strictly controlled at 10% of the total supply, or 2.1 billion. · On September 9 to 11, WaykiChain was invited to IoT World China & 5G China along with 400+ exhibitors including Huawei, Baidu, and Tencent. WaykiChain demonstrated the integrated public chain DeFi ecosystem that will help China’s digital construction. · On September 11, WaykiChain Strategy Analyst Jing Tao was invited to the Bepal community and shared the speech “WaykiChain Governance Token WGRT: Accumulation and Breakout”. WaykiChain airdropped 3,000 WGRT and cash red envelopes to the Bepal community members. · On September 12, WaykiChain Technology & Development Manager Yuanhang Xiao and Strategy Analyst Jing Tao introduced [New WaykiChain DeFi Product: Decentralized Synthetic Asset Issuance Protocol Wayki-X] in the official WaykiChain yizhibo account. During the live broadcast, WaykiChain distributed pure gold bars and branded gifts to lucky users. · On September 13, WaykiChain co-founder & CEO Gordon Gao and Overseas Director Qiyuan Mei shared the speech “WaykiChain Opens the Era of Integrated DeFi Public Chains” in the Gate.io live broadcast room. Gate.io CPO Jiuer was the broadcast host. The guests explained WaykiChain’s DeFi strategy and revealed the launch of Yield Farming. · On September 15, WaykiChain CEO Gordon Gao and BTC38 co-founder Tianwei Huang held the live stream titled “Eight Questions to Explain DeFi Trends and Opportunities” in yizhibo. The hosts analyzed the status and trends of DeFi, discussed DeFi deployment by public chains and exchanges, and new opportunities in synthetic asset trading. WaykiChain distributed pure gold bars and branded gifts to lucky viewers of the stream. · On September 16, WaykiChain Strategy Analyst Jing Tao shared the speech titled “WaykiChain’s Integrated DeFi Ecosystem Layout” as the guest of btcmoney.cc. · On September 18, Bying community invited WaykiChain Strategy Analyst Jing Tao to share the speech “New DeFi Opportunity: Phoenix Yield Farming”. WaykiChain held a WICC airdrop for Bying community members. · On September 18, WaykiChain published the article “No Pre-mining, ICO, or Reserve! WaykiChain Launches Dual-pool Phoenix Yield Farming”. · On September 19, WaykiChain published the article “Chapter 1. The Financial Innovation of Blockchain Reformation. The Origin, Logic, and Value of WaykiChain ROG” introducing the background of ROG, the operation mechanism of the decentralized synthetic asset system Wayki-X, and the value foundation of ROG in detail. · On September 23, “No Pre-mining, ICO, or Reserve! WaykiChain ROG Genesis Farming and Early Release Guide” was released across Chinese media. · On September 24, WaykiChain CEO Gordon Gao, CTO Richard Chen, and CPO Xi Zhang held a joint live stream on yizhibo explaining the future planning of WaykiChain decentralized synthetic asset issuance protocol Wayki-X, ROG, and WaykiChain DeFi in terms of business model, technology, and products. WaykiChain distributed 1 pure gold bar and 6 branded gifts to the lucky stream viewers. · On September 24, Gate.io and WaykiChain launched the WGRT Investment Competition. The prizes are a BMW G 310 R motorcycle, a 13” MacBook Pro, a 10.2” iPad, 17 pure gold bars and 99,000 WGRT. · On September 25, various Chinese media released “Wayki-X 101: WaykiChain Decentralized Synthetic Asset Protocol” introducing the functions and mechanism of the decentralized synthetic asset issuance protocol Wayki-X and the value of its token ROG in detail. · On September 25, WaykiChain launched the “Looking for the Genesis Prophet” community event. The winners received 10 branded gifts. · On September 25, WaykiChain ROG Genesis Yield Farming launched. WICC and WGRT pool quotas (5 million and 25 million, respectively) were full within just one hour. · On September 25, WaykiChain reached ecosystem partnership with AEX. AEX became the first platform to join ROG Ecosystem Yield Farming. · On September 25, WaykiChain partnered with Bying wallet. ROG Genesis Yield Farming is available in Bying wallet. · On September 26, ROG, the main token of WaykiChain’s decentralized synthetic asset issuance protocol Wayki-X, was listed on AEX. ROG/USDT trading pair is available. · On September 26, WaykiChain CEO Gordon Gao gave lectures “DeFi Financial Principles and Commercial Applications” and “DeFi Industry Panoramic Scan” at The First Offline Practical Training Camp of Hash Power University, Shanghai Station. Participants included Ontology founder Jun Li, Chainlink Labs — China Head Philip Fei, Digital Renaissance Foundation Managing Director Cao Yin, and Waterdrip Capital founding partner Zheng Yushan. · On September 28, WaykiChain co-founder and CEO Gordon Gao was a guest at Hash Power Knowledge Base Private Meeting, Shenzhen Station where he shared the speech titled “Feasible Ways of DeFi Application Popularization”. Other guests included Ontology founder Jun Li, DeBank founder and CEO Tang Hongbo, and Huobi Research Chief Technical Researcher Tianyuan Ma.
New England New England 6 States Songs: https://www.reddit.com/newengland/comments/er8wxd/new_england_6_states_songs/ NewEnglandcoin Symbol: NENG NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones. Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt. 1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377 NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number Bitcoin Fork - Suitable for Home Hobbyists NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs. The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity. MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018) https://www.youtube.com/playlist?list=PLUl4u3cNGP63UUkfL0onkxF6MYgVa04Fn CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software. Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%. NENG v1.4.0 release enabled CPU mining inside android phones. Youtube Video Tutorial How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 https://www.youtube.com/watch?v=sdOoPvAjzlE How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2 https://www.youtube.com/watch?v=nHnRJvJRzZg How to CPU Mine NewEnglandcoin (NENG) in macOS https://www.youtube.com/watch?v=Zj7NLMeNSOQ Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG. We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange. Twitter Airdrop Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners Graphic Redesign Bounty Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at: https://discord.gg/UPeBwgs Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form. Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues. Twitter Airdrop/Graphic Redesign bounty sign up: https://goo.gl/forms/L0vcwmVi8c76cR7m1 Milestones
Sep 3, 2018 - Genesis block was mined, NewEnglandcoin created
Sep 8, 2018 - github source uploaded, Window wallet development work started
Sep 11,2018 - Window Qt Graphic wallet completed
Sep 12,2018 - NewEnglandcoin Launched in both Bitcointalk forum and Marinecoin forum
Sep 14,2018 - NewEnglandcoin is listed at ShorelineCrypto Exchange
Sep 17,2018 - Block Explorer is up
Nov 23,2018 - New Source/Wallet Release v1.1.1 - Enabled Dynamic Addjustment on Mining Hashing Difficulty
Nov 28,2018 - NewEnglandcoin became CPU minable coin
Nov 30,2018 - First Retail Real Life usage for NewEnglandcoin Announced
Dec 28,2018 - Cheetah_Cpuminer under Linux is released
Dec 31,2018 - NENG Technical Whitepaper is released
Jan 2,2019 - Cheetah_Cpuminer under Windows is released
Jan 12,2019 - NENG v1.1.2 is released to support MacOS GUI CLI Wallet
Jan 13,2019 - Cheetah_CpuMiner under Mac is released
Feb 11,2019 - NewEnglandcoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork
Mar 16,2019 - NewEnglandcoin v18.104.22.168 Released - Ubuntu 18.04 Wallet Binary Files
Apr 7, 2019 - NENG Report on Security, Decentralization, Valuation
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto
Sep 1, 2019 - Shoreline Tradingbot project is Launched by ShorelineCrypto
Dec 19, 2019 - Shoreline Tradingbot v1.0 is Released by ShorelineCrypto
Jan 30, 2020 - Scrypt RandomSpike - NENG v1.3.0 Hardfork Proposed
Feb 24, 2020 - Scrypt RandomSpike - NENG core v1.3.0 Released
Jun 19, 2020 - Linux scripts for Futurebit Moonlander2 USB ASIC on solo mining Released
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining and Ubuntu 20.04 support
Jul 21, 2020 - NENG v22.214.171.124 Released for MacOS Wallet Upgrade with Catalina
Jul 30, 2020 - NENG v126.96.36.199 Released for Linux Wallet Upgrade with 8 Distros
Aug 11, 2020 - NENG v188.8.131.52 Released for Android arm64 Upgrade, Chromebook Support
Aug 30, 2020 - NENG v184.108.40.206 Released for Android/Chromebook with armhf, better hardware support
2018 Q3 - Birth of NewEnglandcoin, window/linux wallet - Done
2018 Q4 - Decentralization Phase I
Blockchain Upgrade - Dynamic hashing algorithm I - Done
Cheetah Version I- CPU Mining Automation Tool on Linux - Done
2019 Q1 - Decentralization Phase II
Cheetah Version II- CPU Mining Automation Tool on Window/Linux - Done
Blockchain Upgrade Dynamic hashing algorithm II - Done
2019 Q2 - Fiat Phase I
Assessment of Risk of 51% Attack on NENG - done
Launch of Fiat USD/NENG offering for U.S. residents - done
Initiation of Mobile Miner Project - Done
2019 Q3 - Shoreline Tradingbot, Mobile Project
Evaluation and planning of Mobile Miner Project - on Hold
Initiation of Trading Bot Project - Done
2019 Q4 - Shoreline Tradingbot
Shoreline tradingbot Release v1.0 - Done
2020 Q1 - Evaluate NENG core, Mobile Wallet Phase I
NENG core Decentralization Security Evaluation for v1.3.x - Done
Light Mobile Wallet Project Initiation, Evaluation
2020 Q2 - NENG Core, Mobile Wallet Phase II
NENG core Decentralization Security Hardfork on v1.3.x - Scrypt RandomSpike
Light Mobile Wallet Project Design, Coding
2020 Q3 - NENG core, NENG Mobile Wallet Phase II
Review on results of v1.3.x, NENG core Dev Decision on v1.4.x, Hardfork If needed
Light Mobile Wallet Project testing, alpha Release
2020 Q4 - Mobile Wallet Phase III
Light Mobile Wallet Project Beta Release
Light Mobile Wallet Server Deployment Evaluation and Decision
If you believe a client is compromised, either by a Bitcoin miner, or that it’s a rat, or a backdoor, or a Trojan, etc. you should submit real evidence of such claims. You should upload the client executable or suspicious libraries to VirusTotal and give us the link, you should also submit actual evidence. I keep seeing “sigma is a rat” — I don’t use sigma, I use Impact, but it doesn’t make a whole lot of sense. The ONLY “evidence” that anyone has brought to the table is “my CPU usage was high when it was open”. That’s literally it. If you’re going to claim something is bad, you should do it right and in such a way that there isn’t merely suspicion, but there is damning evidence. This way maybe the mods or I can make a master list of clients that can and cannot be trusted. I will start on this master list and call it the Checker Thread so it is easy to search for. I request the mods pin this list for easy access. This master list will contain hacked clients submitted by the community, their supported versions, VirusTotals, etc. to improve the search for clients and to guarantee user safety. “But what if my executable is different?” Each client in the list will have a hash, you will be able to check that hash against your client to verify it is the same executable, and therefore safe.
Link to original article:https://block.co/blockchain-use-in-intellectual-property/ Patents, trademarks, and industrial designs, along with copyrights, are all types of intellectual property protections that help creators of written stories, inventions, artistic works, or symbols to stop people from stealing or copying their pieces of work. In this article, we will examine how blockchain is used in Intellectual Property rights. Broadly speaking, Intellectual Properties (IP) are “unique, value-adding creations of the human intellect that result from human ingenuity, creativity, and inventiveness.” (Kalanje, 2006). By observing trends, we can identify a steady increase in the number of Intellectual Property applications worldwide. According to official statistics by the World Intellectual Property Organization (WIPO), applications worldwide of patents grew 72.3% over ten years, increasing to 3,326,300 from 2008 to 2018. Trademarks grew an astonishing 160% over the same period, to a record 14,321,800 number of applications, while industrial design applications were 1,312,600, growing by 61%. Every country has a specific authority where to apply for proper protection. However, it is becoming increasingly common that these jurisdictions will utilize blockchain technology to provide a smoother, faster, and cheaper application process and a system that ensures an incorruptible and secure timestamping through the hashing function. How does it work? Blockchain ‘trust’ is guaranteed by hashing algorithms, instead of third parties. Since, by default, hashes are unique and cannot be misinterpreted, nor two same hashes can be produced, it’s just easy to identify and match that hash with a unique document creating an unambiguous proof of existence. This way, a permanent ledger of data is created to prove the existence and the lifecycle of a specific IP right, enhancing its protection at a registry or in court. Blockchain use in Intellectual Property potential is enormous, aiding in the evidence of creatorship and provenance authentication to registering and clearing IP rights; digital rights management; establishing and enforcing IP agreements, licenses, or exclusive distribution networks through smart contracts; and transmitting payments in real-time to IP owners. In the case of patents, the real benefit of using blockchain lies in the immutable ledger of records with a tamper-proof code providing strong evidence of facts about an invention life-cycle. However, unlike copyrights, any new creation will still have to be patented with the proper authority or anyone else will be free to copy it or claim it without incurring any legal trouble. https://preview.redd.it/py8eashu7vp51.png?width=940&format=png&auto=webp&s=224cf5fb4087a6100f99a05c19038b18abeca6fa “Deploying blockchain technology within the patent system could reduce inefficiencies in recording and efficiently agreeing the time of registrations, perhaps across several national patent systems” (Boucher et al., 2017). In the case of Copyrights, these do not need to be registered with a government authority, therefore blockchain can have a major role in ensuring that evidence can be provided of authorship, use, and status of a specific production. Particularly, in case of disputes in court, blockchain provides strong evidence to prove an inventor’s right on intellectual property, and protect legal rights on authorship. So, when including writing and literary or artistic works, creators get some type of protection automatically via blockchain, whereas with others, they have to apply for it. Trademarks, on the other hand, are the IP protection type that can most benefit from blockchain because it can easily, quickly, and very cheaply prove how similar are two marks to each other and who can claim to have used it first, providing immutable and timestamped proof of dates and usage. By using blockchain, many of the questions which can arise about exactly when, where, and how the trademark was used, can be instantly answered. Cyprus-based company Block.co provides services in a range of different industries, and timestamping trademarks on the blockchain is one of them. The company is a spin-off of the University of Nicosia, one of the biggest blockchain contributors globally, and its mission is to eliminate document fraud in all sectors, by transforming the way institutions manage digital records. International business and technology lawyer Christiana Aristidou makes large use of Block.co’s services and especially in copyrights and trademarks for several of her clients. “We consider the Block.co solution indispensable towards our objective of constantly enhancing the provision of our legal services through innovative technological solutions. The protection of copyright and other relevant intellectual property rights now involves a simple, fast, automated, and cost-efficient, blockchain-backed certificate issuance. Using blockchain, thereby ensuring a transparent, immutable, secure, time-stamped, and tamper-proof recording of data, the Block.co solution offers a revolutionary and innovative means to protect our clients’ intellectual property, instead of other time-consuming and costly traditional processes.” she recentlystated. “Specifically, our clients’ data and evidence supporting their authorship, invention, or creation of any property that warrants copyright protection, may now be recorded in a digital document, which is then verified in a trusted and time-stamped manner on a blockchain. Our clients retain ownership and control of their data, having been granted easy access to a self-verifiable blockchain-secured certificate of such data.” Smart Contracts Smart contracts could also represent an important asset of blockchain technology because they can be used in intellectual property to establish and enforce agreements such as licenses and allow the transmission of payments in real-time to IP owners. Indeed, they allow automatic payments for transactions between users and rights holders with no middle man, thereby cutting out intermediate fees, longer procedures, and bureaucratic hurdles. https://preview.redd.it/arfnefjx7vp51.png?width=940&format=png&auto=webp&s=78db6dc6f734385de74e2916091fff72e935c4e8 Blockchain in IP around the world In Europe, various governmental agencies and IP registries such as the European Union Intellectual Property Office (EUIPO) are actively involved in researching and promoting blockchain capabilities within the industry. In particular, they believe blockchain can transform IP rights by highlighting, in one of their advanced research forums, that:
IP and blockchain are interrelated
Blockchain is transformative
IP protection will drive innovation in the ecosystem
Blockchain technology will transform IP protection and enforcement
Blockchain technology provides opportunities for both pirates and law enforcement
In India, the IPO (Indian Patent Office) is working on using blockchain and other innovative technologies like AI and IOT to enable smoother patent processes. A Blockchain-AI-based ecosystem is on the table to manage IP protection in India, intending to produce a much more efficient, straightforward, and faster procedure. IPO recently announced a tender called, “Expression of Interest for Making use of Artificial Intelligence, Blockchain, IoT and other latest technologies in the Patent Processing system of IPO”, reinforcing their will to proceed along this line of work and stay up to date with the technological innovation that blockchain, AI and IoT can bring to the benefit of IP rights. A legal framework for a Blockchain-based IP registry to protect and commercialize smart ideas is one of the main and earliest initiatives the IPO is taking for the Indian IP industry. In the United States, we find a clear example of how blockchain is used to protect American businesses from IPR theft by testing imports. Since blockchain has proven to be beneficial to streamline communication between multiple parties securely, the U.S. Customs and Border Protection (CBP), with the funding of the Department of Homeland Security’s Science & Technology Directorate, recently completed a proof-of-concept (PoC) of a blockchain platform with that specific aim. Personal data and trade secrets would be kept safe at all times using encrypted keys, with the blockchain acting as an immutable ledger to record trade transactions. In Southeast Asia, Thailand is leading the way in developing blockchain technology for IP protection. Various organizations and government offices have invested in projects aimed at implementing the tech to make IPR processes more efficient and faster. The Ministry of Commerce has recently launched a feasibility study to explore the use of blockchain for IP registration in the country, while the Thai Trade Policy and Strategy Office (TPSO), in collaboration with the British Embassy, were designated to analyze the study and translate it into action plans for future developments. Conclusion — Blockchain limits and benefits in IP As with every new technology, especially the most disruptive ones, setbacks can be both from a technical and a systemic perspective. Enormous processing power and scalability are still the main issues from a technical point, whereas a system that could connect registries across the world through a single distributed ledger represents the main challenge, not only for IP-related industries. Thankfully, Block.co’s solution already uses the Bitcoin blockchain and its network effect for this purpose, envisioning truly decentralized and secure storage for IP rights, that will outlive any issuing institution itself. An international standardized system and platform that could facilitate global communication and successful management of IP rights via blockchain is an ambition that is reflected in healthcare, law, and many other industries. On the other hand, blockchain based IP rights enforcement is already a huge achievement, especially for those small artists who could not afford teams of lawyers to defend them in disputes to prove records of their authorship. For more info, contactBlock.codirectly or email at [email protected]. Tel +357 70007828 Get the latest from Block.co, like and follow us on social media: ✔️Facebook ✔️LinkedIn ✔️Twitter ✔️YouTube ✔️Medium ✔️Instagram ✔️Telegram ✔️Reddit ✔️GitHub
Energi is a self-funding (no ICO and no premine) cryptocurrency that has a purpose to become the world’s leading cryptocurrency with the unification of Smart Contracts, Governance and Self-funding Treasury to ensure longevity and enable rapid growth. You can read more about why we decided to self-fund and chose not to conduct an ICO here. Energi provides a small allocation to Proof-of-Stake (PoS) rewards, takes a bulk of the coin issuance and gives it to its treasury and active Masternodes. Energi also allocates 10% on-going reward to the leadership of the Energi Backbone, which is significantly less compared to today’s ICOs’ rewarding their founders between 20–50% of the tokens distributed. Another trait that sets Energi apart from ICOs is they give an on-going 10% allocation through each block reward, rather than rewarding the founders up-front.
2. What are the Fundamentals of Energi?
1 minute block times and a 2 megabyte block size limit provide Energi with a vast transaction capacity for regular on-chain transactions. This allows for plenty of space on the blockchain for extremely fast transactions with very low fees. Energi features a powerful on-chain scaling solution with a system of incentivized full nodes called Energi Masternodes. A Masternode is a full node backed by 1,000 NRG collateral that provides level 2 scalability to the Energi Cryptocurrency. 40% of the emissions of Energi is allocated to Masternodes, providing an extremely strong incentive to grow the number of full nodes and scalability of the network.
A key feature of Energi is its powerful treasury system. Energi makes up to 40% of the emissions available to the treasury, to be utilized in a manner that provides maximum benefit. Treasury allocation is decentralized, allowing for submitted proposals from anyone, to be voted on by Masternodes and paid out from the emissions. Energi has a 14 day treasury cycle, allowing quick payments for proposal authors and contributors, as well as strategic responsiveness to effective proposals. Energi is guided by the principle that every dollar spent from its funding model should yield more than one dollar of value in return. Thanks to a 14 day treasury cycle, the Energi team is able to measure results and respond quickly to changes in strategy.
The Energi Treasury is a decentralized governance model designed with Masternodes as caretakers, with voting rights on how to best utilize treasury funding. This governance model reduces risk by allowing participation from everyone who holds 1,000 NRG as a Masternode. In this way, the Energi community can work together on how to best build the strategic direction of Energi.
Energi Cryptocurrency has a simple rate of inflation at 1 million coins per month with no maximum cap. This ensures consistency in funding allocation, Masternode rewards, and PoS rewards, making the economics of the cryptocurrency more understandable for everyone who chooses to participate in Energi. No coin supply limit ensures that Energi is prepared for the long term, avoiding “bubble” economics caused by dramatic early inflation that in most coins only serves to benefit founders ahead of increased adoption.
Energi conducted a fair launch on April 14, 2018 with no ICO and no premine. Prior to launch, the Energi team gave a specific time and date for the launch of its main net, which its vibrant community eagerly awaited, so that mining could begin fairly, again avoiding centralization among the coin founders (It's important to note that Energi has transitioned from Proof-of-Work consensus to a Proof-of-Stake consensus). Energi Masternode payments were designed to begin at block 216000, which occurred on September 18, 2018, almost 160 days after launch. This ensured time to list Energi on exchanges, and to grow the community, encouraging fair and equitable distribution before the extremely powerful Masternode rewards began. It is all too common for Masternode coins to feature a premine, which has the effect of centralizing distribution among the founders and early adopters. From 2018 to 2020, Energi distributed nearly 4 million coins to users who contributed to spreading awareness of the project with social media activities about Energi, such as tweets, follows, and subscriptions on all major social media platforms.
Decentralized governance with Masternodes helps to ensure everyone is able to participate in Energi and help guide the project to achieve the best results. The change to the requirement to run a Masternode, from 10 000 NRG to 1 000 NRG, has allowed more people to be involved and boosted decentralization for the whole project.
Long Term Vision
All of the above features seamlessly work together in concert, to ensure that Energi is prepared for the long term. Rather than try to closely find a niche in the market, Energi is prepared to adapt and overcome all challenges for many years to come. Energi’s use case is that of a traditional cryptocurrency, such as Bitcoin. However, Energi’s strategy is to excel by avoiding the pitfalls of previous projects, while further utilizing and improving upon the most powerful ideas in the cryptocurrency space.
3. Coin Specs
Ticker: NRG Block time: 1 minute. Hashing Algorithm: Dagger-Hashimoto (similar to Ethereum). Masternode requirements: 1,000 Energi. Treasury cycle: Every 14 days. Approximately 1 million Energi will be released per month. The allocations can be observed easily as “10/10/40/40.” 10% will go to the Energi Backbone. 10% to the PoS participants 40% to Masternodes. 40% to the Treasury. Thus, for every block, allocations are: 2.28 Energi to the Backbone, 2.28 Energi to the PoS participants, 9.14 Energi to the Treasury, and 9.14 Energi to Masternodes. Since Treasury allocations are paid in two-week cycles, they are made in lump sums of approximately 184,000 Energi every 14 days. In order to allow for widespread distribution of Energi before Masternode payments began, Masternode rewards were delayed until day 150. This was to allow the airdrop campaign to be completed and ensure a large amount of NRG is spread out through the community. Until that point, Masternode rewards were redirected to the Treasury. Thus for the first 5 months, the Treasury gained approximately 368,000 Energi every two weeks (about 800k Energi per month). The airdrop campaign was designed to release ~4 million Energi to the community.
Bitcoin Average hashrate (hash/s) per day Chart. Transactions Block Size Sent from addresses Difficulty Hashrate Price in USD Mining Profitability Sent in USD Avg. Transaction Fee Median Transaction Fee Block Time Market Capitalization Avg. Transaction Value Median Transaction Value Tweets GTrends Active Addresses Top100ToTotal Fee in Reward Hash functions in bitcoin. In the bitcoin protocol, hash functions are part of the block hashing algorithm which is used to write new transactions into the blockchain through the mining process ... A distributed hash table (DHT) is a class of a decentralized distributed system that provides a lookup service similar to a hash table: (key, value) pairs are stored in a DHT, and any participating node can efficiently retrieve the value associated with a given key. Responsibility for maintaining the mapping from keys to values is distributed among the nodes, in such a way that a change in the ... What is a Bitcoin Hash? Bitcoin’s blockchain uses SHA-256 (Secure Hash Algorithm). In 2001, SHA-256 was developed by the National Security Agency (NSA) in the USA. Bitcoin’s proof of work algorithm is based on SHA-256. Using this, Bitcoin miners solve computationally difficult math problems to add blocks into the blockchain. Bitcoin blocks are added by verifying the hashes on a lottery ... Bitcoin est donc le réseau le plus puissant au monde. Cela tombe bien puisque pour vérifier les transactions et assurer falsifiabilité de la blockchain, Bitcoin fonctionne par Proof-of-Work. Cad qu’aujourd’hui Bitcoin est le seul et unique réseau sécurisé dans le monde des cryptomonnaies. C’est pour cela que l’on peut avoir ...
Hash Pointers and Data Structures - Bitcoin and Cryptocurrency Technologies Part 1 - Introduction to Crypto and Cryptocurrencies Learn about cryptographic building blocks ("primitives") and reason ... Eine einfache, Schritt für Schritt Erklärung zu Hashfunktionen und wie wir sie, meist ohne es zu wissen, täglich mehrfach verwenden. Ohne zuviel technischen ... 1. Crack 95 characters per position, length 8 plaintext in 10 minutes 2. Test 12,000,000 million plaintexts per second 3. Based on time memory tradeoff algor... How Bitcoin Works Under the Hood - Duration: 22:25. CuriousInventor Recommended for ... Setting Up the Hash Table Project - Duration: 8:16. Paul Programming 197,464 views. 8:16. Hash Table (Part ... What is Hashing on the Blockchain? https://blockgeeks.com/guides/what-is-hashing/ Cryptographic hashing is a key feature in the security and efficiency of bl...