{
  "trx_id": "62f4853d057c4f9b8ee7b73635274ca4fa62c9e2",
  "block": 34012040,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-22T04:10:39",
  "op": [
    "comment",
    {
      "parent_author": "ecaf",
      "parent_permlink": "ecaf-caseload-announcement",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-ecaf-20190622t041038000z",
      "title": "",
      "body": "Congratulations @ecaf! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@ecaf/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@ecaf) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=ecaf)_</sub>\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><tr><td><a href=\"https://steemit.com/steemtoolbar/@steemitboard/steemtoolbar-update-display-bug-fixed\"><img src=\"https://steemitimages.com/64x128/http://i.cubeupload.com/7CiQEO.png\"></a></td><td><a href=\"https://steemit.com/steemtoolbar/@steemitboard/steemtoolbar-update-display-bug-fixed\">SteemitBoard - Witness Update</a></td></tr><tr><td><a href=\"https://steemit.com/steem/@steemitboard/do-not-miss-the-coming-rocky-mountain-steem-meetup-and-get-a-new-community-badge\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmUphCGZFWgt6bJ1XTtunV7esnwy6bxnGqcLcHAV3NEqnQ/meetup-rocky-mountain.png\"></a></td><td><a href=\"https://steemit.com/steem/@steemitboard/do-not-miss-the-coming-rocky-mountain-steem-meetup-and-get-a-new-community-badge\">Do not miss the coming Rocky Mountain Steem Meetup and get a new community badge!</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": "7102316319ed4faaa8e432e3fc29415294e3e0ac",
  "block": 31090993,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-03-12T14:37:45",
  "op": [
    "transfer",
    {
      "from": "dlease",
      "to": "ecaf",
      "amount": "0.001 STEEM",
      "memo": "BuildTeam is proud to announce the release of DLease.io - our flagship P2P leasing marketplace app, aimed at assisting Steemians in leasing and delegating STEEM POWER for daily passive returns, with recent yields as high as 20% APR. DLease.io is a professional grade app , designed to replace the current MinnowBooster.net leasing market which has to date facilitated nearly 20 Million STEEM POWER in lease value to happy BuildTeam customers. View the new app at https://dlease.io/ or read the announcement post on https://steemit.com/@dlease."
    }
  ]
}

{
  "trx_id": "db1dc3a28c033e2fa015891164b902e324c9af61",
  "block": 31018842,
  "trx_in_block": 30,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-03-10T02:27:18",
  "op": [
    "vote",
    {
      "voter": "maxocoin",
      "author": "ecaf",
      "permlink": "ecaf-caseload-announcement",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "140f1e7add9def74c73a31cf6c6b5f179bb0626d",
  "block": 31010685,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-03-09T19:39:09",
  "op": [
    "vote",
    {
      "voter": "djjaron",
      "author": "ecaf",
      "permlink": "ecaf-s-fee-schedule",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "7d7984448c4ff10e0c96ed417e5620047ff50df4",
  "block": 30743663,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-02-28T12:59:42",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "ecaf",
      "author": "ecaf",
      "permlink": "ecaf-caseload-announcement",
      "title": "ECAF: Caseload announcement",
      "body": "The EOS Core Arbitration Forum’s (ECAF) caseload has grown to over 900 cases and new cases continue to stream in weekly. Unfortunately, the resolution of cases has slowed down to a crawl due to difficulties experienced in the EOS main-net Community. Dispute resolution on the EOS main-net is therefore not working as expected.\n\nIn particular, a vocal proportion of EOS main-net Block Producers (BPs) have publicly postured to reject all future emergency actions, and have generally indicated that they are not willing to enforce any future ECAF arbitral awards. This is to the point of breaking the EOS Constitution and has led to the current Constitutional deadlock between BPs and ECAF.\n\nECAF has been operating as a volunteer-run organisation with the expectation that it would fund itself through fees charged for its services once rulings were delivered. Being purely volunteer-run was never intended to be the long term mode of operation. Having no clear route to the enforcement of many of its rulings means that ECAF is being effectively defunded which, in turn, means that it is extremely difficult for ECAF to sustain operations at the level demanded by the claimants.\n\nEffective immediately ECAF will take the following steps to manage its caseload.\n## No new cases requiring Emergency Action\nBPs utilise a so-called blacklist to freeze accounts whose ownership is contested. Blacklisting requires that every single BP in the top 21 maintains a table of accounts that are not allowed to transact pending a further decision. Any mistakes in keeping this table up to date means that funds that are supposedly frozen are free to be siphoned off. This has, in fact, happened several times over the last 8 months. ECAF [spoke out against the practice of blacklisting](https://steemit.com/ecaf/@ecaf/the-eos-blacklist-is-broken-ecaf-calls-on-bps-to-change-how-they-freeze-accounts)  multiple times and requested BPs to move to a BFT compliant 15/21 nulling of the keys but this has been up until recently ignored. ECAF takes note that some [BPs are now proposing](https://medium.com/@eos42/proposed-solution-for-a-broken-blacklist-ce1c18bdf81c) to secure the current accounts on the blacklist in this manner and hope that common sense prevails and that this proposal is adopted.\n\nHowever, with more than one BP publicly stating that they will not enact further blacklists then ECAF has no choice but to _completely cease processing of emergency account freeze requests_.\n## No processing of Lost Key cases\nIn December 2018 ECAF [delivered a ruling](https://steemit.com/ecaf/@ecaf/lost-key-cases-and-scalability) ordering the return of a Lost Key account to its rightful owner. The ruling was not enacted and requests to the BPs to engage in dialogue to understand what issues they had with the ruling mostly went unanswered. Since that time several BPs have [proposed an automated solution](https://eosauthority.com/lostkey) to process Lost Key cases that largely mirrors the process that was followed in the original ruling.\n\nECAF is happy for the affected accounts and hopes that this initiative is successful. However, as a result, _ECAF notes that it is no longer tenable to process Lost Key cases and will cease to do so._\n\nAny person who has submitted fees for a Lost Key case and who seeks to withdraw their case from consideration may apply for a refund of the fees. Fees will generally be refunded less costs for any work done on the case to date.\n## Unassigned cases will be closed after 3 months\n\nCases are formally accepted by ECAF for Arbitration upon assignment of an Arbitrator and the collection of any relevant Arbitral fees and deposits. Where a case has not been accepted by the forum for a period of 3 months after filing then _that case will be automatically rejected for lack of an Arbitrator._ This will free the claimants to consider alternate paths to pursue their claims. Claimants will also have the option to resubmit the case if they so wish.\n\nAs cases will not have been accepted by ECAF and no fees collected then no refunds will be due.\n## Priority will be given to closing the cases on the current blacklist\n\nProcessing priority will be given to closing the cases on the current blacklist. Thereafter next priority will be given to cases that are already assigned.\n## Summary\n\nWhile it saddens ECAF and its Arbitrators to take the above steps we note that we see no other alternatives to managing the current cases in the face from well-funded opposition to ECAF’s operation.\n\nA set of answers to possible questions is included below. This will be updated over the next 5 days as additional frequently asked questions come up.\n\n# FAQs\n\n## Q. Will ECAF still accept new cases not in the above categories?\n\nYes. Claimants are however requested to note that routes that require BP enforcement may not be available.\n\n## Q. I would like to withdraw my case. Will I get a refund?\n\nPlease email a request for a refund in response to the email with your original case filing. Refund requests will be treated on a case by case basis. Where a refund request is approved it will be less any costs attributable to the case and for work done to date.",
      "json_metadata": "{\"tags\":[\"ecaf\",\"eos\"],\"links\":[\"https://steemit.com/ecaf/@ecaf/the-eos-blacklist-is-broken-ecaf-calls-on-bps-to-change-how-they-freeze-accounts\",\"https://medium.com/@eos42/proposed-solution-for-a-broken-blacklist-ce1c18bdf81c\",\"https://steemit.com/ecaf/@ecaf/lost-key-cases-and-scalability\",\"https://eosauthority.com/lostkey\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "9d168fe839d75d0b06864b9a601601eef1ab2e31",
  "block": 30738216,
  "trx_in_block": 29,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-02-28T08:26:57",
  "op": [
    "vote",
    {
      "voter": "sobad",
      "author": "ecaf",
      "permlink": "the-eos-blacklist-is-broken-ecaf-calls-on-bps-to-change-how-they-freeze-accounts",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "3b8d13833850c3364c0927bf317df3cbf0caebdb",
  "block": 30529661,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-02-21T02:31:36",
  "op": [
    "comment",
    {
      "parent_author": "ecaf",
      "parent_permlink": "warning-about-fake-ecaf-accounts-and-website",
      "author": "scottbonge",
      "permlink": "re-ecaf-warning-about-fake-ecaf-accounts-and-website-20190221t023136247z",
      "title": "",
      "body": "Is ECAF working or is it DOA?",
      "json_metadata": "{\"tags\":[\"ecaf\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

{
  "trx_id": "7b205e8cfb37ab9c4fd68bf4a09dfaf7f106b133",
  "block": 29784585,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-01-26T05:06:30",
  "op": [
    "comment",
    {
      "parent_author": "ecaf",
      "parent_permlink": "why-arbitration-makes-a-difference-to-the-eos-ecosystem",
      "author": "jimmyfotogallery",
      "permlink": "re-ecaf-why-arbitration-makes-a-difference-to-the-eos-ecosystem-20190126t050249520z",
      "title": "",
      "body": "tks",
      "json_metadata": "{\"tags\":[\"eos\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

{
  "trx_id": "aad7b74964a71b2341994a60b65f0640c3acce76",
  "block": 29557093,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-01-18T07:19:24",
  "op": [
    "comment",
    {
      "parent_author": "ecaf",
      "parent_permlink": "why-arbitration-makes-a-difference-to-the-eos-ecosystem",
      "author": "partiko",
      "permlink": "partiko-re-ecaf-why-arbitration-makes-a-difference-to-the-eos-ecosystem-20190118t071924453z",
      "title": "",
      "body": "[![](https://d1vof77qrk4l5q.cloudfront.net/statics/upsell-delegate-15-steem-power-2.png)](https://partiko-io.app.link/A27hLeUkgT)",
      "json_metadata": "{\"app\":\"partiko\"}"
    }
  ]
}

{
  "trx_id": "7655309aa1f47353b467b233ac7a744565b1ca95",
  "block": 29347214,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-01-11T00:15:36",
  "op": [
    "vote",
    {
      "voter": "dragonsquaw",
      "author": "ecaf",
      "permlink": "on-eos-lost-key-cases",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "e4552039f2db0ff6a9aea742251637b7435e6db2",
  "block": 29347211,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-01-11T00:15:27",
  "op": [
    "vote",
    {
      "voter": "dragonsquaw",
      "author": "ecaf",
      "permlink": "lost-key-cases-and-scalability",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "9f0e087aa86febe1b6dc0af92e11b760e7c97aec",
  "block": 29319375,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-01-10T01:03:09",
  "op": [
    "vote",
    {
      "voter": "dragonsquaw",
      "author": "ecaf",
      "permlink": "why-arbitration-makes-a-difference-to-the-eos-ecosystem",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "e77da4d32bd9cc5727f23d72b8c4862ae8696371",
  "block": 29311383,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-01-09T18:23:24",
  "op": [
    "vote",
    {
      "voter": "fyrstikken",
      "author": "ecaf",
      "permlink": "why-arbitration-makes-a-difference-to-the-eos-ecosystem",
      "weight": 100
    }
  ]
}

{
  "trx_id": "466e0e1c26870ddde7b6e365311bdcfffbb4a441",
  "block": 29311381,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-01-09T18:23:18",
  "op": [
    "vote",
    {
      "voter": "devsup",
      "author": "ecaf",
      "permlink": "why-arbitration-makes-a-difference-to-the-eos-ecosystem",
      "weight": 69
    }
  ]
}

{
  "trx_id": "5d5a3c6dec5d3d9edd7bc7b86f0884a435473f1b",
  "block": 29311082,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-01-09T18:08:21",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eos",
      "author": "ecaf",
      "permlink": "why-arbitration-makes-a-difference-to-the-eos-ecosystem",
      "title": "Why Arbitration makes a difference to the EOS ecosystem",
      "body": "# Introduction\nWith the events that came with the long-awaited first ruling on EOS lost key cases we have a perfect example for how arbitration makes a big difference and has a much wider effect beyond the ruling for a single case. \n\nA problem with individuals losing their EOS private keys occurred that the code or system could not resolve, an impartial dispute resolver stepped in, objectively heard the pros and cons, evaluated the potential solutions and then arrived at a decision. This not only resolved this single dispute but a multitude of disputes by just one precedent arbitration decision. Opening the arena for new solutions to be proposed.\n# What are the events that led up to this?\nThe [EOS Core Arbitration Forum (ECAF)](https://eoscorearbitration.io/) issued a [ruling on the 14th of December to resolve a lost key dispute](https://eoscorearbitration.io/wp-content/uploads/2018/12/ECAF-Ruling-Case-0027-2018-12-14-AR-002.pdf). \n\nTo recap the history that led up to that ruling. The [EOS.IO whitepaper](https://github.com/EOSIO/Documentation/blob/master/TechnicalWhitePaper.md) indicated that the EOS.IO software was a new type of blockchain which would contain a variety of features that would make EOS.IO much more human-usable than previous blockchains. Features such as human-readable names, a better account permission structure and a possibility for lost key recovery. Whilst much of the promise of the whitepaper was fulfilled, when the chain launched it did not include any sort of lost key recovery services.\n\nWhat transpired after launch was that there were quite a large number of people (some estimates put it at thousands) who had lost their keys. We can speculate as to why that is. Maybe this was a consequence of the long duration of the token sale event (which spanned a year)? Maybe people were less careful as they understood that they could recover their lost keys? Or maybe, this is just a defining feature of all blockchains that is just not recognised. (Apocryphally some statistics say that around 30% of the largest cryptocurrency - Bitcoin - is lost value due to people losing their keys. Hence the sensational stories of hard drives worth millions stuck in rubbish dumps the world over.) One way or the other, there were a lot of people who lost their EOS private keys.\n\nThe launch of the EOS Mainnet took place 6 months ago. During that 6 months, the lost key holders languished in patience hoping that somebody would do something. But nobody did anything for 6 months, nobody took responsibility, nobody claimed to be able to do something, nobody set up a tool ....\n\nAnd seriously nobody, besides of maybe [block.one](https://block.one/) could. But there are good and understandable reasons as to why block.one could and would not do anything. Doing anything with accounts on the EOS Mainnet may make them liable for decisions about which accounts got given EOS on the Mainnet in the first place. Which is a control that they clearly wanted to give up. Again for good reasons.\n\nOf the other actors in the ecosystem maybe 15/21 BPs could do something. But one has to ask whether those BPs would want to be able to take deep decisions for every case? BPs in the top 21 turn over regularly depending on voter’s choices, would new BPs in the top 21 want to be liable for decisions that others took before them? One mistake possibly could mean the reputational end for each of them.\n\nA referendum could, but it's not completely there yet. And it's also quite hard to come to a conclusion for a referendum and it clearly wouldn't do for single accounts.\n# ECAF’s place in all this\nAs there was nobody else to turn to, the people with lost keys filed claims with ECAF. ECAF had no option but to take these cases eventually as there clearly was an issue to resolve.\n\nIt took ECAF some time to make a ruling as a lot of buildup had to be done. During that time there was a lot of discussion in the EOS Community about lost keys and a lot of ideas were thrown around. Many good ones, but all requiring some sort of opt-in BEFORE the keys were lost. Which of course did nothing to comfort those who had already lost their keys!\n\nECAF worked silently to set up a working process with as tight as possible checks and giving a potential other owner chances to come up with their claim.\n\nEventually, ECAF ruled. It caused quite a stir. And ... suddenly people knew how to resolve the issue! Now BPs are proposing lost key automated solutions on the back of that and working hard to get a promising solution going ASAP. Something they had laughed about just days before, when ECAF spoke about the possibility of (partial-)automatisation of these cases.\n\nWell, this is exactly what arbitration is about and what was \"promised\" this would be about - settling an issue for everybody so that people know how to do it right next time.\n# That's why and how arbitration makes a difference.\nDispute resolution steps in when the way forward is not clear and is more than simply resolving the dispute. \n\nIn fact, dispute resolution has a particularly special and desirable side effect. It not only resolves a single dispute but also resolves a multitude of disputes by just one precedent decision. A clear and balanced way is found through issues that have not been addressed and often effectively could not be addressed before giving others a path forward.",
      "json_metadata": "{\"tags\":[\"eos\",\"ecaf\",\"dispute\",\"resolution\"],\"links\":[\"https://eoscorearbitration.io/\",\"https://eoscorearbitration.io/wp-content/uploads/2018/12/ECAF-Ruling-Case-0027-2018-12-14-AR-002.pdf\",\"https://github.com/EOSIO/Documentation/blob/master/TechnicalWhitePaper.md\",\"https://block.one/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 28882092,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 5,
  "timestamp": "2018-12-25T20:20:54",
  "op": [
    "author_reward",
    {
      "author": "ecaf",
      "permlink": "warning-about-fake-ecaf-accounts-and-website",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.024 STEEM",
      "vesting_payout": "48.257947 VESTS"
    }
  ]
}

{
  "trx_id": "fc3d39f561f01765b57dd102480af24a26e937b8",
  "block": 28768113,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-21T21:19:27",
  "op": [
    "vote",
    {
      "voter": "acknowledgement",
      "author": "ecaf",
      "permlink": "ecaf-community-fund",
      "weight": 1000
    }
  ]
}

{
  "trx_id": "f9b0fd99cc95dc124130323259085da5b2c86e80",
  "block": 28767918,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-21T21:09:42",
  "op": [
    "vote",
    {
      "voter": "thelionroar",
      "author": "ecaf",
      "permlink": "ecaf-community-fund",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "d55098a470ef7e43f2c0672f9d3650c469e41d22",
  "block": 28766762,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-21T20:11:42",
  "op": [
    "vote",
    {
      "voter": "council",
      "author": "ecaf",
      "permlink": "ecaf-community-fund",
      "weight": 1000
    }
  ]
}

{
  "trx_id": "32245bf1bd1c4990141620d2e27b5cd362c1d78a",
  "block": 28766564,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-21T20:01:48",
  "op": [
    "vote",
    {
      "voter": "yehey",
      "author": "ecaf",
      "permlink": "ecaf-community-fund",
      "weight": 1000
    }
  ]
}

{
  "trx_id": "d9b2932fce44b49d7b0705d786882b7693260df8",
  "block": 28766186,
  "trx_in_block": 36,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-21T19:42:54",
  "op": [
    "vote",
    {
      "voter": "luna777",
      "author": "ecaf",
      "permlink": "ecaf-community-fund",
      "weight": 248
    }
  ]
}

{
  "trx_id": "53dfd1fc6632a0eae45d08f7c0fdb3477430c43f",
  "block": 28766164,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-21T19:41:48",
  "op": [
    "vote",
    {
      "voter": "fyrstikken",
      "author": "ecaf",
      "permlink": "ecaf-community-fund",
      "weight": 100
    }
  ]
}

{
  "trx_id": "cfc24a332723acf3288a128f89f954428326195a",
  "block": 28766082,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-21T19:37:42",
  "op": [
    "vote",
    {
      "voter": "votes4minnows",
      "author": "ecaf",
      "permlink": "ecaf-community-fund",
      "weight": 300
    }
  ]
}

{
  "trx_id": "f33c799d4f1aea5c98b4bfaad4d63e5fb0c4b198",
  "block": 28765864,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-21T19:26:48",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "ecaf",
      "author": "ecaf",
      "permlink": "ecaf-community-fund",
      "title": "ECAF Community fund",
      "body": "Dear members of the EOS Community,\n\nECAF is delighted to announce the formation of the ECAF Community Fund. The fund will serve a variety of purposes, many of which are yet to be realised but all which the community could benefit from in some way.\n\n### Uses of the Community Fund:\n\nWe envisage uses of the community fund to be purely at the discretion of the Arbitrator on a case by case basis. However, potential use cases of the fund are as follows.\n\n1)  A type of case has been ruled on several times and consistencies in approach have been identified as a result. Semi-automation has become possible, the development of which could be funded by the community fund. This would ensure swifter dispute resolution for such cases in the long term and bring the costs down for parties involved. \n\n  2) A case is filed which is clearly in the community interest. If the claimant were to win such a case, then it would only be right that they are reimbursed their accrued case costs even if the respondent isn’t available/does not pay the costs. The availability of the fund gives the Arbitrator the flexibility to partially or wholly reimburse either party in such cases. It could even be used to supplement the ongoing case costs before a ruling has taken place. As a community we do not want financial constraints to stop community interest cases proceeding where possible and meaningful.\n\n3)   A ruling results in the movement of tokens.  An appeal is launched against this ruling by a new claimant based on new evidence that was not available at the time the case was handled, and that ruling has been accepted. The new claimant wins the case and is able to prove that their property changed hands incorrectly. The other party has since disappeared with the property and is unable to be brought to account. Reimbursing the appealing Claimant in this instance may be another potential use case for the fund.\n\nThese are only examples and we do envisage many other use cases of the fund coming to light in the future. It could also be used to fund other community initiatives.\n\n### How it is formed:\n\nLost key case rulings are those in which community members who have lost the private keys to their accounts have had access returned to them. ECAF has decided to deal with them on a flat rate fee basis. Some of the revenue from these rulings could be best used in serving the community interest. As such, ECAF will be depositing  2.5% of all lost key rulings total claim value in the ECAF Community account. This will be taken from the current 15% fixed fee so it will not be an additional burden to the parties involved.\n\nWhy start this fund using the revenue from lost key cases? While the claimants in these case have a right to get the access to their property returned according to the constitution and our governing law of the maxims of equity, they are still responsible for safekeeping their keys and by failing to do so are responsible for this category of cases. As such they take time and resources from other cases which are also in the interest of the community to be served. So a small charge seems to be the best starting point to create this kind of fund in the community’s interest, independently from the worker proposal scheme.\n\nIn the future Arbitrators handling other cases could also decide to direct some of the fees or possibly some fines into the direction of the fund.\n\n**Please note: It is our intention, where possible, to continue this initiative, adding to the community fund by other means beyond revenue received from Lost Key Cases.**",
      "json_metadata": "{\"tags\":[\"ecaf\",\"eos\",\"community\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 28761793,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 8,
  "timestamp": "2018-12-21T16:03:12",
  "op": [
    "author_reward",
    {
      "author": "ecaf",
      "permlink": "lost-key-cases-and-scalability",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.106 STEEM",
      "vesting_payout": "217.211070 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 28761633,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 5,
  "timestamp": "2018-12-21T15:55:12",
  "op": [
    "author_reward",
    {
      "author": "ecaf",
      "permlink": "on-eos-lost-key-cases",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.031 STEEM",
      "vesting_payout": "64.358855 VESTS"
    }
  ]
}

{
  "trx_id": "78e61477f7b1a9ade62e552915f1a20669e46623",
  "block": 28703924,
  "trx_in_block": 38,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-19T15:48:00",
  "op": [
    "vote",
    {
      "voter": "catchfire",
      "author": "ecaf",
      "permlink": "warning-about-fake-ecaf-accounts-and-website",
      "weight": 2200
    }
  ]
}

{
  "trx_id": "3c5fe32ffd7be22a477512aab6806dd8e3552494",
  "block": 28696582,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-19T09:40:51",
  "op": [
    "vote",
    {
      "voter": "cryptoslicex",
      "author": "ecaf",
      "permlink": "warning-about-fake-ecaf-accounts-and-website",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "b3ee218b8bf5528b138c7859381c51367c4c51fc",
  "block": 28680884,
  "trx_in_block": 46,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-18T20:34:36",
  "op": [
    "vote",
    {
      "voter": "raise-me-up",
      "author": "ecaf",
      "permlink": "warning-about-fake-ecaf-accounts-and-website",
      "weight": 1
    }
  ]
}

{
  "trx_id": "f2634ea59b6926be1e23f73fc023044fa821f365",
  "block": 28680814,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-18T20:31:06",
  "op": [
    "vote",
    {
      "voter": "ezravandi",
      "author": "ecaf",
      "permlink": "warning-about-fake-ecaf-accounts-and-website",
      "weight": 229
    }
  ]
}

{
  "trx_id": "696dd84b03a4dcb14c0f134e0d1d78456bd754fc",
  "block": 28680610,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-18T20:20:54",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "ecaf",
      "author": "ecaf",
      "permlink": "warning-about-fake-ecaf-accounts-and-website",
      "title": "Warning about fake ECAF accounts and website",
      "body": "An EOS account purporting to belonging to the EOS Core Arbitration Forum (ECAF) has been issuing fake notices of arbitration to EOS account holders and directing users to a fake website.\n\nThe account `ecafofficiel` was created on 18 December 2018 and does not belong to ECAF. \n\nEOS token holders are advised to disregard any notices from this account and to avoid clicking on any of the links due to the risk of malware being present on the site.\n\nECAF notices will continue to come from the following EOS account:\n\n`ecafofficial`\n\nECAF's website is located at https://eoscorearbitration.io/\n\nAdditionally, please keep your private keys safe. ECAF and its representatives will never ask you for any of your private keys (regardless of the blockchain).",
      "json_metadata": "{\"tags\":[\"ecaf\",\"eos\",\"fake\",\"site\"],\"links\":[\"https://eoscorearbitration.io/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "bbd4bfb0c7b2b738b5a64546dac10fd3e6b22554",
  "block": 28585715,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-15T13:12:57",
  "op": [
    "comment",
    {
      "parent_author": "ecaf",
      "parent_permlink": "lost-key-cases-and-scalability",
      "author": "samstickkz",
      "permlink": "re-ecaf-lost-key-cases-and-scalability-20181215t131252056z",
      "title": "",
      "body": "I want to volunteer",
      "json_metadata": "{\"tags\":[\"ecaf\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

{
  "trx_id": "6f4c612c0e323942c25637b02ba52eeba115ebf5",
  "block": 28568621,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T22:57:42",
  "op": [
    "vote",
    {
      "voter": "sensation",
      "author": "ecaf",
      "permlink": "on-eos-lost-key-cases",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "7d5be99e3bc975b5a71f93dfd8b3617a435109bb",
  "block": 28563883,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T19:00:42",
  "op": [
    "vote",
    {
      "voter": "saunter",
      "author": "ecaf",
      "permlink": "lost-key-cases-and-scalability",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "3f59347efee00739d75787a840079843cb3b0b85",
  "block": 28563877,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T19:00:24",
  "op": [
    "vote",
    {
      "voter": "saunter",
      "author": "ecaf",
      "permlink": "on-eos-lost-key-cases",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "279012655c093a6718ec16e63a68d76002bb0307",
  "block": 28562420,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T17:47:33",
  "op": [
    "vote",
    {
      "voter": "themonetaryfew",
      "author": "ecaf",
      "permlink": "lost-key-cases-and-scalability",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "1df4a06541f3f5d9ca678bca07528c208e300cca",
  "block": 28560897,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:31:24",
  "op": [
    "vote",
    {
      "voter": "magpielover",
      "author": "ecaf",
      "permlink": "on-eos-lost-key-cases",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "5fc51c40e64c4593f187cd74ccc63e71160e7a7b",
  "block": 28560580,
  "trx_in_block": 40,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:15:33",
  "op": [
    "vote",
    {
      "voter": "phatima",
      "author": "ecaf",
      "permlink": "lost-key-cases-and-scalability",
      "weight": 100
    }
  ]
}

{
  "trx_id": "dfc9a7cb03c44e429a73b0d2194fa5e819450f04",
  "block": 28560548,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:13:57",
  "op": [
    "vote",
    {
      "voter": "steem.create",
      "author": "ecaf",
      "permlink": "lost-key-cases-and-scalability",
      "weight": 200
    }
  ]
}

{
  "trx_id": "a7fe5bc445c07c1783ea238b9cfd63d5e4fc6cf1",
  "block": 28560511,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:12:06",
  "op": [
    "vote",
    {
      "voter": "bukiland",
      "author": "ecaf",
      "permlink": "lost-key-cases-and-scalability",
      "weight": 80
    }
  ]
}

{
  "trx_id": "b52fb6967c0c579d9105de0faaa366aca403ef1a",
  "block": 28560499,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:11:30",
  "op": [
    "vote",
    {
      "voter": "curation.trail",
      "author": "ecaf",
      "permlink": "lost-key-cases-and-scalability",
      "weight": 210
    }
  ]
}

{
  "trx_id": "60d76fd2617949760c3a0ab754e7934a16e517a9",
  "block": 28560485,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:10:48",
  "op": [
    "vote",
    {
      "voter": "hdu",
      "author": "ecaf",
      "permlink": "lost-key-cases-and-scalability",
      "weight": 150
    }
  ]
}

{
  "trx_id": "fdd2648ecd5360c563d95fae62ad3dd55fa10b86",
  "block": 28560385,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:05:48",
  "op": [
    "vote",
    {
      "voter": "steem.create",
      "author": "ecaf",
      "permlink": "on-eos-lost-key-cases",
      "weight": 200
    }
  ]
}

{
  "trx_id": "e9d6eb4fffaf8e2f418eb640f26e09cefe0f8ae6",
  "block": 28560361,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:04:36",
  "op": [
    "vote",
    {
      "voter": "phatima",
      "author": "ecaf",
      "permlink": "on-eos-lost-key-cases",
      "weight": 100
    }
  ]
}

{
  "trx_id": "1c399092ca72456218276ab26c06a9ab107cc6b7",
  "block": 28560333,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:03:12",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "ecaf",
      "author": "ecaf",
      "permlink": "lost-key-cases-and-scalability",
      "title": "Lost Key Cases and Scalability",
      "body": "ECAF are delighted to inform the EOS Community that our first Lost Key case has reached [its conclusion](https://eoscorearbitration.io/wp-content/uploads/2018/12/ECAF-Ruling-Case-0027-2018-12-14-AR-002.pdf) with a ruling returning the EOS genesis account in question to the rightful owner.\n\n## What this case means for the community\n\nWe will now be accepting claims for lost key cases relating to EOS genesis accounts provided the following criteria are met:\n* The Claimant must be able to show ownership of the ERC-20 EOS account linked to the EOS account for which the keys have been lost. They can do this by signing a transaction with a memo specified by ECAF.\n* The EOS account in question must be a genesis account with no transactions showing on the block record since the launch of the EOS main net.\n* The Claimant must be prepared to provide a form of official government issued photo ID and sign a waiver accepting liability for losses incurred as a result of fraudulent claims.\n* The Claimant must pay total costs of 15% of the EOS value of the lost key account up front before their claim is processed.\n\n## Scalability\n\nECAF’s ability to handle our caseload by increasing our throughput is one result of this ruling. From now on cases where the situation for the claimant is identical or very similar can be handled much faster. The result is that existing claims of this nature where the claimant has paid the fees should be cleared within the coming months.\nThis represents the beginning of our broader plans to scale our operations.\n\nOther ways in which we intend to improve our efficiency:\n* The hiring of additional staff such as Case Managers to aid our internal workings and the rate at which we can respond to community correspondence regarding claims.\n* The transition from a volunteer workforce to one where we envisage having the budget in place to pay. This will enable our current staff to commit more time to ECAF.\n* The reallocation of case fees to enable us to have more disposable income available with which to grow the organization in general.\n* The possibility of introducing semi-automation for lost key cases to further increase throughput enabling us to deal more effectively with greater volumes of lost key cases being filed. In the future we intend to always employ semi-automation, where possible, to increase our efficiency across multiple case types. However, with regards to Lost Genesis Keys we intend to be putting the wheels in motion for this as soon as possible. Once we have finalised our workflow - which in all reality will probably be after a few more rulings - we intend to put development of the automated part out to tender to the EOS community.\n\n-- Ben Gates\nInterim Administrator",
      "json_metadata": "{\"tags\":[\"ecaf\",\"eos\",\"lost\",\"keys\",\"scalability\"],\"links\":[\"https://eoscorearbitration.io/wp-content/uploads/2018/12/ECAF-Ruling-Case-0027-2018-12-14-AR-002.pdf\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "60a57078d3ad18a2e0f06c1ae8fb6962a89e6311",
  "block": 28560325,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:02:48",
  "op": [
    "vote",
    {
      "voter": "jadabug",
      "author": "ecaf",
      "permlink": "on-eos-lost-key-cases",
      "weight": 70
    }
  ]
}

{
  "trx_id": "99b09a30827102f1bf04fda8d360c956e9137bdb",
  "block": 28560282,
  "trx_in_block": 45,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T16:00:39",
  "op": [
    "vote",
    {
      "voter": "anmol3886",
      "author": "ecaf",
      "permlink": "on-eos-lost-key-cases",
      "weight": 500
    }
  ]
}

{
  "trx_id": "e165afeb681d3a1ade8cadf08cb5288ce6b4abba",
  "block": 28560173,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-14T15:55:12",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "ecaf",
      "author": "ecaf",
      "permlink": "on-eos-lost-key-cases",
      "title": "On EOS lost key cases",
      "body": "## Introduction\n\nThe EOSIO whitepaper promised that the EOSIO software would include some form of lost key recovery, however as at the time of writing this does not exist in the software. \n\nThere are a lot of proposals being made for such key recovery services that include solutions where people “opt-in\" to some kind of private key custodian, insurance solution or provide additional proofs (e.g. biometric) of their identity and ownership. Ideally, there would exist a multitude of such services so that users have a choice of whom to trust with their recovery credentials. Unfortunately, though, these solutions do not currently exist and even if they did, they typically require users to register in advance to offer any protection. These are not services that ECAF can neither do nor is interested to do; ECAF’s focus is to provide dispute resolution. Therefore ECAF encourages developers and entrepreneurs to build those key recovery systems and to deploy them.\n\nWhat then for those who lost their keys prior to the existence of these services? For example, there are a vast number of people who lost the keys to their genesis EOS accounts after registration but before the EOS network launched. How would such users regain access to their accounts?\n## Should ECAF examine lost key cases?\n\nWe should preface the rest of this section with a disclaimer. ECAF does not believe that it should be the preferred entity to resolve lost key cases. If there existed lost key recovery options, like those mentioned in the earlier section, then that would leave ECAF as the exceptional path to be used when 1) all other avenues are exhausted and/or 2) disputes arise with the use of alternate key recovery methods.\n\nIn the current Constitution ECAF functions as a form of \"catch-all\" (or catch-a-lot) as long as there are no specific solutions to which people can and do opt into. At present, without the existence of key recovery solutions, to which claimants have already opted in, there is no other recourse for the claimant. These claimants only recourse is to file a claim with ECAF. But is this a valid dispute? It is instructive to view the purported owner of the lost keys as one party asking the Community, as another party, to accept their rights to the property. Lost key cases are therefore still “peer to peer” dispute resolution and within the jurisdiction of ECAF. \n\nECAF will, therefore, continue to examine lost key cases with the expectation that the number of these cases reduces over time as those affected genesis accounts have their cases resolved and as the Community builds alternative solutions.\n## Are lost key cases simple?\n\nGiven that ECAF will examine lost key cases, what is the process for doing so?\n\nWhile lost key recovery may sound like a problem that people are used to getting resolved easily in other contexts (e.g. with their email service password) it's actually a delicate decision. After all here is somebody who asks to gain control to an account. Somebody who cannot provide the major credential (i.e. the private keys) for the ownership.\nWhile that party claims to have lost the key, it could also be somebody who tries to steal the account of somebody else. And arbitration is always expecting a second party, who until the case is decided has to get the same fair chance to prove that they are right and the claim is wrong. So some waiting time to let another party come forward is reasonable. And would likely be so even for a lot of other recovery approaches.\n\nAnd then the evidence to prove their ownership of the account may not be easily provable by solely on-chain means. \n\nThese last complications are ones that other recovery systems possibly don't have. Others would possibly start with the expectation that their paying customers are actually the owners of the account. And they likely will design their solutions based on that starting point.\n\nSo the Arbitrator needs to review the case and evaluate a variety of factors for example:\nis it an ERC-20 based account, so can ownership be proven via ERC-20? Was there some activity in the account, when last? If yes, were there transactions? Can the claimant provide some information around those transactions? Payment slips or whatever? Can some transaction partner confirm this? Is the story that the claimant provided fitting or does it sound incomplete? How did the claimant claim to have stored the keys? Are there other persons/systems where the claimant has stored their keys? Can the claimant show ownership to another account, maybe on another chain that is linked to the account via some or multiple transactions?\n## How can this process be scaled?\n\nFirst, we need some rulings to set out how to resolve a category of cases as such. Those rulings will include some criteria for why, how and when to identify cases that fall into the same category as ruled.\n\nSecondly, once a category is identified, automation of the handling of cases that fall into that category can be performed. This may include the collection of evidence, the sending out of notices etc. Any cases that have discrepancies that don’t match the category will need to be treated differently.\n\nFinally, if we have a public, transparent set of criteria for how to be granted a new key to an account, then it is possible that people will provide false data that matches those criteria. We then need to be very careful that the material is genuine. And this is the point where we likely will not get away with full automation. It is likely there will need to be a final check of the gathered material before a ruling is made.\n\nHowever, those checks will typically not require a full arbitration process. Most of the heavy work can go through automation and so it should be faster and cheaper to do than manually conducting the process.\n\nTo execute the rulings these will need to be passed to Block Producers pushing the bottleneck from Arbitration to the BPs. We welcome discussion on how best to streamline this process. For example batching of rulings, on chain data formats that will ease the transfer of information etc.\n## Conclusion\n\nWhilst lost keys account resolution is not an activity that ECAF thinks it should be doing in the long term, in the short, to medium term, there is no other recourse for claimants (and for claimants who do not have access to their accounts, no recourse will ever be possible as they cannot opt-in to anything). ECAF will, therefore, hear lost key cases. We call on the EOS Community to build and deploy viable account recovery alternatives to allow token holders to “opt-in” to a service. \n\nNow that the first ruling for a lost key case has been delivered, the throughput for similar cases should be greatly increased. In keeping with its goals to pursue automation once manual rulings are done, ECAF will come out with criteria that will enable increased automation of lost key cases that meet certain attributes. This will give a roadmap for those currently lodged cases that meet the criteria to be swiftly resolved.",
      "json_metadata": "{\"tags\":[\"ecaf\",\"eos\",\"lost\",\"keys\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 28301407,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 38,
  "timestamp": "2018-12-05T16:07:57",
  "op": [
    "author_reward",
    {
      "author": "ecaf",
      "permlink": "ecaf-change-of-leadership-announcement",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.064 STEEM",
      "vesting_payout": "130.845094 VESTS"
    }
  ]
}

{
  "trx_id": "19a87514ea90b7d661fae9d39cedf3f4f4d1116d",
  "block": 28176417,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-12-01T07:56:12",
  "op": [
    "comment",
    {
      "parent_author": "ecaf",
      "parent_permlink": "ecaf-change-of-leadership-announcement",
      "author": "jimmyfotogallery",
      "permlink": "re-ecaf-ecaf-change-of-leadership-announcement-20181201t075255673z",
      "title": "",
      "body": "good to know that. good job ECAF",
      "json_metadata": "{\"tags\":[\"ecaf\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

{
  "trx_id": "f90eacb4f6f8169181fcda8aeaf72d52cd8652e5",
  "block": 28107505,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-28T22:29:21",
  "op": [
    "vote",
    {
      "voter": "indykpol",
      "author": "ecaf",
      "permlink": "ecaf-change-of-leadership-announcement",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "dbe455f1a7b670e4b446be780789ab136174f460",
  "block": 28100308,
  "trx_in_block": 69,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-28T16:29:27",
  "op": [
    "vote",
    {
      "voter": "chitty",
      "author": "ecaf",
      "permlink": "ecaf-change-of-leadership-announcement",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "29be1c0654bdb005d73ba2d574f594fb36d8dd67",
  "block": 28100200,
  "trx_in_block": 51,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-28T16:24:03",
  "op": [
    "vote",
    {
      "voter": "phatima",
      "author": "ecaf",
      "permlink": "ecaf-change-of-leadership-announcement",
      "weight": 1250
    }
  ]
}

{
  "trx_id": "d955032062defce08537fd85fc772f97132bf94d",
  "block": 28100157,
  "trx_in_block": 39,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-28T16:21:51",
  "op": [
    "vote",
    {
      "voter": "bukiland",
      "author": "ecaf",
      "permlink": "ecaf-change-of-leadership-announcement",
      "weight": 122
    }
  ]
}

{
  "trx_id": "2add6df01fcf8bb77a15033c943be8f2a6408c5e",
  "block": 28100134,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-28T16:20:42",
  "op": [
    "vote",
    {
      "voter": "jadabug",
      "author": "ecaf",
      "permlink": "ecaf-change-of-leadership-announcement",
      "weight": 240
    }
  ]
}

{
  "trx_id": "b1e7934b15d7b9d292e20cb7dc9dffb37747ae49",
  "block": 28099988,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-28T16:13:24",
  "op": [
    "vote",
    {
      "voter": "raise-me-up",
      "author": "ecaf",
      "permlink": "ecaf-change-of-leadership-announcement",
      "weight": 1
    }
  ]
}

{
  "trx_id": "58cf0ceaf9579d4a3cd13f06c2e17fd2d25fb2f2",
  "block": 28099959,
  "trx_in_block": 54,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-28T16:11:57",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "ecaf",
      "author": "ecaf",
      "permlink": "ecaf-change-of-leadership-announcement",
      "title": "ECAF change of leadership announcement",
      "body": "@@ -1308,8 +1308,109 @@\n w role.%E2%80%9D\n+%0A%0AFor further information please visit the EOS Dispute Resolution Telegram group: https://t.me/eosarb\n",
      "json_metadata": "{\"tags\":[\"ecaf\",\"eos\"],\"links\":[\"https://eoscorearbitration.io/\",\"https://t.me/eosarb\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "6ef908357d05c0d52466158b692896e2bd07f490",
  "block": 28099879,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-28T16:07:57",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "ecaf",
      "author": "ecaf",
      "permlink": "ecaf-change-of-leadership-announcement",
      "title": "ECAF change of leadership announcement",
      "body": "Effective 3rd December 2018, the [EOS Core Arbitration Forum (ECAF)](https://eoscorearbitration.io/) is pleased to announce that Ben Gates will assume the role of Interim Administrator. Ben holds an LL.B degree in Law and has completed the Legal Practice Course. He has worked in a variety of business and executive roles and is currently an ECAF Interim Arbitrator.\n\nMoti Tabulo will step down as Interim Administrator of the ECAF. This is in keeping with his prior commitment to helm ECAF for a period of 6 months (from the beginning of June).\n\n“I’m very excited for ECAF’s future”, says Ben. “We are a few steps into building the first blockchain dispute resolution function for the world's first governed blockchain. I am excited to further ECAF’s efforts to better serve the EOS community.”\n\nMoti will transition to a part-time role within ECAF. He will continue to support Ben and the ECAF team whilst contributing to case management, transparency and support infrastructure.\n\n“Working on ECAF since launch has been an epic journey”, says Moti. “Going from an unfunded, bootstrapped body to saving over 3 million EOS (and counting!) and working with an engaged team who have been willing to volunteer their efforts to date has been very fulfilling. I look forward to helping Ben transition into his new role.”",
      "json_metadata": "{\"tags\":[\"ecaf\",\"eos\"],\"links\":[\"https://eoscorearbitration.io/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "5c14a92c3d09e20d045b96c745b25ccdd72fc63c",
  "block": 27738117,
  "trx_in_block": 32,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-16T02:31:18",
  "op": [
    "vote",
    {
      "voter": "atticusprime",
      "author": "ecaf",
      "permlink": "the-eos-blacklist-is-broken-ecaf-calls-on-bps-to-change-how-they-freeze-accounts",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 27726982,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 8,
  "timestamp": "2018-11-15T17:13:39",
  "op": [
    "author_reward",
    {
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "sbd_payout": "0.125 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "348.635170 VESTS"
    }
  ]
}

{
  "trx_id": "916a058c5ab17280abd8f2e267c2d8d3f65ef00a",
  "block": 27657287,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-13T07:06:03",
  "op": [
    "vote",
    {
      "voter": "themonetaryfew",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "ff2244bd895d8dbeec6fd9ee2174d38eb243a4b1",
  "block": 27554394,
  "trx_in_block": 57,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-09T17:18:27",
  "op": [
    "comment",
    {
      "parent_author": "ecaf",
      "parent_permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "author": "anamnesia",
      "permlink": "re-ecaf-ecaf-makes-history-today-with-its-first-ruling-20181109t171828507z",
      "title": "",
      "body": "This is really good news. Very happy to see things moving along!",
      "json_metadata": "{\"tags\":[\"ecaf\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

{
  "trx_id": "b6c0837295504a5a66ce5bfea37664d7664ddb4b",
  "block": 27544292,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-09T08:53:06",
  "op": [
    "vote",
    {
      "voter": "rob.roche",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "54a75bf56ef3e0186514e3309911cd5d3ca7b287",
  "block": 27543632,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-09T08:20:06",
  "op": [
    "vote",
    {
      "voter": "trepoleth",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "43ac0e7eac3b5837e55c40c401bafd6b0269bd45",
  "block": 27543588,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-09T08:17:54",
  "op": [
    "vote",
    {
      "voter": "steemitlsh",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "713c87286cfbf8cec66266439a4d98451ce77ab8",
  "block": 27543571,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-09T08:17:03",
  "op": [
    "vote",
    {
      "voter": "harooga",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "7fc2e45fe8b6d15a61e13447828adf03e40d64aa",
  "block": 27538387,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-09T03:57:30",
  "op": [
    "vote",
    {
      "voter": "h3llf15h",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "78ef6cca605738199f16da9f1ce471f2d3a28c0f",
  "block": 27534007,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-09T00:18:27",
  "op": [
    "vote",
    {
      "voter": "vincent9432",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "faf4b606107ffff6d885fa5464639a9274ac786e",
  "block": 27531756,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-08T22:25:48",
  "op": [
    "vote",
    {
      "voter": "johnsmith",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "ff46c293d66c479f1c1f34acd9fe8a887904e4d0",
  "block": 27530564,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-08T21:26:12",
  "op": [
    "comment",
    {
      "parent_author": "ecaf",
      "parent_permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "author": "mjhomb",
      "permlink": "re-ecaf-ecaf-makes-history-today-with-its-first-ruling-20181108t212609547z",
      "title": "",
      "body": "While I am in the dapp layer camp wrt arbitration well done making history! The experience you guys are gaining will be valuable to everyone wanting to improve blockchain governance. Great work",
      "json_metadata": "{\"tags\":[\"ecaf\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

{
  "trx_id": "03a8601d8239deb586760fb2ddea087c5b01d907",
  "block": 27530506,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-08T21:23:18",
  "op": [
    "vote",
    {
      "voter": "mjhomb",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "c8bbc75c2a258c4e223d4f58a8a327b9135322df",
  "block": 27528709,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-08T19:53:24",
  "op": [
    "vote",
    {
      "voter": "ponggod",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "3b372605800c9927311c7766f23209c99c82081b",
  "block": 27525769,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-08T17:26:24",
  "op": [
    "vote",
    {
      "voter": "jadabug",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "weight": 150
    }
  ]
}

{
  "trx_id": "848529dda0cac3ee18fb969cedae46003d996c8e",
  "block": 27525538,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-08T17:14:51",
  "op": [
    "transfer",
    {
      "from": "allaz",
      "to": "ecaf",
      "amount": "0.001 SBD",
      "memo": "Promote your post. Your post will be min. 10  resteemed with over 13000  followers and min. 25  Upvote Different account (5000  STEEM POWER). Your post will be more popular and you will find new friends. Send 0.5 SBD or STEEM to @allaz (post URL as memo ) Service Active."
    }
  ]
}

{
  "trx_id": "309ea91fdf2da4d929dc3fb3e623d150c4ac0067",
  "block": 27525514,
  "trx_in_block": 46,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-08T17:13:39",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "ecaf",
      "author": "ecaf",
      "permlink": "ecaf-makes-history-today-with-its-first-ruling",
      "title": "ECAF makes history today with its first ruling",
      "body": "Today the EOS Core Arbitration Forum (ECAF) made history by issuing the first arbitral ruling on the EOS blockchain! To the best of our knowledge, this is also the first ever in the blockchain sphere.\n\n## The case\nThe case centred around a dispute on the ownership of an EOS account where the claimant alleged that they were victims of a phishing fraud that caused their account to be transferred without their consent at the time of EOS registration. This particular case involved one of the original accounts that were frozen at the launch of the EOS main net. Upon review of the case the arbitrator found in favour of the claimant and ordered that the account be returned to the claimant. More details of the case, the matters considered and the arbitrator’s ruling can be found here (https://eoscorearbitration.io/case-ecaf00000023/).\n\n## Why did it take this long?\nSome in the EOS community have questioned why it took so long to issue the first ruling. For many in the community their first, and frequently only, contact with alternative dispute resolution tends to be with a dispute on credit card transactions or bank charges which are resolved fairly quickly. It is important to note that such a model does not easily translate to the EOS context where a sequence of events and process needs to be followed:\n* There is no on-chain based system for account to account communication. Therefore sufficient time needs to be built into the arbitration process to allow for any respondent to come forward\n* The cases being considered are complex legal issues that span multiple domains including different blockchains, jurisdictions and approaches to governance \n* EOS by its nature is not a centralised system where one single party (e.g. the bank or credit card company) has control over the information, evidence gathering and enforcement. These cases often involve cooperation across multiple parties in the EOS community from the claimants themselves, interested parties, the respondents and finally the EOS Block Producers (BPs) who are tasked with enforcing the arbitrator’s decision.\n\nComplicating the above is the presently unfunded nature of ECAF which is currently a volunteer-driven effort. (ECAF has a fee structure and has started taking in fees, but because good practice is to refrain from disbursing fees until the conclusion of the case, the arbitrators have been working unpaid pending issuing final rulings.)\n\n## What next?\nThe ruling has been passed to the BPs who will be expected to utilise the eosio.wrap function to change the disputed account’s authorisation to the keys that the claimant has provided. At which point the claimant will gain possession of their account and will be able to transact with it as normal.\n\nThis first ruling has been much awaited by BPs and the community alike, and we hope that, barring problems with eosio.wrap, BPs will be able to enact the ruling in a reasonable timescale.\n\n## What more can we expect from ECAF?\nThis is the first of many rulings to come from ECAF’s arbitrators. With each ruling delivered we expect that we will improve our internal processes and hopefully become more efficient in doing so.\n\nHowever, this is not possible without your assistance. If you’d like to learn more or support ECAF’s work then you can:\n* Visit our website: https://eoscorearbitration.io/\n* Join the discussion on Telegram at https://t.me/eosarb\n* Nominate individuals for Case Manager and Arbitrator roles on Telegram at https://t.me/EOSArbNominations\n\n---\nPosted by M Tabulo, ECAF Interim Administrator",
      "json_metadata": "{\"tags\":[\"ecaf\",\"eos\"],\"links\":[\"https://eoscorearbitration.io/case-ecaf00000023/\",\"https://eoscorearbitration.io/\",\"https://t.me/eosarb\",\"https://t.me/EOSArbNominations\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}