Rules to live by. Check out https://tlu.tarilabs.com/cryptography/elliptic-curves and @tari_labs for some great content on elliptic curve cryptography.
The latest vid from @bitluni's channel is a piece of art. You don't know it yet, but you _want_ to know more about phased arrays. Go watch the vid. https://www.youtube.com/watch?v=z4uxC7ISd-c
Checking out the coding style requirements for contributing to the (amazing) SVG.js from @_wout_. This made me giggle: > avoid semicolons, we're not writing PHP here. (https://www.gijsvandam.nl/note/2022/02/25-5777)
Working through the docs of @statelyai, my eye fell on this pattern. Anybody know the official name? It's a JS callback pattern but you get a callback _and_ you get an onReceive that allows for registering a listener to an event at the parent. Voila: 2-way parent-child comms (https://www.gijsvandam.nl/photo/2022/02/22-49012)
Just had an amazing talk with the guys from the #connect_the_world podcast https://www.youtube.com/channel/UCLMp5bH-rY9aEVwfLQ3oq4Q The episode where I talk about my latest #lightningnetwork research will be online soon. (https://www.gijsvandam.nl/photo/2022/02/18-57744)
I am working on some animations to explain basic Lightning Network concepts. Needless to say, I'm not quite there yet.. (https://www.gijsvandam.nl/photo/2022/02/17-33011)
A great write-up on channel balance probing in Lightning Network over at Bitcoin Problems, by @serg_tikhomirov https://bitcoinproblems.org/problems/channel-balance-probing.html (https://www.gijsvandam.nl/note/2022/01/28-20879)
This is a really good (and entirely non-technical, for those who glaze over at equations) summary of a very thorny issue: repudiability in digital communications (it's technically only about DKIM, but the points made apply to other protocols than email).
I think I do agree with the conclusions, but it's something that isn't always so clear (how useful *in reality* are protocols like OTR, for example?)
https://blog.cryptographyengineering.com/2020/11/16/ok-google-please-publish-your-dkim-secret-keys/
Is it just me or are golang interfaces really confusing? I get it that it's low ceremony not having to declare the interface a type is using, but when reading code that is not your own (or that's old enough to be forgotten about entirely) it's just a pain in the butt. I'm constantly off on little puzzle tours finding interfaces that may or may not satisfy a signature.
I wrote a post on my debugging setup for LND.
https://gijswijs.github.io/posts/debugging-lnd/
Interested in how other people did this. I couldn't find much about this, so I had to figure most of this stuff out by myself.
@fribbledom You are my 1st follower! To what do I owe that pleasure?
En spreek je echt Nederlands?
"We didn't call it fuzzing back in the 1950s, but it was our standard practice to test programs by inputting decks of punch cards taken from the trash.
We also used decks of random number punch cards. We weren't networked in those days, so we weren't much worried about security, but our random/trash decks often turned up undesirable behavior.
Every programmer I knew used the trash-deck technique."
-- Gerald M. Weinberg
It is proven! I am gijsvandam on Keybase: https://keybase.io/gijsvandam/sigchain#57a11e7d449abdae54b1773cc974fa4f7476fb9bb0b05b7c586d268d1f108d130f
International man of cryptocurrency