I have just been reading through the whitepaper and looking at the API service. I have a question – how is data in the database replicated between hosts to create redundancy?
We are using DADI Store and our FileStore data connector for API within the network. Store handles replication and edge caching. We’re also playing with an alternate API data connector which leverages OrbitDB, which is a distributed database solution built on top of IPFS.
Could you please compare DADI with Couldflare’s new decentralized CDN service?
From what we can tell, Cloudflare’s offering is simply to provide a public IPFS gateway to allow users to retrieve content from the IPFS network. In contrast to this, DADI offers a suite of products that can run any application by combining those products in different combinations. DADI CDN is a fully-fledged on-the-fly image manipulation solution with support for edge caching in the network.
Also to note, you’re paid for contributing to the DADI network. Cloudflare is a private company. Where’s the incentive to contribute to their network? Actually, not sure anyone can contribute. So that’s a pretty significant point of difference.
In a country like China where access to some webpages (e.g., crypto exchanges) or services (e.g., Telegram) is routinely blocked, do you think it’s technically possible for the government to block the function of a DADI host? I understand that DADI network is not a sensitive website or service and there is no political reason or incentive to block a host. Nonetheless, as a layman I would like to know the possibility of some scenarios.
While it would be possible to block the entire network, this would mean blocking all sites and services, and would require the blocking of all Stargates and Gateways, which as the network grows, will become increasingly difficult to do. It wouldn’t necessarily be possible to block individual domains though. In addition to this, as the network will exist within China as well as outside, blocking it with a national firewall wouldn’t be an option.
Hypothetically if $ETH went to mush would DADI go down with the ship or are there ‘options’?
There are always options! We use ETH for smart contracts and benefit from its scale of adoption, but we are in no way tied to it. We could run our own chain, or use another with a smart contracts layer.
Follow up: Parallel chain?
Could be, but if it came to it I think we’d break completely, run a token swap and then move forward. So more of a fork.
In the event a bad actor got administrator access (sudo) to a Stargate running system, what is the worst that could happen? Will the bad actor be able to manipulate DNS request/replies? Any measures to detect this bad behaving and downrate reputation? Where can I find more about Stargates engineering?
Stargates monitor each other, so a single machine attack would result in the SG in question being off-lined. We take a very strict approach to security in this layer of the platform, with access only available via our secure VPN channel, and within this access is tied to named individuals by machine. In addition to this, we monitor all activity on Stargate machines, so there is no chance of anything happening without us being alerted.
Isn’t a distributed network more vulnerable than a single ‘centralized network’? More nodes means more doors to knock on, which in turn means increasing chances to gain unauthorized access and mess things up?
It’s a matter of perspective: a bunch of servers in a single location represents a single building/IP subset target to break in to/attack, whereas hundreds of thousands of machines in distributed locations would require:
- Knowing where those machines are
- Gaining physical access to the property
- Hacking into the machine
And if you manage of all this, you would find yourself with access to a fragment of a build, in an encrypted area of RAM. In short then, no. Distributed networks are inherently more secure - insanely more secure! - than centralized networks.
How many Stargates, Gateways and Hosts are presently running on the network?
21 Stargates, with a further 21 due online in the coming month. These are non-earning and part of the backbone, providing a geographical distributed DNS layer with coverage to match and exceed any other platform in market. We have an ASN from RIPE along with a DADI owned/operated IP subnet and are utilizing BGP routing at SG level. We have a Gateway for every Stargate as it stands. And finally, we have around 120 Hosts online.
Follow up: The hosts, are they mainly raspberries or all sorts of different computers/hardware?
They’re in the backbone, and are custom spec’d and built systems.
If the DADI wallet is no longer going to be developed, what mechanics are going to be used for management of POS, Nodes and customer side dApp usage? Also, will the smart contract be 3rd party validated and where are the private keys?
Our smart contracts are validated by a third party, including the originating contract. We use Solidified for this. Management of POS, Nodes and customer onboarding will be through my.dadi.cloud, which will provide a full set of mobile and desktop ready interfaces.
Will DADI’s current MRR from customers be shared with node owners after Constellation?
This one is easy. Yes.
How are the founding nodes delivered to international winners?
Well, having looked at teleportation we’ve ruled it out based on cost and impossibility. Instead, we’ll likely put them in a box and use air freight.
Follow up: When will you actually start delivering nodes?
As soon as the remaining components arrive! We’re beholden to our suppliers’ shipping schedules, which is frustrating. Everything else is ready to go.
What is your estimated timeframe for other operating systems to be able to participate as a node?
(b) Is there any particular order you will be making them available, i.e. Windows, iOS, Android, etc.?
We are not far away from a significant update to our product roadmap (next week or two) which will bring this detail, but we expect that after the Founding Nodes are onboarded and users are able to connect their own dedicated devices (by end Q4 2018) we’ll look to launch applications for MacOS and Windows, followed by iOS and Android mobile applications (likely Q1/2 2019). We also have plans for partnerships and more DADI-branded devices. Read more here: https://dadi.cloud/en/knowledge/network/how-to-contribute-to-the-dadi-network/
How will DADI address market saturation and the possibility of the network contracting because of customers and nodes leaving the network?
Given the size of the market we are entering - our major competitors are AWS, Google Cloud and Microsoft Azure for example - we don’t see this as a likely scenario. Even half a handful of percent of the market will sustain rapid growth for our product (to the moon and back, and some). This is why we are so optimistic about the future… 🙂
Follow up: What if AWS decentralized itself like DADI?
Not sure how they could do that. To do so would be to bastardize their own revenues, and they are beholden to their shareholders. Can you see them giving away 85% of their profits? Plus, even if they did (which they won’t) it wouldn’t change the size of the market.
What’s the current status of the DADI network now and has it been fully tested by team? How is it working on Beta and what have been the major challenges so far?
It is live and running CDN (our content delivery network) for a selection of clients - in this sense it is proving itself in the real world with real traffic. We are happy to say the challenges have been minimal, not least because we had a testnet proof of concept live even before our ICO. We are now working to scale the network, initially by adding the Founding Nodes and then applications to connect other devices such as desktop and laptop machines and beyond. We are constantly testing as a part of our development process. Perhaps our biggest challenge yet to be faced is balancing the onboarding of customers and contributors as the network grows - we have significant demand from both sides of this “transaction” and want to make sure we scale effectively!
How far down the track do you see devices for the ‘connected living room’ being done and is there a focus on one in particular right now?
Quite a bit to say here! The quick summary is that we’re fairly advanced, but it’s important to note that we’re addressing this through a multi-channel strategy that will see is working with various OEMs to access existing and future hardware. The Founding Nodes are conceived as the first step towards realising the vision – a plug and play device to be easily set up in the home.
And of course, DADI technology will also make use of spare capacity in the machines already there (such as laptops or desktops). We’re also working to produce more dedicated devices. (More on that in the coming months.) Plus, there’s the potential to leverage capacity in businesses and offices.
Here’s a useful read on this subject: https://dadi.cloud/en/knowledge/network/how-to-contribute-to-the-dadi-network/
Are there plans to introduce more dApps to the marketplace beyond the ones currently on the roadmap such as a VPN service routed through the DADI Network?
Yes, 100%. We have a (currently private) roadmap for this, and will be releasing updates as we move forward. This includes apps from new partners, and ultimately a marketplace for a broader array of third-party apps.
In the future when there’s token scarcity due to the network reaching larger capacity, will the surplus stake that is returned be subject to lockup or will it be available to roll into another node?
In this scenario there will be an additional weighting to earnings of +/- 20%. In the event that we found POS modifications were above this threshold, we would allow for the rolling in to another node, or for withdrawal from the network (after the standard time lock period).
Will the administrative things on my.dadi.cloud be available via an API to open up for third party integrations? For example, data like performance and management of nodes, current earnings, funds or whatever data might be in there.
Lovely idea. While this is not currently in the roadmap, we certainly won’t rule it out.
Assuming the worst, how difficult would it be to migrate the DADI project to a new chain (on the spectrum of ‘relatively easy’ to ‘extremely difficult’)?
The work required for this leans more toward the ‘relatively easy’ end of the spectrum. While it wouldn’t be a walk in the park, we do build our products with the future in mind - and this relates not only to the chosen blockchain platform but every technology we choose. Assuming, of course, that by ‘the worst’ you don’t mean Armageddon.
Is it possible to plug in a USB (USB 3.+ for speed) SSD to the Founding Node or an RPi? If so, with Store, Identity and the other apps coming onto the main, what size is recommended?
The Founding Nodes are self-contained units, so you won’t be able to plug in an SSD drive to them.
I have a personal website and blogs and would like to run it completely on DADI including the hosting. What’s the average cost for DADI to help me convert my website to CDN and Web and also host it on the DADI network?
It varies! Hit us up on email@example.com and we can get in to detail.
I live in one country for 6 months and another for 6 months. I would need to move my host(s) between the two. As much as this is possible, would it be penalised to a point it would be better to have it hosted? Can this also be answered for the founding node too?
There is no penalty to nodes switching networks. Upon joining, nodes will connect to the most topologically and geographically relevant gateway, and will host applications that the network requires.
Will there be opportunity to buy plug and play nodes? How much will they cost? Will they be insured, if so for how long? Are there any estimated on the yields of each node in each tier? Will all nodes in each tier be paid the same or will it be done on an access basis?
Yes. Although I’m not in a position to share any further details at this time.
Will there be tutorials or videos for setting up founding nodes? Will founding members have a separate communication channel Telegram/Discord? Will the Founding Nodes have the power supply and Ethernet cable?
Setting up Founding Nodes will be as simple as plug and play. You’ll plug in the ethernet cable (included), plug in the power cable (included), turn on the devices, and that’s it…online! And yes, there will be social channels for founding members.
How has the team managed the transition from being a real-world business to adapting to the crypto world and what are your advices for other companies looking to do the same?
That’s the biggest issue with crypto right there. Why would anyone think that it’s not the real world? If we want mass adoption - which I have to assume we all do - we need “real world” applications.
That there are projects out there that are not registered as businesses in their local jurisdictions is baffling to me. Not being set up in an official capacity means that you cannot address existing businesses, which means you are doing nothing to aid adoption or the broader perception of crypto.
That there are projects that justify their market cap based solely on some imaginary future where there are no governments and no businesses is insane. Utterly bonkers. Get real or get out.
Has the increase for POS been determined and if so what is it?
We’re still working on the basis of our original PoS requirement, but that doesn’t mean there won’t be an increase. It comes down to supply and demand.
Philosophically, what are the advantages of having a DADI token as opposed to staking ETH for example to support the distributed network?
Philosophically it’s about identity: understanding ourselves in the world as a community of like-minded individuals committed to a cause. So:
- It stakes it out as a concept in its own right
- It enables flexibility in future should we need to move away from a commitment to a single chain
- It enables individuals to track performance of DADI as a distinct entity in a varied ecosystem
When will customers start to pay for the services with DADI tokens?
As soon as our fiat on ramp goes live, which is expect in the coming few weeks. More soon.
Are you still actively working with new clients to build sites for them, or have you paused your traditional side of the business to favour efforts on the network?
Our channel strategy turns down the volume on this approach in favour of partnerships, but business that comes our way will be addressed. So yes, but also no.
How do you ensure one group or entity does not control too many of the nodes and centralize the network too much?
The network is a marketplace that preferences locality for pace of delivery. Centralising by bringing a group of nodes online in a single location where there is a mismatch with audience will lead to a loss of revenue, making the running of those nodes unprofitable.
Can you provide some estimates on the size and use of the DADI network within the next 6-12 months? Are you focusing on any particular niche? Could you describe your competitive edge over AWS et al in two sentences?
We’re not sharing projections at this stage and while we are not focusing on any particular niche, we have over 200 sites in the publishing space running DADI technology so this may be a natural starting point. As for the ‘two sentences’, we need only one: we are faster, more cost effective and by the nature of the network, more localized – which means we’re better for the environment. We have already received positive feedback from potential enterprise customers versus AWS, so we are confident.
Ah, that was two sentences 😂
What would be the best way for a contributor to contribute more than the typical if running a gateway is not possible due to hardware requirements? Will there be other ways to utilize excess tokens, say for those who have 100k+?
Totally depends on your line capacity for example, but there’s nothing to stop you running more Hosts. And gateways should be possible in this context - we’re looking at a possible rental model for backbone devices for example.