Building the infrastructure for the Bitcoin Standard in Canada before the collapse of fiat currencies is the critical mission objective that drives innovation at Bull Bitcoin. We are very excited to announce an important milestone in fulfilling this duty: the public release of Liquid CAD, our newest product designed to accelerate and facilitate the adoption of Bitcoin. Liquid CAD is a non-custodial prepaid payment system denominated in Canadian dollars. Units of Liquid CAD (L-CAD) consist of vouchers issued on the Liquid Network as confidential bearer assets that can be transacted peer-to-peer using a Liquid wallet. Users acquire Liquid CAD by withdrawing their account balance out of Bull Bitcoin, by purchasing Liquid CAD with Bitcoin on Bull Bitcoin, by using the Liquid CAD withdrawal method on other Bitcoin liquidity providers such as Aquanow or by accepting L-CAD as method of payment.
L-CAD assets can only be redeemed for Bitcoin. They cannot be redeemed for a fiat currency payment.
Liquid CAD is a unique project rethinking the concept of fiat-pegged assets, avoiding the banking business model of “fiatcoin” (aka stablecoins) in favor of a prepaid payments model entirely centred around Bitcoin on-ramp and off-ramp. Liquid CAD is not a currency, nor is it a security: it is a prepaid card. Importantly, the business model of Liquid CAD is not to collect interest on funds in our custody, unlike fiatcoins, but rather to drive the sales of Bitcoin from which we derive our revenue and we benefit from Liquid CAD assets being cashed out and thus removed from our balance sheet. Bull Bitcoin does not get any revenue from interest. Every time an L-CAD token is purchased by a user, the amount of dollars deposited on Bull Bitcoin is guaranteed to one day be used by someone to purchase Bitcoin. It’s a one-way street: once a unit of fiat is tokenized as L-CAD, it’s never going back to its off-chain fiat form and will ultimately result in a buy order on a Bitcoin trading platform. The Liquid CAD logo is a drop of blood because our objective is to accelerate “fiat bleed”, a phenomenon best described by Pierre Rochard in his magnificent essay Speculative Attack:
“Bitcoin will not be eagerly adopted by the mainstream, it will be forced upon them. Forced, as in “compelled by economic reality”. People will be forced to pay with bitcoins, not because of ‘the technology’, but because no one will accept their worthless fiat for payments. Contrary to popular belief, good money drives out bad. This “driving out” has started as a small fiat bleed. It will rapidly escalate into Class IV hemorrhaging due to speculative attacks on weak fiat currencies. The end result will be hyperbitcoinization, i.e. “your money is no good here. Bitcoins are not just good money, they are the best money. The Bitcoin network has the best monetary policy and the best brand. We should therefore expect that bitcoins will drive out bad, weak currencies. My own prediction is that slow bleed has been accelerating and is only the first step. The second step will be speculative attacks that use bitcoins as a platform. The third and final step will be hyperbitcoinization.”
Different representations of Canadian dollars compete to be used as payment methods (cash, bank balances, PayPal balances, closed-loop prepaid cards, open-loop prepaid cards, etc.) and that the winner will be the one that has the best Bitcoin saleability, i.e. which can be most easily sold for Bitcoin at a moment’s notice. We’re very proud to provide this alternative payment method to Canadians in a time where the banking system is falling deeper into crisis, especially as the Canadian dollar is demonstrating itself to be one of the most pointless and weakest currencies that nobody really wants to hold. Finally, we’re very happy to be partnering with Aquanow, our recommended institutional liquidity provider for high-volume BTC-CAD trading. They will accept Liquid CAD deposits and withdrawals as being interchangeable with Canadian dollars. We hope that Liquid CAD will become the standard representation of Canadian dollar value among Canadian Bitcoin users.
Liquid Bitcoin (L-BTC) integration
In addition to Liquid CAD, Bull Bitcoin is also announcing that Liquid Bitcoin (L-BTC) payments are now supported interchangeably with Bitcoin transactions for all Bull Bitcoin services. This means that our users can buy, sell and spend L-BTC instead of BTC. Canadian Bitcoin traders can purchase L-BTC from BullBitcoin.com and fund their international trading accounts with L-BTC using ultra fast and cheap confidential transactions. They can also cash-out their Bitcoin balance as L-BTC from these platforms and sell those L-BTC for fiat on Bylls.com, avoiding risky and expensive international wire transfers to unknown and untrusted foreign banks. The transactional benefits of L-BTC are very potent:
Transaction amounts are hidden, in compliance with Canada’s strict privacy protection laws
Observers cannot tell whether the transaction is L-BTC or any other asset
Confirmation times are 1 minute
Transaction fees are very low (< 0.05$)
Disclaimer: Liquid Bitcoin (L-BTC) is not the same as Bitcoin (BTC). L-BTC Liquid Network assets are IOUs for Bitcoin held in a multisignature contract by the Liquid Network federation. The custody of the underlying Bitcoin is managed by a decentralized network of 15 members which process transactions and withdrawals from the multisignature contract according to the Liquid Federation protocol rules.
Liquid CAD detailed overview
Peer-to-peer prepaid payments by Bull Bitcoin
Liquid CAD is a non-custodial prepaid payment system denominated in Canadian dollars. Units of Liquid CAD (L-CAD) consist of vouchers issued on the Liquid Network as confidential bearer assets that can be transacted peer-to-peer using a Liquid wallet. Users acquire Liquid CAD by withdrawing their account balance out of the Bull Bitcoin, by purchasing Liquid CAD with Bitcoin on Bull Bitcoin, by using the Liquid CAD withdrawal method on other Bitcoin liquidity providers such as Aquanow or by accepting L-CAD as method of payment.
A new payment method in Canada
Liquid CAD can be used by anyone to send and receive payments denominated in Canadian dollars. Because of the permissionless nature of the Liquid Network, Bull Bitcoin cannot prevent Liquid CAD from being traded on secondary markets. Merchants, individuals and institutions must accept that only Bull Bitcoin can guarantee redemption of the L-CAD and that this redemption will be exclusively paid out in Bitcoin. Accepting Liquid CAD as payment is, in effect, the same as accepting gift cards as payment. However, Bitcoin being the most liquid commodity on the market, it can be transformed into any other currency easily for example using services such a Bylls which allow Canadians to pay all their utility bills, send bank transfers to third parties or sell Bitcoin to their bank account.
Making Canadian dollars bleed into Bitcoin
The purpose of Liquid CAD is to facilitate the transfer fiat in the context of the purchase and sale of Bitcoin and providing innovative new services that help Bitcoin users hedge the value of Canadian dollars against Bitcoin in the context of their commercial transactions. Our goal is to create a payment method that is specifically targeting Bitcoin users that wish to liquidate Canadian dollar payments for Bitcoin. Our mission is to accelerate the phenomenon known as “fiat bleed” whereby Canadians will gradually abandon inferior money (such as the Canadian dollar) for the superior Bitcoin alternative. Every Liquid CAD issued will ultimately be exchanged into Bitcoin. We are excited for the day Liquid CAD will be made obsolete by the inevitable hyperbitcoinization of the Canadian economy.
Like all other closed-loop prepaid instruments, Liquid CAD has counterparty risk. The owners are trusting that they will eventually be able to use Liquid CAD as a payment method on the Bull Bitcoin platform to fund their account and purchase Bitcoin. When a Bull Bitcoin user withdraws his Bull Bitcoin account balance as an L-CAD token, the Canadian dollars he used to fund this balance remains in our possession in the same manner as regular Bull Bitcoin vouchers. These funds are used to execute Bitcoin purchases when L-CAD owners decide to redeem their L-CAD for Bitcoin. In essence, each L-CAD is “backed” by the Canadian dollar deposit of the user that withdraws it from the platform in the first place.
Benefits of using and accepting Liquid CAD for payments
Irreversible, non-custodial and no bank required
Liquid CAD payments cannot be charged back, cancelled, delayed or frozen. There is no intermediary between the sender and the recipient. It is a bearer asset: whoever owns the keys owns the coins. It is a perfect way to accept payments or transact securely without depending on banks and payment processors. Canadians can use Liquid CAD to purchase Bitcoin and then use Bylls.com to pay billers, personal payees or simply sell Bitcoin to their bank account.
Fast transaction and cheap fees
Liquid Network transactions are sent and received instantly and require 1 minute for settlement. Transaction fees paid using Liquid Bitcoin can be as low as 300 satoshis per transaction (a few cents). In order to benefit from these cheap fees, make sure to download the latest version of the Elements software and ensure that the minimum transaction fee is set at 100 satoshis per kilobye. It only takes a few minutes to set up a free Liquid Network wallet, such a Green Wallet by blockstream.
Unlike Bitcoin, transactions between the sender and the recipient are encrypted. It is impossible for third parties observing Liquid CAD transactions on a block explorer to determine the amount of the transaction. In addition, it’s also impossible to even know you are using Liquid CAD, since the data identifying the asset itself is also encrypted!
What are the use-cases of Liquid CAD?
Buying and selling Bitcoin
The primary use-case of Liquid CAD is to make it easier to buy and sell Bitcoin on the Bull Bitcoin platform. By withdrawing their balance from Bull Bitcoin, users are reducing some (but not all) of the custody risk associated with keeping fiat currency on an exchange. For example, use Liquid CAD to create your own non-custodial dollar-cost-averaging schedule!
Onboarding new Bitcoin users
New users can be overwhelmed by the experience of dealing with banks to buy Bitcoin (and the heavier KYC process of account funding). You may be tempted to buy Bitcoin for them, but that will impose a lot of burdens on you. It’s much easier to set them up with a Green wallet, send them Liquid CAD and show them how to use Bull Bitcoin! They decide when is the right time for them to invest, with a lower KYC burden.
Hedging Bitcoin price
You may believe the price of Bitcoin will go down in the short term, but you still want to hold Bitcoin in the long term. Normally you have two options: short the Bitcoin price (very risky!) or sell your Bitcoin and receive Canadian dollars in your bank account (inconvenient!). By selling your Bitcoin for Liquid CAD, you can lock in the value of Bitcoin right now and buy them back later without needing to use your bank account or taking risks with leverage.
As a merchant, you want to receive the settlement of payments in Bitcoin. But this imposes a burden on your customers, which have to deal with the Bitcoin price volatility when they are paying you. Ask your clients to pay you with Liquid CAD, and you can get the settlement with Bitcoin on your own terms.
Payroll and suppliers
What if your staff or suppliers want to get paid in Bitcoin? It can be very difficult, because this means you are effectively buying Bitcoin on their behalf. Instead, you can pay them in Liquid CAD and let them deal with the process of choosing the exchange rate and using their own wallet. Let them deal with the tax burden, exchange rates and Bitcoin wallet security.
List of Bull Bitcoin Liquid Network features
Withdraw account balance as L-CAD
This is conceptually the same as “buying” Liquid CAD with your account balance. We call it “Withdrawing L-CAD” because on the Bull Bitcoin platform, we consider L-CAD and CAD to be interchangeable and fungible.
Fund account balance with L-CAD
To redeem Liquid CAD for Bitcoin, users need to first fund their account by selecting the “Deposit L-CAD” payment method. Bull Bitcoin users must always fund their account first before buying Bitcoin, and then purchase Bitcoin with their account balances. Reminder: account balances cannot be withdraw as fiat payments, but can later be withdrawn again as L-CAD.
Sell Bitcoin for L-CAD
You can sell Bitcoin and receive Liquid CAD payments instead of a bill payment, personal payee payment or bank payment. As soon as the Bitcoin transaction is confirmed, the Liquid CAD transaction is sent to the address you provided.
Liquid Bitcoin (L-BTC) and Bitcoin interchangeability
For every service which involves a Bitcoin payment, the user can substitute traditional Bitcoin payments for Liquid Bitcoin payments. This includes:
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:
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.
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.
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.
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!
The next XVG? Microcap 100x potential actually supported by fundamentals!
What’s up team? I have a hot one for you. XVG returned 12 million percent in 2017 and this one reminds me a lot of it. Here’s why: Mimblewimble is like Blu-Ray compared to CD-ROM in terms of its ability to compress data on a blockchain. The current BTC chain is 277gb and its capacity is limited because every time you spend a coin, each node needs to validate its history back to when it was mined (this is how double spending is prevented). Mimblewimble is different - all transactions in a block are aggregated and netted out in one giant CoinJoin, and only the current spending needs to be verified. This means that dramatically more transactions can fit into a smaller space, increasing throughput and lowering fees while still retaining the full proof of work game theory of Bitcoin. These blockchains are small enough to run a full node on a cheap smartphone, which enhances the decentralization and censorship resistance of the network. The biggest benefit, though, is that all transactions are private - the blockchain doesn’t reveal amounts or addresses except to the actual wallet owner. Unlike earlier decoy-based approaches that bloat the chain and can still be data mined (XMR), Mimblewimble leaves no trace in the blockchain, instead storing only the present state of coin ownership. The first two Mimblewimble coins, Grin and Beam, launched to great fanfare in 2019, quickly reaching over $100m in market cap (since settled down to $22m and $26m respectively). They are good projects but grin has infinite supply and huge never-decreasing emission, and Beam is a corporate moneygrab whose founding investors are counting on you buying for their ROI. ZEC is valued at $568m today, despite the facts that only 1% of transactions are actually shielded, it has a trusted setup, and generating a confidential transaction takes ~60 seconds on a powerful PC. XMR is a great project but it’s valued at $1.2b (so no 100x) and it uses CryptoNote, which is 2014 tech that relies on a decoy-based approach that could be vulnerable to more powerful computers in the future. Mimblewimble is just a better way to approach privacy because there is simply no data recorded in the blockchain for companies to surveil. Privacy is not just for darknet markets, porn, money launderers and terrorists. In many countries it’s dangerous to be wealthy, and there are all kinds of problems with having your spending data be out there publicly and permanently for all to see. Namely, companies like Amazon are patenting approaches to identify people with their crypto addresses, “for law enforcement” but also so that, just like credit cards, your spending data can be used to target ads. (A) Coinbase is selling user data to the DEA, IRS, FBI, Secret Service, and who knows who else? (B) What about insurance companies raising your premiums or canceling your policy because they see you buying (legal) cannabis? If your business operates using transparent cryptocurrency, competitors can data mine your customer and supply chain data, and employees can see how much everyone else gets paid. I could go on, but the idea of “I have nothing to hide, so what do I care about privacy?” will increasingly ring hollow as people realize that this money printing will have to be paid by massive tax increases AND that those taxes will be directly debited from their “Central Bank Digital Currency” wallets. 100% privacy for all transactions also eliminates one HUGE problem that people aren’t aware of yet, but they will be: fungibility. Fungibility means that each coin is indistinguishable from any other, just like paper cash. Why is this important? Because of the ever-expanding reach of AML/KYC/KYT (Anti-Money Laundering / Know Your Customer / Know Your Transaction) as regulators cramp down on crypto and banks take over, increasingly coins become “tainted” in various ways. For example, if you withdraw coins to a mixing service like Wasabi or Samourai, you may find your account blocked. (C) The next obvious step is that if you receive coins that these chainalysis services don’t like for whatever reason, you will be completely innocent yet forced to prove that you didn’t know that the coins you bought were up to no good in a past life. 3 days ago, $100k of USDC was frozen. (D) Even smaller coins like LTC now have this problem, because “Chinese Drug Kingpins” used them. (E) I believe that censorable money that can be blocked/frozen isn’t really “your money”. Epic Cash is a 100% volunteer community project (like XVG and XMR) that had a fair launch in September last year with no ICO and no premine. There are very few projects like this, and it’s a key ingredient in Verge’s success (still at $110m market cap today despite being down 97% since the bubble peak) and why it’s still around. It has a small but super passionate community of “Freemen” who are united by a belief in the sound money economics of Bitcoin Standard emission (21m supply limit and ever-decreasing inflation) and the importance of privacy. I am super bullish on this coin for the following reasons:
Only $400k market cap
Supply started at zero, so there are no VC’s and team to dump on you into the pumps - all coins are mined into existence, just like Bitcoin.
It just had its first halving, reducing emission from 16 to 8 per block. Between now and 2028 there are FOUR (!) more halvings, from 4 to 2 to 1 and then finally 0.15 (I guess that would be an 85%-ing :p) and at this point the supply is the same as BTC and stays in sync forever until the last coin is mined in 2140. This simple supply curve is already accepted by the market as a winner, so why mess with success? (I)
Meets Andreas Antonopolous’ 5 pillars of open blockchains test: Public, Open, Borderless, Neutral, and Censorship Resistant. (How many coins can say this?)
Unlike Bitcoin, Epic created a multi-algorithm approach that enables people to mine on ordinary computers - 60% for CPU on RandomX, 38% for GPU on ProgPow, and 2% for ASIC’s on Cuckoo31+. The algorithms don’t compete with one another. This is essential for leveling the playing field and preventing massive farms from dominating. These percentages can change over time and new algorithms can be easily dropped in. You can mine today using an old laptop and in 5 years you will still be able to. Incidentally, there is nothing standing in the way of adding mobile phone-based mining, which ETN showed there’s a huge demand for.
Based off the excellent Grin codebase, which means they continue to pull in ongoing core code enhancements and focus on ease of use and market penetration instead. (Smart!)
Litecoin’s Charlie Lee is out there daily talking about their move to Mimblewimble, which provides free publicity. What people don’t realize is that you can’t just bolt on Mimblewimble to a legacy blockchain, that’s like putting a Ferrari engine into a school bus - it’s still a school bus, not a race car! LTC is doing it as an optional soft fork via “extension blocks” which will not be supported by all wallets and exchanges. Also, anyone using “optional” privacy features is declaring themselves to be suspicious, which kind of defeats the point for people who care about privacy.
The community is friendly and welcoming to new people coming in, with lots of helpful (independently created) tutorials and guides. (F)
It’s already a global phenomenon, with the whitepaper in 20+ languages (G) and (not bot-infested) active local-language communities on not only Telegram but also Wechat, LINE, QQ and other messenger platforms.
It’s only on two random little exchanges currently, Citex and Vitex. Vitex is actually a pretty good DEX with no KYC and a great mobile wallet.
They are very creative - since centralized exchanges want huge money to list, they created a non-inflationary ERC20 tracker token that’s exchangeable 1:1 for coins so that Uniswap trading is possible (H)
Because it doesn’t have a huge marketing budget in a sea of VC-funded shitcoins, it is as-yet undiscovered, which is why it’s so cheap. There are only 4 Mimblewimble-based currencies on the market: MWC at $162m, BEAM at $26m, GRIN at $22m, and EPIC at $0.4m. This is not financial advice and as always, do your own research, but I’ve been buying this gem for months and will continue to. This one ticks all the boxes for me, the only real problem is that it’s hard to buy much without causing a huge green candle. Alt season is coming, and coins like this are how your neighbor Chad got his Lambo back in 2017. For 2021, McLaren is a better choice and be sure to pay cash so that it doesn’t get repossessed like Chad!
Energi is a self-funding (no ICO and no premine) cryptocurrency that has a purpose to become the world’s leading cryptocurrency with the unification of Smart Contracts, Governance and Self-funding Treasury to ensure longevity and enable rapid growth. You can read more about why we decided to self-fund and chose not to conduct an ICO here. Energi provides a small allocation to Proof-of-Stake (PoS) rewards, takes a bulk of the coin issuance and gives it to its treasury and active Masternodes. Energi also allocates 10% on-going reward to the leadership of the Energi Backbone, which is significantly less compared to today’s ICOs’ rewarding their founders between 20–50% of the tokens distributed. Another trait that sets Energi apart from ICOs is they give an on-going 10% allocation through each block reward, rather than rewarding the founders up-front.
2. What are the Fundamentals of Energi?
1 minute block times and a 2 megabyte block size limit provide Energi with a vast transaction capacity for regular on-chain transactions. This allows for plenty of space on the blockchain for extremely fast transactions with very low fees. Energi features a powerful on-chain scaling solution with a system of incentivized full nodes called Energi Masternodes. A Masternode is a full node backed by 1,000 NRG collateral that provides level 2 scalability to the Energi Cryptocurrency. 40% of the emissions of Energi is allocated to Masternodes, providing an extremely strong incentive to grow the number of full nodes and scalability of the network.
A key feature of Energi is its powerful treasury system. Energi makes up to 40% of the emissions available to the treasury, to be utilized in a manner that provides maximum benefit. Treasury allocation is decentralized, allowing for submitted proposals from anyone, to be voted on by Masternodes and paid out from the emissions. Energi has a 14 day treasury cycle, allowing quick payments for proposal authors and contributors, as well as strategic responsiveness to effective proposals. Energi is guided by the principle that every dollar spent from its funding model should yield more than one dollar of value in return. Thanks to a 14 day treasury cycle, the Energi team is able to measure results and respond quickly to changes in strategy.
The Energi Treasury is a decentralized governance model designed with Masternodes as caretakers, with voting rights on how to best utilize treasury funding. This governance model reduces risk by allowing participation from everyone who holds 1,000 NRG as a Masternode. In this way, the Energi community can work together on how to best build the strategic direction of Energi.
Energi Cryptocurrency has a simple rate of inflation at 1 million coins per month with no maximum cap. This ensures consistency in funding allocation, Masternode rewards, and PoS rewards, making the economics of the cryptocurrency more understandable for everyone who chooses to participate in Energi. No coin supply limit ensures that Energi is prepared for the long term, avoiding “bubble” economics caused by dramatic early inflation that in most coins only serves to benefit founders ahead of increased adoption.
Energi conducted a fair launch on April 14, 2018 with no ICO and no premine. Prior to launch, the Energi team gave a specific time and date for the launch of its main net, which its vibrant community eagerly awaited, so that mining could begin fairly, again avoiding centralization among the coin founders (It's important to note that Energi has transitioned from Proof-of-Work consensus to a Proof-of-Stake consensus). Energi Masternode payments were designed to begin at block 216000, which occurred on September 18, 2018, almost 160 days after launch. This ensured time to list Energi on exchanges, and to grow the community, encouraging fair and equitable distribution before the extremely powerful Masternode rewards began. It is all too common for Masternode coins to feature a premine, which has the effect of centralizing distribution among the founders and early adopters. From 2018 to 2020, Energi distributed nearly 4 million coins to users who contributed to spreading awareness of the project with social media activities about Energi, such as tweets, follows, and subscriptions on all major social media platforms.
Decentralized governance with Masternodes helps to ensure everyone is able to participate in Energi and help guide the project to achieve the best results. The change to the requirement to run a Masternode, from 10 000 NRG to 1 000 NRG, has allowed more people to be involved and boosted decentralization for the whole project.
Long Term Vision
All of the above features seamlessly work together in concert, to ensure that Energi is prepared for the long term. Rather than try to closely find a niche in the market, Energi is prepared to adapt and overcome all challenges for many years to come. Energi’s use case is that of a traditional cryptocurrency, such as Bitcoin. However, Energi’s strategy is to excel by avoiding the pitfalls of previous projects, while further utilizing and improving upon the most powerful ideas in the cryptocurrency space.
3. Coin Specs
Ticker: NRG Block time: 1 minute. Hashing Algorithm: Dagger-Hashimoto (similar to Ethereum). Masternode requirements: 1,000 Energi. Treasury cycle: Every 14 days. Approximately 1 million Energi will be released per month. The allocations can be observed easily as “10/10/40/40.” 10% will go to the Energi Backbone. 10% to the PoS participants 40% to Masternodes. 40% to the Treasury. Thus, for every block, allocations are: 2.28 Energi to the Backbone, 2.28 Energi to the PoS participants, 9.14 Energi to the Treasury, and 9.14 Energi to Masternodes. Since Treasury allocations are paid in two-week cycles, they are made in lump sums of approximately 184,000 Energi every 14 days. In order to allow for widespread distribution of Energi before Masternode payments began, Masternode rewards were delayed until day 150. This was to allow the airdrop campaign to be completed and ensure a large amount of NRG is spread out through the community. Until that point, Masternode rewards were redirected to the Treasury. Thus for the first 5 months, the Treasury gained approximately 368,000 Energi every two weeks (about 800k Energi per month). The airdrop campaign was designed to release ~4 million Energi to the community.
I am trying to import bitcoin from a rockitcion paper wallet (private key) also did run that paper wallet address through a block explorer like Blockchain.info: But it has no transaction and no funds in it after importing Which is getting me worried. Because I just bought the bitcoin at on the rockitcoin bitcoin atm.
Technical: A Brief History of Payment Channels: from Satoshi to Lightning Network
Who cares about political tweets from some random country's president when payment channels are a much more interesting and are actually capable of carrying value? So let's have a short history of various payment channel techs!
Generation 0: Satoshi's Broken nSequence Channels
Because Satoshi's Vision included payment channels, except his implementation sucked so hard we had to go fix it and added RBF as a by-product. Originally, the plan for nSequence was that mempools would replace any transaction spending certain inputs with another transaction spending the same inputs, but only if the nSequence field of the replacement was larger. Since 0xFFFFFFFF was the highest value that nSequence could get, this would mark a transaction as "final" and not replaceable on the mempool anymore. In fact, this "nSequence channel" I will describe is the reason why we have this weird rule about nLockTime and nSequence. nLockTime actually only works if nSequence is not 0xFFFFFFFF i.e. final. If nSequence is 0xFFFFFFFF then nLockTime is ignored, because this if the "final" version of the transaction. So what you'd do would be something like this:
You go to a bar and promise the bartender to pay by the time the bar closes. Because this is the Bitcoin universe, time is measured in blockheight, so the closing time of the bar is indicated as some future blockheight.
For your first drink, you'd make a transaction paying to the bartender for that drink, paying from some coins you have. The transaction has an nLockTime equal to the closing time of the bar, and a starting nSequence of 0. You hand over the transaction and the bartender hands you your drink.
For your succeeding drink, you'd remake the same transaction, adding the payment for that drink to the transaction output that goes to the bartender (so that output keeps getting larger, by the amount of payment), and having an nSequence that is one higher than the previous one.
Eventually you have to stop drinking. It comes down to one of two possibilities:
You drink until the bar closes. Since it is now the nLockTime indicated in the transaction, the bartender is able to broadcast the latest transaction and tells the bouncers to kick you out of the bar.
You wisely consider the state of your liver. So you re-sign the last transaction with a "final" nSequence of 0xFFFFFFFF i.e. the maximum possible value it can have. This allows the bartender to get his or her funds immediately (nLockTime is ignored if nSequence is 0xFFFFFFFF), so he or she tells the bouncers to let you out of the bar.
Now that of course is a payment channel. Individual payments (purchases of alcohol, so I guess buying coffee is not in scope for payment channels). Closing is done by creating a "final" transaction that is the sum of the individual payments. Sure there's no routing and channels are unidirectional and channels have a maximum lifetime but give Satoshi a break, he was also busy inventing Bitcoin at the time. Now if you noticed I called this kind of payment channel "broken". This is because the mempool rules are not consensus rules, and cannot be validated (nothing about the mempool can be validated onchain: I sigh every time somebody proposes "let's make block size dependent on mempool size", mempool state cannot be validated by onchain data). Fullnodes can't see all of the transactions you signed, and then validate that the final one with the maximum nSequence is the one that actually is used onchain. So you can do the below:
Become friends with Jihan Wu, because he owns >51% of the mining hashrate (he totally reorged Bitcoin to reverse the Binance hack right?).
Slip Jihan Wu some of the more interesting drinks you're ordering as an incentive to cooperate with you. So say you end up ordering 100 drinks, you split it with Jihan Wu and give him 50 of the drinks.
When the bar closes, Jihan Wu quickly calls his mining rig and tells them to mine the version of your transaction with nSequence 0. You know, that first one where you pay for only one drink.
Because fullnodes cannot validate nSequence, they'll accept even the nSequence=0 version and confirm it, immutably adding you paying for a single alcoholic drink to the blockchain.
The bartender, pissed at being cheated, takes out a shotgun from under the bar and shoots at you and Jihan Wu.
Jihan Wu uses his mystical chi powers (actually the combined exhaust from all of his mining rigs) to slow down the shotgun pellets, making them hit you as softly as petals drifting in the wind.
The bartender mutters some words, clothes ripping apart as he or she (hard to believe it could be a she but hey) turns into a bear, ready to maul you for cheating him or her of the payment for all the 100 drinks you ordered from him or her.
Steely-eyed, you stand in front of the bartender-turned-bear, daring him to touch you. You've watched Revenant, you know Leonardo di Caprio could survive a bear mauling, and if some posh actor can survive that, you know you can too. You make a pose. "Drunken troll logic attack!"
I think I got sidetracked here.
Bears are bad news.
You can't reasonably invoke "Satoshi's Vision" and simultaneously reject the Lightning Network because it's not onchain. Satoshi's Vision included a half-assed implementation of payment channels with nSequence, where the onchain transaction represented multiple logical payments, exactly what modern offchain techniques do (except modern offchain techniques actually work). nSequence (the field, but not its modern meaning) has been in Bitcoin since BitCoin For Windows Alpha 0.1.0. And its original intent was payment channels. You can't get nearer to Satoshi's Vision than being a field that Satoshi personally added to transactions on the very first public release of the BitCoin software, like srsly.
Miners can totally bypass mempool rules. In fact, the reason why nSequence has been repurposed to indicate "optional" replace-by-fee is because miners are already incentivized by the nSequence system to always follow replace-by-fee anyway. I mean, what do you think those drinks you passed to Jihan Wu are, other than the fee you pay him to mine a specific version of your transaction?
Satoshi made mistakes. The original design for nSequence is one of them. Today, we no longer use nSequence in this way. So diverging from Satoshi's original design is part and parcel of Bitcoin development, because over time, we learn new lessons that Satoshi never knew about. Satoshi was an important landmark in this technology. He will not be the last, or most important, that we will remember in the future: he will only be the first.
Incentive-compatible time-limited unidirectional channel; or, Satoshi's Vision, Fixed (if transaction malleability hadn't been a problem, that is). Now, we know the bartender will turn into a bear and maul you if you try to cheat the payment channel, and now that we've revealed you're good friends with Jihan Wu, the bartender will no longer accept a payment channel scheme that lets one you cooperate with a miner to cheat the bartender. Fortunately, Jeremy Spilman proposed a better way that would not let you cheat the bartender. First, you and the bartender perform this ritual:
You get some funds and create a transaction that pays to a 2-of-2 multisig between you and the bartender. You don't broadcast this yet: you just sign it and get its txid.
You create another transaction that spends the above transaction. This transaction (the "backoff") has an nLockTime equal to the closing time of the bar, plus one block. You sign it and give this backoff transaction (but not the above transaction) to the bartender.
The bartender signs the backoff and gives it back to you. It is now valid since it's spending a 2-of-2 of you and the bartender, and both of you have signed the backoff transaction.
Now you broadcast the first transaction onchain. You and the bartender wait for it to be deeply confirmed, then you can start ordering.
The above is probably vaguely familiar to LN users. It's the funding process of payment channels! The first transaction, the one that pays to a 2-of-2 multisig, is the funding transaction that backs the payment channel funds. So now you start ordering in this way:
For your first drink, you create a transaction spending the funding transaction output and sending the price of the drink to the bartender, with the rest returning to you.
You sign the transaction and pass it to the bartender, who serves your first drink.
For your succeeding drinks, you recreate the same transaction, adding the price of the new drink to the sum that goes to the bartender and reducing the money returned to you. You sign the transaction and give it to the bartender, who serves you your next drink.
At the end:
If the bar closing time is reached, the bartender signs the latest transaction, completing the needed 2-of-2 signatures and broadcasting this to the Bitcoin network. Since the backoff transaction is the closing time + 1, it can't get used at closing time.
If you decide you want to leave early because your liver is crying, you just tell the bartender to go ahead and close the channel (which the bartender can do at any time by just signing and broadcasting the latest transaction: the bartender won't do that because he or she is hoping you'll stay and drink more).
If you ended up just hanging around the bar and never ordering, then at closing time + 1 you broadcast the backoff transaction and get your funds back in full.
Now, even if you pass 50 drinks to Jihan Wu, you can't give him the first transaction (the one which pays for only one drink) and ask him to mine it: it's spending a 2-of-2 and the copy you have only contains your own signature. You need the bartender's signature to make it valid, but he or she sure as hell isn't going to cooperate in something that would lose him or her money, so a signature from the bartender validating old state where he or she gets paid less isn't going to happen. So, problem solved, right? Right? Okay, let's try it. So you get your funds, put them in a funding tx, get the backoff tx, confirm the funding tx... Once the funding transaction confirms deeply, the bartender laughs uproariously. He or she summons the bouncers, who surround you menacingly. "I'm refusing service to you," the bartender says. "Fine," you say. "I was leaving anyway;" You smirk. "I'll get back my money with the backoff transaction, and posting about your poor service on reddit so you get negative karma, so there!" "Not so fast," the bartender says. His or her voice chills your bones. It looks like your exploitation of the Satoshi nSequence payment channel is still fresh in his or her mind. "Look at the txid of the funding transaction that got confirmed." "What about it?" you ask nonchalantly, as you flip open your desktop computer and open a reputable blockchain explorer. What you see shocks you. "What the --- the txid is different! You--- you changed my signature?? But how? I put the only copy of my private key in a sealed envelope in a cast-iron box inside a safe buried in the Gobi desert protected by a clan of nomads who have dedicated their lives and their childrens' lives to keeping my private key safe in perpetuity!" "Didn't you know?" the bartender asks. "The components of the signature are just very large numbers. The sign of one of the signature components can be changed, from positive to negative, or negative to positive, and the signature will remain valid. Anyone can do that, even if they don't know the private key. But because Bitcoin includes the signatures in the transaction when it's generating the txid, this little change also changes the txid." He or she chuckles. "They say they'll fix it by separating the signatures from the transaction body. They're saying that these kinds of signature malleability won't affect transaction ids anymore after they do this, but I bet I can get my good friend Jihan Wu to delay this 'SepSig' plan for a good while yet. Friendly guy, this Jihan Wu, it turns out all I had to do was slip him 51 drinks and he was willing to mine a tx with the signature signs flipped." His or her grin widens. "I'm afraid your backoff transaction won't work anymore, since it spends a txid that is not existent and will never be confirmed. So here's the deal. You pay me 99% of the funds in the funding transaction, in exchange for me signing the transaction that spends with the txid that you see onchain. Refuse, and you lose 100% of the funds and every other HODLer, including me, benefits from the reduction in coin supply. Accept, and you get to keep 1%. I lose nothing if you refuse, so I won't care if you do, but consider the difference of getting zilch vs. getting 1% of your funds." His or her eyes glow. "GENUFLECT RIGHT NOW." Lesson learned?
Payback's a bitch.
Transaction malleability is a bitchier bitch. It's why we needed to fix the bug in SegWit. Sure, MtGox claimed they were attacked this way because someone kept messing with their transaction signatures and thus they lost track of where their funds went, but really, the bigger impetus for fixing transaction malleability was to support payment channels.
Yes, including the signatures in the hash that ultimately defines the txid was a mistake. Satoshi made a lot of those. So we're just reiterating the lesson "Satoshi was not an infinite being of infinite wisdom" here. Satoshi just gets a pass because of how awesome Bitcoin is.
CLTV-protected Spilman Channels
Using CLTV for the backoff branch. This variation is simply Spilman channels, but with the backoff transaction replaced with a backoff branch in the SCRIPT you pay to. It only became possible after OP_CHECKLOCKTIMEVERIFY (CLTV) was enabled in 2015. Now as we saw in the Spilman Channels discussion, transaction malleability means that any pre-signed offchain transaction can easily be invalidated by flipping the sign of the signature of the funding transaction while the funding transaction is not yet confirmed. This can be avoided by simply putting any special requirements into an explicit branch of the Bitcoin SCRIPT. Now, the backoff branch is supposed to create a maximum lifetime for the payment channel, and prior to the introduction of OP_CHECKLOCKTIMEVERIFY this could only be done by having a pre-signed nLockTime transaction. With CLTV, however, we can now make the branches explicit in the SCRIPT that the funding transaction pays to. Instead of paying to a 2-of-2 in order to set up the funding transaction, you pay to a SCRIPT which is basically "2-of-2, OR this singlesig after a specified lock time". With this, there is no backoff transaction that is pre-signed and which refers to a specific txid. Instead, you can create the backoff transaction later, using whatever txid the funding transaction ends up being confirmed under. Since the funding transaction is immutable once confirmed, it is no longer possible to change the txid afterwards.
Todd Micropayment Networks
The old hub-spoke model (that isn't how LN today actually works). One of the more direct predecessors of the Lightning Network was the hub-spoke model discussed by Peter Todd. In this model, instead of payers directly having channels to payees, payers and payees connect to a central hub server. This allows any payer to pay any payee, using the same channel for every payee on the hub. Similarly, this allows any payee to receive from any payer, using the same channel. Remember from the above Spilman example? When you open a channel to the bartender, you have to wait around for the funding tx to confirm. This will take an hour at best. Now consider that you have to make channels for everyone you want to pay to. That's not very scalable. So the Todd hub-spoke model has a central "clearing house" that transport money from payers to payees. The "Moonbeam" project takes this model. Of course, this reveals to the hub who the payer and payee are, and thus the hub can potentially censor transactions. Generally, though, it was considered that a hub would more efficiently censor by just not maintaining a channel with the payer or payee that it wants to censor (since the money it owned in the channel would just be locked uselessly if the hub won't process payments to/from the censored user). In any case, the ability of the central hub to monitor payments means that it can surveill the payer and payee, and then sell this private transactional data to third parties. This loss of privacy would be intolerable today. Peter Todd also proposed that there might be multiple hubs that could transport funds to each other on behalf of their users, providing somewhat better privacy. Another point of note is that at the time such networks were proposed, only unidirectional (Spilman) channels were available. Thus, while one could be a payer, or payee, you would have to use separate channels for your income versus for your spending. Worse, if you wanted to transfer money from your income channel to your spending channel, you had to close both and reshuffle the money between them, both onchain activities.
Poon-Dryja Lightning Network
Bidirectional two-participant channels. The Poon-Dryja channel mechanism has two important properties:
No time limit.
Both the original Satoshi and the two Spilman variants are unidirectional: there is a payer and a payee, and if the payee wants to do a refund, or wants to pay for a different service or product the payer is providing, then they can't use the same unidirectional channel. The Poon-Dryjam mechanism allows channels, however, to be bidirectional instead: you are not a payer or a payee on the channel, you can receive or send at any time as long as both you and the channel counterparty are online. Further, unlike either of the Spilman variants, there is no time limit for the lifetime of a channel. Instead, you can keep the channel open for as long as you want. Both properties, together, form a very powerful scaling property that I believe most people have not appreciated. With unidirectional channels, as mentioned before, if you both earn and spend over the same network of payment channels, you would have separate channels for earning and spending. You would then need to perform onchain operations to "reverse" the directions of your channels periodically. Secondly, since Spilman channels have a fixed lifetime, even if you never used either channel, you would have to periodically "refresh" it by closing it and reopening. With bidirectional, indefinite-lifetime channels, you may instead open some channels when you first begin managing your own money, then close them only after your lawyers have executed your last will and testament on how the money in your channels get divided up to your heirs: that's just two onchain transactions in your entire lifetime. That is the potentially very powerful scaling property that bidirectional, indefinite-lifetime channels allow. I won't discuss the transaction structure needed for Poon-Dryja bidirectional channels --- it's complicated and you can easily get explanations with cute graphics elsewhere. There is a weakness of Poon-Dryja that people tend to gloss over (because it was fixed very well by RustyReddit):
You have to store all the revocation keys of a channel. This implies you are storing 1 revocation key for every channel update, so if you perform millions of updates over your entire lifetime, you'd be storing several megabytes of keys, for only a single channel. RustyReddit fixed this by requiring that the revocation keys be generated from a "Seed" revocation key, and every key is just the application of SHA256 on that key, repeatedly. For example, suppose I tell you that my first revocation key is SHA256(SHA256(seed)). You can store that in O(1) space. Then for the next revocation, I tell you SHA256(seed). From SHA256(key), you yourself can compute SHA256(SHA256(seed)) (i.e. the previous revocation key). So you can remember just the most recent revocation key, and from there you'd be able to compute every previous revocation key. When you start a channel, you perform SHA256 on your seed for several million times, then use the result as the first revocation key, removing one layer of SHA256 for every revocation key you need to generate. RustyReddit not only came up with this, but also suggested an efficient O(log n) storage structure, the shachain, so that you can quickly look up any revocation key in the past in case of a breach. People no longer really talk about this O(n) revocation storage problem anymore because it was solved very very well by this mechanism.
Another thing I want to emphasize is that while the Lightning Network paper and many of the earlier presentations developed from the old Peter Todd hub-and-spoke model, the modern Lightning Network takes the logical conclusion of removing a strict separation between "hubs" and "spokes". Any node on the Lightning Network can very well work as a hub for any other node. Thus, while you might operate as "mostly a payer", "mostly a forwarding node", "mostly a payee", you still end up being at least partially a forwarding node ("hub") on the network, at least part of the time. This greatly reduces the problems of privacy inherent in having only a few hub nodes: forwarding nodes cannot get significantly useful data from the payments passing through them, because the distance between the payer and the payee can be so large that it would be likely that the ultimate payer and the ultimate payee could be anyone on the Lightning Network. Lessons learned?
We can decentralize if we try hard enough!
"Hubs bad" can be made "hubs good" if everybody is a hub.
Smart people can solve problems. It's kinda why they're smart.
After LN, there's also the Decker-Wattenhofer Duplex Micropayment Channels (DMC). This post is long enough as-is, LOL. But for now, it uses a novel "decrementing nSequence channel", using the new relative-timelock semantics of nSequence (not the broken one originally by Satoshi). It actually uses multiple such "decrementing nSequence" constructs, terminating in a pair of Spilman channels, one in both directions (thus "duplex"). Maybe I'll discuss it some other time. The realization that channel constructions could actually hold more channel constructions inside them (the way the Decker-Wattenhofer puts a pair of Spilman channels inside a series of "decrementing nSequence channels") lead to the further thought behind Burchert-Decker-Wattenhofer channel factories. Basically, you could host multiple two-participant channel constructs inside a larger multiparticipant "channel" construct (i.e. host multiple channels inside a factory). Further, we have the Decker-Russell-Osuntokun or "eltoo" construction. I'd argue that this is "nSequence done right". I'll write more about this later, because this post is long enough. Lessons learned?
Bitcoin offchain scaling is more powerful than you ever thought.
After 3.5years ive found my 100x Chimera $cmra The real $ghost
Market cap circa 100k High risk play What is Chimera? Chimera is an ERC-20 token (Ethereum) that aims to remove the transparency seen in typical Ethereum tokens. The pros and cons for transparency vary from person to person, with some people preferring an asset such as Monero over something like Bitcoin. Chimera is essentially Ethereum's solution to creating an anonymous service on Ethereum's blockchain. Thus, Chimera can be thought of a "private version of Ethereum" - Chimera holds all the capabilities as Ethereum with reduced transparency. Since the development team plans to have Chimera be used as a payment method, it can be seen as a currency. Why buy Chimera? Anyone who is interested in escaping the transparency of the blockchain would benefit from Chimera's technology. Whether you are looking to hide large amounts of funds or to simply stay anonymous, using Chimera's services leaves no paper trails, thus giving benefit to those seeking sanction from taxing authorities (although our team does not endorse this). Chimera tokens can also be used as a form of payment towards services our team will offer in the future. What will Chimera offer to holders? Chimera holders benefit by not being listed under the token contract address when searched on current block explorers. The transactions themselves can only be viewed in raw hexadecimal form and need to be sought out and converted to get the values of transaction functions. This information (commonly displayed for ERC-20 tokens) has been hidden by our token, preventing services such as WhaleWatcher.io from being able to scan the blockchain for large transactions and thus prevents them from posting the information on social media sites. For large coin holders, whale watching services can be trouble. Chimera and its services aim to surpass this hurdle. What incentives does Chimera give? Chimera can be viewed as a private form of Ethereum. It contains all the core functionalities of the Ethereum token and removes the associated transparency. Using Chimera as a currency provides incentives such as secure and anonymous transfers, a store of value over time, and early access to the products and services the Chimera team will be offering. How is this different than any other ERC-20 token? Chimera differs from most ERC-20 tokens in the sense that the token contract will not display the holders or quantities. This means that making a script/tool to collect the information of token holders is much harder to achieve than regular ERC-20 tokens. When Chimera is sent through the Scrambler service, it creates a chain of transactions effectively making the time complexity of a script of software exponential rather than linear. The only "easy to see" transactions are from the initial contract creation, minting, and burning. But wait - can't we still technically see transactions if we look hard enough? While block explorers such as Etherscan typically have trouble displaying the "To" address and amount with our token, it is not completely impossible to trace transactions. While users take part in Chimera's Scrambler, the difficulty of tracing the recipients grows exponentially. As more "middle wallets" are added, the complexity becomes even stronger. What's in store for the future? As of now, the Chimera team has their first main net service working at https://chimera.exchange/scrambler. This service allows you to further conceal a transfer of funds. Future projects include a crypto-based subscription website for content and media creators. Customers will be able to pay in Chimera as well as other major crypto assets to unlock media hosted by a creator, essentially creating the most anonymous subscription space to host your photos and videos. Make sure to check out our News webpage and Twitter for updates! Exchange: Uniswap v1 https://v1.uniswap.exchange/swap Contract: 0x37737ad7e32ed440c312910cfc4a2e4d52867caf 100m total supply. Circ supply is 4.5m https://chimera.exchange/statistics/circulating Useful links https://www.coingecko.com/en/coins/chimera https://etherscan.io/ token/0x37737ad7e 32ed440c312910cfc4a2e4d52867caf https://twitter.com/ChimeraToken https://forkdelta.app/#!/trade/0x37737ad7e32ed440c312910cfc4a2e4d52867caf-ETH https://chimera.exchange Newly incorporated and are now Chimera Digital, Inc based out of Ontario, Canada. See official documentation: Primary focus right now is to finish the last of the security tests for the wallet scramblemixer (now being called Scram!) and a major website redesign. Once they are up and running, they will aggressively apply to dexes to gain as much organic notoriety and liquidity as possible without having to take on any large investors. Whitepaper is being fully reworked atm. LinkedIn profiles for some of team: Lead Developer Alex can be found here: https://www.linkedin.com/in/alex-schwarz-94248269/ and here: https://www.linkedin.com/in/christina-tarpley-b1baa792/ If you look at etherscan you will see the tech working. It will show no transfers. However compare this with uniswap transactions and you will see the real movement. Nice tweet by a good team: https://twitter.com/binanceaudit/status/1266934471674277889?s=19 Federal Corporation Information - 1207567-9 - Online Filing Centre - Corporations Canada - Corporations - Innovation, Science and Economic Development Canada https://www.ic.gc.ca/app/sccc/CorporationsCanada/fdrlCrpDtls.html?corpId=12075679&V_TOKEN=1591294452581&crpNm=&crpNmbr=1207567-9&bsNmbr= Key points to note:
Mixer tech on ether network.
Etherscan can not track real movements due to this. Uniswap info will show transactions though.
Team is only a few months old
Whitepaper is being redesigned.
Website is being redesigned
100k market cap should be looked at as an idea and researched further with their team
Dieter Fishbein, Ecosystem Development Lead, Web3 Foundation
Dan: Hey everyone, thanks for joining us for the Polkadot Launch AMA. We have Dieter Fishbein (Head of Ecosystem Development, our business development team), Logan Saether (Technical Education), and Will Pankiewicz (Master of Validators) joining us today. We had some great questions submitted in advance, and we’ll start by answering those and learning a bit about each of our guests. After we go through the pre-submitted questions, then we’ll open up the chat to live Q&A and the hosts will answer as many questions as they can. We’ll start off with Dieter and ask him a set of some business-related questions.
Dieter could you introduce yourself, your background, and your role within the Polkadot ecosystem?
Dieter: I got my start in the space as a cryptography researcher at the University of Waterloo. This is where I first learned about Bitcoin and started following the space. I spent the next four years or so on the investment team for a large asset manager where I primarily focused on emerging markets. In 2017 I decided to take the plunge and join the space full-time. I worked at a small blockchain-focused VC fund and then joined the Polkadot team just over a year ago. My role at Polkadot is mainly focused on ensuring there is a vibrant community of projects building on our technology.
Q: Adoption of Polkadot of the important factors that all projects need to focus on to become more attractive to the industry. So, what is Polkadot's plan to gain more Adoption? [sic]
A (Dieter): Polkadot is fundamentally a developer-focused product so much of our adoption strategy is focused around making Polkadot an attractive product for developers. This has many elements. Right now the path for most developers to build on Polkadot is by creating a blockchain using the Substrate framework which they will later connect to Polkadot when parachains are enabled. This means that much of our adoption strategy comes down to making Substrate an attractive tool and framework. However, it’s not just enough to make building on Substrate attractive, we must also provide an incentive to these developers to actually connect their Substrate-based chain to Polkadot. Part of this incentive is the security that the Polkadot relay chain provides but another key incentive is becoming interoperable with a rich ecosystem of other projects that connect to Polkadot. This means that a key part of our adoption strategy is outreach focused. We go out there and try to convince the best projects in the space that building on our technology will provide them with significant value-add. This is not a purely technical argument. We provide significant support to projects building in our ecosystem through grants, technical support, incubatoaccelerator programs and other structured support programs such as the Substrate Builders Program (https://www.substrate.io/builders-program). I do think we really stand out in the significant, continued support that we provide to builders in our ecosystem. You can also take a look at the over 100 Grants that we’ve given from the Web3 Foundation: https://medium.com/web3foundation/web3-foundation-grants-program-reaches-100-projects-milestone-8fd2a775fd6b
Q: On moving forward through your roadmap, what are your most important next priorities? Does the Polkadot team have enough fundamentals (Funds, Community, etc.) to achieve those milestones?
A (Dieter): I would say the top priority by far is to ensure a smooth roll-out of key Polkadot features such as parachains, XCMP and other key parts of the protocol. Our recent Proof of Authority network launch was only just the beginning, it’s crucial that we carefully and successfully deploy features that allow builders to build meaningful technology. Second to that, we want to promote adoption by making more teams aware of Polkadot and how they can leverage it to build their product. Part of this comes down to the outreach that I discussed before but a major part of it is much more community-driven and many members of the team focus on this. We are also blessed to have an awesome community to make this process easier 🙂
Q: Where can a list of Polkadot's application-specific chains can be found?
A (Dieter): The best list right now is http://www.polkaproject.com/. This is a community-led effort and the team behind it has done a terrific job. We’re also working on providing our own resource for this and we’ll share that with the community when it’s ready.
Q: Could you explain the differences and similarities between Kusama and Polkadot?
A (Dieter): Kusama is fundamentally a less robust, faster-moving version of Polkadot with less economic backing by validators. It is less robust since we will be deploying new technology to Kusama before Polkadot so it may break more frequently. It has less economic backing than Polkadot, so a network takeover is easier on Kusama than on Polkadot, lending itself more to use cases without the need for bank-like security. In exchange for lower security and robustness, we expect the cost of a parachain lease to be lower on Kusama than Polkadot. Polkadot will always be 100% focused on security and robustness and I expect that applications that deal with high-value transactions such as those in the DeFi space will always want a Polkadot deployment, I think there will be a market for applications that are willing to trade cheap, high throughput for lower security and robustness such as those in the gaming, content distribution or social networking sectors. Check out - https://polkadot.network/kusama-polkadot-comparing-the-cousins/ for more detailed info!
Q: and for what reasons would a developer choose one over the other?
A (Dieter): Firstly, I see some earlier stage teams who are still iterating on their technology choosing to deploy to Kusama exclusively because of its lower-stakes, faster moving environment where it will be easier for them to iterate on their technology and build their user base. These will likely encompass the above sectors I identified earlier. To these teams, Polkadot becomes an eventual upgrade path for them if, and when, they are able to perfect their product, build a larger community of users and start to need the increased stability and security that Polkadot will provide. Secondly, I suspect many teams who have their main deployment on Polkadot will also have an additional deployment on Kusama to allow them to test new features, either their tech or changes to the network, before these are deployed to Polkadot mainnet.
Logan Saether, Technical Education, Web3 Foundation
Q: Sweet, let's move over to Logan. Logan - could you introduce yourself, your background, and your role within the Polkadot ecosystem?
A (Logan): My initial involvement in the industry was as a smart contract engineer. During this time I worked on a few projects, including a reboot of the Ethereum Alarm Clock project originally by Piper M