US Marshals accidentally leak potential Bitcoin bidders list

Why Osana takes so long? (Programmer's point of view on current situation)

I decided to write a comment about «Why Osana takes so long?» somewhere and what can be done to shorten this time. It turned into a long essay. Here's TL;DR of it:
The cost of never paying down this technical debt is clear; eventually the cost to deliver functionality will become so slow that it is easy for a well-designed competitive software product to overtake the badly-designed software in terms of features. In my experience, badly designed software can also lead to a more stressed engineering workforce, in turn leading higher staff churn (which in turn affects costs and productivity when delivering features). Additionally, due to the complexity in a given codebase, the ability to accurately estimate work will also disappear.
Junade Ali, Mastering PHP Design Patterns (2016)
Longer version: I am not sure if people here wanted an explanation from a real developer who works with C and with relatively large projects, but I am going to do it nonetheless. I am not much interested in Yandere Simulator nor in this genre in general, but this particular development has a lot to learn from for any fellow programmers and software engineers to ensure that they'll never end up in Alex's situation, especially considering that he is definitely not the first one to got himself knee-deep in the development hell (do you remember Star Citizen?) and he is definitely not the last one.
On the one hand, people see that Alex works incredibly slowly, equivalent of, like, one hour per day, comparing it with, say, Papers, Please, the game that was developed in nine months from start to finish by one guy. On the other hand, Alex himself most likely thinks that he works until complete exhaustion each day. In fact, I highly suspect that both those sentences are correct! Because of the mistakes made during early development stages, which are highly unlikely to be fixed due to the pressure put on the developer right now and due to his overall approach to coding, cost to add any relatively large feature (e.g. Osana) can be pretty much comparable to the cost of creating a fan game from start to finish. Trust me, I've seen his leaked source code (don't tell anybody about that) and I know what I am talking about. The largest problem in Yandere Simulator right now is its super slow development. So, without further ado, let's talk about how «implementing the low hanging fruit» crippled the development and, more importantly, what would have been an ideal course of action from my point of view to get out. I'll try to explain things in the easiest terms possible.
  1. else if's and lack any sort of refactoring in general
The most «memey» one. I won't talk about the performance though (switch statement is not better in terms of performance, it is a myth. If compiler detects some code that can be turned into a jump table, for example, it will do it, no matter if it is a chain of if's or a switch statement. Compilers nowadays are way smarter than one might think). Just take a look here. I know that it's his older JavaScript code, but, believe it or not, this piece is still present in C# version relatively untouched.
I refactored this code for you using C language (mixed with C++ since there's no this pointer in pure C). Take a note that else if's are still there, else if's are not the problem by itself.
The refactored code is just objectively better for one simple reason: it is shorter, while not being obscure, and now it should be able to handle, say, Trespassing and Blood case without any input from the developer due to the usage of flags. Basically, the shorter your code, the more you can see on screen without spreading your attention too much. As a rule of thumb, the less lines there are, the easier it is for you to work with the code. Just don't overkill that, unless you are going to participate in International Obfuscated C Code Contest. Let me reiterate:
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
Antoine de Saint-Exupéry
This is why refactoring — activity of rewriting your old code so it does the same thing, but does it quicker, in a more generic way, in less lines or simpler — is so powerful. In my experience, you can only keep one module/class/whatever in your brain if it does not exceed ~1000 lines, maybe ~1500. Splitting 17000-line-long class into smaller classes probably won't improve performance at all, but it will make working with parts of this class way easier.
Is it too late now to start refactoring? Of course NO: better late than never.
  1. Comments
If you think that you wrote this code, so you'll always easily remember it, I have some bad news for you: you won't. In my experience, one week and that's it. That's why comments are so crucial. It is not necessary to put a ton of comments everywhere, but just a general idea will help you out in the future. Even if you think that It Just Works™ and you'll never ever need to fix it. Time spent to write and debug one line of code almost always exceeds time to write one comment in large-scale projects. Moreover, the best code is the code that is self-evident. In the example above, what the hell does (float) 6 mean? Why not wrap it around into the constant with a good, self-descriptive name? Again, it won't affect performance, since C# compiler is smart enough to silently remove this constant from the real code and place its value into the method invocation directly. Such constants are here for you.
I rewrote my code above a little bit to illustrate this. With those comments, you don't have to remember your code at all, since its functionality is outlined in two tiny lines of comments above it. Moreover, even a person with zero knowledge in programming will figure out the purpose of this code. It took me less than half a minute to write those comments, but it'll probably save me quite a lot of time of figuring out «what was I thinking back then» one day.
Is it too late now to start adding comments? Again, of course NO. Don't be lazy and redirect all your typing from «debunk» page (which pretty much does the opposite of debunking, but who am I to judge you here?) into some useful comments.
  1. Unit testing
This is often neglected, but consider the following. You wrote some code, you ran your game, you saw a new bug. Was it introduced right now? Is it a problem in your older code which has shown up just because you have never actually used it until now? Where should you search for it? You have no idea, and you have one painful debugging session ahead. Just imagine how easier it would be if you've had some routines which automatically execute after each build and check that environment is still sane and nothing broke on a fundamental level. This is called unit testing, and yes, unit tests won't be able to catch all your bugs, but even getting 20% of bugs identified at the earlier stage is a huge boon to development speed.
Is it too late now to start adding unit tests? Kinda YES and NO at the same time. Unit testing works best if it covers the majority of project's code. On the other side, a journey of a thousand miles begins with a single step. If you decide to start refactoring your code, writing a unit test before refactoring will help you to prove to yourself that you have not broken anything without the need of running the game at all.
  1. Static code analysis
This is basically pretty self-explanatory. You set this thing once, you forget about it. Static code analyzer is another «free estate» to speed up the development process by finding tiny little errors, mostly silly typos (do you think that you are good enough in finding them? Well, good luck catching x << 4; in place of x <<= 4; buried deep in C code by eye!). Again, this is not a silver bullet, it is another tool which will help you out with debugging a little bit along with the debugger, unit tests and other things. You need every little bit of help here.
Is it too late now to hook up static code analyzer? Obviously NO.
  1. Code architecture
Say, you want to build Osana, but then you decided to implement some feature, e.g. Snap Mode. By doing this you have maybe made your game a little bit better, but what you have just essentially done is complicated your life, because now you should also write Osana code for Snap Mode. The way game architecture is done right now, easter eggs code is deeply interleaved with game logic, which leads to code «spaghettifying», which in turn slows down the addition of new features, because one has to consider how this feature would work alongside each and every old feature and easter egg. Even if it is just gazing over one line per easter egg, it adds up to the mess, slowly but surely.
A lot of people mention that developer should have been doing it in object-oritented way. However, there is no silver bullet in programming. It does not matter that much if you are doing it object-oriented way or usual procedural way; you can theoretically write, say, AI routines on functional (e.g. LISP)) or even logical language if you are brave enough (e.g. Prolog). You can even invent your own tiny programming language! The only thing that matters is code quality and avoiding the so-called shotgun surgery situation, which plagues Yandere Simulator from top to bottom right now. Is there a way of adding a new feature without interfering with your older code (e.g. by creating a child class which will encapsulate all the things you need, for example)? Go for it, this feature is basically «free» for you. Otherwise you'd better think twice before doing this, because you are going into the «technical debt» territory, borrowing your time from the future by saying «I'll maybe optimize it later» and «a thousand more lines probably won't slow me down in the future that much, right?». Technical debt will incur interest on its own that you'll have to pay. Basically, the entire situation around Osana right now is just a huge tale about how just «interest» incurred by technical debt can control the entire project, like the tail wiggling the dog.
I won't elaborate here further, since it'll take me an even larger post to fully describe what's wrong about Yandere Simulator's code architecture.
Is it too late to rebuild code architecture? Sadly, YES, although it should be possible to split Student class into descendants by using hooks for individual students. However, code architecture can be improved by a vast margin if you start removing easter eggs and features like Snap Mode that currently bloat Yandere Simulator. I know it is going to be painful, but it is the only way to improve code quality here and now. This will simplify the code, and this will make it easier for you to add the «real» features, like Osana or whatever you'd like to accomplish. If you'll ever want them back, you can track them down in Git history and re-implement them one by one, hopefully without performing the shotgun surgery this time.
  1. Loading times
Again, I won't be talking about the performance, since you can debug your game on 20 FPS as well as on 60 FPS, but this is a very different story. Yandere Simulator is huge. Once you fixed a bug, you want to test it, right? And your workflow right now probably looks like this:
  1. Fix the code (unavoidable time loss)
  2. Rebuild the project (can take a loooong time)
  3. Load your game (can take a loooong time)
  4. Test it (unavoidable time loss, unless another bug has popped up via unit testing, code analyzer etc.)
And you can fix it. For instance, I know that Yandere Simulator makes all the students' photos during loading. Why should that be done there? Why not either move it to project building stage by adding build hook so Unity does that for you during full project rebuild, or, even better, why not disable it completely or replace with «PLACEHOLDER» text for debug builds? Each second spent watching the loading screen will be rightfully interpreted as «son is not coding» by the community.
Is it too late to reduce loading times? Hell NO.
  1. Jenkins
Or any other continuous integration tool. «Rebuild a project» can take a long time too, and what can we do about that? Let me give you an idea. Buy a new PC. Get a 32-core Threadripper, 32 GB of fastest RAM you can afford and a cool motherboard which would support all of that (of course, Ryzen/i5/Celeron/i386/Raspberry Pi is fine too, but the faster, the better). The rest is not necessary, e.g. a barely functional second hand video card burned out by bitcoin mining is fine. You set up another PC in your room. You connect it to your network. You set up ramdisk to speed things up even more. You properly set up Jenkins) on this PC. From now on, Jenkins cares about the rest: tracking your Git repository, (re)building process, large and time-consuming unit tests, invoking static code analyzer, profiling, generating reports and whatever else you can and want to hook up. More importantly, you can fix another bug while Jenkins is rebuilding the project for the previous one et cetera.
In general, continuous integration is a great technology to quickly track down errors that were introduced in previous versions, attempting to avoid those kinds of bug hunting sessions. I am highly unsure if continuous integration is needed for 10000-20000 source lines long projects, but things can be different as soon as we step into the 100k+ territory, and Yandere Simulator by now has approximately 150k+ source lines of code. I think that probably continuous integration might be well worth it for Yandere Simulator.
Is it too late to add continuous integration? NO, albeit it is going to take some time and skills to set up.
  1. Stop caring about the criticism
Stop comparing Alex to Scott Cawton. IMO Alex is very similar to the person known as SgtMarkIV, the developer of Brutal Doom, who is also a notorious edgelord who, for example, also once told somebody to kill himself, just like… However, being a horrible person, SgtMarkIV does his job. He simply does not care much about public opinion. That's the difference.
  1. Go outside
Enough said. Your brain works slower if you only think about games and if you can't provide it with enough oxygen supply. I know that this one is probably the hardest to implement, but…
That's all, folks.
Bonus: Do you think how short this list would have been if someone just simply listened to Mike Zaimont instead of breaking down in tears?
submitted by Dezhitse to Osana [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]

BitcoinBCH.com accidentally publishes on-chain proof that they fake BCHs adoption metrics. Post to r/btc gets deleted and OP is now permanently banned.

Everybody who has posted this on btc has been banned according to modlog. Total of 9 users so far. Don't post this on btc or you will get banned. If you get banned comment on this thread or PM me.

May 2020:

According to btc modlogs, mc-78 has been banned because he questioned the April report with this comment.

According to btc modlogs, BCH4TW has been banned because he questioned the April report with this comment.

March 2020:

According to btc modlogs, bch4god has been banned because he questioned the February report with this comment.

According to btc modlogs, ISeeGregPeople has been banned because he linked to this thread in his comment.

February 2020:

According to btc modlogs, whene-is-satoshi has been banned because he linked to this thread in his comment.

January 2020:

According to btc modlogs, cryptokittykiller's post has been removed for linking to this thread.

According to btc modlogs, bashcalf has now been banned for linking to this thread.

According to btc modlogs, EnterLayer2 has now been banned for this post pointing out that this thread has reached 1000 upvotes.

This article was posted by bitcoinsatellite on btc here. Once it reached frontpage it got deleted and OP was banned from btc and bitcoincash as a result.

Disclaimer: I am not and have never been affiliated with any of the mentioned parties in a private or professional matter.
Presumably in an attempt to smear a local competitor, Hayden Otto inadvertently publishes irrefutable on-chain proof that he excluded non-BCH retail revenue to shape the "BCH #1 in Australia" narrative.
  • Scroll down to "Proof of exclusion" if you are tired of the drama recap.
  • Scroll down to "TLDR" if you want a summary.

Recap

In September 2019, BitcoinBCH.com started publishing so called monthly "reports" about crypto retail payments in Australia. They claimed that ~90% of Australia's crypto retail revenue is processed via their own HULA system and that ~92% of all crypto retail revenue happens in BCH.
They are aggregating two data sources to come up with this claim.
One is TravelByBit (TBB) who publishes their PoS transactions (BTC, LN, ETH, BNB, DASH, BCH) live on a ticker.
The other source is HULA, a newly introduced POS system (BCH only) and direct competitor to TBB run by BitcoinBCH.com - the same company who created the report. Despite being on-chain their transactions are private, not published and not verifiable by third parties outside BitcoinBCH.com
Two things stood out in the "reports", noted by multiple users (including vocal BCH proponents):
  • The non-BCH parts must have tx excluded and the report neglects to mention it (the total in their TBB analysis does not match what is reported on the TBB website.)
  • The BCH part has outliers included (e.g. BCH city conference in September with 35x the daily average)
The TBB website loads the historic tx data in the browser but hides transactions older than 7 days from being displayed, i.e. you can access more than 7 days worth of data if you understand JavaScript and can read the source code (source).

Hayden Otto's reaction

In direct response to me publishing these findings on btc, Hayden Otto - an employee at BitcoinBCH.com and the author of the report who also happens to be a moderator of /BitcoinCash - banned me immediately from said sub (source).
In subsequent discussion (which repeated for every monthly "report" which was flawed in the same ways as described above), Hayden responded using the same tactics:
"No data was removed"
"The guy is straight out lying. There is guaranteed no missing tx as the data was collected directly from the source." (source)
"Only data I considered non-retail was removed"
"I also had these data points and went through them to remove non-retail transactions, on both TravelbyBit and HULA." (source)
He admits to have removed non-BCH tx by "Game Ranger" because he considers them non-retail (source). He also implies they might be involved in money laundering and that TBB might fail their AML obligations in processing Game Ranger's transactions (source).
The report does not mention any data being excluded at all and he still fails to explain why several businesses that are clearly retail (e.g. restaurants, cafes, markets) had tx excluded (source).
"You are too late to prove I altered the data"
"[...] I recorded [the data] manually from https://travelbybit.com/stats/ over the month of September. The website only shows transactions from the last 7 days and then they disappear. No way for anyone to access stats beyond that." (source)
Fortunately you can, if you can read the website's source code. But you need to know a bit of JavaScript to verify it yourself, so not an ideal method to easily prove the claim of data exclusion to the public. But it laters turns out Hayden himself has found an easier way to achieve the same.
"The report can't be wrong because it has been audited."
In response to criticism about the flawed methodology in generating the September report, BitcoinBCH.com hired an accountant from a regional Bitcoin BCH startup to "audit" the October report. This is remarkable, because not only did their reported TBB totals still not match those from the TBB site - their result was mathematically impossible. How so? No subset of TBB transaction in that month sums up to the total they reported. So even if they excluded retail transactions at will, they still must have messed up the sum (source). Why didn't their auditor notice their mistake? She said she "conducted a review based on the TravelByBit data provided to her", i.e. the data acquisition and selection process was explicitly excluded from the audit (source).
"You are a 'pathetic liar', a 'desperate toll', an 'astroturf account' and 'a total dumb ass' and are 'pulling numbers out of your ass!'"
Since he has already banned me from the sub he moderates, he started to resort to ad hominems (source, source, source, source).

Proof of exclusion

I published raw data as extracted from the TBB site after each report for comparison. Hayden responded that I made those numbers up and that I was pulling numbers out of my ass.
Since he was under the impression that
"The website only shows transactions from the last 7 days and then they disappear. No way for anyone to access stats beyond that." (source)
he felt confident to claim that I would be
unable to provide a source for the [missing] data and/or prove that that data was not already included in the report. (source)
Luckily for us Hayden Otto seems to dislike his competitor TravelByBit so much that he attempted to reframe Bitcoin's RBF feature as a vulnerability specific to TBB PoS system (source).
While doublespending a merchant using the TBB PoS he wanted to prove that the merchant successfully registered the purchase as complete and thus exposed that the PoS sales history of TBB's merchants are available to the public (source), in his own words:
"You can literally access it from a public URL in the Web browser. There is no login or anything required, just type in the name of the merchant." (source)
As of yet it is unclear if this is intentional by TBB or if Hayden Ottos followed the rules of responsible disclosure before publishing this kind of data leak.
As it happens, those sale histories do not only include the merchant and time of purchases, they even include the address the funds were sent to (in case of on-chain payments).
This gives us an easy method to prove that the purchases from the TBB website missing in the reports belong to a specific retail business and actually happened - something that is impossible to prove for the alleged HULA txs.
In order to make it easier for you to verify it yourself, we'll focus on a single day in the dataset, September 17th, 2019 as an example:
  • Hayden Otto's report claims 20 tx and $713.00 in total for that day (source)
  • The TBB website listed 40 tx and a total of $1032.90 (daily summary)
  • Pick a merchant, e.g. "The Stand Desserts"
  • Use Hayden's "trick" to access that merchants public sale history at https://www.livingroomofsatoshi.com/merchanthistory/thestanddesserts, sort by date to find the 17th Sep 2019 and look for a transaction at 20:58 for $28. This proves that a purchase of said amount is associated with this specific retail business.
  • Paste the associated crypto on-chain address 17MrHiRcKzCyuKPtvtn7iZhAZxydX8raU9 in a blockchain explorer of your choice, e.g like this. This proves that a transfer of funds has actually happened.
I let software aggregate the TBB statistics with the public sale histories and you'll find at the bottom of this post a table with the on-chain addresses conveniently linked to blockchain explorers for our example date.
The total of all 40 tx is $1032.90 instead of the $713.00 reported by Hayden. 17 tx of those have a corresponding on-chain address and thus have undeniable proof of $758.10. Of the remaining 23, 22 are on Lightning and one had no merchant history available.
This is just for a single day, here is a comparison for the whole month.
Description Total
TBB Total $10,502
TBB wo. Game Ranger $5,407
TBB according to Hayden $3,737

What now?

The usual shills will respond in a predictive manner: The data must be fake even though its proof is on-chain, I would need to provide more data but HULA can be trusted without any proof, if you include outliers BCH comes out ahead, yada, yada.
But this is not important. I am not here to convince them and this post doesn't aim to.
The tx numbers we are talking about are less than 0.005% of Bitcoin's global volume. If you can increase adoption in your area by 100% by just buying 2 coffees more per day you get a rough idea about how irrelevant the numbers are in comparison.
What is relevant though and what this post aims to highlight is that BitcoinBCH.com and the media outlets around news.bitcoin.com flooding you with the BCH #1 narrative are playing dirty. They feel justified because they feel that Bitcoin/Core/Blockstream is playing dirty as well. I am not here to judge that but you as a reader of this sub should be aware that this is happening and that you are the target.
When BitcoinBCH.com excludes $1,000 Bitcoin tx because of high value but includes $15,000 BCH tx because they are made by "professionals", you should be sceptical.
When BitcoinBCH.com excludes game developers, travel businesses or craftsmen accepting Bitcoin because they don't have a physical store but include a lawyer practice accepting BCH, you should be sceptical.
When BitcoinBCH.com excludes restaurants, bars and supermarkets accepting Bitcoin and when pressed reiterate that they excluded non-retail businesses without ever explaning why a restaurant shouldn't be considered reatil, you should be sceptical.
When BitcoinBCH.com claims the reports have been audited but omit that the data acquisition was not part of the audit, you should be sceptical.
I expect that BitcoinBCH.com will stop removing transactions from TBB for their reports now that it has been shown that their exclusion can be provably uncovered. I also expect that HULA's BCH numbers will rise accordingly to maintain a similar difference.
Hayden Otto assumed that nobody could cross-check the TBB data. He was wrong. Nobody will be able to disprove his claims when HULA's BCH numbers rise as he continues to refuse their release. You should treat his claims accordingly.
As usual, do your own research and draw your own conclusion. Sorry for the long read.

TLDR

  • BitcoinBCH.com claimed no transactions were removed from the TBB dataset in their BCH #1 reports and that is impossible to prove the opposite.
  • Hayden Otto's reveals in a double spend attempt that a TBB merchant's sale history can be accessed publicly including the merchant's on-chain addresses.
  • (For example,) this table shows 40 tx listed on the TBB site on Sep 17th, including their on-chain addresses where applicable. The BitcoinBCH.com report lists only 20 tx for the same day.
  • (Most days and every months so far has had BTC transactions excluded.)
  • (For September, TBB lists $10,502 yet the report only claims $3,737.
No. Date Merchant Asset Address Amount Total
1 17 Sep 19 09:28 LTD Espresso Lightning Unable to find merchant history. 4.50 4.50
2 17 Sep 19 09:40 LTD Espresso Binance Coin Unable to find merchant history. 4.50 9.00
3 17 Sep 19 13:22 Josh's IGA Murray Bridge West Ether 0x40fd53aa...b6de43c531 4.60 13.60
4 17 Sep 19 13:23 Nom Nom Korean Eatery Lightning lnbc107727...zkcqvvgklf 16.00 29.60
5 17 Sep 19 13:24 Nom Nom Korean Eatery Lightning lnbc100994...mkspwddgqw 15.00 44.60
6 17 Sep 19 14:02 Nom Nom Korean Eatery Binance Coin bnb1w5mwu9...552thl4ru5 30.00 74.60
7 17 Sep 19 15:19 Dollars and Sense (Fortitude Valley) Lightning lnbc134780...93cpanyxfg 2.00 76.60
8 17 Sep 19 15:34 Steph's Cafe Binance Coin bnb124hcjy...ss3pz9y3r8 57.50 134.10
9 17 Sep 19 19:37 The Stand Desserts Binance Coin bnb13f58s9...qqc7fxln7s 18.00 152.10
10 17 Sep 19 19:59 The Stand Desserts Lightning lnbc575880...48cpl0z06q 8.50 160.60
11 17 Sep 19 20:00 The Stand Desserts Lightning lnbc575770...t8spzjflym 8.50 169.10
12 17 Sep 19 20:13 The Stand Desserts Lightning lnbc202980...lgqp5ha8f4 3.00 172.10
13 17 Sep 19 20:21 The Stand Desserts Lightning lnbc577010...decq7r4p05 8.50 180.60
14 17 Sep 19 20:24 Fat Dumpling Lightning lnbc217145...9dsqpjjr6g 32.10 212.70
15 17 Sep 19 20:31 The Stand Desserts Lightning lnbc574530...wvcpp3pcen 8.50 221.20
16 17 Sep 19 20:33 The Stand Desserts Lightning lnbc540660...rpqpzgk8z0 8.00 229.20
17 17 Sep 19 20:37 The Stand Desserts Lightning lnbc128468...r8cqq50p5c 19.00 248.20
18 17 Sep 19 20:39 The Stand Desserts Lightning lnbc135220...cngp2zq6q4 2.00 250.20
19 17 Sep 19 20:45 The Stand Desserts Lightning lnbc574570...atcqg738p8 8.50 258.70
20 17 Sep 19 20:51 Fat Dumpling Lightning lnbc414190...8hcpg79h9a 61.20 319.90
21 17 Sep 19 20:53 The Stand Desserts Lightning lnbc135350...krqqp3cz8z 2.00 321.90
22 17 Sep 19 20:58 The Stand Desserts Bitcoin 17MrHiRcKz...ZxydX8raU9 28.00 349.90
23 17 Sep 19 21:02 The Stand Desserts Bitcoin 1Hwy8hCBff...iEh5fBsCWK 10.00 359.90
24 17 Sep 19 21:03 The Stand Desserts Lightning lnbc743810...dvqqnuunjq 11.00 370.90
25 17 Sep 19 21:04 The Stand Desserts Lightning lnbc114952...2vqpclm87p 17.00 387.90
26 17 Sep 19 21:10 The Stand Desserts Lightning lnbc169160...lpqqqt574c 2.50 390.40
27 17 Sep 19 21:11 The Stand Desserts Lightning lnbc575150...40qq9yuqmy 8.50 398.90
28 17 Sep 19 21:13 The Stand Desserts Lightning lnbc947370...qjcp3unr33 14.00 412.90
29 17 Sep 19 21:15 The Stand Desserts Binance Coin bnb1tc2vva...xppes5t7d0 16.00 428.90
30 17 Sep 19 21:16 Giardinetto Binance Coin bnb1auyep2...w64p6a6dlk 350.00 778.90
31 17 Sep 19 21:25 The Stand Desserts BCH 3H2iJaKNXH...5sxPk3t2tV 7.00 785.90
32 17 Sep 19 21:39 The Stand Desserts Binance Coin bnb17r7x3e...avaxwumc58 8.00 793.90
33 17 Sep 19 21:47 The Stand Desserts BCH 32kuPYT1tc...uFQwgsA5ku 18.00 811.90
34 17 Sep 19 21:52 The Stand Desserts BCH 3ELPvxtCSy...4QzvfVJsNZ 36.00 847.90
35 17 Sep 19 21:56 The Stand Desserts Lightning lnbc677740...acsp04sjeg 10.00 857.90
36 17 Sep 19 22:04 The Stand Desserts BCH 38b4wHg9cg...9L2WXC2BSK 54.00 911.90
37 17 Sep 19 22:16 The Stand Desserts Binance Coin bnb14lylhs...x6wz7kjzp5 18.00 929.90
38 17 Sep 19 22:21 The Stand Desserts BCH 3L8SK3Hr7u...F3htdSPxfL 90.00 1019.90
39 17 Sep 19 22:30 The Stand Desserts Binance Coin bnb19w6tle...774uknv57t 5.00 1024.90
40 17 Sep 19 22:48 The Stand Desserts BCH 3Qag8c4UYg...9EYuWzGjhs 8.00 1032.90
submitted by YeOldDoc to CryptoCurrency [link] [comments]

subs

sites

http://redditlist.com/nsfw
https://www.reddit.com//SomeRandomReddit/wiki/sickandweirdsubreddits
https://www.reddit.com/NSFW411/wiki/index
https://redditgrid.com/[sub]
https://reddpics.com/[sub]
https://redditp.com/[sub]

subs

/2busty2hide
/2healthbars
/2me4meirl
/2meirl4meirl
/3Dprinting
/3dspiracy
/4chan
/4kmonitors
/4PanelCringe
/11foot8
/13or30
/AAMasterRace
/ABC_PORN
/ABoringDystopia
/AbruptChaos
/absolutechonkers
/absoluteunit
/AbsoluteUnits
/AccidentalComedy
/AccidentalRacism
/AccidentalRenaissance
/AccidentalSlapStick
/accidentalswastika
/ActualFreakouts
/actualsubreddits
/adorableporn
/AdPorn
/AdultEducation
/AdultsAreFuckinStupid
/AdviceAnimals
/AfterTheShot
/agedlikemilk
/AirplaneFood
/AirSwimming
/ALLTHEANIMALS
/ALSScan
/AltBlonde
/AmateurTeen_Porn
/Amd
/AmericanGifs
/amibeingdetained
/amplifiers
/Amry
/Anal_Babes
/AnalHD
/analog
/AnalVidz
/Androgynoushotties
/angryconfusion
/Angryupvote
/AnimalbeingEngineers
/AnimalsBeingAnimals
/AnimalsBeingBros
/AnimalsBeingDerps
/AnimalsBeingJerks
/AnimalsBeingLoveable
/AnimalsBeingPerfect
/animalsdoingstuff
/AnimalsMonching
/AnimalsWithoutNecks
/AnimalTextGifs
/animation
/Animemes
/announcements
/ANormalDayInAmerica
/ANormalDayInRussia
/antiassholedesign
/Anticonsumption
/antifeminists
/antiMLM
/AquaticAsFuck
/archmemes
/arduino
/ArduinoProjects
/AreTheStraightsOK
/AsABlackMan
/AsianCuties
/asianpeoplegifs
/AskElectronics
/AskEngineers
/AssBootyButt
/assholedesign
/AssPotatoCucumberDog
/ATAAE
/ATBGE
/AteTheOnion
/Audiomemes
/AwesomeAss
/awfuleverything
/awfuleyebrows
/aww
/awwtf
/Awww
/Bad_Cop_No_Donut
/badassanimals
/badgunanatomy
/BadMensAnatomy
/badUIbattles
/badwomensanatomy
/BannerIT
/bash
/BeagleBone
/BeAmazed
/BeautifulHardware
/BeforeNAfterAdoption
/bertstrips
/BestCamSluts
/BestSnapchatNudes
/bestxxxgifs
/BetterEveryLoop
/beyondwholesome
/bigfan
/BiggerThanYouExpected
/BigTitsButClothed
/Bitcoin
/blackhat
/blackmagicfuckery
/BlackOps
/blackpeoplegifs
/Blep
/blop
/blunderyears
/blursedimages
/BollywoodRealism
/BoneAppleTea
/bonehurtingjuice
/BonerAlert
/bongbeauty
/Bonsai
/BonsaiPorn
/books
/Boomerhumour
/booty_queens
/bootyshorts
/Bossfight
/Botchedsurgeries
/bptcg
/BrandNewSentence
/Break_Yo_Dick_Thick
/breathinginformation
/BreedingMaterial
/BrokeNotCrappy
/brushybrushy
/BuffFluff
/buildapc
/bulksupplements
/Buttcoin
/ButterflyWings
/C_Programming
/cableadvice
/cablefail
/CableManagement
/cableporn
/cade
/calculators
/CamSluts
/capitalism_in_decay
/carbage
/CasualJiggles
/CatastrophicFailure
/catpranks
/CatsAreAssholes
/CatsareFake
/CatSlaps
/CatsStandingUp
/CatTaps
/celebnsfw
/celebritymouths
/Celebs
/CentOS
/chadsriseup
/Chandler_Bailey
/ChavGirls
/chicas
/China_Flu
/chinesekitty
/Chinesium
/ChipCommunity
/Chonkers
/ChoosingBeggars
/circlebroke2
/ClassicInternetPorn
/cleanhandgang
/cleavage
/coding
/Coffee
/college
/combinedgifs
/ComedyCemetery
/comedyheaven
/comedyhomicide
/Commahorror
/CommentRemovalChecker
/compsci
/CompTIA
/ComputerEngineering
/computerscience
/computersciencehub
/ComputerSecurity
/confidentlyincorrect
/ConfusedBoners
/confusing_perspective
/ConfusingGravity
/consolerepair
/conspiracy
/conspiracyundone
/coolgithubprojects
/CoolPornPicks
/corgi
/Coronavirus
/CoronaVirus_2019_nCoV
/CoronavirusMa
/CoronavirusUS
/CorporateFacepalm
/cosplaygirls
/CouldveBeenWorse
/COVID19
/CovIdiots
/Cplusplus
/cpp
/cpp_questions
/CrackSupport
/CrapperDesign
/CrappyArt
/CrappyDesign
/crappyoffbrands
/CrazyIdeas
/crazystairs
/creepyasterisks
/creepydesign
/creepyPMs
/cringe
/cringepics
/Cringetopia
/cringtopia
/cromch
/crossfail
/CrossfitGirls
/crypto
/cryptography
/csbooks
/CuddlePuddle
/CuntCompanies
/curiousboners
/curledfeetsies
/cursedimages
/cute
/CuteButHorrifying
/Cuties4U
/cybersecurity
/damncute
/Damnthatsinteresting
/dancingdoggos
/dangerousdesign
/DangleAndJingle
/dankmemes
/darkmoney
/dashcamgifs
/data_irl
/DataHoarder
/dataisbeautiful
/dataismisleading
/dataisoffensive
/dataisugly
/datgap
/Death_By_SnuSnu
/debianinrandomplaces
/Deep_Anal
/DeepFriedMemes
/DeepIntoYouTube
/DeerAreFuckingStupid
/Defcon
/DeformedStarfish
/delusionalartists
/DemocraticSocialism
/DesignPorn
/DesirePath
/DesirePaths
/desnudas
/devkit
/didnteventry
/DidntKnowIWantedThat
/didntspecifyifhe
/digitalpiracy
/dislikedreplyingwith
/DIY
/diyelectronics
/DIYGear
/diyguitar
/diykits
/diypedals
/DnDIY
/Dogberg
/dogelore
/doggifs
/doggohate
/Doggystyle_NSFW
/DogReactions
/dogsinbooties
/DogSmiles
/dogssittinglikehumans
/dogswithjobs
/DoMyHomework
/dontdeadopeninside
/DontFundMe
/donthelpjustfilm
/dontputyourdickinthat
/douchey
/drumpfisfinished
/DSPDiscussion
/DWASBPEIF
/earwax
/eatsandwiches
/ECE
/ECEComponentExchange
/EDC
/EDCexchange
/edtech
/education
/eebooks
/ElectricalEngineering
/electricians
/electronics
/ElectronicsList
/emacs
/emergencymedicine
/engineering
/EngineeringPorn
/EngineeringStudents
/enginerdery
/engrish
/ENLIGHTENEDCENTRISM
/EnoughMuskSpam
/EntitledBitch
/entitledparents
/Entrepreneur
/eroticauthors
/Ersties
/esp32
/etymology
/everyfuckingthread
/excgarated
/excusememrwalrus
/Exonumia
/ExpectationVsReality
/explainlikeimfive
/EyeBelch
/Eyebleach
/facepalm
/FacialFun
/facingtheirparenting
/fakealbumcovers
/fakehistoryporn
/FanCentroBabes
/fatsquirrelhate
/Fedora
/Feic
/FellowKids
/FemaleDatingStrategy
/feminineboys
/Feminism
/FeminismStopsWhen
/ff7
/FFVIIRemake
/FieldNuts
/FiftyFifty
/Fighters
/fightinggamesvideos
/fightporn
/fightsticks
/FilthyLatinas
/FinalFantasy
/FinalFantasyVII
/financecirclejerk
/findareddit
/firefox
/Fitness
/flatpak
/Flipping
/florida
/FloridaMan
/FondantHate
/foodscam
/forbiddensnacks
/ForgottenNews
/forwardsfromgrandma
/ForwardsFromKlandma
/FoundTheAmerican
/foundthemobileuser
/fountainpens
/FPGA
/FreeEBOOKS
/freenas
/FreePopcorn
/friendlyarchitecture
/Frugal_Jerk
/Fuckgnome
/FuckStuartLittle
/fuckthesepeople
/FuckYouKaren
/FunBodybuilding
/functionalprints
/funny
/FunnyandSad
/Futurology
/GameDeals
/GamerGhazi
/gamesandtheory
/gaming
/gardening
/gatekeeping
/generalizedtools
/genewilder
/gentlemanboners
/gifs
/gifsthatendtoosoon
/gifsthatkeepongiving
/GifsThatStartTooLate
/git
/github
/gnome
/GnuPG
/GoCommitDie
/GoneMildPlus
/gonewilder
/gonwild
/goodboye
/GoodNsfwMorning
/GreenAndPleasant
/GuiltyDogs
/Guitar
/guitarcirclejerk
/guitarmod
/guitarpedals
/guitarpedalsjerk
/GymFails
/hackernews
/hacking
/HailCorporate
/hailhortler
/hairybuns
/hapas
/happygirls
/HappyWoofGifs
/hardcoreaww
/hats
/HaveWeMet
/HDsexvideos
/HeadlinesYouReadTwice
/HelicopterAddict
/HerCockHisAss
/heythatsneat
/highereducation
/HistoryMemes
/HitBoxPorn
/hitmanimals
/hittableFaces
/hmm
/hmmm
/hmmmgifs
/hoggit
/holdmybraincells
/holdmycosmo
/holdmyfeedingtube
/holdmyfries
/holdmyredbull
/HolUp
/homeautomation
/homedefense
/homelab
/HomemadeTools
/HomeworkHelp
/HostileArchitecture
/HostileBenches
/HotButts
/hottestgals
/howto
/HugePussy
/HumansBeingBros
/humblebrag
/humblebundles
/HydroHomies
/Hypocrisy
/i3wm
/iamatotalpieceofshit
/iamverybadass
/iamverysmart
/IDecidetheContext
/IdiotsFightingThings
/IdiotsInCars
/idiotsinhouses
/IdiotsNearlyDying
/Idiotswithguns
/idontunderstandsatire
/IFC
/ihadastroke
/ihavesex
/iiiiiiitttttttttttt
/im14andthisisdeep
/im14andthisiswoooosh
/imaginarygatekeeping
/Imapieceofshit
/Impracticaltools
/Impressiveasfuck
/imsorryjon
/InclusiveOr
/Incorgnito
/IncreasinglyVerbose
/indianpeoplefacebook
/inductionheaters
/InfowarriorRides
/Infuriating
/inoticed
/insaneparents
/InsanePeopleQuora
/Instagramreality
/instant_regret
/instantbarbarians
/instantkarma
/Instantregret
/INTELLECTUALPROPERTY
/interesting
/interestingasfuck
/internetofshit
/InternetStars
/ISO8601
/ITComputerSecurity
/itsaunixsystem
/JerkOffToCelebs
/jesuschristreddit
/JizzedToThis
/JobDoneBoss
/Journaling
/Julia
/justbootlickerthings
/JustBootThings
/justdependathings
/justforsocialmedia
/Justfuckmyshitup
/JustHotWomen
/JusticeServed
/JustLearnedTheFWord
/justneckbeardthings
/Justrolledintotheshop
/JustStemThings
/juxtaposition
/KamikazeByWords
/kde
/keming
/KenM
/KerbalSpaceProgram
/KidsAreFuckingSmart
/KidsAreFuckingStupid
/killthecameraman
/KittyPupperLove
/KneelingInBikinis
/KotakuInAction
/Kubuntu
/KylieRichardsXXX
/LadiesInBoyshorts
/LadyCocks
/LateStageCapitalism
/LaTeX
/latinas
/lawsuitdesign
/LearnEngineering
/learnlinux
/learnmath
/learnprogramming
/learnpython
/LeatherClassifieds
/lectures
/lefthandpoetry
/LeftHanging
/LegalTeens
/legs
/legsSpread
/Libertarian
/lifehacks
/Light_Fairy
/likeus
/LilGrabbies
/linux
/linux_cucks
/linux4noobs
/linuxadmin
/linuxaudio
/LinuxCirclejerk
/linuxmasterrace
/linuxmemes
/linuxmint
/linuxquestions
/LiveOverflow
/LivestreamFail
/LLLikeAGlove
/lmrcirclejerk
/lockpicking
/Locksmith
/lostredditors
/Loudgifs
/LoveWithFitness
/lowcostplay
/Luthier
/macbookpro
/MachineLuck
/MachinePorn
/MadeMeSmile
/madlads
/MakeMeSuffer
/MaliciousCompliance
/mallninjashit
/MandelaEffect
/ManjaroLinux
/masterhacker
/math
/mathbooks
/matheducation
/MathematicsMemes
/mathmemes
/matlab
/maxon3d00
/maybemaybemaybe
/maybemaybeoriginal
/McDonaldsEmployees
/me_irl
/meatcrayon
/mechanicalgifs
/MechanicalKeyboards
/mechanicalpencils
/mechmarket
/media
/MedicalGore
/medicase
/medicine
/medizzy
/meirl
/MemeGraveyard
/memes
/MEOW_IRL
/mercurial
/MetalZone
/MeTooThanks
/mexico
/michaelbaygifs
/microcomputing
/microgrowery
/mildlyinfuriating
/mildlyinteresting
/mildlypenis
/mildlyterrifying
/mildyinfuriating
/MilitaryPorn
/mindblowing
/minimalcatart
/MinimalWallpaper
/MiniPCs
/Miniworlds
/misleadingthumbnails
/mlem
/MonaLeslie
/Monitors
/Moronavirus
/MortalKombat
/MovieDetails
/MovieMistakes
/mramemes
/msaeachubaets
/MurderedByWords
/murdermittens
/MuscleConfusion
/MyPeopleNeedMe
/nalgonas
/NatureIsFuckingLit
/NCAAgirls
/NeckbeardNests
/Neverbrokeabone
/nevertellmetheodds
/NewChallenger
/NewOffensiveMemes
/NewProductPorn
/newsactors
/newsbloopers
/nextfuckinglevel
/Nibmeisters
/nicechips
/Nicegirls
/NightOutGirls
/NoahGetTheBoat
/NobodyAsked
/NonFunctionSlackFill
/nonnude
/nonono
/nononomaybe
/nononono
/nonononoaww
/nonononoyes
/nonononoyesno
/nonoyesyesnonononono
/nonprofit
/Nonprofit_Jobs
/nonprofitprojects
/normalinfuriating
/nosafetysmokingfirst
/NoStupidQuestions
/Notebook_share
/notebooks
/nothingeverhappens
/notinteresting
/NotKenM
/notlikeothergirls
/NotMyJob
/notreallyhe
/NSALeaks
/NSFW_Cams
/nsfw_gifs
/NSFWBOX
/nsfwcosplay
/NSFWFunny
/NSFWShitposts
/nsfwsports
/NSFWverifiedamateurs
/ntbdbiwdfta
/nycCoronavirus
/OddlyArousing
/oddlysatisfying
/ofcoursethatsathing
/OfficeScripts
/Ohlympics
/okbuddycapitalist
/okbuddylinux
/okbuddyretard
/OldSchoolCool
/olkb
/oneliners
/oneshotsubs
/onlyfanschicks
/OopsDidntMeanTo
/oopsec
/openbsd
/opendirectories
/OpenDirectoriesBot
/opensource
/openSUSE
/OperationsSecurity
/opsec
/OrangePI
/Organ_Eyes
/OSHA
/OutOfTheLoop
/PaidForWinRAR
/palest
/PanelGore
/paradolia
/Pareidolia
/ParentsAreFuckingDumb
/ParodyPornVideos
/patientgamers
/PBSOD
/pchelp
/pcmasterrace
/PCSleeving
/PedoGate
/pencils
/pens
/PeopleFuckingDying
/peopleofwalmart
/Perfectfit
/perfectlycutscreams
/PetsareAmazing
/PetTheDamnDog
/pettyrevenge
/PFSENSE
/photoshopbattles
/physec
/PiCases
/pics
/pihole
/Piracy
/PiratedGames
/Playboy
/playstupidgames
/PLC
/pocketpussy
/podman
/Pointless_Arguments
/PoliticalCompassMemes
/PoliticalHumor
/pop_os
/PopCultureGifs
/Porn2020
/PornCum
/Porndio
/PornHDvideos
/Pornheat
/PornhubComments
/PowerMoves
/PowerShell
/powerwashinggore
/powerwashingporn
/PraiseTheCameraMan
/PrayersToTrump
/Prematurecelebration
/printers
/Prisonwallet
/privacy
/privacytoolsIO
/Product_Hub
/ProgrammerHumor
/programming
/programmingcirclejerk
/programminghumor
/propaganda
/PropagandaPosters
/ProperAnimalNames
/ProRevenge
/PublicFreakout
/punchableface
/punchablefaces
/PunPatrol
/puppersheckingdying
/PuppySmiles
/PurplePillDebate
/PussyPass
/pussypassdenied
/PutYourDickInThat
/Python
/QuickMaffs
/quityourbullshit
/rage
/raisedbynarcissists
/rareinsults
/rarepuppers
/raspberry_pi
/RASPBERRY_PI_PROJECTS
/raspberrypi
/reallifedoodles
/RealTesla
/ReconstructionPorn
/RectalStickers
/redhat
/redneckengineering
/removalbot
/replywithasub
/RepurposedTools
/restofthefuckingowl
/RetroFuturism
/retrogaming
/RHCE
/rhcsa
/rhel
/righthanging
/rimjob_steve
/Roombaww
/royalporn
/RuinedMyDay
/sadcringe
/SafelyEndangered
/salty
/Satisfyingasfuck
/SavageGarden
/savedyouaclick
/sbubby
/SchizophreniaRides
/SchoolRevenge
/ScienceTeachers
/scriptedasiangifs
/ScriptedCaucasianGIFs
/scumoftheearth
/Secguards
/secondsketch
/secretcompartments
/security
/securityguards
/SelfAwarewolves
/Sexyly
/sexyshorts
/sffpc
/sfwpenis
/SFWporn
/ShadowPC
/ShamelesslyStolen
/sharepoint
/sheets
/SHHHHHEEEEEEEIIIITT
/shill
/ShitAmericansSay
/ShitMomGroupsSay
/Shitty_Car_Mods
/ShittyAnimalFacts
/shittyaskscience
/shittyfoodporn
/ShittyGroupMembers
/shittykickstarter
/shittykickstarters
/ShittyLifeProTips
/shittylpt
/shittymoviedetails
/shockwaveporn
/ShortShorts
/Showerthoughts
/ShowMeTheseTits
/Shrimping
/shutupandtakemymoney
/SighsUnzips
/sirensong
/Sissy_hot
/Skookum
/slammywhammies
/sleeving
/SlyGifs
/SnapChad
/Sneks
/snowden
/SocialEngineering
/softwaregore
/soldering
/SommerRay
/SourceOfPorn
/spacex
/specializedtools
/SpecialNeedsPuppers
/spiderbro
/sploot
/SportsDelights
/SquatWearingHeels
/StallmanWasRight
/starterpacks
/StartledCats
/stationery_jp
/stealth100
/steemhunt
/STEMdents
/stolendogbeds
/StonerEngineering
/StopEnoughMuskSpam
/StoppedWorking
/StraightGirlsPlaying
/StreetFighter
/StreetsIsWatchin
/strokewhilecommenting
/Stunning_Girls
/stupidpeople
/stupidtax
/Subliminal
/submechanophobia
/SubredditDrama
/SubredditHashtags
/subreddits
/SubsIFellFor
/subsithoughtifellfor
/subsithoughtwerefake
/SubsThatActuallyExist
/SubsYouFellFor
/suddenlynazi
/suddenlysexoffender
/SuddenlyTrans
/suicidebywords
/SuicideWatch
/SupermodelCats
/SuperThiccGirls
/supplychain
/suspiciouslyspecific
/SweatyPalms
/sysadmin
/systemcrash
/talesfromcavesupport
/TargetedShirts
/TaylorSwiftBreasts
/TaylorSwiftBum
/TaylorSwiftFace
/TaylorSwiftMidriff
/TaylorSwiftPictures
/TaylorSwiftsLegs
/Teachers
/teachingresources
/TechnicallyCorrect
/technicallythetruth
/technicallytrue
/techsupport
/techsupportmacgyver
/TechWar
/TeenHDporn
/TerminallyStupid
/teslamotors
/textbook_piracy
/Textbook_releases
/textbooks
/thanksihateit
/thanksiloveit
/ThanosCar
/thatescalatedquickly
/thathapp
/thatHappened
/ThatLookedExpensive
/ThatsInsane
/The_Dumbass
/the_elon
/The_Musk
/TheBluePill
/TheCuddlePuddle
/TheeHive
/theinternetofshit
/TheMightyPen
/TheNuclearOption
/theocho
/Theranos
/TheRedPill
/therewasanattemp
/therewasanattempt
/TheRightCantMeme
/thespoonyexperiment
/TheWayWeWere
/theydidthemath
/theydidthemeth
/theydidthemonstermath
/theydidthemonstermeth
/theyknew
/thick
/ThickGirlsTwerking
/ThickTaylorSwift
/thingsforants
/ThisButUnironically
/Thisismylifemeow
/thisismylifenow
/ThriftStoreHauls
/ThunderThots
/ti36xproMasterRace
/tight_shorts
/TightShorts
/TIHI
/Tinder
/tippytaps
/Tiresaretheenemy
/titlegore
/Tonedeafcelebs
/toofers
/tooktoomuch
/TopConspiracy
/toptalent
/torrents
/TouchThaFishy
/trashy
/TrashyButWholesome
/TronScript
/trypophobia
/TsundereSharks
/tuckedinkitties
/TwentyCharacterLimit
/twerking
/Twitch
/Ubuntu
/UbuntuAppDev
/umass
/UMassECEMemes
/UNBGBBIIVCHIDCTIICBG
/underbutt
/UnethicalLifeProTips
/Unexpected
/UnexpectedB99
/unexpectedbrooklyn99
/UnexpectedDannyDevito
/unexpectedidubbbz
/UnexpectedOuija
/unexpectedpawnee
/unexpectedstarwars
/UnexpectedThanos
/unexpectedthreefifths
/UnexpectedYoda
/United_Chads
/unixporn
/unRAID
/UnresolvedMysteries
/UnsleepingNsfw
/untrustworthypoptarts
/UpvotedBecauseButt
/usefulredcircle
/usefulscripts
/uselessredcircle
/UsernameChecksOut
/USGEC
/VaporwaveAesthetics
/Vastlystupid
/vaxxhappened
/VEDC
/Veronica_Victoria
/Vertical_NSFW
/VerticalGifs
/vexillology
/videos
/videosurveillance
/VikaBronova
/ViralSnaps
/vuejs
/VXJunkies
/wallpaper
/wallpaperdump
/wallpaperpacks
/wallpapers
/wallstreetbets
/WatchDoggoDieInside
/WatchDogsDieInside
/WatchDogsWoofInside
/Watchexchange
/WatchPeopleDieInside
/watchpeoplesurvive
/watchpuppersdieinside
/webdev
/Wellthatsucks
/wellthereshouldbe
/Wellworn
/whatcouldgoright
/Whatcouldgowrong
/whatisthisthing
/whatsinthebag
/whatsthisbug
/WhatsWrongWithYourDog
/wheredidthesoldergo
/whiteknighting
/whitepeoplegifs
/WhitePeopleReddit
/WhitePeopleTwitter
/wholesome
/wholesomegifs
/whoosh
/Why
/whybrows
/WhyWereTheyFilming
/WikiLeaks
/wildlyinfuriating
/windows
/Windows10
/WindowsMasterRace
/WinStupidPrizes
/woahdude
/wokekids
/womenEngineers
/woodworking
/woooosh
/woosh
/WorshipTaylorSwift
/wowthanksimcured
/wowthanksimrich
/WTF
/WTFwish
/Wuhan_Flu
/XXX_HD
/XxxHDVideos
/yesnoyesno
/yesyesyesdamn
/yesyesyesno
/yesyesyesomgyes
/yesyesyesyesno
/youareverysmart
/YourAnalBabes
/YourJokeButWorse
/youseeingthisshit
/youtubehaiku
/zfs
/Zoomies
/zsh
submitted by porn_account0001 to u/porn_account0001 [link] [comments]

Evernote hacked

Edit: Please note: Evernote as a whole is not hacked, I made a mistake with the title. I mean to say that people's accounts are getting compromised. Please see further down below the copy of the note being added to people's accounts.

Title: Pay attention, you've been hacked

Hello, your account have been hacked.
All of your notes and notebooks were downloaded with all attachments.
You should pay 300$ to Вitcoin address [BTC Address removed]
and then write an email to [protonmail email removed]
with giving an your unique Evernote ID:
[my evernote ID removed]

Otherwise, all your notebooks & notes will be automatically posted to hacking forums in 5 days, where people know what to do with your sensitive data (ID, driver license, passwords, etc...).

Forums: verified, bhf, exploit, hackforums... Why 300$? You can lose much more if your data will be used in crimes or will leak to forums. We learn by our mistakes.

Good luck! :)
Proof Data:
Auth:**[my email removed]:[my actual account password removed]**
Last Notes:
[generified format without my personal notes below]
[note name] | upd: Mon, 01 Jan 1000 00:00:00 GMT
___
There seems to be someone getting passwords for people's evernotes accounts and attempting to extort money or they will post sensitive information online. Unfortunately the posts I have seen on this subreddit have included personal information and so the mods remove it. This is fine, but when the mods remove a post, people don't see the mod saying to remove content. As such, I am posting the message, with content redacted, so at least when people search the message online it doesn't seem like no one else is dealing with this problem.
This is clearly not just spam. This is a note posted directly in someone's unsorted notes and includes your evernote password in plaintext. I can actually see looking back in my account access history that my account has been accessed over the past 3 weeks by devices in places like Russia, Brazil, Mexico, China, Vietnam, South Korea, and Egypt.
I personally am a bit confused about where they got my password as I have phased it out of my accounts a while ago and it has only been in a single breach on haveibeenpwned, compared to my email which has been in quite a few. It could be from some public list of passwords, but I am a bit skeptical. Evernote support says this is not a breach, though, and they would be the ones to know.
I have already contacted protonmail about this and have been informed that the hacker's email listed in this note has been temporarily deactivated. I baited the hackers into admitting their malicious intent via their email account and was told by protonmail that this would be sufficient to make their account deactivation permanent.
I see from looking at the hacker's bitcoin address that they successfully got 2 people to give them the $300 requested.
Please avoid paying the hackers. Look at your access history, they are not the only ones who have downloaded your notes. All that you do by paying them is encourage this malicious behavior.
Instead, per evernote security:
  1. Change your password immediately. Choose a unique password that you don't use on any other website.
  2. Review the authorized applications and access history for your account. Revoke access to any applications that you are suspicious of or that have accessed your account from an IP address you don't know.
  3. Set up two-step verification on your account as an additional layer of security.
  4. Encrypt sensitive text inside your note. When you encrypt text in a note, a separate password will be required to view the text, even if someone, including you, has access to your account.
  5. If you stored any sensitive data in your account like passwords, credit card numbers, or cryptocurrency keys, you should consider changing them to stop or prevent misuse.
Edit: formatting
submitted by joeyishar to Evernote [link] [comments]

Crypto Banking Wars: Will Coinbase or Binance Become The Bank of The Future?

Crypto Banking Wars: Will Coinbase or Binance Become The Bank of The Future?
Can the early success of major crypto exchanges propel them to winning the broader consumer finance market?
https://reddit.com/link/i48t4q/video/v4eo10gom7f51/player
This is the first part of Crypto Banking Wars — a new series that examines what crypto-native company is most likely to become the bank of the future. Who is best positioned to reach mainstream adoption in consumer finance?
While crypto allows the world to get rid of banks, a bank will still very much be necessary for this powerful technology to reach the masses. We believe a crypto-native company, like Genesis Block, will become the bank of the future.
In an earlier series, Crypto-Powered, we laid out arguments for why crypto-native companies have a huge edge in the market. When you consider both the broad spectrum of financial use-cases and the enormous value unlocked through these DeFi protocols, you can see just how big of an unfair advantage blockchain tech becomes for companies who truly understand and leverage it. Traditional banks and fintech unicorns simply won’t be able to keep up.
The power players of consumer finance in the 21st century will be crypto-native companies who build with blockchain technology at their core.
The crypto landscape is still nascent. We’re still very much in the fragmented, unbundled phase of the industry lifecycle. Beyond what Genesis Block is doing, there are signs of other companies slowly starting to bundle financial services into what could be an all-in-one bank replacement.
So the key question that this series hopes to answer:
Which crypto-native company will successfully become the bank of the future?
We obviously think Genesis Block is well-positioned to win. But we certainly aren’t the only game in town. In this series, we’ll be doing an analysis of who is most capable of thwarting our efforts. We’ll look at categories like crypto exchanges, crypto wallets, centralized lending & borrowing services, and crypto debit card companies. Each category will have its own dedicated post.
Today we’re analyzing big crypto exchanges. The two companies we’ll focus on today are Coinbase (biggest American exchange) and Binance (biggest global exchange). They are the top two exchanges in terms of Bitcoin trading volume. They are in pole position to winning this market — they have a huge existing userbase and strong financial resources.
Will Coinbase or Binance become the bank of the future? Can their early success propel them to winning the broader consumer finance market? Is their growth too far ahead for anyone else to catch up? Let’s dive in.
https://preview.redd.it/lau4hevpm7f51.png?width=800&format=png&auto=webp&s=2c5de1ba497199f36aa194e5809bd86e5ab533d8

Binance

The most formidable exchange on the global stage is Binance (Crunchbase). All signs suggest they have significantly more users and a stronger balance sheet than Coinbase. No other exchange is executing as aggressively and relentlessly as Binance is. The cadence at which they are shipping and launching new products is nothing short of impressive. As Tushar Jain from Multicoin argues, Binance is Blitzscaling.
Here are some of the products that they’ve launched in the last 18 months. Only a few are announced but still pre-launch.
Binance is well-positioned to become the crypto-powered, all-in-one, bundled solution for financial services. They already have so many of the pieces. But the key question is:
Can they create a cohesive & united product experience?

Binance Weaknesses

Binance is strong, but they do have a few major weaknesses that could slow them down.
  1. Traders & Speculators Binance is currently very geared for speculators, traders, and financial professionals. Their bread-and-butter is trading (spot, margin, options, futures). Their UI is littered with depth charts, order books, candlesticks, and other financial concepts that are beyond the reach of most normal consumers. Their product today is not at all tailored for the broader consumer market. Given Binance’s popularity and strength among the pro audience, it’s unlikely that they will dumb down or simplify their product any time soon. That would jeopardize their core business. Binance will likely need an entirely new product/brand to go beyond the pro user crowd. That will take time (or an acquisition). So the question remains, is Binance even interested in the broader consumer market? Or will they continue to focus on their core product, the one-stop-shop for pro crypto traders?
  2. Controversies & Hot Water Binance has had a number of controversies. No one seems to know where they are based — so what regulatory agencies can hold them accountable? Last year, some sensitive, private user data got leaked. When they announced their debit card program, they had to remove mentions of Visa quickly after. And though the “police raid” story proved to be untrue, there are still a lot of questions about what happened with their Shanghai office shut down (where there is smoke, there is fire). If any company has had a “move fast and break things” attitude, it is Binance. That attitude has served them well so far but as they try to do business in more regulated countries like America, this will make their road much more difficult — especially in the consumer market where trust takes a long time to earn, but can be destroyed in an instant. This is perhaps why the Binance US product is an empty shell when compared to their main global product.
  3. Disjointed Product Experience Because Binance has so many different teams launching so many different services, their core product is increasingly feeling disjointed and disconnected. Many of the new features are sloppily integrated with each other. There’s no cohesive product experience. This is one of the downsides of executing and shipping at their relentless pace. For example, users don’t have a single wallet that shows their balances. Depending on if the user wants to do spot trading, margin, futures, or savings… the user needs to constantly be transferring their assets from one wallet to another. It’s not a unified, frictionless, simple user experience. This is one major downside of the “move fast and break things” approach.
  4. BNB token Binance raised $15M in a 2017 ICO by selling their $BNB token. The current market cap of $BNB is worth more than $2.6B. Financially this token has served them well. However, given how BNB works (for example, their token burn), there are a lot of open questions as to how BNB will be treated with US security laws. Their Binance US product so far is treading very lightly with its use of BNB. Their token could become a liability for Binance as it enters more regulated markets. Whether the crypto community likes it or not, until regulators get caught up and understand the power of decentralized technology, tokens will still be a regulatory burden — especially for anything that touches consumers.
  5. Binance Chain & Smart Contract Platform Binance is launching its own smart contract platform soon. Based on compatibility choices, they have their sights aimed at the Ethereum developer community. It’s unclear how easy it’ll be to convince developers to move to Binance chain. Most of the current developer energy and momentum around smart contracts is with Ethereum. Because Binance now has their own horse in the race, it’s unlikely they will ever decide to leverage Ethereum’s DeFi protocols. This could likely be a major strategic mistake — and hubris that goes a step too far. Binance will be pushing and promoting protocols on their own platform. The major risk of being all-in on their own platform is that they miss having a seat on the Ethereum rocket ship — specifically the growth of DeFi use-cases and the enormous value that can be unlocked. Integrating with Ethereum’s protocols would be either admitting defeat of their own platform or competing directly against themselves.

Binance Wrap Up

I don’t believe Binance is likely to succeed with a homegrown product aimed at the consumer finance market. Their current product — which is focused heavily on professional traders and speculators — is unlikely to become the bank of the future. If they wanted to enter the broader consumer market, I believe it’s much more likely that they will acquire a company that is getting early traction. They are not afraid to make acquisitions (Trust, JEX, WazirX, DappReview, BxB, CoinMarketCap, Swipe).
However, never count CZ out. He is a hustler. Binance is executing so aggressively and relentlessly that they will always be on the shortlist of major contenders.
https://preview.redd.it/mxmlg1zqm7f51.png?width=800&format=png&auto=webp&s=2d900dd5ff7f3b00df5fe5a48305d57ebeffaa9a

Coinbase

The crypto-native company that I believe is more likely to become the bank of the future is Coinbase (crunchbase). Their dominance in America could serve as a springboard to winning the West (Binance has a stronger foothold in Asia). Coinbase has more than 30M users. Their exchange business is a money-printing machine. They have a solid reputation as it relates to compliance and working with regulators. Their CEO is a longtime member of the crypto community. They are rumored to be going public soon.

Coinbase Strengths

Let’s look at what makes them strong and a likely contender for winning the broader consumer finance market.
  1. Different Audience, Different Experience Coinbase has been smart to create a unique product experience for each audience — the pro speculator crowd and the common retail user. Their simple consumer version is at Coinbase.com. That’s the default. Their product for the more sophisticated traders and speculators is at Coinbase Pro (formerly GDAX). Unlike Binance, Coinbase can slowly build out the bank of the future for the broad consumer market while still having a home for their hardcore crypto traders. They aren’t afraid to have different experiences for different audiences.
  2. Brand & Design Coinbase has a strong product design team. Their brand is capable of going beyond the male-dominated crypto audience. Their product is clean and simple — much more consumer-friendly than Binance. It’s clear they spend a lot of time thinking about their user experience. Interacting directly with crypto can sometimes be rough and raw (especially for n00bs). When I was at Mainframe we hosted a panel about Crypto UX challenges at the DevCon4 Dapp Awards. Connie Yang (Head of Design at Coinbase) was on the panel. She was impressive. Some of their design philosophies will bode well as they push to reach the broader consumer finance market.
  3. USDC Stablecoin Coinbase (along with Circle) launched USDC. We’ve shared some stats about its impressive growth when we discussed DeFi use-cases. USDC is quickly becoming integrated with most DeFi protocols. As a result, Coinbase is getting a front-row seat at some of the most exciting things happening in decentralized finance. As Coinbase builds its knowledge and networks around these protocols, it could put them in a favorable position to unlock incredible value for their users.
  4. Early Signs of Bundling Though Coinbase has nowhere near as many products & services as Binance, they are slowly starting to add more financial services that may appeal to the broader market. They are now letting depositors earn interest on USDC (also DAI & Tezos). In the UK they are piloting a debit card. Users can now invest in crypto with dollar-cost-averaging. It’s not much, but it’s a start. You can start to see hints of a more bundled solution around financial services.

Coinbase Weaknesses

Let’s now look at some things that could hold them back.
  1. Slow Cadence In the fast-paced world of crypto, and especially when compared to Binance, Coinbase does not ship very many new products very often. This is perhaps their greatest weakness. Smaller, more nimble startups may run circles around them. They were smart to launch Coinbase Ventures where tey invest in early-stage startups. They can now keep an ear to the ground on innovation. Perhaps their cadence is normal for a company of their size — but the Binance pace creates quite the contrast.
  2. Lack of Innovation When you consider the previous point (slow cadence), it’s unclear if Coinbase is capable of building and launching new products that are built internally. Most of their new products have come through acquisitions. Their Earn.com acquisition is what led to their Earn educational product. Their acquisition of Xapo helped bolster their institutional custody offering. They acqui-hired a team to help launch their staking infrastructure. Their acquisition of Cipher Browser became an important part of Coinbase Wallet. And recently, they acquired Tagomi — a crypto prime brokerage. Perhaps most of Coinbase’s team is just focused on improving their golden goose, their exchange business. It’s unclear. But the jury is still out on if they can successfully innovate internally and launch any homegrown products.
  3. Talent Exodus There have been numerous reports of executive turmoil at Coinbase. It raises a lot of questions about company culture and vision. Some of the executives who departed include COO Asiff Hirji, CTO Balaji Srinivasan, VP & GM Adam White, VP Eng Tim Wagner, VP Product Jeremy Henrickson, Sr Dir of Eng Namrata Ganatra, VP of Intl Biz Dan Romero, Dir of Inst Sales Christine Sandler, Head of Trading Hunter Merghart, Dir Data Science Soups Ranjan, Policy Lead Mike Lempres, Sr Compliance Vaishali Mehta. Many of these folks didn’t stay with Coinbase very long. We don’t know exactly why it’s happening —but when you consider a few of my first points (slow cadence, lack of innovation), you have to wonder if it’s all related.
  4. Institutional Focus As a company, we are a Coinbase client. We love their institutional offering. It’s clear they’ve been investing a lot in this area. A recent Coinbase blog post made it clear that this has been a focus: “Over the past 12 months, Coinbase has been laser-focused on building out the types of features and services that our institutional customers need.” Their Tagomi acquisition only re-enforced this focus. Perhaps this is why their consumer product has felt so neglected. They’ve been heavily investing in their institutional services since May 2018. For a company that’s getting very close to an IPO, it makes sense that they’d focus on areas that present strong revenue opportunities — as they do with institutional clients. Even for big companies like Coinbase, it’s hard to have a split focus. If they are “laser-focused” on the institutional audience, it’s unlikely they’ll be launching any major consumer products anytime soon.

Coinbase Wrap Up

At Genesis Block, we‘re proud to be working with Coinbase. They are a fantastic company. However, I don’t believe that they’ll succeed in building their own product for the broader consumer finance market. While they have incredible design, there are no signs that they are focused on or capable of internally building this type of product.
Similar to Binance, I think it’s far more likely that Coinbase acquires a promising young startup with strong growth.

Honorable Mentions

Other US-based exchanges worth mentioning are Kraken, Gemini, and Bittrex. So far we’ve seen very few signs that any of them will aggressively attack broader consumer finance. Most are going in the way of Binance — listing more assets and adding more pro tools like margin and futures trading. And many, like Coinbase, are trying to attract more institutional customers. For example, Gemini with their custody product.

Wrap Up

Coinbase and Binance have huge war chests and massive reach. For that alone, they should always be considered threats to Genesis Block. However, their products are very, very different than the product we’re building. And their approach is very different as well. They are trying to educate and onboard people into crypto. At Genesis Block, we believe the masses shouldn’t need to know or care about it. We did an entire series about this, Spreading Crypto.
Most everyone needs banking — whether it be to borrow, spend, invest, earn interest, etc. Not everyone needs a crypto exchange. For non-crypto consumers (the mass market), the differences between a bank and a crypto exchange are immense. Companies like Binance and Coinbase make a lot of money on their crypto exchange business. It would be really difficult, gutsy, and risky for any of them to completely change their narrative, messaging, and product to focus on the broader consumer market. I don’t believe they would ever risk biting the hand that feeds them.
In summary, as it relates to a digital bank aimed at the mass market, I believe both Coinbase and Binance are much more likely to acquire a startup in this space than they are to build it themselves. And I think they would want to keep the brand/product distinct and separate from their core crypto exchange business.
So back to the original question, is Coinbase and Binance a threat to Genesis Block? Not really. Not today. But they could be, and for that, we want to stay close to them.
------
Other Ways to Consume Today's Episode:
Follow our social channels: https://genesisblock.com/follow/
Download the app. We're a digital bank that's powered by crypto: https://genesisblock.com/download
submitted by mickhagen to genesisblockhq [link] [comments]

Bitcoin Trading - YouTube 5 Coins to $5 Million  Teeka Tiwari List LEAKED - YouTube ⚠️ URGENT!! BITCOIN IS UNDER ATTACK !! ⚠️ MASSIVE YOUTUBE CENSORSHIP!!! CRYPTO YOUTUBERS DELETED FOR TALKING ABOUT BITCOIN!!! BITCOIN PUMP OVER?!!! BIG BTC TRADERS SHORTING NOW ...

AstroSat. Scientists discover galaxy that is the earliest source of UV light. Home; Gadgets. Mobiles. Latest Mobile Phones; Popular Mobile Phones; Upcoming Mobile Phones A list of potential bidders for the Bitcoin auction was accidentally leaked by the U.S. Marshals Service on Wednesday, according to the agency. It certainly seems like Microsoft has yet again leaked its own announced console. It reads: “Includes XBox Live Gold and unlimited access to over 100 high-quality games on Xbox Series XS, Xbox One, and Windows 10.” The Latest In A Growing List of Xbox Series S Leaks. This latest mention joins a growing list of Xbox Series S-themed slip-ups centered around Microsoft’s updated Xbox ... A list of potential bidders for the Bitcoin auction was accidentally leaked by the US Marshals Service yesterday, according to the agency. The Marshals Service confirmed that it accidentally ... US Marshals leak likely Bitcoin auction bidders, by mistake. Committing a common email blunder, the government agency accidentally reveals a list of potential bidders for Silk Road's seized bitcoins.

[index] [26576] [14573] [11312] [21243] [8191] [45591] [43810] [38777] [10773] [20433]

Bitcoin Trading - YouTube

Database Bitcoin Private Key 2017, bitcoin private key hack. Andreas Antonopoulos: Just because you don't need bitcoin, doesn't mean it's not needed. - Duration: 1:00:12. Singularity Weblog 23,620 views =====(coinbase trader)===== BITCOIN PUMP OVER?!!! BIG BTC TRADERS SHORTING NOW!!!!! THIS COULD BE A HUGE MISTAKE!!! #coinbase trading account #coinbase tradi... Sign in to like videos, comment, and subscribe. Sign in. Watch Queue Queue. Watch Queue Queue. Remove all; Disconnect; The next video is starting stop This video is unavailable. Watch Queue Queue. Watch Queue

#