And now for something different than the ongoing GitHub nonsense:

And now for something different than the ongoing GitHub nonsense:

https://paragraph.xyz/@quilibrium.com/quil-builders-guide

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

We have a full build tool repo, although GitHub is an ongoing issue we need to have a conclusion on before making any more updates there, so I’m going to release a local simulator tool so you can experiment all you'd like in a Q like environment next week, will land on

W̴̢̛͈̘͇̃̾̐̚͝ͅė̴̱b̴͖̱͗̓͗3̸͖͙̫͙̾̂̊ ̸̥͍̙͉̙̉̀̕͝͝͝D̵͇͖̲͆͊̋͝è̷̺̓v̷͙̟͖̥͔̆, 🟪#153

We have a full build tool repo, although GitHub is an ongoing issue we need to have a conclusion on before making any more updates there, so I’m going to release a local simulator tool so you can experiment all you'd like in a Q like environment next week, will land on https://source.quilibrium.com

If I want to play around and do some simple examples where do I go? My guess would be the ceremony repo but would love some simple directions on where and how to get started, either here or in the blog post 😁

exactly, that's why go is ideal here: it's really easy to compile to garbled circuits, and opens up so much existing battle-tested code for reusability

I don't think go is a great tool always – in fact, I regret choosing it for the node software itself, but in this use case it's a good balance.

i feel like specialized languages are usually a mistake

hubris to think your use case is so important to optimize for that it's worth abandoning having a larger developer community to onboard and learn from