Edge Latest articles from the team en 2019 Edge Network Technologies Ltd. All rights reserved. Tue, 23 Jul 2019 02:55:01 +0000 2019-07-23T02:55:01+00:00 en 2019 Edge Network Technologies Ltd. All rights reserved. Edge https://edge.network/assets/img/dadi-logo-colour.png https://edge.network AMA recap: July 12th, 2019 https://edge.network/knowledge/network/ama-recap-july-12th-2019 Question 1

What has been the most challenging thing to create while setting up this new brand?

Ravi Chandwani: There have been a number of challenges in replacing DADI with the new Edge brand. A key area of focus has been bringing the different App/Services under a single brand style. The existing offering felt somewhat disparate as there were a number of different styles and approaches being used. We have been and continue to work with the team to create more uniformity across the brand. Ensuring there is a stylistic and aesthetic connection in all aspects of the brand. Finalizing the logo itself has also been challenging. Ensuring the logo resonates with the target audience and sits comfortably alongside competitors whilst also having standout and impact. It is important that it is both distinctive and aesthetically pleasing. Something I feel we have achieved.

Joseph Denne: I’d say that you’ve definitely achieved! Super happy with the work

Follow up: Hi Ravi. What did you do to backup this feeling to make sure it’s not just your feeling and effectively something affecting the brand image? How much third-party input was taken for the rebrand? Focus groups, interviews, other designers’ input?

Ravi Chandwani: We’ve spent a few months on the design itself and moved - sometimes frustratingly! - through a wide number of variations and iterations. This included a significant amount of third-party input, including from customers and others within the crypto industry.

Question 2

How long has you been working on the rebrand to Edge?

Joseph Denne: Since October last year! So, we’ve been moving towards it for quite a while - starting with the naming of the network, and then through the reduction in use of DADI in comms, finally getting to the point of being able to announce it, and then of course formally launching it next week.

Question 3

In your opinion, what makes the brand identity that your team has created unique?

Ravi Chandwani: It is difficult to pinpoint any brand out there that is completely unique. Generally, there will be a connection between brands in a similar space which is what ensures they can communicate effectively in the wider industry. However, the intention with the new brand was to create something which differentiates us from our competitors and demonstrates a fresh approach to this space.

Key points of the brand are a focus on clarity and simplicity. We are communicating some complex ideas in a clear and concise manner. This is done through copy, but also through the overall aesthetic. Reduced colour palette, white space and a focus on minimalism. Combined, these qualities should give us stand out from the crowd.

Question 4

Is there any specific message or emotion you wanted expressed when designing this new brand?

Ravi Chandwani: The message we want to convey is clarity and simplicity, ease of use and accessibility to a complex and cutting-edge technology. This is achieved through refining and minimizing the visual and textual content. Lots of white space, giving content room to breathe as well as lighter font weights and a reductive palette should help to communicate these ideas. The brand will continue to develop as more elements are added to the visual language. We are taking an iterative approach so we can be flexible enough to accommodate new developments whilst ensuring that everything retains brand recognition.

Question 5

Will this new style also be used for the products you make together with Blond and how will this collaboration be in the future?

Ravi Chandwani: The new brand will definitely feed into the new products developed with Blond. This will be through the product design as well as packaging. This has been part of the thought process in developing the new brand look and feel. We are excited to see how this develops into 3 dimensional objects in the future.

Question 6

Can you tell us about the reason for the rebrand?

Joseph Denne: DADI was right for us at the beginning of our journey: It communicated the ambition of the technology, and it was a memorable name. However, when addressing a market as part of the proposition as now stands it lacked clarity. It’s also worth acknowledging that it wasn’t universally liked too.

Question 7

How do you comment the modified picture showing $EDGE being #7 on CoinMarketCap with your investors down 90%?

Joseph Denne: Well, #8! Contributors purchased in Eth. $DADI is down ~62% in Eth since the token sale. Eth remains down 76.46% over the same period. I’m not trying to paint a rosy picture, but it’s worth calling out the facts. In a very difficult market, our token price has fared reasonably well. The illustration is just that. It’s playful and reflective of our ambition, nothing more.

Question 8

What does a clean start with the new brand mean for the team and the future?

Joseph Denne: Well, we see Edge as central to our go to market strategy. It’s all about marking the platform out as the leader in the field of edge computing and edge networking. It’s a more grown up brand, and one which clearly communicates the proposition. We believe that this clarity of purpose will help to carry us forward, both internally and with the broader market.

Question 9

Do you think it will ever be super intuitive to create a website on DADI for those who are not code savvy? Like a Wordpress website, for example.

Arthur Mingard: There’s a big difference between wordpress.com and wordpress.org. And between either of those and Wix. Edge is all about network level services. This will eventually include a 1-click deploy marketplace for different technologies, which will lower the barrier to entry significantly.

What we’re doing with the web services under a new brand is much more closely aligned to a Wordpress, in that it is a SaaS proposition designed to lower the barrier to entry. In time we expect this to evolve further, with versions of the offering more closely aligned to the likes of wordpress.com.

Joseph Denne: That’s a yes. But it’s not our core focus in Edge right now.

Question 10

How does the DADI rebrand impact the relationship with the foundation?

Joseph Denne: It doesn’t. The DADI Foundation is also rebranding, and will be known as the Edge Initiative. The go live date for this isn’t confirmed yet, but we expect it to follow on quickly from the launch of Edge.

Question 11

Will DADI support the QUALCOMM Snapdragon Secure Processing Unit feature?

Arthur Mingard: This solution is similar to Intel SGX - we really support the introduction of this sort of feature to all chips on the market. We’ll be watching each version into maturity and adoption, and if they stand up to scrutiny, they’ll almost certainly find their way onto the roadmap.

Question 12

Do DADI customers know that they are migrating services to decentralised services/network? Is this something they like, does DADI advertise it proudly or is it only the cost-saving aspect that customers like? Could you tell a bit what makes customers move and how you gain new customers?

Joseph Denne: Yes, this isn’t something that we’re doing by stealth, although we are doing it slowly as we continue to test and improve the mainnet. And yes, we’re very proud of the technology. The strongest selling points are performance (speed of deployment, speed of delivery), security, transparency and price.

Question 13

Why is it that the response headers of thedecentralisedweb.com seem to return a DADI-host only the first time I load the page then after a refresh those response headers or no longer there?

Arthur Mingard: In CDN, once an object has been generated and moved in to the cache of a Gateway, the original node isn’t participating in the request, which is why the header changes. We are working on updates that will include a breakdown of all of the nodes that participated in a request, regardless of cache state.

Question 14

Have you considered onboarding users from other Crypto projects who need to run nodes, like Tierion?

Joseph Denne: We have been working with a handful of partners on this. So yes! I’m not familiar with Tierion, but will take a look.

Question 15

When can we use Edge like we use AWS. Obviously not all the features, but as a developer, if your offering is CDN, when can I just sign up and get going without any hand holding?

Joseph Denne: You’re correct in identifying this as a key milestone in the go to market. We are working the interfaces for the first services now, and expect to be moving them to live in Q4.

Question 16

It has now been over a year and a half since $DADI has been listed on a reputable exchange. Clearly, not enough has been done on this front since projects which have only launched in Q3/Q4 2018 have already been listed on the likes of Binance or Binance DEX (REN, Loki, Grin to name a few). When can we expect some positive developments on this front? It would be great for brand exposure and legitimacy.

Joseph Denne: We agree that broader reach and liquidity would be beneficial. And in fact, we see it as being essential as we build out the network. This isn’t something that has been ignored, but it’s also unfortunately not something that we can talk about at the moment.

Question 17

If I want to use DADI as my CDN provider, have you implemented some kind of DRM so that only authorized users can see the content and restrict authorized users from uploading content to Facebook or some other platform?

Arthur Mingard: User account management is something that typically exists within the application that makes use of a CDN. There are however plans for single use cryptographic keys within the solution.

Joseph Denne: So, for example, you could choose to lock down certain content and make it available only to authenticated users within your app. Those users would be given links (or the content would be embedded with) URLs which would expire after a set amount of time has passed.

Question 18

It is understandable not wanting to name certain clients using/interested in the network. However, I find this to not be an excuse for more clarity on network stats. It was mentioned that more of these will be available with the new website. Can you specify which stats will be supported?

Joseph Denne: We’ve started to provide more detail on this front and will continue to do so. We are working on client success stories and will be publishing ever deeper levels of data as we move forward and also as we continue to evolve the network explorer.

Question 19

When can we expect the updated roadmap and updated website (please specify what coming weeks mean)?

Joseph Denne: As I think I mentioned in my last weekly update, next week! (And if I didn’t, I meant to!)

Question 20

Self onboarding is one step into decentralization so I guess there will be no restriction and the free market will regulate the node count over time. Is this assumption correct?

Arthur Mingard: In the fullness of time, yes, that is correct. In the first instance self on-boarding will be gated on a first come first serve basis. The reason for this is that we need to monitor and assess performance as the network grows.

Question 21

Can we (as founding node holders) also join the self-onboarding? And how many raspberry PIXs will I be able to run following the launch? (I have a 5-device cluster set up already waiting idle)

Arthur Mingard: Yes, you can. How many devices you can run is limited only by your connectivity and the subsequent performance of the devices in resolving tasks in Gateways job queue.

Question 22

When will the first staking for Gateways and Stargates take place?

Joseph Denne: September for backbone rentals. With some potential for onboarding to start sooner.

Question 23

Will Stargates have the ability to censor specific sites, or will it be up to DADI only?

Arthur Mingard: The right to censorship isn’t something that we believe in as a team, however we have to respect the rule of law within those regions in which we operate. How this is handled within the network when fully decentralized is an open question, but we expect to be handled at Stargate level and on a region by region basis.

Question 24:

How is the Technology Partner programme going? Is this still a thing?

Joseph Denne: It is, yes, although it has taken a backseat to core development in the past few months. We expect to be picking it up again in earnest towards the back end of this year.

Question 25

Is the software on the FNs stable now? Those with original software have the same as the ones with new SD cards?

Arthur Mingard: The stability in the Founding Nodes relates to the update process rather than the node software itself. Because we need support for scale in the network, we need support for unattended updates. This is to support a broad array of devices and to remove the need for a high level of technical understanding to contribute. The auto update process has been one of the most complicated portions of development, other than securing the node software, and this has led to a number of issues with the update process. We see this as par for the course and given the cutting-edge nature of the platform it’s really not that surprising. This is also why we have a backbone of devices in the network: it allows for testing within the Founding Node programme without impacting live services.

Question 26

How could the network withstand an organized attack? (scrape the web for sites running in DADI network, DDOS all those sites simultaneous)

Arthur Mingard: Network scale is a big part of the answer here. But we’re also working with partners to build scrubbing centers into the backbone of the network, which will go a long way to protecting us from DDOS attacks.

Question 27

Does DADI have any international expansion plans?

Joseph Denne: Yes, these are being worked on. As soon as there’s something to share on this front, we will do so.

Question 28

I heard DADI was working on OEM hardware too. Does this involve design and production of PCB schemes and boards?

Joseph Denne: It does. We’re very, very early in this process and are not ready to announce anything on this front yet. Consider it an R&D line, which may or may not come to fruition.

Question 29

How did the network upgrade go? Can we expect a thorough report of the process?

Arthur Mingard: Well! But it’s ongoing and we have changes to telemetry still to make. This may necessitate a further update to Founding Nodes. And yes, I’ll be writing and providing a full update on the process soon!

Question 30

With the branding done, what will the next main challenge be for Ravi and his team?

Ravi Chandwani: The branding process is iterative, so we will continue to work on other aspects of the brand which as yet have not been seen. There are a number of strands which are being worked on, including iconography, illustrative elements as well as the product design. We will continue to develop these with a strong adherence to the overall brand aesthetic and tone. Some of this you will see with the launch of the new site, and some will be added over time.

Joseph Denne: It’s worth noting that we’ve made some additions to https://brand.edge.network as well, and that this will be kept up to date as we go.

Question 31

Can we have a whitelist for Telegram to allow admins to let trusted members of the community post links and images?

Joseph Denne: Yes! We’ve figured out a way to enable this in our bot, and will be rolling it out to our own channel - and to the other crypto projects that our bot power - next week.

Sat, 13 Jul 2019 15:30:00 +0000 5d29f6f6a26508082aa55d3a Bolaji Oyewole 2019-07-13T15:30:00+00:00
Weekly update: 12th July, 2019 https://edge.network/updates/announcements/weekly-update-12th-july-2019 My goodness it’s been hot this week ☀️ Averaging 30º in London… and it feels a hell of a lot hotter inside without air conditioning.

Here’s hoping the sun stays put through the weekend.

We had an AMA today (transcript here), so this update will be quick.

The network engineering team spent the week pushing a major update to mainnet live. There’s more to do and there have been a few hurdles, but in the main it went off smoothly.

Arthur will be posting an article about it early next week.

We are continuing work on the new site for edge,network, which is scheduled for live next week.

The team also made an significant update to API to store collection schemas in the database, rather than the filesystem. This reinstates endpoints for creating, modifying and deleting collections and includes backwards-compatibility with file-based collection schemas using something we call “collection seeds”. This will allow us to create interfaces for content modelling within our SaaS proposition.

They also removed the version portion of collection URLs in API, simplifying the URL used by data consumers.

A list component was added to our interfaces, allowing editors to insert, update and reorder entries within a field.

And they made a start on the migration of our existing documentation to reflect the change in focus as we roll out the Edge rebrand.

We made a number of updates to integrations with Signify (a fraud prevention system) and Nimble (a streaming media platform) for one of our customers.

A number of regional offices at one of our larger customers have expressed interest in migrating to the latest build of our platform. We’ll be following that up next week.

+We had a handful of meetings with prospective customers for the network

+We put a lot of flesh on the bones of our strategy for scaling the network effectively as part of the core approach for our go to market

+We delivered integration docs for CDN to a new property that will be moving to the network

And that’s it from me! I hope you enjoy your weekends 🙂

Fri, 12 Jul 2019 17:30:00 +0000 5d2c3f51f094f707c249e155 Joseph Denne 2019-07-12T17:30:00+00:00
Introducing Edge https://edge.network/updates/announcements/introducing-edge Edge represents the culmination of months of work, and synthesises everything that we know about edge computing, together with the core principles of our network in to a coherent and powerful brand.

The core components are presented below, and you can access a full introduction to the brand here: https://brand.edge.network

Logo concept


Edge levels the playing field. It enables everyone to contribute, be part of, and access a network that exists all around us in the devices we use day-to-day. Edge simplifies the complex, and by decentralising the network creates a level of equality and functionality that surpasses any current offering.

Our logo is derived from these ideas, communicating them in a balanced, aesthetically engaging mark. It displays uniformity and simplicity. A perfect circle denotes equality, clarity, ease of use and accessibility. The circle is also a representation of the individual nodes which make up the network.

Reference to the ‘power symbol’ communicates the idea of democratising computational power, bringing it closer to the user utilising it in the devices that surround us. It’s green because it is always on.

The ‘e’ is edge.



The Edge icon is the foundation of the logo. It is developed from a perfect circle conveying equality and balance. The mark reads as a lowercase ‘e’, whilst also referencing the power symbol.

Using a refined line weight it is both bold and elegant, and it is instantly recognisable The colour is striking and engaging and will ensure standout amongst the plethora of cryptocurrency brands.

The Edge icon is a standalone symbol used in isolation when the wordmark is not appropriate or relevant, for example as a currency symbol.



The Edge wordmark is the primary logo for the brand. The wordmark is constructed using the ‘e’ icon. The ‘g’ is the same shape flipped and rotated. The ‘d’ is derived from the same circular shape. This creates an even, balanced mark which conveys the brand ethos in a clear and elegant way. The four linked circles can be seen as nodes, connected across the edge network.

Tue, 09 Jul 2019 16:30:00 +0000 5d2457bcf094f707c249e14c Ravi Chandwani 2019-07-09T16:30:00+00:00
Mainnet upgrade, July 2019 https://edge.network/knowledge/network/mainnet-upgrade-july-2019 Scale

Important in the networks growth is its ability to accept an increasing number of Hosts without compromising the speed in which vital coordination components calculate and synchronise topology.

Initial builds of the network manifest distributor operated on geographically spread Consul servers, adjacent to the Stargate services. Whilst decentralised in respect to their lack of a single point of failure, these nodes required consensus on all operations, including healthchecks, key/value updates and service metadata. Put simply, if a Host were to tell its nearest Consul server that it was up and healthy, the same data would need to be fully propagated before the write was considered successful. Operationally, this latency just doesn’t scale, so we started to see some failing health checks whilst telemetry painted a far more serene landscape.

One of the largest single changes in the upcoming release is a shift away from globally propagated service data in favour of a multi datacenter approach, more akin to your typical VPC. The services continue to register with their local Consul server, operating alongside the nearest Stargate, but that’s where the syncronisation stops. Consul offers a little flexibility in the way it connects to its peers, so whilst a multi datacenter setup does not share service data globally it does permit access by proxy – something the network relies upon on rare but vital occasions.


When debugging the latency experienced by the single data center configuration the team discovered a number of performance improvements to the way service data is stored. Whilst the refactors were complex, the result can be simplified to two key areas:


The first health checks consisted of periodic writes to a key/value directory on a per-device basis. A pruning process existed to remove services that exceeded the maximum TTL.

The latest iteration of the health check process now uses Consul’s inbuilt healthcheck methods, including GRPC standard health endpoints for Stargates and Gateways, and TTL checks for Hosts. This meant that we were able to completely remove the key/value data which had a significant reduction in latency due to the way the Consul propagates service health.


Until recently all devices wrote information such as their current connections and build digest to Consul key/value. Whilst it appeared to be largely an efficient method, benchmarking showed us that storing this data within the core Service metadata reduced the number of Consul requests by other services. If, for example, a Host wanted to find the closest operational Gateway it would first need to make a call for all services of type ‘Gateway’, before individually requesting the KV metadata of each Gateway before an informed preference could be made. By moving this data to the Service itself, what could be a query of 1+n became simply a query of 1.


ACL tokens were initially created to offer distinguishably different permissions to the three core services, with the Host application having the lowest level of trust, and the lowest staking. The Host token had read-only access to non-sensitive information, and a small amount of write access to its own part of the network manifest making it almost impossible to use it for evil.

A single ACL token for all Hosts does come with a downside, and one we discovered when migrating to multi DC on testnet. Firstly, Consul doesn’t allow ACL migration which poses a risk when embedding a single token into the Host. It also means ACL for a single machine cannot be revoked should an account be deactivated.

The next release will include a refactored method for retrieving ACL tokens to use with Consul, which required the introduction of Vault, an accompanying service which extends Consul ACL with policy templates which act as a blueprint for the onboarding mechanics ahead of self-onboarding.

What you need to do?

If you’re lucky enough to have a Founding Node in operation you’ll need to have it up and running between the 8th and the 12th July. During this time we’ll be issuing a unique token to the machine before we switch off the old ACL and migrate the network over. Don’t worry if you currently have a support ticket open or your device is disconnected under our instruction – we will reach out to you individually after the update and get you back up and running.

Sat, 06 Jul 2019 15:30:00 +0000 5d20bc9baa8a2c080bee2817 Arthur Mingard 2019-07-06T15:30:00+00:00
Weekly update: 05th July, 2019 https://edge.network/updates/announcements/weekly-update-05th-july-2019 Today’s update is going to be short and sweet, as we’re mostly head down building in support of the major update to mainnet next week.

The network team completed the mammoth task of configuring the deployment scripts for the update.

This includes the completion of the final parts of the network-sync scripts.

The network explorer was updated to patch the duplication issues that we have been seeing. A further build has been created with our new brand and fonts in place, ready to go live along with our new site.

We’ve completed and released updates to Agent and Host which are fully compatible with the new Vault ACL policies. This includes a refactored service package which dramatically reduces the amount of data to be written to Consul.

Stargate and Gateway have been upgraded with a new service package which fixes a bug with the service de-registration routine (which had caused orphaned services after reboot), and added vault configurations to the Jenkins deployment scripts.

API is being refactored to store collection schemas in the database, which will enable the creation and modification of collections directly within our interfaces, which is a critical step as we move towards a full SaaS proposition for our web services.

This work is now 80% done.

A list-type field for the interfaces is also in progress (see: https://github.com/dadi/publish/issues/389), which is in final stages of development and should be rolled in early next week.

Ravi and his team have been flat out on the Edge brand update, rolling content updates through the new site, applying the brand to the explorer and working through supporting collateral. It’s looking awesome.

I had planned to show you the work this week, but have decided to hold it back a few days to allow time to build out a page in support of the brand itself (rather than show you internal brand guidelines in documents).

This will be ready next week, and will be made available on brand.edge.network

We made significant progress migrating an existing customer’s data layer to API, which is a big step toward full migration to the network.

Tiipr is on target for being dev complete w/c 15th July, at which point we will start live testing in the network. The team there is expecting to go live with an MVP in August. I’ll let you know when it’s available to play with.

Our relationship with the PPA has led to a number of new leads. We have confirmed the dates and attendees for the product workshops that we will running with them in the coming months.

We started early stage discussions with a new partner, which should open up a good sales channel for network services.

We confirmed our attendance at the Great British Business Show in November (http://www.greatbritishbusinessshow.co.uk/), where David Wilde will be speaking about Edge, blockchain and their applicability to Government.

Finally Paul met with a number of car manufactures and automative publishers at Goodwood. He spoke to them about our technology to explore the potential for future engagement.

And that’s it! Enjoy your weekends.

Fri, 05 Jul 2019 17:30:00 +0000 5d248ba4a26508082aa55d37 Joseph Denne 2019-07-05T17:30:00+00:00
Month in review: June 2019 https://edge.network/updates/announcements/month-in-review-june-2019 June has been another very busy month for us as we have been preparing for a major update to mainnet, working flat out on our rebrand and finalising our roadmaps for the next 12-18 months.

Year to date commits? 3,483 (+357 in June) 💥

DADI is being rebranded to Edge – a move designed to help growth in the network by focusing on core network services. The team is working to launch Edge in the coming weeks: a new site, an update to the explorer, a rename of our ticker to $EDGE, and a clear focus on network-level services.

We will be sharing the brand itself this week.

Aside from the news of our rebrand, highlights this month include our attendance of the PPA awards, our attendance of the Cannes Lions, preparations for the coming mainnnet update, and sustained ROI for network contributors.

We turn six years old on the 08th of July! Quite a milestone.


  1. Business update
  2. Network status
  3. Development report
  4. Highlighted customer stories
  5. The Foundation
  6. Ask us anything

Business update

We have around 47 active deals in our new business pipeline with a combined value of over 6.2 million USD.

We met with eight new prospects in May. These ranged from security specialists to startups, publishers to healthcare businesses.

We attended and presented at the PPA awards:


It was a really positive evening for us – 20+ new conversations have been opened up on the back of the event.

We finished defining the content of the series of workflow Workshops that we’re running with the PPA, plus we’ve also confirmed a set of new product development sessions in September. These are designed to aid with customer engagement and new business.

We were also in Cannes for the Cannes Lions, where we picked up a number of promising leads.

Joseph met with David Wilde to plan an approach for local government. They also discussed the detail of his ongoing engagement with the project, covering speaking arrangements, articles and an approach for central government.

IP protection

We met with our patent lawyers for an update – there has been a lot of progress made, and we expect to have completed the process in the next few months.

This will be an important milestone for us as it means that we will be in a position to fully open source the network codebase.

Pursuing patents for the core architecture and components of the platform is important because it provides protection for the entire community by putting a level of barrier in place to competition, which should help to establish the Edge network as the protocol for edge computing.

We also submitted fourteen trademark applications related to Edge.

Roadmap updates

We released a preview of our roadmap update, covering some of the key updates to the Edge network for the next 12-18 months.You can access the preview here: https://dadi.cloud/en/updates/network/roadmap-updates/

The full version will be released with our new website.

In the news

The future of our web services

We have made huge strides in the definition of what will become a stand alone SaaS proposition for our web services. We are breaking out the web services in the network and will be offering them under a new brand and on a new domain. The reason for this is to allow us to focus the network on network-level services, better supporting its go to market. This approach also means that we don’t lose the momentum and investment made in the web services to date, and will present a stand alone entry point to use of the network (use of the web services under their new brand will deliver revenue directly back to the network).

This will be announced formally when the full branding work for the proposition has been completed. We expect this to be in July.


Earnings in June returned an annualised 56% against the Founding Node proof of stake and we expect the uptrend to continue as more traffic moves in to the network.


Earning reports and payouts for June will happen in the first week of July.

We have gone a long way to enhancing and validating pricing for core services. These will be published on our new site in July, and include the addition of DNS as a service. As we continue to grow network use focus will increasingly move to the optimisation of the economics of the platform, particularly the balance between price and demand, earnings and network growth.

Our goal is to establish a self contained ecosystem that ensures network capacity alongside competitive market pricing for customers of the network.


Moses Skoda joined us as an engineer. He will be working closely with Eduardo on the future of our web services.

We are still looking for an experienced technology sales director. If this sounds like the right job for you, please get in touch.

Network status

Our mainnet continues to grow, with significant additional traffic pushed in to the network in June.

The mainnet maintained 100% uptime for the month, with the switching of devices in and out of production in rapid succession tested and shown to have no impact on performance, proving the architecture for Hosts. This means that we expect to be in a position to lower and potentially even remove the minimum uptime requirement for Hosts in future.


Key stats

Stat Value Description
Uptime 100% The mainnet achieved 100% uptime in May
Nodes online 356 Node capacity remained steady. Additional Founding Nodes are planned for release in July/August
Network reach 54 countries There are Hosts online in 54 countries
Stargates 21 All non-earning and under the control of the core team
Gateways 18 All non-earning and under the control of the core team
Hosts 317 All earning and operated by the community
Compute units 1,268 Edge one units: low-level compute capacity for web-based processing (websites, APIs etc.)
Edge storage 9.49 TB Long term object storage
Edge cache 844.70 GB Short term caching

Development report

The network engineering team were flat out throughout June:

They completed most of the final components of network-sync, the service the network uses to persist device data now that the network manifest is ephemeral. This includes recording the duration of device sessions and metadata, which is important for payout calculations in the next phase of development.

They have also been closing out final changes to Vault ACL, finishing the month with an ACL onboard script that’ll be used to automate the founding node migration away from the current ACL implementation.

API’s test suite has been extended even further. All of the 15,000+ database operations generated from the ~1,000 unit tests are now stored as a snapshot and replayed against each data connector module. you can see the new testing module at https://github.com/dadi/test-tools and an example of it in action at https://travis-ci.org/dadi/api-mongodb/jobs/551251808

Our code quality tools have been improved with consistent linting and code formatting (https://github.com/dadi/code-standards) now applied to Publish and API.

The team have built and released automated deployment for Gateways on test.network and have also introduced the first full build of Vault, a vital new component for the next iteration of network ACL. Account registration for ACL was also progressed. This is the last core component required before we start the much anticipated mainnet release.

A bunch of work has been done to simplify the way that ACL is passed between Agent and Host, which makes the self onboarding process faster, more lightweight and more secure.

We have been hard at work defining and building out the Edge DNS layer, and completed the addition of support for AAAA, CNAME and TXT records.

We completed and successfully deployed auto SSL generation and distribution to the network, so SSL is enabled by default and is now free for all network customers. You can read about this here: https://dadi.cloud/en/knowledge/network/edge-ssl/

API update

API version 5 was released! Release notes as follows: https://github.com/dadi/api/releases/tag/v5.0.0 And documentation can be found here: https://github.com/dadi/api/releases/tag/v5.0.0

Publish update

We’re around 95% through a conversion of Publish to React. The approach here is designed to better align our interfaces to one of the webs most active communities. It also opens up a lot of new functionality for our interfaces.

A network ready build of Publish is also in testing.

Highlighted customer stories



Ecohustler went viral. One of their articles (https://ecohustler.com/article/one-corporation-to-pollute-them-all/) was picked up by just about every social platform you can imagine.

At peak the site was receiving 1k+ concurrent connections. That’s an increase in traffic of 16,566%. Pretty significant!

Uptime during the stampede? 100%

The Foundation

Our charitable foundation attended Rightscon in Tunis, where they met with other organisations and charities to discuss how technology can be leveraged to properly support human rights around the world.

They are continuing to develop a series of training sessions for human rights organisations. If you would like to volunteer to help them deliver the pilot series, please reach out to Jennifer - the CEO of the DADI Foundation - directly on: jennifer@dadi.foundation

They will need half a day of your time. You can be based anywhere in the world, and you’ll earn a warm sense of well-being knowing that you’re helping to make the world a better place 🙏

You can read more about the foundation here: https://dadi.foundation

Ask us anything

The core team is active across all of our community channels, and we operate on the basis of as full a level of transparency as possible. You can always reach out to us. If you don’t get a reply to a question right away, our community moderators will add it to their backlog for the next AMA session.

On which, you can read the transcript of our last AMA here: https://dadi.cloud/en/knowledge/network/ama-recap-june-07th-2019/

Our next AMA will take place on Friday the 12th of July.

The session kicks off at 2pm UTC on Telegram, Reddit and Discord: get you questions in now.

Weekly updates

I write updates for our community covering all aspects of our work. You can access the updates for June here:

Sun, 30 Jun 2019 17:00:00 +0000 5d18de108896c3081cdd42a1 Joseph Denne 2019-06-30T17:00:00+00:00
Weekly update: 28th June, 2019 https://edge.network/updates/announcements/weekly-update-28th-june-2019 Happy Friday all 👋

We’ve just released a preview of our roadmap update, covering some of the key updates to the Edge network for the next 12-18 months. The full version will be released with the our new website, but for now you can access the preview here: https://dadi.cloud/en/updates/network/roadmap-updates/

We met with our patent lawyers for an update early this week. There’s been a lot of progress on this front, and we expect to have completed the process in the next few months.

This will be an important milestone for us as it means that we will be in a position to fully open source the network codebase.

Pursuing patents for the core architecture and components of the platform is important because it provides protection for the entire community by putting a level of barrier in place to competition, which should help to establish the Edge network as the protocol for edge computing.

The third party report on the network will be ready ahead of moving the code base to full open source.

While the PPA site is still not live, it is very close. We’re waiting on final content amends before it gets cut over to live, which with luck will be next week.

We’ve been contacted by and are exploring a research opportunity with an aerospace company.

We kicked off planning for a presence at a major event in London in November. More details in the coming weeks.

The network engineering team have been pretty much flat out:

They have completed some of the final components of network-sync, the service the network uses to persist device data now that the network manifest is ephemeral. This includes recording the duration of device sessions and metadata. It’ll be important for payout calculations in the next phase of development.

They have also been closing out final changes to Vault ACL, finishing this week with an ACL onboard script that’ll be used to automate the founding node migration away from the current ACL implementation.

They have been working on finalising the roadmap updates and timings, as well as migrating data out of consul ahead of the conversion to multi DC.

API’s test suite has been extended even further. all the 15,000+ - !!! - database operations generated from the ~1,000 unit tests are now stored as a snapshot and replayed against each data connector module. you can see the new testing module at https://github.com/dadi/test-tools and an example of it in action at https://travis-ci.org/dadi/api-mongodb/jobs/551251808

Our code quality tools have been improved with consistent linting and code formatting (https://github.com/dadi/code-standards) now applied to Publish and API.

The team also released the first release candidate of Publish v3.0 (which if you remember from previous updates is a React build).

And they closed out a series of Publish issues (https://github.com/dadi/publish/pulls?q=is%3Apr+is%3Aclosed).

And finally…

We are going to be rebranding DADI completely. You can find out more here:


Branding and design will be previewed early next week.

Enjoy your weekends 👊

Fri, 28 Jun 2019 17:30:00 +0000 5d18c05c4f006007f83c0813 Joseph Denne 2019-06-28T17:30:00+00:00
Announcing our rebrand https://edge.network/updates/announcements/announcing-our-rebrand We have been building networking software designed to operate in spare capacity of the devices all around us for several years now, and have deployed the world’s first operational edge computing network.

Running on edge.network, the platform’s architecture enables a multitude of devices - including low-powered and embedded systems - to operate as clusters of computational and storage capacity, providing services that operate as close to the point of need as possible.

For users this means a faster and more responsive experience. For customers cheaper prices, faster build and deployment times, and a huge reduction in ops requirement.

Network operators can contribute their existing estate to the network, enabling delivery within their own networks and reducing north-south transport, effectively converting it to east-west transport between devices and end users. This has fundamental implications for network performance and cost.

Andreessen Horowitz believe that cloud computing will be taking a back seat to edge computing — and that we will very quickly see the majority of processing taking place at the device level. (Watch now: https://a16z.com/2016/12/16/the-end-of-cloud-computing/)

The total addressable market for edge computing is infinitely larger than where we are today. The proliferation of connected devices is moving from a world of billions of connected humans, to one of trillions of connected devices.

Our vision is the Edge network as the standard for decentralised computing. An infinite network of nodes, directly addressable and usable by anyone. A governance system free from individual or multinational control, organised by a Decentralised Autonomous Organisation.

Rebranding to Edge places us at the heart of this paradigm shift.

Fri, 28 Jun 2019 16:30:00 +0000 5d1633a63ea4e008252ed45e Joseph Denne 2019-06-28T16:30:00+00:00
Roadmap updates https://edge.network/updates/network/roadmap-updates 1. Brand update

Start: already started / Release target: mid July


We are refreshing and repositioning our brand to focus on core network services. As supporters already know, we’ve shifted focus from web services to focus on the network itself in much more depth, opening it up for others to build on and work with. Updating the brand itself is a key step in this evolution.

The brand update includes the release of a new version of our site.

2. Multi DC, Vault, ACL and DNS

Start: already started / Release target: 11th July


Our next major update to mainnet is due very soon, and the team has been preparing for it for weeks. The update brings fundamental changes to the structure of the network, introducing the concept of regionality, per device session management and ACL, and rolling out Edge DNS as the second fully live service in the network. The changes here are on the critical path for both scaling out network services and for self-onboarding.

3. DNS updates

Start: already started / Release target: 11th July


The DNS layer in the Edge network now has full support for all major record types, as well as enhanced functionality such as geo-routing and weighting. This update provides us with a beta build of the customer interface set for us internally, which enables us to migrate the domains that we are currently managing with Route53 (AWS) directly to the network. There are well over 100 in all, so this is a fairly major milestone for the network.

4. Network CLI

Start: July 15th / Release target: August 31st 2019


The network CLI is a command line interface for interacting directly with network services. It communicates with Stargates to enable the deployment and management of service in the network, including device configuration for self onboarding. It is built on the building blocks of the existing CLI (https://github.com/dadi/cli)

5. Self onboarding: Hosts

Start: July 15th / Release target: August 31st 2019

Self onboarding is the point at which we are able to open up the network to contributions beyond our partners and Founding Nodes. It is the point at which we can begin to truly scale network capacity. As project supporters will know, the security challenges related to the support of an ad-hoc set of untrusted devices is highly significant. The solution in the Edge network relies on a consensus mechanism that operates at DNS level and across all nodes in the network. This is perhaps the most complex component of the network, and is of fundamental importance.

In the first instance self-onboarding will be gated and limited to Linux devices. This will be broadened out as we gather performance data and scale usage in to the new devices set.

6. Earning automation

Start: July 15th / Release target: August 20th

Earning automation is the point at which payouts move to a fully automated footing in the network. For this update payouts will remain monthly, automated against earnings and displayed within contributor dashboards. Over time the frequency of payouts will increase, with the ultimate goal of getting them to as near to real time as possible.

7. Edge storage completion

Start: Ongoing / Release target: October 1st 2019


Edge storage provides object storage and Edge caching within the network. This update marks the completion of testnet benchmarking in preparation for mainnet release. Storage shards files across multiple hosts, building in a high level of security in that no one host stores the complete image of a single file. Object storage is long term persistent storage, with multi-region distribution and file recovery baked in. Edge caching makes objects addressable via HTTPS, and stores them in memory on Gateways for a very short period of time, stepping down cache in memory on Hosts for a slightly longer time frame, ultimately falling back on Object Storage when the cache expires.

8. CDN conversion to Go

Start: ongoing / Release target: TBC


The conversion of CDN to GO is all about enhancing performance and reducing the footprint of CDN within Host devices. The current build of CDN in node is some 600MB+ – a large footprint for a network app by any measure. The conversion to GO is targeting a footprint of sub 10MB.

9. Backbone rentals

Release target: September


Rentals of backbone infrastructure are designed to enable individuals to take responsibility for Stargates and Gateways ahead of self onboarding for those node types, and to make the running of a Host as simple as possible. Rentals will be offered to our biggest supporters in the first instance, and will ultimately be opened up for everyone.

10. Edge for mobile: iOS

Start: ongoing / Release target: TBC


The mobile build of Host is in heavy R&D. The concept is to enable an SDK for app developers that embeds Host within existing apps, offsetting their infrastructure costs by contributing to the network. We are also working on the build of a dedicated - and earning - app for the network.

11. Full Open source

Release target: September/October


We are in the midst of producing a series of patent applications for the core network. This is designed to protect the core IP of the network for the benefit of the whole community, providing a barrier to entry to other organisations in the space, and in so doing promoting the Edge network as the protocol for edge computing. This is a drawn out process that has been ongoing for a long time. However we are nearing the end and expect to have filled in the coming few months. As soon as this is the case we will be able to fully open source the code base for the network.

12. Web services migration

Release target: July/August

We are in the midst of breaking the web services out of the network to enable a focused go to market strategy core network services. But don’t worry, we’re not throwing the web services away! Instead they are going to be launched under their own brand as a SaaS proposition specifically targeted at the easy production of content-led digital products.

This approach also means that we don’t lose the momentum and investment made in the web services to date, and will present a stand alone entry point to use of the network (use of the web services under their new brand will deliver revenue directly back to the network).

Fri, 28 Jun 2019 15:30:00 +0000 5d16218f3143710843f6210f Arthur Mingard 2019-06-28T15:30:00+00:00
Weekly update: 21st June, 2019 https://edge.network/updates/announcements/weekly-update-21st-june-2019 Hi everyone 👋 The sun is shining here and Bitcoin is up, so all is good with the world ☀️

I have quite a bit to update you on today… here we go!

Moses Skoda joined the team this week. He’s working on our services layer.

We’ve made strong headway with the build of our updated site, focused on core network services. We’ve also closed out the final colour ways and font choices or the brand update. I’ll be sharing some detail on this front with you next week.

And I expect us to be rolling out the changes in the first half of July.

Suffice to say, Ravi’s done an awesome job.

We had the PPA awards this week, where Paul presented one of the gongs:


It was a really positive evening for us – we have 20+ new conversations opened up on the back of the event.

I met with David Wilde to plan introductions to local government, and to explore methods for supporting delivery, for example by embedding our networking software within local data centres.

We also discussed the detail of his ongoing engagement with the project, covering speaking arrangements, articles and an approach for central government.

I wrote an article for Fintech magazine which should be published next week. I’ll share the link when it’s published.

We kicked off with our new PR. Wind up time can take a while, but it’s underway.

We’ve increased our engagement with one of our existing customers, who are now working with us on a deeper level to integrate core services.

One of our advisors Sean King is representing us in Cannes for the Cannes Lions this week, and has a few promising leads which we will be follow up on next week.

We have another promising engagement in the construction industry, which is the final throws of being defined before kicking off. As soon as we have more to share, we will.

The networking team have been continuing to put the finishing touches to the ACL migration piece required ahead of next months Mainnet release. This will make the transition from a single global ACL token to a per-user token seamless.

They also closed out enhancement work to the DNS service within the Edge network. it now supports all major record types in full, including MX, CNAME, NS and SOA record types.

It has also been refactoring in to an interface which makes extending record type coverage simple and lightweight. A version of this will be used for consumer level interfaces. More detail on this service will be released in the coming weeks.

Roadmap updates and timings were also completed this week. Items in the roadmap include:

  • The rebrand
  • Multi DC
  • Vault
  • ACL
  • DNS
  • Network CLI
  • Self onboarding for Hosts
  • Earning automation (DAO)
  • Edge storage
  • Explorer enhancements
  • Backbone rentals
  • Self onboarding for Gateways and Stargates
  • Edge for mobile and existing mobile apps
  • Consumer interfaces
  • ECUs
  • Edge cache
  • CDN comnsumer interfaces
  • Dates for Open Sourcing the core tech

…And a bunch more besides


We will be releasing a version of this to the community next week, and a full version with the release of the updated site in July.

Ecohustler went viral.

One of their articles (https://ecohustler.com/article/one-corporation-to-pollute-them-all/) was picked up by just about every social platform you can imagine. At peak the site was receiving 1k+ concurrent connections.

That’s an increase in traffic of 16,566%. Pretty significant! Uptime during the stampede? 100%

API version 5 was released!

Release notes as follows:


And documentation can be found here:


We’ve also made huge strides in the definition of what will become a stand alone SaaS proposition for our web services. Some of you are already aware of the work being done on this front, but in summary: we are breaking out the web services in the network and will be offering them under a new brand and on a new - and very powerful - domain.

The reason for this is to allow us to focus the network on network-level services, better supporting its go to market.

This approach also means that we don’t loose the momentum and investment made in the web services to date, and will present a stand alone entry point to use of the network (use of the web services under their new brand will deliver revenue directly back to the network).

We’ll be announcing this formally when the full branding work for the proposition has been completed. We expect this to be in July.

The focus for the technology has been on maintaining an open source platform and enabling local development workflows as a key point of difference and supporting mechanic for the SaaS solution.

With regard to token price, I’m happy to see a continued upward trend since early May (+32%).

The token remains central to the network as the only method of realising an internal marketplace that pays for services within an edge proposition at scale. This utility will be further cemented as we move closer to stand alone contracts, and as we work to find new methods for storing the data of the network in the blockchain.

And that’s it this week. Enjoy your weekends ✌️

Fri, 21 Jun 2019 17:30:00 +0000 5d11f262aa8a2c080bee280d Joseph Denne 2019-06-21T17:30:00+00:00
Weekly update: 14th June, 2019 https://edge.network/updates/announcements/weekly-update-14th-june-2019 In case you missed it, here’s the link to the transcript of last week’s AMA: https://dadi.cloud/en/knowledge/network/ama-recap-june-07th-2019/

RC2 of API 5.0 was released today. Here’s the latest for anyone that wants to help us test: https://github.com/dadi/api/releases/tag/v5.0.0-rc2

Key changes:

  • Improvements to document versioning
  • Search
  • Compression Support
  • Conditional GET with ETags

Full release notes for the candidates available on request. They’ll be published to Github with the full release.

We’ve spent a lot of time working through updates to the roadmaps for the Edge network.

The full roadmap is massive.

Jam packed in fact.

32 items and counting, taking through the rest of 2019 and deep in to 2020. We’re going to be finishing it next week, and will release it right after that.

We have the PPA awards night next Wednesday. Paul is now confirmed as a presenter for one of the awards. With luck their new site will be live shortly. (Running in the network of course!)

The networking team have built and released automated deployment for Gateways on test.network and have also introduced the first full build of Vault, a vital new component for the next iteration of network ACL.

Account registration for ACL was also progressed. This is the last core component required before we start the much anticipated mainnet release.

A bunch of work has been done to simplify the way that ACL is passed between Agent and Host, which makes the self onboarding process faster, more lightweight and more secure.

We’ve been hard at work defining and building out the Edge DNS service, and completed the addition of support for AAAA, CNAME and TXT records.

The react build of Publish has been merged in to the dev branch on Github, which includes a new rich editor. It’s not been released yet, but it will be soon (next week!). Check it: https://github.com/dadi/publish/tree/develop. We met with a company in the Governmental and security sector to demo our technology. An early, but very interesting session.

The first full build of the Tippr app running on API in the network went in to testing. More on that soon.

We have an open position for a seasoned technical sales director (role centred on London). If you know anyone, drop me a line.

We’ve progressed our site and brand refresh significantly. I hope to be sharing some of this with you all next week.

And finally the Foundation enjoyed and got a lot out of RightsCon in Tunis (now wrapping up). You can catch their updates here: https://twitter.com/DadiFoundation

And that’s it this week 😀 Enjoy your weekends.

Fri, 14 Jun 2019 17:30:00 +0000 5d11f17285fb9307d649adb8 Joseph Denne 2019-06-14T17:30:00+00:00
AMA recap: June 07th, 2019 https://edge.network/knowledge/network/ama-recap-june-07th-2019 Question 1

Would it be beneficial for $DADI to move to Binance DEX, instead of being an ERC-20 token? Are there any solidity smart contract features being used by $DADI which binds it to ETH/ERC-20?

Joseph Denne: ERC-20 is not of particular value to us as things stand. We’ve explored a lot of alternative options on this front, including Binance DEX (which we’ve tested extensively, and which we rate highly). Key is understanding the requirements that exist within the network. In summary these breakdown as follows (in no particular order):

  1. Smart contracts. The ability to script value transfer based on pre-coded events;
  2. Node-level data storage. Storing all network-level activity against individual nodes and making this directly explorable;
  3. Coin functionality. The ability to mint coins and for these to be able to be integrated in to the broader ecosystem (exchanges etc.).

It would also be great to be able to operate on a feeless footing. Anyway, we have a clear view on the future of the platform in relation to chain requirements and the direction of travel. I can’t say much more than that right now, but we will be releasing a lot of additional information toward the back end of the summer/early autumn.

Question 2

You have said that DADI will use on SGX, but have not explained the how. We need some details on the whole process and its status. That Meher is saying that SGX doesn’t rely on a central authority shows that they haven’t started the SGX implementation, otherwise they would know that it requires a central Intel Key Attestation server to work. So yeah… details on the security concept and how far it is along would be appreciated.

Arthur Mingard: Whilst it is true that an Attestation server is required, it doesn’t necessarily have to be Intel. In 2018 Intel released a whitepaper for the support of third-party attestation. With the introduction of a trust mechanism there is the potential for a decentralized approach which is what we are currently working towards.

Question 3

How does DADI ensure its remote employees stay on top of things? Any encouragements to visit workshops, conferences, networking events etc.? For example: An engineer is seeking specific answers requiring specific expertise…How can DADI facilitate those needs?

Arthur Mingard: We actively encourage attendance across a variety of events however the way in which each engineer keeps their knowledge current is entirely up to them. Working remotely means more flexibility, increased job satisfaction, and improved mental wellbeing. We’re a team, we rely on each other to progress, so it’s fairly obvious when someone has taken their foot off the gas. This is extremely rare though and we usually find ourselves encouraging peers to take a break!

Question 4

How is DADI going to promote business outside Europe?

There are no requests made directly to a Host. This was a key part of the network design which allows Hosts to operate behind Firewalls. All requests are outbound, via GRPC.

Joseph Denne: We plan to build local sales and partnerships teams in each of our key target markets. Marketing efforts are global, with tailored messaging for individual markets. PR is being localized.

Question 5

Can you share an ETA for your next purpose-built device we can buy?

Joseph Denne: The best case would be the back end of 2019. Industrial design and POC is complete internally, but there’s a lot more to do to take it to production and our timings are not yet set. We’ll share more as soon as we can though.

Question 6

Would it be possible to share the transactions each time DADI does buy tokens on behalf of customers? (assuming DADI always buys on behalf of them). What’s the wallet address to keep an eye on for monitoring network revenue?

Joseph Denne: Probably not. At least not quickly. There is a lot of commercial sensitivity around infrastructure, which is likely to prevent this level of transparency. However, it may just be a question of scale: at a point the batching of transactions may allow enough scale to effectively hide the scale of individual customer operations. This is something we’ll return to and review in a few months.

Question 7

Can you run SGX servers running on Gateways or Stargates?

Arthur Mingard: SGX can be used on any machine with supporting hardware so Gateways and Stargates can run in a secure enclave.

Question 8

What are the main fields of research to be conducted when DADI starts to move towards trustless setup (DAO)? What are the challenges involved with making DADI trustless (or at least fully verifiable in trustless fashion)?

Arthur Mingard: We’re spending a lot of effort exploring blockchain technology and looking at what can be done to more efficiently and transparently store network activity, and doing so in a way that enables faster - and cheaper! - payouts. Our biggest challenge remains security around self-onboarding, but we’ve made huge strides on this front in the past month.

Joseph Denne: Specifically, as I covered in last week’s update, we’ve been working with Vault for the issuance of individual machine authentication codes, a setup that enables node access revocation without impacting the broader network.

Question 9

Amazon spends $25 Billion each year on R & D. That’s like 700x the amount we got in the ICO. Of course, they would not focus everything on Blockchain, but they probably use some (i.e. Aelf and Amazon collaboration) And this is only one example of a competitor in this huge market. My question basically boils down to this: what makes our project that unique? What do we possess that would be really difficult for a major company to achieve even with all the money they have?

Joseph Denne: What prevents Amazon/Apple/Google/Facebook from doing anything that any other company does? Should all businesses pack up and go home? Obviously not.

Fundamentally our proposition is designed as a counterpoint to the centralization and control of these mega corporations. And of course, the same question was asked of those very companies in their start up phases.

Size isn’t everything. In fact, beyond a certain size companies slow down and find it hard to change. Look at Google. It’s getting increasingly hard to argue that they are still a technology company that’s interested in R&D. Buying other companies!= R&D

Question 10

Why has $DADI not been listed on any additional exchange?

Joseph Denne: Liquidity is important to us as access to tokens is central to the performance of the network (for both usage and consumption of services). Availability on exchanges is something that we monitor and spend a fair amount of time on, and there is a strategy behind this. I can’t say more than that at the moment.

Question 11

Will the team provide an API for the edge explorer?

Arthur Mingard: This is something we would like to offer. Encouraging the development of alternative interfaces and integration into third party monitoring services would be a great way in engage more in the networks goal to be open and transparent.

Question 12

How is the DADI token price volatility going to be dealt with?

Joseph Denne: Volatility in the cryptosphere in general poses an issue for the industry as it drives misconception about the maturity of the underlying technology. However, volatility in token value has no impact on our business in terms of customer onboarding, so it’s not a major concern right now. What seems likely is that if we are able to continue to drive growth in the network in terms of scale and adoption by customers, is that the token value will increase first to reflect the value of the business and then to reflect the potential of the platform and the size of the market that it is helping to define.

Question 13

Last AMA skipped my question about the code audit progress, can we get info about this? Do we already know who will perform the audit? or when its approximately finished?

Joseph Denne: Yes, we know who is performing the audit. It was pitched as a technology due diligence report for our community, and to this end is being produced by an impartial third party with solid technology and IP experience. I don’t have a handle on timings yet as there are some complexities to overcome – how do we publish a technical report in such a way that it doesn’t damage the IP protection process currently in process for example – but it will be sooner rather than later.

Question 14

What’s the difference between gateway onboarding and network backbone rentals mentioned in roadmap?

Arthur Mingard: One is the addition of third-party hardware to the network and the other is the rental of hardware currently maintained by the core team.

Question 15

If a customer is charged in fiat when token price is low, is it converted to DADI at one time or when there is a payout?

Joseph Denne: Conversion happens at the point of charge. And earnings are calculated at the point of processing.

Question 16

You mentioned that you will be rolling out a much bigger brand refresh. Is there a clearer ETA on that?

Joseph Denne: Yes, there is - we have a full rollout plan: we’ll be sharing the direction of travel with you all in the next week or so, and the design work itself soon after that.

Question 17

How does DADI feel about the GAS cost for sending micropayments over the Ethereum network? For example, my first founding node payment cost 24 cents in gas. For paying out all founding nodes alone it should have cost at least $25. How will this workout at full scale?

Joseph Denne: It’s workable for now, but ultimately, we want to get as close to real time payouts as possible, and this will require fee free transactions.

Question 18

What specific instances of AWS EC2 and google GCP are the price comparisons based on?

Arthur Mingard: Varying, but in the same ballpark in terms of power.

Question 19

What about a webinar type format on one media source for the AMAs vs doing it over multiple sources?

Joseph Denne: We’ve done a few of these in the past and plan to do so again. I’m not sure of the when of this though, but we’ll keep you posted. We’re also considering consolidating to a single channel for the regular AMAs, perhaps to Reddit to aid accessibility. Would be interested in your thoughts on this front.

Question 20

What is the difference between DADI and Ankr?

Arthur Mingard: I know next to nothing about Ankr apart from what is on their site (which seems thin on detail). They appear to be focused on the creation of a marketplace for spare capacity at DC level. I can’t comment much further than that I’m afraid.

Question 21

Introducing new devices to run DADI network (founding nodes) DADI also creates new idle computing power as a node usage depends on demand. Does DADI foresee a way to use/monetize this idle capacity elsewhere?

Joseph Denne: For Founding Nodes, no, as they are the foundation of the network designed to provide enough baseline capacity for the mainnet to bootstrap itself. But overall, we see dedicated devices as making up a small percentage of the total device set in the network. The primary focus is on unlocking the idle capacity in laptops, on mobiles, in set top boxes etc.

Question 22

Can you elaborate on the current use of the DADI token in general? How is the token involved with current paying customers?

Joseph Denne: It’s largely hidden from customers as most are not involved in the cryptosphere. That said this is starting to change and we have had some really engaged customer discussions around crypto. And you know what, when they get their heads around it they are really excited by the possibilities – we’ve had some start to explore how they could use the blockchain in their own offerings as well.

Question 23

What part of services DADI is currently generating revenue from are covered with DADI tokens? (ratio) I can imagine DADI is not buying tokens each time somebody paid for consultancy for example. So the question is, for what services DADI does buy tokens? How does this process currently work?

Joseph Denne: Currently all hosting fees run back to the network. It is the intention that everything that happens around the Edge network will return to the network, which will ultimately include support/consultancy services. When this cross fade will complete is not currently defined.

Question 24:

Have you considered migrating Telegram and Discord into one community channel?

Joseph Denne: Yes, we’ve considered it. They’re very different channels and experiences though. What do you think?

Question 25

I noticed that my node sometimes appears as ‘offline’ on the explorer list. Yet on the map it shows a green dot and in my dashboard, it also appears ‘online’. Why does it show offline in the explorer list and online in the dashboard? How does that influence node earnings and reputation?

Arthur Mingard: The explorer list is heavily cached so it’s likely that the device was temporarily offline at the point the data was captured. How this affects earnings depends on how long it was offline, which sounds like it wasn’t long at all.

Question 26

Is the compute units in the edge explorer a standardized way of measuring capacity or is it something the DADI team made up?

Joseph Denne: The concept of an Edge Compute Unit is something originated here. We needed a way of measuring the relative power of machines contributing to the network. They are benchmarked with the Founding Node as the baseline. We are working to define the boundaries of edge networking, and are setting our own language as the first stage in that process.

Question 27

Automated payout (daily i guess) for nodes how will it deal with the price volatility? Is the fiat to DADI conversion going to be automated or manual?

Joseph Denne: Fiat to token conversion will be automated, making use of the APIs provided by our exchange partners. Payouts are being fully automated with the intention of getting to as close to real time as possible.

Question 28

Ok so the baseline is Raspberry PI cores. How does that compare to how larger players like Amazon, Microsoft etc. sells and sets prices? They using the same measurements?

Arthur Mingard: If you take a look at the real performance of an EC2 instance for example a t3.small, they’re pretty comparable. The reality is, when you pay for cloud resource you tend to get a bit of fluctuation in real terms performance, and you pay a lot for very little. These overheads and excessive costs come from the fact redundancy has to be accounted for. A warehouse of machines still needs maintenance and security no matter how much is really being used. These factors mean that by the time you get to paying for a machine as powerful as even the older generation RPi, you’re paying a good deal more, and the pricing vs machine performance is intentionally lacking in detail.

Question 29

The company pays DADI tokens to the FN holders. Is it better for the company to have a low token price so that they can buy back low every month, or when the price increases the payout will be the same if we think $ only less tokens?

Joseph Denne: Network pricing is tied to $ USD value at the moment, as it is currency that is understood well by our target customer base. Payment is taken monthly in arrears. This means that the value of the token doesn’t really matter, as there is a Fiat>Token swap at the point of charge, and earnings are calculated at the point of use throughout a month.

Question 30

Will FN holders be able to add DADI tokens to the staking balance?

Joseph Denne: Nothing is planned on this front at this stage. But we’re going to be maintaining the Founding Node programme, so never say never!

Sun, 09 Jun 2019 11:00:00 +0000 5cfcedd43143710843f620fa Bolaji Oyewole 2019-06-09T11:00:00+00:00