BigInteger (Java Platform SE 7 ) - Oracle

Dragonchain Great Reddit Scaling Bake-Off Public Proposal

Dragonchain Great Reddit Scaling Bake-Off Public Proposal

Dragonchain Public Proposal TL;DR:

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

Hello Reddit and Ethereum community!

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

Executive summary

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

Response and PoC

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

Live Demo

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

Source Code

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

Scaling

How it works & scales

Architectural Scaling

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

Economic Scaling

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

Scaled Deployment

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

Flexibility in Scaling

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

Cost

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

Getting Started

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

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

API Documentation

APIs (on chain & off)

SDK Source

Nobody’s Perfect

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

Costs and resources

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

Requirements

Scaling

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

Decentralization

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

Usability Scaling solutions should have a simple end user experience.

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

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

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

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

Bonus Points

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

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

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

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

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

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

Bonus

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

TIME

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

Dragon Den

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

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

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

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

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

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

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

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

Other Considerations

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

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

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

Conclusion

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

Disney Releases Blockchain Platform as Open Source

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

Open Source

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

Dragonchain Foundation

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

Collapse of MakerDAO Keepers: $4.5M lost & how to become a Keeper to earn 13%+ liquidation penalties by providing liquidity to MakerDAO Keeper Pool.

TL;DR - join waitlist for MakerDAO Keeper Pool to earn yield on DAI/ETH/USDC/USDT/Chai/sUSD/cDAI from liquidation penalties and ETH/DAI arbitrage profits earned in collateral auctions by the Keeper Pool (zero fee pool, non-custodial of course:) - https://docs.google.com/forms/d/e/1FAIpQLSfekQcjT5up5Uh2W_C2W0U5zJ5miLd5ott_87CW8-dDH75TZg/viewform
________
Unfortunately, many of us became victims of MakerDAO collateral auctions market. This market was brought to its knees today, resulting in:
1) Losses affecting some of the MakerDAO Vault holders (borrowers of DAI from the Multi-Collateral DAI system), and
2) Losses affecting 100% of MKR token holders, - minting enough MKR and selling them for DAI to cover the missing DAI in the system. The auctions will begin on Wednesday, March 18, 2020.
For the last 14 hours I've been focusing on determining the root cause of the problem, and determining WHAT CAN I DO? to prevent this collapse from ever happening again.
Collapse of the MakerDAO Auctions.
Losses above is a result of a short-term monopoly in the auction market of collateral liquidation of MakerDAO vaults becoming under-collateralized with price of collateral (ETH, BAT) on the decline. This monopoly existed for ~3.5 hours this morning, allowing a single Keeper to buy close to $4.5M worth of ETH in exchange for ~0 DAI + gas fees.
The collapse negatively affected two classes of market participants:
1) Victim class #1: MCD Vault holders who were being liquidated between ~10am EST until ~1pm EST
Please meet Paul, one of the people who lost money. Read his story:
https://www.reddit.com/MakerDAO/comments/fhn1qn/complete_vault_liquidation_no_eth_left/
If you still didn't get it, please meet BitBurst who lost his life savings today:
https://www.reddit.com/MakerDAO/comments/fhs7kp/just_got_100_liquidated_with_my_1713_eth_cdp_fck/
Want more? One of us with a Reddit handle 'phyzled' is calling for help:
https://www.reddit.com/MakerDAO/comments/fhrjxp/help_complete_liquidation/
Even 'Bitcoin_Bender' is threatened. Not just him but his life and his family are going downhill:
https://www.reddit.com/MakerDAO/comments/fhupn8/total_liquidation_mkr_holders_should_take/
2) Victim class #2: MKR holders who will be diluted on Wednesday, March 18th as a result of Flop auction - minting new MKR tokens and selling them at an auction until the auction proceeds cover the missing DAI ($4.5M DAI at the time of this writing).
WHAT HAPPENED?
Prior to ~10am EST, there were a lot of Keepers bidding against each other for collateral at 13% liquidation penalty. Keepers are software bots which monitor Vaults and participate in auctions for collateral of borrowers who became under-collateralized. Operators of such bots are incentivized with mandatory 13% liquidation penalty imposed on Vault collateral upon liquidation.
https://docs.makerdao.com/auctions/the-auctions-of-the-maker-protocol
https://docs.makerdao.com/smart-contract-modules/collateral-module/flipper-detailed-documentation
However, after 10am EST, a single liquidation auction bot was able to bid at 0 DAI (or slightly above) PER EACH COLLATERAL ETH BEING AUCTIONED, AND WIN THE AUCTION. As a result, this Keeper was effectively steal $4M worth of ETH collateral because the auction was designed to raise at least 4M DAI in exchange for the ETH that was auctioned during liquidations, however all except one Keepers stopping their operations, there was only one bidder. Any price above 0 would be accepted. As a result, but the Vault holders who supposed to receive some ETH back, never got any ETH back > making the effective liquidation penalty to over 50% instead of 13%.
Why did the Keeper's market collapse? Why most Keepers stop operating?
Unfortunately, most Keepers stopped operating this morning due to the following reasons:
Root cause #1: Catastrophic liquidity crunch. Keepers simply ran out of DAI to bid in the collateral auctions due to
1.a I believe some Keepers were unable to continue Keeper operations due to inability to liquidate ETH fast enough for DAI.
1.b Some Keepers shut down due to squeeze (bought ETH for 170 DAI, and hours later can only sell for 130 DAI at a loss - which is way more than 13% liquidation penalty).
Root cause #2: Network congestion. This brought many Keepers to its knees. Even with liquidity, many were unable participating in auctions due to stuck transactions & high gas costs. In addition, issues like longer client sync times + some Ethereum clients (like Parity) sufferring from known problems of keeping transactions stuck in Mempool for a very, very long time, amplified this problem.
PROPOSED SOLUTION - MakerDAO Keeper Pool.
Why don't we pool our liquidity (non-custodial pool, Uniswap-style) and give Keepers some competition!?
To prevent more people from losing their funds, I decided to fund development of a MakerDAO Keeper Pool, which will allow anybody to become a Keeper and participate in liquidations of collateral (to earn 13% liquidation penalty).
Background: During today’s Community Call (5 hours and still ongoing at the time of this writing), multiple members of the Maker community stressed importance of increasing # of Keepers servicing the MCD system in order to prevent yet another collapse of the Keepers market as it happened today.
To improve maturity of the Keepers market, increase the collective liquidity used by Keeper’s, engineers at Protofire.io (developers of MakerDAO governance dashboard https://mkrgov.science, Solhint - Solidity Linter https://github.com/protofire/solhint, maintainers of Gnosis Conditional Exchange https://github.com/protofire/gnosis-conditional-exchange) and risk team + engineering team at Atomica.org (developers of Atomica.org/unwind/) launched emergency efforts to ship one or more of the following ASAP:
  1. Web-based MakerDAO Keeper. Perform liquidations of 3rd party collateral from your browser as a Keeper. Earn 13% liquidation penalty.
  2. Open Source Keeper Templates. Run your own Keeper Bot on AWS - 1-click Installer for a MakerDAO Keeper Bot (open source Amazon Machine Image).
  3. Non-custodial MakerDAO Keeper Pool. Earn yield on DAI/ETH/USDC/USDT/cDAI/Chai from a pool running multiple Keeper bots servicing MakerDAO ecosystem. Join/Exit/Add/Withdraw DAI/ETH/USDC/USDT/cDAI/Chai, and earn 100% of liquidation penalties earned by the Keeper (zero fee pool).
Ultimately, we aim to:
- Upgrade the MakerDAO Keeper Pool to be a Keeper of Last Resort. Think of a Keeper backed by on-chain, guaranteed liquidity AND configured to participate in auctions with bids of at least 0.85 of the current ETH-DAI market price, as reported by oracles. So long as the Keeper Pool is operating, no Keeper will be able to take advantage of the system and cause yet another collapse of the MakerDAO Collateral Auction markets.
- Ship 3rd party JavaScript / npm library + Android/iOS SDKs to embed Web-based Keeper or MakerDAO Keeper Pool join/exit/add/withdraw liquidity into your own dApp, protocol, product or service.
If anyone is interested in developing/observing/joining MakerDAO Keeper Pool (for example by running their own Keeper using hardened AWS AMI template, or by providing liquidity (DAI/ETH/USDC/USDT/cDAI/Chai) to a Keeper Pool) - feel free to join our working group working to ship a MakerDAO Keeper Pool ASAP - https://docs.google.com/forms/d/e/1FAIpQLSfekQcjT5up5Uh2W_C2W0U5zJ5miLd5ott_87CW8-dDH75TZg/viewform
Its not about what DeFi can do for you. It is about what YOU can do for DeFi.
submitted by renatco to ethereum [link] [comments]

RiB Newsletter #14 – Are We Smart (Contract) Yet?

We’re seeing a bunch of interesting Rust blockchain and crypto projects, so this month the “Interesting Things” section is loaded up with news, papers, and project links.
This month, Elrond, appeared on our radar with the launch of their mainnet. Although not written in Rust, it runs Rust smart contracts on its Arwen WASM VM, which itself is based on the Rust Wasmer VM. Along with NEAR, Nervos, and Enigma (and probably others), this continues an encouraging trend of blockchains enabling smart contracts in Rust. See the “Interesting Things” section for examples of Elrond’s Rust contracts.
Rust continues to be popular for research into zero-knowledge proofs, with Microsoft releasing Spartan, a zk-SNARK system without trusted setup.
In RiB news, we published a late one-year anniversary blog post. It has some reflection on the changes to, and growth of, RiB over the last year.
The Awesome Blockchain Rust project, which is maintained by Sun under the rust-in-blockchain GitHub org, has received a stream of updates recently, and is now published as the Awesome-RiB page on rustinblockchain.org.
It’s a pretty good resource for finding blockchain-related Rust projects, with links to many of the more prominent and mature projects noted in the RiB newsletter. It could use more eyes on it though.

Project Spotlight

Each month we like to shine a light on a notable Rust blockchain project. This month that project is…
ethers.rs
ethers.rs is an Ethereum & Celo library and wallet implementation, implemented as a port of the ethers.js library to Rust.
Ethereum client programming is usually done in JavaScript with either web3.js or ethers.js, with ethers.js being the newer of the two. These clients communicate to an Ethereum node, typically via JSON-RPC (or, when in the browser, via an “injected” client provider that follows EIP-1193, like MetaMask).
ethers.rs then provides a strongly-typed alternative for writing software that interacts with the Ethereum network.
As of now it is only suited for non-browser use cases, but if you prefer hacking in Rust to JavaScript, as some of us surely do, it is worth looking into for your next Ethereum project.
The author of ethers.rs, Georgios Konstantopoulos, accepts donations to sponsor their work.
Note that there is also a Rust alternative to web3.js, rust-web3.

Interesting Things

News

Blog Posts

Papers

Projects

Podcasts and Videos


Read more: https://rustinblockchain.org/newsletters/2020-08-05-are-we-smart-contract-yet/
submitted by Aimeedeer to rust [link] [comments]

Why did I build AmputatorBot?

Why did I build AmputatorBot?
AmputatorBot.com | Remove AMP from URLs in just one click! - More info
Open-sourced on GitHub - More info
Summon AmputatorBot by mentioning it like this: u/AmputatorBot

Why AMP is a threat to the Open Web

What is AMP?
AMP is an open-source web component framework developed by the AMP Open Source Project, first announced by Google in 2015 as a reaction to Facebook’s Instant Articles and Apple News. While it was originally aimed at accelerating mobile pages (hence AMP), it’s now a much broader project aimed at improving the UX of websites, stories, ads and mail. The AMP framework consists of three components: AMP HTML, which is standard HTML markup with web components; AMP JavaScript, which manages resource loading; and AMP caches, which serves and validates AMP pages.
In plain English: AMP is Google’s attempt at making pages (and more) faster. They did a good job, pages built with the AMP framework will normally load faster. However, as this article explains, you won’t notice much of a difference unless the AMP library is served using the AMP cache, but more on that later.
The controversies with cached AMP pages
The AMP format is itself not much of a problem. In fact, we should applaud search engines that give ranking preference to fast-loading pages like AMP, but four aspects of its implementation are flawed:
  1. Google mobile Search’s Top Stories carousel has a premium position above of all other results, which is only accessible for AMP pages. These pages have to use a technology that was build and maintained mostly by Google (of the top 10 contributors to the AMP project on GitHub, 9 are Google employees), are then served by Google from their infrastructure and placed within a Google controlled user experience. And since this carousel generates a lot of clicks and revenue, publishers are left no choice but to embrace AMP. This has the effect of further reinforcing Google’s dominance of the Web. Fortunately, Google has announced that it's working on opening up the Top Stories carousel to non-AMP pages in 2021.
  2. The biggest performance boost doesn’t come from the AMP framework, but from preloading the page. It begs the question: Should preloading really be exclusive to AMP? They could introduce a way for publishers to allow or disallow preloading and if Google sees fit, they could preload those pages too, alongside AMP.
  3. When a user navigates from Google to a piece of content Google has recommended (or when a user clicks on a shared cached AMP link), they are, unwittingly, remaining within Google’s ecosystem and the publisher’s domain is obscured by the google.com/amp prefix. To work around this Google introduced Signed HTTP Exchanges ([Draft], [1], [2]), a web-standard that allows the browser to display the original site's URL, instead of the actual one (the one with the google.com/prefix). This would solve the original issue, but while doing so it introduced new ones (e.g. it obfuscates the fact that they're delivering the AMP page you're visiting). Interestingly enough, Google's Chrome already has support for this technology, but parties not involved with AMP are not so enthusiastic: Mozilla has deemed it a harmful web standard [2], and Apple has taken a similar stance.
  4. Google’s entire business model is about collecting as much personal data as possible, AMP is just another tool to do so. As described in Google’s Support article:
“When you use the Google AMP Viewer, Google and the publisher that made the AMP page may each collect data about you.”
The controversies with non-cached AMP pages
To be clear, the above flaws are only with AMP pages cached by Google (or another party like Bing or Cloudflare) but there are also plenty of pages simply utilizing the AMP framework, recognized by URLs such as bbc.com/news/amp/. However, these are also problematic, mainly because there's only a small performance improvement when AMP pages aren't cached and AMP pages tend to be less feature-rich and less diverse than their originals. And in some edge cases, it breaks stuff.
One could argue that the more popular the AMP framework becomes, the more AMP threatens the open web. That said, it should be clear that the biggest problem lies with the cached AMP pages.
AMP is open source, but that doesn't make it holy. Or as Ferdy Christant puts it quite nicely in his blog:
Google’s main defense is that AMP is open source. Which isn’t just a weak defense, it’s no defense at all. I can open source a plan for genocide. The term “open source” is meaningless if the thing that is open source is harmful.
Just so we’re clear, I’m not claiming Google or the AMP project is evil (hell, they might even have good intentions!), but the fact is that AMP and it's implementation have some major flaws that threaten the Open Web. And as long as that's the case, AmputatorBot will be there to remove AMP from your URLs.
AmputatorBot scans for AMP pages on Reddit and replies with the canonical version
Learn more
Up next for the nerds among us:
  • AmputatorBot.com
  • Automatic working subreddits
  • Non-working subreddits
  • Changelog
  • Opt-out & opt-back-in
  • Browser extension
  • Support the project by donating, giving feedback, summoning the bot or spreading the word

AmputatorBot.com

Remove AMP in just one click with www.AmputatorBot.com! This is a free online tool (no ads) to remove AMP from your URLs. All you have to do is to copy paste an AMP URL, click the conversion-button and that's all! For more (background) info, check out this post. Here's a quick (no but literally) demo:
A demo of the AMP-removal process over at AmputatorBot.com
Alternatively, you can do it even quicker by doing this:
https://amputatorbot.com/?https://www.google.com/amp/s/electrek.co/2018/06/19/tesla-model-3-assembly-line-inside-tent-elon-musk/amp/
It's build up like this:
https://amputatorbot.com + /? + https://www.google.com/amp/s/electrek.co/2018/06/19/tesla-model-3-assembly-line-inside-tent-elon-musk/amp/

Automatic working subreddits

u/amputatorbot currently works automatically in a select number of subreddits: Afghanistan, Africa, against5G, againstRFID, amputatorbot, anime_titties, Argentina, Assyria, Azerbaijan, Bangladesh, Bosnia, Brasil, Bulgaria, Business, CenturyClubStairs, Chile, Chodi, chrome, Colombia, conspiracy, CorpFree, cyberpunk, Cuba, DeAmazon, DebunkThis, DeFacebook, deGoogle, deMicrosoft, economy, Ecuador, entertainment, Environment, europe, Europe, europrivacy, FakeNews, Features, Fijian, firefox, France, freesoftware, gamernews, Germany, Greece, Guyana, hacking, helpmefind, hockey, HumanRights, Hungary, ID_news, indiaspeaks, initFreedom, Iranian, Iraq, Israel, Italy, Kazakhstan, Kerala, Kurdistan, LeopardsAteMyFace, LevantineWar, MachineLearning, Malaysia, Mexico, MiddleEastNews, MideastPeace, Moldova, Nepal, NewsOfTheWeird, Nicaragua, NorthKoreaNews, Oceania, OnGuardForThee, Pakistan, Palestine, pcgaming, PeerTube, Philippines, Piracy, Poland, praisetheeditor, privacy, PuertoRico, robotics, Russia, Scotland, security, selfhosted, seo, Serbia, singapore, socialism, spacex, Spain, suckless, Switzerland, Syria, tech, technology, TechnologyDetox, test, TrueCrime, TrueCrimeDiscussion, TrueReddit, Turkey, Turkey, Ukraina, Ukraine, UkrainianConflict, UnresolvedMysteries, upliftingnews, Uruguay, USA, Venezuela, web_design, Westpapua, whatisthisthing, worldnews, Yemen and YemeniCrisis.
Feel free to hit me up with suggestions for subreddits to add!
You can summon the bot almost everywhere else by typing: u/AmputatorBot, more info here.

Non-working subreddits

AmputatorBot doesn't work in these subreddits android, androiddev, armenia, AskHistorians, askscience, AskScienceDiscussion, audio, australia, awfuleverything, bayarea, beer, belgium, bitcoin, books, canada, CanadaPolitics, cars, CCW, childfree, China, collapse, conservative, Cringetopia, croatia, CryptoCurrency, DataHoarder, disneyvacation, economics, ELI5, facepalm, flying, Futurology, gadgets, Games, gaming, gatesopencomeonin, geopolitics, Georgia, GlobalTalk, google, history, India, insaneparents, insanepeoplefacebook, instantkarma, iphone, iran, ireland, kitchener, korea, meme, moviedetails, movies, news, newzealand, nextfuckinglevel, nottheonion, oklahoma, pcmasterrace, Pete_Buttigieg, Philosophy, pihole, PoliticalDiscussion, politics, popheads, programming, raisedbynarcissists, rareinsults, Romania, science, SeattleWA, Sikh, SouthAfrica, space, survivor, television, Thailand, thenetherlands, TikTokCringe, TIL_Uncensored, todayilearned, trashy, tumblr, TwoXChromosomes, ukpolitics, unitedkingdom, unpopularopinion, USANews, warplaneporn, WatchPeopleDieInside, wellthatsucks, whatcouldgowrong, worldevents, worldpolitics, YouShouldKnow and almost all subreddits moderated by u/BotDefense or u/BotTerminator for diverse reasons. When you summon the bot there, you'll receive a DM with the canonical URL instead.p
If you're moderating a subreddit that is incorrectly listed here or if you would like AmputatorBot to work in your subreddit that's using u/BotDefense or u/BotTerminator please contact me.

Changelog

Check out the changelog here. Latest update: 22/08/2020

Opt out & opt back in

The bot works automatically in the subreddits mentioned above and manually using mentions.
Opt out: If you want to prevent the bot from replying to your comments and submissions, click here to opt out.
Opt back in: Did you opt-out and regret it? NP! Click here to opt back in.
Note: If you want to opt out from AmputatorBot on Twitter, please contact me or block it.

Browser-extension

Check out this browser-extension by Daniel Aleksandersen: 'Redirect AMP to HTML', it makes it that every time you click an AMP page, you will be redirected to the canonical page instead. In other words, it does the the same as u/AmputatorBot and AmputatorBot.com, but fully automatic. I can't recommend this one enough!

Support the project

.. By summoning the bot: If you've spotted an AMP URL on Reddit and u/AmputatorBot seems absent, you can summon the bot by mentioning u/AmputatorBot in a reply to the comment or submission containing the AMP URL. You'll receive a confirmation through PM. For more details, check out this post!
.. By giving feedback: Most of the new features were made after suggestions from you guys, so hit me up if you have any feedback! You can contact me on Reddit, fill an issue or make a pull request.
.. By sponsoring: The bot and website cost approximately €8.26 a month to host and while that might not seem like much, it adds up. All donations will be used ONLY to pay for hosting. You can specify any amount you want, but please keep in mind that I only want to try to cover some of the costs. Thank you so much! - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=EU6ZFKTVT9VH2
.. By spreading the word: In the end, the only goal of AmputatorBot is to allow people to have an informed choice. You can help by spreading the word in whatever way you deem the most appropriate.

From the bottom of my heart, thank you so much for the tremendous support you've given me and AmputatorBot <3

https://preview.redd.it/fzhy8jedu6e51.png?width=3890&format=png&auto=webp&s=581561e0e267bb53ee3961a5e894633f8d6ff73f
submitted by Killed_Mufasa to AmputatorBot [link] [comments]

Collapse of MakerDAO Auctions: $4.5M lost & how to become a Keeper to earn 13%+ liquidation penalties by providing liquidity to MakerDAO Keeper Pool.

TL;DR - join waitlist for MakerDAO Keeper Pool to earn yield on DAI/ETH/USDC/USDT/Chai/sUSD/cDAI from liquidation penalties and ETH/DAI arbitrage profits earned in collateral auctions by the Keeper Pool (zero fee pool, non-custodial of course:) - https://docs.google.com/forms/d/e/1FAIpQLSfekQcjT5up5Uh2W_C2W0U5zJ5miLd5ott_87CW8-dDH75TZg/viewform
________
Unfortunately, many of us became victims of MakerDAO collateral auctions market. This market was brought to its knees today, resulting in:
1) Losses affecting some of the MakerDAO Vault holders (borrowers of DAI from the Multi-Collateral DAI system), and
2) Losses affecting 100% of MKR token holders, - minting enough MKR and selling them for DAI to cover the missing DAI in the system. The auctions will begin on Wednesday, March 18, 2020.
For the last 14 hours I've been focusing on determining the root cause of the problem, and determining WHAT CAN I DO? to prevent this collapse from ever happening again.
Collapse of the MakerDAO Auctions.
Losses above is a result of a short-term monopoly in the auction market of collateral liquidation of MakerDAO vaults becoming under-collateralized with price of collateral (ETH, BAT) on the decline. This monopoly existed for ~3.5 hours this morning, allowing a single Keeper to buy close to $4.5M worth of ETH in exchange for ~0 DAI + gas fees.
The collapse negatively affected two classes of market participants:
1) Victim class #1: MCD Vault holders who were being liquidated between ~10am EST until ~1pm EST
Please meet Paul, one of the people who lost money. Read his story:
https://www.reddit.com/MakerDAO/comments/fhn1qn/complete_vault_liquidation_no_eth_left/
If you still didn't get it, please meet BitBurst who lost his life savings today:
https://www.reddit.com/MakerDAO/comments/fhs7kp/just_got_100_liquidated_with_my_1713_eth_cdp_fck/
Want more? One of us with a Reddit handle 'phyzled' is calling for help:
https://www.reddit.com/MakerDAO/comments/fhrjxp/help_complete_liquidation/
Even 'Bitcoin_Bender' is threatened. Not just him but his life and his family are going downhill:
https://www.reddit.com/MakerDAO/comments/fhupn8/total_liquidation_mkr_holders_should_take/
2) Victim class #2: MKR holders who will be diluted on Wednesday, March 18th as a result of Flop auction - minting new MKR tokens and selling them at an auction until the auction proceeds cover the missing DAI ($4.5M DAI at the time of this writing).
WHAT HAPPENED?
Prior to ~10am EST, there were a lot of Keepers bidding against each other for collateral at 13% liquidation penalty. Keepers are software bots which monitor Vaults and participate in auctions for collateral of borrowers who became under-collateralized. Operators of such bots are incentivized with mandatory 13% liquidation penalty imposed on Vault collateral upon liquidation.
https://docs.makerdao.com/auctions/the-auctions-of-the-maker-protocol
https://docs.makerdao.com/smart-contract-modules/collateral-module/flipper-detailed-documentation
However, after 10am EST, a single liquidation auction bot was able to bid at 0 DAI (or slightly above) PER EACH COLLATERAL ETH BEING AUCTIONED, AND WIN THE AUCTION. As a result, this Keeper was effectively steal $4M worth of ETH collateral because the auction was designed to raise at least 4M DAI in exchange for the ETH that was auctioned during liquidations, however all except one Keepers stopping their operations, there was only one bidder. Any price above 0 would be accepted. As a result, but the Vault holders who supposed to receive some ETH back, never got any ETH back > making the effective liquidation penalty to over 50% instead of 13%.
Why did the Keeper's market collapse? Why most Keepers stop operating?
Unfortunately, most Keepers stopped operating this morning due to the following reasons:
Root cause #1: Catastrophic liquidity crunch. Keepers simply ran out of DAI to bid in the collateral auctions due to
1.a I believe some Keepers were unable to continue Keeper operations due to inability to liquidate ETH fast enough for DAI.
1.b Some Keepers shut down due to squeeze (bought ETH for 170 DAI, and hours later can only sell for 130 DAI at a loss - which is way more than 13% liquidation penalty).
Root cause #2: Network congestion. This brought many Keepers to its knees. Even with liquidity, many were unable participating in auctions due to stuck transactions & high gas costs. In addition, issues like longer client sync times + some Ethereum clients (like Parity) sufferring from known problems of keeping transactions stuck in Mempool for a very, very long time, amplified this problem.
PROPOSED SOLUTION - MakerDAO Keeper Pool.
Why don't we pool our liquidity (non-custodial pool, Uniswap-style) and give Keepers some competition!?
To prevent more people from losing their funds, I decided to fund development of a MakerDAO Keeper Pool, which will allow anybody to become a Keeper and participate in liquidations of collateral (to earn 13% liquidation penalty).
Background: During today’s Community Call (5 hours and still ongoing at the time of this writing), multiple members of the Maker community stressed importance of increasing # of Keepers servicing the MCD system in order to prevent yet another collapse of the Keepers market as it happened today.
To improve maturity of the Keepers market, increase the collective liquidity used by Keeper’s, engineers at Protofire.io (developers of MakerDAO governance dashboard https://mkrgov.science, Solhint - Solidity Linter https://github.com/protofire/solhint, maintainers of Gnosis Conditional Exchange https://github.com/protofire/gnosis-conditional-exchange) and risk team + engineering team at Atomica.org (developers of Atomica.org/unwind/) launched emergency efforts to ship one or more of the following ASAP:
  1. Web-based MakerDAO Keeper. Perform liquidations of 3rd party collateral from your browser as a Keeper. Earn 13% liquidation penalty.
  2. Open Source Keeper Templates. Run your own Keeper Bot on AWS - 1-click Installer for a MakerDAO Keeper Bot (open source Amazon Machine Image).
  3. Non-custodial MakerDAO Keeper Pool. Earn yield on DAI/ETH/USDC/USDT/cDAI/Chai from a pool running multiple Keeper bots servicing MakerDAO ecosystem. Join/Exit/Add/Withdraw DAI/ETH/USDC/USDT/cDAI/Chai, and earn 100% of liquidation penalties earned by the Keeper (zero fee pool).
Ultimately, we aim to:
- Upgrade the MakerDAO Keeper Pool to be a Keeper of Last Resort. Think of a Keeper backed by on-chain, guaranteed liquidity AND configured to participate in auctions with bids of at least 0.85 of the current ETH-DAI market price, as reported by oracles. So long as the Keeper Pool is operating, no Keeper will be able to take advantage of the system and cause yet another collapse of the MakerDAO Collateral Auction markets.
- Ship 3rd party JavaScript / npm library + Android/iOS SDKs to embed Web-based Keeper or MakerDAO Keeper Pool join/exit/add/withdraw liquidity into your own dApp, protocol, product or service.
If anyone is interested in developing/observing/joining MakerDAO Keeper Pool (for example by running their own Keeper using hardened AWS AMI template, or by providing liquidity (DAI/ETH/USDC/USDT/cDAI/Chai) to a Keeper Pool) - feel free to join our working group working to ship a MakerDAO Keeper Pool ASAP - https://docs.google.com/forms/d/e/1FAIpQLSfekQcjT5up5Uh2W_C2W0U5zJ5miLd5ott_87CW8-dDH75TZg/viewform
Its not about what DeFi can do for you. It is about what YOU can do for DeFi.
submitted by renatco to defi [link] [comments]

AMA: Ask Mike Anything

Hello again. It's been a while.
People have been emailing me about once a week or so for the last year to ask if I'm coming back to Bitcoin now that Bitcoin Cash exists. And a couple of weeks ago I was summoned on a thread called "Ask Mike Hearn Anything", but that was nothing to do with me and I was on holiday in Japan at the time. So I figured I should just answer all the different questions and answers in one place rather than keep doing it individually over email.
Firstly, thanks for the kind words on this sub. I don't take part anymore but I still visit occasionally to see what people are talking about, and the people posting nice messages is a pleasant change from three years ago.
Secondly, who am I? Some new Bitcoiners might not know.
I am Satoshi.
Just kidding. I'm not Satoshi. I was a Bitcoin developer for about five years, from 2010-2015. I was also one of the first Bitcoin users, sending my first coins in April 2009 (to SN), about 4 months after the genesis block. I worked on various things:
You can see a trend here - I was always interested in developing peer to peer decentralised applications that used Bitcoin.
But what I'm best known for is my role in the block size debate/civil war, documented by Nathaniel Popper in the New York Times. I spent most of 2015 writing extensively about why various proposals from the small-block/Blockstream faction weren't going to work (e.g. on replace by fee, lightning network, what would occur if no hard fork happened, soft forks, scaling conferences etc). After Blockstream successfully took over Bitcoin Core and expelled anyone who opposed them, Gavin and I forked Bitcoin Core to create Bitcoin XT, the first alternative node implementation to gain any serious usage. The creation of XT led to the imposition of censorship across all Bitcoin discussion forums and news outlets, resulted in the creation of this sub, and Core supporters paid a botnet operator to force XT nodes offline with DDoS attacks. They also convinced the miners and wider community to do nothing for years, resulting in the eventual overload of the main network.
I left the project at the start of 2016, documenting my reasons and what I expected to happen in my final essay on Bitcoin in which I said I considered it a failed experiment. Along with the article in the New York Times this pierced the censorship, made the wider world aware of what was going on, and thus my last gift to the community was a 20% drop in price (it soon recovered).

The last two years

Left Bitcoin ... but not decentralisation. After all that went down I started a new project called Corda. You can think of Corda as Bitcoin++, but modified for industrial use cases where a decentralised p2p database is more immediately useful than a new coin.
Corda incorporates many ideas I had back when I was working on Bitcoin but couldn't implement due to lack of time, resources, because of ideological wars or because they were too technically radical for the community. So even though it's doesn't provide a new cryptocurrency out of the box, it might be interesting for the Bitcoin Cash community to study anyway. By resigning myself to Bitcoin's fate and joining R3 I could go back to the drawing board and design with a lot more freedom, creating something inspired by Bitcoin's protocol but incorporating all the experience we gained writing Bitcoin apps over the years.
The most common question I'm asked is whether I'd come back and work on Bitcoin again. The obvious followup question is - come back and work on what? If you want to see some of the ideas I'd have been exploring if things had worked out differently, go read the Corda tech white paper. Here's a few of the things it might be worth asking about:
I don't plan on returning to Bitcoin but if you'd like to know what sort of things I'd have been researching or doing, ask about these things.
edit: Richard pointed out some essays he wrote that might be useful, Enterprise blockchains for cryptocurrency experts and New to Corda? Start here!
submitted by mike_hearn to btc [link] [comments]

⚡ Lightning Network Megathread ⚡

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

⚡What is the Lightning Network? ⚡

Explanations:

Image Explanations:

Specifications / White Papers

Videos

Lightning Network Experts on Reddit

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

Lightning Network Experts on Twitter

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

Medium Posts

Learning Resources

Books

Desktop Interfaces

Web Interfaces

Tutorials and resources

Lightning on Testnet

Lightning Wallets

Place a testnet transaction

Altcoin Trading using Lightning

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

Lightning on Mainnet

Warning - Testing should be done on Testnet

Atomic Swaps

Developer Documentation and Resources

Lightning implementations

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

Libraries

Lightning Network Visualizers/Explorers

Testnet

Mainnet

Payment Processors

  • BTCPay - Next stable version will include Lightning Network

Community

Slack

IRC

Slack Channel

Discord Channel

Miscellaneous

⚡ Lightning FAQs ⚡

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

Unanswered Questions

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

Special Thanks and Notes

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

Bitcoin Cash exclusive Crowdsourcing marketplace (pre-launch)

About a month ago we asked our friends to post a link to our landing page and nobody believed us...
Anyway, we are pre-launching to those who have signed up at taskfuture.one! Slowly, in beta, as promised - about a month later.
From the same team that brought you https://freelanceforcoins.com
We are introducing the Bitcoin Cash exclusive Crowdsourcing marketplace Taskopus (think Mechanical Turk, but everyone is accepted, payouts are almost immediate and in BCH! The only way to interact inside is with Bitcoin Cash, because of the fees).
A few teaser screenshots:
(We are a very small team without an ICO or the venture funding, so please excuse our simple designs)
The landing page taskfuture.one was always meant to be a placeholder, hence the "future" in the name. That's why we've never registered taskfuture.com (.one was just cheaper).
The real name of the project is Taskopus, the website is https://taskopus.io and yes, it is still in closed beta.
Today we have invited first 30 users of those signed up on our landing page (taskfuture.one) to download the software and try it themselves and we are waiting for the first feedback.
Over the course of next few weeks we hope to let everybody in.
Ok, if you are feeling adventurous, you can kind of guess where the download is on https://taskopus.io site, it's not exactly secret, but it's not public either. We are still fixing the bugs we discover, so we aren't yet ready for 245192 readers of btc to sign up at once. :)
You can complete tasks, but if you want to create tasks - this function is currently enabled manually on case-by-case basis.
If you want to try it - contact me via PM or at [email protected]
The payments are peer-to-peer inside of Taskopus (hence the downloadable software - we wanted to make sure not to ever see your private key and seed phrase, so that in case we are hacked - your funds are safe on your computer). The Taskopus software is effectively a downloadable Bitcoin Cash wallet with additional functions.
The payments are immediate as soon as buyer is online.
There are a few mechanisms to prevent cheating, you can read about some of them here: https://docs.taskopus.io/w/projects_debt_quota.html
There is a big difference between us and other crowdsourcing sites, though (besides the fact that everybody is accepted, irregardless of age, country, social status, etc... and that all payouts are immediate and final and we don't ever keep your money) and that is with Taskopus you can have a longer relationship with a Worker.
Typical microjobs website treats Workers as completely interchangeable. Do one simple task if you fit our description and get out.
Taskopus is different in that regard. You can build a multi-step selection process for your employees, educate them and give them complex long higher-priced specialized tasks.
For example, say you are a SEO agency and you need to create guest posts on other sites. This involves having to contact many sites and trying to pitch them with your guest article. You can create a selection task to select about a hundred workers for $0.01 each that kind of maybe suit you. After that selection you can take this hundred of users and educate them via the YouTube video about how to do your task and again pay maybe $0.20 each for that. After that you can create a test task so that users can try to pitch some sites with some guest post.
The persistent 10 users who managed to do it can now continue to work for you. Those 10 can now earn maybe $20 for each successful placement, which could translate to maybe $40/hour for those workers. It's a win-win - an agency gets placement for $20 (which is quite cheap) and a worker gets paid like a highly qualified professional, even though he or she was just educated for this particular job (instead of having to have 10 years of experience).
What happens if you lose some of those 10 highly paid workers? Easy! You can just raise the limit on the original task of 100 workers to 200 and so that now you have 100 candidates more. The second task with the YouTube video and test task gets its limit raised to 20 and now you have 10 users more for $11 in total fees. Compare that with hiring and educating 10 people in real life and you should see the benefit immediately.
There is one more big difference - we are also data-driven, and if you want to understand it - you can go here and read the Example about classifying cities.
And there is more. We have JavaScript validation tasks, we have limits (daily, hourly), we have automated invoice payments for when you are offline, we have an REST API, WebHooks, aggregate WebHooks, profile questions, targeting of tasks to users... There's just way too much to explain even if the software looks quite simple.
So, we hope to explain more when we fully launch in some near time, but if for now you want to give our workers some tasks - please contact me via PM or at [email protected] and I'll be happy to provide you with a test access to Task creation functionality.
How are we going to make money? There is a 10% commission that the buyer pays for his task.
See you soon!
EDIT:
Some early feedback from first users:
Very intuitive, but lacking tasks atm.
Fairly good for early beta.
I am very impressed by the smoothness of the app!
great
I like it. The program is simple to use and the design is also simple and not too complicated. I will definitely keep using.
It looks clean. I wish it paid in paypal since I'm not savvy with all the coin stuff, but I'll manage. Also I did a task twice about "is this a city" where it asked the same questions both times, and it's still there, so I'm wary of doing it more in case it's an error.
The first ever platform of this kind that I actually enjoy. Can't wait till it grows more and we get to have some really nice gigs! Thanks for all that you're doing.
I like the intuitive UI of the application and that there are good number of tasks to complete. As someone who has been working online for a while I can say it is a promising project.
The fact that it has it's own software gives it an edge to sites for microwork and so far this has been incredibly easy to use and much more interesting. I'll have a bit of trouble with bitcoin cash since I haven't really used cryptocurrency but hey there's a first time for everything. Will be regularly on Taskopus from now on! Great job!
I love the system, is pretty clean and works great!, just hoping for more tasks!
submitted by FreelanceForCoins to btc [link] [comments]

My growing collection of info about NEO

It can be very time consuming to keep up to date on a single blockchain project let alone multiple ones. If you just heard about NEO a few weeks ago it would be impossible catch up on past occurrences due to high volume of Reddit posts and articles made on the project. I’m going to try and simplify the past, present and future as much as I can into one well thought-out post. I hope I can be helpful to anyone who has been investigating like myself. I will include sources with all of my research.
https://imgur.com/a/NBI7S (img for mobile backround)
Key notes from the White Paper http://docs.neo.org/en-us/
Digital Assets
Digital assets are programmable assets that exist in the form of electronic data. With blockchain technology, the digitization of assets can be decentralized, trustful, traceable, highly transparent, and free of intermediaries. On the NEO blockchain, users are able to register, trade, and circulate multiple types of assets. Proving the connection between digital and physical assets is possible through digital identity. Assets registered through a validated digital identity are protected by law.
Digital Identity
Digital identity refers to the identity information of individuals, organizations, and other entities that exist in electronic form. The more mature digital identity system is based on the PKI (Public Key Infrastructure) X.509 standard. In NEO, we will implement a set of X.509 compatible digital identity standards. This set of digital identity standards, in addition to compatible X.509 level certificate issuance model, will also support Web Of Trust point-to-point certificate issuance model. Our verification of identity when issuing or using digital identities includes the use of facial features, fingerprint, voice, SMS and other multi-factor authentication methods.
Smart Contracts
The NeoContract smart contract system is the biggest feature of the seamless integration of the existing developer ecosystem. Developers do not need to learn a new programming language but use C#, Java and other mainstream programming languages in their familiar IDE environments (Visual Studio, Eclipse, etc.) for smart contract development, debugging and compilation. NEO's Universal Lightweight Virtual Machine, NeoVM, has the advantages of high certainty, high concurrency, and high scalability. The NeoContract smart contract system will allow millions of developers around the world to quickly carry out the development of smart contracts.
Economic Model
NEO has two native tokens, NEOand NeoGas NEO represents the right to manage the network. Management rights include voting for bookkeeping, NEO network parameter changes, and so on. The minimum unit of NEO is 1 and tokens cannot be subdivided. GAS is the fuel token for the realization of NEO network resource control. The NEO network charges for the operation and storage of tokens and smart contracts, thereby creating economic incentives for bookkeepers and preventing the abuse of resources. The minimum unit of GAS is 0.00000001.
Distribution Mechanism
NEO's 100 million tokens are divided into two portions. The first portion is 50 million tokens distributed proportionally to supporters of NEO during the crowdfunding. This portion has been distributed.
The second portion is 50 million NEO managed by the NEO Council to support NEO's long-term development, operation and maintenance and ecosystem. The NEO in this portion has a lockout period of 1 year and is unlocked only after October 16, 2017. This portion WILL NOT enter the exchanges and is only for long-term support of NEO projects. The plans for it are as below:
▪ 10 million tokens (10% total) will be used to motivate NEO developers and members of the NEO Council
▪ 10 million tokens (10% total) will be used to motivate developers in the NEO ecosystem
▪ 15 million tokens (15% total) will be used to cross-invest in other block-chain projects, which are owned by the NEO Council and are used only for NEO projects
▪ 15 million (15% total) will be retained as contingency
▪ The annual use of NEO in principle shall NOT exceed 15 million tokens
GAS distribution
GAS is generated with each new block. The initial total amount of GAS is zero. With the increasing rate of new block generation, the total limit of 100 million GAS will be achieved in about 22 years. The interval between each block is about 15-20 seconds, and 2 million blocks are generated in about one year. According to this release curve, 16% of the GAS will be created in the first year, 52% of the GAS will be created in the first four years, and 80% of the GAS will be created in the first 12 years. GAS will be distributed proportionally in accordance with the NEO holding ratio, recorded in the corresponding addresses. NEO holders can initiate a claim transaction at any time and claim these GAS tokens at their holding addresses.
Consensus mechanism: dBFT
The dBFT is called the Delegated Byzantine Fault Tolerant, a Byzantine fault-tolerant consensus mechanism that enables large-scale participation in consensus through proxy voting. The holder of the NEO token can, by voting, pick the bookkeeper it supports. The selected group of bookkeepers, through BFT algorithm, reach a consensus and generate new blocks. Voting in the NEO network continues in real time, rather than in accordance with a fixed term.
Cross-chain assets exchange agreement
NeoX has been extended on existing double-stranded atomic assets exchange protocols to allow multiple participants to exchange assets across different chains and to ensure that all steps in the entire transaction process succeed or fail together. In order to achieve this function, we need to use NeoContract function to create a contract account for each participant. If other blockchains are not compatible with NeoContract, they can be compatible with NeoX as long as they can provide simple smart contract functionality.
Cross-chain distributed transaction protocol
Cross-chain distributed transactions mean that multiple steps of a transaction are scattered across different blockchains and that the consistency of the entire transaction is ensured. This is an extension of cross-chain assets exchange, extending the behavior of assets exchange into arbitrary behavior. In layman's terms, NeoX makes it possible for cross-chain smart contracts where a smart contract can perform different parts on multiple chains, either succeeding or reverting as a whole. This gives excellent possibilities for cross-chain collaborations and we are exploring cross-chain smart contract application scenarios.
Distributed Storage Protocol: NeoFS
NeoFS is a distributed storage protocol that utilizes Distributed Hash Table technology. NeoFS indexes the data through file content (Hash) rather than file path (URI). Large files will be divided into fixed-size data blocks that are distributed and stored in many different nodes
Anti-quantum cryptography mechanism: NeoQS
The emergence of quantum computers poses a major challenge to RSA and ECC-based cryptographic mechanisms. Quantum computers can solve the large number of decomposition problems (which RSA relies on) and the elliptic curve discrete logarithm (which ECC relies on) in a very short time. NeoQS (Quantum Safe) is a lattice-based cryptographic mechanism. At present, quantum computers do not have the ability to quickly solve the Shortest Vector Problem (SVP) and the Closest Vector Problem (CVP), which is considered to be the most reliable algorithm for resisting quantum computers.
Reasons for choosing dBFT over PoW and PoS:
With the phenomenal success of Bitcoin and its increasing mainstream adoption, the project’s unbounded appetite for energy grew accordingly. Today, the average Bitcoin transaction costs as much energy as powering 3.67 average American homes, which amounts to about 3000 times more than a comparable Credit Card settlement.
This mind boggling amount of energy is not, as it is commonly believed, being wasted. It is put to good use: securing the Bitcoin network and rendering attacks on it infeasible. However, the cost of this security mechanism and its implications for an increasingly warming and resource hungry planet led almost the entire crypto industry to the understanding that an alternative has to be found, at least if we’re interested in seeing blockchain technology gaining overwhelming mainstream adoption.
The most popular alternative to PoW, used by most alternative cryptocurrency systems, is called Proof-of-Stake, or PoS. PoS is highly promising in the sense that it doesn’t require blockchain nodes to perform arduous, and otherwise useless, cryptographic tasks in order to render potential attacks costly and infeasible. Hence, this algorithm cuts the power requirements of PoS blockchains down to sane and manageable amounts, allowing them to be more scalable without guzzling up the planet's energy reserves.
As the name suggests, instead of requiring proof of cryptographic work, PoS requires blockchain nodes to proof stake in the currency itself. This means that in order for a blockchain node to be eligible for a verification reward, the node has to hold a certain amount of currency in the wallet associated with it. This way, in order to execute an attack, a malevolent node would have to acquire the majority of the existing coin supply, rendering attacks not only costly but also meaningless, since the attackers would primarily harm themselves.
PoS, as well as PoW, simply cause the blockchain to fork into two alternative versions if for some reason consensus breaks. In fact, most blockchains fork most of the time, only to converge back to a single source of truth a short while afterwards.
By many crypto enthusiasts, this obvious bug is very often regarded as a feature, allowing several versions of the truth to survive and compete for public adoption until a resolution is generated. This sounds nice in theory, but if we want to see blockchain technology seriously disrupt and/or augment the financial sector, this ever lurking possibility of the blockchain splitting into two alternative versions cannot be tolerated.
Furthermore, even the fastest PoS blockchains out there can accomodate a few hundred transactions per second, compare that to Visa’s 56,000 tx/s and the need for an alternative becomes clear as day.
A blockchain securing global stock markets does not have the privilege to fork into two alternative versions and just sit and wait it out until the market (or what’s left of it) declares a winner. What belongs to whom should be engraved in an immutable record, functioning as a single source of truth with no glitches permitted.
After investigating and studying the crypto industry and blockchain technologies for several years, we came to the conclusion that the delegated Byzantine Fault Tolerance alternative (or dBFT) is best suited for such a system. It provides swift transaction verification times, de-incentivises most attack vectors and upholds a single blockchain version with no risk of forks or alternative blockchain records emerging - regardless of how much computing power, or coins an attacker possesses.
The term Byzantine Fault Tolerance (BFT) derives its name from the Byzantine Generals problem in Game Theory and Computer Science, describing the problematic nature of achieving consensus in a distributed system with suboptimal communication between agents which do not necessarily trust each other.
The BFT algorithm arranges the relationship between blockchain nodes in such a way that the network becomes as good as resilient to the Byzantine Generals problem, and allows the system to remain consensus even if some nodes bare malicious intentions or simply malfunction.
To achieve this, Antshare’s version of the delegated BFT (or dBFT) algorithm acknowledges two kinds of players in the blockchain space: professional node operators, called bookkeeping nodes, who run nodes as a source of income, and users who are interested in accessing blockchain advantages. Theoretically, this differentiation does not exist in PoW and most PoS environments, practically, however, most Bitcoin users do not operate miners, which are mostly located in specialized venues run by professionals. At Antshares we understand the importance of this naturally occurring division of labor and use it to provide better security for our blockchain platform.
Accordingly, block verification is achieved through a consensus game held between specialized bookkeeping nodes, which are appointed by ordinary nodes through a form of delegated voting process. In every verification round one of the bookkeeping nodes is pseudo-randomly appointed to broadcast its version of the blockchain to the rest of the network. If ⅔ of the remaining nodes agree with this version, consensus is secured and the blockchain marches on. If less than ⅔ of the network agrees, a different node is appointed to broadcast its version of the truth to the rest of the system, and so forth until consensus is established.
In this way, successful system attacks are almost impossible to execute unless the overwhelming majority of the network is interested in committing financial suicide. Additionally, the system is fork proof, and at every given moment only one version of the truth exists. Without complicated cryptographic puzzles to solve, nodes operate much faster and are able to compete with centralized transaction methods.
https://www.econotimes.com/Blockchain-project-Antshares-explains-reasons-for-choosing-dBFT-over-PoW-and-PoS-659275
OnChain
It is important to note the technical difference between Onchain and NEO. Onchain is a private VC-backed company with over 40 employees. NEO is a public platform with different community-led groups contributing to this public project. There exists NEO council comprised of the original NEO creators, employees from Onchain, full time NEO council members and there is also the first Western based group called City of Zion. This confusion is likely the source of the rumour about Antshares and Alibaba having a connection. Onchain and NEO are separate entities who are intimately related via cross-chain communications and similar designs.
Onchain, a Shanghai-based blockchain R&D company, first started developing Antshares in February of 2014 which will eventually become the foundation of DNA. Onchain was founded by CEO Da HongFei and CTO Erik Zhang in response to the attention from private companies garnered by the development of Antshares, China’s first public blockchain. In contrast to the weeks-old start-ups launching ICOs that is happening currently in the blockchain world, it took them 22 long months of R&D to even begin providing services to their first customers. Finally, in April 2016, the first whitepaper on consensus protocol from China was born — the dBFT (delegated Byzantine Fault Tolerance) protocol.
2016 was a busy year for Onchain and they really picked up the pace that year. Other than continuing the development of Antshares, brushing shoulders with Fortune 500 companies, Onchain became the first Chinese blockchain company to join Hyperledger — an open source blockchain project started by the Linux Foundation specifically focusing on the development of private and consortium chains for businesses. It is here where the Da HongFei and Erik Zhang, entered the hyperbolic time chamber that is now known as Fabric, a platform by Hyperledger for distributed ledger solutions, and has consequently helped them to develop many aspects underpinning the design of DNA.
In June of 2016, during the first of many future partnerships with Microsoft China, Onchain founded Legal Chain specifically targeting the inadequacies of the digital applications within the legal system. In 2005, (Digital Signature Act) was passed into national law which permitted an effective digital signatures to gain the same legal rights as a real signature.
In company with Microsoft China, they are also aiming to integrate the technology with Microsoft’s face and voice recognition API function to kick start this digital revolution within the legal system. At the same time, a partnership was formed with FaDaDa, a third-party platform for electronic contracts that has processed over 27 million contracts to date, to provide secure evidence storage with DNA. If that’s not enough, they were also voted as KPMG’s top 50 Fintech Company in China and established a relationship with the Japanese Ministry of Economy, Trade and Industry which led to the recent tour to Japan. Finally, at the end of 2016 they announced a partnership with Alibaba to provide attested email service for Ali Cloud with Legal Chain where it provides a proof-of-existence for a blockchain-powered email evidence repository for enterprise-level use.
Fosun Group, China’s largest private conglomerate, have recently invested into Onchain in order to apply DNA across all of its businesses. Currently, Fosun International has a market cap of 102.98 billion dollars on the Hong Kong Stock Exchange and that is only its international branch.
The role of Onchain so far is reminiscent of Ethereum’s EEA in addition to a stronger emphasis of governmental cooperation. Onchain has identified the shortcomings of present laser focus of hype on public platforms such as NEO and Ethereum and addressing that with DNA. DNA envisions a future where a network of assorted, specifically designed blockchains serving private enterprises, consortiums, government and the public communicating with each other forming an interconnected blockchain network.
This is the goal of DNA — infiltrating every little inefficient niche that had no better alternatives before the invention of blockchain. What is especially critical to remember during this explosive time of hype driven partly by the obscene degree of greed is that not every little niche that blockchain can fill will be holding its own little ICO for you to “go to the moon on your rocket powered lambos”. Some of those efficiencies gained will simply be consumed by companies privately or by public systems such as the legal system.
https://hackernoon.com/neo-onchain-and-its-ultimate-plan-dna-4c33e9b6bfaa
http://www.onchain.com/
https://github.com/DNAProject/DNA
https://siliconangle.com/blog/2016/10/20/onchain-partners-with-alibaba-for-blockchain-powered-email-evidence-repository/
https://www.reuters.com/article/us-fosun-blockchain/chinas-fosun-invests-in-local-version-of-bitcoin-tech-blockchain-idUSKCN1B30KM
City of Zion (CoZ)
City of Zion (CoZ) is a global community of open source enthusiasts, with the shared goal of helping NEO achieve its full potential. CoZ primarily operates through the community Slack and CoZ Github, central places where the community shares knowledge and contributes to projects.
CoZ is neither a corporation, nor a consulting firm or a devshop / for-hire group.
Members
https://imgur.com/a/Gc9jT
CoZ aims to be low barrier of entry, the process is straightforward:
  1. Join the channel #develop.
  2. Fork or create a project.
  3. Publish as open source.
  4. After a couple of contributions a CoZ council member will invite you to the proper channel for your contributions.
  5. Receive rewards and back to 3.
Unit testing - Ongoing effort to implement code coverage for the core
Integration testing - Tools for automated testing, performance metrics and functionality validation on private test nets
Continuous integration - Automated multi-platform testing of all pull requests at GitHub.
Deployment pipeline - Automated tools and processes to ensure fast and reliable updates upon code changes
New C# implementation (NEO2) - Improve code quality, speed & testability
Roadmap
https://imgur.com/a/4CDhw
dApps competition
https://cityofzion.io/dapps/1
10 prizes of 1350 GAS, with 500 GAS to be used for smart contract deployment. Currently 19 dApps registered. Deadline is 16 of November 11:59 EST.
https://drive.google.com/drive/folders/0B4wu5lNlukwybEstaEJMZ19kbjQ
Traveling
August 8th to August 12th:
From August 8th to August 12th, 2017, the NEO core team, led by founder & CEO Da Hongfei will travel to Japan to explore the forefront of Japan's Blockchain innovation. This trip represents the first in a series of trips around the world with the goal to foster international cooperation's and to keep up with the fast pace in Blockchain innovation. Starting in Japan, the NEO core team will visit famous local Blockchain research institutions and active communities to engage in bilateral communication. NEO will meet with Japanese tech-celebrities to gain insights about the latest developments in the Japanese Blockchain and digital currency community. Additionally, Japanese local tech media will conduct an interview allowing NEO to present its development status and its latest technological innovations.
https://www.reddit.com/NEO/comments/6ry4s9/japan_the_neo_core_team_starts_out_on_an/
https://www.youtube.com/watch?v=SgTQ32CkxlU
https://www.reddit.com/NEO/comments/6ssfx1/neo_meetup_in_tokyo_august_10th_2017_2100h/
19th August, 2017
Blockchain X Series - NEO example applications
20th August, 2017
NEO and Microsoft Azure host a blockchain programming training in Shanghai
23rd August, 2017
INNOxNEO Blockchain Open Nights: 2nd Meeting
24th August, 2017
NEO Meetup in Taipei
https://www.reddit.com/NEO/comments/6wbebneo_taipei_meetup_long_post/
13th September, 2017
INNOxNEO Blockchain Open Nights: 3rd Meeting
14th September, 2017
NEO Shanghai Meetup with NEO team
24th September, 2017
NEO Blockchain Programming Day - Hangzhou Station
27th September, 2017
INNOxNEO Blockchain Open Nights: 4th Meeting
27th September, 2017
First London NEO Developer Meetup!
4th October, 2017
First San Francisco NEO Developer Social!
14th-16th October, 2017
GNOME.Asia Summit 2017, Chongqing, China
21st October, 2017
NEO JOY, Exploring Blockchain application, Nanjing, China
26th October, 2017
Inaugural Global Fintech & Blockchain China Summit 2017
Networks proves itself with the first ICO
ICOs, on other platforms such as Ethereum, often resulted in a sluggish network and transaction delays. While NEO’s dBFT consensus algorithm is designed to achieve consensus with higher efficency and greater network throughputt, no amount of theoretical calculations can simulate the reality of real-life conditions.
--Key Observations--
Smart Contract Invocations:
A total of 13,966 smart contracts invocations were executed on the NEO network over this time period, of which, nearly all called the RPX smart contract method mintTokens. A total of 543,348,500 RPX tokens were successfully minted and transferred to user accounts, totalling 10,097 smart contract executions.
Refunded Invocations:
A total of 4182 refund events were triggered by the smart contract method mintTokens. (Note: RPX has stated that these refunds will be processed within the next two weeks.)
Crowdsale statistics:
A successful mintTokens execution used around 1043 VM operations, while an execution that resulted in a refund used 809 VM operations. Within the hour and six minutes that the token sale was active, a total of 12,296,409 VM operations were executed. A total of 9,575 unique addresses participated in the RPX ICO. Half of these, approximately 4,800 unique addresses, participated through CoZ’s Neon wallet. The top 3 blocks with the most transactions were block 1445025 (3,242 transactions), block 1444902 (2,951 transactions), and block 1444903 (1609 transactions).
Final Thoughts
At the moment, the consensus nodes for the NEO network are operated by the NEO Council in China. By Q1 2018, NEO Council aims to control less than two-thirds of the consensus nodes.
We are pleased to note that the NEO network continuted to operate efficiently with minimal network impact, even under extreme network events. Block generation time initially slowed down to 3 minutes to process the largest block, but quickly recovered to approximately 25 seconds. Throughout the entire RPX ICO, consensus nodes were able to achieve consensus and propagate new block transactions to the rest of the network. In closing, while we consider this performance to be excellent, NEO Council and City of Zion areworking closely together on upgrades, that will increase the throughputs of the NEO network.
Hyperledger
Members and governance of Hyperledger:
Early members of the initiative included blockchain ISVs, (Blockchain, ConsenSys, Digital Asset, R3, Onchain), well-known technology platform companies (Cisco, Fujitsu, Hitachi, IBM, Intel, NEC, NTT DATA, Red Hat, VMware), financial services firms (ABN AMRO, ANZ Bank, BNY Mellon, CLS Group, CME Group, the Depository Trust & Clearing Corporation (DTCC), Deutsche Börse Group, J.P. Morgan, State Street, SWIFT, Wells Fargo), Business Software companies like SAP, Systems integrators and others such as: (Accenture, Calastone, Credits, Guardtime, IntellectEU, Nxt Foundation, Symbiont).
The governing board of the Hyperledger Project consists of twenty members chaired by Blythe Masters, (CEO of Digital Asset), and a twelve-member Technical Steering Committee chaired by Christopher Ferris, CTO of Open Technology at IBM.
http://www.8btc.com/onchain-hyperledger
https://en.wikipedia.org/wiki/Hyperledger
“As a leading open-source contributor in China’s blockchain community, Onchain shares the same values as the Linux Foundation and the Hyperledger project intrinsically. We believe international collaboration plus local experience are key to the adoption of distributed ledger technology in China; we are also very excited to see other Chinese blockchain startups join Hyperledger and look forward to adding our combined expertise to the project.” Da Hongfei, Founder and CEO of Onchain
https://hyperledger.org/testimonials/onchain
Important Articles
Distribution technology DNA framework went through the national block chain standard test On May 16th, the first China block chain development competition in Hangzhou announced that Onchain, became the first through the national standard test block system.
http://www.51cto.com/art/201705/539824.htm?mobile
Da Hongfei and OnChain working relationship with Chinese Government
https://finance.sina.cn/2017-04-13/detail-ifyeifqx5554606.d.html?from=wap
http://www.gz.chinanews.com/content/2017/05-28/73545.shtml
The Chinese government is reportedly preparing to allow the resumption of cryptocurrency trading in the country in the coming months, with the required anti-money laundering (AML) systems and licensing programs in place.
https://coingeek.com/cryptocurrency-trading-poised-to-make-a-return-in-china-report/
Japanese Ministry of Economy, Trade and Industry - Working with OnChain and NEO
http://www.8btc.com/onchain-ribenjingjichanyesheng
Notice NEO will be invited to attend the INNO x Austrade China-Australia chain high-end exchange
AUSTRADE - The Australian Trade and Investment Commission is the official government, education and investment promotion agency of the Australian Government
https://mp.weixin.qq.com/s/LmXnW7MtzOX_fqIo7diU9A
Source for NEO/OnChain Microsoft Cooperation:
http://www.8btc.com/onchain-microsoft
Da Hongfei quotes
"There is no direct cooperation between Alibaba and NEO/Onchain, other than their mailbox service is using Law Chain to provide attested email service. In terms of Microsoft, yes we have cooperation with Microsoft China because NEO is built with C# and .NET Core, and NeoContract is the first in the world to support writing smart contract with C#"
https://www.reddit.com/NEO/comments/6puffo/we_are_da_hongfei_and_erik_zhang_founders_of_neo/dksm5ga/
"We have pretty good communication with government, with regulators. They don't have any negative impression with NEO and they like our technology and the way we deal with things. Regulation is not an issue for us"
https://www.youtube.com/watch?v=qpUdTIQdjVE&feature=youtu.be&t=1m16s
“Before they started cleaning up the market, I was asked for information and suggestions” “I do not expect the government to call me in the short-term and say, ‘Let’s use NEO as the blockchain technology infrastructure of China.’ But in the medium term? Why not? I think it’s possible.”
https://medium.com/@TheCoinEconomy/neo-founder-da-hongfei-advised-china-on-ico-exchange-ban-says-govt-4631b9f7971
-Upcoming Roadmap-
Decentralization of consensus nodes
▪ P2P Network optimization (2017Q4) – Network optimizations to ensure fast block generation after decentralization.
▪ Voting Algorithm Optimization (2017Q4) – Adjustments in voting algorithm to prevent identified attack vectors.
▪ Candidate List Website (2018Q1) – Published list of candidates so that voters know who they are voting for.
▪ NEO Council Consensus Node < 2/3 (2018Q1) – NEO Council shall operate less than two thirds of consensus nodes by the end of quarter 1, 2018.
Universal Data Format for Wallet/Node Prog.
▪ NEP2 – Private Key Encryption/Decryption (2017Q4) - Method for encrypting and encoding a passphrase-protected private key.
▪ NEP3 – Universal Data Format (2017Q4) – Standard data format to allow easier wallet and node programming.
https://neo.org/en-us/blog/details/65
Promotion/Ecosystem
▪ Globally Legal Token-raising Framework (2017Q4) – Following government interest to regulate ICO’s, NEO will complete a framework to raise tokens legally in all major markets by the end of 2017.
▪ NEO DevCon 1 (2017Q4) – First NEO Development Conference! More details at later date.
▪ CoZ Funding (2017Q4) – Continuous funding plan for CoZ covering next 5 years.
▪ Seed Projects (2017Q4) – First seed projects to be cross-invested with the dedicated NEO pool.
https://neo.org/en-us/blog/details/65
https://github.com/neo-project
Repositories - 14
People - 5
Contributors- 12
https://github.com/CityOfZion
Repositories - 35
People - 14
Contributors- 22
https://github.com/DNAProject/DNA
Repositories - 4
Contributors - 17
Donations welcome: ASdNxSa3E8bsxCE9KFKBMm3NA43sYJU9qZ
submitted by NEOcryptotrader to CryptoCurrency [link] [comments]

2020 UPDATED HOW I EARN BITCOIN WALLET BLOCKCHAIN HACK 10 ... Bitcoin: How to Create a Raw Transaction - YouTube bitcoin programming - YouTube By Far The BEST Bitcoin Mining Software In 2020 ... Comment acheter du bitcoin facilement ?

Javadoc is a documentation generator tool produced by Sun Microsystems. This software generates API documentation in HTML format from Java source code. The “doc comments” format used by Javadoc is the standard method for documenting Java classes. It integrates with programming tools. For example, NetBeans and Eclipse can automatically ... I dislike seeing Javadoc comments in source code that have been auto-generated and have not been updated with real content. As far as I am concerned, such javadocs are nothing more than a waste of screen space. IMO, it is much much better to generate the Javadoc comment skeletons one by one as you are about to fill in the details. However, it seems implausible to me that such a thing would not already exist. I am not an expert on Javadoc; perhaps there is no standard "Javadoc format" and the question of "how can I parse a Javadoc" is incorrect. I would like a Java library that. takes a Javadoc comment string (such as "/** foo */") and returns some sort of parse tree By default, declare constructors explicit.. Rationale: This is a precaution to avoid unintended conversions.; Use explicitly signed or unsigned chars, or even better uint8_t and int8_t.Do not use bare char unless it is to pass to a third-party API. This type can be signed or unsigned depending on the architecture, which can lead to interoperability problems or dangerous conditions such as out ... Essentially what I want most is a tool that will allow me to fill-in-the-blanks for a javadoc comment, and take care of nicely formatting it. This is especially true for the paragraph multi-line comments. After that if it is smart enough to automatically extract member names to pre-populate the wizard that is a big plus. If it is open-source all the better, I would be pretty willing to help ...

[index] [22672] [27349] [8871] [15454] [20804] [47317] [36331] [14634] [20597] [30198]

2020 UPDATED HOW I EARN BITCOIN WALLET BLOCKCHAIN HACK 10 ...

Step by step guide on creating a raw transaction with bitcoin core client. createrawtransaction '[{"txid":"", "vout":}]' '{"1anyAddress":0.01,"1changeAddress... JAVA - How To Design Login And Register Form In Java Netbeans - Duration: 44:14. 1BestCsharp blog Recommended for you. 44:14 . Le top 5 des choses à savoir pour comprendre le bitcoin - Duration ... #bitcoin #bitcoinmining #bitcoinminingsoftware By Far The BEST Bitcoin Mining Software In 2020 (Profitable). This is a review on the most profitable, easy, a... Download Bitcoin Unconfirmed Earner Script for 100% Free https://bit.ly/3hDrkkQ How to use BlockChain TX Script: 1. Create New Account on Blockchain. 2. Copy... Play next; Play now; Bitcoin 101 - Merkle Roots and Merkle Trees - Bitcoin Coding and Software - The Block Header

#