Add Dingo Node to Builder Tools

[EarnCoinPool]

👋 Hello there! Welcome. Please follow the steps below to tell us about your contribution.

1. Please complete a Checklist
2. Fill in all sections of the template
3. Click "Create pull request"

Checklist

<-- Please fill the boxes with [x] before submitting a pull request -->

• I have read the Contributing Guidelines.
• I have read the Builder Tool Requirements
• I have added my image to src/data/builder-tools/images/
• I have run yarn build after adding my changes without getting any errors.
• I have not committed any changes to yarn.lock (or have removed these changes).

Builder Tool addition

<-- Provide information for every bullet in the list below. The tags you select must match the tags in your changes to tools.js -->

• Title: Dingo
• Description: A Cardano blockchain data node written in Go which actively participates in network communications on the Cardano blockchain using the Ouroboros Network Node-to-Node family of mini-protocols.
• Website: <https://github.com/blinklabs-io/dingo>
• Getstarted: <https://pkg.go.dev/github.com/blinklabs-io/dingo>
• Tags:
  • golang
  • nodeclient

[rphair]

@EarnCoinPool - from the description: suggested (cc @agaffney @wolf31o2), should Dingo be added to the Implementors: list for CIP-0137?

[wolf31o2]

Yes, both gOuroboros (library/protocol) and Dingo (implementation) support CIP-0137 messaging.

[rphair]

thanks @wolf31o2 ... if you submit a CIP repository PR to update CIP-0137 with Blink Labs as an implementor (I'll endorse it & would confirm @ the CIP meeting), I am sure it would both help the standard and encourage other node implementations (cc @jpraynaud) ⭐

[jpraynaud]

thanks @wolf31o2 ... if you submit a CIP repository PR to update CIP-0137 with Blink Labs as an implementor (I'll endorse it & would confirm @ the CIP meeting), I am sure it would both help the standard and encourage other node implementations (cc @jpraynaud) ⭐

Happy to see that other node implementations are willing to implement the DMQ protocol 👍

@wolf31o2, do you intend to implement the n2c only or both n2c and n2n mini-protocols?

For your information, we are currently working on some modifications to fix some problems we have identified in the protocol during the testing phase:

• The n2n message submission mini-protocol will have its agency reversed as this is creating problems with the peer discovery (see this draft PR CIP-0137 | Message Submission V2 + fixes CIPs#1141)
• The n2c local notification mini-protocol will be slightly change to provide better support of blocking and non-blocking requests
• We intend to enforce the computation of the message id to prevent some type of attacks (which will likely change the way the KES signature needs to be computed)

[wolf31o2]

Cool. We've implemented both n2n and n2c in gOuroboros and Dingo gets, but it hasn't been wired up just yet. We're also working on our own client application, so we're definitely interested in changes as they come.