tatmanblue/ironbar

.NET core distributed ledger application

Hi there 👋

I'm an engineer who's primary hobbies are programming for Unity and Dotnet. I also have interests in SSI and blockchain.

Several of my most active projects are private due to the fact I am publishing the artifacts and are commerical in nature. For those repos, a public repo with public information may also exist. And, I will entertain access to the private repos via a signed NDA agreement on an as needed basis. In particular:

• Max Capacity
• Pitcairn Island
• Unity projects shared with Max Capacity and Pitcairn Island
• TatmanGames and personal websites

A lot of the public repos are archives of very old projects I no longer work on. These are uploaded into github for archival purposes only and are marked archive.

Looking forward to hearing from you. In the mean time, check out my YouTube Channel for video updates.

Links

Linked In
YouTube

Top Technologies

Programming languages: C# • TypeScript • HTML • CSS • Rust • C/C++

Software: Visual Studio/Jet Brains • Unity • GitHub • Docker • Google Cloud

ironbar's Issues

Change block output format

Considering changing block output format (aka what's saved to file) to json instead of the custom string format. This is will achieve 2 things:

1. changes to block will be easier to manage including upgrades
2. help avoid block data containing the same character as the field separator from breaking parsing

Fix Boot Node / Child Node mess

The design was that boot node and child nodes are the same service just configured to run as either. For the most part this is true.

The mess lies in the types consumed in the service, and particularly with the event pub/sub system and the ledger system(s).

Not sure what the best approach is to correct these. Refactoring around injection, interfaces and maybe implement a strategy pattern or something similar.

Note: this issue is mostly another one of these issues that will be fixed over time as other work is completed.

Fix Interface Mess

The implementation is a bit of a mess when it comes to:

1. Some types are injected without an interface
2. Some types implement an interface, but references are not to the interface