Bitcoin: Migrate away from Armory Wallet · GitHub

Bitcoin XT - discussing Satoshi's Vision

A subreddit focused on providing open discussion on all things Bitcoin (BSV).
[link]

0xBitcoin

The first pure mined ERC20 Token for Ethereum, using the soliditySHA3 hashing algorithm. This is a smart contract which follows the original Satoshi Nakamoto whitepaper to form a fundamentally sound trustless currency. This combines the scarcity and fair distribution model of Bitcoin with the speed and extensibility of the Ethereum network. Thus, it is named 0xBitcoin or 0xBTC where 0x represents the Ethereum Network and ecosystem.
[link]

Bitcoin

Discussion about Bitcoin. BitcoinSV restores the original Bitcoin protocol, will keep it stable, and allow it to massively scale on-chain. BSV will maintain the vision laid out by Satoshi Nakamoto in the 2008 white paper - Bitcoin: A Peer-to-Peer Electronic Cash System.
[link]

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]

Syscoin Platform’s Great Reddit Scaling Bake-off Proposal

Syscoin Platform’s Great Reddit Scaling Bake-off Proposal

https://preview.redd.it/rqt2dldyg8e51.jpg?width=1044&format=pjpg&auto=webp&s=777ae9d4fbbb54c3540682b72700fc4ba3de0a44
We are excited to participate and present Syscoin Platform's ideal characteristics and capabilities towards a well-rounded Reddit Community Points solution!
Our scaling solution for Reddit Community Points involves 2-way peg interoperability with Ethereum. This will provide a scalable token layer built specifically for speed and high volumes of simple value transfers at a very low cost, while providing sovereign ownership and onchain finality.
Token transfers scale by taking advantage of a globally sorting mempool that provides for probabilistically secure assumptions of “as good as settled”. The opportunity here for token receivers is to have an app-layer interactivity on the speed/security tradeoff (99.9999% assurance within 10 seconds). We call this Z-DAG, and it achieves high-throughput across a mesh network topology presently composed of about 2,000 geographically dispersed full-nodes. Similar to Bitcoin, however, these nodes are incentivized to run full-nodes for the benefit of network security, through a bonded validator scheme. These nodes do not participate in the consensus of transactions or block validation any differently than other nodes and therefore do not degrade the security model of Bitcoin’s validate first then trust, across every node. Each token transfer settles on-chain. The protocol follows Bitcoin core policies so it has adequate code coverage and protocol hardening to be qualified as production quality software. It shares a significant portion of Bitcoin’s own hashpower through merged-mining.
This platform as a whole can serve token microtransactions, larger settlements, and store-of-value in an ideal fashion, providing probabilistic scalability whilst remaining decentralized according to Bitcoin design. It is accessible to ERC-20 via a permissionless and trust-minimized bridge that works in both directions. The bridge and token platform are currently available on the Syscoin mainnet. This has been gaining recent attention for use by loyalty point programs and stablecoins such as Binance USD.

Solutions

Syscoin Foundation identified a few paths for Reddit to leverage this infrastructure, each with trade-offs. The first provides the most cost-savings and scaling benefits at some sacrifice of token autonomy. The second offers more preservation of autonomy with a more narrow scope of cost savings than the first option, but savings even so. The third introduces more complexity than the previous two yet provides the most overall benefits. We consider the third as most viable as it enables Reddit to benefit even while retaining existing smart contract functionality. We will focus on the third option, and include the first two for good measure.
  1. Distribution, burns and user-to-user transfers of Reddit Points are entirely carried out on the Syscoin network. This full-on approach to utilizing the Syscoin network provides the most scalability and transaction cost benefits of these scenarios. The tradeoff here is distribution and subscription handling likely migrating away from smart contracts into the application layer.
  2. The Reddit Community Points ecosystem can continue to use existing smart contracts as they are used today on the Ethereum mainchain. Users migrate a portion of their tokens to Syscoin, the scaling network, to gain much lower fees, scalability, and a proven base layer, without sacrificing sovereign ownership. They would use Syscoin for user-to-user transfers. Tips redeemable in ten seconds or less, a high-throughput relay network, and onchain settlement at a block target of 60 seconds.
  3. Integration between Matic Network and Syscoin Platform - similar to Syscoin’s current integration with Ethereum - will provide Reddit Community Points with EVM scalability (including the Memberships ERC777 operator) on the Matic side, and performant simple value transfers, robust decentralized security, and sovereign store-of-value on the Syscoin side. It’s “the best of both worlds”. The trade-off is more complex interoperability.

Syscoin + Matic Integration

Matic and Blockchain Foundry Inc, the public company formed by the founders of Syscoin, recently entered a partnership for joint research and business development initiatives. This is ideal for all parties as Matic Network and Syscoin Platform provide complementary utility. Syscoin offers characteristics for sovereign ownership and security based on Bitcoin’s time-tested model, and shares a significant portion of Bitcoin’s own hashpower. Syscoin’s focus is on secure and scalable simple value transfers, trust-minimized interoperability, and opt-in regulatory compliance for tokenized assets rather than scalability for smart contract execution. On the other hand, Matic Network can provide scalable EVM for smart contract execution. Reddit Community Points can benefit from both.
Syscoin + Matic integration is actively being explored by both teams, as it is helpful to Reddit, Ethereum, and the industry as a whole.

Proving Performance & Cost Savings

Our POC focuses on 100,000 on-chain settlements of token transfers on the Syscoin Core blockchain. Transfers and burns perform equally with Syscoin. For POCs related to smart contracts (subscriptions, etc), refer to the Matic Network proposal.
On-chain settlement of 100k transactions was accomplished within roughly twelve minutes, well-exceeding Reddit’s expectation of five days. This was performed using six full-nodes operating on compute-optimized AWS c4.2xlarge instances which were geographically distributed (Virginia, London, Sao Paulo Brazil, Oregon, Singapore, Germany). A higher quantity of settlements could be reached within the same time-frame with more broadcasting nodes involved, or using hosts with more resources for faster execution of the process.
Addresses used: 100,014
The demonstration was executed using this tool. The results can be seen in the following blocks:
612722: https://sys1.bcfn.ca/block/6d47796d043bb4c508d29123e6ae81b051f5e0aaef849f253c8f3a6942a022ce
612723: https://sys1.bcfn.ca/block/8e2077f743461b90f80b4bef502f564933a8e04de97972901f3d65cfadcf1faf
612724: https://sys1.bcfn.ca/block/205436d25b1b499fce44c29567c5c807beaca915b83cc9f3c35b0d76dbb11f6e
612725: https://sys1.bcfn.ca/block/776d1b1a0f90f655a6bbdf559ff5072459cbdc5682d7615ff4b78c00babdc237
612726: https://sys1.bcfn.ca/block/de4df0994253742a1ac8ac9eec8d2a8c8b0a6d72c53d6f3caa29bb6c171b0a6b
612727: https://sys1.bcfn.ca/block/e5e167c52a9decb313fbaadf49a5e34cb490f8084f642a850385476d4ef10d70
612728: https://sys1.bcfn.ca/block/ab64d989edc71890e7b5b8491c20e9a27520dc45a5f7c776d3dae79057f59fe7
612729: https://sys1.bcfn.ca/block/5e8b7ecd0e36f99d07e4ea6e135fc952bf7ec30164ab6f4d1e98b0f2d405df6d
612730: https://sys1.bcfn.ca/block/d395df3d31dde60bbb0bece6bd5b358297da878f0beb96be389e5f0e043580a3
It is important to note that this POC is not focused on Z-DAG. The performance of Z-DAG has been benchmarked within realistic network conditions: Whiteblock’s audit is publicly available. Network latency tests showed an average TPS around 15k with burst capacity up to 61k. Zero-latency control group exhibited ~150k TPS. Mainnet testing of the Z-DAG network is achievable and will require further coordination and additional resources.
Even further optimizations are expected in the upcoming Syscoin Core release which will implement a UTXO model for our token layer bringing further efficiency as well as open the door to additional scaling technology currently under research by our team and academic partners. At present our token layer is account-based, similar to Ethereum. Opt-in compliance structures will also be introduced soon which will offer some positive performance characteristics as well. It makes the most sense to implement these optimizations before performing another benchmark for Z-DAG, especially on the mainnet considering the resources required to stress-test this network.

Cost Savings

Total cost for these 100k transactions: $0.63 USD
See the live fee comparison for savings estimation between transactions on Ethereum and Syscoin. Below is a snapshot at time of writing:
ETH price: $318.55 ETH gas price: 55.00 Gwei ($0.37)
Syscoin price: $0.11
Snapshot of live fee comparison chart
Z-DAG provides a more efficient fee-market. A typical Z-DAG transaction costs 0.0000582 SYS. Tokens can be safely redeemed/re-spent within seconds or allowed to settle on-chain beforehand. The costs should remain about this low for microtransactions.
Syscoin will achieve further reduction of fees and even greater scalability with offchain payment channels for assets, with Z-DAG as a resilience fallback. New payment channel technology is one of the topics under research by the Syscoin development team with our academic partners at TU Delft. In line with the calculation in the Lightning Networks white paper, payment channels using assets with Syscoin Core will bring theoretical capacity for each person on Earth (7.8 billion) to have five on-chain transactions per year, per person, without requiring anyone to enter a fee market (aka “wait for a block”). This exceeds the minimum LN expectation of two transactions per person, per year; one to exist on-chain and one to settle aggregated value.

Tools, Infrastructure & Documentation

Syscoin Bridge

Mainnet Demonstration of Syscoin Bridge with the Basic Attention Token ERC-20
A two-way blockchain interoperability system that uses Simple Payment Verification to enable:
  • Any Standard ERC-20 token to be moved from Ethereum to the Syscoin blockchain as a Syscoin Platform Token (SPT), and back to Ethereum
  • Any SPT to be moved from Syscoin to the Ethereum blockchain as an ERC-20 token, and back to Syscoin

Benefits

  • Permissionless
  • No counterparties involved
  • No trading mechanisms involved
  • No third-party liquidity providers required
  • Cross-chain Fractional Supply - 2-way peg - Token supply maintained globally
  • ERC-20s gain vastly improved transactionality with the Syscoin Token Platform, along with the security of bitcoin-core-compliant PoW.
  • SPTs gain access to all the tooling, applications and capabilities of Ethereum for ERC-20, including smart contracts.
https://preview.redd.it/l8t2m8ldh8e51.png?width=1180&format=png&auto=webp&s=b0a955a0181746dc79aff718bd0bf607d3c3aa23
https://preview.redd.it/26htnxzfh8e51.png?width=1180&format=png&auto=webp&s=d0383d3c2ee836c9f60b57eca35542e9545f741d

Source code

https://github.com/syscoin/?q=sysethereum
Main Subprojects

API

Tools to simplify using Syscoin Bridge as a service with dapps and wallets will be released some time after implementation of Syscoin Core 4.2. These will be based upon the same processes which are automated in the current live Sysethereum Dapp that is functioning with the Syscoin mainnet.

Documentation

Syscoin Bridge & How it Works (description and process flow)
Superblock Validation Battles
HOWTO: Provision the Bridge for your ERC-20
HOWTO: Setup an Agent
Developer & User Diligence

Trade-off

The Syscoin Ethereum Bridge is secured by Agent nodes participating in a decentralized and incentivized model that involves roles of Superblock challengers and submitters. This model is open to participation. The benefits here are trust-minimization, permissionless-ness, and potentially less legal/regulatory red-tape than interop mechanisms that involve liquidity providers and/or trading mechanisms.
The trade-off is that due to the decentralized nature there are cross-chain settlement times of one hour to cross from Ethereum to Syscoin, and three hours to cross from Syscoin to Ethereum. We are exploring ways to reduce this time while maintaining decentralization via zkp. Even so, an “instant bridge” experience could be provided by means of a third-party liquidity mechanism. That option exists but is not required for bridge functionality today. Typically bridges are used with batch value, not with high frequencies of smaller values, and generally it is advantageous to keep some value on both chains for maximum availability of utility. Even so, the cross-chain settlement time is good to mention here.

Cost

Ethereum -> Syscoin: Matic or Ethereum transaction fee for bridge contract interaction, negligible Syscoin transaction fee for minting tokens
Syscoin -> Ethereum: Negligible Syscoin transaction fee for burning tokens, 0.01% transaction fee paid to Bridge Agent in the form of the ERC-20, Matic or Ethereum transaction fee for contract interaction.

Z-DAG

Zero-Confirmation Directed Acyclic Graph is an instant settlement protocol that is used as a complementary system to proof-of-work (PoW) in the confirmation of Syscoin service transactions. In essence, a Z-DAG is simply a directed acyclic graph (DAG) where validating nodes verify the sequential ordering of transactions that are received in their memory pools. Z-DAG is used by the validating nodes across the network to ensure that there is absolute consensus on the ordering of transactions and no balances are overflowed (no double-spends).

Benefits

  • Unique fee-market that is more efficient for microtransaction redemption and settlement
  • Uses decentralized means to enable tokens with value transfer scalability that is comparable or exceeds that of credit card networks
  • Provides high throughput and secure fulfillment even if blocks are full
  • Probabilistic and interactive
  • 99.9999% security assurance within 10 seconds
  • Can serve payment channels as a resilience fallback that is faster and lower-cost than falling-back directly to a blockchain
  • Each Z-DAG transaction also settles onchain through Syscoin Core at 60-second block target using SHA-256 Proof of Work consensus
https://preview.redd.it/pgbx84jih8e51.png?width=1614&format=png&auto=webp&s=5f631d42a33dc698365eb8dd184b6d442def6640

Source code

https://github.com/syscoin/syscoin

API

Syscoin-js provides tooling for all Syscoin Core RPCs including interactivity with Z-DAG.

Documentation

Z-DAG White Paper
Useful read: An in-depth Z-DAG discussion between Syscoin Core developer Jag Sidhu and Brave Software Research Engineer Gonçalo Pestana

Trade-off

Z-DAG enables the ideal speed/security tradeoff to be determined per use-case in the application layer. It minimizes the sacrifice required to accept and redeem fast transfers/payments while providing more-than-ample security for microtransactions. This is supported on the premise that a Reddit user receiving points does need security yet generally doesn’t want nor need to wait for the same level of security as a nation-state settling an international trade debt. In any case, each Z-DAG transaction settles onchain at a block target of 60 seconds.

Syscoin Specs

Syscoin 3.0 White Paper
(4.0 white paper is pending. For improved scalability and less blockchain bloat, some features of v3 no longer exist in current v4: Specifically Marketplace Offers, Aliases, Escrow, Certificates, Pruning, Encrypted Messaging)
  • 16MB block bandwidth per minute assuming segwit witness carrying transactions, and transactions ~200 bytes on average
  • SHA256 merge mined with Bitcoin
  • UTXO asset layer, with base Syscoin layer sharing identical security policies as Bitcoin Core
  • Z-DAG on asset layer, bridge to Ethereum on asset layer
  • On-chain scaling with prospect of enabling enterprise grade reliable trustless payment processing with on/offchain hybrid solution
  • Focus only on Simple Value Transfers. MVP of blockchain consensus footprint is balances and ownership of them. Everything else can reduce data availability in exchange for scale (Ethereum 2.0 model). We leave that to other designs, we focus on transfers.
  • Future integrations of MAST/Taproot to get more complex value transfers without trading off trustlessness or decentralization.
  • Zero-knowledge Proofs are a cryptographic new frontier. We are dabbling here to generalize the concept of bridging and also verify the state of a chain efficiently. We also apply it in our Digital Identity projects at Blockchain Foundry (a publicly traded company which develops Syscoin softwares for clients). We are also looking to integrate privacy preserving payment channels for off-chain payments through zkSNARK hub & spoke design which does not suffer from the HTLC attack vectors evident on LN. Much of the issues plaguing Lightning Network can be resolved using a zkSNARK design whilst also providing the ability to do a multi-asset payment channel system. Currently we found a showstopper attack (American Call Option) on LN if we were to use multiple-assets. This would not exist in a system such as this.

Wallets

Web3 and mobile wallets are under active development by Blockchain Foundry Inc as WebAssembly applications and expected for release not long after mainnet deployment of Syscoin Core 4.2. Both of these will be multi-coin wallets that support Syscoin, SPTs, Ethereum, and ERC-20 tokens. The Web3 wallet will provide functionality similar to Metamask.
Syscoin Platform and tokens are already integrated with Blockbook. Custom hardware wallet support currently exists via ElectrumSys. First-class HW wallet integration through apps such as Ledger Live will exist after 4.2.
Current supported wallets
Syscoin Spark Desktop
Syscoin-Qt

Explorers

Mainnet: https://sys1.bcfn.ca (Blockbook)
Testnet: https://explorer-testnet.blockchainfoundry.co

Thank you for close consideration of our proposal. We look forward to feedback, and to working with the Reddit community to implement an ideal solution using Syscoin Platform!

submitted by sidhujag to ethereum [link] [comments]

Why i’m bullish on Zilliqa (long read)

Edit: TL;DR added in the comments
 
Hey all, I've been researching coins since 2017 and have gone through 100s of them in the last 3 years. I got introduced to blockchain via Bitcoin of course, analyzed Ethereum thereafter and from that moment I have a keen interest in smart contact platforms. I’m passionate about Ethereum but I find Zilliqa to have a better risk-reward ratio. Especially because Zilliqa has found an elegant balance between being secure, decentralized and scalable in my opinion.
 
Below I post my analysis of why from all the coins I went through I’m most bullish on Zilliqa (yes I went through Tezos, EOS, NEO, VeChain, Harmony, Algorand, Cardano etc.). Note that this is not investment advice and although it's a thorough analysis there is obviously some bias involved. Looking forward to what you all think!
 
Fun fact: the name Zilliqa is a play on ‘silica’ silicon dioxide which means “Silicon for the high-throughput consensus computer.”
 
This post is divided into (i) Technology, (ii) Business & Partnerships, and (iii) Marketing & Community. I’ve tried to make the technology part readable for a broad audience. If you’ve ever tried understanding the inner workings of Bitcoin and Ethereum you should be able to grasp most parts. Otherwise, just skim through and once you are zoning out head to the next part.
 
Technology and some more:
 
Introduction
 
The technology is one of the main reasons why I’m so bullish on Zilliqa. First thing you see on their website is: “Zilliqa is a high-performance, high-security blockchain platform for enterprises and next-generation applications.” These are some bold statements.
 
Before we deep dive into the technology let’s take a step back in time first as they have quite the history. The initial research paper from which Zilliqa originated dates back to August 2016: Elastico: A Secure Sharding Protocol For Open Blockchains where Loi Luu (Kyber Network) is one of the co-authors. Other ideas that led to the development of what Zilliqa has become today are: Bitcoin-NG, collective signing CoSi, ByzCoin and Omniledger.
 
The technical white paper was made public in August 2017 and since then they have achieved everything stated in the white paper and also created their own open source intermediate level smart contract language called Scilla (functional programming language similar to OCaml) too.
 
Mainnet is live since the end of January 2019 with daily transaction rates growing continuously. About a week ago mainnet reached 5 million transactions, 500.000+ addresses in total along with 2400 nodes keeping the network decentralized and secure. Circulating supply is nearing 11 billion and currently only mining rewards are left. The maximum supply is 21 billion with annual inflation being 7.13% currently and will only decrease with time.
 
Zilliqa realized early on that the usage of public cryptocurrencies and smart contracts were increasing but decentralized, secure, and scalable alternatives were lacking in the crypto space. They proposed to apply sharding onto a public smart contract blockchain where the transaction rate increases almost linear with the increase in the amount of nodes. More nodes = higher transaction throughput and increased decentralization. Sharding comes in many forms and Zilliqa uses network-, transaction- and computational sharding. Network sharding opens up the possibility of using transaction- and computational sharding on top. Zilliqa does not use state sharding for now. We’ll come back to this later.
 
Before we continue dissecting how Zilliqa achieves such from a technological standpoint it’s good to keep in mind that a blockchain being decentralised and secure and scalable is still one of the main hurdles in allowing widespread usage of decentralised networks. In my opinion this needs to be solved first before blockchains can get to the point where they can create and add large scale value. So I invite you to read the next section to grasp the underlying fundamentals. Because after all these premises need to be true otherwise there isn’t a fundamental case to be bullish on Zilliqa, right?
 
Down the rabbit hole
 
How have they achieved this? Let’s define the basics first: key players on Zilliqa are the users and the miners. A user is anybody who uses the blockchain to transfer funds or run smart contracts. Miners are the (shard) nodes in the network who run the consensus protocol and get rewarded for their service in Zillings (ZIL). The mining network is divided into several smaller networks called shards, which is also referred to as ‘network sharding’. Miners subsequently are randomly assigned to a shard by another set of miners called DS (Directory Service) nodes. The regular shards process transactions and the outputs of these shards are eventually combined by the DS shard as they reach consensus on the final state. More on how these DS shards reach consensus (via pBFT) will be explained later on.
 
The Zilliqa network produces two types of blocks: DS blocks and Tx blocks. One DS Block consists of 100 Tx Blocks. And as previously mentioned there are two types of nodes concerned with reaching consensus: shard nodes and DS nodes. Becoming a shard node or DS node is being defined by the result of a PoW cycle (Ethash) at the beginning of the DS Block. All candidate mining nodes compete with each other and run the PoW (Proof-of-Work) cycle for 60 seconds and the submissions achieving the highest difficulty will be allowed on the network. And to put it in perspective: the average difficulty for one DS node is ~ 2 Th/s equaling 2.000.000 Mh/s or 55 thousand+ GeForce GTX 1070 / 8 GB GPUs at 35.4 Mh/s. Each DS Block 10 new DS nodes are allowed. And a shard node needs to provide around 8.53 GH/s currently (around 240 GTX 1070s). Dual mining ETH/ETC and ZIL is possible and can be done via mining software such as Phoenix and Claymore. There are pools and if you have large amounts of hashing power (Ethash) available you could mine solo.
 
The PoW cycle of 60 seconds is a peak performance and acts as an entry ticket to the network. The entry ticket is called a sybil resistance mechanism and makes it incredibly hard for adversaries to spawn lots of identities and manipulate the network with these identities. And after every 100 Tx Blocks which corresponds to roughly 1,5 hour this PoW process repeats. In between these 1,5 hour, no PoW needs to be done meaning Zilliqa’s energy consumption to keep the network secure is low. For more detailed information on how mining works click here.
Okay, hats off to you. You have made it this far. Before we go any deeper down the rabbit hole we first must understand why Zilliqa goes through all of the above technicalities and understand a bit more what a blockchain on a more fundamental level is. Because the core of Zilliqa’s consensus protocol relies on the usage of pBFT (practical Byzantine Fault Tolerance) we need to know more about state machines and their function. Navigate to Viewblock, a Zilliqa block explorer, and just come back to this article. We will use this site to navigate through a few concepts.
 
We have established that Zilliqa is a public and distributed blockchain. Meaning that everyone with an internet connection can send ZILs, trigger smart contracts, etc. and there is no central authority who fully controls the network. Zilliqa and other public and distributed blockchains (like Bitcoin and Ethereum) can also be defined as state machines.
 
Taking the liberty of paraphrasing examples and definitions given by Samuel Brooks’ medium article, he describes the definition of a blockchain (like Zilliqa) as: “A peer-to-peer, append-only datastore that uses consensus to synchronize cryptographically-secure data”.
 
Next, he states that: "blockchains are fundamentally systems for managing valid state transitions”. For some more context, I recommend reading the whole medium article to get a better grasp of the definitions and understanding of state machines. Nevertheless, let’s try to simplify and compile it into a single paragraph. Take traffic lights as an example: all its states (red, amber, and green) are predefined, all possible outcomes are known and it doesn’t matter if you encounter the traffic light today or tomorrow. It will still behave the same. Managing the states of a traffic light can be done by triggering a sensor on the road or pushing a button resulting in one traffic lights’ state going from green to red (via amber) and another light from red to green.
 
With public blockchains like Zilliqa, this isn’t so straightforward and simple. It started with block #1 almost 1,5 years ago and every 45 seconds or so a new block linked to the previous block is being added. Resulting in a chain of blocks with transactions in it that everyone can verify from block #1 to the current #647.000+ block. The state is ever changing and the states it can find itself in are infinite. And while the traffic light might work together in tandem with various other traffic lights, it’s rather insignificant comparing it to a public blockchain. Because Zilliqa consists of 2400 nodes who need to work together to achieve consensus on what the latest valid state is while some of these nodes may have latency or broadcast issues, drop offline or are deliberately trying to attack the network, etc.
 
Now go back to the Viewblock page take a look at the amount of transaction, addresses, block and DS height and then hit refresh. Obviously as expected you see new incremented values on one or all parameters. And how did the Zilliqa blockchain manage to transition from a previous valid state to the latest valid state? By using pBFT to reach consensus on the latest valid state.
 
After having obtained the entry ticket, miners execute pBFT to reach consensus on the ever-changing state of the blockchain. pBFT requires a series of network communication between nodes, and as such there is no GPU involved (but CPU). Resulting in the total energy consumed to keep the blockchain secure, decentralized and scalable being low.
 
pBFT stands for practical Byzantine Fault Tolerance and is an optimization on the Byzantine Fault Tolerant algorithm. To quote Blockonomi: “In the context of distributed systems, Byzantine Fault Tolerance is the ability of a distributed computer network to function as desired and correctly reach a sufficient consensus despite malicious components (nodes) of the system failing or propagating incorrect information to other peers.” Zilliqa is such a distributed computer network and depends on the honesty of the nodes (shard and DS) to reach consensus and to continuously update the state with the latest block. If pBFT is a new term for you I can highly recommend the Blockonomi article.
 
The idea of pBFT was introduced in 1999 - one of the authors even won a Turing award for it - and it is well researched and applied in various blockchains and distributed systems nowadays. If you want more advanced information than the Blockonomi link provides click here. And if you’re in between Blockonomi and the University of Singapore read the Zilliqa Design Story Part 2 dating from October 2017.
Quoting from the Zilliqa tech whitepaper: “pBFT relies upon a correct leader (which is randomly selected) to begin each phase and proceed when the sufficient majority exists. In case the leader is byzantine it can stall the entire consensus protocol. To address this challenge, pBFT offers a view change protocol to replace the byzantine leader with another one.”
 
pBFT can tolerate ⅓ of the nodes being dishonest (offline counts as Byzantine = dishonest) and the consensus protocol will function without stalling or hiccups. Once there are more than ⅓ of dishonest nodes but no more than ⅔ the network will be stalled and a view change will be triggered to elect a new DS leader. Only when more than ⅔ of the nodes are dishonest (66%) double-spend attacks become possible.
 
If the network stalls no transactions can be processed and one has to wait until a new honest leader has been elected. When the mainnet was just launched and in its early phases, view changes happened regularly. As of today the last stalling of the network - and view change being triggered - was at the end of October 2019.
 
Another benefit of using pBFT for consensus besides low energy is the immediate finality it provides. Once your transaction is included in a block and the block is added to the chain it’s done. Lastly, take a look at this article where three types of finality are being defined: probabilistic, absolute and economic finality. Zilliqa falls under the absolute finality (just like Tendermint for example). Although lengthy already we skipped through some of the inner workings from Zilliqa’s consensus: read the Zilliqa Design Story Part 3 and you will be close to having a complete picture on it. Enough about PoW, sybil resistance mechanism, pBFT, etc. Another thing we haven’t looked at yet is the amount of decentralization.
 
Decentralisation
 
Currently, there are four shards, each one of them consisting of 600 nodes. 1 shard with 600 so-called DS nodes (Directory Service - they need to achieve a higher difficulty than shard nodes) and 1800 shard nodes of which 250 are shard guards (centralized nodes controlled by the team). The amount of shard guards has been steadily declining from 1200 in January 2019 to 250 as of May 2020. On the Viewblock statistics, you can see that many of the nodes are being located in the US but those are only the (CPU parts of the) shard nodes who perform pBFT. There is no data from where the PoW sources are coming. And when the Zilliqa blockchain starts reaching its transaction capacity limit, a network upgrade needs to be executed to lift the current cap of maximum 2400 nodes to allow more nodes and formation of more shards which will allow to network to keep on scaling according to demand.
Besides shard nodes there are also seed nodes. The main role of seed nodes is to serve as direct access points (for end-users and clients) to the core Zilliqa network that validates transactions. Seed nodes consolidate transaction requests and forward these to the lookup nodes (another type of nodes) for distribution to the shards in the network. Seed nodes also maintain the entire transaction history and the global state of the blockchain which is needed to provide services such as block explorers. Seed nodes in the Zilliqa network are comparable to Infura on Ethereum.
 
The seed nodes were first only operated by Zilliqa themselves, exchanges and Viewblock. Operators of seed nodes like exchanges had no incentive to open them for the greater public. They were centralised at first. Decentralisation at the seed nodes level has been steadily rolled out since March 2020 ( Zilliqa Improvement Proposal 3 ). Currently the amount of seed nodes is being increased, they are public-facing and at the same time PoS is applied to incentivize seed node operators and make it possible for ZIL holders to stake and earn passive yields. Important distinction: seed nodes are not involved with consensus! That is still PoW as entry ticket and pBFT for the actual consensus.
 
5% of the block rewards are being assigned to seed nodes (from the beginning in 2019) and those are being used to pay out ZIL stakers. The 5% block rewards with an annual yield of 10.03% translate to roughly 610 MM ZILs in total that can be staked. Exchanges use the custodial variant of staking and wallets like Moonlet will use the non-custodial version (starting in Q3 2020). Staking is being done by sending ZILs to a smart contract created by Zilliqa and audited by Quantstamp.
 
With a high amount of DS; shard nodes and seed nodes becoming more decentralized too, Zilliqa qualifies for the label of decentralized in my opinion.
 
Smart contracts
 
Let me start by saying I’m not a developer and my programming skills are quite limited. So I‘m taking the ELI5 route (maybe 12) but if you are familiar with Javascript, Solidity or specifically OCaml please head straight to Scilla - read the docs to get a good initial grasp of how Zilliqa’s smart contract language Scilla works and if you ask yourself “why another programming language?” check this article. And if you want to play around with some sample contracts in an IDE click here. The faucet can be found here. And more information on architecture, dapp development and API can be found on the Developer Portal.
If you are more into listening and watching: check this recent webinar explaining Zilliqa and Scilla. Link is time-stamped so you’ll start right away with a platform introduction, roadmap 2020 and afterwards a proper Scilla introduction.
 
Generalized: programming languages can be divided into being ‘object-oriented’ or ‘functional’. Here is an ELI5 given by software development academy: * “all programs have two basic components, data – what the program knows – and behavior – what the program can do with that data. So object-oriented programming states that combining data and related behaviors in one place, is called “object”, which makes it easier to understand how a particular program works. On the other hand, functional programming argues that data and behavior are different things and should be separated to ensure their clarity.” *
 
Scilla is on the functional side and shares similarities with OCaml: OCaml is a general-purpose programming language with an emphasis on expressiveness and safety. It has an advanced type system that helps catch your mistakes without getting in your way. It's used in environments where a single mistake can cost millions and speed matters, is supported by an active community, and has a rich set of libraries and development tools. For all its power, OCaml is also pretty simple, which is one reason it's often used as a teaching language.
 
Scilla is blockchain agnostic, can be implemented onto other blockchains as well, is recognized by academics and won a so-called Distinguished Artifact Award award at the end of last year.
 
One of the reasons why the Zilliqa team decided to create their own programming language focused on preventing smart contract vulnerabilities is that adding logic on a blockchain, programming, means that you cannot afford to make mistakes. Otherwise, it could cost you. It’s all great and fun blockchains being immutable but updating your code because you found a bug isn’t the same as with a regular web application for example. And with smart contracts, it inherently involves cryptocurrencies in some form thus value.
 
Another difference with programming languages on a blockchain is gas. Every transaction you do on a smart contract platform like Zilliqa or Ethereum costs gas. With gas you basically pay for computational costs. Sending a ZIL from address A to address B costs 0.001 ZIL currently. Smart contracts are more complex, often involve various functions and require more gas (if gas is a new concept click here ).
 
So with Scilla, similar to Solidity, you need to make sure that “every function in your smart contract will run as expected without hitting gas limits. An improper resource analysis may lead to situations where funds may get stuck simply because a part of the smart contract code cannot be executed due to gas limits. Such constraints are not present in traditional software systems”. Scilla design story part 1
 
Some examples of smart contract issues you’d want to avoid are: leaking funds, ‘unexpected changes to critical state variables’ (example: someone other than you setting his or her address as the owner of the smart contract after creation) or simply killing a contract.
 
Scilla also allows for formal verification. Wikipedia to the rescue: In the context of hardware and software systems, formal verification is the act of proving or disproving the correctness of intended algorithms underlying a system with respect to a certain formal specification or property, using formal methods of mathematics.
 
Formal verification can be helpful in proving the correctness of systems such as: cryptographic protocols, combinational circuits, digital circuits with internal memory, and software expressed as source code.
 
Scilla is being developed hand-in-hand with formalization of its semantics and its embedding into the Coq proof assistant — a state-of-the art tool for mechanized proofs about properties of programs.”
 
Simply put, with Scilla and accompanying tooling developers can be mathematically sure and proof that the smart contract they’ve written does what he or she intends it to do.
 
Smart contract on a sharded environment and state sharding
 
There is one more topic I’d like to touch on: smart contract execution in a sharded environment (and what is the effect of state sharding). This is a complex topic. I’m not able to explain it any easier than what is posted here. But I will try to compress the post into something easy to digest.
 
Earlier on we have established that Zilliqa can process transactions in parallel due to network sharding. This is where the linear scalability comes from. We can define simple transactions: a transaction from address A to B (Category 1), a transaction where a user interacts with one smart contract (Category 2) and the most complex ones where triggering a transaction results in multiple smart contracts being involved (Category 3). The shards are able to process transactions on their own without interference of the other shards. With Category 1 transactions that is doable, with Category 2 transactions sometimes if that address is in the same shard as the smart contract but with Category 3 you definitely need communication between the shards. Solving that requires to make a set of communication rules the protocol needs to follow in order to process all transactions in a generalised fashion.
 
And this is where the downsides of state sharding comes in currently. All shards in Zilliqa have access to the complete state. Yes the state size (0.1 GB at the moment) grows and all of the nodes need to store it but it also means that they don’t need to shop around for information available on other shards. Requiring more communication and adding more complexity. Computer science knowledge and/or developer knowledge required links if you want to dig further: Scilla - language grammar Scilla - Foundations for Verifiable Decentralised Computations on a Blockchain Gas Accounting NUS x Zilliqa: Smart contract language workshop
 
Easier to follow links on programming Scilla https://learnscilla.com/home Ivan on Tech
 
Roadmap / Zilliqa 2.0
 
There is no strict defined roadmap but here are topics being worked on. And via the Zilliqa website there is also more information on the projects they are working on.
 
Business & Partnerships
 
It’s not only technology in which Zilliqa seems to be excelling as their ecosystem has been expanding and starting to grow rapidly. The project is on a mission to provide OpenFinance (OpFi) to the world and Singapore is the right place to be due to its progressive regulations and futuristic thinking. Singapore has taken a proactive approach towards cryptocurrencies by introducing the Payment Services Act 2019 (PS Act). Among other things, the PS Act will regulate intermediaries dealing with certain cryptocurrencies, with a particular focus on consumer protection and anti-money laundering. It will also provide a stable regulatory licensing and operating framework for cryptocurrency entities, effectively covering all crypto businesses and exchanges based in Singapore. According to PWC 82% of the surveyed executives in Singapore reported blockchain initiatives underway and 13% of them have already brought the initiatives live to the market. There is also an increasing list of organizations that are starting to provide digital payment services. Moreover, Singaporean blockchain developers Building Cities Beyond has recently created an innovation $15 million grant to encourage development on its ecosystem. This all suggests that Singapore tries to position itself as (one of) the leading blockchain hubs in the world.
 
Zilliqa seems to already take advantage of this and recently helped launch Hg Exchange on their platform, together with financial institutions PhillipCapital, PrimePartners and Fundnel. Hg Exchange, which is now approved by the Monetary Authority of Singapore (MAS), uses smart contracts to represent digital assets. Through Hg Exchange financial institutions worldwide can use Zilliqa's safe-by-design smart contracts to enable the trading of private equities. For example, think of companies such as Grab, Airbnb, SpaceX that are not available for public trading right now. Hg Exchange will allow investors to buy shares of private companies & unicorns and capture their value before an IPO. Anquan, the main company behind Zilliqa, has also recently announced that they became a partner and shareholder in TEN31 Bank, which is a fully regulated bank allowing for tokenization of assets and is aiming to bridge the gap between conventional banking and the blockchain world. If STOs, the tokenization of assets, and equity trading will continue to increase, then Zilliqa’s public blockchain would be the ideal candidate due to its strategic positioning, partnerships, regulatory compliance and the technology that is being built on top of it.
 
What is also very encouraging is their focus on banking the un(der)banked. They are launching a stablecoin basket starting with XSGD. As many of you know, stablecoins are currently mostly used for trading. However, Zilliqa is actively trying to broaden the use case of stablecoins. I recommend everybody to read this text that Amrit Kumar wrote (one of the co-founders). These stablecoins will be integrated in the traditional markets and bridge the gap between the crypto world and the traditional world. This could potentially revolutionize and legitimise the crypto space if retailers and companies will for example start to use stablecoins for payments or remittances, instead of it solely being used for trading.
 
Zilliqa also released their DeFi strategic roadmap (dating November 2019) which seems to be aligning well with their OpFi strategy. A non-custodial DEX is coming to Zilliqa made by Switcheo which allows cross-chain trading (atomic swaps) between ETH, EOS and ZIL based tokens. They also signed a Memorandum of Understanding for a (soon to be announced) USD stablecoin. And as Zilliqa is all about regulations and being compliant, I’m speculating on it to be a regulated USD stablecoin. Furthermore, XSGD is already created and visible on block explorer and XIDR (Indonesian Stablecoin) is also coming soon via StraitsX. Here also an overview of the Tech Stack for Financial Applications from September 2019. Further quoting Amrit Kumar on this:
 
There are two basic building blocks in DeFi/OpFi though: 1) stablecoins as you need a non-volatile currency to get access to this market and 2) a dex to be able to trade all these financial assets. The rest are built on top of these blocks.
 
So far, together with our partners and community, we have worked on developing these building blocks with XSGD as a stablecoin. We are working on bringing a USD-backed stablecoin as well. We will soon have a decentralised exchange developed by Switcheo. And with HGX going live, we are also venturing into the tokenization space. More to come in the future.”
 
Additionally, they also have this ZILHive initiative that injects capital into projects. There have been already 6 waves of various teams working on infrastructure, innovation and research, and they are not from ASEAN or Singapore only but global: see Grantees breakdown by country. Over 60 project teams from over 20 countries have contributed to Zilliqa's ecosystem. This includes individuals and teams developing wallets, explorers, developer toolkits, smart contract testing frameworks, dapps, etc. As some of you may know, Unstoppable Domains (UD) blew up when they launched on Zilliqa. UD aims to replace cryptocurrency addresses with a human-readable name and allows for uncensorable websites. Zilliqa will probably be the only one able to handle all these transactions onchain due to ability to scale and its resulting low fees which is why the UD team launched this on Zilliqa in the first place. Furthermore, Zilliqa also has a strong emphasis on security, compliance, and privacy, which is why they partnered with companies like Elliptic, ChainSecurity (part of PwC Switzerland), and Incognito. Their sister company Aqilliz (Zilliqa spelled backwards) focuses on revolutionizing the digital advertising space and is doing interesting things like using Zilliqa to track outdoor digital ads with companies like Foodpanda.
 
Zilliqa is listed on nearly all major exchanges, having several different fiat-gateways and recently have been added to Binance’s margin trading and futures trading with really good volume. They also have a very impressive team with good credentials and experience. They don't just have “tech people”. They have a mix of tech people, business people, marketeers, scientists, and more. Naturally, it's good to have a mix of people with different skill sets if you work in the crypto space.
 
Marketing & Community
 
Zilliqa has a very strong community. If you just follow their Twitter their engagement is much higher for a coin that has approximately 80k followers. They also have been ‘coin of the day’ by LunarCrush many times. LunarCrush tracks real-time cryptocurrency value and social data. According to their data, it seems Zilliqa has a more fundamental and deeper understanding of marketing and community engagement than almost all other coins. While almost all coins have been a bit frozen in the last months, Zilliqa seems to be on its own bull run. It was somewhere in the 100s a few months ago and is currently ranked #46 on CoinGecko. Their official Telegram also has over 20k people and is very active, and their community channel which is over 7k now is more active and larger than many other official channels. Their local communities also seem to be growing.
 
Moreover, their community started ‘Zillacracy’ together with the Zilliqa core team ( see www.zillacracy.com ). It’s a community-run initiative where people from all over the world are now helping with marketing and development on Zilliqa. Since its launch in February 2020 they have been doing a lot and will also run their own non-custodial seed node for staking. This seed node will also allow them to start generating revenue for them to become a self sustaining entity that could potentially scale up to become a decentralized company working in parallel with the Zilliqa core team. Comparing it to all the other smart contract platforms (e.g. Cardano, EOS, Tezos etc.) they don't seem to have started a similar initiative (correct me if I’m wrong though). This suggests in my opinion that these other smart contract platforms do not fully understand how to utilize the ‘power of the community’. This is something you cannot ‘buy with money’ and gives many projects in the space a disadvantage.
 
Zilliqa also released two social products called SocialPay and Zeeves. SocialPay allows users to earn ZILs while tweeting with a specific hashtag. They have recently used it in partnership with the Singapore Red Cross for a marketing campaign after their initial pilot program. It seems like a very valuable social product with a good use case. I can see a lot of traditional companies entering the space through this product, which they seem to suggest will happen. Tokenizing hashtags with smart contracts to get network effect is a very smart and innovative idea.
 
Regarding Zeeves, this is a tipping bot for Telegram. They already have 1000s of signups and they plan to keep upgrading it for more and more people to use it (e.g. they recently have added a quiz features). They also use it during AMAs to reward people in real-time. It’s a very smart approach to grow their communities and get familiar with ZIL. I can see this becoming very big on Telegram. This tool suggests, again, that the Zilliqa team has a deeper understanding of what the crypto space and community needs and is good at finding the right innovative tools to grow and scale.
 
To be honest, I haven’t covered everything (i’m also reaching the character limited haha). So many updates happening lately that it's hard to keep up, such as the International Monetary Fund mentioning Zilliqa in their report, custodial and non-custodial Staking, Binance Margin, Futures, Widget, entering the Indian market, and more. The Head of Marketing Colin Miles has also released this as an overview of what is coming next. And last but not least, Vitalik Buterin has been mentioning Zilliqa lately acknowledging Zilliqa and mentioning that both projects have a lot of room to grow. There is much more info of course and a good part of it has been served to you on a silver platter. I invite you to continue researching by yourself :-) And if you have any comments or questions please post here!
submitted by haveyouheardaboutit to CryptoCurrency [link] [comments]

[ANN][ANDROID MINING][AIRDROP] NewEnglandcoin: Scrypt RandomSpike

New England
New England 6 States Songs: https://www.reddit.com/newengland/comments/er8wxd/new_england_6_states_songs/
NewEnglandcoin
Symbol: NENG
NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones.
Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt.
1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377
NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number
Bitcoin Fork - Suitable for Home Hobbyists
NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs.
The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity.
MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018)
https://www.youtube.com/playlist?list=PLUl4u3cNGP63UUkfL0onkxF6MYgVa04Fn
CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software.
Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%.
NENG v1.4.0 release enabled CPU mining inside android phones.
Youtube Video Tutorial
How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 https://www.youtube.com/watch?v=sdOoPvAjzlE How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2 https://www.youtube.com/watch?v=nHnRJvJRzZg
How to CPU Mine NewEnglandcoin (NENG) in macOS https://www.youtube.com/watch?v=Zj7NLMeNSOQ
Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG.
We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange.
Twitter Airdrop
Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners
Graphic Redesign Bounty
Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at: https://discord.gg/UPeBwgs
Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form.
Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues.
Twitter Airdrop/Graphic Redesign bounty sign up: https://goo.gl/forms/L0vcwmVi8c76cR7m1
Milestones
Roadmap
NENG v1.4.0 Android Mining, randomSpike Evaluation https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/NENG_2020_Q3_report/NENG_2020_Q3_report.pdf
RandomSpike - NENG core v1.3.0 Hardfork Upgrade Proposal https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/2020Q1_Report/Scrypt_RandomSpike_NENGv1.3.0_Hardfork_Proposal.pdf
NENG Security, Decentralization & Valuation
https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/2019Q2_report/NENG_Security_Decentralization_Value.pdf
Whitepaper v1.0 https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/whitepaper_v1.0/NENG_WhitePaper.pdf
DISCORD https://discord.gg/UPeBwgs
Explorer
http://www.findblocks.com/exploreNENG http://86.100.49.209/exploreNENG http://nengexplorer.mooo.com:3001/
Step by step guide on how to setup an explorer: https://github.com/ShorelineCrypto/nengexplorer
Github https://github.com/ShorelineCrypto/NewEnglandCoin
Wallet
Android with UserLand App (arm64/armhf), Chromebook (x64/arm64/armhf): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.5
Linux Wallet (Ubuntu/Linux Mint, Debian/MX Linux, Arch/Manjaro, Fedora, openSUSE): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.3
MacOS Wallet (10.11 El Capitan or higher): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.2
Android with GNUroot on 32 bits old Phones (alpha release) wallet: https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0
Windows wallet: https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.3.0.1
addnode ip address for the wallet to sync faster, frequently updated conf file: https://github.com/ShorelineCrypto/cheetah_cpumineblob/mastenewenglandcoin.conf-example
How to Sync Full Node Desktop Wallet https://www.reddit.com/NewEnglandCoin/comments/er6f0q/how_to_sync_full_node_desktop_wallet/
TWITTER https://twitter.com/newenglandcoin
REDDIT https://www.reddit.com/NewEnglandCoin/
Cheetah CPU Miner Software https://github.com/ShorelineCrypto/cheetah_cpuminer
Solo Mining with GPU or ASIC https://bitcointalk.org/index.php?topic=5027091.msg52187727#msg52187727
How to Run Two Full Node in Same Desktop PC https://bitcointalk.org/index.php?topic=5027091.msg53581449#msg53581449
ASIC/GPU Mining Pools Warning to Big ASIC Miners Due to DynDiff Algo on top of Scrypt, solo mining is recommended for ASIC/GPU miners. Further more, even for mining pools, small mining pool will generate better performance than big NENG mining pool because of new algo v1.2.x post hard fork.
The set up configuration of NENG for scrypt pool mining is same as a typical normal scrypt coin. In other word, DynDiff on Scrypt algo is backward compatible with Scrypt algo. Because ASIC/GPU miners rely on CPU miners for smooth blockchain movement, checkout bottom of "Latest News" section for A WARNING to All ASIC miners before you decide to dump big ASIC hash rate into NENG mining.
(1) Original DynDiff Warning: https://bitcointalk.org/index.php?topic=5027091.msg48324708#msg48324708 (2) New Warning on RandomSpike Spike difficulty (244k) introduced in RandomSpike served as roadblocks to instant mining and provide security against 51% attack risk. However, this spike difficulty like a roadblock that makes big ASIC mining less profitable. In case of spike block to be mined, the spike difficulty immediately serve as base difficulty, which will block GPU/ASIC miners effectively and leave CPU cheetah solo miners dominating mining almost 100% until next base difficulty reset.
FindBlocks http://findblocks.com/
CRpool http://crpool.xyz/
Cminors' Pool http://newenglandcoin.cminors-pool.com/
SPOOL https://spools.online/
Exchange
📷
https://shorelinecrypto.com/
Features: anonymous sign up and trading. No restriction or limit on deposit or withdraw.
The trading pairs available: NewEnglandcoin (NENG) / Dogecoin (DOGE)
Trading commission: A round trip trading will incur 0.10% trading fees in average. Fees are paid only on buyer side. buy fee: 0.2% / sell fee: 0% Deposit fees: free for all coins Withdraw fees: ZERO per withdraw. Mining fees are appointed by each coin blockchain. To cover the blockchain mining fees, there is minimum balance per coin per account: * Dogecoin 2 DOGE * NewEnglandcoin 1 NENG
Latest News Aug 30, 2020 - NENG v1.4.0.5 Released for Android/Chromebook Upgrade with armhf, better hardware support https://bitcointalk.org/index.php?topic=5027091.msg55098029#msg55098029
Aug 11, 2020 - NENG v1.4.0.4 Released for Android arm64 Upgrade / Chromebook Support https://bitcointalk.org/index.php?topic=5027091.msg54977437#msg54977437
Jul 30, 2020 - NENG v1.4.0.3 Released for Linux Wallet Upgrade with 8 Distros https://bitcointalk.org/index.php?topic=5027091.msg54898540#msg54898540
Jul 21, 2020 - NENG v1.4.0.2 Released for MacOS Upgrade with Catalina https://bitcointalk.org/index.php?topic=5027091.msg54839522#msg54839522
Jul 19, 2020 - NENG v1.4.0.1 Released for MacOS Wallet Upgrade https://bitcointalk.org/index.php?topic=5027091.msg54830333#msg54830333
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining, Ubuntu 20.04 support https://bitcointalk.org/index.php?topic=5027091.msg54803639#msg54803639
Jul 11, 2020 - NENG v1.4.0 Android Mining, randomSpike Evaluation https://bitcointalk.org/index.php?topic=5027091.msg54777222#msg54777222
Jun 27, 2020 - Pre-Announce: NENG v1.4.0 Proposal for Mobile Miner Upgrade, Android Mining Start in July 2020 https://bitcointalk.org/index.php?topic=5027091.msg54694233#msg54694233
Jun 19, 2020 - Best Practice for Futurebit Moonlander2 USB ASIC on solo mining mode https://bitcointalk.org/index.php?topic=5027091.msg54645726#msg54645726
Mar 15, 2020 - Scrypt RandomSpike - NENG v1.3.0.1 Released for better wallet syncing https://bitcointalk.org/index.php?topic=5027091.msg54030923#msg54030923
Feb 23, 2020 - Scrypt RandomSpike - NENG Core v1.3.0 Relased, Hardfork on Mar 1 https://bitcointalk.org/index.php?topic=5027091.msg53900926#msg53900926
Feb 1, 2020 - Scrypt RandomSpike Proposal Published- NENG 1.3.0 Hardfork https://bitcointalk.org/index.php?topic=5027091.msg53735458#msg53735458
Jan 15, 2020 - NewEnglandcoin Dev Team Expanded with New Kickoff https://bitcointalk.org/index.php?topic=5027091.msg53617358#msg53617358
Jan 12, 2020 - Explanation of Base Diff Reset and Effect of Supply https://www.reddit.com/NewEnglandCoin/comments/envmo1/explanation_of_base_diff_reset_and_effect_of/
Dec 19, 2019 - Shoreline_tradingbot version 1.0 is released https://bitcointalk.org/index.php?topic=5121953.msg53391184#msg53391184
Sept 1, 2019 - NewEnglandcoin (NENG) is Selected as Shoreline Tradingbot First Supported Coin https://bitcointalk.org/index.php?topic=5027091.msg52331201#msg52331201
Aug 15, 2019 - Mining Update on Effect of Base Difficulty Reset, GPU vs ASIC https://bitcointalk.org/index.php?topic=5027091.msg52169572#msg52169572
Jul 7, 2019 - CPU Mining on macOS Mojave is supported under latest Cheetah_Cpuminer Release https://bitcointalk.org/index.php?topic=5027091.msg51745839#msg51745839
Jun 1, 2019 - NENG Fiat project is stopped by Square, Inc https://bitcointalk.org/index.php?topic=5027091.msg51312291#msg51312291
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto https://bitcointalk.org/index.php?topic=5027091.msg50714764#msg50714764
Apr 7, 2019 - Announcement of Fiat Project for all U.S. Residents & Mobile Miner Project Initiation https://bitcointalk.org/index.php?topic=5027091.msg50506585#msg50506585
Apr 1, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50417196#msg50417196
Mar 27, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50332097#msg50332097
Mar 17, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50208194#msg50208194
Feb 26, 2019 - Community Project - NewEnglandcoin Graphic Redesign Bounty Initiated https://bitcointalk.org/index.php?topic=5027091.msg49931305#msg49931305
Feb 22, 2019 - Dev Policy on Checkpoints on NewEnglandcoin https://bitcointalk.org/index.php?topic=5027091.msg49875242#msg49875242
Feb 20, 2019 - NewEnglandCoin v1.2.1 Released to Secure the Hard Kork https://bitcointalk.org/index.php?topic=5027091.msg49831059#msg49831059
Feb 11, 2019 - NewEnglandCoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork https://bitcointalk.org/index.php?topic=5027091.msg49685389#msg49685389
Jan 13, 2019 - Cheetah_CpuMiner added support for CPU Mining on Mac https://bitcointalk.org/index.php?topic=5027091.msg49218760#msg49218760
Jan 12, 2019 - NENG Core v1.1.2 Released to support MacOS OSX Wallet https://bitcointalk.org/index.php?topic=5027091.msg49202088#msg49202088
Jan 2, 2019 - Cheetah_Cpuminer v1.1.0 is released for both Linux and Windows https://bitcointalk.org/index.php?topic=5027091.msg49004345#msg49004345
Dec 31, 2018 - Technical Whitepaper is Released https://bitcointalk.org/index.php?topic=5027091.msg48990334#msg48990334
Dec 28, 2018 - Cheetah_Cpuminer v1.0.0 is released for Linux https://bitcointalk.org/index.php?topic=5027091.msg48935135#msg48935135
Update on Dec 14, 2018 - NENG Blockchain Stuck Issue https://bitcointalk.org/index.php?topic=5027091.msg48668375#msg48668375
Nov 27, 2018 - Exclusive for PC CPU Miners - How to Steal a Block from ASIC Miners https://bitcointalk.org/index.php?topic=5027091.msg48258465#msg48258465
Nov 28, 2018 - How to CPU Mine a NENG block with window/linux PC https://bitcointalk.org/index.php?topic=5027091.msg48298311#msg48298311
Nov 29, 2018 - A Warning to ASIC Miners https://bitcointalk.org/index.php?topic=5027091.msg48324708#msg48324708
Disclosure: Dev Team Came from ShorelineCrypto, a US based Informatics Service Business offering Fee for service for Coin Creation, Coin Exchange Listing, Blockchain Consulting, etc.
submitted by honglu69 to NewEnglandCoin [link] [comments]

On F-Droid apps and bitcoin donations

The recent post on FOSS android apps and how they can earn money made me curious about their bitcoin donations, so I slapped together a quick script, grabbed the donation addresses from the F-Droid metadata and queried their total received amount.
The result, sorted by total received and valued using some value of today (9366.36 EUR per BTC)

Package address total EUR
net.i2p.android.router 1BPdWwovytfGdBwUDVgqbMZ8omcPQzshpX 100.35295704 939941.92
net.i2p.android 1BPdWwovytfGdBwUDVgqbMZ8omcPQzshpX 100.35295704 939941.92
com.piratebayfree 1KeBs4HBQzkdHC2ou3gpyGHqcL7aKzwTve 76.80127006 719348.34
org.asnelt.derandom 1NZz4TGpJ1VL4Qmqw7aRAurASAT3Cq5S6s 60.84434648 569890.05
com.nononsenseapps.notepad 16DUL1X4yARfM88GN7TV6Y3wQwqrstJs7A 58.40632213 547054.64
ch.blinkenlights.android.vanilla 1adrianERDJusC4c8whyT81zAuiENEqub 52.62216723 492878.16
org.fdroid.fdroid.privileged.ota 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
org.fdroid.fdroid.privileged 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
org.fdroid.fdroid.ota 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
org.fdroid.fdroid 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
org.fdroid.basic 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
de.k3b.android.lossless_jpg_crop 15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18 52.00899644 487134.98
org.calyxinstitute.vpn 14wntQ8cBdnhUVfYmDjXz6PbpSSX8nCtkr 17.65221369 165336.99
de.tutao.tutanota 3MDrR5gaMvL8sphuQLX6BvPPKYNArdXsv6 10.30485934 96519.02
net.osmand.plus 1GRgEnKujorJJ9VBa76g8cp3sfoWtQqSs4 8.49212217 79540.27
me.tripsit.tripmobile 1EDqf32gw73tc1WtgdT2FymfmDN4RyC9RN 7.00970601 65655.43
player.efis.pfd 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.mfd 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.data.zar.aus 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.data.usa.can 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.data.sah.jap 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.data.pan.arg 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.data.eur.rus 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
player.efis.cfd 1KKWRF25NwVgNdankr1vBphtkLbX766Ee1 5.0014 46844.91
com.nutomic.zertman 1NUqm2kyaiRdssFaxYd7CQaWy4og19xH5g 5.0 46831.80
com.nutomic.ensichat 1DmU6QVGSKXGXJU1bqmmStPDNsNnYoMJB4 4.99995 46831.33
com.brentpanther.litecoinwidget 15SHnY7HC5bTxzErHDPe7wHXj1HhtDKV7z 4.29288259 40208.68
com.brentpanther.ethereumwidget 15SHnY7HC5bTxzErHDPe7wHXj1HhtDKV7z 4.29288259 40208.68
com.brentpanther.bitcoinwidget 15SHnY7HC5bTxzErHDPe7wHXj1HhtDKV7z 4.29288259 40208.68
com.brentpanther.bitcoincashwidget 15SHnY7HC5bTxzErHDPe7wHXj1HhtDKV7z 4.29288259 40208.68
im.vector.alpha 1LxowEgsquZ3UPZ68wHf8v2MDZw82dVmAE 3.65680571 34250.96
in.p1x.tanks_of_freedom 18oHovhxpevALZFcjH3mgNKB1yLi3nNFRY 3.59251169 33648.76
com.veken0m.bitcoinium 1yjDmiukhB2i1XyVw5t7hpAK4WXo32d54 3.49440553 32729.86
com.vuze.android.remote 15j7vKgJbixQFZ6AvEFw2BhtA4KG7E14JZ 2.52566983 23656.33
at.bitfire.nophonespam 1KSCy7RHztKuhW9fLLaUYqdwdC2iwbejZU 2.40361077 22513.08
at.bitfire.icsdroid 1KSCy7RHztKuhW9fLLaUYqdwdC2iwbejZU 2.40361077 22513.08
at.bitfire.gfxtablet 1KSCy7RHztKuhW9fLLaUYqdwdC2iwbejZU 2.40361077 22513.08
at.bitfire.davdroid 1KSCy7RHztKuhW9fLLaUYqdwdC2iwbejZU 2.40361077 22513.08
at.bitfire.cadroid 1KSCy7RHztKuhW9fLLaUYqdwdC2iwbejZU 2.40361077 22513.08
com.wireguard.android 1ASnTs4UjXKR8tHnLi9yG42n42hbFYV2um 2.36196229 22122.99
net.sourceforge.wifiremoteplay 1LKCFto9SQGqtcvqZxHkqDPqNjSnfMmsow 2.20225896 20627.15
net.sourceforge.opencamera 1LKCFto9SQGqtcvqZxHkqDPqNjSnfMmsow 2.20225896 20627.15
org.witness.sscphase1 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
org.torproject.android 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
org.havenapp.main 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.ripple 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.pixelknot 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.otr.app.im 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.orfox 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.notepadbot 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.locationprivacy 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.lildebi 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.gilga 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.courier 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.checkey 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.cacert 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
info.guardianproject.browser 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
at.or.at.plugoffairplane 1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk 2.00473917 18777.11
sk.baka.aedict 1KJyEutxrm3yL7chvsciMJTvXahXoWE3Pw 2.0 18732.72
byrne.utilities.pasteedroid 1L44pgmZpeMsWsd24WgN6SJjEUARG5eY6G 1.93771879 18149.37
byrne.utilities.hashpass 1L44pgmZpeMsWsd24WgN6SJjEUARG5eY6G 1.93771879 18149.37
byrne.utilities.converter 1L44pgmZpeMsWsd24WgN6SJjEUARG5eY6G 1.93771879 18149.37
com.zoffcc.applications.zanavi 1ZANav18WY8ytM7bhnAEBS3bdrTohsD9p 1.3792561 12918.61
eu.domob.shopt 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm 1.30931 12263.47
eu.domob.bjtrainer 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm 1.30931 12263.47
eu.domob.angulo 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm 1.30931 12263.47
eu.domob.anacam 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm 1.30931 12263.47
libretasks.app 193Xb3sySr2oEMuJC6bqAov444rSyVczW 1.24689782 11678.89
com.ymber.eleven 12aDckQC6YHEn75zReQWxXFCivBBNXfRjM 1.19375821 11181.17
si.modrajagoda.didi 1FU27EyocpFFhexjoakSe7Hxvf4jD2KmFh 1.05 9834.68
com.nononsenseapps.feeder 1PdmeeGxB2iktvmtkGqwUNmYq7L9tnxjwE 1.02972708 9644.79
org.projectmaxs.transport.xmpp bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.wifichange bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.wifiaccess bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.smswrite bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.smssend bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.smsread bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.smsnotify bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.shell bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.ringermode bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.phonestateread bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.notification bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.nfc bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.misc bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.locationfine bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.filewrite bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.fileread bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.contactsread bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.clipboard bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.bluetoothadmin bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.bluetooth bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.module.alarmset bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
org.projectmaxs.main bc1qu482c0tngkcvx3q7mrm8zmuldrh2f2lrh26ym0 0.9995 9361.68
com.eibriel.reddot 1MD8wCtnx5zqGvkY1VYPNqckAyTWDhXKzY 0.923361 8648.53
org.briarproject.briar.android 1NZCKkUCtJV2U2Y9hDb9uq8S7ksFCFGR6K 0.59356774 5559.57
eu.faircode.email 13nUbfsLUzK9Sr7ZJgDRHNR91BJMuDuJnf 0.51806696 4852.40
de.robv.android.xposed.installer 1uAEzZrfJt96UHYQheUUC8gSp2TJdwdw3 0.49531493 4639.30
org.kontalk 14vipppSvCG7VdvoYmbhKZ8DbTfv9U1QfS 0.48859802 4576.38
hashengineering.groestlcoin.wallet_test 3BCeMXVny1HbDc4NK64UZs9oFjKZdajBfx 0.48 4495.85
hashengineering.groestlcoin.wallet 3BCeMXVny1HbDc4NK64UZs9oFjKZdajBfx 0.48 4495.85
org.disrupted.rumble 1PXXMinxQgYUPXzZq6BixZpJTFeiCLqDqD 0.44804797 4196.58
se.manyver 3NNGfHL96UrjggaBVQojF1mnGnXNx1SXv7 0.44135235 4133.86
org.schabi.sharewithnewpipe 16A9J59ahMRqkLSZjhYj33n9j3fMztFxnh 0.40426632 3786.50
org.schabi.openhitboxstreams 16A9J59ahMRqkLSZjhYj33n9j3fMztFxnh 0.40426632 3786.50
org.schabi.newpipelegacy 16A9J59ahMRqkLSZjhYj33n9j3fMztFxnh 0.40426632 3786.50
org.schabi.newpipe 16A9J59ahMRqkLSZjhYj33n9j3fMztFxnh 0.40426632 3786.50
org.mariotaku.twidere 1FHAVAzge7cj1LfCTMfnLL49DgA3mVUCuW 0.33555159 3142.90
de.gabbo.forro_lyrics 1MDjHkXQud77UJk6TqmGkjeyhmz67NfE6g 0.32967373 3087.84
org.disroot.disrootapp 1GNmDSXxpU1zaxEopKCJK2TzLh3dbZAxEA 0.32853919 3077.22
com.dfa.hubzilla_android 1GNmDSXxpU1zaxEopKCJK2TzLh3dbZAxEA 0.32853919 3077.22
com.watabou.pixeldungeon 1LyLJAzxCfieivap1yK3iCpGoUmzAnjdyK 0.30544626 2860.92
ca.pr0ps.xposed.entrustunblocker 15jv7w1AdCMkNpDaAQrPtwK3Lfxx5ggAKX 0.2981067 2792.17
ca.cmetcalfe.xposed.flatconnectivityicons 15jv7w1AdCMkNpDaAQrPtwK3Lfxx5ggAKX 0.2981067 2792.17
ca.cmetcalfe.xposed.disablebatterywarnings 15jv7w1AdCMkNpDaAQrPtwK3Lfxx5ggAKX 0.2981067 2792.17
ca.cmetcalfe.locationshare 15jv7w1AdCMkNpDaAQrPtwK3Lfxx5ggAKX 0.2981067 2792.17
eu.faircode.netguard 13vtPytVVqCwojmohAqsK61Tk4yGXSWpJK 0.28845628 2701.79
org.totschnig.myexpenses 1GCUGCSfFXzSC81ogHu12KxfUn3cShekMn 0.26904759 2520.00
com.termux.window 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux.widget 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux.tasker 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux.styling 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux.boot 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux.api 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
com.termux 1BXS5qPhJzhr5iK5nmNDSmoLDfB6VmN5hv 0.2645677 2478.04
se.leap.riseupvpn 1F3KowUJBfvocr1H6DRvwFxfETJ18e8Dp6 0.25404247 2379.45
eu.siacs.conversations.voicerecorder 1AeqNAcg85APAZj9BZfAjdFCC5zesqXp2B 0.25226604 2362.81
eu.siacs.conversations.legacy 1AeqNAcg85APAZj9BZfAjdFCC5zesqXp2B 0.25226604 2362.81
com.morphoss.acal 1C7ChLNbwiQNWS6BLCPNU5TzX3ve7Xup2m 0.24548194 2299.27
com.b44t.messenger 18e3zwis2raitdZVhEhHHT7xG6oXsZte9L 0.24530249 2297.59
com.achep.acdisplay 1GYj49ZnMByKj2f6p7r4f92GQi5pR6BSMz 0.23828669 2231.88
net.alegen.android.netclip 1862EpKxs4BGUM6Td2Gs83QCkVC889Eqja 0.23149008 2168.22
com.simplemobiletools.voicerecorder 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.thankyou 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.smsmessenger 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.notes.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.notes 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.musicplayer 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.gallery.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.gallery 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.flashlight 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.filemanager.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.filemanager 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.draw.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.draw 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.dialer 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.contacts.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.contacts 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.clock 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.camera 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.calendar.pro 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.calendar 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.calculator 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
com.simplemobiletools.applauncher 19Hc8A7sWGud8sP19VXDC5a5j28UyJfpyJ 0.20711972 1939.96
cx.hell.android.pdfviewpro 1MLdh6uAPymWVJ4bmRde684uTcLJWwumkK 0.20361036 1907.09
cx.hell.android.pdfview 1MLdh6uAPymWVJ4bmRde684uTcLJWwumkK 0.20361036 1907.09
de.grobox.liberario 12JaQp8zfqRb83JfSwVjH4rZWsZnWRPoyG 0.18405547 1723.93
de.grobox.blitzmail 12JaQp8zfqRb83JfSwVjH4rZWsZnWRPoyG 0.18405547 1723.93
com.todobom.opennotescanner 1H5tqKZoWdqkR54PGe9w67EzBnLXHBFmt9 0.16962324 1588.75
org.libreoffice.impressremote 129jj3HiLfj3zCfqoro3sMTdovizXEdo8A 0.16380002 1534.21
org.eu.exodus_privacy.exodusprivacy 1exodusdyqXD81tS8SkcLhyFj9ioxWsaZ 0.15745937 1474.82
org.openintents.shopping 16MJeiftw9LRuvqoSH18v16kYTeNx7wJSZ 0.1507208 1411.71
org.openintents.safe 16MJeiftw9LRuvqoSH18v16kYTeNx7wJSZ 0.1507208 1411.71
org.openintents.notepad 16MJeiftw9LRuvqoSH18v16kYTeNx7wJSZ 0.1507208 1411.71
org.openintents.flashlight 16MJeiftw9LRuvqoSH18v16kYTeNx7wJSZ 0.1507208 1411.71
org.openintents.filemanager 16MJeiftw9LRuvqoSH18v16kYTeNx7wJSZ 0.1507208 1411.71
de.smasi.tickmate 18tub3juj26zyGwdpmGDLgtLEpfFf2Nvhu 0.14452004 1353.63
me.hda.urlhda 1N5czHaoSLukFSTq2ZJujaWGjkmBxv2dT9 0.142 1330.02
com.passcard 1N5czHaoSLukFSTq2ZJujaWGjkmBxv2dT9 0.142 1330.02
org.blokada.alarm 16rJ49uNKCohVhHvWNganP6Y48Ba9BTyKd 0.14151834 1325.51
org.floens.chan 1N7VtcNh8L8u4tF9CJ38GjnPbmxM4Vixi6 0.13177915 1234.29
press.condense.www 325oe18pc8npqHeBGozobnvWfXXe3pujXq 0.12791726 1198.12
org.quantumbadger.redreader 1874wapGxDo2vEp4avisda4gx3SCjsHCQJ 0.12570044 1177.36
wb.receiptspro 3MGikseSB69cGjUkJs4Cqg93s5s8tv38tK 0.12023971 1126.21
be.brunoparmentier.wifikeyshare 168utA5DWMVXLFVfQDahG5abEWUSk9Wcfm 0.11048893 1034.88
be.brunoparmentier.openbikesharing.app 168utA5DWMVXLFVfQDahG5abEWUSk9Wcfm 0.11048893 1034.88
be.brunoparmentier.dnssetter 168utA5DWMVXLFVfQDahG5abEWUSk9Wcfm 0.11048893 1034.88
be.brunoparmentier.apkshare 168utA5DWMVXLFVfQDahG5abEWUSk9Wcfm 0.11048893 1034.88
org.smssecure.smssecure 1LoKZXg3bx6kfwAhEFQqS9pgeCE1CFMEJb 0.10927359 1023.50
mobi.boilr.boilr 1PHuSWfuAwR6oz9qV93rTdMVozfM85Qqxx 0.101 946.00
com.morlunk.mountie 1ySD4UzFDtPLq9agRg9eiFtWmz6DJ7bBf 0.09228972 864.42
org.lf_net.pgpunlocker 18ii4wvKxPFvKoGk7MXLngq9yWNsp7ABPd 0.08827862 826.85
com.orpheusdroid.sqliteviewer 1Cbf61y8XNx3BLWvoZB71x4XgBKB7r8BuB 0.07990648 748.43
com.orpheusdroid.screenrecorder 1Cbf61y8XNx3BLWvoZB71x4XgBKB7r8BuB 0.07990648 748.43
com.biglybt.android.client 1BiGLYBT38ttJhvZkjGc5mCw5uKoRHcUmr 0.06538094 612.38
net.gsantner.markor 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
net.gsantner.dandelior 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
io.github.gsantner.memetastic 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
io.github.froodyapp 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
de.live.gdev.timetracker 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
de.live.gdev.cherrymusic 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
com.github.dfa.diaspora_android 1B9ZyYdQoY9BxMe9dRUEKaZbJWsbQqfXU5 0.06195393 580.28
org.woltage.irssiconnectbot 12Xe9L8Kam2F838RipTstT1BAxWLZjWRxh 0.05900001 552.62
dev.ukanth.ufirewall 1LBUdALwYXDv38wvnUSGvsFjituaWAHvFo 0.05663316 530.45
org.totschnig.sendwithftp 1Dmj6keLGgNHBUD5unsbZz5vnk9wRinRAy 0.05247253 491.48
com.github.yeriomin.yalpstore 14HvYHKe6joHbQjVdAPd1Ha1yXaGS2pVTW 0.05018261 470.03
com.github.yeriomin.smsscheduler 14HvYHKe6joHbQjVdAPd1Ha1yXaGS2pVTW 0.05018261 470.03
com.github.yeriomin.dumbphoneassistant 14HvYHKe6joHbQjVdAPd1Ha1yXaGS2pVTW 0.05018261 470.03
org.ethack.orwall 1Kriu9owRhEsFkj8Lc6Wr5xTv8YTNphhXn 0.04385552 410.77
org.indywidualni.fblite 1JUaZytkub2CP5jhRYQDDY6pibqrUUSp2y 0.04214968 394.79
com.anthony.deepl.openl 3DetrDfft3ChjXMQUsTwQL1ozQvBXwGSsQ 0.04 374.65
org.jamienicol.episodes 149XkMSs84ZyzNMqiQeJLt5DbPru16amwA 0.033 309.09
io.github.powerinside.syncplay 16E1hn96zg9h16VCrxSG6p7b72vyNh64ft 0.03048045 285.49
io.github.powerinside.scrollsocket 16E1hn96zg9h16VCrxSG6p7b72vyNh64ft 0.03048045 285.49
nya.miku.wishmaster 1LaumSD5Y9npHxsq9Cqo3esmWiytqv95QW 0.03 280.99
am.ed.importcontacts 14FPuKQfmV31Fx4uxwXvehmM189nxaQpKB 0.02695857 252.50
am.ed.exportcontacts 14FPuKQfmV31Fx4uxwXvehmM189nxaQpKB 0.02695857 252.50
org.tasks 136mW34jW3cmZKhxuTDn3tHXMRwbbaRU8s 0.02141326 200.56
com.moonpi.tapunlock 1NZGAU1rEs1zBpwdjmnBjiyRsJHfycWhSF 0.02106 197.26
com.moonpi.swiftnotes 1NZGAU1rEs1zBpwdjmnBjiyRsJHfycWhSF 0.02106 197.26
org.telegram.messenger 1McafEgMvqAVujNLtcJumZHxp2UfaNByqs 0.02006732 187.96
eu.faircode.xlua 1GePXhRPgLhwQmBwRHhX1nSCgvfnCY97Gg 0.01687755 158.08
org.decsync.sparss.floss 1JWYoV2MZyu8LYYHCur9jUJgGqE98m566z 0.01598957 149.76
org.decsync.cc 1JWYoV2MZyu8LYYHCur9jUJgGqE98m566z 0.01598957 149.76
org.asdtm.goodweather 1FV8m1MKqZ9ZKB8YNwpsjsuubHTznJSiT8 0.01510861 141.51
org.asdtm.fas 1FV8m1MKqZ9ZKB8YNwpsjsuubHTznJSiT8 0.01510861 141.51
com.nma.util.sdcardtrac 16bxTv1fP8X2QN5SWXc1AcKhhA1tJQKcTa 0.015 140.50
com.kunzisoft.keyboard.switcher 1DSwXCk7Sob24sNsofywNoRQw2f5Qj5t2F 0.01473243 137.99
com.kunzisoft.keepass.libre 1DSwXCk7Sob24sNsofywNoRQw2f5Qj5t2F 0.01473243 137.99
fr.kwiatkowski.ApkTrack 19wFVDUWhrjRe3rPCsokhcf1w9Stj3Sr6K 0.01440284 134.90
com.stripe1.xmouse 17DaqbcEEG3Hn5jBv3sRjPTUUCW1eBp1Wg 0.01358135 127.21
org.nutritionfacts.dailydozen 3GQUrb9sw36MoQeZNJ4g16CCNqgr3Va6bx 0.0118 110.52
com.stoutner.privacybrowser.standard 1Jiooc5L238VnhiWtkdYEkwm7kRNWQspSC 0.01159484 108.60
org.sufficientlysecure.termbot 1LY6Hs6SurATjfxnihzLMDUMUuMxvQ4aEi 0.01151042 107.81
org.sufficientlysecure.keychain 1LY6Hs6SurATjfxnihzLMDUMUuMxvQ4aEi 0.01151042 107.81
com.zeapo.pwdstore 1H1Z1NPTrR5Cej9bKV3Hu4f5WJZYtkbpox 0.01141762 106.94
pk.contender.earmouse 1FdwmPaKhE6pmPRxNHcWh3yFDo3mdtMPy 0.01041024 97.51
im.quicksy.client 3KAD8vew6tPZDjiUJNnZ3YUoUxrCEVNwFL 0.01024848 95.99
eu.siacs.conversations 3KAD8vew6tPZDjiUJNnZ3YUoUxrCEVNwFL 0.01024848 95.99
org.hoi_polloi.android.ringcode 18FLvxn8Vgz5DTgVH1kT4DRJoaANpWhqvP 0.01 93.66
at.linuxtage.companion 1GLTBBirbj8GZ8uY1gwovZ1QEMjfWu3rWT 0.01 93.66
com.jarsilio.android.waveup 16DXeCxxKGvepYLehyHSr3M1nv1s1eUotZ 0.00789495 73.95
com.jarsilio.android.scrambledeggsif 16DXeCxxKGvepYLehyHSr3M1nv1s1eUotZ 0.00789495 73.95
com.jarsilio.android.pocketup 16DXeCxxKGvepYLehyHSr3M1nv1s1eUotZ 0.00789495 73.95
com.jarsilio.android.drowser 16DXeCxxKGvepYLehyHSr3M1nv1s1eUotZ 0.00789495 73.95
se.leap.bitmaskclient 1Fze6GLjoxFnwAGNreYLK8ktFdGJdPRxeY 0.00763591 71.52
com.saha.batchuninstaller 3GRYNKRUFsefuvKuTycgbMjB4DFxUXVys4 0.007 65.56
org.sufficientlysecure.viewer.fontpack 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.sufficientlysecure.viewer 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.sufficientlysecure.standalonecalendar 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.sufficientlysecure.localcalendar 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.sufficientlysecure.ical 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.shortcuts 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.ntpsync 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.fastergps 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
org.birthdayadapter 12Y6zbBYoRxf8kBrjau3WedjtzvcACvPMk 0.00666289 62.41
com.moez.QKSMS 3ELLdraJTuJB2CtQACZiAuf1X3udeAsRgP 0.00403494 37.79
org.xposeddownloader 16VEzu37BePgR3o9hAciZkGK2VCAQFE28r 0.0035 32.78
org.opengappsdownloader 16VEzu37BePgR3o9hAciZkGK2VCAQFE28r 0.0035 32.78
org.basketbuilddownloader 16VEzu37BePgR3o9hAciZkGK2VCAQFE28r 0.0035 32.78
org.afhdownloader 16VEzu37BePgR3o9hAciZkGK2VCAQFE28r 0.0035 32.78
com.gianlu.aria2app 18rrPNGgz8UkzUYgAnqVye83xEe5fB7XfY 0.00330638 30.97
com.gianlu.aria2android 18rrPNGgz8UkzUYgAnqVye83xEe5fB7XfY 0.00330638 30.97
com.oriondev.moneywallet 1J3APoaFT2jcqRzpb8bEt2rwUn3mDpWE5U 0.00290149 27.18
com.omegavesko.holocounter 19J43UNjckM9Q2M59ZM8ptCW5kA1dWdHdp 0.00277121 25.96
ir.hsn6.turo 1PUJ5sFWxvbx5Np2CjFmhHFnzPe2GPvinj 0.00271154 25.40
com.fr3ts0n.stagefever 19UApzsc5eDJ5VNDNYCA1bpszPnkcpWeFP 0.00235526 22.06
com.fr3ts0n.ecu.gui.androbd 19UApzsc5eDJ5VNDNYCA1bpszPnkcpWeFP 0.00235526 22.06
com.fr3ts0n.androbd.plugin.sensorprovider 19UApzsc5eDJ5VNDNYCA1bpszPnkcpWeFP 0.00235526 22.06
com.fr3ts0n.androbd.plugin.mqtt 19UApzsc5eDJ5VNDNYCA1bpszPnkcpWeFP 0.00235526 22.06
com.fr3ts0n.androbd.plugin.gpsprovider 19UApzsc5eDJ5VNDNYCA1bpszPnkcpWeFP 0.00235526 22.06
de.tadris.fitness 3BSbGRbJaiSxVg3D6nVRK5C1SZEezhjtK5 0.00214369 20.08
eu.uwot.fabio.altcoinprices 353x3kNMUaAt3i79kQTf3KCJWRAVXSRGpW 0.00213 19.95
ch.bailu.aat 3GK4KLiqKqGg5UQxdkkGXhhDZkdFFicy5T 0.002 18.73
org.elijaxapps.androidxmrigminer 37GpugVZNiof2DzWQX5aivHewc4wZLxATL 0.00189005 17.70
io.oversec.one 16tan5fBNJ6n1QmVxwvvondyvuwgx1W6fE 0.00177442 16.62
com.goltzkiste.guessaday 1Guessas8CtCA9S9ZA9p9fCFAD3VZTE9ey 0.00176227 16.51
net.khertan.forrunners 1s38rpyuJvfvcRFaESZmVSp6EYpVLEDWU 0.00134051 12.56
de.schildbach.oeffi bc1qxm9r8n3pe47r30e04gs2xsalxef55zrfvelvln 0.0012577 11.78
org.gdroid.gdroid 1J2bbhJYksSjeynGGhuSPN9aTEaxiGm4nR 0.001 9.37
com.gitlab.ardash.appleflinger.android 1J2bbhJYksSjeynGGhuSPN9aTEaxiGm4nR 0.001 9.37
org.zamedev.gloomydungeons2.opensource 1BkmsNEeW5A2YketBaa4pDFSAcDwnDuyDp 0.00099 9.27
net.fabiszewski.ulogger bc1qt3uwhze9x8tj6v73c587gprhufg9uur0rzxhvh 0.00097941 9.17
ir.hsn6.trans 1MkJyXh8y3ViXTAFhKUpXfgfECEfnZmLGY 0.00080184 7.51
net.frju.flym 3DprwFMg5bXGz8QimyiaoEE7mmCkj2DGf5 0.00068 6.37
com.zeusln.zeus 3Lbz4vdt15Fsa4wVD3Yk8uGf6ugKKY4zSc 0.0006 5.62
de.schildbach.wallet bc1qedxd9jssgw2fferdmjyyh6fm8jax75q7drfnd4 0.00059521 5.57
com.zoffcc.applications.trifa 1TRifA7eNLHZEcCTj43eYVWHBbLqTuXkS 0.00028782 2.70
com.notecryptpro 1MHEbHt4sBeqGoriwAq1MsXZaZJinoUeLH 0.00027552 2.58
ir.hsn6.defendo 16D7Nroenpx4QDNqfq3Js7sdAVhew2NzGp 0.00018749 1.76
org.proninyaroslav.libretorrent 1Af9DgxtWvVp6bFiYQw2MeWtRzTXshRYpB 0.0001747 1.64
me.shrimadhavuk.numselapp 13csS5SByVR4e3tJ9c4gjC18Lua8dXDp9A 0.00010397 0.97
com.wesaphzt.privatelock 1GCkvAg9oG79niQTbh6EH9rPALQDXKyHKK 5.773e-05 0.54
com.wesaphzt.privatelocation 1GCkvAg9oG79niQTbh6EH9rPALQDXKyHKK 5.773e-05 0.54
ru.glesik.nostrangersms 1DbZjPqe4uaBv32deNqwbWUTrCempo2Wqk 5e-05 0.47
ru.ttyh.neko259.notey 1Lh7a1tx7EREENawQyHhiKoCRF6u6TzVrD 0.0 0.00
re.jcg.playmusicexporter 1NdzpDWPQ53xWT5fraGPZX5F9XrKiPBXjp 0.0 0.00
pl.sanszo.pcis 1PbH84rewi34Ffgr3C5NutMdvEzSQ13wUt 0.0 0.00
pl.net.szafraniec.NFCTagmaker 17E32x5ygXkqf5EWJkryZuarUDUFrb8UqQ 0.0 0.00
pl.net.szafraniec.NFCKey 17E32x5ygXkqf5EWJkryZuarUDUFrb8UqQ 0.0 0.00
org.valos.isolmoa 1LbgYALbkQ2Trgh4yXqdBnbdQosGard5hd 0.0 0.00
org.thecongers.mtpms 1Pg54vVnaLxNsziA6cy9CTefoEG5iAm9Uh 0.0 0.00
org.pacien.tincapp 152t9TEBBhEescQx5gG7T5wHaJVeupAXQm 0.0 0.00
org.opengemara.shiurim 19p5TXDfMksHjUstFEp2PUt383Cy7JdmLa 0.0 0.00
org.nuntius35.wrongpinshutdown 1LSs1BR4ktQcW8DrCjrSrWUvBD6h2rqNJm 0.0 0.00
org.nick.wwwjdic 1DXhWFS9SL78GGyX7Luao9EuP5SxtDiPG1 0.0 0.00
org.miamplayer.autoairplanemode 39RBokXr4V9FPpuF7v1bM6PYcbgRRApp9W 0.0 0.00
org.mbach.lemonde 39RBokXr4V9FPpuF7v1bM6PYcbgRRApp9W 0.0 0.00
org.kost.nmap.android.networkmapper 1588ArbHPcb5VtpZPQgue9iPZ9LiA1eEjF 0.0 0.00
org.kost.externalip 1KbtLnxp6mhkGznFNZZQdcaCUQHmrTtLm4 0.0 0.00
org.kaqui 12bnT7epKmf9ztkAeuM8dHCcoc76r9rgVX 0.0 0.00
org.emunix.unipatcher 16coztryz7xbNNDNhhf98wuHmi3hEintsW 0.0 0.00
org.emunix.insteadlauncher 16coztryz7xbNNDNhhf98wuHmi3hEintsW 0.0 0.00
org.chickenhook.startflagexploit bc1qvll2mp5ndwd4sgycu4ad2ken4clhjac7mdlcaj 0.0 0.00
org.androidpn.client 13MjTPDFQtxv1u1sWURkDduFSw97KbMfsS 0.0 0.00
org.amoradi.syncopoli 1DT8ijBkGUAvW9VZqfCQBJFS62vvw5E7QK 0.0 0.00
net.schueller.peertube 1LoTXo728HzYTtyfbkaf5ewSRvu8ABTDPm 0.0 0.00
net.mabako.steamgifts 1NQBKppWPZiE5PshLxqfFW4pgsnAv9irEu 0.0 0.00
name.gdr.acastus_photon 1NjjuTxXm3ezpnVUGk4VmdEZUcym3SKZ8z 0.0 0.00
me.dbarnett.acastus 1NjjuTxXm3ezpnVUGk4VmdEZUcym3SKZ8z 0.0 0.00
me.danielbarnett.addresstogps 1NjjuTxXm3ezpnVUGk4VmdEZUcym3SKZ8z 0.0 0.00
it.reyboz.screenlock 16oHee3jeENnN6fPxFq6LpNP6SZG9rimRD 0.0 0.00
it.reyboz.minesweeper 16oHee3jeENnN6fPxFq6LpNP6SZG9rimRD 0.0 0.00
it.reyboz.chordshift 16oHee3jeENnN6fPxFq6LpNP6SZG9rimRD 0.0 0.00
it.reyboz.bustorino 16oHee3jeENnN6fPxFq6LpNP6SZG9rimRD 0.0 0.00
it.andreascarpino.hostisdown 1Ph3hFEoQaD4PK6MhL3kBNNh9FZFBfisEH 0.0 0.00
is.zi.huewidgets 1FdGg777eP4cqMrJVMRQiMXEHE2Ee6F62T 0.0 0.00
ir.hsn6.tpb 12SL5VgtjozKTXMgpX7w4MjKvvcFAHbTks 0.0 0.00
ir.hsn6.k2 1iNMJMFqDgYp7iUMd4qkP79CiCLSwLPyp 0.0 0.00
io.github.tjg1.nori 1NHUsSzj3N7TE8rykUYk8rqqLWWSmTVzdp 0.0 0.00
in.shick.lockpatterngenerator 1JscvZEbchRUpCXYX13bJb3aF6U1yT9BwG 0.0 0.00
ga.testapp.testapp 3NUiJXDCkyRTb9Tg7n63yK6Y7CexADtSEh 0.0 0.00
fr.renzo.wikipoff 1BAaxTvK1jkoFKf7qWF2C6M4UX1y86MxaF 0.0 0.00
fr.cph.chicago.foss 13WUmCX1AePEKFGv5U1qRgBockFahsm21o 0.0 0.00
fr.corenting.traficparis 3JmaEkuviReVdCG8fjqCs5LwQkaEGcTMtZ 0.0 0.00
eth.matteljay.mastermindy 14VZcizduTvUTesw4T9yAHZ7GjDDmXZmVs 0.0 0.00
design.codeux.authpass.fdroid 3NcBacCmJbYWpwxj6rWzpM7sx48etMrPtc 0.0 0.00
de.yaacc 1MUvbfNgunNCUtitCkoEEMgmQGZJJg4isj 0.0 0.00
de.vanitasvitae.enigmandroid 1EqhcKs1pZJhEmyCtbH3qtkHT3Y48MCoAT 0.0 0.00
de.schildbach.wallet_test bc1qglkj2svuu3xsktup5xla8u2wjzlu8mfzk6509r 0.0 0.00
de.naturalnet.zahnarztgeraeusche 1EAytSwn1u7tKTZ9sMDVCzDqe2nwVf4Pra 0.0 0.00
de.naturalnet.mirwtfapp 1EAytSwn1u7tKTZ9sMDVCzDqe2nwVf4Pra 0.0 0.00
de.k4ever.k4android 1KiwFPGCunGXF53DBTBf32cNTPXq9FbX5H 0.0 0.00
de.jkliemann.parkendd 1HBFDdz7dJeBE2c3zQmWnzeWCbHoZQ64dd 0.0 0.00
de.Cherubin7th.blackscreenpresentationremote 18QSJmV6Liia7Cau65JnEj2JyxEUCGE2oz 0.0 0.00
com.tritop.androsense2 1Dj4Xkz5KtsarmioEKuuZCBVjahr14dih4 0.0 0.00
com.toxtox.philosopherstonewidget 1KvYjRx1VozqUpiYSCMrEL6mo9LvmpCcNN 0.0 0.00
com.sanskritbasics.memory bc1q3xasvfn2c84dprkk2mxj5g7n6ujwylphu8qsf3 0.0 0.00
com.rockbyte.arxiv 1jokQaTneW1KCbCWsMdVtvPv6oSJ1H3tF 0.0 0.00
com.rigid.birthdroid 1BLEeqwXnJJbpaLHiskZ5WyJJRyEWqCAQZ 0.0 0.00
com.readrops.app bc1qlkzlcsvvtn3y6mek5umv5tc4ln09l64x6y42hr 0.0 0.00
com.onetwofivegames.kungfoobarracuda 1MVNsgRmLqgMoEoQu918ozFFiTaepF8Ti5 0.0 0.00
com.mdroid 18BqyV9mNbFLi5HNNnfUprnPJyJDFP59Xh 0.0 0.00
com.mareksebera.simpledilbert 1FpGN3kcZ3GQsaJgBa8rxGRJjBjJavu78g 0.0 0.00
com.marceljurtz.lifecounter 1HDdKd3uoxdvS8pBKKKxEkjoJqUuBiEjkL 0.0 0.00
com.llamacorp.equate 15KCzAPJvSJLUfjuTQgAgSiSwQu6uLiexC 0.0 0.00
com.kn.paper_foss_theme 1CYiRF6AncdNkxcWTRFf5Mxi7UaFhC3jFG 0.0 0.00
com.ideasfrombrain.search_based_launcher_v2 1NapZs8brWNifGk7QFemqTByczdBAAg9cA 0.0 0.00
com.gmail.anubhavdas54.whatsdeleted bc1qs50wst8x53ud5lr80wukhjcy6l7zpxf5mz5rtm 0.0 0.00
com.github.igrmk.smsq 32JdGEVP42WiVxsADa3Z65qn1xe2K7Yg3S 0.0 0.00
com.genonbeta.TrebleShot 1DBsq8aZjn54hnDYsRY7pTLb3HfsE1mSv8 0.0 0.00
com.example.root.analyticaltranslator 15WVb3LZWCsdZGjkNFBuELwt3U4zpnSgwa 0.0 0.00
com.emmanuelmess.simpleaccounting 1HFhPxH9bqMKvs44nHqXjEEPC2m7z1V8tW 0.0 0.00
com.easwareapps.marbleone_ad_free 1PNwD199whFao1rjMX82Zi5A7M5B6KB7be 0.0 0.00
com.easwareapps.g2l 1PNwD199whFao1rjMX82Zi5A7M5B6KB7be 0.0 0.00
com.easwareapps.f2lflap2lock_adfree 1PNwD199whFao1rjMX82Zi5A7M5B6KB7be 0.0 0.00
com.danhasting.radar 1EwgjPGYiChJ5vyBndt9ugzd963FiVc6gj 0.0 0.00
com.atop 15G2T13emQnJRMvA74Zr6Q71bBcaYBn71v 0.0 0.00
com.aptasystems.dicewarepasswordgenerator 1PbHGv88KH6SXw6d66uSFTUzW2aeqxvQ7V 0.0 0.00
com.andreasgift.totalzero 1Q9TinY9kWoNMWuiToHiGC9uxCk6Vd41Gb 0.0 0.00
com.anddevw.getchromium 188RxvRnSXSZZnjuDdLwNirHDfNusVPobh 0.0 0.00
at.tacticaldevc.panictrigger 1EVr5tm2kugffNy3RWPGFoug6X9v3GTxuJ 0.0 0.00
im.vector.riotx 1LxowEgsquZ3UPZ68wHf8v2MDZw82dVmAEa -1.0 -9366.36
im.vector.app 1LxowEgsquZ3UPZ68wHf8v2MDZw82dVmAEa -1.0 -9366.36
I know this is flawed, I found it interesting nonetheless
The post which inspired this: https://www.reddit.com/fossdroid/comments/hyral2/are_there_fossdroid_apps_that_are_making_money/
submitted by prcrst to fossdroid [link] [comments]

DIY Bitcoin Paper Wallet Tutorial - free wallet - YouTube Paper Wallet für Bitcoin & Co: Darauf müsst Ihr achten! How To Open a Bitcoin Wallet How to use Blockchain Wallet API v2 Ultimate Guide To Paper Wallets(Storing Cryptocurrency ...

A Bitcoin Cash (BCH) wallet is as simple as a single pairing of a Bitcoin Cash (BCH) address with its corresponding Bitcoin Cash (BCH) private key. Such a wallet has been generated for you in your web browser and is displayed above. To safeguard this wallet you must print or otherwise record the Bitcoin Cash (BCH) address and private key. It is important to make a backup copy of the private ... Step 2. Print the Paper Wallet. Click the Paper Wallet tab and print the page on high quality setting. Never save the page as a PDF file to print it later since a file is more likely to be hacked than a piece of paper. Step 3. Fold the Paper Wallet. Fold your new Paper wallet following the lines. You can insert one side inside the other to lock ... bitcoin-wallet-api.github.io. Hunter. Jack Smith. Previously co-founded Vungle & Shyp. Makers. No Makers. Ally.io. OKR goal-planning and execution management software. Promoted. Related Products . prooV 2.0 Run PoCs with global enterprises, quickly and easily. Wallet List Shareable list of your public cryptocurrency wallets. BRD 3.0 for iPhone The simple way to purchase and protect your ... The Root Key is all you need to access the bitcoin in all addresses of the wallet, except any imported addresses. Be sure that you have a paper copy of the Root Key - KEEP IT SAFE!. Armory Root Key -> Addresses and Private Keys. The Armory wallet Root Key is the one stored on your paper backup [ OFFLINE PC ] Bitcoin Paper wallets are ways to store your BTC holdings safely and that too for a longer-term if you meticulously keep your private key discreet. You just have to print out your own tamper-resistant bitcoin wallets and by generating your own address, you can be sure to keep hackers at bay. You don’t need the internet to access your paper wallets which is why it comes under the cold wallet ...

[index] [7339] [321] [15439] [28521] [24427] [2457] [32824] [39602] [25843] [30385]

DIY Bitcoin Paper Wallet Tutorial - free wallet - YouTube

Paper Wallets eignen sich sehr gut, um Coins langfristig sicher aufzubewahren. In diesem Video zeigen wir, wie die Erstellung eines Bitcoin und Litecoin Paper Wallets funktioniert und welche ... Learn how to open a Bitcoin Wallet Blockchain wallet, Xapo Wallet, Coinbase Wallet, bitcoin wallet, best bitcoin wallet, bitcoin wallets, bitcoin paper walle... Welcome back! In a market that is highly susceptible to hacks, storage is one of the most important aspects to keeping your profits safe. This video will exp... SUBSCRIBE FOR MORE HOW MUCH - http://shorturl.at/arBHL Did you know? You can make Bitcoin Paper Wallets even if you don't own any bitcoins! Here is a list of... This quick Video Tutorial explains how to make a Dr. Evil Paper Wallet or Bitcoin Brain Wallet. Get the ZIP file for BitAddress.org @GitHub https://github.co...

#