DADI Latest article from the team en 2019 DADI+ Limited. All rights reserved. Sun, 16 Jun 2019 20:55:24 +0000 2019-06-16T20:55:24+00:00 en 2019 DADI+ Limited. All rights reserved. DADI https://dadi.cloud/assets/img/dadi-logo-colour.png https://dadi.cloud AMA recap: June 07th, 2019 https://dadi.cloud/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
Weekly update: 07th June, 2019 https://dadi.cloud/updates/announcements/weekly-update-07th-june-2019 We had an AMA today, so I’ll keep this weeks update short.

We’ve been interviewing for a couple of positions and have whittled a huge candidate list to a handful of excellent individuals. With luck a couple of them will be joining the team in the coming weeks.

Eduardo has been cracking through on development of a new rich editor for our interfaces, which is looking extremely impressive.

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/

The networking team made good headway on integrating Vault for per-user authentication tokens, improving network-wide security by granting ACL specific to each machine.

And they have been progressing well with the move to using Consul sessions for identifying the uptime of each network device, improving the accuracy of network sync.

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 are also going to be hosting a table at the PPA Awards, bringing customers and friends from Bauer Media, the BBC and Immediate Media.

The charitable project mentioned a couple of week ago has been signed off internally, and we’re expecting confirmation of the engagement within a fortnight.

They will be building on our stack and hosting in the network.

We gave a demo of our technology to one of the most exciting new automative companies today.

And finally a reminder that our Foundation will be at Rightscon in Tunis next week. (One of our core network devs, Meher, will also be in attendance.) Hit us up if you’d like to meet up.

And that’s it! Enjoy your weekends.

]]>
Fri, 07 Jun 2019 17:00:00 +0000 5cfce409f8009807feb197bc Joseph Denne 2019-06-07T17:00:00+00:00
Edge SSL https://dadi.cloud/knowledge/network/edge-ssl Encrypted traffic across the internet is of fundamental importance to our collective and individual security and privacy. Authentication credentials, sensitive financial data and private messaging are all key targets for attack. SSL encrypted traffic is so important that its absence significantly impacts SEO. Security is a key focus on the Edge network, and that’s why from the very beginning we chose to make network traffic fully encrypted by default.

Image

Generating a certificate requires some back-and-forth between the client server and the certificate authority, a sort of call and response that confirms proof of control for the domain. Each step of verification relies on previously transmitted data so typically the same server must be used throughout.

Image

With requests to the Gateway being load balanced, the likelihood of the CA’s response terminating at the origin Gateway is not guaranteed. LetsEncrypt does support DNS record verification for such circumstances, but that would require forcing clients to exclusively use the network as their Name Server, which is unnecessarily restrictive.

Image

Another option we explored was to create a temporary DNS lock, directing all requests to a single Gateway. Temporarily directing all traffic to a single production server risks creating potentially harmful load, increasing global latency for the domain in question, and creating bias in the payout mechanism by limiting contribution to a single contributor.

Image

With locking out of the question, we moved to exploring the option of distributing the certificate verification process. This would require the current terminating Gateway to distribute the certificate verification history across the network so that other Gateways can pick up where the previous Gateway left off. The autocert package has a cache interface, making it easy to build a custom getter/setter for previously obtained certificates and other account data. Using Consul Key/Value as an ephemeral store for the cache, the ACME (Automated Certificate Management Environment) becomes decentralised, allowing multiple Gateways to contribute towards the successful generation of a free certificate.

Image

After the certificate is generated and temporarily cached in Consul KV, the datacenter’s primary Stargate begins the process of migrating the payload to the network’s persisted certificate store, removing the original from Consul. Once migrated, it becomes visible to the wider network and is synchronized with each Consul datacenter by their respective primary Stargates.

And that’s it! The network now looks after the creation, renewal and distribution of free and secure SSL with zero maintenance, further simplifying the onboarding process and making all network traffic secure and encrypted as standard.

]]>
Fri, 07 Jun 2019 10:30:00 +0000 5cfa3b813ea4e008252ed448 Arthur Mingard 2019-06-07T10:30:00+00:00
Weekly update: 31st May, 2019 https://dadi.cloud/updates/announcements/weekly-update-31st-may-2019 It’s been a bank holiday week, and it’s also half term here, so this will be shorter than usual ☀️

I’ve written the first of what will be monthly updates, wrapping up the key developments for the projects and delving a little deeper in to some performance metrics.

You can read it here: https://dadi.cloud/en/updates/network/month-in-review-may-2019/

We had an early meeting with Sport England to discuss opportunities for our tech.

We also connected with a wide array of publishers (including Bloomsbury Publishing, Sage Publishing, NewsNow, Schibstead Media Group, NBCUniversal, Financial Times, Bicester Heritage, Conde Nast, Dennis and Immediate), many of whom we’ll be meeting in the coming weeks.

And we’ve also arranged a meeting with one of the largest automative properties for the week after next.

Plans have been put in place for Workflow Workshops. They are designed to provide both a free service to potential customers and as a legitimate conversation starter for new business opportunities. Each workshop is a targeted one-hour listening exercise, auditing workflow for a company’s digital product(s). The output is a recommendation on how this can be improved, in many cases using our technology.

The PPA site is looking awesome. Concept to beta inside of one month. The development pace that you can achieve on our stack is quite incredible…

It’s being handed over to the PPA on Monday, and should go live on the network towards the end of next week.

The network engineering team have been preparing for a major upgrade to mainnet, bringing a little over a month’s worth of development work to live.

The team have also been debugging issues with telemetry reporting, exposed while in testing on test.network

And they have been working on the network-sync service, which is now building automatically and logging device sessions. While it’s not yet ready for deployment, it’s laying the groundwork for a very important piece of the network reporting apparatus.

Work on the integration of Vault into Consul ACL is ongoing. This is a big update to the platform that will take a number of weeks to bear fruit.

Finally a few of us spent some time volunteering with the foundation in support of the development if their training programmes. If you haven’t pitched in yet, now is as good a time as any. Hit up jennifer@dadi.foundation for more information.

The Foundation team will be at Rightscon in Tunis in just over a week. If you’re going to be there and fancy a chat, please contact them to set up a meeting.

And that’s it from me for this week. Have a good weekend.

]]>
Fri, 31 May 2019 17:00:00 +0000 5cf15f8ccdffa807fb505a7a Joseph Denne 2019-05-31T17:00:00+00:00
Month in review: May 2019 https://dadi.cloud/updates/network/month-in-review-may-2019 We’ve been flat out so far in 2019, with a huge level of development and highly significant progress in terms of strategic positioning and planning for the evolution and expansion of our roadmaps.

Year to date commits? 3,126 💥

As a company we’re heading toward our sixth birthday: we’re 5 years, 10 months and 24 days old. We’re basically the granddaddy of the cryptosphere!

We are in the midst of a brand refresh – the fourth iteration, designed to better harness our market positioning and to support our growth for the long term. The team is working to a deadline of early-mid July for launch, along with an updated site focused on network-level services (on which you can find out more here: https://dadi.cloud/en/knowledge/network/network-level-services/).

The community will be brought across the plans for the refresh ahead of launch.

Highlights this month include our announcement as the technical partner for the PPA, strong growth in network capacity, sustained ROI for network contributors, and strong development progress.

Contents

  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 40 active deals in our new business pipeline with a combined value of over 6 million USD.

We met with fifteen new prospects in May. These ranged from startups looking for technology to get their products online quickly, to established businesses in streaming media, to data companies looking for storage capacity for their AI training data.

The team took to the stage at the PPA festival in Tobacco Dock in East London, talking on a variety of themes including blockchain, AI and headless content management technology.

Paul spoke along with Eduardo as well as our advisor Rob Belgrave from Wirehive, and all of the sessions were very well received.

Image

Earnings

Earnings in April returned 42% against the Founding Node proof of stake and May is expected to be even higher as more traffic has come onto the network, even when considering the number of nodes sharing in earnings will have grown.

Image

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

We expect to have earnings and payouts fully automated and running daily by the end of July. Hopefully sooner.

We’ve been engaged with HMRC here in the UK about the VAT treatment of tokens within a decentralised context. We’re working to be able to give clarity in relation to the tax position of network transactions for contributors to the network. Whilst we have a pretty clear view on this front, it is important that we seek confirmation from the relevant authorities on the application of any recent guidance and existing regulatory regimes. Once we have this we’ll share the details of the position. In the fullness of time our intention is to be able to provide specific guidance on a jurisdiction by jurisdiction basis (as we’ve discussed here before).

Network status

Our mainnet continues to grow, both in terms of capacity and in terms of production load. The network is comprised of members of the Founding Node programme and a series of non-earning masternodes managed by the core team.

As we start to move beyond this in the coming months we expect to see significant growth in network capacity, which in turn will support increasing customer usage.

Image

Key stats

Stat Value Description
Uptime 100% The mainnet achieved 100% uptime in May
Nodes online 345 Strong node growth was achieved in May, largely as a result of Founding Nodes being updated with new SD cards
Network reach 45 countries There are Hosts online in 45 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 306 All earning and operated by the community
Compute units 1,224 Edge one units: low-level compute capacity for web-based processing (websites, APIs etc.)
Edge storage 9.16 TB Long term object storage
Edge cache 815.39 GB Short term caching

Development report

A new service for network telemetry was completed, written in Go and deployed successfully to test.network. It will be moved to mainnet - edge.network - once testing completes. Testing has already raised a few issues which we are working hard to patch ahead of planned release to mainnet in the next fortnight. The update provides a greater level of data insight into activity on nodes, which is central to the next release of the network explorer.

The network data synchronisation layer has progressed nicely, and we are now able to detect devices coming online and going offline in any datacenter in the world. This is the next stage of the multi-DC work, the data from which will be stored under my.dadi.cloud. You can read about multi datacenter world here: https://dadi.cloud/en/knowledge/network/scaling-the-edge/

Progress towards the cracking of secure ACL for self-onboarding has been very strong, with a proof of concept revealed internally last week. Efforts to determine how best to integrate this in to the testnet are ongoing. The team have also been working on integrating Vault (https://www.vaultproject.io) into Consul ACL. This is a big update to the platform that will take a number of weeks to bear fruit.

An auto SSL certificate generation service was scoped, built and released: Gateways now create free SSL certificates using Lets Encrypt for all apps deployed to the network. This means that any domain that you configure against your apps in my.dadi.cloud will automatically run under SSL in the network. This is BOTH for the subdomains the network generates for you, and also for your own domains mapped in to the network. We’ll be writing about this in more detail soon.

A remote update system for Stargate was completed, which allows for configuration files to be updated automatically. The update included the addition of remote control of the BGP system, which is now deployed as a container in the application - enhancing security and hugely improving efficiency.

API update

We moved a step closer to the release of API 5.0, which includes a tonne of changes.

We also completed development on a Golang wrapper for API. Documentation is being written and once done we will be releasing it as an Open Source package.

CDN update

CDN version 3.6.9 was released. This brings animated gif support to the platform. Release notes and source code: https://github.com/dadi/cdn/releases/tag/v3.6.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

Tiipr

Image

We’ve been working with mobile startup Tiipr. They are developing a tipping application that guarantees that tips go to their intended recipient, and that makes payments to staff in real time. It’s a super smart and pretty revolutionary concept for the service industry. And the app itself is looking quite brilliant.

We are supporting them in development: the app is being built using our technology stack, and it will be running in the network using storage (including database use), caching and compute services.

A pre-launch site is live and running in the network. You can see it here: https://tiipr.com

Tiipr’s roadmap is pretty aggressive, and should see the first build of their consumer app live this summer. As soon as it is out there, we’ll let you know.

We’ve also been given permission to share details about the build and its performance within the network. We’ll be writing about this as we go.

Ecohustler

Image

Ecohustler launched a new version of their site on our stack at https://ecohustler.com

The site went from concept to live in five weeks, providing a great example of what’s possible in the stack.

They are also going to be launching an app which will be API and Store, both running in the network. We expect to have the details of this fleshed out in early June.

PPA

Image

The PPA’s site is being moved to our stack. This kicked off four weeks ago and is due to complete next week. The site is a port from SiteCore, with a design and functionality refresh included. This is another great example of how quickly you can move using our technology, and as with Tiipr and Ecohustler, it will be running in the network and we’ll be reporting back on performance over time.

(We also launched a voting site for the PPA Festival, also built on our tech: https://ppacoveroftheyear.co.uk/ – get your vote in now! [Closing date 07th June])

The Foundation

Our charitable foundation has been busy compiling research, and has also been working with the charity commission here in the UK to help them understand blockchain and its application to the charitable sector.

The Foundation team will be at Rightscon in Tunis in just over a week. If you’re going to be there and fancy a chat, please hit them up for a meeting.

They are also developing 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-may-03rd-2019/

Our next AMA will take place on Friday the 07th of June. I’ll be joined by Arthur, newly in post as our CTO.

The session kicks off at 2pm UTC on Reddit: 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 May here:

]]>
Fri, 31 May 2019 17:00:00 +0000 5cf14d551e21e60843cfc75d Joseph Denne 2019-05-31T17:00:00+00:00
Weekly update: 24th May, 2019 https://dadi.cloud/updates/announcements/weekly-update-24th-may-2019 👋

There are a bunch of holidays this week and we’re running in to a bank holiday weekend, so this week’s update will be shorter than usual…

Even so, are we ever getting through a lot!

The app startup that I’ve mentioned in previous updates is called Tiipr. They are developing a tipping application that guarantees that tips go to their intended recipient, and that makes payments to staff in realtime.

It’s a super smart and pretty revolutionary concept for the service industry. And the app itself is looking quite brilliant.

We are supporting them in development: the app is being built using our technology stack, and it will be running in the network using storage (including database use), caching and compute services.

A pre-launch site went live last week, running on Web and API. It will be shifted to CDN in the coming weeks. You can see it here: https://tiipr.com

Tiipr’s roadmap is pretty aggressive, and should see the first build of their consumer app live this summer.

As soon as it is out there, I’ll let you know.

We’ve also been given permission to share details about the build and its performance within the network, which will give us a great customer success story. We’ll be posting about the process of building for mobile on the stack as well.

Paul has been in outreach pretty much all week - on the road and in a series of meetings.

We met with one of our advisors to chat strategy for the hiring of a senior sales director to help scale our sales approach. We expect to be moving on this hire in the next couple of months.

We now have 268 nodes in the Edge network – 22 Stargates, 20 Gateways and 226 Hosts. This gives us a total capacity of 900 Edge #1 compute units, a little over 6TB of object storage and 536 GB of cache availability. Pretty punchy given the age of the mainnet 💪

Year to date commits? 2,996 💥

And in the past month we’ve seen 31,415,160 requests to CDN and counting…

As a company we’re heading toward our sixth birthday: we’re 5 years, 10 months and 17 days old. We’re basically the granddaddy of the cryptosphere 😂

We’re working on a format for providing regular statistical updates. This will include a level of financial data too.

I’m also going to be writing a “month in review” wrap up from the end of this month on. This is on the back of a suggestion from the community, and is designed to further help drive awareness of the pace of development in the business.

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

And we expect to have earnings and payouts fully automated and running daily no later than the end of July. Hopefully sooner.

James is stepping down as our CTO. He will remain attached to the business as a senior technical advisor. He is being replaced by Arthur, who is being promoted to the role after four years with the company, two of which have been as the technical lead for the network. He’s the perfect fit the role as we move our key services to live and begin to scale out the platform.

On network development:

We have containerised the my.dadi.cloud stack for local development, which has enabled us to start working on integrating it with the new network changes, as well as to start work on an automated tested for the stack. This includes a network ready build of Publish.

As we’ve been testing telemetry on test.network we’ve discovered a few issues, which we are working hard to patch ahead of planned release to mainnet in the next fortnight.

The network data synchronisation layer has come along nicely, and we are now able to detect devices coming online and going offline in any datacenter in the world. This is the next stage of the multi-DC work, the data from which will be stored in my.dadi.cloud

We have made great progress towards cracking of secure ACL for self-onboarding, with a proof of concept revealed internally this morning, and efforts ongoing to determine how best to integrate this in to the testnet.

And finally a reminder that our charitable foundation is developing 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’ll need half a day of your time, you can be based anywhere and you’ll earn a warm sense of wellbeing knowing that you’re helping to make the world a better place 🙏

And that’s it! Enjoy your weekends.

]]>
Fri, 24 May 2019 17:30:00 +0000 5ceb8edd51380e081d55966d Joseph Denne 2019-05-24T17:30:00+00:00
Weekly update: 17th May, 2019 https://dadi.cloud/updates/announcements/weekly-update-17th-may-2019 👋 It’s been another packed week here… here are the edited highlights:

It looks like Ecohustler are going to be launching an app. This will be powered by API and Store, both running in the network. We expect to have the details of this fleshed out in early June.

All of the nodes flagged as needing a new SD card have now had one posted out (the final batch were posted today). The account pages for Founding Nodes have been updated to match the new device IDs and should pick them up once the new SDs have been inserted and the device powered on.

We’ve architected a solution to prevent issues like this happening again in future: it involves Agent on a Host performing a status check to the central network services within Stargate, which will enable the flagging of a node as non-updating and in need of a reset. In this instance Agent will remove the existing build of Host, reset itself and then proceed to download the latest version.

You can think of it as a remote reset.

There’s a bunch of planning needed to flesh this out, but the network team expect to have a version available within the next month.

The latest build of the networks central telemetry service deployed successfully to test.network and will be moved to mainnet - edge.network - after a week or two of testing. This provides a greater level of insight data in to activity on nodes, which is central to the next release of the network explorer.

Chris met with a streaming media site focused on the music industry about shifting their platform to our tech and their media delivery to the network. Early days, but we have a second meeting booked for next week.

I met with an AI business focused on the lead generation space about the provision of a database and API in the network. I expect to be moving them in a trial and proof of concept in the next few weeks.

We also met with a dating business, who are looking for a new platform and who are interested in our stack and underlying network services.

Work on the PPA’s own site - shifting it to our stack - is progressing extremely well and is due live in early June. It will be launched in the network from day #1.

We have a bunch of leads on the back of the PPA event last week and meetings booked with four of the world’s biggest publishers to discuss our platform.

+We have the PPA awards coming up in June, which we’ll be attending.

We’ve continued to refine and move forward the brand refresh that I’ve mentioned in the last few updates. I’m working to a deadline of early-mid July for launch, along with an updated site focused on network-level services (https://dadi.cloud/en/knowledge/network/network-level-services/).

I’ll be sharing more information on this front ahead of release.

We’re hiring for two new positions, one in the network team and one in the web services team.

The Foundation has been busy compiling research, and has also been working with the charity commission here in the UK to help them understand blockchain and its application to the charitable sector.

We’ve also been engaged with HMRC here in the UK about the VAT treatment of tokens within a decentralised context.

We’re working to be able to give clarity in relation to the tax position of network transactions in relation to contributors to the network. We have a pretty clear view on this front, but are looking for confirmation. Once we have this we’ll share the position in full. In the fullness of time our intention is to be able to provide tax advice on a jurisdiction by jurisdiction basis (as we’ve discussed here before).

CDN version 3.6.9 was released. This brings animated gif support to the platform. Release notes and source code: https://github.com/dadi/cdn/releases/tag/v3.6.0

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 bunch of new functionality for our interfaces.

We submitted a proposal for the take on of a conservation website. We expect to hear back from that within the next fortnight.

The startup that I mentioned last week that is about to go live on CrowdCube will be pushing a basic site to the network next week.

Arthur is currently in Japan, ostensibly on holiday, but from the photos he’s shared I’m fairly sure that he’s just there to dismantle some robots 🤖

Heads up that our next AMA will be Friday 07th June, when Arthur’s back. Chris will also be joining us.

And that’s it for today! Enjoy your weekends.

]]>
Fri, 17 May 2019 17:30:00 +0000 5ce28098ac1ac007f10205ac Joseph Denne 2019-05-17T17:30:00+00:00
Weekly update: 10th May, 2019 https://dadi.cloud/updates/announcements/weekly-update-10th-may-2019 It’s Friday! The sun is shining again… and we’re busy! ☀️ (Like always!)

This week saw the team take to the stage at the PPA festival in Tobacco Dock in East London, talking on a variety of themes including blockchain, AI and headless content management technology.

Paul spoke along with Eduardo as well as our advisor Rob Belgrave from Wirehive, and the talks were very well received.

Image

We launched a voting site for the festival, built on our tech: https://ppacoveroftheyear.co.uk/

And will be following that up with a site for the organisation itself, which will be launched in the network in June.

We’ve progressed a promising lead in the connected devices space, which is focused on extending and rebuilding their platform on our stack and helping them to scale (by providing processing capacity for their devices in the network).

We’re also working with a startup that’s going live on CrowdCube in the next few weeks. And we’ve started early conversations with a well known lifestyle company based out of London. Both early stage, but great opportunities.

Ravi has knocked our brand refresh out of the park. I’ll be able to share this with you all very soon.

On network developments, Meher finished the telemetry service for the network in Go, and deployed it to test.network

We completed an auto SSL certificate generation service: Gateways now create free SSL certificates using Lets Encrypt for all apps deployed to the network.

This means that any domain that you configure against your apps in my.dadi.cloud will automatically run under SSL in the network. This is BOTH for the subdomains we generate for you, and also for your own domains mapped in to the network.

We’ll be writing about this in more detail soon.

We completed auto-deployment for Stargate and BGP is now fully containerised within Stargate, meaning that we’re completely abstracted from the host operating system.

We also completed development on a Golang wrapper for API. Documentation is being written over the next week or so and once done we will be releasing it as an Open Source package.

We finished a Consul replicate deployment - a big step in getting the network explorer to persist service data. This is the second to last thing to do be done before we can deploy the multi data centre update to edge.network

You may have noticed nodes appearing multiple times in the explorer: this is a bug whereby a service that’s written to network when a Host connects is being replicated by nearby Stargate. For example Paris’s service is being replicated to Amsterdam. We’re not sure why this is happening, but are investigating. There’s no performance impact on the network.

And that’s it for today! I have to run to pick up my cat form the vets before it closes, but will be online later to answer any questions that you may have on the above.

Enjoy your weekends.

]]>
Fri, 10 May 2019 17:30:00 +0000 5cd80db5b611cc0896032d67 Joseph Denne 2019-05-10T17:30:00+00:00
AMA recap: May 03rd, 2019 https://dadi.cloud/knowledge/network/ama-recap-may-03rd-2019 Question 1

How many $DADI does the team still hold?

Joseph Denne: Almost all of our allocation remains in hand. More specifically: c.598k have been distributed to team members. (And of that a tiny amount sold.) The vast majority remain unclaimed - despite vesting periods having passed - and are in the originating wallet. Why? Because we’re in this for the long game… why would anyone want to sell this low?

Question 2

Can you clarify Meher Assel’s role at DADI? What’s his view on ‘decentralizing the #cloud to make the Internet fairer for everyone’?

Meher Assel: As a software engineer with lot of experiences working with the programming language Go, my role is mainly work with the network team implementing/optimize features. With lack of entertainment activities and proper education at my childhood town (Gafsa, South Tunisia), internet was a way for me to explore the world and go beyond the borders. Knowing how important a fair internet is to humanity, I’m all in with all my technical skills to help make this a reality.

Arthur Mingard: We’re really happy to have Meher on the team and his contributions have been crucial in the advancement of the network, as well as company-wide R&D efforts.

Question 3

With the self-onboarding getting ever closer, will you open it as a free-for-all or will you control the onboarding with a waiting list to control supply vs demand in the network? If it’s the latter will you prioritize people without existing nodes for fairness and to maximize decentralization and robustness of the network?

Joseph Denne: The latter is our current preferred approach. Why? Because as you identify, it enables the management of supply and demand, which in the early stages of the network are fairly sensitive. Assuming this is where we end up, there will be a gated approach to rollout, with individuals on boarded a way designed to ensure fairness.

Question 4

How are dynamic ip address changes handled for host devices?

Arthur Mingard: 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.

Question 5

When can we expect CDN waitlist metrics?

Joseph Denne: You know I’m not sure. We’ve ever been asked for these. Happy to share. There are currently around 400+ names & domains in the list.

Question 6

How far along is patenting?

Joseph Denne: Well, we are many months in to the process but do not currently have an end date. However, we have started to release code and will continue to do so.

Question 7

Could a DADI engineer elaborate on this BFT standpoint from Consuls POV vs DADI’s proposition? In this video Jon Currey, Director of Research at HashiCorp, is explaining the reasoning for choosing for a crash failure model (SWIM protocol) rather than a full BFT model. Hashicorp says BFT is not widely adopted because there are no bad actors inside the datacenters, thus crash failure is good enough. Of course, this does not add up with DADI’s proposition with homes and offices as a datacenter. So, is DADI working on a different implementation to replace SWIM with a higher hierarchy solution?

Arthur Mingard: All of the Consul Datacenters are run on Stargate and not on machines in Homes or Offices. We may move to running Consul Agent on Gateways too and at that point there will be some considerations to make around how to handle bad actors and crash failures.

Question 8

Who is part of the ownership structure of the holding company? Have there been any new investors?

Joseph Denne: There has been no change on this front: my partners Will (Lebens), Chris (Mair) and I own the company outright. There are no other investors or partners.

Question 9

Are you going to include random stats for the founding nodes like upload time DL/UL speed, average ping, etc.?

Arthur Mingard: There are a bunch of detailed statistics that are being collected and will be visualized through the explorer in time. You can see a breakdown of what we expect to be highlighting here: https://dadi.cloud/en/updates/network/explore-the-edge/

Question 10

Can you tell us more about the security of the self-onboarding nodes? Does it only rely on Intel SGX, or is AMD and ARM also supported? Does the SGX solution rely on the (centralized) secure attestation servers of Intel, or is some other implementation like Golem’s Graphene-ng being considered?

Meher Assel: We’ve recently revisited some decisions relating to the potentially sensitive nature of network data and are exploring some alternative approaches. One key focus has been finding ways to shard and encode data so that a single Host would not host any meaningful and sensitive information. We’re still working on running containers under SGX and are working on AMD and ARM, but we’re more focused on Intel as the hardware enclaves are more mature. SGX does not rely on any centralized authority.

Question 11

Someone was able to crash the price to 230 sats with just a few hundred dollars on Kucoin today, although there is a market maker bot supposedly trading hundred-thousand dollars every day. 1) what is the point of this bot, if he can’t even sustain the price of a hundred-dollar market sell? How will clients buy and providers sell with this kind of liquidity? 2) Why is the team not buying back tokens at these prices and keeping at least a somewhat stable price at this low market cap? With not even 0.5% of ICO funds, they could not only keep the prices stable and make less people rage-quit but also save their own investments. Companies buy back their shares when they think they are undervalued all the time, but DADI seems to have 0 problems with the price crashing to 0. Please explain your rationale.

Joseph Denne: That’s a nice short question! We obviously care about token price – it’s an important instrument in the network, being central to network growth and performance. We have bought back tokens, specifically to aid the onboarding of customers through the provision of OTC for services. However, we are not interested in manipulating the price. I see no long-term benefit to this, and am honestly alarmed by the amount of manipulation that the cryptosphere tolerates. There is very little in the way of real-world use cases, business or traction for a very high percentage of coins. If we are to really drive adoption of these technologies, we need to get away from this sort of thing.

Question 12

Why are nodes on their second SD card reporting as offline with no resolution? Are there still fundamental issues that haven’t been resolved?

Arthur Mingard: A lot of testing and regular software releases have been made over the last few months, averaging around 1 major release per week. In this early phase there have been some breaking changes, and for machines that were disconnected during the release period we have instead chosen to send out updates cards rather than asking the owners to manually update. This service is something we expected to deliver and has been taking into account when calculating earnings. We expect the latest release of cards, which are currently shipping, to be the last.

Question 13

How many founding nodes have been sent out and how many of those are online? I currently see 132 FN in the network explorer. Feels like we are missing some.

Joseph Denne: I believe we’ve built and shipped 179 nodes so far. Not all of them have been plugged in, and the explorer is in Beta. There will be another set of nodes available btw - not sure how many yet, but so far, we’ve had no breakages in shipping, which is really quite remarkable, meaning that we still have spare inventory!

Question 14

How is the ‘security’ challenge of self-boarding going?

Arthur Mingard: We’ve been working on revamping the Access Control List process which is an important part of the wider security challenges ahead of SO. As a large piece of work, we’ll be writing more about this as we release the first version later on this month.

Question 15

Does DADI monitor uptime performance (+DNS lookups) for each individual region? I would love it if DADI provided a tool like Pingdom Tools to test from each DADI server locations.

Joseph Denne: Yes, this is done at Stargate level on a region by region basis. And I love the idea of a public test suite for performance like Pingdom provides. Will add that to our backlog 🙂

Question 16

Why is the team holding so many tokens in one contract as it is unsafe from a cyber security standpoint? Are there plans to split these tokens into different wallets or separate purposes?

Joseph Denne: Holding tokens in the originating contract reduces circulating supply and these tokens have not yet been claimed by the team. The contract has been third party audited for security, but there are plans to review the holding strategy as there are other methods of addressing this.

Question 17

How can we trust Stargates when they are decentralized? Aren’t they too susceptible to byzantine attacks?

Arthur Mingard: Stargates form a consensus with each other, so majority rules. DNS records are regularly checked under this process to ensure no foul play.

Joseph Denne: To elaborate on that a little, consensus for DNS means that any machine found returning unexpected results is removed from the network, with their stake forfeit. In the case of Stargates this is a highly considerable amount of money.

Follow Up: Will you have an Invalid Activity Appeal process?

Joseph Denne: We’ve not specified this yet. But yes, one will be needed, at least in the early days. How this will work in a fully decentralized set up is a question.

Question 18

What level of diagnostics and insights is DADI team able to perform on specific problematic nodes and what tools/options does the team have to investigate specific node problems?

Meher Assel: Live logging at a debugging level can be performed on any node on the network. We also started to work on system that allows us to inspect what’s happening inside a node remotely (like listing running containers). This already helped us troubleshoot production problems in the past, and we are putting more efforts in these components. Telemetry data as part of the latest release of the telemetry application will be rolled out soon, and we’ll cover this in a write up.

Question 19

Does Dadi require different types of nodes? For example, are there disadvantages to having all hosts as raspberries?

Arthur Mingard: As new applications are pushed out to the network, we’ll be introducing performance bands for devices so yes, there will be a series of device types/classifications. We chose to launch with CDN because of its performance on an RPi. Believe it or not, we see better performance from the Pi than we do from some of the relatively expensive EC2 machines and we’re seeing great results already.

Question 20

How will payments to those whose nodes were offline be determined and when can they be expected?

Joseph Denne: There is a base payment to Founding Nodes who have been affected by the earlier issue with SD cards. This has already been factored, earnings added to account pages and the first month of payouts made

Question 21

As the dev team is spread over building dadi apps, building client projects and developing the network core itself, how confident is the team that they can compete against much larger teams, who are focusing on a single thing. Or more precisely, how confident is the team that they can deliver the ‘edge compute’ sdk on schedule in Q4 with their current team size and compete against others like iExec, Holo, Dfinity or Golem who have been focused on this single goal with much larger teams since multiple years?

Joseph Denne: A few of the projects mentioned “who have been focused on this single goal with much larger teams since multiple years” have technology and a proposition far less developed than ours. So I’d flip it around: how is it that so many projects in this space have failed to deliver working technology, product-market fit and real-world customer derived revenue?

Looking to our own set up, we’ve been in the process of shifting focus to core network services for some time, specifically to ensure that we have the right resource focused on the platform. See: https://dadi.cloud/en/knowledge/network/network-level-services/ We’re also working on a go to market for the individual web services that will directly support the network through the use of core services, but that does so with ring fenced resource that is paid for through its own uptake. We’ll be talking about this in much more detail soon.

Question 22

When can you release actual network metrics and specifically, who is using the network and for what?

Arthur Mingard: We’ve released a bunch of network metrics – check out the explorer: explorer.edge.network We can’t talk about individual customer engagements unless we have direct permission to do so. This is the case on a few fronts, and some examples have been given. And as previously indicated, we will be writing about a number of success stories. In terms of the what it’s being used for, that’s also a matter of public record. Right now, it’s content distribution through CDN (including hosting), storage and a low level of compute (in testing).

Question 23

How does DNS TTL work in DADI network?

Arthur Mingard: TTL has a standard of 30 seconds for all deployed applications, however this will become configurable, allowing for longer TTL times if necessary.

Question 24:

How long does it take for a deployment to the network to fully spread? Is it different for different services? CDN, API, Web, Store, Publish?

Joseph Denne: Deployments to the network are very quick thanks in part to the layered filesystem of Docker, which we use for the majority of network deployment.

Meher Assel: The network applications take about 30 seconds to spread. The service applications like CDN take a few minutes on first install, then a few seconds for updates.

Joseph Denne: +There is a balance to be struck, between speed of updating and disruption to services, so a staggered update is performed for each deployment.

Question 25

What’s the teams current plans for fiat to DADI payments of services, how will this be done?

Joseph Denne: Payments for services will be available in fiat (GBP, USD and Euro) via credit card using a traditional payment gateway. Once payments are made in fiat, we attribute the equivalent amount in $DADI from a holding account and push it in to the network. The holding account is kept topped up through a market buy service. Payments will also be possible directly in $DADI (of course), Bitcoin and Eth.

Question 26

When will the visualization and payout of node earnings be automated for us to view in more real time?

Joseph Denne: We don’t have a fixed deadline for this, but we are actively working on it. The first phase is done (automated processing), so moving it to a full autonomous will be fairly quick, but we’ll want to hand hold a few runs to ensure it’s working as expected first.

Question 27

When a stargate in the network is dedicating his rack to DADI, but DADI cannot use 100% of that rack, is the stargate provider allowed to sell this idle capacity elsewhere?

Arthur Mingard: Yes. Our Node software doesn’t mandate capacity, but the network expects that minimum availability is provided.

Question 28

Has there been progress on video streaming for CDN and when can we expect it to be ready?

Meher Assel: Right now, we don’t have any optimized delivery method for videos as we do have for images, but CDN does support delivering any kind of assets, which include video assets.

Joseph Denne: So, yes to video support (right now), but no to live streaming.

Question 29

When we see Mac OS and Windows desktop app?

Arthur Mingard: Once self-onboarding for Linux is complete, rolling out to other platforms will be pretty fast as the mechanisms are broadly the same OS to OS. We already have Host working on OSX for example and have a basic POC for iOS as well. The thing standing in the way right now is security testing of the primary build. We’re working hard on this front and soon as we have an update to give, you’ll be the first to know.

Question 30

Can the Dadi team give their honest opinion of Brexit?

Joseph Denne: Seriously?! I can’t speak for the entire team on this issue, but here’s my take: I don’t believe in borders, and like a significant number of people in the UK, I’m pro migration. This is worth a read: https://www.theguardian.com/world/2019/may/02/britons-more-sold-on-immigration-benefits-than-other-europeans

So, I guess I’m broadly pro EU - accepting that this is a different concept to being pro-European, which I also am - and I think that we should be a positive and leading member of the European community. However, democracy trumps my personal outlook and I find the current situation to be pretty anti-democratic. No matter how you look at it.

What a happy note to end on!

]]>
Sat, 04 May 2019 08:30:00 +0000 5cce929217092707ec18198a Bolaji Oyewole 2019-05-04T08:30:00+00:00
Weekly update: 03rd May, 2019 https://dadi.cloud/updates/announcements/weekly-update-03rd-may-2019 We had an AMA today (the transcript of which will be shared shortly), so today’s weekly wrap is short and sweet.

Jean-Luc has delivered a site on our stack in the network support of the PPA, which launching at their festival in London next week.

On which the team finished planning the content for the talks we are giving next week, covering blockchain, content management and AI for publishers.

Josh and Paul Davis have moved the mobile app that’s being built on our stack on a bunch, with the first full build now in testing. It’s working well.

Chris met with a couple of startups about the use of our technology in the build of their platforms. He also dropped a couple of Founding Nodes off to colleagues in Italy.

Eduardo has been full throttle migrating Publish to React to better align it with a broader dev community and to open up the potential for easier integrations with existing plugins that should help to kickstart new and enhanced functionality.

The branding refresh I mentioned last week has come on leaps and bounds – we’ve settled on a route and I hope to be sharing it with you in the coming few weeks.

Testing completed on the sign in functionality for Ecohustler, which will be launching soon.

This was a week of planning for the networking team in the main, but they guys did complete work on the VPC hopping solution for Hosts within the multi-DC setup that I spoke about last week.

Meher’s almost finished a build of the telemetry service for the network in Go, which brings new functionality and efficiencies to the fore, and which we hope to roll out next week.

Adam completed a remote update system for Stargate, which allows us to update the config automatically, including giving us remote control of the BGP system which is now deployed as a container in the application - enhancing security and hugely improving efficiency.

And finally we moved a step closer to the release of API 5.0, which includes a tonne of changes.

And that’s it! Have a great weekend 🙏

]]>
Fri, 03 May 2019 17:30:00 +0000 5cce87cee23fa30891d46e35 Joseph Denne 2019-05-03T17:30:00+00:00
Weekly update: 26th April, 2019 https://dadi.cloud/updates/announcements/weekly-update-26th-april-2019 Two shortened weeks because of what was a wonderfully sunny four day Easter weekend here, but our pace barely dipped.

Here are some highlights:

Payments to Founding Nodes for April will be released to dashboards on Wednesday next week. Payouts for March are being processed through our distribution scripts this weekend and should have completed by Monday.

If you need to update your payout wallet, please do so now!

We moved Ecohustler.com - an ecology focused magazine - to live in the network. It was redesigned and rebuilt on our stack in four weeks, migrated from Wordpress. We’ll be writing about the experience next week.

It’s also the first live deployment to make use of a single sign on mechanism in the stack (not yet live, but it will be soon!), which is a great proof point for user data in the platform.

Multi DC was completed (see: https://dadi.cloud/en/knowledge/network/scaling-the-edge). This started testing on test.network last week.

The update includes a significant development to participatory DNS. Previously we returned a gateway that was local to the Stargate handling the DNS response. Multi DC splits the network in to VPCs: if I’m in Paris, Stargate will look for a Gateway and give me an IP. If there’s no Gateways connected to Paris, the system needs to be able to give me a Gateway from within another VPC. So we designed and built a system called DNS Exchange – a process that forwards request records on to the closest Stargate on the basis of network coordinates, factoring the application availability of the request being made.

In short, DNS now transfers through VPCs to find the nearest gateway.

This is massively cool, and a huge performance and redundancy win for the network.

We’ve also migrated to v1.4.4 of Consul, which is the latest release.

Test coverage for the Finite Test Machine - https://dadi.cloud/en/knowledge/network/finite-state-machine/ - is now at 100%.

As a result we’ll be moving this in to its own repository and releasing it on Monday – the first of our network code to be open sourced.

I’ll share the Git link as soon as it is public.

We migrated registry and our build servers to more powerful machines in the network, which ups the performance of builds, speeding up development somewhat.

We’ve started working with a startup working in film, specifically performance testing their *massive* datasets in the network (read: tens of millions of documents - almost 100m in fact). Assuming we can show sufficient performance we expect them to become a customer. And if that does happen, I expect to be able to talk about the engagement publicly.

We’ve been speaking to an existing customer about extending their use of our technology to those areas of their business not yet utilising it. It’s nice to see positive experiences with the platform leading to greater engagement. A great proof point for what we’re doing.

We have three speaking spots at the PPA Festival in London on the 09th of May. Eduardo, Paul and Rob Belgrave will be speaking at the event.

+It looks like Chris and/or I will be at Consensus this year too. Hit me up if you’re going to be there.

The onboarding of the startup in the mobile payments space that we’re working with is cracking on at pace. Their core data layer is now in testing on the network. I expect to be able to share more detail with you on that in the coming weeks.

Ravi has been making great strides with our brand refresh. We’ll have a bunch to share on this front soon.

And here they are on a trolley, ready for pick up by UPS:

Image

And finally, our next AMA will be Friday next week. Get your questions ready!

]]>
Fri, 26 Apr 2019 17:30:00 +0000 5cc483c1cedda3085751c158 Joseph Denne 2019-04-26T17:30:00+00:00
Weekly update: 12th April, 2019 https://dadi.cloud/updates/announcements/weekly-update-12th-april-2019 A shorter update this week, as we’ve largely been head down in delivery… and we’re still going!

Meher finished adding the new build package to Host, which marks the end of a long journey into making the network more versatile and capable of running on devices with much smaller footprints than originally envisaged

The networking team have otherwise been focused on continuous integration & delivery tooling, as well working to improve reporting of all network & core service builds

Image

We delivered Publish version 2.3.0 (more information: https://github.com/dadi/publish/releases/tag/v2.3.0)

Image

Adam wrote about telemetry and how we manage pulling data from a multitude of disparate devices: https://dadi.cloud/en/knowledge/network/an-introduction-to-telemetry/

A new site launched on our stack and in the network. It’s a first version, but still very cool. We’ll be writing about this next week

Ravi kicked off the brand refresh for DADI, which I’ll be sharing more information on as it moves forward

We’ve been working on the development of a dedicated go to market strategy for individual web services distinct from the network’s go to market (which is focused on core network-level services). This is looking pretty exciting, and should help us in our driving of adoption for network services. As soon as I can, I’ll share more

Chris spent 48 hours with a big prospective new customer, a start up in the sporting arena with a pretty revolutionary idea

James moved forward release planning for API 5, with a focus on improvements to document versioning, search, compression support, conditional GET requests and new security methods for client secrets

Finally our new mobile engineering hire started this week. He’s working on networking components for mobile devices, as well as supporting customers with their own deployments of our technology

And that’s it from me for this week. Enjoy your weekends X

]]>
Fri, 12 Apr 2019 17:30:00 +0000 5cb341dde19cd7478ac119f7 Joseph Denne 2019-04-12T17:30:00+00:00