IOTA: Azimuth — a different approach to PoW, The results of the Trinity Security Audit by SIXGEN, Client libraries and IRI with networking rewrite update, Partnership with Primority to ensure allergen food safety, The team at IEEE ICBC

Paradigm
Paradigm
Published in
23 min readJun 27, 2019

Biweekly update 13th June — 27th June

Hello, IOTA fans! The project is still ongoing their evolution to become the most successful blockchain project! These weeks IOTA team worked fingers to the bone as usual! They introduced Azimuth (previously known as NB-PoW): a different approach to proof of work that they are working on as part of our long-term vision for IOTA. Azimuth will allow IoT nodes to protect themselves from spam without using unnecessary computational power doing proof of work. This approach to spam protection will also allow nodes to accept incoming transactions from any neighbor who is close enough (autopeering). As a result, small IoT devices will easily be able join an IOTA network without wasting their resources, leading to an increased number of nodes — an important step towards a machine-to-machine economy. Read IOTA latest Tech Update on the blog: Client libraries and IRI with networking rewrite update. Trinity Desktop 0.6.2 and Trinity Mobile 0.7.3 released. Last week the team released the results of the Trinity audit conducted by world-leading cybersecurity firm SIXGEN. A security assessment of all desktop and mobile versions revealed an overall low risk of compromise from external attackers. IOTA partnered with Primority to ensure allergen food safety using DLT. 220 million people worldwide live with food allergies! New technology aims to minimize threat of potentially fatal food allergens. Through the app, consumers can scan any food product in their hands. As for the social side, the IOTA research team’s paper on Achieving Fairness in the Tangle through an Adaptive Rate Control Algorithm was accepted and presented these weeks at IEEE ICBC in Seoul. IOTA presented at Central Texas Regional Mobility Authority, TwoToTangle IOTA Meetup took place in Bolzano. Dominik Schiener gave an interview to Digitimes and participated in a very interesting discussion in the TraderCobb podcast. He talked about IOTA, the origins, growth and maturation, and how the IOTA Foundation is realizing their vision. Dan Simerman blogged on “Connecting The Human Economy and The Machine Economy” arguing IOTA is much more than a “protocol for machines.” Learn more about how it is designed to be the connective tissue between the human economy and the machine economy in IOTA official blog. A must read! As for upcoming events, the IOTA Barbecue Satellite TOA Event and IOTA Meetup in Berlin coming in July. IOTA community and ecosystem are increasing in size and this is amazing. Stay tuned for more!

Development

GitHub metrics:

Development is ongoing. Commits on public GitHub appears regularly, several times a day.

Developer activity (from Coinlib.io):

IOTA Foundation Releases the Results of the Trinity Security Audit by SIXGEN:

The team releases the results of the Trinity audit conducted by world-leading cybersecurity firm SIXGEN. A security assessment of all desktop and mobile versions (Windows, Mac, Linux, iOS and Android) revealed an overall LOW risk of compromise from external attackers. Wallet security is at the core of the Trinity team’s approach and they maintain high standards across all app areas. The audit results validate this approach and confirm the overall security of Trinity as a method for safeguarding IOTA tokens. The report can be found here.

The audit was performed in a two-stage process. First SIXGEN conducted manual and automatic analyses of encryption methodologies, sensitive data handling, network and OS interfacing, alongside emulation of real world attack attempts. And provided remediation steps for their findings (all of low and informational risk level). Then, working together with the SIXGEN team members, the Trinity team applied the suggested remediations. And finally, the SIXGEN team reassessed and retested those remediations.

“We reviewed the security of the Trinity wallet and determined it to have a low risk of compromise from external threats,” said Ethan Dietrich, CEO, SIXGEN, “It is clear the Trinity team takes security very seriously and has applied best practices throughout the wallet’s development.”

Trinity beta is available for download on all major mobile and desktop platforms.

Introducing Azimuth (previously known as NB-PoW):

A simple explanation of Azimuth (also known as NB-PoW) — A different approach to proof of work that IOTA team is working on as part of their long-term vision for IOTA. This post is the result of a collaboration among Marcos Andrade, Philipp Blum, Andrew Brough, Jake Cahill, Dave de Fijter, Sabri Goldberg, Sergey Ivancheglo, Igor Nielsen, Navin Ramachandran, and Samuel Reid.

The Bar — Explained

In Azimuth, nodes can send transactions to nearby neighbors through the air. On receipt, the neighbors make a note of which direction a transaction came from before processing it.

If, during the same round, a neighbor receives another transaction from the same direction, it will treat it as spam and ignore it.

The idea here is that, during a round, a node cannot occupy enough physical space to send lots of spam from different directions and overwhelm the neighbor.

Because nodes limit transactions by direction, they don’t need to know who their neighbors are in advance. Instead, they can accept transactions from any node as long as they don’t send them from a direction that’s already been used during a round.

An 8-second round at the bar

Why are the team building Azimuth?

When anyone is free to take part in a network, some users turn out to be dishonest. An example of a dishonest user is one that sends many transactions to a node to try and take it offline. These transactions are known as spam.

To discourage spam, IOTA uses proof of work (PoW), which links transactions to a limited resource: computational power. This way, sending spam transactions costs time and energy.

For devices such as laptops or servers that have access to the Internet and plenty of power supply, PoW is easy to do. But, devices on the IoT are often small and power-constrained, so this extra use of power is wasteful.

Instead, a way for these IoT devices to protect themselves from spam without wasting their energy on PoW is needed.

With Azimuth, IOTA can replace computational power with direction (a limited number of directions exist, so they link each transaction with a direction).

When a device uses Azimuth, it doesn’t need to do any work. The action of sending a transaction from a given direction is enough.

By using this approach, small IoT nodes can save energy, extend battery life, and avoid doing those troublesome push-ups.

Comparison of energy use between proof of work and Azimuth

Want to know more?

In this post, the team discusses how Azimuth can use direction to limit transactions. For example, Li-Fi networks could use optical sensors to detect direction. But, Azimuth does not enforce any specific implementation. For example, radio networks are free to use antennas to detect signal strength and distinguish devices by distance.

As they mentioned before, all permissionless networks have dishonest users. In the case of Azimuth, these users could try to fake their direction or their distance to be able to send more transactions during a round. This type of attack is called a Sybil attack.

Today, devices already have the means to detect some of these attacks through radio resource tests, which would be prohibitively expensive to cheat. For example, a radio device would need many transmitters, and a LiFi device would need to be large enough to occupy lots of physical space.

Client libraries and IRI with networking rewrite update:

Many things have been baking in IOTA IRI and client lib development efforts the past few months and the team feels like it is time for another update to highlight what is coming. The team goes over some of the breaking changes coming with the networking rewrite.

Client libraries

The team has released the stateful versions of client libraries back in April. Since then they have worked on improving the documentation and most recently, they have started ramping on the new MAM protocol.

MAM will also be the focus of the upcoming weeks. All the libraries — Java, JS, and Go will provide wrappers for the new MAM protocol that has been in the works for a few months now. You can take a look at the alpha of the new MAM here.

IRI

A lot has been happening in IRI. There is a version 1.7.1 coming this week. This version introduces a large number of different fixes and changes. One of the fixes the team believes should improve the issue where the node got stuck at ‘repairing corrupted milestone`. This issue has proven very difficult to debug.

Another important change in IRI is a new tip selection timeout mechanism. The node stops the tip selection process if it is not able to return a response in a given time. This is controlled by the `TIP_SELECTION_TIMEOUT_SEC` configuration parameter. The default timeout is 60 seconds.

There are also some breaking changes introduced by the unification of the behavior of boolean configuration flags. All boolean flags now require explicitly passing a parameter to make their behavior clearer. Also, in the past, it was possible to overwrite the values if you had passed the same value in both the configuration file and the CLI.

Many changes also happened under the hood. For example, the team has made the API much easier to work with in code. This will help them whenever they are extending or making changes to the APIs. They has also improved the whole release process as they aim to shorten the release cycles in the future.

A full list of changes will be available in the release on GitHub as usual.

A shout out also goes to IOTA community for their contributions. For example, Viossat changed the hashing algorithm for caching incoming transactions.

IRI networking rewrite and preparing for upgrade

Another large effort in IRI is the complete rewrite of the networking layer. The code has been rewritten from the ground up, with a lot of significant changes.

Part of the process to rewrite the networking protocol was setting up the Iota Community Committee (ICC). A group of representatives voted in by the community. The members of the ICC then set up a network on which the new code is being tested.

The team would like to release IRI with the new networking in the second week of July (July 8–12).

Read more on how to prepare for the new networking >>>

Also, you can see a description of the networking rewrite changes in this pull request.

Trinity Desktop 0.6.2 Release

The new build brings a number of crash and bug fixes. Notably, migrations from < 0.5.0 versions to latest have been fixed.

“We reviewed the security of the Trinity wallet and determined it to have a low risk of compromise from external threats,” said E. Dietr., CEO, SIXGEN, “It is clear the Trinity team takes security very seriously and has applied best practices throughout the wallet’s development.”

Download it here.

Fix: Migration not successful when migrating from 0.4.x and below to latest (#1832)

Fix: Incorrect already spent from address errors on transaction retry (#1835)

Fix: Incorrect transaction failure alert when successfully broadcast (#1835)

Fix: Quorum being conducted on transaction account syncs when explicitly turned off (#1835)

Fix: Error-related crashes (#1833)

Update: Add remote node list endpoint back-ups (#1811)

Update: Add more verbose error log messages (#1834)

Update: New translations (#1826)

Closes #1538, #1386, #1815, #1422

Trinity Mobile 0.7.3 Release

Trinity Mobile 0.7.3 (74) has been released. Like the latest Desktop version, the new build brings a number of crash and bug fixes. Notably, migrations from very old versions to latest have been fixed.

Fix: Migration not successful when migrating from very old versions to latest (#1832)

Fix: Handle exception if salt is missing from keychain (#1772)

Fix: Incorrect already spent from address errors on transaction retry (#1835)

Fix: Incorrect transaction failure alert when successfully broadcast (#1835)

Fix: Quorum being conducted on transaction account syncs when explicitly turned off (#1835)

Update: Add remote node list endpoint back-ups (#1811)

Update: Add more verbose error log messages (#1834)

Update: New translations (#1826, #1838, #1853)

Closes #1538, #1386, #1815, #1422

Social encounters

🎙Podcast: Very interesting discussion with Dominik Schiener and TraderCobb about IOTA, the origins, growth and maturation, and how the IOTA Foundation is realizing their vision.

Digitimes Interview with Dominik Schiener and Biilabs.

Connecting The Human Economy and The Machine Economy by Dan Simerman:

The IOTA technology and digital asset is a unique player in the world of distributed ledger technologies. Its forward thinking design was architected to support the unforeseen challenges of wide-scale IoT networks, quantum resistant computers, automation, and feeless payments in a digital world.

What is often overlooked is that IOTA is much more than a “protocol for machines.” Due to its design, it is incredibly well-suited to be the connective tissue between the human economy and the machine economy.

It is expected that linking the physical and digital world may generate up to 6.2 trillion dollars a year in economic value by 2025, with 40% of that value as a result of interoperability between humans and devices.

In the IOTA Foundation the team believes that any distributed ledger technology that hopes to be successful must create a level of interoperability between devices and humans in the future.

This requires an entirely new type of digital infrastructure. One that supports value transfer, data integrity, and security across hundreds of billions of market participants.

IOTA’s digital infrastructure is one of the first of its kind to embed a value transfer mechanism alongside a data transfer mechanism, with the IOTA digital asset acting as a key component in the connective tissue of the network.

The IOTA digital asset is a bridge to connect two of the largest marketplaces in the world, successfully achieving one of main failed premises of Bitcoin. Because the IOTA digital asset is feeless, it enables a plethora of use-cases that cannot be realized using existing payment processors or current blockchain protocols.

Out of the many current and unforeseen use-cases, the greatest one is the ability for humans and devices to transact with one another, building a common language for economic activity to thrive.

Without such a system, IOTA run the risk of creating more data and technology silos and re-engineering the same problems that have plagued us over the last few decades.

Because of this, the team believes the majority of blockchain protocols are not appropriate as designs for a new ‘decentralized internet.’ They simply cannot be used if you consider that the machine marketplace is not taken into account during the design process.

In the end, IOTA is so much more than a “protocol for machines.” It is a living ecosystem that enables interoperability between the digital and the physical, the human and the device, the past and the future. In a way, it is the digital infrastructure for an entirely new economy. The IOTA Economy.

These weeks events:

June 17th, 2019: IOTA presented at Central Texas Regional Mobility Authority.

June 18th, 2019: TwoToTangle IOTA Meetup in Bolzano.

IOTA presents at IEEE ICBC in Seoul:

The IEEE ICBC is a premier forum for the latest research in the field of DLT. At the IEEE International Conference on Blockchain and Cryptocurrency 2019 in Seoul, South Korea, several members of IOTA research team co-authored and presented the paper ‘Achieving Fairness in the Tangle through an Adaptive Rate Control Algorithm.’

The paper, co-authored by Dr. Luigi Vigneri, Senior Research Scientist at IOTA and member of the Coordicide team, proposes a novel algorithm to deal with network congestion and to prevent spam attacks in the Tangle. Instead of using Proof of Work with fixed difficulty (as in the current IOTA implementation), the work suggests to adapt it depending on node reputation and the number of transactions recently issued. This allows slow nodes to get their transactions confirmed with high probability while introducing a throughput cap for potential attackers.

At the conference, Director of Research Dr. Moody Alam also served as a panelist on the “Beyond Cryptocurrencies” roundtable, where he discussed the current status of research into scalable DLT, as evidenced by IOTA, as well as a vision for the role of these new technologies in the near future.

IOTA also set up a desk in the conference hall, wherethe paper and broader vision received a lot of interest from conference participants.

Having a paper accepted and presented at IEEE ICBC is no small feat, and served as a true testament to the growth and strength of the research team.

Upcoming events:

July 4th, 2019: IOTA Barbecue — How Distributed Ledger Technology shapes our future. J Hafenküche, Zur alten Flussbadeanstalt 5, 10317 Berlin.

July 17th, 2019: IOTA Meetup/Workshop in Berlin — Learn how to send data from the Bosch XDK to the IOTA Tangle via MAM even as a programming beginner — presented by XDK2MAM.io and IOTAshops.com

Finance

Information from Thetangle.org (27th June, 2019):

Wallets:

Information from Coinmarketcap.com:

Roadmap

Research & Development Roadmap: Status of projects in progress at the IOTA Foundation.

Research: Projects still in the research phase

  • Coordicide

List and solve all the problems on the way to a Coo-less IOTA. This project is mostly theoretical, and includes threat analysis, mathematical modeling, simulation, and formalization of our consensus protocol.

  • Spam prevention and detection

IOTA is looking for creative ways of dealing with FPGAs and asymmetric PoW. They are examining various options, mostly around the idea of throttling noisy neighbors. Their aim is to isolate spammers and protect the rest of the network.

  • Automatic peer discovery

Given the community input and various ecosystem projects, IOTA is taking a closer look at the security implications of auto-peering. Although this is a complex research topic, it is important for the team to formulate a well-founded position on this matter, and carefully assess the risks involved.

  • Economic Incentives

Continuing the recent efforts of Popov et al with their Nash Equilibria work, the team is analyzing the IOTA incentive model using increasingly more realistic game theoretical models. This incentive analysis plays a fundamental role in understanding the Tangle behavior and its stability when deployed at scale.

  • Consensus Algorithm spec

IOTA is working on detailed spec of the Tangle consensus algorithm, building upon the foundation set by the white paper. The main purpose of this doc is allowing public peer review of the algorithm.

  • Cryptography spec

This spec details all the cryptographic elements of IOTA: the hash functions, signing schemes, and threat model assumptions. The purpose of this document is to provide a basis for a public peer review and audit.

  • Attack analysis

This project is related to the Coordicide efforts, and involves analytical and numerical analysis of various sorts of attacks, from the simplest side-chain double spend to the more complex thug, parasite chain, and splitting attacks. IOTA is working to get numerical estimations for the cost of attacking the network, and making sure the price tag stays prohibitively in the post-Coordinator world.

Engineering: Projects under active development

  • Hub

While a number of exchanges have had great success integrating IOTA, it is certainly not the easiest task in the world. Hub simplifies exchange integration of IOTA so that IOTA can be listed in weeks, not months.

  • IRI

The IOTA Reference Implementation is the de facto model for running an IOTA node. It is the place where both community and Foundation engineers meet and collaborate to improve the Tangle, and the focus of IOTA network target.

  • Coo-free IRI

As it stands, IRI does not support the Tangle as described in the white paper. In order to support alternate consensus mechanisms, the current approach to consensus must be abstracted out so that it can later be replaced by a fully distributed mechanism. This project is separate from, but closely related to Coordicide, and this separation allows us to work on different parts of the problem in parallel.

  • Qubic

Enable smart contracts, oracles, and outsourced computation on the Tangle.

  • Trinity

While the original desktop IOTA wallet got the job done, it is not exactly the best in terms of user experience. With Trinity, IOTA brings a top quality user experience together with in-depth security audits, enabling more people to use IOTA easily and safely.

  • Local Snapshots & Permanodes

Some IOTA nodes care about the entire history of the Tangle, and some don’t. As the Tangle scales, it would become impossible for smaller nodes to keep up. Allowing for local snapshots and permanodes are the ‘two sides of the same coin’ needed to allow for either permanent and selective storage as required for a particular use case.

  • C Client

Most existing client libraries are written in higher-level languages unsuitable for embedded devices. Since IOTA is designed for the IoT, it will ultimately be necessary to support small, low-powered, embedded devices, and C is the ‘lowest common denominator’ programming language for many of these potential applications.

  • MAM+

While MAM already exists, it is missing a few key features and documentation. A formal specification and improved version of MAM leveraging public-key encryption is currently being written by the experts from the Research Institute for Applied Problems of Mathematics and Informatics at Belarusian State University.

  • Tanglescope

Performance and monitoring tools such as TangleScope allow researchers, engineers and interested 3rd parties to gain deeper insights into the Tangle’s network capabilities.

  • PoWBox

One of the difficulties in developing for IOTA is waiting for Proof of Work results for every transaction. Additionally, small or low-powered devices may simply be unable to do PoW in a realistic timeframe. The PoWBox provides an example of how PoW may simply be outsourced to a more powerful machine, and demonstrates the flexibility of the IOTA protocol.

  • iota.lib.js

The JavaScript client library is widely used for IOTA development, and serves as a reference point for client libraries in other languages.

  • Curl+

Since replacing Curl-P with the industry standard Keccak hash function, IOTA has enlisted the help of the renowned cryptography experts from CyberCrypt. CyberCrypt’s experts will take what they’ve learned from Curl-P, work to understand IOTA’s specific requirements, and design a better, more secure lightweight hash function specifically for the IoT.

You can also follow the development on IOTA Official Discord.

Partnerships and team members

IOTA-Primority Partnership: Tracking Food Allergens & Improving Consumer Safety:

Food allergy can be a fatal threat for unaware consumers. But even the most cautious allergy sufferers run a daily risk when they carefully pick their groceries.

The labels on packaged food can be hard to read and difficult to understand and they might not even be accurate. The complexity of supply chains and food manufacturing processes makes it almost impossible for our current systems to ensure the level of granularity that can mean a deadly difference for sensitive immune systems.

And that is just talking about the well-known allergens that are relatively easy to track.

There are other hidden allergens that might contaminate a given batch of packaged food. This happens when different foods share the same production line. This is not uncommon in the food preparation industry. Small traces of an allergen can then appear in the food which was supposed to be allergens free.

Peanuts in the porridge?

As an example, think about pre-packaged porridge being manufactured on the same production line as peanut butter. The porridge might still contain traces of peanuts. Such allergens and the associated risks are much more difficult to track as they can affect only a few batches and only for a limited production time.

In order to ensure food transparency and consumer safety the IOTA Foundation and Primority have partnered to collaborate on an easy-to-use and innovative approach combining the best of cutting-edge technologies.

Using the 3iVerify platform, Primority’s customers (food manufacturers), can collect accurate information related to their manufacturing chains. Such information spans the accurate tracking of used raw materials and their suppliers, as well as a detailed assessment of food production processes.

Reaching consumers with IOTA

By storing this valuable information on IOTA’s immutable distributed ledger, the Tangle, consumers will also be able to gain full insights about the allergens they seek to avoid by the simple act of scanning a barcode on just one app on their phone.

Consumers will be able to do so without sharing any personal, sensitive information, and without owning any cryptocurrency.

Thanks to IOTA’s permissionless nature, food manufacturers will be able to seamlessly share the data via feeless micro transactions without dealing with complex and costly business models and infrastructure.

Here is how it works:

IOTA-3iVerify architecture

With the consent of the food manufacturer, the information collected by the 3iVerify platform is shared on the IOTA Tangle. This is done using MAM Channels.

“MAM (Masked Authenticated Messaging) is a second layer communication protocol that allows to easily create and read data stream on the IOTA Tangle, guaranteeing the integrity of the information and protecting its confidentiality through encryption.”

A dedicated MAM channel is therefore created for each specific food product. A dedicated code, usually the same as on the corresponding food packaging, is used as identifier of the MAM channel. A digital twin is created for the product and contains the list of allergens identified in the product together with its expiry date. The expiration date is used to select the correct MAM message with the information matching the right product batch once the product label is scanned.

MAM Channels were preferred to single IOTA transactions to share product information because it allows us to easily issue, connect and retrieve updated information about the given product. By simply issuing new MAM messages for the same channel, food specs can easily be updated.

Differently, using single IOTA transactions the complexity cost of maintaining consistency across different updates might exceed the value of the shared information and reduce scalability. Particularly when the variety and quantity of food products increases.

Once stored into the IOTA Tangle this information becomes immutable and its integrity guaranteed, thus manufacturers take responsibility to confirm that shared information is the one contained in the Primority database. To confirm this, a hash of the product information contained in the Primority database is added to the digital twin.

Once on the IOTA Tangle, information can be accessed from anywhere and by anybody. For demonstration purposes Primority developed the AllergensCheck App.

AllergensCheck App

Through the app, consumers can scan any food product in their hands. Using the food barcode and expiration date, the right MAM channel is selected and all the MAM messages containing an expiration date earlier than the indicated one are fetched.

To increase safety and overcome the impossibility of current barcodes to track information at product level, the superset of allergens identified in the specific product, before that closest expiration date, is presented to the consumer.

This allows consumers to make an informed choice on the packaged food they wish to buy, by having greater real-time awareness of any food safety risk.

Watch how the app works in practice

Thanks to a decentralized system similar to the one developed, consumers do not need to share any sensitive information related to their food allergies. Such information can simply be stored inside the app and user mobile phone and used only to simplify identifying risks once the food product information is fetched.

Moreover, a similar system does not require any consumer log in into the app and information can be fetched from any app or even by using any Tangle explorer available on the web. Retailers or any third party can integrate the same logic and the available information to provide the same food allergens service as part of their offer to customers.

Furthermore, IOTA’s permissionless nature allows food app developers to access an already and always available and general purpose infrastructure for the access of required data, without the need to perform one-to-one integration with proprietary systems. This increases interoperability.

In order to evolve and facilitate the adoption of our Proof of Concept the team is currently integrating industry standards for the sharing of product information (e.g. GS1 Digital Link) and testing the use of new product codes (such as a QR-code) in order to provide more granular information at product rather than only batch level.

To leverage the full IOTA power they are now investigating the role of tokens as incentives to generate more consumer awareness by rewarding scanning activities and other desired user behaviors.

Ecosystem

XDK2MAM Status Review: XDK2MAM Phase 1 compromised to the EDF is now finished.

“But, perhaps, the more important Dashboard feature is its ability to take live data, collect it on a local database and build bundles that will be published to the Tangle using MAM transactions every n seconds.”

Welcome Alexander Lehnert to lidbot.

AKITA: Machine Economy: A community book project.

Ayni | Status | June 2019.

Articles by James JD Sutton

Social media metrics

Social media activity:

Social media dynamics:

IOTA community continues to grow, there is a constant increase in the number of subscribers of IOTA social media channels. However, the number of subscribers of IOTA official Telegram chats slightly decreased these weeks.

Check out Official IOTA Foundation blog.

Twitter — Official announcements channel. Average number of retweets is 50–100 for one post. Publications with 250–350 likes.

There is also a dedicated Engineering Twitter.

Facebook — Not active since 2019. 50–100 likes per publication, 5–10 shares.

Reddit — Threads with 10–30 comments, 50–100 upvotes.

IOTA Support — Subreddit for all IOTA related problems. 546

IOTA Markets — Subreddit for price speculation.

IOTA Stack Exchange — For the really tough questions.

IOTA Bitcointalk.org: since October 21st, 2015. Discussions on latest updates, price, social encounters etc. Last publication — on June 25th, 2019.

IOTA Family website — Basic knowledge for IOTA beginners such as: what is IOTA, how is it organized, how you can contribute, where you can buy $MIOTA on a onepager website, etc.

See also and IOTA forum.

The graph above shows the dynamics of changes in the number of IOTA Facebook likes, Reddit subscribers and Twitter followers. The information is taken from Coingecko.com.

This is not financial advice.

Subscribe to detailed companies’ updates by Paradigm!

Medium. Twitter. Telegram. Reddit.

--

--