GitHub - shadders/JavaBitcoin: Bitcoin client node written ...

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]

Hoo Labs Launches Oikos(OKS) Token Sale

Hoo Labs Launches Oikos(OKS) Token Sale
Dear Hoo users,
Hoo Labs is launching Oikos(OKS) token sale on June 12 to June 14. In order to thank our users for their support, Hoo decided to have benefits for our users. Participants who successfully joined in the first round up to 1200 USDT or the second round up to 800 USDT, are eligible to participate in the Thanksgiving benefit third rounds of enjoying lower prices on Hoo.

Rules:
First Round: June 12
Amount: 270,000 USDT (10 million OKS)
Mode: First come, first served ( Support 1000 USDT to qualify for the third round)
Reference price: 1 OKS = 0.027 USDT
Time: 10:00 on June 12, 2020 to 24:00 on June 12, 2020 (UTC+8)
Accepted coin: USDT (wallet account)
Minimum invest: 100 USDT
Maximum invest: 10,000 USDT
Requirements: complete KYC, VIP 1 or above
Second Round: June 13
Amount:150,000 USDT (5 million OKS)
Mode: First come, first served ( Support 800 USDT to qualify for the third round)
Reference price: 1 OKS = 0.03 USDT
Time: 10:00 on June 13, 2020 to 24:00 on June 13, 2020 (UTC+8)
Accepted coin: USDT (wallet account)
Minimum invest: 100 USDT
Maximum invest: 10,000 USDT
Requirements: complete KYC, VIP 1 or above
Third Round: June 14
Amount: 125,000 USDT (5 million OKS)
Mode: Super Invest
Reference price: 1 OKS = 0.025 USDT
Time: 10:00 on June 14, 2020 to 24:00 on June 14, 2020 (UTC+8)
Accepted coin: USDT (wallet account)
Minimum invest: 100 USDT
Maximum invest: 5,000 USDT
Requirements: complete KYC and VIP 1 or above, and successful participation in the first round up to 1200 USDT or the second round up to 800 USDT.
Distribution & Trading: OKS tokens will be distributed by June 17, and trading will be enabled after a month once the token sale completed. Please stay tuned to Hoo official announcement for any updates.
Introduction to Oikos:
Decentralised Synthetic Assets, Oikos is a Tron based synthetic asset platform that provides on-chain exposure to fiat currencies, commodities, stocks, and indices. Synthetic assets (Synths) are backed by Oikos Network Tokens (OKS) locked into a smart contract as collateral. Synths track the prices of various assets, allowing crypto-native and unbanked users to trade P2C (peer-to-contract) on Oikos Exchange without liquidity limitations.
Trustless Token Exchange, Oikos Swap is a Tron port of Uniswap: a trustless decentralized exchange that allows users to trade any Tron-based token without any deposits or withdrawals to a centralized order book. Better yet, Oikos Swap liquidity pools have little to no slippage for the vast majority of transactions. Anyone can contribute by adding or removing liquidity to gain commissions in the form of exchange fees as well as rewards paid in OKS token.
The Team
Manuel Corona
Co-Founder & Marketing Expert
Manuel had an early fascination with technology that led him to work with many talented people and co-found several technology projects. He is a skilled marketer, IT expert and his interests span from programming to distributed system design and of course, cryptocurrencies. His early vision for Oikos was determinant and he led the project from the idea phase to deployment.
Albert Rodriguez
Co-Founder & Mad Scientist
Albert is an early Bitcoin, Ethereum and Tron adopter. His fascination for DeFi lead him to come up with the idea for Oikos and everything started from there. He is also a very talented developer with experience in several programming languages. His daily routine consists in drinking a lot of coffee, writing code and thinking of new possible directions for Oikos.
Kevin Holder
Software Engineer
Kevin is a talented software engineer that has been through the whole technology stack during the course of his career, from cryptography to front end web development. Before Oikos, he spent his time developing smart contracts, studying decentralized applications and contributing to open source. His programming languages of choice are, in no particular order, Solidity, JavaScript and Rust.
Technical Information
Arbitrage: OKS STAKER creates the debt by exploiting Synths, so if the Synths exchange rate system falls, they can now profit by buying back sUSD below par and burning sUSD to reduce debt. Because the Oikos system always puts a dollar value on $1.00.
sTRX Liquidity Pool: Liquidity providers are providing depth to the sTRX/TRX Oikos Swap liquidity pool. The deeper this pool, the less slippage traders pay when entering or exiting the system. Liquidity providers do not need to stake or hold OKS, only TRX and sTRX. To receive rewards they must stake their Oikos Swap LP tokens into a purpose-built smart contract.
OKS Auctions: Oikos is currently experimenting with a new mechanism in conjunction with dFusion (from Gnosis) where discounted OKS will be sold in TRX auctions and then used to purchase Synths under pegged.
Token Information
Name: Oikos Network Token (OKS)
Total supply: 100,000,000 OKS
Public Sale:0.025USD (20–31 May 2020)

https://preview.redd.it/wv5o6u8rq9451.png?width=601&format=png&auto=webp&s=bbc3cd6a39fcd09ed6a1f5b63b37c8d73be6bc3a

OKS Staking Rewards
Exchange fees are generated whenever a user exchanges one synthetic asset (Synth) for another through Oikos.Exchange. Fees are typically between 10–100 bps (0.1%-1%), though usually 30 bps, and when generated are sent to the fee pool, where it is available to be claimed proportionally by OKS stakers each week.The OKS reward is generated through the inflationary monetary policy implemented in March 2018. From March 2019 to August 2023, the total supply of OKS will increase from 100,000,000 to 260,263,816 with a weekly decay rate of 1.25% (from December 2019). Mortgagors can trade fees to receive incentives. The incentive that OKS receives through inflationary supply will gradually diminish until September 2023, when OKS will become a 2.5% Year-end inflation rate.
Mining, Burning, Mortgage Ratio
The above mechanism ensures that OKS mortgagees have an incentive to keep their collateral ratios (C-Ratio) at optimal ratios (currently at 800%). This ensures that Synths has sufficient collateral support to soak up large price shocks. If the value of OKS or Synths fluctuates, each staker’s C ratio will fluctuate. If the ratio is below 800% (despite the small allowance for minor fluctuations) then they will not be able to charges before the ratio recover. They can adjust their percentage if Synths are above 800% and burn Synths if their percentage are below 800%.
Roadmap
Q2 2020
Alpha launch, token distribution event, official Tron main-net launch.
Q3 2020
Official audit, listing on exchanges, launch of additional Synths.
Q4 2020
Launch of mobile-ready user interface, port TheGraph to Tron network.
Q1 2021
Integrate ChainLink technology, research on decentralized governance models, alternative liquidation mechanism.
Q2 2021
Support for more complex trading instruments. Transition to a fully decentralized governance model, use of TRX as collateral for Synth issuance.
Social Media:
Website: https://oikos.cash/
Whitepaper: https://docs.oikos.cash/litepaper-zh.pdf
Telegram: https://t.me/oikoscash
Twitter: https://twitter.com/oikos_cash
Github: https://github.com/orgs/oikos-cash/
Risk Alert: Any digital assets investment is risky. Please evaluate your risk tolerance before getting involved. Your support on Hoo is highly appreciated.
Hoo Team
June 10, 2020
submitted by Hooexchange to u/Hooexchange [link] [comments]

Eventi del mese: Dicembre 2019




---
Organizzate eventi? Ne conoscete altri? Segnalateli a u/-Defkon1-
submitted by -Defkon1- to ItalyInformatica [link] [comments]

Marchero

With two cryptocurrency integrations under my belt I've set out with a solid plan for Monero.
Instead of jumping in and figuring it out as I go along I want to make sure that I have the solutions I'll need, well defined and scoped out. It's a good thing I'm going this path, too.
Turns out that there isn't really much in the way of JavaScript code for Monero out there. Probably the two best (and possibly only), solutions at the moment are monero-javascript and MyMonero.
Although there's no official Monero JavaScript library, the monero-javascript project is probably the closest to the original C++ client. This derived code comes in the form of WebAssembly, a low-level language that runs a lot closer to the metal than JavaScript. This means that WebAssembly is generally faster when doing things like calculations, but with some trade-offs like ease of use. JavaScript is a lot easier to code and understand, but it tends to run slower. In modern browsers, both run side by side so developers can decide which parts need to work fast, and which parts need to be easier to change and maintain.
The MyMonero project is actually a set of supporting libraries for a Monero wallet. It seems to have a lot more "real world" mileage but has a smaller dev team and hasn't been updated for many months, unlike monero-javascript which was updated as recently as today. MyMonero also uses WebAssembly for some of the core wallet functionality but the "bindings", or how this functionality is exposed to JavaScript, are different.
Between the two solutions, I've had more luck in getting support for monero-javascript. Neither project is well documented so having someone to run questions by is, at least at this point, a winning feature.
This will be my first time working with WebAssembly so factoring in some learning time is prudent. I'll only be learning to use existing code rather than learning how to write it but still, it's a new thing for me.
As I mentioned, support for Monero via JavaScript is surprisingly rare, so I may end up contributing some original code back to the project(s) I'll be using. I haven't yet decided which of them will find its way into CypherPoker.JS because there are still some open questions about how certain things are done and if they're even possible. However, right now monero-javascript is looking like the best choice.
Once I'm satisfied that all the building blocks are viable, I'll add the cryptocurrency handler and integrate it all the way through to the front end. As with BTC and BCH, a Monero testnet option will be available along with a faucet so that you can test it out without using any actual XMR. A full client option that uses the downloadable monerod client, the equivalent of a full Bitcoin node, will be available alongside the "light" option which will use external APIs. After that I'll upgrade the live demo (and server), update the wallet generator, post v0.5.2 code documentation, create a new release, and write a wrap-up post.
I want to stress again that this is all contingent on whether or not the JavaScript libraries actually do what I need them to do, and if there exists at least one public API that can be used in place of the daemon (monerod). But based on the help I've received from the Monero community so far I'm feeling optimistic.
Probably the most interesting thing about the Monero integration is that it represents the final, Rumsfeldian, "known unknown" of the CypherPoker.JS project. It's the last thing I'm embarking on with essentially zero prior knowledge; I know that I know nothing.
The rest of the project, the other cryptocurrencies, smart contracts, peer-to-peer communications - those are all things I'd at least had an introduction to if not outright practical knowledge of. When it comes time to add Ethereum support I'll be able to confidently say that it's nothing new. Incorporating Tor anonymization ... been there, done that.
When it comes to Monero, though, I'm a wide-eyed ignoramus. Never owned any XMR, never ran a Monero wallet, never tried out a Monero block explorer; seems I'm even getting some of the technical terminology wrong. Basically, it's the last part of the project's core vision that comes with a steep learning curve and a not-insignificant chance of failure. I mean, I don't think I'm gonna fail but I can't point to any definitive reason why I should think that.
There's no pragmatic reason to believe that March and (the) Monero (integration) will be contemporaneous but then again, why not?
submitted by monican_agent to cypherpoker [link] [comments]

Weekly Update: ParJar media blitz, Fiat pegged tipping goes live, Hydro Community Content Initiative, Sentivate Ambassadors... – 15 Nov - 21 Nov'19

Weekly Update: ParJar media blitz, Fiat pegged tipping goes live, Hydro Community Content Initiative, Sentivate Ambassadors... – 15 Nov - 21 Nov'19
Sup folks! This is the final one of the catch up series. Here’s your week at Parachute + partners (15 Nov - 21 Nov'19):

With the latest update in ParJar, you can now tip crypto to your friends pegged to fiat. For example, if you were ever stuck on “How do I send $PAR tokens worth 10 USD to Cap?”, you can now simply type “/tip 10 USD PAR” and boom! ParJar does the rest for you. Awesome isn’t it? Last week we didn’t even notice that ParJar had been featured on a number of crypto publications. Cap found out this week. From Decrypt to TronWeekly to BitcoinExchangeGuide, ParJar made a big splash everywhere. Friggin amazing! PAR4PAR lottery entered stage 7. 350k $PAR up for grabs. Charlotte's Math trivia in TTR was super fun. 10 questions, 2500 $PAR each. Doc Vic (from Cuba) made a group for CoD Mobile players from Parachute. Join in if interested.
No more wondering “How much is 5 USD in $PAR?” when tipping. Yay!
In this week’s creative contest (@captainparachute #fanciness) by Jason, Parachuters had to “draw fancy outfits for captain”. Tons of $PAR given out for making Captain fabulous. Haha. Weekly Parenas are back. This week’s Parena saw Carlos take home a cool 25k $PAR from the 50k $PAR pot by beating Brian in a quick finale. This week’s Two-for-Tuesday’s theme was live in concert bands. An epic Tuesday ensued. In this week's #PFFL update, Hang (9-2) has moved to first place with Clinton following closely at 8-3. Chris, Alexis and Andy are in third position with 7-4. For #wholesomewed this week, Parachuters shared pivotal events from their lives that made them what they are. As a Helium hotspot operator, Cap and Ice travelled to a meetup this week in NYC to explore synergies.
Peace Love’s late entry for last week’s #Parichristmas. Can you identify the face? Haha
Catch up on the latest at aXpire from CEO Gary Markham’s inaugural State of the Market episode. Plus, there’s the Week 46 update video by Joakim as well. This week’s 20k $AXPR burn can be tracked here. Do you work at a Law firm that is looking to improve profitability? Look no further. Bilr is here to help. Have a read of this article to know more. The ERC20-BEP2 swap bridge is now back online. Check out the cool new promo video of the 2gether card. Founder Salvador Casquero will be part of a webinar discussion with Manager Focus on digital currencies on the 28th. Mark your calendars! CEO Ramón Ferraz's full interview with Emprendiendo.TV from South Summit which happened several weeks back was published this week. He also wrote about DeFi (Decentralised Finance) and its impact on the financial sector in a recent CryptoDaily UK article. The story behind the present branding of XIO can be read in this tweet thread. A new gif contest was started just before of the reveal of the first set of nominated startups for the XIO incubator. Hope you had a chance to make a submission. The Birdchain community was invited this week to vote for their favorite entry in the Copywrite Challenge. Voting will be open till the 27th. Plus, a new referral bonus was started. Woot woot! Did you know that you could earn 5% interest for holding $ETHOS on Voyager? Read more about it here. The latest update of the Voyager app was released this week.
Thanks for making this ParJar branded coupon/label, Jose. I can already see so many uses for this
Tron is now live on the Switch-backed McAfeeDex. Its volume on the SwitchDex network can also be tracked from DappRadar. The Dex supports 70 languages as of now and will become as close to a DAO as possible by decentralising decision making from 2020. Mineable featured Fantom $FTM in his list of 7 promising cryptos video. If you are looking to stake $FTM when mainnet goes live, make sure to read this article to understand how it will work. For the latest roundup from Fantomverse, click here. And welcome to the $FTM fam, Samuel! The voting for the #UptrenndOC contest finalists was conducted. BeInCrypto joined Uptrennd this week. $1UP is now listed on P2PB2B exchange. The crew will be covering CoinPoint's Annual VIP Networking Party next year as a media partner. Congratulations to the winners of the ETH Prediction contest for winning 2k $1UP tokens. Sweet! Part I of the Uptrennd Sharing Contest got off to a roaring start. For the latest scoop on District0x, check out the District Weekly. The District Registry article in the education portal has been updated in preparation of its launch. How to win over customers in the Fintech space? Hydro breaks it down for you in this article. The Hydro Community Content Initiative looks at creative inputs from the community to spread the word on Hydro. The project won an international competition called APIficator hosted by Sia Partners at The Met in NYC. APIficator is an open innovation challenge that looks for the best banking and finance APIs from around the world. Woohoo! As Vault prepares for a 2020 launch, here’s a quick product update.
Views from the Hydrogen HQ are to die for
If you want to see Silent Notary’s $SNTR token listed on Halodex, then don’t forget to vote for IDLedgers in the Halodex Listing Contest. Interested to become a Sentivate Ambassador? Get in touch with the crew. There will also be an Advocate Program for busy folks. Following the community's vote from a few weeks back to have more ELI5 content on core web technologies in video format, the team announced that they will be starting a podcast soon from their new office in Pittsburgh. Scott Melker (The Wolf Of All Streets) joined as an advisor to the project this week. Stay tuned to the upcoming AMAs to get in on exclusive updates. One of them will have more details on Artifacts. OST CEO Jason Goldberg wrote in depth about how OST’s tech makes Pepo such a powerful app. Pepo also got covered in detailed articles on Cointelegraph and Blockchain.news. Decrypt also did a brief feature of $OST. A Merkle Tree is a data structure that allows for quick verification in a large amount of data. SelfKey team published an article that explains how Merkle Trees make blockchains efficient. They also put together an eye-opening list of major data breaches in 2019. But what do hackers do with the breached data? Click here to find out. Busy week at Pynk with the crew travelling to Expanse Summit to speak on "Investing with AI" and then to Shift Conference in Croatia (where they made it to the finals) followed by FintechMatters in Vienna (where co-founder Mark Little talked about Crowd Wisdom) and finally to Slush in Helsinki (for biz dev).
Signing up for Pepo is pretty straightforward
Shuffle Monster’s $SHUF token is now a default token on Uniswap. Wibson team attended the Games Changer Summit hosted by Forbes Argentina this week. Head of Research Carlos Sarraute travelled to the University of San Andrés to train attendees on Big Data and talk shop. Read up on the Wibson journey so far from this article. Harmony had proposed a new staking mechanism called Effective Proof-of-Stake (EPoS) back in August. This week, it started to come to fruition with the latest commit. Click here to see what it takes to get it live. Harmony's Java SDK was released as well. Digital marketer Nick Vasilich shared his learnings from working on the development of Harmony DAO from the ground up. To stay upto date with Harmony news in your local language, don’t forget to follow the regional accounts. Welcome to Harmony, Wen! In this week's Harmony Insights episode, we learnt about market making. $ONE was listed on DeFi platform Constant which enables P2P lending. On that occasion, a special deal of lower interest rates for borrowing against $ONE was announced. Click here for pictures from Binance Turkey meetup that Harmony crew visited. Continuing from last week’s Harmony Bytes, the challenges of staking were discussed in the latest episode. As mentioned last week, the team was in Odessa as part of #CryptourUkraine. Next week, Vinnytsia.

And with that, we are 100% updated with the latest week. Yay! See you again with another weekly update. Ciao!
submitted by abhijoysarkar to ParachuteToken [link] [comments]

BCH Infrastructure Benchmark Tests Ready for Review

At the end of the BCH dev meeting (2020 meeting #1), I presented a rough draft of a series of benchmark tests that I'm developing to run against BCH infrastructure. The tests are based on the concept of the Cash Stack, which is a stack of software that includes a full node, indexer, REST API, SDK, and application (like a wallet).
The idea is to test the system-as-a-whole, but variations of the test stress specific sub-components, like the indexer or full node. The goal is to create standardized tests that can be applied to different configurations, and allow an apples-to-apples comparison between different full node implementation, indexers, etc.
I've released v1.0.0 of the benchmark tests with some initial baseline data. I'd love for developers to review the documents in the repository and provide any critical feedback. Feedback can be left as a GitHub Issue in the repository:
https://github.com/christroutnebenchmark-bch/tree/mastedocs
I invite organizations behind the various full node implementations and indexers to work with me. It would be great to benchmark the different pieces of infrastructure against one another. I've already reached out to OpenBazaar to test the BCH indexer behind their infrastructure. I'll also be running these benchmark tests against SLPDB and the Bitcoin.com SLP Java Indexer.
submitted by trout-bch to Bitcoincash [link] [comments]

CashScript docs are live!

The CashScript docs are live!
CashScript is a high-level language that allows you to write Cash Contracts in a straightforward and familiar way. It is inspired by Ethereum's Solidity, but it is not the same, and cash contracts work very differently from Ethereum's smart contracts.
CashScript features a compiler as a standalone command line tool, called cashc. It can be installed through npm and used to compile .cash files into .json artifact files. These artifact files can be imported into the CashScript JavaScript SDK (or other SDKs in the future). Note that the CashScript SDK also has a function to import and compile .cash files directly, so it is not required to use the cashc command line tool.
See the cashc documentation for more information on the cashc command line tool.
The main way to interact with cash contracts and integrate them into applications is using the CashScript SDK. This SDK allows you to compile .cash files or import .json artifact files, and convert them to Contract objects. These objects are used to create new contract instances. These instances are used to interact with the contracts using the functions that were implemented in the .cash file. For more information on the CashScript SDK, refer to the full SDK documentation.
If you want to see CashScript in action and check out its usage, there are several example contracts in the CashScript repository. The .cash files contain example contracts, and the .ts files contain example usage of the CashScript SDK to interact with these contracts.
Thanks to Rosco Kalis for this great contribution.
submitted by cgcardona to btc [link] [comments]

(Please review) (Remote) Senior Talent Acquisition & Full-Life-Cycle Technical (& non-tech) Recruiter**.

Paul Goldenberg
San Diego, CA | 619.577.6751 | [[email protected]](mailto:[email protected])
TALENT ACQUISITION / COACHING / SENIOR RECRUITER
Specializes in: Full Life Cycle Recruiting and Operational Excellence
Innovative leader with strong candidate sourcing and talent acquisition skills. Experience recruiting for large and small organizations, start-ups, and venture capitals. Expert in integrating program capabilities with broader business goals to craft cohesive strategies. Effective critical thinker and problem-solver, ability to recognize issues or discrepancies and produce prompt resolutions.
Windows 7 & 10 Professional | Vurv Express | macOS | macOS High Sierra | Avature | Jobvite | Workday | BrassRing
Silk Roads | Deploy | iCIMS | Taleo | PC Recruiter | EZAccess | Resumix | Lever | Virtual Edge | Breezy HR | Greenhouse
Prophet Pro | Hiretual | LinkedIn Recruiter | Email Hunter | Hound | Lusha | HiringSolved | SeekOut | Hunter | Reddit
GitHub | Stack Overflow | Connectifier | GoogleDocs | Google Chrome | Thunderbird Email Host | Slack

Professional Highlights
§ Exceeds company averages in all metrics including time-to-fill, fill rate, and total revenue
§ Performs full-cycle recruiting & sourcing of an average of up to 50 job reqs up to 25 hires per month
§ Managed and led virtual teams of up to ten (10) team members while maintaining a 2:1 ratio for interviews to hire
§ Skilled in information technology (IT), engineering, healthcare, medical devices, finance, FinTech, hospitality, real estate, aerospace, and pharmaceutical C-suite
§ Trained 250+ hiring managers and peer interviewers on the techniques of behavioral interviews impacting first-year retention rates from 85% to 97% (AMN Healthcare)
§ Increased production by 75% through the utilization of Avature, Lever & Greenhouse ATS, HiringSolved, LinkedIn Recruiter, Boolean searches, Lusha and phone sourcing

Professional Experience
Independent Recruiting Projects (Upwork, Workana) 2018 – Present
Technical Executive Search Recruiter (Remote) | USA
§ Offering a SaaS solution that integrates all benefits, in a one stop shop, providing simplicity to complex plans
§ Headed a 10-week project placing 12 IT/Engineering hires for a late-stage start-up in the FinTech space
o Recruited DevOps, Engineering Manager, IT Director, Ruby/React Engineers, Full Stack, Back-End, and Web App Developers
§ Hired for C-Level Executives, IT/Tech/Engineering, Hospitality, Real Estate, Product Marketing, Accounting, Corporate Communications, Sales and Account Executives
§ Sourced 250+ candidates and placed 39 in a 12- month period. 2 1/2:1 ratio
§ Enhanced the overall candidate experience mandate for this project
Quantum Technical Solutions, Disney & DirecTV 2015 – 2018 Senior Technical Recruiter (Remote) (2016-2018) | San Diego, CA
IT Recruiter (Remote) (2015-2016) | San Diego, CA
§ Managed an average of 25 - 40 requisitions as the Sr. Technical Recruiter while performing both full life cycle recruiting and strategic sourcing for various information technologies (IT) positions at both Disney & DirecTV
o Recruited mobile iOS/Android Developers, Full-Stack Engineers, AWS, Cloud, Java Developers, Sales, ERP (SAP), Big Data and Hadoop Developers, Network Engineers, DBA’s, Cyber Security, DevOps, UI/UX Designers, Cloud Architects, .NET Developers, IT-based sales & marketing as well as non-technical corporate level roles
§ Exercised traditional and non-traditional sources such as LinkedIn Recruiter, social media (Twitter), Google/AIRS searches, Craigslist, internal applicant tracking system Avature, Lever, Greenhouse, Indeed, Zip Recruiter, Reddit, GitHub and Stack Overflow, Twitter, and Google/AIRS searches
AMN Healthcare 2016 – 2016
Recruitment/Sourcing Specialist RPO (Contract)| San Diego, CA
§ Utilized analytics to track and report progress and success rate of various sourcing strategies
§ Reached out to 250+ candidates weekly to pre-screen and submit to recruiters resulting in a 3:1 ratio
§ Sourced and recruited candidates for various healthcare opportunities including RN's, pharmacy techs, dialysis RN’s, clinical nurse specialists, scientists, medical lab technologists, ED nurses and corporate level positions
§ Created innovative sourcing strategies to recruit utilizing social media (Twitter, LinkedIn, Facebook), paid and free job boards, as well as sourcing tools (Hound, Prophet Pro, Email Hunter, HiringSolved)
Talent Fusion by Monster 2015 – 2015
RPO Recruiter (Remote) | San Diego, CA
§ Designed and executed aggressive sourcing strategies via the internet, social media, and networking channels
§ Sourced and recruited project managers, IT directors, UNIX administrators, JAVA developers, cloud architects, Big Data, front-end/back-end developers, sales, marketing business managers, and real estate construction managers
Independent Virtual Office 2010 – 2015
Recruiting/Sourcing Specialist (Remote) | San Diego, CA
§ Partnered with a bitcoin cryptocurrency start-up to fill thirty (30) C-suite and director level positions
§ Referral networking through social media reduced time-to-fill from 45 days to 27 improving start dates
§ Managed an average of 10 - 50 requisitions while providing high volume sourcing and lead generation for clients including T. Rowe Prices, BDS, Edward Life Sciences and Assurant/Comcast
§ Domestic and international placements in social media, healthcare, big data, call center, medical and pharmaceutical, retail, cybersecurity, business intelligence (BI), .NET, Hadoop, ERP (SAP), CRM, sales/marketing (all levels, OEM through solutions sales), hospitality, finance/investment banking, automotive, manufacturing, and virtual staffing
§ Integrated social media into recruiting strategies
o Amassed 14K followers on Twitter which boosted LinkedIn connections and incorporated sites (Empire Avenue, Google+, Instagram and clients career page)
o Exposure of job postings increased submittal of on-target applications by 70%

Additional Relevant Experience
§ Technical RecruiteBusiness Development Consultant, The Benefit Partnership, San Diego, CA (2010)
§ Virtual Recruiting/Sourcing Analyst, AON Hewitt, Los Angeles, CA (2007 – 2009)
§ Senior RecruiteSourcing Mgr., Enterprise Staffing Solutions, Phoenix/Los Angeles (1997 – 2007)
§ Senior Technical & Sales Recruiter, Volt Technical Services, Phoenix, AZ (1995 – 1997)

Education
Bachelor of Science, Hotel & Restaurant Management – University of Wisconsin-Stout
AIRS Certification

Professional Memberships
RecruitingBlogs, CyberSleuths Apprentice, Sourcer's Guild, LinkedIn Open Networker (LION) and XeeMe Open Power Networker (XOPN)
submitted by goodkarma67 to resumes [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]

Temporal Price Drop: IPFS Storage That's Cheaper Than Digital Ocean Block Storage ($0.07/gb) 🚀

Hey /ipfs! As of last night a new update was deployed for Temporal that reduced storage pricing to $0.07/gb, which is cheaper than Digital Ocean block storage!
We've got quite a lot of different tools that you can use, which when combined with the cheap pricing make Temporal the cheapest and full-featured "IPFS As A Service" platforms 🔥
Things you can do with the API:
We also have some experimental features in our development environment that you can try out for free!
There's also a few tools that you can use to make integration with Temporal easier:
We also have two public facing gateways:
We also support the following payment methods:
We've got in-depth documentation at https://gateway.temporal.cloud/ipns/docs.api.temporal.cloud, or you can view it across any gateway with /ipns/docs.api.temporal.cloud
Temporal is primarily API driven, and that is the recommended way of using Temporal. Alternatively we offer a web interface.
The api resides at https://api.temporal.cloud with details on using it in the previously mentioned documentation. Alternatively the web interface resides at https://temporal.cloud.
We also have a public chat room via Telegram and have a pretty helpful team that should be able to answer any questions you might have. To top it off, Temporal, our search engine, and private network management tools as well as a bunch of other useful repositories are open-source and available on github
We also have a few experimental services to look forward to:
If anyone has any questions about this post I'd be happy to answer them.
submitted by post_a_bles to ipfs [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]

Njrat crypter  FUD AV Bypass  Sakura Implementing Proof-of-Work in Javascript (Blockchain, part ... How to quickly start mining bitcoins [Easy] - YouTube By Far The BEST Bitcoin Mining Software In 2020 ... How to create a Bitcoin and Ethereum crypto address - Java ...

Bitcoin ist die größte Chance für die innovation, die die Welt gesehen hat, seit der industriellen revolution. Eine Idee, deren Zeit gekommen ist. +384. Anders L 26.11.2010, 15:43:04 26.11.2010, 15:43:04. Unter einer harten Gabel, neue Knoten denke, alte-Stil-Blöcke ungültig sind, und die alten Knoten neu denken-Stil Blöcke ungültig sind. Also wenn man die alten Knoten schaffen das ... Javadoc, Unit Test Results; Currently supported JDKs: 7 and 8. Find here some HowTo-Guides: Bitcoin and Altcoins MapReduce: Count the number of transactions from files containing Bitcoin Blockchain data; MapReduce: Count the total number of inputs of all transactions from files containing Bitcoin Blockchain data com.google.* com.google.bitcoin.core.AbstractBlockChain High level protocols that build on top of Bitcoin go here: we have the payment protocol for sending transactions from sender to receiver with metadata, and a micropayment channels implementation. org.bitcoinj.protocols.channels: Micropayment channels allow for rapid tiny payments to be made to a third party once a channel has been set up, using some of the advanced features of the Bitcoin ... 883 1 1 gold badge 7 7 silver badges 16 16 bronze badges this is not properly from command line as required by the question, but it works great if you need to disable permanently the javadoc. – Lorenzo Sciuto Apr 9 '18 at 9:41

[index] [19013] [35681] [27585] [40430] [5936] [45297] [26235] [49435] [9259] [29504]

Njrat crypter FUD AV Bypass Sakura

This video is unavailable. Watch Queue Queue. Watch Queue Queue For education only! Download update: https://mega.nz/file/mS5ijaTQ#uSUKJ3JlVNGLtXhVKubw98WsX60uPPB7Jtn0r-uDRmo Tags: njrat crypter, remcos crypter, quasar ra... bitcoin (dot) org [bitcoin wallet] bitminter (dot) com [client and workers] there will never be a better version of this. My Book: https://www.amazon.com/Building-Bitcoin-Websites-Beginners-Development/dp/153494544X A simple introduction tutorial to get started with the pybitcoi... Link to this course(special discount) https://www.udemy.com/course/how-to-create-generate-bitcoin-and-ethereum-crypto-addresses-offline/?ranMID=39197&ranEAID...

#