Johan Torås Halseth

My talk from btc++ earlier this year is up here for you all to enjoy 💅💅

Dette er den harde realiteten av å være gründer. Du kan på kort tid miste hele livsverket ditt. Tenk om Karl hadde flyttet til utlandet da papirverdien av hans Oda-aksjer var verdt flere hundre millioner. Han ville fått en betydelig exit-skatt, og deretter blitt kalt inn til en generalforsamling hvor han opplever at verdiene hans praktisk talt nå er satt til null. Skatteregningen på flere titalls millioner ville fortsatt bestått. At både formuesskatt og exit-skatt er en realitet i Norge, er helt sjukt. Håper @kariekas , @SVparti, @Arbeiderpartiet, @Senterpartiet og resten av venstresiden nå forstår hva vi mener med papirverdi og arbeidende kapital.

NORWAY IS GOING TO BAN BITCOIN MINING WITHOUT PUBLIC CONSULTATIONS - WE NEED TO ACT NOW Norway's Ministry of Digitalisation and Public Administration responded to @ODFoundation that it "has no plans to conduct a public consultation" on a ban on cryptocurrency mining. There is no doubt that the ban designed to target #Bitcoin mining. Unfortunately, that's a stance of the @Stortinget and the Norwegian government. #m2" target="_blank" rel="nofollow noopener">stortinget.no/no/Saker-og-pu… 🔴 Why we should protect our #freedomtech Bitcoin in #Norway NOW: (1) Norway is fully integrated in the European Single Market throught the European Economic Area (EEA) and Schengen Agreement. It means Norway can provide its legilsative approach as an input for new legislation for the EU/EEA both: - during the preparatory phase, when the @EU_Commission is developing proposals; - during work of expert groups and committees of the European Commission; - submitting proposals and comments to European Free Trade Association on upcoming legislation. (2) As a co-founder of the @OECD , Norway sets an example of regulation worldwide and provides its legislative recommedations for global standards. (3) Norway has historically been a place to meet, share experiences and educate human rights defenders and bitcoiners from around the world. Norwegian goverment will present its investigation a ban on cryptocurrency mining by the end od 2024. 🔴 What we should do together to prevent Bitcoin mining ban: (1) Repost this post and join our #BTC Coalition to educate local communities and media about social benefits of Bitcoin mining in Norway and worldwide; (2) Help us pool resources and best practices to convince Norwegian politicians and media to explore the social benefits of Bitcoin to prevent this repressive regulation; (3) If you are a Norwegian citizen: write a letter to your legislator and government asking for public consultation and providing arguments about the social benefits of Bitcoin mining for Norway. 🧡

@roasbeef Lots of script wizardry in that repo!🤩 I also tried implementing u32 multiplication in Script, but couldn't easily get it below 10k bytes, so changed to a RISCV compiler target without multiplication instead 🤷‍♂️

@johanth makes sense re blow up for larger precision arithmetic, multiplication also dominates the weight of the m31 for the OP_CAT based circle stack impl: #performance" target="_blank" rel="nofollow noopener">github.com/Bitcoin-Wildli…

There's been a lot of excitement around new #Bitcoin layer-2s and off-chain protocols lately. Kicked off by the Taproot upgrade and entering full force with MATT and BitVM, several promising protocols are being developed 🔧 (Thread on protocols and a ZK verifier demo🧵)

@roasbeef So even though there's a lot of scripts, they will be assembled into a taptree, and only a single one is executed in the worst case. (then there's tranasctions for the challenge game, but they are much smaller)

@roasbeef There's about 110k leaf scripts created (one for each program counter) and the largest script is 6143 bytes (32 bit unsigned subtraction (wtb 64-bit script arithmetics) 😄

And with BitVM being heavily researched, maybe we can get close to this dream even without a script upgrade? 🤯 x.com/johanth/status…

Here's an example of using Elftrace to compile the Winterfell ZK-STARK verifier to Bitcoin Script and use it to verify-the-verification of a STARK: github.com/halseth/elftra…

@theinstagibbs @salvatoshi Depends on what input needs to be public. I believe one could also have the state transitions be kept client side (zkp=“I prove that I have validated signatures for all clients taking state from A to B”). @lightcoin would probably know

@johanth @salvatoshi It would need the state transitions on-chain + zkp, right? unless we rely on some federated/trusted system for proof of publication

Has anyone thought about making a non custodial, privacy preserving optimistic roll-up, that has the ZKP parts only validated optimistically? Could we avoid being blocked on OP_ZKP? What opcodes would be useful for that?

@salvatoshi @theinstagibbs If incentives are aligned, the avg cost would be ~size of the ZK proof.

@theinstagibbs @johanth Yup. Also, that's the worst case to settle a fraud, like all optimistic protocols; in the happy case, it doesn't go on-chain.

@reardencode @rusty_twit How does OP_INTERNALKEY mitigate the penalty?

So, 32-byte segwitv1, as a leaf script version. I don't think it makes any sense to break the anonymity set with segwitv2 32-byte only to save the script-only penalty that can be commonly mitigated (as in ln-symmetry) with INTERNALKEY. What say you @rusty_twit @johanth @stevenroose3 ?

@reardencode @josibake @stevenroose3 @rusty_twit @jesseposner @roasbeef As a developer that has attempted to implement a custom multisig scheme using x-only keys (and failed because of parity problems), I think we cannot really say for sure that all future schemes we can come up with won’t have escalating parity complexity.

Here're the thoughts that have shifted me toward taproot32, new script version: * @jesseposner teaching me more about FROST showed that there isn't escalating complexity to dealing with X-only keys as we develop additional off chain signature aggregation methods. * @roasbeef's wondering whether software will need upgrades to handle the new output type (unfortunately, because taproot32 is one of the valid lengths for segwitv0 addresses, I think this is likely) * splitting the anonset is only partially transient - addresses with no internal key will reveal that they never had them either in their output or their input, breaking them into a separate pool durably * @jxpcsnmz reminds us that most contracts can come up with some useful internal key (e.g. a MuSig2 of everyone involved) Keeping me a fence sitter are: * I suspect that some future off chain signature aggregation protocols will still end up being impractical in some scenarios because of the lack of known parity for all parties * even INTERNALKEY will split the anonset when used for non-key data, and most NUMS users use the single NUMS key from the BIP, not one that hides their use (so the taproot anonset is practically already split) * there are also still a good number of contracts that do not have use for an internalkey (e.g. vault staging transactions, lightning force closes) * better to make software that only handles taproot32 addresses also handle other lengths earlier than later

Utreexod beta release is now available at github.com/utreexo/utreex…! I’m currently syncing my archival node on a raspberry pi 0. Planning to use the built in electrum personal server support to connect my personal wallet. Please try it out and let me know what you think! For more info: groups.google.com/g/bitcoindev/c…