{
  "trx_id": "9fb0af07f9fbad6e059fb6bf28a4459d258b12dd",
  "block": 75356691,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-06-09T11:32:24",
  "op": [
    "transfer",
    {
      "from": "steemgoon.witnez",
      "to": "josephdenne",
      "amount": "0.001 STEEM",
      "memo": "Do you know that you can get free steem rewards and upvote for your witness vote? Cast your witness vote on @steemgoon.witnez, get daily steem rewards and free upvote to your post everyday."
    }
  ]
}

{
  "trx_id": "1418c3ce63119362a7ca505632a33fe4079e2f0b",
  "block": 38177221,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-14T20:39:54",
  "op": [
    "comment",
    {
      "parent_author": "josephdenne",
      "parent_permlink": "ama-recap-july-12th-2019",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-josephdenne-20191114t203954000z",
      "title": "",
      "body": "<center>[![](https://steemitimages.com/175x175/http://steemitboard.com/@josephdenne/level.png?201911141947)](https://steemitboard.com/@josephdenne)\r\n<center>@josephdenne, sorry to see you have less Steem Power.\r\nYour level lowered and you are now a **Red Fish**!</center>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

{
  "trx_id": "357d585c32cd525125cea148bf0f92d63c85d24e",
  "block": 38174955,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-14T18:46:24",
  "op": [
    "comment",
    {
      "parent_author": "josephdenne",
      "parent_permlink": "ama-recap-july-12th-2019",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-josephdenne-20191114t184623000z",
      "title": "",
      "body": "Congratulations @josephdenne! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@josephdenne/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@josephdenne) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=josephdenne)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 36209196,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2019-09-07T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "0.000002 VESTS",
      "deposited": "0.000 STEEM"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 36024398,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2019-08-31T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "257.407 STEEM"
    }
  ]
}

{
  "trx_id": "9f91b5e8a50fbc133ce54376ef9b5c43346d1c10",
  "block": 35995731,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-08-30T08:59:45",
  "op": [
    "transfer",
    {
      "from": "crypto.piotr",
      "to": "josephdenne",
      "amount": "0.001 STEEM",
      "memo": "Dear @josephdenne. I hope you don't mind this little memo. Every week I'm trying to help and promote content published by few selected authors and today I would like to share with you post published by my friend @honarparvar: \"WARNING: This might not be a trend!\". I'm curious if you believe in TA and what's your opinion on using indicators while trading crypto. Share your opinion, I read all valuable comments. Piotr // LINK: https://steemit.com/trading/@honarparvar/warning-this-might-not-be-a-trend"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 35828395,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2019-08-24T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "257.300 STEEM"
    }
  ]
}

{
  "trx_id": "86c34436dc7d59aeaea96a0ca468965f19ef6407",
  "block": 35744208,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-08-21T10:47:18",
  "op": [
    "transfer",
    {
      "from": "crypto.piotr",
      "to": "josephdenne",
      "amount": "0.003 STEEM",
      "memo": "Dear @josephdenne, I hope you don't mind this little memo. If you do then please let me know. // Good friend of mine is looking for \"dedicated Steemians interested in AI, VR, robotics, blockchain\". They would help him with small paid research. Perhaps this is something that could interest you. He explained quite in details what kind of tasks he needs to be performed (check out also comment section between and author and @creativeblue). Yours, LINK // https://steemit.com/ftin/@varioso/paid-research-looking-for-a-few-dedicated-steemians-interested-in-ai-vr-robotics-blockchain"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 35627134,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 10,
  "timestamp": "2019-08-17T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "257.189 STEEM"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 35425881,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2019-08-10T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "257.078 STEEM"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 35225524,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 115,
  "timestamp": "2019-08-03T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "256.968 STEEM"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 35024285,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2019-07-27T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "256.859 STEEM"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34881098,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 7,
  "timestamp": "2019-07-22T09:16:27",
  "op": [
    "author_reward",
    {
      "author": "josephdenne",
      "permlink": "ama-recap-july-12th-2019",
      "sbd_payout": "0.002 SBD",
      "steem_payout": "0.024 STEEM",
      "vesting_payout": "69.534787 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34881098,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 6,
  "timestamp": "2019-07-22T09:16:27",
  "op": [
    "curation_reward",
    {
      "curator": "josephdenne",
      "reward": "1.986708 VESTS",
      "comment_author": "josephdenne",
      "comment_permlink": "ama-recap-july-12th-2019"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34880981,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 13,
  "timestamp": "2019-07-22T09:10:36",
  "op": [
    "author_reward",
    {
      "author": "josephdenne",
      "permlink": "weekly-update-12th-july-2019",
      "sbd_payout": "0.002 SBD",
      "steem_payout": "0.024 STEEM",
      "vesting_payout": "67.548096 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34880981,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 12,
  "timestamp": "2019-07-22T09:10:36",
  "op": [
    "curation_reward",
    {
      "curator": "josephdenne",
      "reward": "17.880378 VESTS",
      "comment_author": "josephdenne",
      "comment_permlink": "weekly-update-12th-july-2019"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34823288,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2019-07-20T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "256.749 STEEM"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34715219,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2019-07-16T14:52:51",
  "op": [
    "author_reward",
    {
      "author": "josephdenne",
      "permlink": "weekly-update-05th-july-2019",
      "sbd_payout": "0.006 SBD",
      "steem_payout": "0.015 STEEM",
      "vesting_payout": "79.496208 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34715219,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2019-07-16T14:52:51",
  "op": [
    "curation_reward",
    {
      "curator": "josephdenne",
      "reward": "5.962215 VESTS",
      "comment_author": "josephdenne",
      "comment_permlink": "weekly-update-05th-july-2019"
    }
  ]
}

{
  "trx_id": "078052fc4bf5e2df1760077dbd75ef5db5f6c1e3",
  "block": 34679764,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-15T09:17:15",
  "op": [
    "vote",
    {
      "voter": "josephdenne",
      "author": "josephdenne",
      "permlink": "weekly-update-12th-july-2019",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "59568361ae556a14e615c528ee7fcc84385768c3",
  "block": 34679762,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-15T09:17:09",
  "op": [
    "vote",
    {
      "voter": "josephdenne",
      "author": "josephdenne",
      "permlink": "ama-recap-july-12th-2019",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "a64d9a2fbac84eff5c3b860ff126f75034747db2",
  "block": 34679748,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-15T09:16:27",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "ama-recap-july-12th-2019",
      "title": "AMA recap: July 12th, 2019",
      "body": "Friday’s AMA was focused on the rebrand of DADI to Edge, but that didn’t stop us covering a plethora of other topics. Those questions not answered this time will be picked up in the next AMA.\n\n![AMA.jpg](https://cdn.steemitimages.com/DQmRkoXKJQjRbHvNGgZSaFa966Q74WkKnkgWo8enGS3yxbc/AMA.jpg)\n\n## Question 1\n\n### What has been the most challenging thing to create while setting up this new brand?\n\nRavi 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.\n\nJoseph Denne: I'd say that you've definitely achieved! Super happy with the work\n\n## 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?\n\nRavi 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.\n\n## Question 2\n\n### How long has you been working on the rebrand to Edge?\n\nJoseph 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.\n\n## Question 3\n\n### In your opinion, what makes the brand identity that your team has created unique?\n\nRavi 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.\n\nKey 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.\n\n## Question 4\n\n### Is there any specific message or emotion you wanted expressed when designing this new brand?\n\nRavi 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.\n\n## Question 5\n\n### Will this new style also be used for the products you make together with Blond and how will this collaboration be in the future?\n\nRavi 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.\n\n## Question 6\n\n### Can you tell us about the reason for the rebrand?\n\nJoseph 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.\n\n## Question 7\n\n### How do you comment the modified picture showing $EDGE being #7 on CoinMarketCap with your investors down 90%?\n\nJoseph 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.\n\n## Question 8\n\n### What does a clean start with the new brand mean for the team and the future?\n\nJoseph 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.\n\n## Question 9\n\n### 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.\n\nArthur 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.\n\nWhat 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.\n\nJoseph Denne: That's a yes. But it's not our core focus in Edge right now.\n\n## Question 10\n\n### How does the DADI rebrand impact the relationship with the foundation?\n\nJoseph 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.\n\n## Question 11\n\n### Will DADI support the QUALCOMM Snapdragon Secure Processing Unit feature?\n\nArthur 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.\n\n## Question 12\n\n### 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?\n\nJoseph 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.\n\n## Question 13\n\n### 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?\n\nArthur 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.\n\n## Question 14\n\n### Have you considered onboarding users from other Crypto projects who need to run nodes, like Tierion?\n\nJoseph 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.\n\n## Question 15\n\n### 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?\n\nJoseph 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.\n\n## Question 16\n\n### 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.\n\nJoseph 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.\n\n## Question 17\n\n### 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?\n\nArthur 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.\n\nJoseph 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.\n\n## Question 18\n\n### 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?\n\nJoseph 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.\n\n## Question 19\n\n### When can we expect the updated roadmap and updated website (please specify what coming weeks mean)?\n\nJoseph Denne: As I think I mentioned in my last weekly update, next week! (And if I didn't, I meant to!)\n\n## Question 20\n\n### 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?\n\nArthur 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.\n\n## Question 21\n\n### 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)\n\nArthur 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.\n\n## Question 22\n\n### When will the first staking for Gateways and Stargates take place?\n\nJoseph Denne: September for backbone rentals. With some potential for onboarding to start sooner.\n\n## Question 23\n\n### Will Stargates have the ability to censor specific sites, or will it be up to DADI only?\n\nArthur 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.\n\n## Question 24:\n\n### How is the Technology Partner programme going? Is this still a thing?\n\nJoseph 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.\n\n## Question 25\n\n### Is the software on the FNs stable now? Those with original software have the same as the ones with new SD cards?\n\nArthur 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.\n\n## Question 26\n\n### How could the network withstand an organized attack? (scrape the web for sites running in DADI network, DDOS all those sites simultaneous)\n\nArthur 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.\n\n## Question 27\n\n### Does DADI have any international expansion plans?\n\nJoseph Denne: Yes, these are being worked on. As soon as there's something to share on this front, we will do so.\n\n## Question 28\n\n### I heard DADI was working on OEM hardware too. Does this involve design and production of PCB schemes and boards?\n\nJoseph 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.\n\n## Question 29\n\n### How did the network upgrade go? Can we expect a thorough report of the process?\n\nArthur 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!\n\n## Question 30\n\n### With the branding done, what will the next main challenge be for Ravi and his team?\n\nRavi 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.\n\nJoseph Denne: It's worth noting that we've made some additions to [https://brand.edge.network](https://brand.edge.network) as well, and that this will be kept up to date as we go.\n\n## Question 31\n\n### Can we have a whitelist for Telegram to allow admins to let trusted members of the community post links and images?\n\nJoseph 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.",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"image\":[\"https://cdn.steemitimages.com/DQmRkoXKJQjRbHvNGgZSaFa966Q74WkKnkgWo8enGS3yxbc/AMA.jpg\"],\"links\":[\"https://brand.edge.network\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "66235e4b3cdcde34c908382d28ab29a367a0d3fa",
  "block": 34679631,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-15T09:10:36",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "weekly-update-12th-july-2019",
      "title": "Weekly update: 12th July, 2019",
      "body": "As part of our ongoing commitment to transparency and development in the open, we are now providing weekly updates to our community, drawn from internal all-team updates. This is the 18th of these updates, originally posted to Telegram.\n\n![weekly-staus-update-12.07.png](https://cdn.steemitimages.com/DQmSNvreNLGsJ7AfCsAEYfLrYJ7HuKb25Gf1iDJ7FQnPU71/weekly-staus-update-12.07.png)\n\nMy goodness it’s been hot this week ☀️ Averaging 30º in London… and it feels a hell of a lot hotter inside without air conditioning.\n\nHere’s hoping the sun stays put through the weekend.\n\nWe had an AMA today, so this update will be quick.\n\nThe 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.\n\nArthur will be posting an article about it early next week.\n\nWe are continuing work on the new site for edge,network, which is scheduled for live next week.\n\nThe 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.\n\nThey also removed the version portion of collection URLs in API, simplifying the URL used by data consumers.\n\nA list component was added to our interfaces, allowing editors to insert, update and reorder entries within a field.\n\nAnd they made a start on the migration of our existing documentation to reflect the change in focus as we roll out the Edge rebrand.\n\nWe made a number of updates to integrations with Signify (a fraud prevention system) and Nimble (a streaming media platform) for one of our customers.\n\nA 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.\n\n+We had a handful of meetings with prospective customers for the network\n\n+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\n\n+We delivered integration docs for CDN to a new property that will be moving to the network\n\nAnd that’s it from me! I hope you enjoy your weekends 🙂",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"image\":[\"https://cdn.steemitimages.com/DQmSNvreNLGsJ7AfCsAEYfLrYJ7HuKb25Gf1iDJ7FQnPU71/weekly-staus-update-12.07.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34630382,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2019-07-13T16:06:12",
  "op": [
    "author_reward",
    {
      "author": "josephdenne",
      "permlink": "mainnet-upgrade-july-2019",
      "sbd_payout": "0.011 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "79.510308 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34621927,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2019-07-13T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "256.640 STEEM"
    }
  ]
}

{
  "trx_id": "4dfd18cbfe529e21e7e107077a84833c7815588a",
  "block": 34517744,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-09T18:08:15",
  "op": [
    "vote",
    {
      "voter": "steemitboard",
      "author": "josephdenne",
      "permlink": "introducing-edge",
      "weight": 100
    }
  ]
}

{
  "trx_id": "dafdb6302ac2c12c8e4e13dc82b1d8d269d54be5",
  "block": 34517743,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-09T18:08:12",
  "op": [
    "comment",
    {
      "parent_author": "josephdenne",
      "parent_permlink": "introducing-edge",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-josephdenne-20190709t180814000z",
      "title": "",
      "body": "Congratulations @josephdenne! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n<table><tr><td><img src=\"https://steemitimages.com/60x70/http://steemitboard.com/@josephdenne/posts.png?201907091707\"></td><td>You published more than 10 posts. Your next target is to reach 20 posts.</td></tr>\n</table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@josephdenne) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=josephdenne)_</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\nTo support your work, I also upvoted your post!\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

{
  "trx_id": "1d37df48a7d67b55c20208b19a3067c2c4e039cb",
  "block": 34516198,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-09T16:50:51",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "introducing-edge",
      "title": "Introducing Edge",
      "body": "Today we are thrilled to be able to share the branding for Edge.\n\n![edge.jpg](https://cdn.steemitimages.com/DQmcWPuXm49mTudcuYB7aiZ2YSXGqr7Efztd5zd22NB5zpx/edge.jpg)\n\nEdge represent 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.\n\nThe core components are presented below, and you can access a full introduction to the brand here: https://brand.edge.network\n\n## Logo concept\n\n![Concept.jpg](https://cdn.steemitimages.com/DQmbuBH73DiZnFWXbgmBHytYUoYUVY7HSpEre3phXFnK1go/Concept.jpg)\n\nEdge 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.\n\nOur 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.\n\nReference 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.\n\nThe ‘e’ is edge.\n\n## Icon\n\n![Icon.jpg](https://cdn.steemitimages.com/DQmVoz6kg2eYpfgzDT1eo6Czq9BesrzYngxkue9rmmhNRYg/Icon.jpg)\n\nThe 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.\n\nUsing 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.\n\nThe Edge icon is a standalone symbol used in isolation when the wordmark is not appropriate or relevant, for example as a currency symbol.\n\n## Wordmark\n\n![Logo.jpg](https://cdn.steemitimages.com/DQmceo4iKdxMqCAQCBBYonrbYBwREzpeZ96gNS3ZYgkX1FU/Logo.jpg)\n\nThe 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.",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"image\":[\"https://cdn.steemitimages.com/DQmcWPuXm49mTudcuYB7aiZ2YSXGqr7Efztd5zd22NB5zpx/edge.jpg\",\"https://cdn.steemitimages.com/DQmbuBH73DiZnFWXbgmBHytYUoYUVY7HSpEre3phXFnK1go/Concept.jpg\",\"https://cdn.steemitimages.com/DQmVoz6kg2eYpfgzDT1eo6Czq9BesrzYngxkue9rmmhNRYg/Icon.jpg\",\"https://cdn.steemitimages.com/DQmceo4iKdxMqCAQCBBYonrbYBwREzpeZ96gNS3ZYgkX1FU/Logo.jpg\"],\"links\":[\"https://brand.edge.network\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "227ae026b368973ed57e7a25b6fe1d20d2336f27",
  "block": 34514342,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-09T15:18:00",
  "op": [
    "vote",
    {
      "voter": "fyrstikken",
      "author": "josephdenne",
      "permlink": "weekly-update-05th-july-2019",
      "weight": 100
    }
  ]
}

{
  "trx_id": "1185031d2ff040b52b58c734d4174f0a1a997fec",
  "block": 34513882,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-09T14:54:57",
  "op": [
    "vote",
    {
      "voter": "josephdenne",
      "author": "josephdenne",
      "permlink": "weekly-update-05th-july-2019",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "a0cf5b26a377bab19a06e257ca82a1367cd65035",
  "block": 34513840,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-09T14:52:51",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "weekly-update-05th-july-2019",
      "title": "Weekly update: 05th July, 2019",
      "body": "As part of our ongoing commitment to transparency and development in the open, we are now providing weekly updates to our community, drawn from internal all-team updates. This is the 17th of these updates, originally posted to Telegram.\n\n![weekly-staus-update-05.07.png](https://cdn.steemitimages.com/DQmeeW7bGYcv2UyLa2EUgpvBCKwghiWttz4BxWMWmCJkNb4/weekly-staus-update-05.07.png)\n\nToday'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.\n\nThe network team completed the mammoth task of configuring the deployment scripts for the update.\n\nThis includes the completion of the final parts of the network-sync scripts.\n\nThe 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.\n\nWe'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.\n\nStargate 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.\n\nAPI 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.\n\nThis work is now 80% done.\n\nA 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.\n\nRavi 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.\n\nI 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).\n\nThis will be ready next week, and will be made available on brand.edge.network\n\nWe made significant progress migrating an existing customer's data layer to API, which is a big step toward full migration to the network.\n\nTiipr 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.\n\nOur 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.\n\nWe started early stage discussions with a new partner, which should open up a good sales channel for network services.\n\nWe 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.\n\nFinally 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.\n\nAnd that's it! Enjoy your weekends.",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"image\":[\"https://cdn.steemitimages.com/DQmeeW7bGYcv2UyLa2EUgpvBCKwghiWttz4BxWMWmCJkNb4/weekly-staus-update-05.07.png\"],\"links\":[\"https://github.com/dadi/publish/issues/389\",\"http://www.greatbritishbusinessshow.co.uk/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34455570,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 9,
  "timestamp": "2019-07-07T14:16:57",
  "op": [
    "author_reward",
    {
      "author": "josephdenne",
      "permlink": "roadmap-updates",
      "sbd_payout": "0.015 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "93.458206 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34455570,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 8,
  "timestamp": "2019-07-07T14:16:57",
  "op": [
    "curation_reward",
    {
      "curator": "josephdenne",
      "reward": "1.988472 VESTS",
      "comment_author": "josephdenne",
      "comment_permlink": "roadmap-updates"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34455455,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 5,
  "timestamp": "2019-07-07T14:11:12",
  "op": [
    "author_reward",
    {
      "author": "josephdenne",
      "permlink": "weekly-update-28th-june-2019",
      "sbd_payout": "0.015 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "91.469755 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34455455,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2019-07-07T14:11:12",
  "op": [
    "curation_reward",
    {
      "curator": "josephdenne",
      "reward": "1.988472 VESTS",
      "comment_author": "josephdenne",
      "comment_permlink": "weekly-update-28th-june-2019"
    }
  ]
}

{
  "trx_id": "c8c8e20ea9a9dc52fc92699daa8b200412c2da15",
  "block": 34429467,
  "trx_in_block": 31,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-06T16:30:30",
  "op": [
    "vote",
    {
      "voter": "fyrstikken",
      "author": "josephdenne",
      "permlink": "mainnet-upgrade-july-2019",
      "weight": 100
    }
  ]
}

{
  "trx_id": "f6e120753938e7223ce079743ef40071e6ea44fc",
  "block": 34428996,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-06T16:06:57",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "mainnet-upgrade-july-2019",
      "title": "Mainnet upgrade, July 2019",
      "body": "@@ -1,12 +1,133 @@\n+!%5BmainnetUpgrade.png%5D(https://cdn.steemitimages.com/DQmPuWMhht5dyrf51rTxCE7LtQ9QHcVeTtBiYNjuQm8APh7/mainnetUpgrade.png)%0A%0A\n ## Scale%0A%0AIm\n",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"image\":[\"https://cdn.steemitimages.com/DQmPuWMhht5dyrf51rTxCE7LtQ9QHcVeTtBiYNjuQm8APh7/mainnetUpgrade.png\"]}"
    }
  ]
}

{
  "trx_id": "2fd728e319a44ce02217f1c180a7d71b701b262b",
  "block": 34428990,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-06T16:06:39",
  "op": [
    "vote",
    {
      "voter": "josephdenne",
      "author": "josephdenne",
      "permlink": "mainnet-upgrade-july-2019",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "390c0bf00790caef964314cdc431b880f220b557",
  "block": 34428981,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-07-06T16:06:12",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "mainnet-upgrade-july-2019",
      "title": "Mainnet upgrade, July 2019",
      "body": "## Scale\n\nImportant in the networks growth is its ability to accept the an increasing number of Hosts without compromising the speed in which vital coordination components calculate and synchronise topology.\n\nInitial 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.\n\nOne 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.\n\n## Performance\n\nWhen 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:\n\n### Health\n\nThe 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.\n\nThe 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.\n\n### Metadata\n\nUntil 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.\n\n## Security\n\nACL 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.\n\nA 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.\n\nThe 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.\n\n## What you need to do?\n\nIf 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.",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34420521,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2019-07-06T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "256.534 STEEM"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34307009,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2019-07-02T10:14:57",
  "op": [
    "author_reward",
    {
      "author": "josephdenne",
      "permlink": "weekly-update-21st-june-2019",
      "sbd_payout": "0.018 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "107.410110 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34307009,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2019-07-02T10:14:57",
  "op": [
    "curation_reward",
    {
      "curator": "josephdenne",
      "reward": "9.945380 VESTS",
      "comment_author": "josephdenne",
      "comment_permlink": "weekly-update-21st-june-2019"
    }
  ]
}

{
  "trx_id": "60b1c9beca10a8fe07442b04abb55c35712ca59e",
  "block": 34258926,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T18:08:42",
  "op": [
    "vote",
    {
      "voter": "steemitboard",
      "author": "josephdenne",
      "permlink": "announcing-our-rebrand",
      "weight": 100
    }
  ]
}

{
  "trx_id": "77eb375cc3669dd7625fb1da5293186e23c4c3bc",
  "block": 34258925,
  "trx_in_block": 32,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T18:08:39",
  "op": [
    "comment",
    {
      "parent_author": "josephdenne",
      "parent_permlink": "announcing-our-rebrand",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-josephdenne-20190630t180841000z",
      "title": "",
      "body": "Congratulations @josephdenne! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n<table><tr><td><img src=\"https://steemitimages.com/60x70/http://steemitboard.com/@josephdenne/votes.png?201906301708\"></td><td>You distributed more than 10 upvotes. Your next target is to reach 50 upvotes.</td></tr>\n</table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@josephdenne) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=josephdenne)_</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\nTo support your work, I also upvoted your post!\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

{
  "trx_id": "caf42365a28d04cc2dcda84a1894282c290d266d",
  "block": 34255541,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T15:19:18",
  "op": [
    "vote",
    {
      "voter": "pinoy",
      "author": "josephdenne",
      "permlink": "roadmap-updates",
      "weight": 1000
    }
  ]
}

{
  "trx_id": "a50777c4bef36f8c140bbeb18a0f93ace886a921",
  "block": 34255238,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T15:04:06",
  "op": [
    "vote",
    {
      "voter": "yehey",
      "author": "josephdenne",
      "permlink": "roadmap-updates",
      "weight": 1000
    }
  ]
}

{
  "trx_id": "0ef7b73ce41dd7a75b6fe2b314f62bd12220960f",
  "block": 34254482,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T14:26:15",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "roadmap-updates",
      "title": "Roadmap updates",
      "body": "@@ -1,8 +1,135 @@\n+!%5Bog-roadmap-update.png%5D(https://cdn.steemitimages.com/DQmWHnrecnrqCagCCMwN7jNPobpfA4gkH8iZinZ7vSabiZY/og-roadmap-update.png)%0A%0A\n We will \n",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"image\":[\"https://cdn.steemitimages.com/DQmWHnrecnrqCagCCMwN7jNPobpfA4gkH8iZinZ7vSabiZY/og-roadmap-update.png\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/10-open-source.png\"],\"links\":[\"https://dadi.cloud/en/knowledge/network/network-level-services/\",\"https://github.com/dadi/cli\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "619b56bb382c612fed6a5aa94b0373bfee455f9f",
  "block": 34254466,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T14:25:27",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "announcing-our-rebrand",
      "title": "Announcing our rebrand",
      "body": "![[email protected]](https://cdn.steemitimages.com/DQmfLUf3p7CAznGicK3w9RLLDTw9YUhTur8SNjA2wtYniJb/[email protected])\n\nAs followers of our project will be aware, we have been in the process of refreshing our brand for the past few months, and working to focus on network level services since the end of 2018.\n\nToday we are thrilled to announce that we are rebranding to Edge.\n\nWe 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.\n\nRunning 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.\n\nFor 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.\n\nNetwork 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.\n\nAndreessen 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/)\n\nThe 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.\n\nOur 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.\n\nRebranding to Edge places us at the heart of this paradigm shift.",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"image\":[\"https://cdn.steemitimages.com/DQmfLUf3p7CAznGicK3w9RLLDTw9YUhTur8SNjA2wtYniJb/[email protected]\"],\"links\":[\"https://a16z.com/2016/12/16/the-end-of-cloud-computing/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "f78ebb9aecbfc5e69662fd51fb6f2dcf368d47a0",
  "block": 34254311,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T14:17:42",
  "op": [
    "vote",
    {
      "voter": "josephdenne",
      "author": "josephdenne",
      "permlink": "roadmap-updates",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "a925c92a6a4562512e76c91e1c0f838c35c80785",
  "block": 34254296,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T14:16:57",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "roadmap-updates",
      "title": "Roadmap updates",
      "body": "We will be releasing a full roadmap update along with the launch of our new site in the coming weeks. In the meantime, here are some of the biggest updates that the next 12-18 months have in store for the Edge network.\n\n## 1\\. Brand update\n\nStart: already started / Release target: mid July\n\n![](https://api.dadi.cloud:443/media/2019/06/28/[email protected])\n\nWe are refreshing and repositioning our brand to focus on [core network services](https://dadi.cloud/en/knowledge/network/network-level-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.\n\nThe brand update includes the release of a new version of our site.\n\n## 2\\. Multi DC, Vault, ACL and DNS\n\nStart: already started / Release target: 11th July\n\n![](https://api.dadi.cloud:443/media/2019/06/28/[email protected])\n\nOur 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.\n\n## 3\\. DNS updates\n\nStart: already started / Release target: 11th July\n\n![](https://api.dadi.cloud:443/media/2019/06/28/[email protected])\n\nThe 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.\n\n## 4\\. Network CLI\n\nStart: July 15th / Release target: August 31st 2019\n\n![](https://api.dadi.cloud:443/media/2019/06/28/[email protected])\n\nThe 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](https://github.com/dadi/cli))\n\n## 5\\. Self onboarding: Hosts\n\nStart: July 15th / Release target: August 31st 2019\n\nSelf 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.\n\nIn 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.\n\n## 6\\. Earning automation\n\nStart: July 15th / Release target: August 20th\n\nEarning 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.\n\n## 7\\. Edge storage completion\n\nStart: Ongoing / Release target: October 1st 2019\n\n![](https://api.dadi.cloud:443/media/2019/06/28/[email protected])\n\nEdge 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.\n\n## 8\\. CDN conversion to Go\n\nStart: ongoing / Release target: TBC\n\n![](https://api.dadi.cloud:443/media/2019/06/28/[email protected])\n\nThe 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.\n\n## 9\\. Backbone rentals\n\nRelease target: September\n\n![](https://api.dadi.cloud:443/media/2019/06/28/[email protected])\n\nRentals 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.\n\n## 10\\. Edge for mobile: iOS\n\nStart: ongoing / Release target: TBC\n\n![](https://api.dadi.cloud:443/media/2019/06/28/[email protected])\n\nThe 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.\n\n## 11\\. Full Open source\n\nRelease target: September/October\n\n![](https://api.dadi.cloud:443/media/2019/06/28/10-open-source.png)\n\nWe 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.\n\n## 12\\. Web services migration\n\nRelease target: July/August\n\nWe 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.\n\nThis 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).",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"image\":[\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/[email protected]\",\"https://api.dadi.cloud:443/media/2019/06/28/10-open-source.png\"],\"links\":[\"https://dadi.cloud/en/knowledge/network/network-level-services/\",\"https://github.com/dadi/cli\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "77005ccb00363ffd90d2077d29ad219629b59f66",
  "block": 34254204,
  "trx_in_block": 50,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T14:12:21",
  "op": [
    "vote",
    {
      "voter": "millibot",
      "author": "josephdenne",
      "permlink": "weekly-update-28th-june-2019",
      "weight": 500
    }
  ]
}

{
  "trx_id": "340218d8d0b6f8a5f71a153a227f4ee6e8421840",
  "block": 34254195,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T14:11:54",
  "op": [
    "vote",
    {
      "voter": "josephdenne",
      "author": "josephdenne",
      "permlink": "weekly-update-28th-june-2019",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "dab85101273e756f9c0a549335ce70edeaa14b56",
  "block": 34254181,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-30T14:11:12",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "weekly-update-28th-june-2019",
      "title": "Weekly update: 28th June, 2019",
      "body": "Happy Friday all 👋\n\nWe'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/\n\nWe 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.\n\nThis will be an important milestone for us as it means that we will be in a position to fully open source the network codebase.\n\nPursuing 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.\n\nThe third party report on the network will be ready ahead of moving the code base to full open source.\n\nWhile 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.\n\nWe've been contacted by and are exploring a research opportunity with an aerospace company.\n\nWe kicked off planning for a presence at a major event in London in November. More details in the coming weeks.\n\nThe network engineering team have been pretty much flat out:\n\nThey 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.\n\nThey 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.\n\nThey 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.\n\nAPI’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\n\nOur code quality tools have been improved with consistent linting and code formatting (https://github.com/dadi/code-standards) now applied to Publish and API.\n\nThe team also released the first release candidate of Publish v3.0 (which if you remember from previous updates is a React build).\n\nAnd they closed out a series of Publish issues (https://github.com/dadi/publish/pulls?q=is%3Apr+is%3Aclosed).\n\nAnd finally...\n\nWe are going to be rebranding DADI completely. You can find out more here:\n\nhttps://dadi.cloud/en/updates/announcements/announcing-our-rebrand/\n\nBranding and design will be previewed early next week.\n\nEnjoy your weekends 👊",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"links\":[\"https://dadi.cloud/en/updates/network/roadmap-updates/\",\"https://github.com/dadi/test-tools\",\"https://travis-ci.org/dadi/api-mongodb/jobs/551251808\",\"https://github.com/dadi/code-standards\",\"https://github.com/dadi/publish/pulls?q=is%3Apr+is%3Aclosed\",\"https://dadi.cloud/en/updates/announcements/announcing-our-rebrand/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34219247,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2019-06-29T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "256.429 STEEM"
    }
  ]
}

{
  "trx_id": "d43c3a03ff18e653068d6d358e8ffec170df22b6",
  "block": 34118479,
  "trx_in_block": 46,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-25T20:58:12",
  "op": [
    "comment",
    {
      "parent_author": "josephdenne",
      "parent_permlink": "weekly-update-21st-june-2019",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-josephdenne-20190625t205814000z",
      "title": "",
      "body": "Congratulations @josephdenne! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n<table><tr><td><img src=\"https://steemitimages.com/60x60/http://steemitboard.com/img/notifications/firstpayout.png\"></td><td>You got your First payout</td></tr>\n</table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@josephdenne) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=josephdenne)_</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/the-steem-community-has-lost-an-epic-member-farewell-woflhart\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmQWnM36SWCPGn98nY83M1ArgweMz5fnovQEp2E4FiDdug/Wolfhart_header.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/the-steem-community-has-lost-an-epic-member-farewell-woflhart\">The Steem community has lost an epic member! Farewell @woflhart!</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

{
  "trx_id": "4ac293ec6718b8ab794e620088ebd582039c3692",
  "block": 34106900,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-25T11:18:09",
  "op": [
    "vote",
    {
      "voter": "pinoy",
      "author": "josephdenne",
      "permlink": "weekly-update-21st-june-2019",
      "weight": 1000
    }
  ]
}

{
  "trx_id": "107e4e056f9c622a4c04d7b7c27d2da2802eda15",
  "block": 34106595,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-25T11:02:54",
  "op": [
    "vote",
    {
      "voter": "yehey",
      "author": "josephdenne",
      "permlink": "weekly-update-21st-june-2019",
      "weight": 1000
    }
  ]
}

{
  "trx_id": "b4ec30e1afaeb09ebefa73abab52b23559e946db",
  "block": 34105691,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-25T10:17:42",
  "op": [
    "vote",
    {
      "voter": "josephdenne",
      "author": "josephdenne",
      "permlink": "weekly-update-21st-june-2019",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "d52d4cb85ef8c4614b7620804c01d66005a3f0d8",
  "block": 34105670,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-25T10:16:39",
  "op": [
    "vote",
    {
      "voter": "microbot",
      "author": "josephdenne",
      "permlink": "weekly-update-21st-june-2019",
      "weight": 500
    }
  ]
}

{
  "trx_id": "612644208609d278bcaf6deb1f56c2a17ac1af44",
  "block": 34105636,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-25T10:14:57",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "weekly-update-21st-june-2019",
      "title": "Weekly update: 21st June, 2019",
      "body": "Hi everyone 👋 The sun is shining here and Bitcoin is up, so all is good with the world ☀️\n\nI have quite a bit to update you on today... here we go!\n\nMoses Skoda joined the team this week. He's working on our services layer.\n\nWe'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.\n\nAnd I expect us to be rolling out the changes in the first half of July.\n\nSuffice to say, Ravi's done an awesome job.\n\nWe had the PPA awards this week, where Paul presented one of the gongs:\n\n![photo_2019-06-25 11.07.05.jpeg](https://cdn.steemitimages.com/DQmaysnmfy4kg4aGR6xy17Jv9Ca3pxKFBNx57UvyY5YALZZ/photo_2019-06-25%2011.07.05.jpeg)\n\nIt was a really positive evening for us – we have 20+ new conversations opened up on the back of the event.\n\nI met with David Wilde to plan introductions to local government, and to explore methods for supporting delivery, for example by embedded our networking software within local data centres.\n\nWe also discussed the detail of for his ongoing engagement with the project, covering speaking arrangements, articles and an approach for central government.\n\nI wrote an article for Fintech magazine which should be published next week. I'll share the link when it's published.\n\nWe kicked off with our new PR. Wind up time can take a while, but it's underway.\n\nWe've increased our engagement with one of our existing customers, who are now working with us on a deeper level to integrate core services.\n\nOne 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.\n\nWe have another promising engagement in construction industry, which is the final throws of being defined before kicking off. As soon as we have more to share, we will.\n\nThe 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.\n\nThey 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.\n\nIt 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.\n\nRoadmap updates and timings were also completed this week. Items in the roadmap include:\n\n- The rebrand\n- Multi DC\n- Vault\n- ACL\n- DNS\n- Network CLI\n- Self onboarding for Hosts\n- Earning automation (DAO)\n- Edge storage\n- Explorer enhancements\n- Backbone rentals\n- Self onboarding for Gateways and Stargates\n- Edge for mobile and existing mobile apps\n- Consumer interfaces\n- ECUs\n- Edge cache\n- CDN comnsumer interfaces\n- Dates for Open Sourcing the core tech\n\n...And a bunch more besides\n\n!\n\nWe 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.\n\nEcohustler went viral.\n\nOne 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.\n\nThat's an increase in traffic of 16,566%. Pretty significant! Uptime during the stampede? 100%\n\nAPI version 5 was released!\n\nRelease notes as follows:\n\nhttps://github.com/dadi/api/releases/tag/v5.0.0\n\nAnd documentation can be found here:\n\nhttps://github.com/dadi/api/releases/tag/v5.0.0\n\nWe'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.\n\nThe reason for this is to allow us to focus the network on network-level services, better supporting its go to market.\n\nThis 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).\n\nWe'll be announcing this formally when the full branding work for the proposition has been completed. We expect this to be in July.\n\nThe 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.\n\nWith regard to token price, I'm happy to see a continued upward trend since early May (+32%).\n\nThe 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.\n\nAnd that's it this week. Enjoy your weekends ✌️",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"image\":[\"https://cdn.steemitimages.com/DQmaysnmfy4kg4aGR6xy17Jv9Ca3pxKFBNx57UvyY5YALZZ/photo_2019-06-25%2011.07.05.jpeg\"],\"links\":[\"https://ecohustler.com/article/one-corporation-to-pollute-them-all/\",\"https://github.com/dadi/api/releases/tag/v5.0.0\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 34017878,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 35,
  "timestamp": "2019-06-22T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "256.324 STEEM"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 33848723,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2019-06-16T11:44:51",
  "op": [
    "author_reward",
    {
      "author": "josephdenne",
      "permlink": "ama-recap-june-07th-2019",
      "sbd_payout": "0.024 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "119.455147 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 33848280,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 5,
  "timestamp": "2019-06-16T11:22:39",
  "op": [
    "author_reward",
    {
      "author": "josephdenne",
      "permlink": "edge-ssl",
      "sbd_payout": "0.025 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "123.437096 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 33848280,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2019-06-16T11:22:39",
  "op": [
    "curation_reward",
    {
      "curator": "josephdenne",
      "reward": "1.990920 VESTS",
      "comment_author": "josephdenne",
      "comment_permlink": "edge-ssl"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 33848161,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 6,
  "timestamp": "2019-06-16T11:16:42",
  "op": [
    "author_reward",
    {
      "author": "josephdenne",
      "permlink": "weekly-update-07th-june-2019",
      "sbd_payout": "0.026 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "129.409889 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 33848161,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2019-06-16T11:16:42",
  "op": [
    "curation_reward",
    {
      "curator": "josephdenne",
      "reward": "35.836584 VESTS",
      "comment_author": "josephdenne",
      "comment_permlink": "weekly-update-07th-june-2019"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 33816715,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2019-06-15T09:02:54",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "josephdenne",
      "to_account": "josephdenne",
      "withdrawn": "510136.463544 VESTS",
      "deposited": "256.220 STEEM"
    }
  ]
}

{
  "trx_id": "e1681eb769cddafb5d96bbba2e0c031ca3f8f6a2",
  "block": 33649070,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-09T13:09:45",
  "op": [
    "comment",
    {
      "parent_author": "josephdenne",
      "parent_permlink": "ama-recap-june-07th-2019",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-josephdenne-20190609t130947000z",
      "title": "",
      "body": "Congratulations @josephdenne! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n<table><tr><td><img src=\"https://steemitimages.com/60x70/https://steemitboard.com/@josephdenne/voted.png?201906091203\"></td><td>You received more than 10 upvotes. Your next target is to reach 50 upvotes.</td></tr>\n</table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@josephdenne) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=josephdenne)_</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

{
  "trx_id": "38365aecfcc291a757fae5f15bf197d25199b6a0",
  "block": 33648020,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-09T12:17:00",
  "op": [
    "vote",
    {
      "voter": "pinoy",
      "author": "josephdenne",
      "permlink": "weekly-update-07th-june-2019",
      "weight": 1000
    }
  ]
}

{
  "trx_id": "ee7b811fc0123e62a67649eb5ca0443851495ba4",
  "block": 33647718,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-09T12:01:54",
  "op": [
    "vote",
    {
      "voter": "yehey",
      "author": "josephdenne",
      "permlink": "weekly-update-07th-june-2019",
      "weight": 1000
    }
  ]
}

{
  "trx_id": "bb2a36c5883d2f645f868465d39ca27fdf2bc439",
  "block": 33647384,
  "trx_in_block": 50,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-09T11:45:12",
  "op": [
    "vote",
    {
      "voter": "josephdenne",
      "author": "josephdenne",
      "permlink": "ama-recap-june-07th-2019",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "a2afa17bac4cd23ac4450cb9750cc603c1b01a87",
  "block": 33647377,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-09T11:44:51",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "edge",
      "author": "josephdenne",
      "permlink": "ama-recap-june-07th-2019",
      "title": "AMA recap: June 07th, 2019",
      "body": "_Friday’s AMA was another stacked affair. With 100’s of questions to get though, we didn’t manage to get to them all in the two hour session. Those not covered this time will be picked up in the next AMA._\n\nhttps://cdn.dadi.cloud/media/2019/06/09/og-ama-07-06.png?w=1600&q=70\n\n## Question 1\n\n### 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?\n\nJoseph 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 existing within the network. In summary these breakdown as follows (in no particular order):\n\n1.    Smart contracts. The ability to script value transfer based on pre-coded events;\n2.    Node-level data storage. Storing all network-level activity against individual nodes and making this directly explorable;\n3.    Coin functionality. The ability to mint coins and for these to be able to be integrated in to the broader ecosystem (exchanges etc.). \n\nIt 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.\n\n## Question 2\n\n### 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.\n \nArthur 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.\n\n## Question 3\n \n### 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?\n \nArthur 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!\n \n## Question 4\n \n### How is DADI going to promote business outside Europe?\nThere 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.\n \nJoseph 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.\n \n## Question 5 \n \n### Can you share an ETA for your next purpose-built device we can buy?\n \nJoseph 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.\n \n## Question 6\n \n### 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?\n \nJoseph 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.\n \n## Question 7\n \n### Can you run SGX servers running on Gateways or Stargates?\n \nArthur Mingard: SGX can be used on any machine with supporting hardware so Gateways and Stargates can run in a secure enclave.\n\n## Question 8\n \n### 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)?\n \nArthur 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 stride on this front in the past month.\n \nJoseph 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.\n \n## Question 9\n \n### 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?\n \nJoseph 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.\n\nFundamentally 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.\n\nSize 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\n \n## Question 10\n \n### Why has $DADI not been listed on any additional exchange?\n \nJoseph 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.\n \n## Question 11\n \n### Will the team provide an API for the edge explorer?\n \nArthur 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.\n \n## Question 12\n \n### How is the DADI token price volatility going to be dealt with?\n \nJoseph 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 to potential of the platform and the size of the market that it is helping to define.\n \n## Question 13\n \n### 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?\n \nJoseph 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.\n \n## Question 14\n \n### What's the difference between gateway onboarding and network backbone rentals mentioned in roadmap?\n \nArthur 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.\n \n## Question 15\n \n### 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?\n \nJoseph Denne: Conversion happens at the point of charge. And earnings are calculated at the point of processing.\n \n## Question 16\n \n### You mentioned that you will be rolling out a much bigger brand refresh. Is there a clearer ETA on that?\n \nJoseph 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.\n\n## Question 17\n \n### 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?\n \nJoseph 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.\n \n## Question 18\n \n### What specific instances of AWS EC2 and google GCP are the price comparisons based on?\n \nArthur Mingard: Varying, but in the same ballpark in terms of power.\n \n## Question 19\n \n### What about a webinar type format on one media source for the AMAs vs doing it over multiple sources?\n \nJoseph 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.\n \n## Question 20\n \n### What is the difference between DADI and Ankr?\n \nArthur 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.\n \n## Question 21\n \n### 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?\n \nJoseph 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.\n \n## Question 22\n \n### Can you elaborate on the current use of the DADI token in general? How is the token involved with current paying customers?\nJoseph 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.\n \n## Question 23\n \n### 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?\n \nJoseph 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.\n \n## Question 24:\n \n### Have you considered migrating Telegram and Discord into one community channel?\n \nJoseph Denne: Yes, we've considered it. They're very different channels and experiences though. What do you think?\n \n## Question 25\n \n### 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?\n \nArthur 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.\n \n## Question 26\n \n### Is the compute units in the edge explorer a standardized way of measuring capacity or is it something the DADI team made up?\n \nJoseph 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.\n \n## Question 27\n \n### 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?\n \nJoseph 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.\n \n## Question 28\n \n### 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? \n \nArthur 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.\n \n## Question 29\n \n### 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?\n \nJoseph 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.\n \n## Question 30\n \n### Will FN holders be able to add DADI tokens to the staking balance?\n \nJoseph 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!",
      "json_metadata": "{\"tags\":[\"edge\",\"dadi\",\"blockchain\",\"crypto\",\"decentralized\"],\"image\":[\"https://cdn.dadi.cloud/media/2019/06/09/og-ama-07-06.png?w=1600&q=70\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "959e2efd44481dd2ded769ce83f32f31a41a1536",
  "block": 33646947,
  "trx_in_block": 28,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-09T11:23:15",
  "op": [
    "vote",
    {
      "voter": "josephdenne",
      "author": "josephdenne",
      "permlink": "weekly-update-07th-june-2019",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "67a8281669f8957026c12ada6a1e877fea2bf739",
  "block": 33646944,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-09T11:23:06",
  "op": [
    "vote",
    {
      "voter": "josephdenne",
      "author": "josephdenne",
      "permlink": "edge-ssl",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "708a56799e712991f43e5c6117b82f83db1835ad",
  "block": 33646940,
  "trx_in_block": 27,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-09T11:22:54",
  "op": [
    "comment",
    {
      "parent_author": "josephdenne",
      "parent_permlink": "edge-ssl",
      "author": "cheetah",
      "permlink": "cheetah-re-josephdenneedge-ssl",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://dadi.cloud/en/knowledge/network/edge-ssl/",
      "json_metadata": ""
    }
  ]
}