{
  "@context": {
    "CIP100": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#",
    "hashAlgorithm": "CIP100:hashAlgorithm",
    "body": {
      "@id": "CIP100:body",
      "@context": {
        "references": {
          "@id": "CIP100:references",
          "@container": "@set",
          "@context": {
            "GovernanceMetadata": "CIP100:GovernanceMetadataReference",
            "Other": "CIP100:OtherReference",
            "label": "CIP100:reference-label",
            "uri": "CIP100:reference-uri",
            "referenceHash": {
              "@id": "CIP100:referenceHash",
              "@context": {
                "hashDigest": "CIP100:hashDigest",
                "hashAlgorithm": "CIP100:hashAlgorithm"
              }
            }
          }
        },
        "comment": "CIP100:comment",
        "externalUpdates": {
          "@id": "CIP100:externalUpdates",
          "@context": {
            "title": "CIP100:update-title",
            "uri": "CIP100:uri"
          }
        }
      }
    },
    "authors": {
      "@id": "CIP100:authors",
      "@container": "@set",
      "@context": {
        "name": "http://xmlns.com/foaf/0.1/name",
        "witness": {
          "@id": "CIP100:witness",
          "@context": {
            "witnessAlgorithm": "CIP100:witnessAlgorithm",
            "publicKey": "CIP100:publicKey",
            "signature": "CIP100:signature"
          }
        }
      }
    }
  },
  "authors": [],
  "body": {
    "comment": "I vote YES on the treasury withdrawal proposal “Dingo: a Production-Grade Block Producer in Go by Blink Labs” (gov_action17dfgtkeufcy945e3ssanqpmn09ft3gezhvepvvg7msmlmaz260dqqjtsmpe).\n\nIt is refreshing to see a continued return to detailed, well-composed governance action proposals, backed by numerous supporting links, after a recent drop in proposal quality. The Blink Labs team has a history of developing open source software for the Cardano ecosystem and are seeking funding for the continued development of a Cardano node written in the Go programming language.\n\nI have already seen some comments like “no use case” and “a hobby project” from early voting DReps and so did some digging into current applications using Go in the wider world today. I knew IPFS was built on Go having installed it on a server at home already but beyond that I hadn’t quite appreciated the scale of its use in cloud infrastructure and distributed systems. Ethereum's primary execution node client Geth (short for Go Ethereum) accounts for ~66% of the Ethereum networks execution layer nodes as of October 2025 (having held a previous high of ~85%), while Go is also utilised across the Cosmos SDK, Docker and Kubernetes, and Hyperledger Fabric to name but a few instances. Its wide application across cloud computing, microservices and DevOps tools is supported by a global community of ~5 million+ developers. Investing in a Go node would not be merely funding a “hobby project”, it would be a strategic investment in opening Cardano up to a large developer community, predominantly in enterprise and cloud infrastructure fields.\n\nThis doesn’t appear to simply be a case of a team looking to cash in on a potential “node diversity goldrush”, coming so soon after the recent Amaru node proposal, they have a track record of work and delivery in the Cardano ecosystem and operate with a dedication to open source practices. While some DReps have expressed concerns regarding some of the quoted FTE rates within this proposal, it does feel like it could be an acceptable trade-off for the potential upside that a successful Go node implementation could bring by opening the Cardano ecosystem up to a much wider developer talent pool and the wider cloud computing/distributed systems space.\n\nI have also seen some comments along the lines of “not necessary, everyone will use the Rust node”. This is also short-sighted. Funding node diversity to reduce the single node client risk to then all move to that same new client would be counter-intuitive to the intended decentralisation effort. Having a third node client here would be more beneficial to that end, not detrimental. The event of November 2025 highlighted the need for greater node diversity, now more than ever.\n\nWhile a largely well written and documented proposal, it is worth noting for a moment that the Constitutionality Checklist does contain some errors. This practice of self-awareness has been much welcomed as governance progressed through its first year as it helped reduce bad proposals being submitted. Unfortunately, although stating that the checklist included here follows Constitution 2.4, it actually utlises an older template from Pragma that has not yet been updated since the previous Constitution (https://github.com/pragma-org/mnemos/blob/3402a6f12ffb042783112eeb5d3f30ae4f3965d4/BudgetInfoActionProposalTemplate.md) and as a result references incorrect Constitution articles within the proposal. While not a deal breaker here as a “Constitutionality Checklist” is largely an exercise in “self-awareness” and ultimately it is the Constitutional Committee that decides what is and what isn’t constitutional, it is an unfortunate blemish on what was otherwise a well put together proposal document. I have reached out to the proposer and it has been confirmed that the template used will be updated to reflect the new relevant sections of the Constitution, namely Article II Sections 6 & 7, for anyone else seeking to reference the template in the future."
  },
  "hashAlgorithm": "blake2b-256"
}