CryptoURANUS Economics

Anti-AdBlocker

Saturday, July 20, 2019

GisselQuist-Technology_LLC: Cryptocurrency




This is For ReferenceOnly Research and All Below is a Paste and Copy So I do not loose this awesome site information:


Powered by Xilinx Virtex-7 V2000T, V585, or X690T  the HTG-700 is ideal for ASIC/SOC prototyping, high-performance computing, high-end image processing, PCI Express Gen 2 & 3 development, general purpose FPGA development, and/or applications requiring high speed serial transceivers (up to 12.5Gbps).  

Three High Pin Count (HPC) FMC connectors provide access to 480 single-ended I/Os and 24 high-speed Serial Transceivers of the on board Virtex 7 FPGA. Availability of over 100 different off-the-shelf FMC modules extend functionality of the board for variety of different applications.
Eight lane of PCI Express Gen 2 is supported by hard coded controllers inside the Virtex 7 FPGA. The board's layout, performance of the Virtex 7 FPGA fabric, high speed serial transceivers (used for PHY interface), flexible on-board clock/jitter attenuator, along with soft PCI Express Gen 3 IP core allow usage of the board for PCI Express Gen3 applications.
The HTG-700 Virtex 7 FPGA board can be used either in PCI Express mode (plugged into host PC/Server) or stand alone mode (powered by external ATX or wall power supply).











Blog Posts

  • Last-Update:

    Lessons learned while building crossbar interconnects

    Connecting N bus masters to M bus slaves is the task of an interconnect. While many approaches exist, one of the most common FPGA approaches is a crossbar interconnect. This article examines some common features among several crossbar interconnects I've recently built.
  • Breaking all the rules to create an arbitrary clock signal

    Never generate a clock signal using logic! Why not? Let's break this rule today in order to create an arbitrary clock generator and see how things work out for us.
  • Building the perfect AXI4 slave

    Xilinx provides example code which can be used to build an AXI slave from. As we've already seen, this code is broken to the extent that it can be made to violate the AXI protocol. Worse, even when it does work the demo core does not perform well. Here's an example of how to do better.
  • Building a Skid Buffer for AXI processing

    Skid buffers provide an elastic support between pipeline stages, relieving the pressure from combinatorial logic which would otherwise accumulate from one stage to the next.
  • Examining Xilinx's AXI demonstration core

    Vivado has a wonderful capability, whereby it can create a AXI4 IP core for you to build a design off of. Sadly, the core generated by Vivado 2018.3 doesn't pass formal verification. Let's look at some of the problems with it today.
  • Understanding AXI Addressing

    An AXI4 component must three different addressing modes, 8 different sub-word sizes, four different wrapping lengths, and both aligned and to-be-aligned addressing. It's not trivial. This article takes a look at how you can compute the next address in an AXI burst.
  • Project Ideas: PMod AMP2

    Do you have a PMod AMP2? Are you wondering what to do with it? Here are some ideas
  • Applying Formal Methods to the Events of the Resurrection

    When was the last supper? When was the crucifixion? Friday? How about the sabbath? Let's apply formal methods to discover these events
  • The most common AXI mistake

    After formally verifying several AXI-lite slaves, one bug stands head and shoulders above the rest as the most common bug
  • The ZipCPU's Interrupt Controller

    The ZipCPU has only a single interrupt line. For many microprocessor applications, this is way too few. Therefore, let's discuss how to build a simple interrupt control peripheral that can then give the ZipCPU access to more than just the one interrupt
  • Logic usage and decoding return results with cascaded multiplexers

    How your CPU or bus aggregates return values from its components, can have an affect on your logic usage
  • Building a universal QSPI flash controller

    In this article, I'll discuss how to build a QSPI flash controller in Verilog, and then make sure it works under all configurations. As always, formally verified example code is provided.
  • Introducing the ArrowZip ZipCPU design, featuring the Max-1000

    The Max-1000 is a very small and cheap FPGA development board from Trenz, and sold by Arrow in the US for only $30. Today, let's take a an example design that runs the ZipCPU on this board.
  • Using Sequence Properties to Verify a Serial Port Transmitter

    Formally Verifying a serial port makes a great example of both the good and bad about SystemVerilog sequences, and how you can still work around the bad with SymbiYosys
  • Why does blinky make a CPU appear to be so slow?

    If your CPU runs at 100MHz, what speed would you expect it to be able to blink an I/O pin at? Let's take a look.
  • Debugging a CPU

    This is the story of finding and fixing a bug in the ZipCPU. As with most bugs, the bug I found wasn't where I expected it. Along the way, though, we'll go over several tools you can use to accomplish such a task--should you ever find you need to do so yourself.
  • Building a custom yet functional AXI-lite slave

    Some time ago, I wrote on this blog about how to verify an AXI-lite slave, showing along the way how Xilinx's demonstration slave wouldn't pass a verification test. Instead of illustrating the problem again, let's take a moment to examine how to build an AXI-lite slave that will not only work, but have twice the throughput.
  • ZipCPU highlights from 2018

    A quick summary of the highlights of the ZipCPU blog over 2018, to include a list of the most read articles
  • Using a formal property file to verify an AXI-lite peripheral

    A file of formal properties defining an interface is worth gold: you can get a strong guarantee that your code will conform to the interface if it passes a formal verification step using the interface. Even better, one such file, used across an enterprise, can guarantee that all of the cores within the enterprise are interface compatible.
  • AutoFPGA's linker script support gets an update

    AutoFPGA is a very powerful scripting tool for composing ad-hoc System on a Chip (SoC) designs. Today it gets an update for handling linker scripts.
  • Makefiles for formal proofs with SymbiYosys

    Building a make script to verify multiple configuration options using SymbiYosys can be done very easily. Let's take a quick look and see how that might be done.
  • Swapping assumptions and assertions doesn't work

    Some time ago, I blogged about how to go about aggregating subcomponents together into a larger design. While I've used the technique often with great success, this article shares a counter example that renders the approach invalid.
  • Building a video controller: it's just a pair of counters

    Building a video display can be a fun beginners exercise: at its fundamental core, it just consists of a pair of counters. This article will examine the lower level component of a video display controller for a VGA display.
  • Accessing the registers of a SoC+FPGA

    Accessing the memory mapped registers connected to a CPU-attached FPGA is usually easy to do. However, if you are doing this from within a Linux system, across a virtual memory interface, then there are a couple more steps involved. The result is still fairly simple.
  • Taking a look at the TinyFPGA BX

    The TinyFPGA BX offers a new approach to the classic FPGA loading problem. Let's take a look at this board and see what it offers.
  • To my new readers and my new twitter followers, welcome!

    I've recently acquired several new twitter and blog feed followers. Today, I'd like to take a moment to welcome them, and let them know what they can expect from the ZipCPU blog.
  • An Open Source Pipelined FFT Generator

    Not having an open source FFT implementation can make simulating DSP algorithms with an open source simulator such as Verilator nearly impossible. Now there's a highly configurable open source alternative. Better yet, this alternative has been formally verified. We'll discuss that FFT, and how the formal verification was accomplished, here.
  • It's time for ORCONF 2018!

    ORCONF 2018 will be held this weekend in Gdansk, Poland. I look forward to meeting many of you there. Here's the abstract of what I intend to present this year.
  • My design works in simulation, but not in hardware. Can formal methods help me?

    Formal methods are traditionally viewed as a design tool to be used before implementation. Today, let's take a peek at a recent example where formal methods were able to help me after implementation.
  • Handling multiple clocks with Verilator

    If you look through the Verilator on-line documentation, you'll notice that all of the examples use a single clock only. Verilator is more capable than that, so let's try to fill in that gap today. This article takes a quick look at how you might handle multiple clocks within Verilator.
  • RE: Building a simulation for my design? What does that mean?

    A student recently asked me what I meant by simulating a design. To answer his question and encourage others, let's spend a moment and look at some examples of what you can do with simulation. I'll also offer several links to other blog posts showing you how to do many of these things.
  • How to build a SPI Flash Controller for an FPGA

    I've now written several (Q/D)SPI flash drivers, and just recently had the opportunity to build another. Here I present the design decisions, the design, and even the formal verification of this new core.
  • Reasons why Synthesis might not match Simulation

    I now recommend simulation to anyone doing HDL design. It's can even be faster to run and debug a simulation then actual hardware. However, there are plenty of times when simulation doesn't match reality. Let's enumerate some of the reasons why simulation might not match hardware performance.
  • Why I like Formal: the ZipCPU and the ICO board

    Recently, I had to move logic from one clock to another in order to fit the ZipCPU onto the ICO board. Having a set of formal properties for the ZipCPU, properties that covered this change, gave me a strong confidence when making the change that the result would still work.
  • What does Formal Development look like in Practice?

    I just built a basic, simple SPI controller last night, using formal tools along the way. Care to read what the development was like?
  • Formally Verifying Memory and Cache Components

    There's a necessary but basic trick necessary when formally verifying something that acts like or interacts with memory, and it's not all that hard to do. In this article, I'll present that basic trick and show how to formally verify a block RAM device.
  • Crossing clock domains with an Asynchronous FIFO

    A two or three clock synchronizer works great for passing small amounts of information across clock domains. If you need to pass more information, such as a full data stream, you will need an asynchronous FIFO. This article examines the Asynchronous FIFO designed by Cliff Cummings, applying formal methods to it to see if it truly maintains the properties he discusses.
  • Formally Verifying Asynchronous Components

    There's a very small bit of trickery required to formally verify an asynchronous design using yosys. Once you know the trick, it becomes easy to set up the properties necessary to formally verify any asynchronous design. In this article, we'll demonstrate this principle by formally verifying a clock switch.
  • A Slow but Symmetric FIR Filter Implementation

    The cost of an FIR filter is usually measured by the number of multiplies required to calculate an output. If you want to implement a better filter, you only need to be able to afford more multiplies. However, if the filter is symmetric, and most FIR filters are, then a little cleverness will allow you to implement the same filter with half as many multiplies.
  • Updated Projects List

    Just a quick note to let everyone know I updated my projects page.
  • Aggregating verified modules together

    Aggregating multiple modules together to formally verify a larger whole can be a very difficult challenge. While I am by no means the expert on this topic, I can at least share some lessons I've learned myself.
  • ZipTimer: A simple countdown timer

    When learning Formal Verification, it helps to start with the simplest designs possible. The ZipTimer is just about that simple: it is nothing more than a programmable countdown timer. More than that, though, it's a usable and critical component of the ZipSystem. Today, let's examine that timer and then formally verify it.
  • Formally Verifying an Asynchronous Reset

    It's one thing to synchronize reset logic within your code, its another to formally prove that your reset synchronizing logic works. This article takes a look at an example reset synchronizer, and then applies SymbiYosys to formally verifying that it works.
  • What would you like to see on the ZipCPU blog?

    It seems there are more topics to post about then there is time to post or to read them. Hence, it's time to ask my Patreon sponsors what topics they'd be interested in reading about next, and thus where my focus should be for the next couple of months. If you are not a blog sponsor, please consider yourself invited to become one!
  • Will formal methods ever find a bug in a working CPU?

    I've now turned my attention to formally Verifying the ZipCPU. Having used the ZipCPU for several years, do you think I'll find any errors within i?
  • Resurrection Day!

    Today is the day Christianity celebrates the resurrection of Jesus Christ. Please join me in reflecting on what makes Jesus different.
  • Quadratic fits are entirely inappropriate for DSP

    If you ever need to estimate a signal's value between samples points, don't use a quadratic fit. There are much better techniques out there which don't suffer from the discontinuities and high frequency distortions associated with a simple quadratic fit. Want to see an example?
  • Pipelining a Prefetch

    We've already discussed the simplest of the ZipCPU's several prefetch modules. Today's discussion focuses on another module that's nearly as simple, but yet can achieve much better performance.
  • Is formal really all that hard?

    There seems to be a myth that formal verification is very difficult, and that it is only used by the smartest digital designers. Let me take a moment in this article to dispel that myth: If you are smart enough to do digital design, then you will appreciate the benefits of formal verification
  • An Exercise in using Formal Induction

    Passing N steps of a formal bounded model check isn't nearly as hard as proving a design works for all steps. This post explores some of the differences, and offers some explanations for those new to formal methods.
  • Want to use ZBasic? Let's have some fun--no actual FPGA required!

    The ZBasic distribution is a very basic ZipCPU distribution that has full Verilator support for all of its peripherals: flash, serial port, and an (optional) SD-card. Want to play a game?
  • Debugging a Cyclone-V

    I just delivered my first design using the Cyclone-V. It was a new experience for me, and I'd like to share some lessons learned in debugging.
  • ZipCPU toolchain and initial test

    This article discusses how to clone the ZipCPU repository from github, and then build the compiler and toolchain. The toolchain is then proven using the basic simulation test program that comes with the ZipCPU repository.
  • Updating ZipCPU files

    I'll admit, I've enjoyed formal methods so much I've started formally verifying much of the ZipCPU repository. Here's a quick status update of what's been accomplished.
  • Interpolation is just a special type of convolution

    One of the more profound DSP lessons I ever learned was that most practical interpolators can be understood as convolutions. This is important because it means that interpolation function have frequency responses, and that their performance can be understood by examining this response.
  • A Quick Introduction to the ZipCPU Instruction Set

    If you've ever wanted to examine a minimalist, yet still powerful, CPU's instruction set, then you might wish to take a peek at the ZipCPU's ISA. If you've ever wanted to program the ZipCPU in assembly, or evaluate or understand an assembly representation of a ZipCPU program, then read along and see the basics of the ZipCPU instruction set.
  • Top 10 ZipCPU blog posts for 2017

    In the spirit of all good New Year's blog posts, here's a quick list of the top ten blog posts on ZipCPU.com from this last year.
  • A better filter implementation for slower signals

    All of the filter implementations we've presented so far are high speed implementations--appropriate for signals at or close to the system clock rate. These implementations, however, end up being very resource expensive when all you want to do is to filter a much slower signal--such as an audio signal. This post, therefore, presents an alternative that is more resource efficient for audio signals.
  • Mystery post: The ugliest bug I've ever encountered

    For someone who has been debugging software for many years, this bug caught me by surprise. I'd never seen anything like it, and had no idea where to look to find the problem. Care to see if you can guess what it was? (Solution at the end.)
  • Arrow's Max-1000: A gem for all the wrong reasons

    I recently purchased a MAX-1000 development board from Arrow. It's a nice, small, FPGA development board for anyone interested low price. In the process, however, I discovered some amazing things about the FTDI FT2232H chip on board.
  • Building a Simple Logic PLL

    Phase-Locked Loops are components designed to lock an oscillator to the phase and frequency of an incoming oscillator. In this article, we'll present a very basic PLL algorithm that can, at high speed and within an FPGA, lock onto the phase of an incoming logic signal.
  • Building a Numerically Controlled Oscillator

    A Numerically Controlled Oscillator (NCO) plus a Digital to Analog (D/A) converter creates a Direct Digital Synthesizer (DDS)--something that can create a tone of any user-controlled frequency. Let's skip the D/A today, and discuss how to drive a sine wave generator to create that known frequency.
  • Testing the fast, generic FIR filter

    The last filter we presented was a high speed, generic, reconfigurable, FIR filter that can be used for many purposes. Since then, we've been working our way towards a framework for testing that filter. Today, let's build that test bench from the framework we've developed and see how well our filter actually works.
  • Thank you!

    O give thanks unto the LORD; for He is good!
  • Measuring the frequency response of a filter under test

    Our generic filtering harness development stopped short of measuring the frequency response of a test filter. Here, we pick back up the discussion and work through how you might measure the frequency response of a filter under test using Verilator.
  • Building a prefetch module for the ZipCPU

    The pre-fetch module is one of the fundamental components of any CPU. It is responsible for fetching instructions from memory. The ZipCPU prefetch is also an example of a Wishbone master, something worth looking at again in and of itself. This post adds a twist, though, to those two topics in that we'll also formally prove that this prefetch algorithm properly accesses the Wishbone bus.
  • Generating more than one bit at a time with an LFSR

    The typical LFSR development ends with logic that can create one bit per clock. What happens when you need many bits per clock, not just one? So let's continue our discussion of LFSRs and investigate how to calculate many LFSR bits per clock.
  • An example LFSR

    To many people, LFSRs magically produce random numbers. They are a confusing unknown. So let's look at an example 5-bit LFSR, and see what happens when we step through its logic.
  • A Configurable Signal Delay Element

    Many DSP applications have a need to delay a signal against itself by some period of time. Such delays are fundamental. They are also fairly easy to build.
  • Building Formal Assumptions to Describe Wishbone Behaviour

    The most critical component of any bus based system, such as a System on a Chip (SoC), is the bus interface. One failure of this interface can easily lock up the entire system. This post examines the Wishbone bus interface, and presents some formal properties that can be used to verify that a Wishbone master works.
  • The Interface to a Generic Filtering Testbench

    As we work our way through discussing digital filtering, and presenting multiple digital filters, we're going to need to test these filters. This article outlines, from the bottom up, a test harness that can be used to aid testing whether or not a digital filter produces the response one would desire.
  • Good Software Engineering Principles Apply to Students Too

    Just because you'll be turning in a one-time project for your class, doesn't mean you can ignore good software engineering principles. Those same principles might be the difference between getting your project working or not.
  • Generating Pseudo-Random Numbers on an FPGA

    At some point or other, when working with FPGAs, you will need a pseudorandom number sequence. Linear Feedback Shift Registers are commonly used for this purpose. Here, we discuss such registers and how to create them within Verilog.
  • Some Simple Clock-Domain Crossing Solutions

    Crossing clock domains is one of those FPGA design topics that is strictly a hardware topic. By the time a software engineer starts his work, any CDC issues have likely been resolved. Not so for the FPGA designer. Let's examine several methods for crossing clock domains.
  • My first experience with Formal Methods

    I've just started trying formal verification methods based upon yosys and yosys-smtbmc this week. As a result, I've now found several subtle bugs within my FIFOs, things that I would never have found otherwise. This post shares some of my initial thoughts and experiences, as well as providing a short primer to the method.
  • Just some notes to new readers of the ZipCPU blog

    If you've just started reading the ZipCPU blog, welcome! Let's take a look at some upcoming topics.
  • Implementing the Moving Average (Boxcar) filter

    A fully generic filter can be difficult to implement within an FPGA, since FPGAs can only support a limited number of multiplies. One way of simplifying the problem is to use a moving average filter. Let's examine how to build one of these filters.
  • FPGAs vs ASICs

    While I like to lump both FPGA and ASIC development into a catch-all phrase 'digital logic', there are some very real differences between the two. Let's examine some of those differences together.
  • It's all about the interfaces

    If you want raw algorithmic speed, look no farther than an FPGA. However, before you start drooling over how fast an FPGA can run a task, take a moment to think about what it will take to get your data in and out of the FPGA at the speed you want the FPGA to run.
  • Using AutoFPGA to connect simple registers to a debugging bus

    Let's take a look at what it takes to add a simple, single-register component to an AutpFPGA based design. We'll look at and examine some simple peripherals, and look at how the components configuration file tells AutoFPGA how to connect the component to the rest of the design.
  • A Brief Introduction to AutoFPGA

    Many of my readers are aware that I am working on a project I've called AutoFPGA. AutoFPGA makes it easy to reconfigure a bus and reassign addresses when adding new components to a design. This post presents a high level overview of how AutoFPGA may be used.
  • A CORDIC testbench

    Building a test bench for a CORDIC with an arbitrary number of bits, both input, output, and phase bits, is not a trivial task. However, without knowing how good a component should be, it's hard to know whether or not the component works to its specification.
  • A Cheaper Fast FIR Filter

    After I last posted on how to build a generic FIR filter, a friend showed me a cheaper implementation. This post presents and examines that cheaper implementation.
  • Understanding the effects of Quantization

    If you are building DSP algorithms within FPGAs or other digital logic, it's important to know how your logic will handle finite bit arithmetic. This post just goes over some of the basic effects of quantization: what it is, and some simple means of modeling it to determine how it will affect your algorithm.
  • Clocks for Software Engineers

    If you have a software background, and you want to pick up digital design, then one of the first things you need to learn about is the clock. To many software engineers, the concept of a clock is an annoyance. Without using a clock, they can turn HDL into a programming language. Yet the clock they are ignoring is often the most fundamental part of digital design.
  • Demonstrating the improved PWM waveform

    Having posted on an improved form of Pulse Width Modulation, I've been asked to provide a demonstration of this capability illustrating that this technique actually works. So today we'll discuss the technique again and present performance measures showing how well this method of signal generation outshines its traditional PWM counterpart. Sample code is provided, so you can test it for yourself.
  • Building a high speed Finite Impulse Response (FIR) Digital Filter

    Digital Filtering is one of the most fundamental DSP operations. Further, because of their speed, FPGAs can filter things that nothing else can. This post will develop a simple, extensable, generic high speed re-programmable digital filter.
  • Even I get stuck in FPGA Hell

    Yes, even I get stuck in FPGA Hell from time to time. Here's a quick discussion of three problems where I got stuck recently: HDMI input, getting the debugging bus up and running, and an arbitrary clock rate generator. In each case, I present not only how I was stuck, but also how I got unstuck.
  • Glad I went to ORCONF

    My thanks go out to the ORCONF team for making this years conference a success!
  • Off to ORCONF-2017!

    This week, I'm off to ORCONF-2017 in Hebden Bridge, England. I'll be giving a presentation on AutoFPGA, and a quick update on the ZipCPU development.
  • Reinventing PWM

    A PWM output can often be used as a poor man's low-frequency digital to analog converter. Such outputs are so easy to create, that they often make sample problems for beginners. Here, we'll not only show an example of the beginners solution, but we'll also create a simple no-cost improvement that can be applied for audio signals.
  • Big Money Engineering Integrity

    This article is a true story of what happens when engineering integrity is lost at the big money government level. The result wasn't pretty.
  • CORDIC part two: rectangular to polar conversion

    The CORDIC algorithm we discussed can be used in more than one fashion. We've now discussed how to use it to calculate sine and cosine functions. Today, let turn the algorithm around and use the same method to generate polar coordinates from rectangular inputs--essentially the reverss of the last operation.
  • Using a CORDIC to calculate sines and cosines in an FPGA

    Having presented several simple means of calculating a sinewaves within an FPGA, we turn to a more powerful method today: the Coordinate Rotation Digital Computer, or CORDIC. Although this method has a higher latency than the two table based lookup methods, it also has the capability for much greater precision than either table method can provide.
  • Building a quarter sine-wave lookup table

    Since we've already discussed how to build a simple sine wave lookup table, as well as several general strategies for controlling pipeline logic, let's take a look at creating a sine wave from a quarter wave table. We'll also use this as an opportunity to discuss how to create pipelined logic in general.
  • Debugging your soft-core CPU within an FPGA

    We've already looked at the requirements for debugging a CPU in general, as well as how to debug a CPU in simulation. Let's now take a look at how to modify your soft-core CPU so that you can debug it when it is on an FPGA.
  • The ZipCPU's pipeline logic

    Having discussed several strategies for pipelining in general, we turn our attention to the strategy used for handling pipelining within the ZipCPU. Hence, we present the pipelining logic used by the ZipCPU, as well as the variable names you can search on in case you want to see in detail how a CPU can handle its pipeline logic.
  • Rules for new FPGA designers

    This year many students will try to take up digital design. Some of these students will enjoy their experience, many will not. Here are some tips to help keep you out of trouble, so your experience will be one of the more enjoyable ones.
  • Two of the Simplest Digital filters

    The simplest digital FIR filter out there is a simple adjacent sample averager. Here we present not only that filter, but also discuss how any Digital filter may be tested and proven.
  • Strategies for pipelining logic

    Pipelining logic is one of the most basic digital logic concepts. Many processing algorithms can naturally be pipelined--reducing logic and speeding up algorithm completion. However, most pipelines require some form of handshake signals. This post, therefore, discusses those handshaking signals, presenting several options that can be used depending upon the circumstances.
  • What would cause you to lie?

    Engineering integrity should not need to be discussed on any engineering forum. The honesty of every engineer should be assumed. That this is not the case, and that this needs to be discussed is unfortunate. It is, however reality. So, let's ask, what would it take for you to compromise your integrity?
  • A Simple ALU, drawn from the ZipCPU

    When it comes to building a CPU, an ALU may be the simplest part. This discussion examines how simple an ALU can be made to be, by examining the ALU within the ZipCPU.
  • Series: Debouncing in Digital Logic

    This completes our series on button bouncing, and the logic necessary to both measure and to eliminate button bouncing.
  • Using a debug-bus to Measure Bouncing

    While many other FPGA web sites discuss contact bounce and how to get rid of it, let's take a different approach here. Let's combine our debouncer with our measurement code, connect it to our debugging bus, a get a trace from within the FPGA indicating what was taking place.
  • Measuring Contact Bounce

    Now that we know that buttons don't behave like we would like, what would it take to measure that behavior? Let's measure not only the number of times a button changes, but also how long it takes from the initial change to the final change.
  • How to eliminate button bounces with digital logic

    Unilke LEDs, pushbuttons have a series of problems associated with them that make them difficult to use as part of debugging a design. They can be useful, but only after your debouncing logic has first been proven
  • Visualizing Contact Bounce

    Buttons when pressed often report more than one contact, or even more than one release. This post presents the result of measuring several such bounces.
  • ZipCPU Advertising

    Disqus support has been removed, since their advertising was not consistent with my strong Christian scruples. The ZipCPU blog is not, nor has it ever been, supported by advertising.
  • Writing your own VCD File

    If you ever decide you want to create your own scope, but not your own viewer, than knowing how to write a Value-Change Dump (VCD) file may be required. Here, we'll go over the basics of how to write such a file, as well as discuss the meanings of the most common parts of one.
  • Linear Interpolation

    An Overview of the Linear Interpolation Series
  • Getting the basic FIFO right

    A FIFO is a very basic component of any digital logic system. Getting the components and the timing right, though, can be a careful chore. Here, let's examine how to build a basic FIFO.
  • Windows FPGA designers may not need a Linux machine ... yet

    Many of the programs I use for FPGA design and debugging, such as verilator or GTKWave, run just fine under Windows when using Cygwin. Here's how to set up some Linux FPGA tools under Windows.
  • How to build a simulation based debugger for your own soft-core CPU

    While Verilator makes for a great simulator, gtkwave isn't the most intuitive way to debug a CPU. Rather than staring at incomprehensible wires, give your simulator the feel of a proper debugger using these techniques
  • How to Debug a DSP algorithm

    DSP algorithms are not like other algorithms when it comes to debugging. printf() and gtkwave just don't work as well. Let's look into an alternative.
  • Rounding Numbers without Adding a Bias

    If every operation adds to the number of bits required to represent the result, how do you get rid of bits? It's not nearly as simple as it sounds, since most of the methods for getting rid of bits bias the result one way or another. Here we'll examine a couple rounding methods, and discuss their problems, and also describe a solution.
  • Bit growth in FPGA arithmetic

    Integer arithmetic from a small domain, creates larger and larger numbers. Here, we'll quantify that effect.
  • A Basic Upsampling Linear Interpolator

    This blog article is the second in a series on rate conversion within DSP's. Specifically, we'll look at how to upsample an incoming signal from whatever rate it was given to you at, on up to any rate at or less than your FPGA's clock rate.
  • Verilator doesn't find everything (today)

    After posting the debugging bus stories, I was embarrassed to implement it on my own FPGA and not get immediate and perfect success. Verilator just doesn't find everything (today).
  • Design Needs when Debugging a SoftCore CPU

    There's more to designing a CPU than picking the instructions that the CPU must support. This blog post discusses the debugging facilities you are likely to want while you work to bring your design to fruition.
  • The simplest sine wave generator within an FPGA

    If you find yourself needing a sine wave within an FPGA, here's the simplest method(s) I know of creating one.
  • Getting Started with the Wishbone Scope

    This post describes how to get started with the wishbone scope in your own design. As a fun end result, we'll draw the information necessary to create a VCD file and thus a GTKWave plot from logic within your design
  • Finishing off the debugging bus: building a software interface

    This post completes the sequence on what it takes to build a debugging bus, by building a software controller to encode commands for and decode responses from the FPGA. Once built and integrated into your design, the dbgbus controller should be able to help you communicate with components within your FPGA
  • Why you want a debug port into your FPGA

    Just a quick picture of what you can do with the dbgbus once finished
  • Simulating an FPGA through the debugging interface

    Given the debugging interface just created, this post goes into how to go about simulating it via Verilator
  • My own FPGA debugging philosophy

    Many individuals have read my previous posts and have wondered what my design philosophy actually is. This post attempts to outline the general approaches I used to debugging my own FPGA designs
  • Building a very simple wishbone interconnect

    Having now built all of the components of a UART to wishbone bridge, it's time to build a test design that would use it. This article, therefore, discusses how to build the interconnect that will connect a single wishbone master to multiple wishbone slaves
  • Taking a New Look at Verilator

    Verilator is not a simulator in the sense of any of the other commercial HDL simulators on the market, yet it has some very unique capabilities when it comes to simulating components that you won't find in other simulation tools
  • Putting our Debugging Bus RTL Components Together

    We've now built all the individual components of an RTL based debugging bus. This post discusses how to put them all together.
  • Sending bus idle notifications down the line

    One difficult part of dealing with multiple serial interfaces is knowing which one has what port on it. We'll solve this problem on our FPGA debugging interface by adding a simple idle indication into our debugging port. With this capability, if we watch long enough, we can tell if the port is the right port or not.
  • Why Use a Network Interface to your FPGA

    Several of you have asked why the debug interface needs to be networked. What does that mean? and, is it worth the pain of a capability I don't think I need? This article discusses what it takes to network a debugging interface, therefore, and outlines why it isn't as difficult to do as it might sound.
  • Support me on Patreon

    The ZipCPU blog now has Patreon support! If you'd like to see this blog continue ...
  • The debugging bus: a goal for FPGA interaction

    We're now halfway through describing how to build a debugging bus within an FPGA for command, control, and feedback from that FPGA. This post takes a quick review of why we wish to do this.
  • Adding interrupt reporting to our debugging bus

    Now that we have a mostly working bus, let's add interrupt reporting as a simple feature to it
  • How to send our bus results back out the serial port

    We're close to having a working demonstration debug port to our design, but not quite there yet. This lesson focuses on how to turn the output words from our hexadecimal bus back into characters that we can then read on the output.
  • No PI for you

    Neither the units of degrees nor Radians make sense within an FPGA. This article discusses a better unit for angles within an FPGA.
  • How to create bus command words, from a 7-bit data stream

    Continuing our series on how to make a debugging bus, this article discusses how you can create bus command words from a stream of printable bytes.
  • Minimizing FPGA Resource Utilization

    At some time, every project will come face to face with the fact that FPGA resources equal dollars. Keep your dollar commitment small. Use the techniques in this post to keep your resource usage to a minimum.
  • A College Student's Response to the FPGA Design Process

    When I wrote the blog article about the FPGA design process, and how it differed between students, experts, and reality, one particular student's experiences were fresh in my mind. Here, he writes about his experiences from his own perspective.
  • Building a Simple Wishbone Master

    A discussion of how to build a simple bus master, such as you might wish to use to debug a wishbone-based system
  • Building A Simple In-Circuit Logic Analyzer

    Building your own in-circuit logic analyzer is a whole lot easier than it sounds
  • Nearest Neighbor Interpolation

    A simple presentation of how to handle resampling via a nearest-neightbor interpolation scheme.
  • An Overview of a Wishbone-UART Bridge

    I'd like to describe how to control a wishbone bus from an external command and control port. It's not that simple. This article discusses instead how one such approach works, decomposing the parts and pieces of it. It then outlines what a simplified control port structure might look like.
  • Campus Sidewalks and FPGA Design

    Sometimes you need to build something to fill a gap, before you know what to build. Here's an example.
  • Controlling Timing within an FPGA

    Every FPGA design needs to carefully control the timing of events. Here, we'll explore several ways to control timing within your design.
  • The Actual FPGA Design Process

    There seems to be a disconnect between the FPGA design process used by experts, and the students who request help from the online forums. This post examines that disconnect, pointing out the detail that's often missed.
  • Building a simple wishbone slave

    Bus slave interaction is actually fairly easy. Let's walk through an example wishbone bus slave and look at how it works.
  • Bus Select Lines

    If you want 8-bit access to a 32-bit bus, you'll need to incorporate the bus select lines into your logic. See how it's done here.
  • FFT debugging

    If you find you need to debug an FFT and that you are struggling to do so, the answer is that you need to go back to the basics of engineering. Working from the basics, debugging either an FFT or any other block will become straight-forward.
  • Debugging an FPGA through the serial port--first steps

    If you have a serial port, how might you use it to get information from your FPGA? Can you use it to help debug the rest of your design?
  • That first serial port: Debugging when you are blind

    A serial port can be a very useful way to get information from an FPGA. How can you avoid FPGA Hell when you are trying to get that first serial port up and running?
  • Building a simple bus

    For this article, we'll discuss the logic necessary to implement a very simple bus slave.
  • Moving to memory

    Blinking LEDs is a fun exercise, but eventually you will need to learn to walk to grow up. Within FPGA's, that means you'll need to learn how to deal with memory.
  • A Vision for Controlling FPGA Logic

    My approach to controlling and debugging an FPGA seems to be unique among those I share it with. Here I describe that approach for you, as a vision for where we might go here.
  • Which comes first: the CPU or the peripherals?

    Not whether or not the chicken or the egg came first, but in digital design which comes first: the CPU or the peripherals?
  • Knight Rider

    Knight Rider's car: KIT's LEDs can be a fun twist on a beginners first FPGA design
  • FPGA Hell

    FPGA Hell is where your design doesn't work, and you don't know why not. Here, we'll discuss basic approaches to avoiding FPGA Hell.
  • Blinky

    Your first FPGA design -- blinking an LED
  • Most common Digilent FPGA support requests

    After watching Digilent forum support requests for a year, they start to repeat into these categories
  • Cannot be done

    Never underestimate someone's creativity to make things work outside of spec
  • Welcome to the ZipCPU blog!

subscribe via RSS







  • ZipCPU

  • 123
    Ref-Source: FPGA Metastability Solutions







    Gisselquist Technology recently posted a good blog article about metastability and common solutions. If you are trying to learn FPGAs, you’ll want to read it. If you know a lot about FPGAs already, you might still pick up some interesting tidbits in the post.

    Don’t let the word metastability scare you. It is just a fancy way of saying that a flip flop can go crazy if the inputs are not stable for a certain amount of time before the clock edge and remain stable for a certain amount of time after the clock edge. These times are the setup and hold times, respectively.
    Normally, your design tool will warn you about possible problems if you are using a single clock. However, any time your design generates a signal with one clock and then uses it somewhere with another clock, metastability is a possible problem. Even if you only have one clock, any inputs from the outside world that don’t reference your clock — or, perhaps, any clock at all — introduce the possibility of metastability.




    What’s even worse is that a design can work most of the time and only hit a set up or hold violation occasionally. For example, an input connected to a push button might work nine times out of ten, but then on the tenth time, the button push just happens to sync with a clock edge. What will the flip flop do? It could adopt a level that is neither a zero or a one, or it could oscillate back and forth.
    We’ll let you read about the solutions yourself. However, if you want our take on it, we talked about metastability as part of a series about flip flops. You can also see the video below about real life occurrences. If you want to learn more basics about flip flops, you might want to start with the first post in that series.



    123

    Friday, July 19, 2019

    Paul-Le-Roux Satoshi-Nakamoto Criminal-Mastermind

    Paul Le Roux is Satoshi Nakamoto A Criminal Mastermind





    Satoshi Nakamoto, Bitcoin’s pseudonymous and enigmatic creator, has not been seen online in more than eight years. Evidence has now surfaced that points to a new Satoshi candidate, whose known life has a number of parallels with that of Bitcoin’s inventor. 

    His name is Paul Le Roux and, if proven to be Satoshi, there is a good reason why his over 1 million BTC hasn’t moved as a whale and the Rhodesian has been in jail since 2012.


    Also read: Blockchain Researchers Mock Craig Wright’s Unsealed Bitcoin Address List

    Craig Wright, Paul Le Roux, and the Badly Redacted Document

    The Kleiman v. Wright lawsuit unfolding in the Florida courts has been filled with misdirection, red herrings, mistruths, forgeries, and bizarre theories, often floated by the defendant Craig Wright.

    Please read Document 187.
    “Dr. Craig Wright’s Motion For Protective Order,” been filed with heavy redaction.

    Mr. Wright supposedly, “lives in well-founded vigilant fear these murderous criminals and their associates enact violent retribution if they learned of his involvement in their apprehension and incarceration.”



    Someone forgot to redact one of the corresponding footnotes, however, enabling a sharp-eyed sleuth to identify the master criminal in question: Paul Le Roux.

    The 46-year-old cartel boss is a character as flamboyant as Wright himself, but cut from a very different cloth.

    Many are familiar with Le Roux’s life story as a counter-informant used by multiple U.S.government agencies that kept him out of federal prison.

    A small fraction of this profile surfaced in a seven-part series on Atavist and subsequent book titled “The Mastermind.”

    As the blurb summarizes:
    He was a brilliant programmer and a vicious cartel boss, who became a prized U.S. government asset.

    Now uncovered Paul Le Roux signatures Satoshi Nakamoto electronic signature tracked back to him via amateur cybersecurity and professionals

    Craig Wright has possession of encrypted hard storage DATA containing Le Roux’s multi-billion-dollar stash of bitcoins.

    This is not a crazy whale theory, but fact.

     This is a prima facie case for Bitcoin’s mastermind being criminalizing mastermind Le Roux.


    A young criminal mastermind Le Roux.


    Paul Le Roux Built a Criminal Empire – Who Built Bitcoin!

    His Wikipedia page that escaped redaction in the Kleiman v. Wright case – notes, “Paul Calder Le Roux is a former programmer, former criminal cartel boss and informant to the US Drug Enforcement Administration (DEA) and other multitier U.S.government agencies.

    Paul Le Roux created E4M, a free open-source MS-Windows disk encryption software program, in 1999, and is a suspected creator of the open-source TrueCrypt, which it's core-base if from the E4M’s code”, Paul Le Roux creation, again.


    Then it drops a bomb: 
    “Paul Le Roux currently is in US custody for ordering the assassinations of six people U.S.citizens bitcoin investors.”

    Paul Le Roux career that’s included logging, precious metals mining, gold smuggling, land deals, drug shipments, arms trafficking and money laundering whereby Paul Le Roux is guilty before the Bitcoin connection is thrown into the mix.

    In one of the many passports Paul Le Roux owned, he goes by the Satoshi-like name of “Solotshi” and of curious coincidence.

    A Daily Mail article which also slipped through the redactor’s net, leaving a trace of the URL visible in document 187 cited at the outset, calls Paul Le Roux a “real-life Bond criminal-mastermind villain.

    Paul Le Roux stands behind a cocaine and "lord-of-war" global weapon sales and an empire spanning four continents who always been a super-snitch” equal to countless others of his life-style greater or small.

    Quote from a U.S. agents as calling him “an extreme murderous criminal and a very bad guy.”

    Satoshi and Solotshi (“Solotshi” Paul Le Roux.)

    As the anon who posted on 4chan’s /biz/ messageboard on May 12, after spotting Paul Le Roux’s name in the Wright case postulated, “Bitcoin was a project of a evil genius … Paul Solotshi Calder Le Roux said.

    He intended it simply for the purpose of money laundering …

    Unfortunately, soon after he went quiet with the Satoshi identity, he was captured by law enforcement, and he’s going to spend the rest of his life rotting in a dirty bitcoin jail cell.”

    Paul Le Roux did create Bitcoin, because programming languages match 101%.

    Paul Le Roux stated money laundering was his goal, but is his obsession with cryptography, which can be traced back to the 90s with equal same programming signatures of coding style unique, uncommon, and repetative.

    Paul Le Roux broke bad, and was by all accounts a brilliant programmer within privacy ideologue.

    In 1997, he began work on E4M (Encryption for the Masses), software which “is capable of encrypting entire disks and of plausible deniability (denying the existence of an encrypted volume),” Wikipedia explains. It continues:
    In the “Politics” section of the E4M website [archive], Paul Le Roux published his egocentric manifesto stating that governments are increasingly relying on electronic data gathering. Citing projects such as Echelon, linked to the five nation states which would become known as the “Five Eyes” more than a decade later, he stated that encryption is the only way to preserve civil liberties.
    The E4M manifesto finishes: “Strong Encryption is the mechanism with which to combat these intrusions, preserve your rights, and guarantee your freedoms into the information age and beyond – Paul Le Roux, Author, Encryption for the Masses” letting the masses know who created bitcoin as himself, Paul Le Roux.



    10 Clues That Point to Le Roux Building Bitcoin
    Comparing Satoshi and Paul Le Roux’s personas for similarities relied on private-military-security-contractors on spare time/off-duty proving Paul Le Roux is Satoshi Nakamoto there are several attributes and actions that align – plus a few that don’t. Given that both entities were adept at assuming false personas and concealing their natural language and idiosyncrasies, identification is no easy task. Here’s what’s known about the pair that points to them being the same person:
    1. The curious Satoshi/Solotshi monikers.
    2. Both were programmers familiar with C++, same signatures.
    3. Both had a strong interest in cryptography and privacy.
    4. Both were wary of authority, as Paul Le Roux is a crazy narq.
    5. Both had an interest in online gambling – Bitcoin’s initial code had a poker client included.
    6. Both were well aware of the difficulty with traditional payment systems, Paul Le Roux on account of the illegal prescription drug racket he was running and worse crimes against humanity.
    7. Satoshi’s spelling style, and language are finger-prints by “hardened analyse” is consistent with Rhodesian Paul Le Roux.
    8. Satoshi disappeared in early 2011 to “move on to other things” at the time that Paul Le Roux was transitioning from software genius to cartel boss.
    9. With tens of millions of dollars in cash, Le Roux invest more BTC once the price began rising.
    10. If anyone could have hidden wallets containing-over 1 million BTC, signatured the creator of disk encryption software TrueCrypt.

    Now there’s this 2002 post, seven years before Bitcoin is released:


    It all reads identifying Satoshi Nakamoto’s voice, but it does read an awfully lot like someone’s early idea of Bitcoin.

    The IP address of the author has supposedly been traced to the Netherlands – a country where Paul Le Roux lived, and at that specific location via IP and Mac-Address.

    Surface evidence that points Paul Le Roux could have been Satoshi Nakamoto countless times, and different researchers have points that did not align.

    In 2009, when Satoshi Nakamoto was diligently refining Bitcoin, Paul Le Roux was already dabbling within international drug smuggling and gun running.

    Would it have been possible to maintain such a double life, one chaotic and the other scholarly?

    Yes, many programmers agree takes only minutes posting to forums and responding at times via cell-phone technology and at times appeared automated.




    Some of the $100M of cocaine seized from a shipment that Le Roux sent by boat

    Satoshi Nakamoto Mind Chess From Craig Wright!
    In an IRC chat dating in same time-frame of the Bitcoin Cash ABC/SV split, user “CSW” (Craig Wright) connects Bitcointalk and r/Bitcoin moderator Theymos to Paul Le Roux, claiming that the pair used to be partners “before Le Roux was arrested”. Now you are snagged, gotchyas!

    He also asserts that Theymos is still in the “pharma spam business,” which dovetails with Le Roux’s illegal pharmaceutical business cartel ties.





    There is a caveat to all of this, of course: 
    Craig Wright is a habitual liar by every utterance must always be fact-checked as with all millionaire/billionaires/wealthy same always and 99% are not self made without drug investments, sales, gun running, and money laundering, hence extreme dirty and dishonest.

    Given that Paul Le Roux’s name has been linked with Satoshi Nakamoto since before late 2018, everyone pointed.

    Now, it is possible that Mr. Wright made a holy-diver onto it weaving it into fanfiction he’s been crafting for the Kleiman case.

    All evidence from the mouth of the man known as Faketoshi should be treated with extreme caution.

    Less than few, "aside from Calvin Ayre", believe that Craig Wright created Bitcoin.

    Many unveiled by luck ans less than design he have been lurking in the background from near the start, but was quickly disqualified and remove from the project untrusted by these dirty bitcoin criminals.




    His involvement to Wright serving as an informant on Paul Le Roux is obvious and alread admitted to by agencies behind closed coder doors..

    For himself as an informant following his arrest in September 2012 is speculations.

    It sounds like a fanciful adventure crypto-movie make by hollywood, but it’s certainly an intriguing notion.

    As one anon theorized, “Craig Wright" was an employee of Paul Le Roux, but not at all and in actuality just a lying dead weight hanging around.

    Craig Wright was vaguely aware of the bitcoin project and his assertions signature jealousy. Craig was a big narq snitch of an informant who helped bring down Paul Le Roux.

    Now, after his arrest, Craig managed (via long time friend and partner in crime, Dave Kleiman) to get his hands on the bitcoin wallets worth over $1+million in bitcoins.

    Unfortunately for Craig, all of Solotshi’s coins are locked away in secure TrueCrypt volumes (TrueCrypt being another software that Paul Le Roux developed).

    He has been trying for years to crack them but with no success.”


    “Another of Craig’s long time friends, Calvin Ayre, has set up warehouses of computers to try to crack Solotshi’s password and unlock the vast fortunes; his mining activity is simply a front to make these massive datacenters look legitimate.

    Unfortunately Craig is being set up as ‘the real Satoshi Nakamoto’ so that when the coins are finally unlocked, they can legitimately sell them off.”




    In this document from the Kleiman v. Wright case, Wright claims to have access to Truecrypt files that he cannot access. 

    It has been speculated that these are not Dave’s, but rather Paul Le Roux’s, obviously. 

    If the Rhodesian crime boss is Satoshi Nakamoto, it means that the two biggest contributors to Bitcoin’s early success, Paul Le Roux and Ross Ulbricht, are both in the custody of U.S. authorities.

    Paul Le Roux and Ross Ulbricht will wait-out the rest of their lives in prison, while the rest of the world profits from the innovations of these flawed dirty criminal geniuses.

    This site, Gotsatoshi.com promises to reveal the identity of Bitcoin’s creator.

    While the cryptosphere will not be holding its breath in anticipation, the countdown adds further intrigue to the most enduring mystery of the digital age.



    Paul Le Roux and Satoshi connection unveiled!






    Monday, July 15, 2019

    2018-2019+ Hottest-Insiders Under-Radar Tech-Stock


    2018-2019+Hottest-Insiders Under-Radar Tech-Stock




    This is what happens when new technology whales the stock-market that’s already worth nearly $300 billion?

    You are about to find out.




    BTC














    The market is cannabis, and the tech is from a little-known company called TruTrace (CSE:TTT; OTC:TTTSF) that’s years ahead of the competition in this multi-billion-dollar niche segment.

    The global cannabis consumer market is worth an estimated $344 billion buoyed by 160 million users, according to New Frontier data. The legal segment of this is growing at a record pace: Jefferies Group projects the legal cannabis market will be worth $130 billion by 2029.

    The U.S. and Canada alone are expected to generate $172 billion in retail sales over the next six years, according to New Frontier.
    Virtually everyone seems bullish about the future of legal weed.
    Cannabis

    However you look at it, the numbers are astounding.
    But there’s one big problem with this booming market…

    The supply chain. It is both vulnerable and lacks transparency, a problem that could be keeping marijuana from growing into a trillion-dollar industry.

    With TruTrace (CSE:TTT; OTC:TTTSF), this bottleneck might be removed entirely. This company’s new tech is designed to assist with the entire supply chain, from plant to market.

    And the best thing? There’s no apparent competition yet.
    For cannabis right now, the difference between a multi-billion-dollar industry and a potential trillion-dollar industry seems to be quality and provenance.
    That requires a global technological solution that can secure every single strain on the planet for consumers. And the company first out of the gates in this game could likely have a major advantage.

    Here are 5 reasons to keep Ontario-based TruTrace Technologies Inc. (CSE:TTT; OTC:TTTSF) on your radar.

    Reason #1: Legalization Drive = Explosive growth for $146B industry
    Marijuana is fast losing its reputation as a grungy, pothead gateway drug, rebranding itself as modern, premium and artisanal - all thanks to the global legalization drive.
    Just look at the U.S. cannabis legalization map, which only tells a part of this global story:
    Legal

    Source: RollingStone
    You can now light up legally in Canada, the District of Columbia, 30 different states in the U.S., Mexico, Belize, Costa Rica, Jamaica, Colombia, Ecuador, Peru, Argentina, Uruguay, Cambodia and Laos. Many more will soon follow.

    According to the UN, a staggering 158.8 million people, or nearly 4 percent of the world’s population, now consume marijuana.

    But here’s the alarming part: although the trend toward legalization for both medicinal and recreational purposes has been moving full steam ahead, the black market for marijuana remains massive. Despite the incredible potential of this emerging market, legal cannabis only made up $11.9 billion of the U.S. market in 2018.

    And this trend rings true in Canada as well, the world’s biggest legal weed venue.

    During the final quarter of 2018, nearly 80 percent of Canadian weed sales were through the black market - a slight improvement from 90 percent the previous quarter.

    Part of the reason for this curious trend is the fact that legal weed costs more than its illegitimate brethren, but the bigger reason has to do with supply chain issues (the Canadian government has curtailed retail hours and limited licensing distributions mainly due to health and safety concerns).

    Luckily for marijuana investors, all that is about to change...fast.

    According to industry estimates, the global legal cannabis industry is expected to experience explosive growth that will hit $146.4 billion by the end of 2025.
    The future of the legal weed industry is bullish to the extent that even a famous Wall Street short-seller is calling it “The Big Long”.

    However, it simply won’t get there without legitimacy.

    The crippling bottlenecks in the marijuana supply chain need to be ironed out
    ASAP.

    Luckily, the turning point for the industry has finally arrived.
    TruTrace’s (CSE:TTT; OTC:TTTSF) proprietary StrainSecure seed-to-sale tracking technology, the first in the marijuana industry, is a genuine gamechanger that’s set to significantly speed up the industry’s legalization push.

    Reason #2: Wide moat company with first-of-a-kind tracking tech
    The legal weed industry is facing some formidable challenges.
    • A disparate and highly fractured supply chain fueling a massive black market…
    • Lack of product quality and consistency…
    • A growing trend of piracy and counterfeiting brands…

    That’s why state regulators are demanding strict seed-to-sale tracking capabilities that will allow companies to seamlessly monitor legalized marijuana products across the supply chain.

    That means monitoring where it was planted, harvested, processed, and ultimately - sold.

    Consider this: each year, more than 1,000 tons of illegal marijuana are seized along the U.S.-Mexico border. That’s weed worth millions of dollars going to fund criminal activities.

    Just like the jewelry industry is now using IBM’s blockchain technology to trace the origin of diamonds in a bid to filter out blood diamonds, the cannabis industry badly needs tracking tech for provenance and for preventing harmful or illegal products into the marketplace.

    TruTrace (CSE:TTT; OTC:TTTSF) has already developed the technology that will take care of business here:
    Strain Secure

    Source: StrainSecure
    TruTrace Technologies has developed StrainSecure, the industry’s first integrated blockchain platform to register and track intellectual property in the cannabis industry.

    This advanced blockchain technology establishes a single-source, accurate, validated and permanent account for any cannabis strain - all the way to the market.

    Even better: The digital platform also streamlines the administrative process, lowering the costs related to genetic and mandatory quality-control testing for legal cannabis.

    Each time a product is tested and verified by the network, a Registration Affidavit is auto-generated and assigned a unique StrainSecure Address traceable through a QR Code.

    Producers, patients and consumers can not only verify and test their products but also rate them and share reviews. These details are secured on the StrainSecure blockchain and cannot be altered by any one party.
    Tru

    In short, TruTrace (CSE:TTT; OTC:TTTSF) seeks to become the marijuana’s industry’s IBM, the only company out there that can make claims related to traceability.

    Incredibly, they have built this proprietary platform in-house, with a team with 21 years of large-scale enterprise software development for fortune 500 companies such as Microsoft and Mercedes Benz, as well as 8 years of experience in the cannabis and supply chain industry.

    They are so confident in their product that they don’t see any other company having anything like it for years to come.

    This gives TruTrace a huge first-mover advantage and an incredibly wide moat that it can exploit for years to come…

    Another advantage: TruTrace has signed a deal with Strainprint, a leading source of medical cannabis use data with more than 60 million data points from 1.2 million medical cannabis patients with reported outcomes.

    TruTrace (CSE:TTT; OTC:TTTSF) has also entered an agreement with Molecular Science Corp. to leverage its industry-leading analytical capabilities.

    Instead of being a chess piece on a crowded board, TruTrace has positioned itself as the board itself.

    This is the epicenter of legal marijuana testing. It’s the lucrative starting point for the entire industry’s drive for transparency, standardization and compliance.

    Reason #3: High revenue potential
    Having a first-mover advantage in the modern tech world is almost always a ticket to breakout revenue and profits…

    Not to mention nearly endless growth runways…
    For TruTrace, the possibilities for growth are extremely attractive.

    They already have the attention of the large medical community in the Canadian market-place and some in the US market-place.

    And the company just signed a deal with one of the biggest drug distributors in Canada—with more than 1200 brick-and-mortar stores.

    Next to this, the company is working on a deal that it hopes will bring in several of the top producers in the Canadian market-place, and potentially many more from the U.S. and then the rest of the world.

    Why? Because it’s the only tech of its kind available, and because the cannabis industry is in desperate need of it.

    One of TruTrace’s key markets are marijuana distributors - with more than 100 pot shops in Canada and over 2,000 dispensaries in the United States, it’s safe to say the company’s StrainSecure product will likely find a very ready and healthy market.

    The outlook is certainly very compelling…

    The cannabis testing market is rapidly taking off and is expected to grow from $1.5 billion currently to $2.4 billion over the next 5 years.

    The food safety testing market is much bigger, currently valued at $14 billion and expected to exceed $23 billion by 2025.

    TruTrace (CSE:TTT; OTC:TTTSF) has already performed test runs on the StrainSecure platform and has received permission to deploy a blockchain-secured pilot program to help tackle some of the industry’s biggest problems.
    The company’s management estimates that the company could hit $7-10 million in annual revenues from a standing start. They think that could grow to $25-$50 million in a few years as the company ramps up its distribution channels.
    Mind you, this is a company currently valued at just $25 million.

    Reason #4: Considerable M&A Potential
    Capital

    Source: Marijuana Business Daily

    The green rush is well and truly underway.
    Currently, corporate tie-ups are all the rage in the marijuana sector.
    Some very large transactions have sparked the cannabis sector lately, and much more is expected to come.

    Mostly it’s been big pot and big tobacco buying marijuana companies in multi-billion-dollar deals in the hope of getting a piece of the action.

    Constellation Brands’(NYSE:STZ) invested $4 billion investment into Canopy Growth Corporation (NYSE:CGC).
    Altria Group Inc. (NYSE:MO) has agreed to take a $1.8B minority stake in Cronos Group Inc.(NASDAQ:CRON).
    Aurora Cannabis Inc (NYSE:ABC) has agreed to buy smaller rival CanniMed Therapeutics Inc. for C$1.1 billion ($852 million.

    One big risk: the marijuana growers and producers is an overcrowded industry and a major shakeout appears imminent.  Concerns surrounding overproduction have repeatedly come up with fears that too much weed could crash the market.

    In any crowded industry, only the most differentiated companies survive, i.e. those with the smartest and most unique solutions that cannot be easily duplicated. TruTrace (CSE:TTT; OTC:TTTSF) (formerly BlockStrain) has been identified as  one of the few companies using technology in a unique way to transform the marijuana industry.

    Who could potentially acquire TruTrace?

    There’s literally an endless list of companies that could be interested in buying this gem.

    It could be any of the 100 or so public companies that operate in the medical and legal marijuana sector.

    Or any of the thousands of private producers and distributors…

    Or any of the hundreds in the food safety testing industry…
    It could even be one of several companies that have already struck deals or Joint Ventures with TruTrace.

    Let’s now examine what TruTrace could fetch in such a scenario…or when the market finally wakes up to its true potential.

    Reason #5: Explosive upside potential stock
    You will be hard-pressed to find any industry that has gone through such explosive growth as the marijuana sector has over the past few years.
    Tens of thousands of investors have realized incredible returns on marijuana investments…

    Even after the latest correction, Cronos Group stock is still up a staggering 6,500 percent over the past three years…
    Cronos

    Source: CNN Money
    Aurora Cannabis stock has rallied more than 2,000 percent over the past 36 months…
    Aurora

    Source: CNN Money
    While Aphria Inc. has gained nearly 500 percent over the timeframe...
    Aphria

    Source: CNN Money

    Despite concerns about frothy valuations, investors have continued to flock to marijuana stocks with the medicine and legal marijuana sector rallying 25 percent in the year-to-date, nearly doubling the return by the market benchmark S&P 500.
    Cannabis

    Source: New Cannabis Ventures

    So, how does TruTrace stock stack up?
    At a share price of just $0.31, TruTrace (CSE:TTT; OTC:TTTSF) is a bona fide penny stock, but penny stocks tend to have the most explosive upside potential compared to their pricier brethren.

    The great part is that unlike many marijuana companies, TruTrace has zero debt on its books and technology that could potentially expand well beyond the cannabis industry.

    Early-in investors have a chance to make a potential killing off this company, regardless of whether it gets acquired or continues to grow organically.
    As Alan Brochstein, Founding Partner of New Cannabis Ventures, has aptly observed: “Companies with unique assets or business models are likely to be more appealing to potential buyers. Different geographies or modes of production are often cited by the buying companies, Consolidation is picking up in the cannabis space, and investors are rewarding the companies that are buying by pushing their stocks up after the deals are announced. This will likely encourage other companies to be me more aggressive in their M&A strategies.’’

    TruTrace ticks all the right boxes.
    By. Meredith Taylor

    IMPORTANT NOTICE AND DISCLAIMER
    PAID ADVERTISEMENT.
    This communication should be viewed as a paid advertisement. Leacap Ltd and Safehaven and their owners, managers, employees, and assigns (collectively “the Publisher”) is often paid by one or more of the profiled companies or a third party to disseminate these types of communications. In this case, the Publisher was not specifically paid for this communication. However, a related company was previously compensated by Tru Trace Technologies In May 2018, to produce and disseminate other similar articles and certain banner ads. This compensation should be viewed as a major conflict with our ability to be unbiased.

    Readers should beware that third parties, profiled companies, and/or their affiliates may liquidate shares of the profiled companies at any time, including at or near the time you receive this communication, which has the potential to hurt share prices. Frequently companies profiled in our articles experience a large increase in volume and share price during the course of investor awareness marketing, which often ends as soon as the investor awareness marketing ceases. The investor awareness marketing may be as brief as one day, after which a large decrease in volume and share price may likely occur.

    This communication is not, and should not be construed to be, an offer to sell or a solicitation of an offer to buy any security. Neither this communication nor the Publisher purport to provide a complete analysis of any company or its financial position. The Publisher is not, and does not purport to be, a broker-dealer or registered investment adviser. This communication is not, and should not be construed to be, personalized investment advice directed to or appropriate for any particular investor. Any investment should be made only after consulting a professional investment advisor and only after reviewing the financial statements and other pertinent corporate information about the company.

    Further, readers are advised to read and carefully consider the Risk Factors identified and discussed in the advertised company’s SEC and/or other government filings. Investing in securities, particularly microcap securities, is speculative and carries a high degree of risk. Past performance does not guarantee future results. This communication is based on information generally available to the public and on an interview conducted with the company’s CEO, and does not contain any material, non-public information. The information on which it is based is believed to be reliable. Nevertheless, the Publisher cannot guarantee the accuracy or completeness of the information.

    SHARE OWNERSHIP.
    The owner of Safehaven owns shares and/or stock options of the featured companies and therefore has an additional incentive to see the featured companies’ stock perform well. The owner of Safehaven has no present intention to sell any of the issuer’s securities in the near future but does not undertake any obligation to notify the market when it decides to buy or sell shares of the issuer in the market. The owner of Safehaven will be buying and selling shares of the featured company for its own profit. This is why we stress that you conduct extensive due diligence as well as seek the advice of your financial advisor or a registered broker-dealer before investing in any securities.

    FORWARD LOOKING STATEMENTS.
    This publication contains forward-looking statements, including statements regarding expected continual growth of the featured companies and/or industry. The publisher notes that statements contained herein that look forward in time, which include everything other than historical information, involve risks and uncertainties that may affect the companies’ actual results of operations. Factors that could cause actual results to differ include, but are not limited to, changing governmental laws and policies, the success of the companies’ technology, the size and growth of the market for the companies’ products and services, the companies’ ability to fund their capital requirements in the near term and long term, pricing pressures, etc.

    INDEMNIFICATION/RELEASE OF LIABILITY.
    By reading this communication, you acknowledge that you have read and understand this disclaimer, and further that to the greatest extent permitted under law, you release the Publisher, its affiliates, assigns and successors from any and all liability, damages, and injury from this communication. You further warrant that you are solely responsible for any financial outcome that may come from your investment decisions.

    TERMS OF USE.
    By reading this communication you agree that you have reviewed and fully agree to the Terms of Use found here http://Safehaven/terms-and-conditions If you do not agree to the Terms of Use http://Safehaven/terms-and-conditions, please contact Safehaven to discontinue receiving future communications.

    INTELLECTUAL PROPERTY.
    Safehaven is the Publisher’s trademark. All other trademarks used in this communication are the property of their respective trademark holders. The Publisher is not affiliated, connected, or associated with, and is not sponsored, approved, or originated by, the trademark holders unless otherwise stated. No claim is made by the Publisher to any rights in any third-party trademarks.


    Sunday, July 14, 2019

    S&T Blockchain-Program: Cryptocurrency



    S&T Blockchain Program Focuses on Security, Privacy, Interoperability, Standards


    There has been a lot of buzz lately about how Blockchain will revolutionize the secure transfer of information. S&T says that by understanding its potential applications and impact, and setting universal standards for usage, S&T is paving the way for multiple agencies such as U.S. Customs and Border Protection (CBP), U.S. Citizenship and Immigration Services (USCIS), Transportation Security Administration (TSA) and others to successfully and easily integrate Blockchain into their mission.




    BTC














    There has been a lot of buzz lately about how Blockchain will revolutionize the secure transfer of information. However, many are still unclear on exactly what Blockchain is, where its applications can be used and how the leaders in the field will be able to deliver usable software to potential buyers.

    As an emerging tech trend, the Department of Homeland Security (DHS) Science and Technology Directorate (S&T) has been tracking Blockchain’s birth, development and progress for years. S&T was particularly interested because of the potential for building resilience into digital transaction systems.

    S&T says that by understanding its potential applications and impact, and setting universal standards for usage, S&T is paving the way for multiple agencies such as U.S. Customs and Border Protection (CBP), U.S. Citizenship and Immigration Services (USCIS), Transportation Security Administration (TSA) and others to successfully and easily integrate Blockchain into their mission.

    As the DHS science advisor, S&T keeps its finger on the pulse of emerging technologies. When the assessment is made that the time is right, S&T may even offer assistance to industry to help the tech both achieve its full potential and reach perspective government buyers and users. That is exactly what happened with Blockchain.


    What is Blockchain?


    Blockchain first gained wide notoriety as the system that runs the Bitcoin digital currency transaction confirmation process.

    What makes it so different from previous models is that each transaction of the digital monies forms a new “block” in a public ledger. The ledger is transparent and communally verifiable within an open and shared database. As a shared, synchronized and geographically disbursed database, with no centralized data storage, the system is designed to remove the “single point of failure” risk (including technical malfunction and malicious alteration) that is present in many other systems.

    One of the other key differentiators from previous structures is that since it is a “distributed electronic ledger,” if one wants to track the historical transactions of a specific unit of currency (or data) from its introduction into the system until a specific date, that can be done and verified by multiple independent users. The blocks form an unbroken “chain” that acts as a visible digital paper trail.
    So far, Blockchain has proven extremely resistant to any type of hacking or alteration, and that makes it especially attractive for Homeland Security Enterprise (HSE) uses.


    SVIP and Blockchain


    S&T’s Silicon Valley Innovation Program (SVIP) bridges the public/private sector gap by cultivating relationships, advising and educating innovators on DHS needs and then offering opportunities to fund and test technologies.

    According to Anil John, SVIP Technical Director, “About three years ago, we saw that the global interest in Blockchain technology was not matched by technical investments that ensured that the technology incorporated fundamental security, privacy and interoperability functions. In other words, while its capabilities could represent a dramatic change in the way that things will be done in the future, so much so that it could disrupt the current norms in multiple sectors, there were still missing links in the chain. That’s when we offered our assistance.”

    And with that, S&T launched a program for Blockchain that focused on security, privacy and interoperability specifications and standards.

    Although it may sound mundane at first, one of S&T’s other lesser known roles within the HSE is to assist components and vendor partners with identifying, creating and setting standards for the technologies themselves.

    By developing standardized specifications, S&T creates a common language and criteria for vendor and end-user, alike. This shared understanding facilitates seamless interoperability which enhances utility, efficiency and ultimately, mission success.

    The goal of the Blockchain program was to further understand the technology’s capabilities, and also to support and, as needed, create broadly accepted standards to benefit both government entities and the companies in the emerging sector.

    By supporting a set of vetted standards, S&T enables government and non-government users to avoid spending additional time and money “re-creating the wheel” to build multiple new interfaces that connect with individual proprietary vendor tools.

    John pointed out that, “Historically, when new technologies or solutions are incorporated into legacy systems, there are obstacles that create slowdowns as work-arounds are developed so that the systems mesh properly. However, through the use of globally acceptable and implemented specifications and standards, we are addressing and removing those interoperability hurdles before deployment. That way our industry partners and government components can hit the ground running.”

    This is important because multiple agencies can immediately benefit from the advantages of Blockchain.

    Throughout the HSE, agencies issue entitlements, attestations and certifications. The holders of those credentials might be an individual, organization or product, but from the HSE perspective, they all have at least one thing in common—the documentation must be quickly verified, extremely robust and resistant to tampering. Paper-based, manual verification solutions are slow, non-centralized and pose are greater risk of forgery and counterfeiting. Blockchain is tailor-made to address and mitigate these security and speed issues.


    CBP and Blockchain

    S&T first piloted Blockchain with CBP; the nation’s leading law enforcement agency to facilitate lawful international trade across U.S borders. CBP has primary responsibility over the import/export supply chain (the system responsible for bringing a raw product or service to the end customer), verifying international treaty certifications and providing for the timely approval and movement of cargo.

    John explained, “We are a support organization for components and their operators. CBP saw that we were ahead of the curve with our understanding of the Blockchain landscape, so they reached out to us. It’s a great example, because their desires intersected with our knowledge.”

    The tracking and validation of goods, their elements and their origins throughout the entire supply chain for audit and compliance purposes, is extremely challenging. CBP was interested in updating the paper-based system that they had been using to verify and approve trade agreements.

    They saw that Blockchain could enable stakeholders (broker, importer and government) to know instantly the status of import products. By adding a level of secure transparency to the supply chain, all involved parties would be able to track and verify each product from origin to destination.

     “Blockchain and CBP’s needs were an excellent match and the lessons learned in the pilot are being applied to additional agencies.” said John.

    Based on the success with CBP, additional DHS Components are starting to explore how Blockchain technologies could help with their missions.

    In particular, throughout the HSE, agencies such as USCIS issue entitlements, attestations and certifications. The holders of those credentials might be an individual, organization or product, but from the HSE perspective, they all have at least one thing in common—the documentation must be quickly verified, extremely robust and resistant to tampering. Paper-based, manual verification solutions at areas such as TSA checkpoints are non-centralized and pose are greater risk of forgery and counterfeiting. Blockchain is a potential solution that can address and mitigate these security and speed issues.


    USCIS and Blockchain


    USCIS is responsible for issuance of documentation proving citizenship, immigration and employment work-status authorization. They wanted to upgrade their existing manual system to be faster, more accurate and more secure.

    USCIS wanted a solution to reduce fraud in citizenship, immigration and authorization documentations. And that is exactly the type of functions where Blockchain excels.” added John.

    By working and  partnering with SVIP to sponsor the “Preventing Forgeries of and Counterfeiting of Certificates and Licenses” Call,  USCIS is seeking how Blockchain technologies can help secure and automate these processes, which translates into faster and more accurate verification.


    TSA and Blockchain


    The TSA is the lead organization responsible for the security of the traveling public. In that role, it is responsible for verifying that each passenger that interacts with a TSA checkpoint presents lawful and legitimate proof of identity that also matches them and their boarding pass. Currently, much of this verification is done manually and by visual assessment. With Blockchain, passenger identification could be accelerated, and detection of fraudulent documentation enhanced.

     “TSA is another great capability match,” remarked John. “Blockchain is the infrastructure that supports the validation of credentials. Greater speed and accuracy at checkpoints means a better and safer traveler experience.”

    By partnering with SVIP to sponsor the “Preventing Forgeries of and Counterfeiting of Certificates and Licenses” Call, TSA is seeking how Blockchain technologies can help secure, automate and speed up the credential validation processes at checkpoints.


    S&T, SVIP, Blockchain and the Future


    S&T says it is taking the lead in developing the processes for the use of Blockchain. This work will accelerate the development and deployment of this important technology throughout the HSE and other government agencies.

    By modernizing these systems, Blockchain will save time, money and reduce fraud.

    Development of standards enables a robust and competitive marketplace for Blockchain uses that will benefit both the government clients and the private sector industry manufacturers and sellers.

    Meanwhile, S&T SVIP is continuing to fund and explore new ways to facilitate the speedy and secure transfer of authenticated data and the verification of documentation to secure trade, travel and ultimately, the country.

     “The work we’re doing with Blockchain will enable the HSE to execute its mission more efficiently. By automating a multitude of time-consuming tasks, agents will be freed to focus on other areas of trade, travel and security,” said John, “The program’s success will serve as the foundation of our ‘whole of government’ approach to Blockchain in the future.”

    Iran-Indoctrinates Gold-Backed-Cryptocurrency

    Iran-Indoctrinates Gold-Backed-Cryptocurrency






    Iran-Indoctrinates Gold-Backed: Bitcoin supporter Caitlin Long unleashed on President Trump an impassioned tweet storm in reaction to U.S. President Donald Trump’s tweeted anti-crypto remarks.




    BTC














    Caitlin Long tweeted Trump is being misled by his staff and argued that cryptocurrency could function within the law despite POTUS45 misdirected fears staffers have pressed upon him.

    Caitlin Long Warns Trump That Staff Is Misleading Him on Bitcoin:



    A series of tweets, Trump declared that he is not a fan of bitcoin or other cryptocurrencies.

    Trump adamantly iterates that cryptocurrency is “not money,” and took issue with bitcoin’s extreme volatility.

    President Trump said its value is “based on thin air.”

    Trump believes bitcoin and all virtual currencies are used to facilitate crimes, such as drug trafficking, and human trafficking.

    Iran Body Slams Trump With Gold Backed Cryptocurrency:



    Meanwhile the Persians in Tehran/Iran think-tank engineering cryptocurrency with Gold-back held in reserve by the Middle East country’s central bank.

    This will back the value of the new iranian cryptocurrency tokens on the blockchain of Iran’s new central bank “cryptocurrency” launched countering U.S. sanctions.

    The new Iranian gold back cryptocurrency will be mined by a small consortium of private Iranian tech companies directly attached to the regime.

    The game-theory move have already complicate the oil-rich country and the United States.

    Rothschild, Rockefeller, and the other blue-blood banker families will usher a global war into game-theory levels never recorded, nor imagined by historians.

    Iran have solidified uncertain times for the entire earth. Decentralizing Iranian controled and created cryptocurrency currently created shockwave globally already.

    Now the entire plant is keenly watching President Donald Trump’s game of chicken with Iran taken critical turn into the cryptocurrency decentralization giving middle finger to the federal reserve banking empire.

     -------  -------  ------- Iran has admitted that it actively violates embargoes and treaties against its developing nuclear weapons or technology and now their own gold-back cryptocurrency is above genius game-theory move.

    This Middle East country, Iran, is an increasing headache for the United States and their allies with the regimes new cryptocurrency global body slam unprecedented ever before.

    Iran nuclear ambitions in plain sight despite being told repeatedly that this could lead to severe consequences.

    Iran repeatedly demonstrates global defiance against the Rothschild Rockefeller Federal Reserve Empire as China and Russia are 101% allied with Irans cryptocurrency game-theory efforts.

    Iran has the sovereignty and freedom to pursue its nuclear vision just as other nations in opposition to this oil-back currency USD.
     --- 

    All sides will continue to ratchet up the rhetoric for the foreseeable future for their own versons sovereign freedom.

    Trump warned Iran of complete obliteration using the military might of the United States.

    The Iranian presidential advisor Hesameddin Ashena warned they will target the former reality TV star, Donald Trump.


    Iranian monetary development comes from a report from Mehr News that is currently sending shock-waves into global market back by China and Russia each step of Iran's efforts.


    Tehran-based news announcement that the Central Bank of Iran (CBI) gives prime directive permission for an Irainian gold-backed crypto currency.

    Shahab Javanmardi, CEO of FANAP – an Iranian information and communications technology (ICT) firm – revealed this cryptocurrency role-out:
    “The Iranian cryptocurrency is backed by gold but its function is similar to foreign rivals. The domestically encrypted money is to ease optimal use of Iranian banks’ frozen resources.”

    Iran Staged Their Own Cryptocurrency Creation:



    Announcement of Iran’s new state cryptocurrency came days after the CBI banned all private cryptocurrencies in preperation of it's own cryptocurrency businesses ventures in the country.

    The legal and regulatory status of bitcoin in Iran isvery clear and resolves their own cryptocurrency and no other.

    Different authorities in varying agencies have issued contradictory statements to mislead nations regards to their own cryptocurrency hallmark creation.

    Iran projected  as perplexed about cryptocurrency, but secretly targeting  financial authorities in the United States and globally.

    Iran has the cheapest least expensive energy costs in the world, Iran is an extremely profitable place cryptocurrency mining and now with Iran's new cryptocurrency creation banning all other cryptocurrency blockchain coins nationwide is diabolical genius game-theory

    The U.S. has accused Iran of using cryptocurrency to circumvent international sanctions, and they have done just that.

    Central Bank Cryptocurrencies on the Rise:



    As Irish playwright Oscar Wilde once said, “Imitation is the sincerest form of flattery that mediocrity can pay to greatness.”

    By Wilde’s estimation, many of the world’s central banks are paying the most sincere flattery to bitcoin, ethereum, and other large-cap cryptocurrencies.

    As of 2019, the world’s central banks are working on digital currencies.

    Iran’s central bank move changes everything.


    In Venezuela, President Maduro launched a state cryptocurrency backed by oil.

    Last month "Maduro Orders Venezuela’s Biggest Bank to Accept Crypto Petro Nationwide."

    The oil-rich South American country’s largest bank, the Bank of Venezuela, to open trading desks for the controversial cryptocurrency this nations new-asset.

    Venezuela, a country battling one of the deepest economic recessions on global record, is set to launch a new fiat currency pegged to its oil-backed “petro” cryptocurrency according to President Nicolas Maduro.

    Singapore’s central bank has deployed a full-blown cryptocurrency, and Singapore Trials its Digital Dollar via an Ethereum Blockchain.

    The Singapore dollar, on an ethereum-based private blockchain. That was in 2017.

    -------

    Your Bitcoins Are Now Fully Backed by Gold and Silver?




    Maya Preferred 223 (MAPR), a stablecoin with each unit worth about $34,000 in gold and silver assets, announced that their ambitious plan to back Bitcoin with gold and silver has entered its final stage and accelerated by Iran's cryptocurrency efforts.
    Part of Maya Preferred 223’s business plan is to stabilize the cryptocurrency market by using its own coin to back other cryptocurrencies and tokens with gold and silver reserves. 

    Maya Preferred 223’s developers, U.K. Financial Ltd, recently transferred $21 million MAPR into to escrow accounts,

    This is the amount equal to the total number of Bitcoins which signatures these nations have been the cryptocurrency whales since it's conception.

    The reasoning behind the move is cryptocurrency markets have always been secretly controled by central banks via whales.

    Bitcoin will loses its value ounce centralized. 

    The Maya team is guaranteeing the flagship cryptocurrency, backed by the silver and gold assets currently behind their MAPR venture. 

    The cryptocurrency that is backed with MAPR, is DFS Inc. token, a utility gaming token, based on Ethereum. 

    Maya have signed contracts tha hands over 51% control of global tokens and then the team will start backing DFS with $2.50 of assets per token.