_ _ _
| | | | | |
_ _| |___ _____ ___| |_ _| |__
| | | | __\ \/ / _ \ / __| | | | | '_ \
| |_| | |_ > < (_) | (__| | |_| | |_) |
\__,_|\__/_/\_\___(_)___|_|\__,_|_.__/
pay this invoice to help fund my expensive test-on-mainnet addiction:
or send an unspecified amount onchain 👀
this could be you
At Frostsnap ❄ we're building the new age of mathematically enforced monetary powertools. With Frostsnap, you can protect digital assets and identity behind multiple keys:
For example, you could arrange a '2-of-3' where one key is your phone, one is a hardware wallet device, and the third key is given to a friend you trust. In order to spend your bitcoin you must sign on two of these three devices.
An alternative scenario is a company with a treasury and identity they need to protect. They have a bunch of executives, say 6. The executives generate a Frostsnap key which they share, requiring 4-of-6 excetutives to sign in order to take actions on behalf of the company.
The ownership of this money and indentity (read: social media) is
cryptographically protected through mathematics; making you secure,
soverign, and uncensorable.
Frostsnap provides upmost financial flexibility suited to your
needs as an individual or organisation, you're not just another
customer at a bank.
FROST has good privacy, scales well with fees, and is malleable (can
add or remove signers after key generation!). 🪄
polynomials ❄.
Team (Lloyd, Adam, myself) were recently spotted booth hijacking and performing rogue demos of our stealth Frostsnap project @ BTCPrague,
A plus of the work from home ratcage during lockdowns was that lots
of time could be spent on my first free open-source software
project: SatSale.
SatSale is a lightweight payment processor written in python -
SatSale.org.
Notably it was the first piece of software I have written which
others have found to be useful.
You can connect SatSale to your own Bitcoin node or clightning/lnd
node. SatSale also supports xpubs, lightning addresses, woocommerce
point-of-sales and more! It can be used to spit out unique addresses
like we see around this page (test em).
Making a blind schnorr signature implementation in a
PR to secp256kfun.
Blind signatures allow you to disguise a message which you then ask
a signing server to sign. Once you recieve the signature for the
message, you can unblind it, resulting in a completely new signature
that is still valid under the server's public key.
You can have a server sign something, without them learning what
they have signed! This is powerful for building coordinators or
authorities that respect user privacy.
I've built a demonstration of
blind schnorr signatures
👀 which runs entirely in browser using WASM 🦀 and it can even sign
a Nostr post!
I've also been helping make the secp256kfun MuSig2 implementation compatible with the MuSig BIP. Work was needed for the the ability to create "ordinary" taproot tweaks to the joint MuSig key. These ordinary tweaks, as opposed to X-only tweaks, are used to derive BIP32 child keys for addresses using the MuSig aggregate key.
