Pinned post

Hello everyone! I’m Nathaniel, software developer (and avid coffee addict) by day and by night a pretty active gamer (lately it’s been World of Warcraft). My favorite drink is an old fashioned. 🍻 I joined mastodon to see what this open source platform is like. Cheers all! Happy to be here!

Once I finish learning C++, I’ll get back into working on Yggdrasil. 🙂

“The mind that is anxious about future events is miserable.”
- Seneca

Three days ago I started learning ++. I think after three days of working through this tutorial:, I have a pretty good understanding of the basics of C++ syntax. There are still some things I need more practice with, but I am glad that I’ve got the basics down at least. The thing that really sticks out to me is the amount of control that the programmer has over aspects of the runtime and value/object references as compared to Java.

“It is a rough road that leads to the heights of greatness.”
~ Seneca

Soon going to start learning C++ as required for work, kinda excited though because I think it’s going to be fun to get back into a lower level language again.

Right now I admit, it feels like the messaging protocol changes won’t end…but honestly it’s really important to get this part correct since it is pretty integral to blockchain data integrity in Yggdrasil. Made some good progress today on the response data handlers. Slowly making progress!

Started building qt locally like 15 minutes ago… still building lol. 😅

At some point, I will be making a thread on the messaging protocol of Yggdrasil and how this might solve the synchronization issues seen in decentralized systems.

Show thread

Continued writing some message handling this morning for the Yggdrasil blockchain and implemented a major difference to the messaging protocol from the Bitcoin protocol. For all getData-type requests, the response to those requests will include the checksum of the original getData request. This will allow nodes in the system to be able to match up the request and responding data in order to better make decisions around attempting to retrieve data from another peer.

Took a bit of a break from working on Yggdrasil and played some Destiny 2. It’s good to take some breaks, clear the mind, and come back to a task. When I first started that project, I got burned out and I really don’t want to do that again.

Additionally going to need to write more code comments and comment headers on all the messages once they are finalized, since those are protocol defs that won’t be changing very often.

Show thread

Documentation always feels tedious 😅, but I’ll definitely need to write some additional documentation into the Yggdrasil repo. It’s serverly lacking up-to-date config examples and does not have any protocol defs (though to be fair, protocol is what I am currently wrapping up at the moment…so that’s kind of expected to not be well documented yet).

So much more work to do. In the Yggdrasil code repo, there are definitions for handlers that correspond 1:1 with different message types that can be received by a node. Because of this architecture, there is a lot of additional implementation that I have been working on. Realizing too that there are some fundamental issues with the Txn definition in the core of Yggdrasil…so I’ll have to work on that as well to fix. At this point, I want to just get to a clean build 😅

Show thread

Once the build issues are fixed (mostly switching the handlers and deserializers to use the new message defs) then I can finally re-focus back on the core dev, ie, developing txn/block validation and development around txn input/output logic (and eventually txn scripting).

Show thread

I think I finally got the message protocol written for the Yggdrasil . Hoping to make a PR soon. The majority of the time was spent developing new message types for a (mostly) 1:1 to ’s protocol according to this doc:

“First say to yourself what you would be; and then do what you have to do.”

“A ship ought not to be held by one anchor, nor life by a single hope.”

Show older

The original server operated by the Mastodon gGmbH non-profit